[go: up one dir, main page]

WO2008098497A1 - Système de service de diffusion multimedia et procédé de début de session, procédé de fin de session - Google Patents

Système de service de diffusion multimedia et procédé de début de session, procédé de fin de session Download PDF

Info

Publication number
WO2008098497A1
WO2008098497A1 PCT/CN2008/070243 CN2008070243W WO2008098497A1 WO 2008098497 A1 WO2008098497 A1 WO 2008098497A1 CN 2008070243 W CN2008070243 W CN 2008070243W WO 2008098497 A1 WO2008098497 A1 WO 2008098497A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbms
bearer
service
traffic
session
Prior art date
Application number
PCT/CN2008/070243
Other languages
English (en)
Chinese (zh)
Inventor
Jinyi Zhou
Rui Wang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008098497A1 publication Critical patent/WO2008098497A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a Multimedia Broadcast Multicast Service (MBMS) technology.
  • MBMS Multimedia Broadcast Multicast Service
  • third generation mobile communication can provide higher data rate services than second generation mobile communication, thereby supporting multiple service forms.
  • One of the characteristics of the service is that the service can be simultaneously sent to the user terminal that subscribes to the service in the wireless network. For example, weather forecasts, news clips, sports highlights, and more.
  • the third generation of mobile communications introduced the concept of multicast/broadcast.
  • the networking structure of the multicast/broadcast service is shown in Figure 1. In this structure, for intermediate nodes
  • the upstream node always sends a piece of data to the intermediate node; after receiving the data, the intermediate node expects to receive data according to its downstream node.
  • the data is copied by the quantity, and the data is distributed to the nodes that are expected to receive the data downstream, so that each branch of the multicast/broadcast service data transmission tree has only one piece of data for transmission, occupying one transmission resource, and the root node The same is true for the data transmission of 10 and its downstream node 11.
  • the MBMS architecture proposed by the 3rd Generation Partnership Project (“3GPP”) is shown in Figure 2.
  • the Broadcast Multicast Service Center (“BM-SC”) 20 is a new mobile network function entity for supporting MBMS services. It is an entry point for content providers for authorization and on the mobile network. Initiate the MBMS bearer service and deliver the MBMS content according to the scheduled schedule.
  • the BM-SC is connected to the Traffic Plane Function (TPF) Gateway GPRS Support Node (GGSN) 21 through the Gmb interface or the Gi interface; the TPF GGSN21 uses the Gn/Gp interface and service.
  • TPF Traffic Plane Function
  • GGSN Gateway GPRS Support Node
  • the GPRS support node (Serving GPRS Support Node, referred to as "SGSN”) 22 is connected; the SGSN 22 can communicate with the universal mobile communication system via the Iu interface.
  • the UMTS Terrestrial Radio Access Network (“UTRAN”) 23 is connected; the UTRAN 23 is connected to a User Equipment (“UE”) 24 through a Uu interface, and the SGSN 22 can also communicate with the Global System for Mobile Communications via the Iu/Gb interface.
  • the evolved enhanced data radio access network (GSM EDGE Radio Access Network, referred to as "GERAN”) 25 is connected; the GERAN 25 is connected to the UE 26 through the Um interface.
  • GGSN21 and SGSN22 belong to nodes in the core network (Core Net, referred to as "CN”) in the wireless network.
  • MBMS includes multicast mode and broadcast mode.
  • the multicast service has a registration requirement for the UE, and the broadcast service does not require the UE to register.
  • the UE is usually registered in the network through the activation process of the MBMS multicast service, so that the UE can receive data of the specific multicast MBMS bearer service.
  • Activation is a signaling procedure between the UE and the network. The procedure is for each user that activates the multicast MBMS bearer service in the UE, SGSN, GGSN, BM-SC, and Base Station Controller ("BSC").
  • BSC Base Station Controller
  • RNC Radio Network Controller
  • the UE leaves the MBMS multicast service through the deactivation process of the MBMS multicast service. After the UE leaves the MBMS multicast service, the MBMS UE context of the UE is deleted.
  • the MBMS bearer context is used to store MBMS bearer information, and includes all information descriptions that define an MBMS service bearer. All the nodes carrying the MBMS data in the network need to create the MBMS bearer context. As shown in Table 1, the MBMS bearer context includes: an IP multicast address, an Access Point Name (APN, for short), a Temporary Mobile Group Identity (TMGI), a status, Required MBMS bearer capability, Quality of Service (QoS), MBMS service area, downlink node list, number of UEs, etc.
  • API Access Point Name
  • TMGI Temporary Mobile Group Identity
  • QoS Quality of Service
  • MBMS service area downlink node list
  • number of UEs etc.
  • the IP multicast address identifies the MBMS bearer described by the MBMS bearer context;
  • TMGI is the temporary mobility group identity assigned to the MBMS bearer;
  • the state is the activity state of the MBMS bearer, including: Standby state or activation state, whether the identity is required to be established for
  • the QoS is the quality of service required for the MBMS bearer;
  • the MBMS service area is the area that the MBMS service needs to send;
  • the downstream node list is the list of the downstream nodes to which the MBMS bearer is requested and the MBMS data must be delivered.
  • the multicast/broadcast mode indicates whether the MBMS bearer is in multicast or broadcast mode.
  • the "X" in the table indicates the corresponding network. This information is stored on the entity.
  • Parameter Description RAN SGSN GGSN BM-SC Multicast/Broadcast Mode MBMS Bearer Service in Broadcast or Group XXXX Broadcast Mode
  • IP multicast address IP multicast address only by the MBMS X X X X to multicast mode
  • APN (only for multicast IP X multicast address has been defined X X X X mode)
  • MBMS service area The area to be sent by the MBMS service X X X X
  • the list of downstream nodes The MBMS bearer is requested, and the number of MBMS X X data must be sent to the downstream node list.
  • the user joins the MBMS service through the MBMS activation process, so that the network knows which users want to receive a specific MBMS service.
  • the network node establishes a distribution tree from the BM-SC, via the GGSN, SGSN to the RNC through the MBMS registration process, thereby allowing transmission of MBMS session attributes and data.
  • the MBMS bearer context in the BM-SC is pre-statically configured; on the SGSN and the GGSN, when the first MBMS UE context is created or when the downstream node requests the MBMS service, the corresponding MBMS bearer context is created; in the RNC, When the first MBMS UE context is created, the corresponding MBMS bearer context is created. Alternatively, when there is no corresponding MBMS bearer context in the RNC, the MBMS session start process (Session Start) may also cause the MBMS bearer context to be created.
  • FIG. 3 shows the MBMS bearer context Relationship with the MBMS UE context.
  • the network activates the bearer resources necessary for transmitting data (for the broadcast mode, it also includes creating a corresponding MBMS bearer context), and on the other hand, notifies all relevant
  • the UE is about to start transmitting data.
  • the attributes related to the MBMS session (such as: quality of service, service area, etc.) are also provided to the relevant network nodes.
  • the BM-SC sends a session start request message indicating the upcoming transmission, and provides session attributes, including temporary mobility group identification, QoS, to all GGSNs saved in the "downstream node list" parameter in the MBMS bearer context.
  • session attributes including temporary mobility group identification, QoS, to all GGSNs saved in the "downstream node list" parameter in the MBMS bearer context.
  • MBMS service area MBMS service area, broadcast/multicast mode, etc.
  • the GGSN downstream node list parameter is also included, and the BM-SC sets the status attribute of the MBMS bearer context to "active".
  • each GGSN After receiving the session start request message, each GGSN performs the following operations: For the MBMS bearer service in the broadcast mode, since there is no corresponding MBMS bearer context in the GGSN, the GGSN needs to create an MBMS bearer context, and The session attribute and the downstream node list are saved in this context, the status attribute of the MBMS bearer context is set to "active", and a session start response message is sent to the BM-SC.
  • the corresponding MBMS bearer service context in the GGSN is created in the MBMS registration process.
  • the GGSN directly saves the session attribute in the MBMS bearer context, sets the status attribute of the MBMS bearer context to "active", and sends A session starts responding to the message to the BM-SC.
  • the GGSN sends an MBMS Session Start Request message to the SGSN stored in the corresponding Downstream Node List parameter of the MBMS Bearer Context, and provides session attributes (including Temporary Mobile Group Identity, QoS, MBMS Service Area, Broadcast/Multicast). Mode, etc.).
  • session attributes including Temporary Mobile Group Identity, QoS, MBMS Service Area, Broadcast/Multicast). Mode, etc.
  • each SGSN performs the following operations: For the MBMS bearer service in the broadcast mode, the SGSN creates a corresponding MBMS bearer context. For the MBMS bearer service in the broadcast mode and the multicast mode, the SGSN saves the session attribute in the MBMS bearer context, and sets the state attribute of the MBMS bearer context to "active".
  • the GGSN returns an MBMS Session Start Response message, which is provided in the message for the bearer plane.
  • a Tunnel Endpoint Identifier (TEID) is used to send MBMS data to the GGSN.
  • the SGSN sends an MBMS Session Start Request message to the RNC to which it is connected, and the message includes the session attribute (temporary mobile group identity, QoS, MBMS service area, broadcast/multicast mode, and route area (Route Area, referred to as "RA") list, etc.).
  • session attribute temporary mobile group identity, QoS, MBMS service area, broadcast/multicast mode, and route area (Route Area, referred to as "RA" list, etc.
  • each RNC performs the following operations: If it is the MBMS bearer service in the broadcast mode, the RNC creates a corresponding MBMS bearer context.
  • the RNC For the MBMS bearer service in broadcast mode and multicast mode, the RNC returns an MBMS session start response message to the SGSN. If the RNC is in the MBMS service domain, the RNC saves the session attribute in the MBMS service context, sets the status attribute of the MBMS service context to "active", responds to an MBMS session start response message, and the RNC includes the TEID in the MBMS session to start responding. In the message, it is used when the SGSN sends MBMS data.
  • step 470 the RNC establishes the necessary radio resources for transmitting the MBMS data to the interested UE.
  • the prior art MBMS session stop process is shown in FIG.
  • the BM-SC sends a session stop request message to all GGSNs in the "downstream node list" parameter in the corresponding MBMS bearer context, indicating that the MBMS session ends, and the bearer plane resource can be released.
  • the BM-SC sets the status attribute of the MBMS bearer context to "standby".
  • each GGSN After receiving the session stop request message, each GGSN returns a session stop response message to the BM-SC.
  • each GGSN sends an MBMS session stop request message to all SGSNs in the parameter in the "downstream node list" in the corresponding MBMS bearer context, and releases the bearer plane resources corresponding to the SGSNs, and sets the state attribute of the MBMS bearer context. For "standby.”
  • each SGSN After receiving the session stop request message, each SGSN returns a session stop response message to the corresponding GGSN.
  • each SGSN releases the TEID, releases the bearer plane resource of the MBMS data of the corresponding MBMS bearer service from the GGSN, and sends an MBMS session stop request message to all RNCs that establish a bearer plane with the SGSN.
  • each RNC after receiving the session stop request message, each RNC returns a session stop response message to the corresponding SGSN.
  • step 570 the RNC releases the corresponding wireless and Iu resources.
  • each network node can only use the bearer resources corresponding to a single quality of service and service area to transmit data.
  • the prior art 2 binds multiple traffic bearers to one MBMS bearer service, which means that the original MBMS bearer context is divided into two logical entities: MBMS Bearer Service Context, And MBMS Traffic Bearer Context.
  • the MBMS bearer service context is determined by the IP multicast address and APN, or by TMGI. Some information is stored in the MBMS bearer service context, such as: the number of UEs, the list of downstream nodes, and so on.
  • the MBMS Traffic Bearer Context is determined by TMGI.
  • the information stored in the MBMS traffic bearer context includes: QoS, Service Area, and the like.
  • the UE After the UE activates an MBMS bearer service, it will trigger the establishment of the corresponding UE context. For a certain node, when the first UE context for the bearer service is established, or a service request from a downstream node is received, a corresponding MBMS bearer context is created.
  • the traffic bearer context is created at the beginning of the session. There may be multiple different traffic bearer contexts corresponding to the same bearer service. As shown in Figure 6, these traffic bearer contexts each contain a set of mutually disjointed port numbers. In the request message of the start of the session, a port number set may be carried, and one or more traffic bearers are identified by the port in the port number set.
  • Each traffic carries its own corresponding Quality of Service (QoS) distribution tree and a General Packet Tunneling Protocol ("GTP") tunnel.
  • QoS Quality of Service
  • GTP General Packet Tunneling Protocol
  • the RNC On the radio link, the RNC must multiplex those traffic bearers belonging to the same bearer service so that the UE can receive these traffic bearers in parallel. Typically, these traffic bearers can be placed in the same frequency band. There may be a priority between multiple traffic bearers corresponding to the same bearer service. Department.
  • the session starts to trigger the paging and counting process.
  • a bearer service has multiple traffic bearers, only the first traffic bearer session will start the paging and counting process.
  • the prior art 2 solves the problem of the prior art one. By separating the bearer service context and the traffic bearer context, multiple sets of traffic corresponding to different service qualities and service areas can be used for any MBMS bearer service. Host resources to transfer data.
  • the inventors of the present invention have found that in the prior art 2, when different bearer resources can be used between different MBMS bearer services, the bearer resources cannot be shared, for example, different MBMS bearer services need to transmit the same. When the service data is transmitted, the same content is separately transmitted through the respective traffic bearers, thereby causing waste of resources.
  • the main technical problem to be solved by the embodiments of the present invention is to provide a multimedia broadcast multicast service system and a session start and stop method, so that the bearer resources of the MBMS service can be saved.
  • an embodiment of the present invention provides an MBMS system, including: at least one bearer device, configured to provide an MBMS traffic bearer;
  • At least one service device is configured to provide an MBMS bearer service, and each MBMS bearer service is delivered by using at least one MBMS traffic bearer;
  • the service device delivers the data shared by the at least two MBMS bearer services through the shared MBMS traffic bearer provided by the bearer device.
  • An embodiment of the present invention further provides an MBMS session starting method, including:
  • the MBMS bearer service When the MBMS bearer service is started, if the MBMS traffic bearer involved in the session is established, the corresponding relationship between the MBMS bearer service and the established traffic bearer is updated. Otherwise, the MBMS traffic bearer is newly created, and the MBMS bearer service is updated. Correspondence of newly created traffic bearers.
  • An embodiment of the present invention further provides an MBMS session stopping method, including:
  • the MBMS bearer service When the session of the MBMS bearer service is stopped, if the session of all other MBMS bearer services corresponding to each MBMS traffic bearer in the session is stopped, the MBMS traffic bearer is released, otherwise, the MBMS bearer service and each MBMS traffic bearer are updated. Correspondence.
  • the embodiment of the present invention separates the MBMS bearer service from the MBMS traffic bearer, and one MBMS bearer service can be delivered by using multiple traffic bearers, and multiple MBMS bearer services are shared. The information can be delivered through the same traffic bearer. By sharing the traffic bearer to multiple MBMS bearer services, the bearer resources of the MBMS service are saved.
  • the session of the MBMS bearer service starts, it is first determined whether the MBMS traffic bearer involved in the session has been established. If yes, only the correspondence between the MBMS bearer service and the established traffic bearer is updated. If not, the MBMS traffic bearer is created. And updating the correspondence between the MBMS bearer service and the newly created traffic bearer. Therefore, while sharing bearer resources, it is avoided to repeatedly establish a traffic bearer.
  • the MBMS bearer service When the session of the MBMS bearer service is stopped, if all the other MBMS bearer service sessions corresponding to the MBMS traffic bearers in the session are stopped, the MBMS traffic bearer is released, otherwise, the MBMS bearer service and each MBMS traffic bearer are updated. Correspondence relationship. Therefore, the other MBMS bearer services cannot be normally transmitted after the session of the MBMS bearer service is stopped, and the MBMS bearer services can be performed normally while the bearer services share resources.
  • FIG. 1 is a schematic diagram of a networking structure of a multicast/broadcast service in the prior art
  • FIG. 2 is a schematic structural diagram of an MBMS network proposed by the 3GPP in the prior art
  • FIG. 3 is a schematic diagram of a relationship between an MBMS bearer context and an MBMS UE context in the prior art
  • FIG. 4 is a schematic diagram of a MBMS session start process in the prior art
  • FIG. 5 is a schematic diagram of a MBMS session stop process in the prior art
  • FIG. 6 is a schematic diagram of a relationship between an MBMS bearer service context and an MBMS traffic bearer context in the prior art
  • FIG. 7 is a schematic diagram of a relationship between a traffic bearer and a bearer service in an MBMS system according to a first embodiment of the present invention
  • FIG. 8 is a schematic diagram of a relationship between a traffic bearer context and a bearer service context in an MBMS system according to a first embodiment of the present invention
  • FIG. 9 is a flowchart of an MBMS session start method according to a second embodiment of the present invention
  • FIG. 10 is a first schematic diagram of an MBMS session start method according to a third embodiment of the present invention
  • FIG. 11 is an MBMS according to a third embodiment of the present invention.
  • FIG. 12 is a first schematic diagram of an MBMS session stop method according to a fourth embodiment of the present invention
  • FIG. 13 is a first schematic diagram of an MBMS session stop method according to a sixth embodiment of the present invention
  • FIG. 14 is a second schematic diagram of an MBMS session stop method according to a sixth embodiment of the present invention.
  • the first embodiment of the present invention relates to an MBMS system, including at least one bearer device, configured to provide an MBMS traffic bearer, and at least one service device, configured to provide an MBMS bearer service, where each MBMS bearer service is carried by at least one MBMS traffic bearer. hair.
  • the service device delivers the data shared by the at least two MBMS bearer services through the shared MBMS traffic provided by the bearer device. By sharing traffic bearers to multiple MBMS bearer services, the bearer resources of the MBMS service are saved.
  • a bearer service can be associated with multiple traffic bearers, forming a "one-to-many" binding relationship.
  • each traffic bearer belongs to only one designated bearer service. It can only be used by the bearer service, and the utilization of the bearer resources is low.
  • one traffic bearer can be used by multiple bearer services, and one bearer service can use multiple traffic bearers, and the bearer service and the traffic bearer are in a many-to-many relationship, as shown in the figure. 7 (b) is shown.
  • the traffic bearer when the traffic bearer and the bearer service are in a one-to-many relationship, since the same traffic bearer does not belong to multiple bearer services at the same time, the traffic bearer needs to be determined according to the valid identifier in the bearer service scope. Yes, there is no need to globally identify the traffic bearers.
  • the traffic bearer can belong to multiple bearer services at the same time, that is, different bearer services can use the same traffic bearer. Therefore, the traffic bearer needs to be globally independent in the preset range.
  • each MBMS traffic bearer corresponds to one traffic bearer identifier, and the traffic bearer identifier is unique within a preset range.
  • the preset range is at least one scope of the GGSN; for the System Architecture Evolution (“SAE”) network architecture, the preset range is at least one gateway jurisdiction. range. Through the traffic bearer identifier, all network nodes within the preset range can directly determine the traffic bearer and the traffic bearer context.
  • SAE System Architecture Evolution
  • the traffic bearer identifier may be configured by one of the following methods or any combination thereof: using a part of a flow label (Flow Id ) in an IPv6 packet structure, an entire flow label, or a stream label set as a traffic bearer. Part of the identity or traffic bearer identity; use the access point name (APN) as part of the traffic bearer identity or traffic 7-mark; use the BM-SC's identity as part of the traffic 7-load identity or traffic-loaded identity.
  • API access point name
  • the bearer device provides a context of MBMS traffic bearer, and each MBMS traffic bearer context includes part or all identifiers of each MBMS bearer service delivered by the traffic bearer;
  • a context of the MBMS bearer service is provided, and each MBMS bearer service context includes part or all of the traffic bearer identifiers of the MBMS traffic bearers that deliver the bearer services.
  • the bearer service identifier and the traffic bearer identifier included in the traffic bearer or bearer service context are not necessarily complete identifiers, and may be only a part of the identifier or an alternative identifier, as long as the bearer service or traffic bearer can be uniquely determined on the network node. can.
  • the bearer device and the service device in this embodiment are one or any combination of the following: BM-SC, GGSN, SGSN, RNC in the MBMS network architecture of 3GPP; Gateway, mobility management in the SAE network architecture Entity (Mobility Management Entity, referred to as "MME”), evolved base station (eNodeB).
  • MME Mobility Management Entity
  • eNodeB evolved base station
  • a bearer device such as a GGSN
  • receives an IP packet whose destination address is multicast it can determine the IP packet according to the traffic bearer identifier (such as the flow label) in the packet.
  • the associated "traffic bearer context" and the traffic bearer to be used can be used.
  • the service device can determine the associated service context according to the "bearer service identifier" part (such as the IP multicast destination address) in the IP packet, so as to determine which 7-carrier service the IP address belongs to.
  • the necessary information (such as the flow node list, service quality, service area, etc.) can be obtained from the "bearing service context," and "traffic bearer context” respectively, so as to perform corresponding processing.
  • the IP ⁇ text is sent downstream.
  • a second embodiment of the present invention relates to an MBMS session start method.
  • the MBMS session start procedure is initiated.
  • the network activates the bearer resources necessary for transmitting data, and on the other hand, notifies all relevant UEs that data transmission is about to start.
  • MBMS session related attributes including parameters such as quality of service, service area, etc.
  • activating the necessary bearer resources includes establishing the necessary context to save relevant information.
  • For the multicast mode one or more MBMS flows corresponding to the MBMS bearer service context are established.
  • For the broadcast mode one or more MBMS traffic bearer contexts are established. When there is no corresponding MBMS bearer service context, the bearer service context is established and corresponds to the MBMS traffic bearer.
  • one MBMS bearer service (session) may correspond to multiple MBMS traffic bearers, and the session starts for traffic bearers, a session start process may be for one or more traffic bearers, and corresponding one or more traffic bearer contexts may be established. And its carrying resources.
  • a session start process may be for one or more traffic bearers, and corresponding one or more traffic bearer contexts may be established. And its carrying resources. The above applies to both broadcast and multicast modes.
  • the MBMS traffic bearer context may correspond to multiple MBMS bearer service contexts.
  • the relationship between the MBMS bearer service (session) and the MBMS traffic bearer is existing in the BM-SC (such as by pre-configuration), and includes both the MBMS bearer service and several MBMS traffic bearers.
  • the correspondence between the MBMS traffic bearers and several MBMS bearer services is also included.
  • BM-SC and GGSN, GGSN and SGSN, SGSN and RNC are the relationship between the upstream network node and the downstream network node.
  • the upstream network node sends a session start request message to all the downstream network nodes related to the MBMS bearer service, and the session start request message may correspond to one or more MBMS traffic belonging to the MBMS bearer service. Hosted. Which downstream network nodes send the session start request message to the upstream network node, depending on the relevant information in the MBMS bearer service (eg, the downstream node list).
  • a session start request message needs to be sent to the downstream network node.
  • the MBMS bearer service context exists on the downstream network node that receives the session start request message, so only the corresponding MBMS traffic bearer context needs to be established.
  • the broadcast mode when there is no corresponding MBMS bearer service context, You need to create an MBMS bearer service context and a corresponding MBMS traffic bearer context.
  • the MBMS traffic bearer involved in the session of the MBMS bearer service may have established a corresponding MBMS traffic bearer context on some downstream network nodes, and the upstream network node Related bearer resources may have been activated between them, then The new MBMS bearer service context is no longer created and the new bearer resource is no longer activated. Therefore, while sharing bearer resources, avoid repeatedly establishing traffic bearers.
  • the downstream network node acknowledges and activates the associated bearer resource by returning a session start response message.
  • the upstream network node still needs to initiate a session start procedure to all downstream network nodes indicated by the bearer service context.
  • the session start process at this time is to notify the downstream network node that the MBMS bearer service session has started, and the information is transmitted, and the association relationship between the bearer service and the traffic bearer is established.
  • the downstream network node it is also possible for the downstream network node to establish a corresponding MBMS bearer service context. At the same time, it can trigger a process to start a session further to a more downstream network node.
  • the BM-SC sends a session start request message to all the GGSNs stored in the parameter according to the MBMS bearer service context of the MBMS service, indicating that the GGSN is the MBMS.
  • the service is about to start data transmission and provides the session attribute of the MBMS.
  • the session attributes of the MBMS include "MBMS bearer service related session attributes" and corresponding one or more sets of "MBMS traffic bearer related session attributes".
  • MBMS bearer The service-related session attribute may include a bearer service identifier, a broadcast/multicast mode, and the like, and if it is a broadcast mode, it also carries a GGSN downstream node list parameter; "MBMS traffic bearer-related session attribute, which may include a traffic bearer identifier. , service quality, service area, etc.
  • the status attribute of the MBMS bearer service context in the BM-SC is "standby", it is set to "activate” in this step, and it is identified that the MBMS bearer service is using at least one traffic bearer.
  • an MBMS bearer service has only one MBMS traffic bearer. Therefore, when the service uses all traffic bearers, the MBMS bearer service corresponds to multiple MBMS traffic bearers, and only one of the traffic flows is used. The bearer is activated.
  • step 920 after the GGSN receives the session start request message, it first searches the GGSN according to the “traffic bearer identifier” included in the request message, so as to avoid the repeated establishment of the traffic bearer while sharing the bearer resource.
  • the traffic bearer indicated by each "traffic bearer identifier” if the MBMS traffic bearer context corresponding to the traffic bearer has not been established on the GGSN, the corresponding MBMS traffic 7-load context is established for the traffic, and the traffic is 7 Related conversation The attribute is saved in the corresponding MBMS traffic bearer context; if the MBMS traffic bearer has established the corresponding MBMS traffic bearer context on the GGSN, the context is not re-created for the MBMS traffic, if the MBMS traffic carried in the session start request message
  • the related session attribute of the bearer is different from the information stored in the MBMS traffic bearer context corresponding to the traffic bearer on the GGSN, and the corresponding MBMS traffic bearer context is performed according
  • This change may be due to the update of the attribute information. For example, when the bearer service change carried by the traffic is used, the service area may be changed, and the service area parameter in the corresponding traffic bearer context may be changed.
  • the MBMS bears the service context, and in this step, the GGSN creates an MBMS bearer service context, and associates the bearer service-related session attribute with the bearer service and the traffic bearer (that is, the traffic bearer included in the session start request message).
  • the identifier "or part of the traffic bearer identifier" and the list of downstream nodes are stored in this context.
  • the identifier of the MBMS bearer service needs to be saved in the newly created MBMS traffic bearer context.
  • the association between the MBMS bearer service and the MBMS traffic bearer is updated, including: adding the identifier of the MBMS bearer service in the created MBMS traffic bearer context; And, adding an identifier (or a part of the identifier) of the created MBMS traffic bearers to the MBMS bearer service context. After that, if the status attribute of the MBMS-loaded business context is "standby,” then change to "active".
  • the corresponding MBMS bearer service context in the GGSN is created in the MBMS registration process.
  • the GGSN directly updates the association between the MBMS bearer service and the MBMS traffic bearer in the MBMS bearer service context, including An identifier of the MBMS bearer service added to the newly created or created MBMS traffic bearer context corresponding to the MBMS bearer service; and an identifier (or identifier) of the newly created or created MBMS traffic corresponding to the MBMS bearer service Part of it is added to the MBMS 7-loaded service context; in addition, if the status attribute of the MBMS-bearing service context is "standby", it is changed to "active".
  • the GGSN sends a session start response message to the BM-SC.
  • the GGSN sends an MBMS Session Start Request message to the SGSN stored in the corresponding Downstream Node List parameter of the MBMS Bearer Service Context, the information contained in the message is similar to that sent by the BM-SC.
  • step 940 after the SGSN receives the MBMS session start request message, the SGSN performs the same operations as the GGSN in step 920, and details are not described herein. After that, the SGSN returns an MBMS Session Start Response message to the GGSN, which is included in the response message.
  • the TEID of the plane is used by the GGSN to send MBMS data.
  • step 950 the SGSN sends an MBMS Session Start Request message to the RNC to which it is connected, and the information contained in the message is similar to that sent by the GGSN.
  • step 960 the operation after the RNC receives the MBMS Session Start Request message is similar to the operation of the GGSN in step 920 and the SGSN in step 940. Afterwards, the RNC returns an MBMS Session Start Response message to the SGSN, where the response message includes a TEID for the bearer plane, which is used when the SGSN sends the MBMS data.
  • step 970 the RNC establishes the necessary radio resources for the UE interested in the MBMS for transmitting MBMS data.
  • the third embodiment of the present invention also relates to an MBMS session start method, which is substantially the same as the second embodiment, except that the second embodiment describes a method for starting an MBMS session under the MBMS network architecture currently defined by 3GPP;
  • the present embodiment mainly describes an MBMS session start method under the SAE network architecture.
  • the MBMS bears the same service.
  • the relationship between the MBMS traffic bearers is existing in the BM-SC, and is usually pre-configured in the BM-SC, including the correspondence between the MBMS bearer service and each MBMS traffic bearer, and the MBMS traffic bearer and each MBMS.
  • the correspondence between bearer services is not limited to the MBMS bearer service, and the MBMS traffic bearer and each MBMS.
  • each network node is collectively described using the upstream network node and the downstream network node.
  • the network nodes referred to by the upstream network node and the downstream network node are described below.
  • the BM-SC is an upstream network node
  • the Gateway and/or the MME are downstream network nodes
  • the MME and the eNodeB evolutionary base
  • the MME is the upstream network node and the eNodeB is the downstream network node.
  • the BM-SC is the upstream network node
  • the Gateway is the downstream network node
  • the Gateway is the upstream network node
  • the MME is the downstream network node
  • MME and eNodeB Between the MME is the upstream network node and the eNodeB is the downstream network node.
  • the upstream network node initiates a session start procedure to its corresponding downstream network node, indicating that the MBMS service is about to begin data transmission, and provides session attributes to the downstream network node.
  • the "session attribute" includes "MBMS bearer service-related session attributes” (including bearer service identifiers, broadcast/multicast mode, etc.) and corresponding one or more sets of "MBMS traffic bearer-related session attributes” (including traffic bearer identifiers). , service quality, service area, etc.).
  • the downstream network node first searches on the local node according to the "traffic bearer identifier" provided by the upstream network node. For the traffic bearer indicated by each "traffic bearer identifier", if the traffic of the traffic is not established on the local node, the corresponding MBMS traffic is not established. 7 If the context is loaded, the corresponding MBMS traffic bearer context is established for the traffic, and the session attributes related to the traffic bearer are saved in the corresponding MBMS traffic carrying context; if the MBMS traffic is carried on the node, a corresponding correspondence has been established.
  • the MBMS traffic bearer context no longer re-creates the context for it, so as to avoid the repeated establishment of the traffic bearer while sharing the bearer resources; if the relevant session attribute of the MBMS traffic bearer provided by the upstream network node and the traffic bearer on the local node If the information stored in the corresponding MBMS traffic bearer context is different, the corresponding MBMS traffic bearer context is updated according to the relevant session attribute of the MBMS traffic bearer provided by the upstream network node to ensure that the new MBMS bearer service can use the existing one. Traffic carrying, Realize resource sharing. This change may be due to the update of the attribute information. For example, when the bearer service change carried by the traffic is used, the service area may be changed, and the service area parameter in the corresponding traffic bearer context may be changed.
  • the downstream network node creates the MBMS bearer service context, and associates the service-related session attribute and the bearer service with the traffic bearer (That is, the "traffic bearer ID" or "part of the traffic bearer ID" provided by the upstream network node and the list of downstream nodes are stored in this context.
  • the MBMS bearer service needs to be saved in the newly created MBMS traffic bearer context.
  • the association between the new MBMS bearer service and the MBMS traffic bearer includes: adding the identifier of the MBMS bearer service in the created MBMS traffic bearer context; and marking the created MBMS traffic 7 (or Part of the identity) is added to the MBMS 7-load business context. After that, if the status attribute of the MBMS bearer service context is "standby", it is changed to "active".
  • the corresponding MBMS bearer service context in the downstream network node already exists, and the downstream network node directly updates the association relationship between the MBMS bearer service and the MBMS traffic bearer in the MBMS bearer service context, including Adding the identifier of the MBMS bearer service to the newly created or created MBMS traffic bearer context corresponding to the MBMS bearer service; and identifying the newly created or created MBMS traffic bearer context corresponding to the MBMS bearer service (or part of the identifier) ) is added to the MBMS bearer service context; in addition, if the status attribute of the MBMS bearer service context is "standby", it is changed to "active".
  • each of the downstream network nodes (except the eNodeB) completes the above operation, it further initiates an MBMS session start procedure to its downstream network node, repeats the above operations, and implements all correlations from the BM-SC to the eNodeB.
  • the activation of resources is carried between the network nodes, and the relevant session attributes are provided to the network nodes to ensure that the MBMS service data can be transmitted normally.
  • a fourth embodiment of the present invention relates to an MBMS session stop method.
  • the end of the session is indicated by the session stop process, including releasing the related bearer resources.
  • a session of an MBMS bearer service may correspond to multiple MBMS traffic bearers, and the session stop is for a traffic bearer
  • a session stop process may be for one or more traffic bearers, and corresponding one may cause release of one or more traffic bearer contexts. And its carrying resources.
  • one MBMS traffic bearer may be used by multiple MBMS bearer services, that is, one MBMS traffic bearer context may correspond to multiple MBMS bearer service contexts. As a result, any MBMS traffic bearer context and its resources are only released when it is not used by any MBMS bearer service.
  • whether to release the MBMS traffic bearer is controlled by each network node.
  • the BM-SC does not consider such a one-to-many relationship between the traffic bearer and the bearer service, and directly initiates the session stop procedure at the end of the MBMS session.
  • each network node including GGSN, SGSN, RNC
  • the identifier or part of the identity of the bearer MBMS bearer service When the session stop process is used to learn that an MBMS bearer service is stopped, the bearer service identifier is marked or deleted in all traffic bearer contexts corresponding to the session.
  • all bearer service identifiers in a traffic bearer context are marked or deleted After that, it indicates that the bearer service carried by the traffic has not been used. At this time, the related resources can be released, and the traffic bearer context is deleted.
  • This approach is more flexible to implement and reduces the pressure on upstream network nodes (mainly BM-SC).
  • the BM-SC sends a session stop request message to all GGSNs in the MBMS bearer service context "downstream node list" parameter, indicating that the MBMS session ends, and its bearer resources can be released.
  • the session stop request message may be for one or more MBMS traffic bearers involved in the session, that is, the message carries the MBMS bearer service identifier and the corresponding one or more MBMS traffic carrying identifiers.
  • the GGSN searches for the MBMS traffic bearer identifier according to the MBMS traffic bearer identifier in the message, and determines the corresponding MBMS traffic bearer context, and labels or deletes the identifier of the MBMS bearer service in the MBMS traffic bearer context, indicating that the MBMS bearer service is not Then use this MBMS traffic bearer. If all the bearer service identifiers in the traffic bearer context are marked or deleted after the labeling or deletion process, it indicates that no MBMS bearer service uses the MBMS traffic bearer, and the related bearer resources are released, and the The context of the MBMS traffic bearer. In this step, the GGSN also returns a session stop response message to the BM-SC.
  • the GGSN sends a session stop request message to all SGSNs in the MBMS bearer service context "downstream node list" parameter, indicating that the MBMS session is over, and its bearer resources can be released.
  • step 1240 the operation after the SGSN receives the session stop request message is similar to that of the GGSN, and details are not described herein.
  • the SGSN also needs to return a session stop response message to the GGSN.
  • the SGSN sends an MBMS Session Stop Request message to all RNCs that establish a bearer plane with the SGSN, indicating that the MBMS session ends and its bearer resources can be released.
  • step 1260 the operation after the RNC receives the session stop request message is similar to the operation of the GGSN and the SGSN, and details are not described herein again.
  • the RNC also needs to return a session stop response message to the SGSN.
  • the RNC releases the corresponding wireless and Iu resources.
  • the fifth embodiment of the present invention also relates to an MBMS session stop method. Unlike the fourth embodiment, in the present embodiment, the deletion of the MBMS bearer service is completely controlled by the BM-SC. Because of the many-to-many relationship between the MBMS bearer service and the MBMS traffic bearer, it is originally embodied by the BM-SC, and is also released by the BM-SC (through the session start process). Thus, for a given MBMS traffic bearer, the BM-SC can select the appropriate time to terminate it through the session stop procedure without relying on the corresponding MBMS bearer service.
  • the BM-SC judges each MBMS traffic bearer involved in the session. If the other MBMS bearer service is still using the MBMS traffic bearer, the BM-SC does not initiate a session stop process for the traffic bearer, or only those that are no longer involved in the traffic bearer (ie, other devices that do not involve using the traffic bearer)
  • the downstream network node that carries the service initiates a session stop process, notifying the downstream network nodes to delete the traffic bearer and the corresponding traffic bearer context; if the BM-SC determines that the MBMS traffic bearer is no longer used, then all relevant downstream
  • the network node initiates a session stop process, and notifies the downstream network nodes to delete the traffic bearer and the corresponding traffic bearer context.
  • This method does not require each network node to save the corresponding MBMS bearer service identifier in its MBMS traffic bearer context, which simplifies the operation of the downstream network node.
  • the corresponding downstream network node such as the GGSN
  • receives the session stop request it can directly release and delete the corresponding traffic bearer and traffic bearer context according to the traffic bearer identifier in the request, and further trigger the relationship between the downstream network nodes.
  • the session stop process between the GGSN and the SGSN and between the SGSN and the RNC deletes the corresponding traffic bearer from the RNC to the BM-SC.
  • the sixth embodiment of the present invention also relates to a method for stopping an MBMS service, which is similar to the fourth embodiment, except that the fourth embodiment describes a method for stopping an MBMS session under the MBMS network architecture currently defined by 3GPP;
  • the present embodiment mainly describes an MBMS session end method under the S AE network architecture.
  • each network node is collectively described using the upstream network node and the downstream network node.
  • the following describes the network nodes referred to by the upstream network node and the downstream network node.
  • the BM-SC is an upstream network node, and the Gateway and/or the MME are downstream network nodes; between the MME and the eNodeB, the MME is an upstream network node.
  • the eNodeB is a downstream network node.
  • the BM-SC is an upstream network node
  • the Gateway is a downstream network node
  • the Gateway is an upstream network node
  • the MME is a downstream network node
  • the MME and the eNodeB Between the MME is the upstream network node and the eNodeB is the downstream network node.
  • the session stop process sends a session stop request message to indicate that the MBMS session ends, and the bearer resource can be released.
  • the session stop request message may be related to one or more MBMS traffic bearers involved in the session, that is, the message carries the MBMS bearer service identifier and the corresponding one or more MBMS traffic carrying identifiers. .
  • the downstream network node When receiving the request message, the downstream network node performs a search according to the MBMS traffic bearer identifier in the message, determines a corresponding MBMS traffic bearer context, and then labels or deletes the MBMS bearer service identifier in the determined MBMS traffic bearer context. Indicates that the MBMS bearer service no longer uses this MBMS traffic bearer. When all bearer service identifiers in a traffic bearer context are marked or deleted, indicating that the bearer service carried by the traffic bearer has not been used, the related bearer resources are released, and the corresponding MBMS traffic bearer context can be deleted.
  • the downstream network node needs to send a session stop request message to the re-downstream network node (for example, the gateway needs to send to the MME, and the MME needs to send to the eNodeB), and triggers the corresponding downstream network node (such as the MME, eNodeB) to perform the foregoing operation.
  • the gateway needs to send to the MME, and the MME needs to send to the eNodeB
  • the corresponding downstream network node such as the MME, eNodeB
  • the seventh embodiment of the present invention also relates to a method for stopping an MBMS service, which is similar to the fifth embodiment, and the difference is that the fifth embodiment describes a method for stopping an MBMS session under the MBMS network architecture currently defined by 3GPP;
  • the present embodiment mainly describes an MBMS session end method under the S AE network architecture.
  • the deletion of the MBMS bearer service is also controlled by the BM-SC. Because of the many-to-many relationship between the MBMS bearer service and the MBMS traffic bearer, it is originally embodied by the BM-SC, and is also released by the BM-SC (through the session start process). Thus, for a given MBMS traffic bearer, the BM-SC can choose the appropriate time to stop the flow through the session. To terminate it, without relying on the corresponding MBMS bearer service. When the session of the MBMS bearer service needs to be stopped, the BM-SC judges each MBMS traffic bearer involved in the session.
  • the BM-SC does not initiate a session stop process for the traffic bearer, or only those that are no longer involved in the traffic bearer (ie, other devices that do not involve using the traffic bearer)
  • the downstream network node (Gateway and/or MME) of the bearer service initiates a session stop procedure, notifying the downstream network nodes to delete the traffic bearer and the corresponding traffic bearer context; if the BM-SC determines that the MBMS traffic bearer is no longer used Then, a session stop procedure is initiated to all relevant downstream network nodes (Gateway and/or MME), and these downstream network nodes are notified to delete the traffic bearer and the corresponding traffic bearer context.
  • This method does not require each network node to save the corresponding MBMS bearer service identifier in its MBMS traffic bearer context, which simplifies the operation of the downstream network node.
  • the corresponding downstream network node (such as the Gateway) can directly release the corresponding traffic bearer and delete the corresponding traffic bearer context according to the traffic bearer identifier in the request, and further trigger the relationship between the downstream network nodes (Gateway)
  • the flow between the MME and the eNodeB stops the corresponding traffic bearer from the eNodeB to the BM-SC.
  • the attribute of the traffic bearer may change (such as the service area changes).
  • the process may be modified by using a session update process or the like.
  • the attributes of the MBMS traffic bearer if the attributes of an MBMS traffic bearer need to be changed for other reasons, you can also modify the attributes of the MBMS traffic bearer by using a process such as session update.
  • the MBMS bearer service is separated from the MBMS traffic bearer, and one MBMS bearer service may be delivered by using multiple traffic bearers, and the common information of multiple MBMS bearer services may be the same.
  • the traffic is delivered.
  • the bearer resources of the MBMS service are saved.
  • Each MBMS traffic bearer corresponds to a traffic bearer identifier, and the traffic bearer identifier is unique within a preset range, so that the network node within the preset range can uniquely determine the traffic bearer to be used by the identifier.
  • the preset range contains at least one GGSN or gateway.
  • the MBMS traffic bearer context includes part or all of the identifiers of the MBMS bearer services delivered by the traffic bearer; Part or all of the traffic bearer identifier carried by the MBMS traffic. Therefore, in the process of implementing the MBMS bearer service, the bearer service can be delivered according to the corresponding relationship, and the establishment and release of the traffic bearer can be managed according to the corresponding relationship.
  • the session of the MBMS bearer service starts, it is first determined whether the MBMS traffic bearer involved in the session has been established. If yes, only the correspondence between the MBMS bearer service and the established traffic bearer is updated. If not, the MBMS traffic bearer is created. And updating the correspondence between the MBMS bearer service and the newly established traffic bearer. Therefore, while sharing bearer resources, it is avoided to repeatedly establish traffic bearers.
  • the MBMS traffic bearer involved in the session has been established, it is also required to determine whether the information in the context of the MBMS traffic bearer that has been established is consistent with the information carried by the current upstream network node, and if it is different, according to the upstream network.
  • the information sent by the node updates the MBMS traffic bearer context, so as to ensure that the MBMS traffic bearer can be shared by the corresponding bearer service.
  • the session of the MBMS bearer service is stopped, if the session of all other MBMS bearer services corresponding to each MBMS traffic bearer in the session is stopped, the MBMS traffic bearer is released, otherwise, the MBMS bearer service and each MBMS traffic bearer are updated. Correspondence. Therefore, the other MBMS bearer services cannot be normally transmitted after the session of the MBMS bearer service is stopped, and the MBMS bearer services can be performed normally while the bearer services share resources.
  • the upstream network node determines whether the traffic bearer involved in the session can be released, and notifies the downstream network node when the network node can be released, and the downstream network node only needs to release the resource according to the notification of the upstream network node. Or, the upstream network node only informs the downstream network node that the MBMS bearer service session is stopped, and the downstream network node determines whether the traffic bearer involved in the session can be released, and if not, releases the corresponding traffic bearer.
  • the former method is uniformly controlled by the upstream network node, and the downstream network node does not need to separately store the correspondence between each MBMS traffic bearer and the MBMS bearer service, which simplifies the operation of the downstream network node; the latter method is more flexible and reduces The pressure of the upstream network node.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un système de service de diffusion multimédia et un procédé de début de session, un procédé de fin de session, selon lequel un service de support MBMS et un support de trafic MBMS sont séparés, un parmi les services de support MBMS peut utiliser une pluralité de support de trafic pour transmettre, l'information commune de la pluralité de services porteurs MBMS peut être transmise grâce à l'utilisation du porteur de trafic partagé. Le contexte de support de trafic MBMS comprend les identifiants associés des divers services support MBMS qui sont transmis par le porteur de trafic. Lorsque la session de service support MBMS débute, si un ou des porteurs de trafic auxquels la session est associée existe, le porteur de trafic existant peut être utilisé directement. Lorsque la session du service de support MBMS s'arrête, le support de trafic ne peut être libéré jusqu'à ce que tous les services support MBMS auxquels la session est associée se sont arrêtés.
PCT/CN2008/070243 2007-02-13 2008-02-02 Système de service de diffusion multimedia et procédé de début de session, procédé de fin de session WO2008098497A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710084649.6 2007-02-13
CN2007100846496A CN101247553B (zh) 2007-02-13 2007-02-13 多媒体广播组播业务系统及会话开始和停止方法

Publications (1)

Publication Number Publication Date
WO2008098497A1 true WO2008098497A1 (fr) 2008-08-21

Family

ID=39689660

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070243 WO2008098497A1 (fr) 2007-02-13 2008-02-02 Système de service de diffusion multimedia et procédé de début de session, procédé de fin de session

Country Status (2)

Country Link
CN (1) CN101247553B (fr)
WO (1) WO2008098497A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766431A (zh) * 2020-06-02 2021-12-07 海能达通信股份有限公司 增强型广播多播服务的业务调度方法及系统

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101800938A (zh) * 2009-02-05 2010-08-11 华为技术有限公司 为mbms承载业务建立无线承载的方法、装置和系统
WO2010127485A1 (fr) * 2009-05-06 2010-11-11 华为技术有限公司 Procédé et appareil de traitement de session de service de diffusion-multidiffusion multimédia
CN103747527B (zh) * 2009-06-26 2017-04-26 华为技术有限公司 寻呼处理方法、通信装置及通信系统
CN101932040B (zh) 2009-06-26 2014-01-01 华为技术有限公司 寻呼处理方法、通信装置及通信系统
CN101702789B (zh) * 2009-10-20 2014-11-05 中兴通讯股份有限公司 多媒体组播和广播业务控制方法及其装置
CN103391513B (zh) * 2012-05-07 2019-05-10 中兴通讯股份有限公司 宽带数字集群业务的实现方法及集群调度管理中心
CN104301287B (zh) * 2013-07-16 2020-03-31 中兴通讯股份有限公司 一种多对多会话的实现方法、网络节点、服务器及系统
WO2016011621A1 (fr) * 2014-07-23 2016-01-28 华为技术有限公司 Procédé et appareil pour identifier un utilisateur de groupe
KR20170122640A (ko) * 2015-02-27 2017-11-06 소니 주식회사 수신 장치, 수신 방법, 송신 장치 및 송신 방법
CN106162372B (zh) * 2015-03-30 2019-05-10 中国移动通信集团公司 增强型多媒体广播多播业务音视频数据分流方法及装置
CN106612295B (zh) * 2015-10-21 2021-04-20 中兴通讯股份有限公司 一种应用下载方法、推送方法、装置及系统
US10667322B2 (en) * 2016-05-03 2020-05-26 Kt Corporation Method and apparatus for changing connection state of terminal
CN111813900B (zh) * 2019-04-10 2023-12-08 北京猎户星空科技有限公司 多轮对话处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1490960A (zh) * 2002-10-14 2004-04-21 北京三星通信技术研究有限公司 多媒体广播和组播业务中单用户的基于流量的计费方法
CN1645798A (zh) * 2004-07-26 2005-07-27 华为技术有限公司 多媒体广播/组播服务业务数据传输的方法
CN1839652A (zh) * 2003-08-19 2006-09-27 Lg电子株式会社 用于保证移动终端的通信业务质量的方法和装置
CN1848728A (zh) * 2005-04-14 2006-10-18 中国科学院声学研究所 一种基于ip网络的组播数据受控方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1490960A (zh) * 2002-10-14 2004-04-21 北京三星通信技术研究有限公司 多媒体广播和组播业务中单用户的基于流量的计费方法
CN1839652A (zh) * 2003-08-19 2006-09-27 Lg电子株式会社 用于保证移动终端的通信业务质量的方法和装置
CN1645798A (zh) * 2004-07-26 2005-07-27 华为技术有限公司 多媒体广播/组播服务业务数据传输的方法
CN1848728A (zh) * 2005-04-14 2006-10-18 中国科学院声学研究所 一种基于ip网络的组播数据受控方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766431A (zh) * 2020-06-02 2021-12-07 海能达通信股份有限公司 增强型广播多播服务的业务调度方法及系统

Also Published As

Publication number Publication date
CN101247553A (zh) 2008-08-20
CN101247553B (zh) 2011-08-10

Similar Documents

Publication Publication Date Title
WO2008098497A1 (fr) Système de service de diffusion multimedia et procédé de début de session, procédé de fin de session
US8107407B2 (en) EHSPA architecture
KR100640462B1 (ko) 임시 이동 그룹 식별자 생성 및 분배 방법
WO2019091456A1 (fr) Procédé et dispositif de transmission de service de multidiffusion
US8270324B2 (en) Method for bearer control and deletion, data distribution, and modification
US9030989B2 (en) Method and apparatus for broadcasting/multicasting content from mobile user equipment over an MBMS network
WO2008113263A1 (fr) Procédé pour supporter un service de diffusion/multidiffusion multimédia dans l'évolution d'une architecture système
CN101009908A (zh) Lte系统中支持mbms业务传输的方法
US7953006B2 (en) Handling multiple point-to-multipoint services
WO2008000130A1 (fr) Procédé et système permettant de réaliser un service multidiffusion multimédia
WO2018006279A1 (fr) Procédé, dispositif et système de traitement de service
CN102057699A (zh) Mbms的sae应用
JP2007535248A (ja) マルチメディアブロードキャスト／マルチキャストサービスにおけるセル情報の変化の通知方法
JP2006081173A (ja) マルチメディアブロードキャストマルチキャストサービスおよび関連デバイスの非アクティブ化方法
WO2008134968A1 (fr) Système, procédé et appareil pour fournir un service de diffusion/multidiffusion multimédia
KR20060120591A (ko) Ｍｂｍｓ용 공통 전송 채널 설정 방법
JP2007518318A (ja) マルチメディアマルチキャストサービスの登録方法
CN101166306A (zh) 承载控制、承载删除及数据分发的方法、系统及网络节点
WO2008025206A1 (fr) Procédé et réseau pour créer le tunnel de plan de contrôle dans le service de multidiffusion du système de communication mobile
JP4422763B2 (ja) マルチメディアブロードキャスト・マルチキャストサービスの起動方法
CN116684831A (zh) 一种数据传输方法、装置以及系统
WO2006015544A1 (fr) Procede d'etablissement d'une prise en charge dans un service de diffusion/multi-diffusion multimedia
CN101242353B (zh) 演进的通信系统及通信方法
CN102395110B (zh) Lte系统中支持mbms业务传输的方法
EP1821465B1 (fr) Procede de desactivation du service de diffusion multidiffusion multimedias

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08706619

Country of ref document: EP

Kind code of ref document: A1