WO2010124422A1 - 同步实体创建、更新和释放方法、基站和广播组播业务中心 - Google Patents

同步实体创建、更新和释放方法、基站和广播组播业务中心 Download PDF

Info

Publication number
WO2010124422A1
WO2010124422A1 PCT/CN2009/000473 CN2009000473W WO2010124422A1 WO 2010124422 A1 WO2010124422 A1 WO 2010124422A1 CN 2009000473 W CN2009000473 W CN 2009000473W WO 2010124422 A1 WO2010124422 A1 WO 2010124422A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
entity
synchronization
indication
synchronization entity
Prior art date
Application number
PCT/CN2009/000473
Other languages
English (en)
French (fr)
Inventor
陈宇
王河
Original Assignee
上海贝尔股份有限公司
阿尔卡特朗讯
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 上海贝尔股份有限公司, 阿尔卡特朗讯 filed Critical 上海贝尔股份有限公司
Priority to BRPI0925082-4A priority Critical patent/BRPI0925082A2/pt
Priority to JP2012507565A priority patent/JP5250719B2/ja
Priority to CN200980157385.XA priority patent/CN102326433B/zh
Priority to EP09843834.4A priority patent/EP2427003A4/en
Priority to US13/318,105 priority patent/US8867424B2/en
Priority to KR1020117025650A priority patent/KR101351290B1/ko
Priority to RU2011141582/07A priority patent/RU2491786C2/ru
Priority to PCT/CN2009/000473 priority patent/WO2010124422A1/zh
Publication of WO2010124422A1 publication Critical patent/WO2010124422A1/zh
Priority to US14/518,781 priority patent/US9609611B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W56/00Synchronisation arrangements
    • H04W56/001Synchronization between nodes
    • H04W56/002Mutual synchronization
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W56/00Synchronisation arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices

Definitions

  • the present invention relates to the field of mobile communications, and more particularly to an eNB (base station) and a BM-SC
  • SYNC synchronization
  • update update
  • release procedures broadcast multicast service centers
  • eNBs and BM-SCs for implementing the SYNC entity creation, update, and release procedures described above.
  • the SYNC entity peer t is located in the eNB and BM-SC to ensure content synchronization between the two SYNC entities.
  • 3 GPP generally recognizes the service statistics multiplexing scheme (sat isti ca l mul ti plexing), in which multiple services are Performing bundling or grouping, and can treat the service bundle or service button as a virtual large service, thereby simplifying; (2) - only one MBSFN (Multimedia Broadcast Multicast Service Single Frequency Network) area in one cell, one MBSFN area All cells transmit the same service.
  • 3 GPP generally recognizes the service statistics multiplexing scheme (sat isti ca l mul ti plexing), in which multiple services are Performing bundling or grouping, and can treat the service bundle or service button as a virtual large service, thereby simplifying
  • MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
  • the present invention proposes a novel SYNC entity creation, update and release procedure between eNB and BM-SC, and an eNB and BM SC for implementing the above SYNC entity creation, update and release procedures.
  • a method for creating a SYNC entity including: creating, at a BM-SC, the same number of SYNC entities as the total number of services, and correspondingly creating a plurality of SYNC entities The manner is associated with the service; sending a SYNC entity creation indication to all eNBs in the MBSFN area; at each eNB, creating the same number of SYNC entities as the total number of services according to the received SYNC entity creation indication, and The multiple SYNC entities created are associated with the service in a corresponding manner.
  • the SYNC entity creation indication comprises: a total number of services, service identification information, and a service start indication.
  • a method for updating a SYNC entity comprising: at a BM-SC, when a new service starts, a new SYNC entity is created, and the newly created SYNC entity is correspondingly The mode is associated with the new service; the SYNC entity update indication is sent to all eNBs in the MBSFN area; at each eNB, a new SYNC entity is created according to the received SYNC entity update indication, and the newly created SYNC entity is -- The corresponding way is associated with the new business.
  • the SYNC entity update indication comprises: service identification information and a service start indication.
  • a SYNC entity release method including: at a BM-SC, when an original service ends, releasing a SYNC entity associated with the original service; to an MBSFN area All eNBs transmit a SYNC entity release indication; at each eNB, the SYNC entity associated with the legacy service is released based on the received SYNC entity release indication.
  • the SYNC entity release indication comprises: service identification information and a service end indication.
  • a method for creating a SYNC entity including: creating, at a BM-SC, the same number of SYNC entities as the total number of service groups, and creating a plurality of SYNC entities by Corresponding manner is associated with the service group; sending a SYNC entity creation indication to all eNBs in the MBSFN area; at each eNB, creating the same number of multiple SYNC entities as the total number of service groups according to the received SYNC entity creation indication And associate multiple SYNC entities created with a business group in a "" * corresponding manner.
  • the SYNC entity creation indication comprises: a total number of services, industry group information, and a service start indication.
  • the SYNC entity creation indication includes: a total number of services, service identification information, and a service start indication, and buffering and reorganizing data packets of each service at the BM-SC.
  • a method for updating a SYNC entity including: at a BM-SC, when a new service starts, first determining whether a new service belongs to an existing service group; when the new service does not belong to any one When there is a service group, a new SYNC entity is created, and the newly created SYNC entity is associated with the new service in a corresponding manner; a SYNC entity update indication is sent to all eNBs in the MBSFN area; at each eNB, According to the received SYNC entity update indication, first determine whether the new service belongs to the existing service group; when the new service does not belong to any existing service group, create a new SYNC entity, and the newly created SYNC entity is - The corresponding way is associated with the new business
  • the SYNC entity update indication includes: service identification information, service group information, and service start indication.
  • the SYNC entity update indication includes: service identification information and a service start indication, and buffering and reorganizing data packets of each service at the BM-SC.
  • the SYNC entity update method further includes: at the BM-SC, when the new service belongs to the existing service group, directly sending a SYNC entity update indication to all eNBs in the MBSFN area; and at each eNB, when When the new service belongs to an existing service group, the SYNC entity update process is directly ended.
  • a method for releasing a SYNC entity including: determining, at the BM-SC, whether the original service is the last service in the belonging service group when the original service ends; When the original service is the last service in the associated service group, release the SYNC entity associated with the associated service group; send a SYNC entity release indication to all eNBs in the MBSFN area; at each eNB, according to the received The SYNC entity is released to indicate whether the original service is the last service in the service group; when the original service is the last service in the service group, the SYNC associated with the service group is released. entity.
  • the SYNC entity release indication comprises: service identification information, service group information, and a service end indication.
  • the SYNC entity release indication includes: service identification information and a service end indication, and buffering and reorganizing data packets of each service at the BM-SC.
  • the SYNC entity release method further includes: at the BM-SC, when the original service is not the last service in the belonging service group, directly to the MBSFN area All eNBs send a SYNC entity release indication; and at each eNB, when the original service is not the last service in the belonging service group, the SYNC entity release process is directly ended.
  • a SYNC entity creation method comprising: creating or statically configuring a single SYNC entity at a BM-SC; transmitting a SYNC entity creation indication to all eNBs in an MBSFN area; At the eNB, a single SYNC entity is created based on the received SYNC entity creation indication.
  • the SYNC entity creation indication includes: service identification information, service group information, and service start indication.
  • the SYNC entity creation indication comprises: service identification information and a service start indication, and buffering and reorganizing data packets of each service at the SC-SC.
  • the SYNC entity creation method further comprises: sending a SYNC entity update indication from the BM-SC to all eNBs in the MBSFN area.
  • the SYNC entity update indication includes: service identity information, service packet information, and a service start indication; or the SYNC entity update indication includes: service identity information, service group information, and a service end indication.
  • the SYNC entity update indication includes: the service identity information and the service start indication, or the SYNC entity update indication includes: the service identity information and the service end indication, and at the leg-SC, the data packet of each service is performed. Cache and reorganize.
  • a BM-SC comprising: a SYNC entity creating unit for creating a SYNC entity; and a SYNC entity associating unit for using a SYNC entity created by a SYNC entity creating unit with a service or service
  • the indication unit is configured to transmit a SYNC entity creation indication or a SYNC entity update indication to all eNBs in the MBSFN area.
  • the BM-SC further includes: a service initiation/ending unit, configured to determine whether a new service starts or whether the original service ends; and a SYNC entity release unit, configured to release the SYNC entity according to the service or the service group,
  • the service initiation/end unit instructs the SYNC entity creation unit to create a SYNC entity when it is determined that a new service starts.
  • the service initiation/closing unit instructs the SYNC entity release unit to release the SYNC entity
  • the indication unit is further configured to transmit a SYNC entity release indication to all eNBs in the MBSFN area.
  • the SYNC entity creation unit creates a SYNC entity according to a service or a service group.
  • an eNB comprising: a receiving unit, configured to receive a SYNC entity creation indication or a SYNC entity update indication from a BM-SC; a SYNC entity creation unit, configured to create a SYNC entity; A unit, configured to associate a SYNC entity created by a SYNC entity creation unit with a service or a business group.
  • the receiving unit is further configured to receive a SYNC entity release indication from the BM-SC, and the eNB further includes: a SYNC entity release unit, configured to release the SYNC entity according to the service or the service group.
  • the SYNC entity creation unit creates a SYNC entity based on the service or service group.
  • the above various alternatives in accordance with the present invention successfully solve the configuration problems with respect to the SYNC entity, each having its own advantages and disadvantages (see the detailed analysis of the Detailed Description section).
  • a person skilled in the art can select an appropriate technical solution according to actual needs.
  • Figure 1A shows an embodiment in which each service has a corresponding SYNC entity
  • FIG. 1B shows a SYNC entity creation process according to Embodiment 1.
  • FIG. 1C shows a SYNC entity update procedure according to Embodiment 1.
  • FIG. 1D shows a SYNC entity release process according to Embodiment 1.
  • Embodiment 2A shows a schematic diagram of Embodiment 2 in which a SYNC entity is based on a service multiplexing group.
  • Fig. 2B shows a SYNC entity creation process according to Embodiment 2.
  • Figure 2C shows the SYNC entity update procedure according to embodiment 2.
  • Fig. 2D shows the SYNC entity release process according to Embodiment 2.
  • FIG. 3A shows a schematic diagram of Embodiment 3 in which the SYNC entity is based on the MBSFN area.
  • FIG. 3B shows a specific operation flow of Embodiment 3, including: a SYNC entity creation process and a SYNC entity update process.
  • Figure 4 shows a block diagram of the structure of the SC for implementing the SYNC entity creation, update and release procedures described above.
  • FIG. 5 is a block diagram showing the structure of an eNB for implementing the above SYNC entity creation, update and release procedures. detailed description
  • MBMS Multimedia Broadcast Multicast Service
  • SYNC entity configuration schemes will affect the complexity of the SYNC protocol and system.
  • a pair of peer SYNC entities ensures that the content of the data is synchronized between the two.
  • service multiplexing based on the byte count and the packet count, multiple services are related to each other, especially in the case where packet loss occurs at the service switching point. Therefore, the synchronization of a business will affect other services that are multiplexed with it. In this case, the SYNC entities also become related to each other.
  • Embodiment 1 Each service has a corresponding SYNC entity
  • Figure 1A shows a schematic diagram of Embodiment 1 in which each service has a corresponding SYNC entity.
  • Embodiment 1 is the most straightforward solution, in which case the SYNC entity is service dependent.
  • the SYNC entity is created or released at the start or end of the business. Since the packet count and the byte count are performed independently for each service, in the case where packet loss occurs in the multiplexed service group, it can be clearly determined which service or services will be affected by the packet loss. Based on this point, Embodiment 1 is inherently robust in dealing with the problem of packet loss at the service transmission switching point.
  • Embodiment 1 In general, the advantages and disadvantages of Embodiment 1 are as follows:
  • Figures IB ⁇ ID show the specific operational flow of Embodiment 1, including: SYNC entity creation process, SYNC entity update process, and SYNC entity release process.
  • FIG. 1B shows a SYNC entity creation process according to Embodiment 1.
  • the BM-SC creates the same number of multiple SYNC entities as the total number of services.
  • the BM-SC associates the created plurality of SYNC entities with the service in a corresponding manner, each SYNC entity is associated with a service, and each service is also associated with a SYNC entity.
  • the BM-SC sends a SYNC entity creation indication to the eNB in the MBSFN area, where the SYNC entity creation indication may include: a total number of services, a service identifier 00473
  • step S107 the eNB creates the same number of multiple SYNC entities as the total number of services according to the received SYNC entity creation indication.
  • step S109 the eNB associates the created plurality of SYNC entities with the service in a corresponding manner, each SYNC entity is associated with a service, and each service is also associated with a SYNC entity. In this way, the SYNC entity creation process is completed.
  • This SYNC entity creation process typically occurs during system initialization.
  • the SYNC entity update process and the SYNC entity release process are performed when the system is already running and a business change occurs during the run (new service start or legacy service end).
  • FIG. 1C shows a SYNC entity update procedure according to Embodiment 1.
  • the leg-SC creates a new SYNC entity.
  • the BM-SC associates the newly created SYNC entity with the new service in a corresponding manner.
  • the BM-SC sends a SYNC entity update indication to the eNB in the MBSFN area, where the SYNC entity update indication may include: service identification information and a service start indication.
  • the eNB creates a new SYNC entity according to the received SYNC entity update indication.
  • the eNB associates the newly created SYNC entity with the new service in a corresponding manner. In this way, the SYNC entity update process for the start of a new service is completed.
  • FIG. 1D shows a SYNC entity release process according to Embodiment 1.
  • the BM-SC detects the end of the original service.
  • the BM-SC releases the SYNC entity associated with the service.
  • the BM-SC sends a SYNC entity release indication to the eNB in the MBSFN area, where the SYNC entity release indication may include: service identification information and a service end indication.
  • the eNB releases the SYNC entity associated with the service according to the received SYNC entity release indication. In this way, the SYNC entity release process for the end of the original service is completed.
  • Embodiment 2 SYNC entity based on service reuse group
  • Embodiment 2A shows a schematic diagram of Embodiment 2 in which a SYNC entity is based on a service multiplexing group.
  • the SYNC entity is based on a service multiplexing group, that is, each service multiplexing group has a corresponding SYNC entity.
  • the creation and release of SYNC entities is less frequent because only all services in the service reuse group At the end of the release, the SYNC entity associated with the service reuse group is released.
  • Embodiment 2 The advantage of Embodiment 2 is that the SYNC entity is originally designed to support service multiplexing (for example, the multiplexed service can be regarded as a virtual service); the non-multiplexing scenario can be regarded as a special service complex. Used (ie, each service is reused separately). In Embodiment 2, additional information is required to identify each service in the same SYNC entity; or data packets of different services may be buffered and shuffled at the BM-SC before transmission.
  • service multiplexing for example, the multiplexed service can be regarded as a virtual service
  • the non-multiplexing scenario can be regarded as a special service complex. Used (ie, each service is reused separately).
  • additional information is required to identify each service in the same SYNC entity; or data packets of different services may be buffered and shuffled at the BM-SC before transmission.
  • Embodiment 2 In general, the advantages and disadvantages of Embodiment 2 are as follows:
  • the multiplexed service is regarded as a virtual service, which can more easily support service reuse;
  • 2B to 1D show the specific operational flow of Embodiment 2, including: SYNC entity creation process, SYNC entity update process, and SYNC entity release process.
  • FIG. 2B shows a SYNC entity creation process according to Embodiment 2.
  • the BM-SC creates the same number of SYNC entities as the total number of service groups.
  • the BM-SC associates the created plurality of SYNC entities with the service group in a corresponding manner, each SYNC entity is associated with a service group, and each service group is also associated with one SYNC entity.
  • the BM-SC sends a SYNC entity creation indication to the eNB in the MBSFN area, where the SYNC entity creation indication may include: a total number of services, service group information, and a service start indication.
  • step S2 Q7 the eNB creates the same number of SYNC entities as the total number of service groups according to the received SYNC entity creation indication.
  • step S209 the eNB associates the created plurality of SYNC entities with the service group in a corresponding manner, each SYNC entity is associated with one service group, and each service group is also associated with one SYNC entity. In this way, the SYNC entity creation process is completed.
  • This SYNC entity creation process typically occurs during system initialization. When the system is already running, but in transit When a business change occurs during the process of the line (new business starts or the original business ends), it will be executed
  • step S210 when a new service starts, the BM-SC first determines whether the new service belongs to the existing service group. If the new service belongs to the existing service group (step S210: YES), the BM-SC directly performs step S215. On the other hand, if the new service does not belong to any of the existing service groups (step S21 0: NO), then in step S211, the BM-SC creates a new SYNC entity. In step S213, the BM-SC associates the newly created SYNC entity with the new service in a corresponding manner.
  • step S215 the BM-SC sends a SYNC entity update indication to the eNB in the MBSFN area, where the SYNC entity update indication may include: service identification information, service group information, and service start indication.
  • step S216 the eNB first determines whether the new service belongs to the existing service group according to the received SYNC entity update indication. If the new service belongs to the existing service group (step S216: YES), the eNB does not need to perform any SYNC entity update operation, and in step S218, the SYNC entity update operation is ended.
  • step S216 if the new service does not belong to any of the existing service groups (step S216: NO), then in step S217, the eNB creates a new SYNC entity based on the received SYNC entity update indication. At step S219, the eNB associates the newly created S YNC entity with the new service in a corresponding manner. In this way, the SYNC entity update process for the start of a new service is completed.
  • FIG. 2D shows the SYNC entity release process according to Embodiment 2.
  • the BM-SC detects the end of the original service.
  • the BM-SC determines whether the original service is the last service in the belonging service group. If the original service is not the last service in the associated service group (step S222: NO), the BM-SC directly performs step S225. On the other hand, if the original service is the last service in the associated service group (step S222: Yes), then in step S223, the BM-SC releases the SYNC entity associated with the associated service group.
  • step S225 the BM-SC sends a SYNC entity release indication to the eNB in the MBSFN area, where the SYNC entity release indication may include: service identification information, service group information, and service end indication.
  • the eNB first determines whether the original service is the last service in the belonging service group according to the received SYNC entity release indication. If the original service is not the last service in the associated service group (step S226: NO), the eNB does not need to perform any SYNC entity release operation, in the step S228, ending the SYNC entity release operation.
  • step S227 the eNB releases the SYNC entity associated with the associated service group according to the received SYNC entity release indication. In this way, the SYNC entity release process for the end of the original service is completed.
  • service grouping information is used to identify different services in the service group, but as mentioned earlier, caching and reorganization can also be performed at the ship-SC. Way, and omitting these extra letters
  • Embodiment 3 SYNC entity based on MBSFN area
  • FIG 3A shows a schematic diagram of Embodiment 3 in which the SYNC entity is based on the MBSFN area 326.
  • each MBSFN area has only one SYNC entity, and the SYNC entity can be statically configured and never released. It seems that Example 3 seems simpler, but it is not.
  • Different services may be transmitted in different ways: Multiplex/non-multiplexed; Some services have ended / Some services are still in progress. Since the byte count and the packet count are counted together for all services, the ongoing business may be affected by the business that has ended. In fact, there is no need to share a SYNC entity between services that are not related to each other. Therefore, Embodiment 3 may be more complicated in the design of the SYNC mechanism.
  • Embodiment 3 In general, the advantages and disadvantages of Embodiment 3 are as follows:
  • FIG. 3B shows a specific operation flow of Embodiment 3, including: a SYNC entity creation process and a SYNC entity update process.
  • step S301 the BM-SC creates or statically configures a single SYNC entity.
  • step S305 the BM-SC sends a SYNC entity creation indication to the eNB in the MBSFN area, where the SYNC entity creation indication may include: service identification information, service group information, and a service start indication.
  • step S307 the eNB creates a single SYNC entity according to the received SYNC entity creation indication. In this way, the SYNC entity creation process is completed.
  • This SYNC entity creation process occurs during system initialization.
  • the SYNC entity update process is performed when the system is already running and a business change occurs during the run (new business start or legacy business end).
  • the leg-SC sends a SYNC entity update indication to the eNB in the MBSFN area
  • the SYNC entity update indication may include: service identification information, service group information, and service start indication (or service) End instruction). In this way, the SYNC entity update process is completed.
  • FIG. 4 shows a block diagram of the structure of a BM-SC for implementing the SYNC entity creation, update and release procedures described above. It should be noted that, for the sake of convenience, FIG. 4 shows all of the components that may be required for each process, but in the case of any single process, all of these components are not required to be completed, and those skilled in the art can It is desirable to trade off and merge the components shown for different processes of the different embodiments implemented.
  • the BM-SC 400 includes: a service origination/ending unit 410, configured to determine whether a new service starts or whether an original service ends (S111, S121, S210, S221);
  • the creating unit 420 is configured to create a SYNC entity, which may be created according to a service or a service group (S101, Sl11, S201, S210, S211), or may be independent of a service or a service group (S301); a SYNC entity association unit 425, Used to associate the SYNC entity created by the SYNC entity creation unit 420 with a business or business group 9 000473
  • FIG. 5 is a block diagram showing the structure of an eNB for implementing the above SYNC entity creation, update and release procedures.
  • Figure 5 shows all of the components that may be required for each process, but for any single process, not all of these components are required to be completed, and those skilled in the art can fully The components shown are traded off and combined for different processes of the different embodiments implemented. As shown in FIG.
  • the eNB 500 includes: a receiving unit 510, configured to receive a SYNC entity creation indication, a SYNC entity update indication, or a SYNC entity release indication from the BM-SC (S105, S115, S125, S205) , S215, S225, S305, S 315); SYNC entity creation unit 520, used to create a SYNC entity, which can be created according to a service or a service group (S107, S117, S207, S216, S217), or can be associated with a service or a service group.
  • a receiving unit 510 configured to receive a SYNC entity creation indication, a SYNC entity update indication, or a SYNC entity release indication from the BM-SC (S105, S115, S125, S205) , S215, S225, S305, S 315); SYNC entity creation unit 520, used to create a SYNC entity, which can be created according to a service or a service group (S107, S
  • S307 SYNC entity association unit 525, configured to associate a SYNC entity created by the SYNC entity creation unit O with a service or service group (S109, S119, S209, S219); and a SYNC entity release unit 530, The SYNC entity (S127, S226 S227) is released according to the business or business group.
  • SYNC entity S127, S226 S227) is released according to the business or business group.

Description

同歩实体创建、 更新和释放方法、 基站和广播组播业务中心 技术领域
本发明涉及移动通信领域, 更具体地, 涉及 eNB (基站)和 BM - SC
(广播组播业务中心)间的 SYNC (同步)实体创建、 更新和释放过程, 以及用于实现上述 SYNC实体创建、 更新和释放过程的 eNB和 BM- SC。 背景技术
SYNC实体对等 t 位于 eNB和 BM- SC中, 用于确保这两个 SYNC实 体间的内容同步。但是,如何配置 SYNC实体仍然是一个需要讨论的问 题。 在考虑对 SYNC实体的配置时, 需要注意以下两点事实: ( 1 ) 3GPP 大体上认可了业务统计复用方案 ( s tat i s t i ca l mul t i plexing ), 在该 方案中, 对多个业务进行集束或分组, 并且可以将业务束或业务纽看 作虛拟的大业务,从而实现简化; (2 )—个小区中只有一个 MBSFN (多 媒体广播组播业务单频网) 区域, 一个 MBSFN区域中的所有小区都传 输相同的业务。
基于以上考虑, 本发明提出了一组关于 SYNC 实体配置结构的技 术方案。 发明内容
本发明提出了一种全新的 eNB和 BM- SC间的 SYNC实体创建、 更 新和释放过程, 以及用于实现上述 SYNC实体创建、 更新和释放过程的 eNB和 BM SC。 根据本发明的第一方案, 提出了一种 SYNC实体创建方法, 包括: 在 BM- SC处,创建与业务总数相同数目的多个 SYNC实体, 并将所创建 的多个 SYNC实体以——对应的方式与业务相关联;向 MBSFN区域内的 所有 eNB发送 SYNC实体创建指示; 在每个 eNB处, 根据所接收到的 SYNC实体创建指示, 创建与业务总数相同数目的多个 SYNC实体, 并 将所创建的多个 SYNC实体以——对应的方式与业务相关联。
优选地, 所述 SYNC 实体创建指示包括: 业务总数、 业务标识信 息和业务开始指示。
根据本发明的第一方案, 还提出了一种 SYNC 实体更新方法, 包 括: 在 BM- SC处, 当新业务开始时, 创建新的 SYNC实体, 并将新创建 的 SYNC实体以——对应的方式与新业务相关联;向 MBSFN区域内的所 有 eNB发送 SYNC实体更新指示;在每个 eNB处,根据所接收到的 SYNC 实体更新指示, 创建新的 SYNC实体, 并将新创建的 SYNC实体以—— 对应的方式与新业务相关联。
优选地, 所述 SYNC 实体更新指示包括: 业务标识信息和业务开 始指示。
根据本发明的第一方案, 还提出了一种 SYNC 实体释放方法, 包 括: 在 BM- SC处, 当原有业务结束时, 释放与所述原有业务相关联的 SYNC实体; 向 MBSFN区域内的所有 eNB发送 SYNC实体释放指示; 在 每个 eNB处,根据所接收到的 SYNC实体释放指示,释放与所述原有业 务相关联的 SYNC实体。
优选地, 所述 SYNC 实体释放指示包括: 业务标识信息和业务结 束指示。 根据本发明的第二方案, 提出了一种 SYNC实体创建方法, 包括: 在 BM- SC处,创建与业务组总数相同数目的多个 SYNC实体, 并将所创 建的多个 SYNC实体以——对应的方式与业务組相关联;向 MBSFN区域 内的所有 eNB发送 SYNC实体创建指示;在每个 eNB处,根据所接收到 的 SYNC实体创建指示,创建与业务组总数相同数目的多个 SYNC实体, 并将所创建的多个 SYNC实体以一"" *对应的方式与业务组相关联。
优选地, 所述 SYNC 实体创建指示包括: 业务总数、 业 分组信 息和业务开始指示。
优选地, 所述 SYNC 实体创建指示包括: 业务总数、 业务标识信 息和业务开始指示, 以及在 BM-SC处, 对各业务的数据包进行緩存和 改组。 根据本发明的第二方案, 还提出了一种 SYNC 实体更新方法, 包 括: 在 BM- SC处, 当新业务开始时, 首先确定新业务是否属于已有业 务组; 当新业务不属于任何一个已有业务組时, 创建新的 SYNC实体, 并将新创建的 SYNC实体以——对应的方式与新业务相关联; 向 MBSFN 区域内的所有 eNB发送 SYNC实体更新指示; 在每个 eNB处,根据所接 收到的 SYNC实体更新指示,首先确定新业务是否属于已有业务组; 当 新业务不属于任何一个已有业务组时,创建新的 SYNC实体, 并将新创 建的 SYNC实体以——对应的方式与新业务相关联。
优选地, 所述 SYNC 实体更新指示包括: 业务标识信息、 业务分 组信息和业务开始指示。
优选地, 所述 SYNC 实体更新指示包括: 业务标识信息和业务开 始指示, 以及在 BM- SC处, 对各业务的数据包进行緩存和改组。
优选地, 所述 SYNC实体更新方法还包括: 在 BM- SC处, 当新业 务属于已有业务组时,直接向 MBSFN区域内的所有 eNB发送 SYNC实体 更新指示; 以及在每个 eNB处, 当新业务属于已有业务组时, 直接结 束 SYNC实体更新处理。
根据本发明的第二方案, 还提出了一种 SYNC 实体释放方法, 包 括: 在 BM- SC处, 当原有业务结束时, 确定所述原有业务是否是所属 业务组中的最后一个业务; 当所述原有业务是所属业务组中的最后一 个业务时, 释放与所属业务组相关联的 SYNC实体; 向 MBSFN区域内的 所有 eNB发送 SYNC实体释放指示; 在每个 eNB处, 根据所接收到的 SYNC实体释放指示, 确定所述原有业务是否是所属业务組中的最后一 个业务; 当所述原有业务是所属业务组中的最后一个业务时, 释放与 所属业务组相关联的 SYNC实体。
优选地, 所述 SYNC 实体释放指示包括: 业务标识信息、 业务分 组信息和和业务结束指示。
优选地, 所述 SYNC 实体释放指示包括: 业务标识信息和业务结 束指示, 以及在 BM- SC处, 对各业务的数据包进行緩存和改组。
优选地, 所述 SYNC实体释放方法还包括: 在 BM- SC处, 当所述 原有业务不是所属业务组中的最后一个业务时, 直接向 MBSFN区域内 的所有 eNB发送 SYNC实体释放指示; 以及在每个 eNB处, 当所述原有 业务不是所属业务組中的最后一个业务时,直接结束 SYNC实体释放处 理。 根据本发明的第三方案, 提出了一种 SYNC实体创建方法, 包括: 在 BM- SC处,创建或静态配置单一的 SYNC实体; 向 MBSFN区域内的所 有 eNB发送 SYNC实体创建指示;在每个 eNB处,根据所接收到的 SYNC 实体创建指示, 创建单一的 SYNC实体。
优选地, 所述 SYNC 实体创建指示包括: 业务标识信息、 业务分 组信息和业务开始指示。
优选地, 所述 SYNC 实体创建指示包括: 业务标识信息和业务开 始指示, 以及在應- SC处, 对各业务的数据包进行緩存和改组。
优选地, 所述 SYNC实体创建方法还包括: 从 BM- SC向 MBSFN 区 域内的所有 eNB发送 SYNC实体更新指示。
优选地, 所述 SYNC 实体更新指示包括: 业务标识信息、 业务分 组信息和业务开始指示; 或者所述 SYNC实体更新指示包括: 业务标识 信息、 业务分组信息和业务结束指示。
优选地, 所述 SYNC 实体更新指示包括: 业务标识信息和业务开 始指示,或者所述 SYNC实体更新指示包括: 业务标识信息和业务结束 指示, 以及在腿- SC处, 对各业务的数据包进行緩存和改组。 根据本发明的第四方案, 提出了一种 BM- SC, 包括: SYNC实体创 建单元, 用于创建 SYNC实体; SYNC实体关联单元, 用于将 SYNC实体 创建单元所创建的 SYNC实体与业务或业务组相关联; 以及指示单元, 用于向 MBSFN区域内的所有 eNB传输 SYNC实体创建指示或 SYNC实体 更新指示。
优选地, 所述 BM- SC 还包括: 业务发起 /结束单元, 用于确定是 否有新业务开始或者是否原有业务结束; 以及 SYNC实体释放单元, 用 于根据业务或业务组, 释放 SYNC实体, 其中在确定有新业务开始时, 所述业务发起 /结束单元指示所述 SYNC实体创建单元创建 SYNC实体, 在确定原有业务结束时, 所述业务发起 /结束单元指示所述 SYNC实体 释放单元释放 SYNC实体,以及所述指示单元还用于向 MBSFN区域内的 所有 eNB传输 SYNC实体释放指示。 '
优选地, 所述 SYNC实体创建单元根据业务或业务组, 创建 SYNC 实体。 根据本发明的第五方案, 提出了一种 eNB, 包括: 接收单元, 用 于从 BM- SC接收 SYNC实体创建指示或 SYNC实体更新指示; SYNC实体 创建单元, 用于创建 SYNC实体; SYNC实体关联单元, 用于将 SYNC实 体创建单元所创建的 SYNC实体与业务或业务組相关联。
优选地, 所述接收单元还用于从 BM- SC接收 SYNC实体释放指示, 以及所述 eNB还包括: SYNC实体释放单元, 用于根据业务或业务组, 释放 SYNC实体。
优选地, '所述 SYNC实体创建单元根据业务或业务组, 创建 SYNC 实体。 根据本发明的上述多种可选方案成功地解决了关于 SYNC 实体的 配置问题, 又各有优缺点(可参见具体实施方式部分的详细分析)。 在 系统应用和配置中, 本领域普通技术人员可以根据实际需求, 选取适 当的技术方案。 附图说明
根据以下结合附图对本发明非限制实施例的详细描述, 本发明的 以上和其他目的、 特征和优点将变得更加清楚, 其中:
图 1A示出了其中每个业务都具有一个对应的 SYNC实体的实施例
1的示意图。
图 1B示出了根据实施例 1的 SYNC实体创建过程。
图 1C示出了根据实施例 1的 SYNC实体更新过程。
图 1 D示出了根据实施例 1的 SYNC实体释放过程。
图 2A示出了其中 SYNC实体基于业务复用组的实施例 2的示意图。 3
图 2B示出了根据实施例 2的 SYNC实体创建过程。
图 2C示出了才艮据实施例 2的 SYNC实体更新过程。
图 2D示出了根据实施例 2的 SYNC实体释放过程。
图 3A示出了其中 SYNC实体基于 MBSFN区域的实施例 3的示意图。 图 3B示出了实施例 3的具体操作流程, 包括: SYNC实体创建过 程和 SYNC实体更新过程。
图 4 示出了用于实现上述 SYNC 实体创建 、 更新和释放过程的 爾 SC的结构方框图。
图 5示出了用于实现上述 SYNC实体创建 、更新和释放过程的 eNB 的结构方框图。 具体实施方式
下面, 将根据附图描述本发明。 在以下描述中, 一些具体的实施 例只用于描述的目的, 不应该将其理解为对于本发明的任何限制, 而 只是示例。 当可能导致使本发明的理解发生模糊时, 将省略传统结构 或构造。 . 在本发明中, 针对 MBMS (多媒体广播组播业务)的前提是每个小 区中只有一个 MBSFN区域, 而且 MBSFN区域间不发生重叠。 因此, 一 个 MBSFN区域中的所有小区具有相同的业务轮廓、 无线电配置和相同 的 IP组播目的地。基于上述前提, 网络部署和相关技术方案将更为简 单。 在这种情况下, 需要考虑如何配置 SYNC实体的问题。 背后的原因 在于: 在传输业务时, 一些业务可能会被复用在一起, 例如, 具有相 同的 SDU (业务数据包) 误包率要求的业务, 而一些业务不会被复用 在一起。不同的 SYNC实体配置方案将影响 SYNC协议和系统的复杂度。 一对对等的 SYNC 实体确保了二者之间数据的内容同步。 在业务 复用的情形下, 基于字节计数和包计数, 多个业务彼此相关, 尤其是 在业务切换点发生丢包的情形下。 因此, 一个业务的同步将影响与之 复用的其他业务。 在这种情况下, SYNC实体也变得彼此相关。 根据本 发明, 提出了下述三种实施例, 但本发明的范围不应局限于这些实施 例中的具体描述, 而应涵盖本领域普通技术人员通过阅读这些具体描 迷所能构思出的所有等同技术方案。 实施例 1 : 每个业务都具有一个对应的 SYNC实体
图 1A示出了其中每个业务都具有一个对应的 SYNC实体的实施例 1的示意图。
如图 1A所示, 实施例 1是一种最为直接的解决方案, 在这种情 况下, SYNC实体是业务相关的。 在业务发起或结束时, 将创建或释放 SYNC实体。 由于包计数和字节计数是针对每个业务独立地进行的, 在 复用业务组中发生丢包的情形下, 能够清楚地确定哪个或哪些业务将 受到丟包的影响。 基于这一点来看, 在处理业务传输切换点发生丢包 的问题上, 实施例 1具有天生的鲁棒性。
大体上, 实施例 1的优缺点如下:
优点:
今 简单、 直观;
今 因为能够很好地识别出受到丢包影响的业务, 对于复用业务 中的丟包问题, 具有良好的抵御性。
缺点:
今 与本发明的其他实施例相比, SYNC 实体的创建和释放过于频 繁。 图 IB ~ ID示出了实施例 1的具体操作流程, 包括: SYNC实体创 建过程、 SYNC实体更新过程和 SYNC实体释放过程。
图 1B示出了根据实施例 1的 SYNC实体创建过程。 如图 1B所示, 在步骤 S 101 , BM-SC创建与业务总数相同数目的多个 SYNC实体。在步 骤 S103 , BM- SC将所创建的多个 SYNC实体以——对应的方式与业务相 关联, 每个 SYNC实体与一个业务相关联, 每个业务也与一个 SYNC实 体相关联。然后,在步骤 S105 , BM- SC向 MBSFN区域内的 eNB发送 SYNC 实体创建指示, 所述 SYNC实体创建指示可以包括: 业务总数、 业务标 00473
识信息和业务开始指示。在步骤 S107 , eNB根据所接收到的 SYNC实体 创建指示, 创建与业务总数相同数目的多个 SYNC实体。 在步骤 S109 , eNB将所创建的多个 SYNC实体以——对应的方式与业务相关联,每个 SYNC实体与一个业务相关联, 每个业务也与一个 SYNC实体相关联。 这样, 完成了 SYNC实体创建过程。 这一 SYNC实体创建过程一般发生 在系统初始化的过程中。 当系统已经运行, 而在运行的过程中发生业 务变化(新业务开始或原有业务结束)时, 将执行 SYNC实体更新过程 和 SYNC实体释放过程。
图 1C示出了根据实施例 1的 SYNC实体更新过程。 如图 1C所示, 在步驟 S111 , 当新业务开始时, 腿- SC创建新的 SYNC 实体。 在步骤 S113 , BM- SC将新创建的 SYNC实体以——对应的方式与新业务相关联。 然后,在步骤 S115 , BM-SC向 MBSFN区域内的 eNB发送 SYNC实体更新 指示, 所述 SYNC实体更新指示可以包括: 业务标识信息和业务开始指 示。 在步驟 S117 , eNB根据所接收到的 SYNC实体更新指示, 创建新的 SYNC实体。 在步骤 S119 , eNB将新创建的 SYNC实体以 对应的方 式与新业务相关联。这样, 完成了针对新业务开始的 SYNC实体更新过 程。
图 1D示出了根据实施例 1的 SYNC实体释放过程。 如图 1D所示, 在步骤 S121 , BM- SC检测到原有业务结束。 在步驟 S123 , BM- SC释放 与所述业务相关联的 SYNC实体。 然后, 在步骤 S125 , BM- SC向 MBSFN 区域内的 eNB发送 SYNC实体释放指示, 所述 SYNC实体释放指示可以 包括: 业务标识信息和业务结束指示。 在步骤 S127 , eNB根据所接收 到的 SYNC实体释放指示,释放与所述业务相关联的 SYNC实体。这样, 完成了针对原有业务结束的 SYNC实体释放过程。 实施例 2 : 基于业务复用组的 SYNC实体
图 2A示出了其中 SYNC实体基于业务复用组的实施例 2的示意图。 如图 2A所示, 在实施例 2 中, SYNC实体是基于业务复用组的, 即每个业务复用组具有一个对应的 SYNC实体。与实施例 1相比, SYNC 实体的创建和释放不那么频繁, 因为只有在业务复用组中的所有业务 都结束时, 才释放与该业务复用组关联的 SYNC实体。 实施例 2的优势 在于: SYNC实体最初^ <是设计用于支持业务复用的 (例如, 可以将复 用后的业务看作一个虛拟业务);而非复用情形可以看作特殊的业务复 用 (即, 每个业务被单独复用)。 在实施例 2中, 需要额外的信息来标 识相同 SYNC实体中的各个业务; 或者也可以在传输前,在 BM - SC处对 不同业务的数据包进行緩存和改组。
大体上, 实施例 2的优缺点如下:
优点:
今 将复用后的业务看作一个虛拟业务, 能够更容易地支持业务 复用;
今 较低的复杂性, 因为业务复用组中单一业务的开始或结束并 不影响业务复用组的内容同步。
' 缺点: '
今 需要额外的信息或 BM- SC 緩存, 以标识业务复用组中的不同 业务。 图 2B ~ 1D示出了实施例 2的具体操作流程, 包括: SYNC实体创 建过程、 SYNC实体更新过程和 SYNC实体释放过程。
图 2B示出了根据实施例 2的 SYNC实体创建过程。 如图 2B所示, 在步骤 S201 , BM-SC创建与业务组总数相同数目的多个 SYNC实体。在 步骤 S203 , BM-SC将所创建的多个 SYNC实体以——对应的方式与业务 组相关联,每个 SYNC实体与一个业务组相关联,每个业务组也与一个 SYNC实体相关联。 然后, 在步骤 S205 , BM-SC向 MBSFN区域内的 eNB 发送 SYNC实体创建指示, 所述 SYNC实体创建指示可以包括: 业务总 数、 业务分组信息和业务开始指示。 在步骤 S2 Q7 , eNB根据所接收到 的 SYNC实体创建指示,创建与业务組总数相同数目的多个 SYNC实体。 在步骤 S209 , eNB将所创建的多个 SYNC实体以——对应的方式与业务 組相关联,每个 SYNC实体与一个业务组相关联,每个业务组也与一个 SYNC实体相关联。 这样, 完成了 SYNC实体创建过程。 这一 SYNC实体 创建过程一般发生在系统初始化的过程中。 当系统已经运行, 而在运 行的过程中发生业务变化 (新业务开始或原有业务结束) 时, 将执行
SYNC实体更新过程和 SYNC实体释放过程。
图 2C示出了根据实施例 2的 SYNC实体更新过程。 如图 2C所示, 在步驟 S210 , 当新业务开始时, BM- SC首先确定新业务是否属于已有 业务组。 如果新业务属于已有业务组 (步骤 S210: 是), 则 BM- SC直 接执行步骤 S215。 另一方面, 如果新业务并不属于任何一个已有业务 组(步骤 S21 0: 否), 则在步驟 S211 , BM-SC创建新的 SYNC实体。 在 步骤 S213 , BM- SC将新创建的 SYNC实体以——对应的方式与新业务相 关联。 然后, 在步骤 S215 , BM-SC向 MBSFN 区域内的 eNB发送 SYNC 实体更新指示, 所述 SYNC实体更新指示可以包括: 业务标识信息、 业 务分组信息和业务开始指示。 在步驟 S216 , eNB根据所接收到的 SYNC 实体更新指示, 首先确定新业务是否属于已有业务组。 如果新业务属 于已有业务组(步骤 S216 : 是), 则 eNB无需进行任何 SYNC实体更新 操作, 在步骤 S218 , 结束 SYNC实体更新操作。 另一方面, 如果新业 务并不属于任何一个已有业务组 (步驟 S216 : 否), 则在步骤 S217 , eNB根据所接收到的 SYNC实体更新指示, 创建新的 SYNC实体。 在步 骤 S 219 , eNB将新创建的 S YNC实体以——对应的方式与新业务相关联。 这样, 完成了针对新业务开始的 SYNC实体更新过程。
图 2D示出了根据实施例 2的 SYNC实体释放过程。 如图 2D所示, 在步骤 S221 , BM- SC检测到原有业务结束。 在步驟 S222 , BM- SC确定 该原有业务是否是所属业务組中的最后一个业务。 如果该原有业务不 是所属业务組中的最后一个业务 (步骤 S222 : 否), 则 BM- SC直接执 行步驟 S225。 另一方面, 如果该原有业务是所属业务组中的最后一个 业务 (步骤 S222 : 是), 则在步驟 S223 , BM- SC释放与所属业务组相 关联的 SYNC实体。 然后, 在步骤 S225 , BM-SC向 MBSFN区域内的 eNB 发送 SYNC实体释放指示, 所述 SYNC实体释放指示可以包括: 业务标 识信息、 业务分組信息和业务结束指示。 在步骤 S226 , eNB根据所接 收到的 SYNC实体释放指示,首先确定该原有业务是否是所属业务组中 的最后一个业务。 如果该原有业务不是所属业务组中的最后一个业务 (步骤 S226 : 否), 则 eNB无需进行任何 SYNC实体释放操作, 在步驟 S228 , 结束 SYNC实体释放操作。 另一方面, 如果该原有业务是所属业 务组中的最后一个业务(步骤 是), 则在步骤 S227 , eNB根据 所接收到的 SYNC实体释放指示, 释放与所属业务组相关联的 SYNC实 体。 这样, 完成了针对原有业务结束的 SYNC实体释放过程。
在上述的 SYNC 实体创建、 更新和释放过程中, 均采用了额外的 信息 (业务分组信息) 来标识业务组中的不同业务, 但是正如前面所 述, 也可以在舰- SC处执行緩存和改组的方式, 而省略这些额外的信
实施例 3: 基于 MBSFN区域的 SYNC实体
图 3A示出了其中 SYNC实体基于 MBSFN区¾的实施例 3的示意图。 如图 3A所示, 在实施例 3中, 每个 MBSFN区域只有一个 SYNC实 体, 该 SYNC实体可以是静态配置的, 而且始终不被释放。 看上去, 实 施例 3似乎更加简单, 但事实并非如此。 不同的业务可能按照不同的 方式进行传输: 复用 /非复用; 一些业务已经结束 /一些业务仍在进行。 因为字节计数和包计数是所有业务一起进行计数的, 正在进行的业务 可能会受到巳经结束的业务的影响。 事实上, 在彼此传输无关的业务 间, 不需要共享 SYNC实体。 因此, 实施例 3可能会在 SYNC机制设计 上更为复杂。
大体上, 实施例 3的优缺点如下:
优点:
今 只有一个 SYNC实体, 而且始终不被释放。
缺点:
今 相对复杂, 因为需要在单一的 SYNC算法中考虑彼此无关的业 务;
今 需要额外的信息或 BM- SC 緩存, 以标识业务复用组中的不同 业务。 图 3B示出了实施例 3的具体操作流程, 包括: SYNC实体创建过 程和 SYNC实体更新过程。
I I 如图 3B所示, 在步骤 S 301, BM- SC创建或静态配置单一的 SYNC 实体。 然后, 在步骤 S 305, BM-SC向 MBSFN 区域内的 eNB发送 SYNC 实体创建指示, 所述 SYNC实体创建指示可以包括: 业务标识信息、 业 务分组信息和业务开始指示。 在步骤 S307 , eNB根据所接收到的 SYNC 实体创建指示, 创建单一的 SYNC实体。 这样, 完成了 SYNC实体创建 过程。这一 SYNC实体创建过程一 ^ 发生在系统初始化的过程中。 当系 统已经运行, 而在运行的过程中发生业务变化 (新业务开始或原有业 务结束) 时, 将执行 SYNC实体更新过程。
仍然参考图 3B, 如图 3B中的虚线所示, 由于实施例 3中并不涉 及 SYNC实体的释放, 无论是发生新业务开始或原有业务结束,仅执行 SYNC实体更新过程。 在 SYNC实体更新过程中 (步骤 S 315 ), 腿- SC向 MBSFN区域内的 eNB发送 SYNC实体更新指示, 所述 SYNC实体更新指 示可以包括: 业务标识信息、 业务分組信息和业务开始指示 (或业务 结束指示)。 这样, 完成了 SYNC实体更新过程。
在上述的 SYNC实体创建和更新过程中,均采用了额外的信息(业 务分组信息) 来标识业务组中的不同业务, 但是正如前面所述, 也可 以在 BM- SC处执行緩存和改组的方式, 而省略这些额外的信息。 图 4 示出了用于实现上述 SYNC 实体创建 、 更新和释放过程的 BM-SC的结构方框图。 应当注意的是, 为了筒便起见, 图 4示出了各 个过程可能需要的所有组件, 但是就任何一个单一的过程而言, 并不 需要所有这些組件来完成, 本领域普通技术人员完全可以根据需要, 针对所实现的不同实施例的不同过程, 对所示出的组件进行取舍和合 并。
如图 4所示, 根据本发明的 BM- SC 400 包括: 业务发起 /结束单 元 410 , 用于确定是否有新业务开始或者是否原有业务结束 (Sl l l、 S121、 S210、 S221 ); SYNC实体创建单元 420, 用于创建 SYNC实体, 可以根据业务或业务组进行创建 ( S101、 Sl l l、 S201、 S210、 S211 ), 也可以与业务或业务组无关(S 301 ); SYNC实体关联单元 425 , 用于将 SYNC 实体创建单元 420 所创建的 SYNC 实体与业务或业务組相关联 9 000473
( S103、 S113、 S203、 S213 ); SYNC实体释放单元 430 , 用于根据业务 或业务组, 释放 SYNC实体( S123、 S222、 S223 ); 以及指示单元 440 , 用于向 MBSFN区域内的所有 eNB传输 SYNC实体创建指示、 SYNC实体 更新指示或 SYNC实体释放指示( S105、 S115、 S125 , S205、 S215、 S225、 S 305、 S315 )。 图 5示出了用于实现上述 SYNC实体创建 、更新和释放过程的 eNB 的结构方框图。 应当注意的是, 为了简便起见, 图 5示出了各个过程 可能需要的所有组件, 但是就任何一个单一的过程而言, 并不需要所 有这些组件来完成, 本领域普通技术人员完全可以根据需要, 针对所 实现的不同实施例的不同过程, 对所示出的组件进行取舍和合并。 如图 5所示, 根据本发明的 eNB 500包括: 接收单元 510, 用于 从 BM- SC接收 SYNC实体创建指示、 SYNC实体更新指示或 SYNC实体释 放指示(S 105、 S 115、 S 125、 S205、 S215、 S225、 S305、 S 315 ); SYNC 实体创建单元 520, 用于创建 SYNC实体, 可以根据业务或业务組进行 创建(S107、 S117、 S207、 S216、 S217 ), 也可以与业务或业务组无关 ( S 307 ); SYNC实体关联单元 525, 用于将 SYNC实体创建单元 O所 创建的 SYNC实体与业务或业务组相关联(S109、 S119、 S209、 S219 ); 以及 SYNC实体释放单元 530, 用于根据业务或业务组, 释放 SYNC实 体 ( S127、 S226 S227 )。 以上实施例只是用于示例目的, 并不倾向于限制本发明。 本领域 普通技术人员应该理解的是,在不脱离本发明的范围和精神的情况下, 可以存在对该实施例的各种修改和代替, 并且这些修改和代替落在所 附权利要求所限定的范围中。

Claims

1. 一种同步实体创建方法, 包括:
在广播組播业务中心处, 创建与业务总数相同数目的多个同步实 体, 并将所创建的多个权同步实体以——对应的方式与业务相关联; 向多媒体广播組播业务单频网区域内的所有基站发送同步实体 创建指示;
在每个基站处, 根据所接收到的同步实体创建指示, 创建与业务 总数相同数目的多个同步实体, 并将所创建的多个同步实体以——对 应的方式与业务相关联。
2. 根据权利要求 1所述的同步实体创建方法, 其中
所述同步实体创建指示包括: 业务总数、 业务标识信息和业务开 始指示。
3. 一种同步实体更新方法, 包括:
^广播组播业务中心处, 当新业务开始时, 创建新的同步实体, 并将新创建的同步实体以——对应的方式与新业务相关联;
向多媒体广播组播业务单频网区域内的所有基站发送同步实体 更新指示;
在每个基站处, 根据所接收到的同步实体更新指示, 创建新的同 步实体, 并将新创建的同步实体以——对应的方式与新业务相关联。
4. 根据权利要求 3所述的同步实体更新方法, 其中
所述同步实体更新指示包括: 业务标识信息和业务开始指示。
5. 一种同步实体释放方法, 包括:
在广播组播业务中心处, 当原有业务结束时, 释放与所述原有业 务相关联的同步实体;
向多媒体广播組播业务单频网区域内的所有基站发送同步实体 释放指示;
在每个基站处, 根据所接收到的同步实体释放指示, 释放与所述 原有业务相关联的同步实体。
6. 根据杈利要求 5所述的同步实体释放方法,. 其中
所述同步实体释放指示包括: 业务标识信息和业务结束指示。
7. —种同步实体创建方法, 包括:
在广播组播业务中心处, 创建与业务組总数相同数目的多个同步 实体,并将所创建的多个同步实体以——对应的方式与业务组相关联; 向多媒体广播組播业务单频网区域内的所有基站发送同步实体 创建指示;
在每个基站处, 根据所接收到的同步实体创建指示, 创建与业务 组总数相同数目的多个同步实体, 并将所创建的多个同步实体以—— 对应的方式与业务组相关联。
8. 根据权利要求 7所述的同步实体创建方法, 其中
所述同步实体创建指示包括: 业务总数、 业务分组信息和业务开 始指示。
9. 根据权利要求 7所述的同步实体创建方法, 其中
所述同步实体创建指示包括: 业务总数、 业务标识信息和业务开 始指示, 以及
在广播組播业务中心处, 对各业务的数据包进行緩存和改组。
1 0. 一种同步实体更新方法, 包括:
在广播组播业务中心处, 当新业务开始时, 首先确定新业务是否 属于巳有业务组;
当新业务不属于任何一个已有业务组时, 创建新的同步实体, 并 将新创建的同步实体以——对应的方式与新业务相关联;
向多媒体广播組播业务单频网区域内的所有基站发送同步实体 更新指示;
在每个基站处, 根据所接收到的同步实体更新指示, 首先确定新 业务是否属于已有业务组;
当新业务不属于任何一个已有业务组时, 创建新的同步实体, 并 将新创建的同步实体以——对应的方式与新业务相关联。
11. 根据权利要求 10所述的同步实体更新方法, 其中
所述同步实体更新指示包括: 业务标识信息、 业务分组信息和业 务开始指示。
12. 根据权利要求 10所述的同步实体更新方法, 其中 所述同步实体更新指示包括: 业务标识信息和业务开始指示, 以 及
在广播组播业务中心处, 对各业务的数据包进行緩存和改组。
13. 根据权利要求 1 0 ~ 12之一所述的同步实体更新方法, 还包 括:
在广播组播业务中心处, 当新业务属于已有业务組时, 直接向多 媒体广播组播业务单频网区域内的所有基站发送同步实体更新指示; 以及
在每个基站处, 当新业务属于已有业务组时, 直接结束同步实体 更新处理。
14. 一种同步实体释放方法, 包括:
在广播组播业务中心处, 当原有业务结束时, 确定所述原有业务 是否是所属业务组中的最后一个业务;
当所述原有业务是所属业务组中的最后一个业务时, 释放与所属 业务组相关联的同步实体;
向多媒体广播组播业务单频网区域内的所有基站发送同步实体 释放指示; .
在每个基站处, 根据所接收到的同步实体释放指示, 确定所述原 有业务是否是所属业务组中的最后一个业务;
当所述原有业务是所属业务組中的最后一个业务时, 释放与所属 业务组相关联的同步实体。
15. 根据权利要求 14所述的同步实体释放方法, 其中 所述同步实体释放指示包括: 业务标识信息、 业务分组信息和和 业务结束指示。
1 6. 根据权利要求 14所述的同步实体释放方法, 其中 所述同步实体释放指示包括: 业务标识信息和业务结束指示, 以 及
在广播组播业务中心处, 对各业务的数据包进行緩存和改组。
17. 根据权利要求 14 ~ 16之一所述的同步实体释放方法, 还包 括:
在广播组播业务中心处, 当所述原有业务不是所属业务组中的最 后一个业务时, 直接向多媒体广播组播业务单频网区域内的所有基站 发送同步实体释放指示; 以及
在每个基站处, 当所述原有业务不是所属业务组中的最后一个业 务时, 直接结束同步实体释放处理。
18. 一种同步实体创建方法, 包括:
在广播组播业务中心处, 创建或静态配置单一的同步实体; 向多媒体广播组播业务单频网区域内的所有基站发送同步实体 创建指示;
在每个基站处, 根据所接收到的同步实体创建指示, 创建单一的 同步实体。
19. 根据权利要求 18所述的同步实体创建方法, 其中 所述同步实体创建指示包括: 业务标识信息、 业务分组信息和业 务开始指示。
20. 根据权利要求 18所述的同步实体创建方法, 其中 所述同步实体创建指示包括: 业务标识信息和业务开始指示, 以 及
在广播組播业务中心处, 对各业务的数据包进行緩存和改组。
21. 根据权利要求 18所述的同步实体创建方法, 还包括: 从广播組播业务中心向多媒体广播组播业务单频网区域内的所 有基站发送同步实体更新指示。
22. 根据权利要求 21所述的同步实体创建方法, 其中
所述同步实体更新指示包括: 业务标识信息、 业务分组信息和业 务开始指示; 或者
所述同步实体更新指示包括: 业务标识信息、 业务分组信息和业 务结束指示。
23. 根据权利要求 21所述的同步实体创建方法, 其中
所述同步实体更新指示包括: 业务标识信息和业务开始指示, 或 者所述同步实体更新指示包括: 业务标识信息和业务结束指示, 以及 在广播组播业务中心处, 对各业务的数据包进行緩存和改組。
24. 一种广播组播业务中心, 包括:
同步实体创建单元, 用于创建同步实体;
同步实体关联单元, 用于将同步实体创建单元所创建的同步实体 与业务或业务組相关联; 以及
指示单元, 用于向多媒体广播组播业务单频网区域内的所有基站 传输同步实体创建指示或同步实体更新指示。
25. 根椐权利要求 24所述的广播组播业务中心, 还包括: 业务发起 /结束单元, 用于确定是否有新业务开始或者是否原有 业务结束; 以及
同步实体释放单元, 用于根据业务或业务組, 释放同步实体, 其中在确定有新业务开始时, 所述业务发起 /结束单元指示所述 同步实体创建单元创建同步实体,
在确定原有业务结束时, 所述业务发起 /结束单元指示所述同步 实体释放单元释放同步实体, 以及所述指示单元还用于向多媒体广播 组播业务单频网区域内的所有基站传输同步实体释放指示。
26. 根据权利要求 24或 25所述的广播组播业务中心, 其中 所述同步实体创建单元根据业务或业务组, 创建同步实体。
27. 一种基站, 包括:
接收单元, 用于从广播组播业务中心接收同步实体创建指示或同 步实体更新指示;
同步实体创建单元, 用于创建同步实体;
同步实体关联单元, 用于将同步实体创建单元所创建的同步实体 与业务或业务组相关联。
28. 根据权利要求 27所述的基站, 其中
所述接收单元还用于从广播组播业务中心接收同步实体释放指 示, 以及
所述基站还包括: 同步实体释放单元, 用于根据业务或业务組, 释放同步实体。
29. 根据权利要求 27或 28所述的基站, 其中
所述同步实体创建单元根据业务或业务组, 创建同步实体。
PCT/CN2009/000473 2009-04-29 2009-04-29 同步实体创建、更新和释放方法、基站和广播组播业务中心 WO2010124422A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
BRPI0925082-4A BRPI0925082A2 (pt) 2009-04-29 2009-04-29 Método, estação base, e centro de serviço de difusão e multidifusão para criar, atualizar e liberar de entidades de sincronização
JP2012507565A JP5250719B2 (ja) 2009-04-29 2009-04-29 同期エンティティを作成し、更新し、かつ解放するための方法、基地局、およびブロードキャスト・マルチキャスト・サービスセンター
CN200980157385.XA CN102326433B (zh) 2009-04-29 2009-04-29 同步实体创建、更新和释放方法、基站和广播组播业务中心
EP09843834.4A EP2427003A4 (en) 2009-04-29 2009-04-29 Base station, broadcast multicast service centre and method for creating, updating and releasing synchronization entities
US13/318,105 US8867424B2 (en) 2009-04-29 2009-04-29 Method, base station, and broadcast multicast service center for creating, updating, and releasing synchronization entities
KR1020117025650A KR101351290B1 (ko) 2009-04-29 2009-04-29 동기화 엔티티들을 생성, 업데이트, 및 해제하기 위한 기지국, 브로드캐스트 멀티캐스트 서비스 센터 및 방법
RU2011141582/07A RU2491786C2 (ru) 2009-04-29 2009-04-29 Способ, базовая станция и центр широковещательного и многоадресного сервиса для создания, обновления и высвобождения объектов синхронизации
PCT/CN2009/000473 WO2010124422A1 (zh) 2009-04-29 2009-04-29 同步实体创建、更新和释放方法、基站和广播组播业务中心
US14/518,781 US9609611B2 (en) 2009-04-29 2014-10-20 Method, base station, and broadcast multicast service center for creating, updating, and releasing synchronization entities

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/000473 WO2010124422A1 (zh) 2009-04-29 2009-04-29 同步实体创建、更新和释放方法、基站和广播组播业务中心

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US13/318,105 A-371-Of-International US8867424B2 (en) 2009-04-29 2009-04-29 Method, base station, and broadcast multicast service center for creating, updating, and releasing synchronization entities
US14/518,781 Continuation US9609611B2 (en) 2009-04-29 2014-10-20 Method, base station, and broadcast multicast service center for creating, updating, and releasing synchronization entities

Publications (1)

Publication Number Publication Date
WO2010124422A1 true WO2010124422A1 (zh) 2010-11-04

Family

ID=43031645

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/000473 WO2010124422A1 (zh) 2009-04-29 2009-04-29 同步实体创建、更新和释放方法、基站和广播组播业务中心

Country Status (8)

Country Link
US (2) US8867424B2 (zh)
EP (1) EP2427003A4 (zh)
JP (1) JP5250719B2 (zh)
KR (1) KR101351290B1 (zh)
CN (1) CN102326433B (zh)
BR (1) BRPI0925082A2 (zh)
RU (1) RU2491786C2 (zh)
WO (1) WO2010124422A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109792697A (zh) * 2016-09-02 2019-05-21 索尼移动通讯有限公司 下行链路同步信号

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10306424B2 (en) * 2015-04-09 2019-05-28 Lg Electronics Inc. Method and apparatus for handling L2 entity in continuity between SC-PTM transmission and MBSFN transmission in wireless communication system
KR20220138296A (ko) * 2021-04-05 2022-10-12 삼성전자주식회사 무선 통신 시스템에서 단말의 시각 동기화를 지원하는 방법 및 장치

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247315A (zh) * 2007-02-12 2008-08-20 上海贝尔阿尔卡特股份有限公司 用于单频网传输的内容同步方法和装置
EP1978762A1 (en) * 2007-04-05 2008-10-08 Matsushita Electric Industrial Co., Ltd. Service content synchronization of multicast data for mobile nodes moving between networks with different radio access technologies

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100350935B1 (ko) * 1997-07-03 2002-08-30 가부시끼가이샤 도시바 위성 방송 시스템
US6778493B1 (en) * 2000-02-07 2004-08-17 Sharp Laboratories Of America, Inc. Real-time media content synchronization and transmission in packet network apparatus and method
KR100917042B1 (ko) * 2002-08-14 2009-09-10 엘지전자 주식회사 무선 이동통신 시스템의 방송 및 멀티캐스트 데이터의전송 방법
US20050198126A1 (en) * 2004-02-06 2005-09-08 Verbestel Willy M. System and method of providing content in a multicast system
US7664467B2 (en) 2006-06-19 2010-02-16 Alcatel-Lucent Usa Inc. Method for coordinated control of radio resources for multicasting in a distributed wireless system
US20080016248A1 (en) * 2006-07-14 2008-01-17 George Tsirtsis Method and apparatus for time synchronization of parameters
BRPI0714640A2 (pt) * 2006-08-21 2013-05-07 Interdigital Tech Corp coordenaÇço de métiplas cÉlulas para serviÇos de multicast e broadcast multimÍdia em um sistemas de comunicaÇço sem fio
KR100774365B1 (ko) 2006-12-07 2007-11-08 한국전자통신연구원 통신 시스템에서 멀티캐스트 방송 서비스 제공 방법
GB0711833D0 (en) * 2007-06-18 2007-07-25 Nokia Siemens Networks Oy A method for providing a plurality of services
EP2180620A4 (en) * 2007-08-14 2015-06-03 Ntt Docomo Inc RECEIVING DEVICE AND METHOD FOR ACQUIRING DATA

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247315A (zh) * 2007-02-12 2008-08-20 上海贝尔阿尔卡特股份有限公司 用于单频网传输的内容同步方法和装置
EP1978762A1 (en) * 2007-04-05 2008-10-08 Matsushita Electric Industrial Co., Ltd. Service content synchronization of multicast data for mobile nodes moving between networks with different radio access technologies

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Evolved Universal Terrestrial Radio Access(E-UTRA) and Evolved Universal Terrestrial Radio Access Network(E-UTRAN); Overall description; Stage", 3GPP TS 36.300 V8.0.0, 2 March 2007 (2007-03-02), XP050377575 *
"Introduction of the Multimedia Broadcast Multicast Service(MBMS) in the Radio Access Network(RAN)", 3GPP TS 25.346 V8.3.0, 2 March 2009 (2009-03-02), XP050368058 *
NTT DOCOMO: "Content synchronization by absolute time stamp in BM-SC, R3-061474", 3GPP TSG-RAN 3#53BIS, 10 October 2006 (2006-10-10), SEOUL, KOREA, XP050160362 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109792697A (zh) * 2016-09-02 2019-05-21 索尼移动通讯有限公司 下行链路同步信号

Also Published As

Publication number Publication date
BRPI0925082A2 (pt) 2015-07-21
US9609611B2 (en) 2017-03-28
US20120044854A1 (en) 2012-02-23
JP5250719B2 (ja) 2013-07-31
RU2011141582A (ru) 2013-06-10
KR20120018130A (ko) 2012-02-29
JP2012525734A (ja) 2012-10-22
US20150036583A1 (en) 2015-02-05
KR101351290B1 (ko) 2014-02-14
EP2427003A1 (en) 2012-03-07
EP2427003A4 (en) 2017-07-05
US8867424B2 (en) 2014-10-21
CN102326433B (zh) 2014-10-01
RU2491786C2 (ru) 2013-08-27
CN102326433A (zh) 2012-01-18

Similar Documents

Publication Publication Date Title
CN108377567B (zh) 一种在5g架构下建立双连接传输数据的方法、装置和系统
US6999434B1 (en) Method, system and circuitry for soft handoff in internet protocol-based code division multiple access networks
ES2351597T3 (es) Procedimiento y aparato para la resincronización de un contenido de una comunicación de difusión durante el traspaso en un sistema de comunicación.
JP5279846B2 (ja) シグナリング・メッセージを同期する方法および基地局
WO2012167743A1 (zh) 无线局域网与无线广域网互操作方法、用户设备和基站
WO2008113262A1 (fr) Procédé de programmation pour mbms, dispositif de programmation et station de base comprenant ce dispositif
WO2008092408A1 (en) Method, device and system for establishing s1 signaling connection in evolved network
KR20120070945A (ko) 무선통신 시스템에서 기지국 장비 및 데이터 처리 방법
WO2008106891A1 (fr) Procédé, système de communication et entité de réseau pour le transfert d&#39;un groupe de nœuds
WO2009132565A1 (zh) 网元间公共控制消息的同步方法
WO2010025658A1 (zh) 中继网络的路由方法、装置及系统
WO2007098690A1 (fr) Procédé et système de synchronisation de clés de service de radiodiffusion de paquets entre de multiples stations de base
WO2011076074A1 (zh) 一种第一类中继站接收系统信息的系统及方法
WO2011032494A1 (zh) 精确时间协议报文处理方法和时钟设备
TW200926852A (en) Handover method and apparatus in a wireless telecommunications network
WO2010124422A1 (zh) 同步实体创建、更新和释放方法、基站和广播组播业务中心
WO2013086858A1 (zh) 一种恢复用户业务的方法和装置
WO2011144137A1 (zh) 消息处理方法、装置及系统
WO2014067371A1 (zh) 集群业务实现方法、系统及网元
WO2011110002A1 (zh) 一种识别iur接口传输承载能力的方法及系统
WO2009043306A1 (fr) Procédé pour la négociation d&#39;une configuration et appareil associé
JP5208284B2 (ja) 固定ネットワークにおいてモバイルマルチキャストサービスを送信する方法および装置
WO2009105981A1 (zh) 组业务加密密钥更新方法及系统
CN100433722C (zh) 一种识别多条仿真业务流路径方法
WO2010102425A1 (zh) 演进多媒体广播组播业务分组传输方法、网关和基站

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980157385.X

Country of ref document: CN

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

Ref document number: 09843834

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2009843834

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 7673/CHENP/2011

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20117025650

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2012507565

Country of ref document: JP

Ref document number: 13318105

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2011141582

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

Country of ref document: BR

ENP Entry into the national phase

Ref document number: PI0925082

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20111028