[go: up one dir, main page]

WO2009000127A1 - Procédé permettant à un utilisateur d'accéder à un service de multidiffusion - Google Patents

Procédé permettant à un utilisateur d'accéder à un service de multidiffusion Download PDF

Info

Publication number
WO2009000127A1
WO2009000127A1 PCT/CN2007/003946 CN2007003946W WO2009000127A1 WO 2009000127 A1 WO2009000127 A1 WO 2009000127A1 CN 2007003946 W CN2007003946 W CN 2007003946W WO 2009000127 A1 WO2009000127 A1 WO 2009000127A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
user
terminal
service
join
Prior art date
Application number
PCT/CN2007/003946
Other languages
English (en)
Chinese (zh)
Inventor
Meiping Liu
Yong Zhao
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Publication of WO2009000127A1 publication Critical patent/WO2009000127A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present invention relates to the field of multimedia multicast, and more particularly to a method for realizing a user rejoining a multicast service when performing a mobile multimedia multicast service of multimedia broadcast multicast.
  • Multimedia Broadcast/Multicast Service enables point-to-multipoint services where a data source sends data to multiple users.
  • MBMS services can not only achieve plain text low-rate message-like multicast and broadcast, but also enable high-speed multimedia services for multicast and broadcast, multicast and broadcast services based on WCDMA (Wideband Code Division Multiple Access) / GSM (Global Mobile Communications) System) packet network, by adding some new functional entities, such as the Broadcast Multicast Service Center (BM-SC), to existing packet domain functional entities such as SGSN (Serving General Radio Packet Service Support Node), GGSN (Gateway Universal Wireless) The packet service support node), RNC (Radio Network Controller) and UE (User Equipment) add MBMS functions and define a new logical shared channel to implement air interface resource sharing.
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global Mobile Communications
  • BM-SC Broadcast Multicast Service Center
  • SGSN Serving General Radio Packet Service Support Node
  • GGSN Gateway Universal Wireless
  • the broadcast/multicast service center passes the Gmb interface (the control plane interface between the BM-SC and the GGSN) and the Gi interface (the bearer interface between the BM-SC and the GGSN) and the gateway general wireless packet service.
  • GPRS support node GGSN is connected, one BM-SC can be connected with multiple GGSNs, GGSN through Gn/Gp interface (in the same mobile network, the interface between GGSN and SGSN uses Gn interface protocol, GGSN and SGSN are In different mobile networks, the interface between the GGSN and the SGSN is connected to the SSGN by the Gp interface protocol, and one GGSN can be connected to multiple SGSNs through the Iu interface and the Universal Mobile Telecommunications System (UMTS) terrestrial radio access network ( UTRAN is connected, then UTRAN is connected to the mobile terminal through the Uu interface, and the SGSN can also be connected to the GSM Enhanced Radio Access Network (GERAN) through the Iu/Gb interface, and the GERAN is interfaced with Um (the interface between the GERAN and the UE is through the Um interface protocol).
  • the mobile terminal is connected.
  • Step a a user subscription process (Subscription)
  • the process is used for the user to subscribe to the multicast service, and establish a relationship between the user and the service provider.
  • Step b Announcement, which is used to notify the user of the services that the service provider can provide, as well as other business-related information.
  • Step c User join process (Joining), the process is used for the user to request to join the multicast group to the service network.
  • Step d Session Start
  • this process is used for ⁇ - SC to prepare to send data.
  • the BM-SC When the BM-SC is ready to transmit data, the BM-SC initiates the MBMS session start process. This is all the bearer resources required by the network when requesting activation of the MBMS data. And inform the interested UE to start data transmission.
  • Step e Notification process, which is used by the RNC to notify the user that MBMS multicast starts immediately.
  • Step f Data transfer process, which is a process of transmitting user multimedia data.
  • Step g Session Stop, the process is used to indicate that the session ends and the bearer resource is released.
  • Step h leaving the process (Leaving), the process is used for the process that the user is not ready to receive the multimedia broadcast and leave the multicast group.
  • the terminal After receiving the service announcement, if the terminal does not have a subscription service, the terminal can subscribe to the multimedia multicast service through various methods such as short message, WAP (Wireless Application Protocol), voice, and the like.
  • the terminal After the user subscribes to the multicast service, the terminal can join the multicast group for a period of time after receiving the service advertisement.
  • the join time may be before the start of the multimedia multicast service (the time interval between the join time and the session start request message may be several seconds, several minutes, or even hours), or may be during the multimedia multicast service reception process.
  • the user leaves the multicast service.
  • the user context is released due to the terminal or the network, that is, the user leaves the multicast service. For these reasons, users cannot receive multicast services in time. For these situations, the user does not necessarily know that he has left the multicast service he has actively joined, and the user does not want to be in these situations. Next, you need to check it out often to re-join.
  • the terminal needs to provide a better and more convenient function of rejoining the multicast service.
  • the technical problem to be solved by the present invention is to provide a method for a user to join a multicast service, and provide a solution for rejoining the multicast service for a non-user to leave the multicast group actively.
  • the present invention provides a method for a user to join a multicast service, including the following steps.
  • the terminal saves and adds the markup.
  • the user terminal When a non-user initiates the leave of the multicast group, the user terminal initiates a re-join process to the broadcast multicast service center according to the saved join flag, and joins the multicast service with the join mark.
  • the method may further include: the adding the tag is saved in the service guide; or the terminal constructing the table separately to save the service identifier of the multicast service that needs to be rejoined.
  • the foregoing method may further include: the situation that the non-user actively initiates leaving the multicast group refers to a terminal abnormal situation or a non-terminal abnormal situation.
  • the non-terminal abnormality situation is the network side cause, and the network side cause includes the broadcast multicast service center side initiating a leaving message to the user, or the gateway universal wireless packet service supporting node initiating a leaving message to the user, or serving the general wireless grouping.
  • the service support node initiates a leave message to the user.
  • the abnormal situation of the terminal refers to a situation in which the user context is released or the terminal leaves the multicast group unless the terminal abnormality occurs.
  • the method may further include: the time when the user rejoins the multicast service is one of the following conditions: after receiving the service guide of the multicast service, but the service user context is not present, the terminal checks the user. The joining mark is added to join the multicast service;
  • the terminal ends the multicast service with the join flag but no service user context at this time. Ending the specified time according to the content of the multicast service, and joining the multicast service;
  • the terminal joins the multicast service by checking the broadcast service after the location check or after the location update is completed, and the service has the join flag.
  • the method may further include: the user rejoining the multicast service by using an automatic mode or a manual mode, where
  • the automatic mode is to automatically join the multicast service according to the saved join flag; the manual mode is #> according to the saved join flag, reminding the user to determine whether to re-join the user according to the user's selection. Multicast service.
  • the method may further include: the step a further includes the following steps: Step 110: After the user opens the multicast service list, select the multicast service to be joined; Step 120, prompt the user to select whether the If the non-user initiates leaving the multicast group, the user rejoins the multicast service. If yes, go to step 130, otherwise, end.
  • Step 130 Save various reasons for joining the multicast service.
  • Step 140 Determine whether the user needs to automatically join the multicast service, and if yes, go to step 150, otherwise go to step 160;
  • Step 150 The terminal saves the required multicast service information, and marks the multicast service to be automatically added.
  • Steps The terminal saves the multicast service information required for re-joining, and marks the multicast service to remind the user to join manually.
  • the foregoing method may further include: in the step b, the user automatically joins the multicast service before receiving the multimedia multicast service, including the following steps,
  • Step 200 The terminal periodically scans the list with the added tag to find a multicast service in which the content has not started yet and needs to be rejoined;
  • Step 210 Select the multicast service that needs to be automatically rejoined
  • Step 220 Determine whether the reason for the terminal to leave the multicast group is the same as the reason why the terminal needs to be automatically re-joined. If yes, go to step 230. Otherwise, go to step 240.
  • Step 230 The terminal automatically generates A join message is sent to the broadcast multicast service center Send, the user rejoins the multicast service;
  • Step 240 Determine whether the scan is completed. If yes, the task ends, otherwise step 210 is performed. Further, the foregoing method may further include: in the step b, the method further includes: the user automatically joining the multicast service during the multimedia multicast service receiving process, including the following steps,
  • Step 300 When the terminal status changes from abnormal to normal, read a list with a join flag;
  • Step 310 it is determined whether there is the multicast service being received, and if so, step 320 is performed, otherwise, step 340 is performed;
  • Step 320 Determine whether the reason for the terminal leaving the multicast group is the same as the reason why the terminal needs to re-automatically join, if yes, go to step 330, otherwise, go to step 340;
  • Step 330 The terminal automatically generates one of the join messages to be sent to the broadcast multicast service center, and the user rejoins the multicast service.
  • Step 340 Determine whether the list with the join flag is read, and if yes, end the task; otherwise, execute step 310.
  • the method may further include: in the step b, the method further includes: the multimedia multicast service is prompted to manually join the multicast service before starting, including the following steps,
  • Step 400 The terminal periodically scans the list with the added tag to find a multicast service in which the content has not started yet and needs to be rejoined;
  • Step 410 Determine the multicast service that needs to be prompted to manually join the user
  • Step 420 The terminal sends a reminder message, or sends a prompt tone to remind the user whether to rejoin the multicast service by using the manual mode.
  • the foregoing method may further include: in the step b, the method further includes: prompting the user to manually join the multicast service during the multimedia multicast service receiving process, including the following steps,
  • Step 500 When the terminal status changes from abnormal to normal, read a list with a join flag;
  • Step 510 Determine the multicast service that needs to be prompted to manually join the user.
  • Step 520 The terminal sends a reminder message, or sends a prompt tone to remind the user whether to pass The manual mode is used to rejoin the multicast service.
  • the foregoing method may further include: the terminal periodically saves the reason for the user leaving the multicast service, or saves the reason for leaving the multicast group most recently:
  • the reason why the terminal saves the user of the multicast service according to the received leaving message is the network side reason, and the reason that the user who has not sent the active leaving message to save the multicast service leaves the user is the terminal side reason.
  • the present invention saves the multicast service information that the user joins in the terminal, and before the content of the multicast service starts or is sent by the multicast service, the terminal abnormally leaves the multicast group during the receiving process, and the network and the terminal If the user context is not established or the user leaves the multicast group service, the function of rejoining the multicast service is provided.
  • the present invention analyzes the user's context in which the user's context is released, causes the user to join the multicast service to be released, analyzes the way the user rejoins, and analyzes the time point when the user rejoins to achieve reasonable user rejoin.
  • the business enables the services that the user has joined to receive normally, and the users get better service.
  • FIG. 1 is a schematic diagram of a MBMS network structure
  • FIG. 2 is a flowchart of a method for a user to join a multicast service according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a user actively joining a multicast service according to an embodiment of the present invention
  • FIG. 4 is a multimedia diagram of a specific embodiment of the present invention
  • FIG. 5 is a flowchart of the user automatically joining the multicast service during the process of receiving the multimedia multicast service according to the embodiment of the present invention
  • FIG. 6 is a flowchart of a method for prompting a user to manually join a multicast service before the multimedia multicast service is started according to the embodiment of the present invention
  • the method of the specific embodiment of the present invention manages the multicast service that needs to be rejoined by the terminal, so that when the user needs to rejoin, the user can perform the multicast service in a manual or automatic manner.
  • the service that the terminal re-joins can be saved in combination with the service guide, that is, the re-added identifier is saved in the information related to the service guide, or the terminal separately creates a table to save the service identifier and re-add the identifier.
  • the multicast service starts to select the time for the user to join, including the multimedia multicast service content before the start of the multimedia multicast service, and the user needs to re-join the multicast service during the receiving process.
  • FIG. 2 A method for a user to join a multicast service according to a specific embodiment of the present invention is shown in FIG. 2, and the specific steps are as follows.
  • Step 210 Save the multicast service that the user needs to rejoin in the terminal and add the registration mark.
  • the add-on tag is stored in the service guide, or the terminal establishes a table to use the service identifier, and adds the identifier to mark. For example, the terminal can separately establish a list, where the service identifier of all the multicast services that need to be rejoined is saved.
  • the service guide is also called a service announcement, and the terminal usually keeps a service announcement locally.
  • Step 220 According to the saved join flag, if the user leaves the multicast group in an abnormal situation, the user terminal initiates re-joining to the BM-SC, and joins the multicast service with the join flag.
  • An abnormal situation occurs when a user leaves a multicast group.
  • the abnormal situation of the terminal (the user shuts down, the user does not shut down, and the abnormality leaves the multicast group), and the non-terminal abnormality (that is, the network side causes).
  • the abnormal situation of the terminal includes the user leaving the multicast group when the user is shut down, and the user is passively leaving the multicast group when the user is shut down.
  • the non-user shutdown situation includes power failure, power plugging and unplugging the battery.
  • the network side causes that the BM-SC side initiates a Leaving message to the user; the GGSN initiates a Leaving message to the user; the SGSN side initiates Leaving to the user, and the time for the user to rejoin the multicast service can be added according to the join.
  • the tag check service guide or the re-established service list is already delivered to the multicast service, but the multicast service is not added to the multicast group service (that is, there is no service user context), and the multicast service is added; or, for the multicast service. If the service is not added to the multicast group, the service is not added to the multicast group.
  • the multicast service is added to the multicast service before the start of the multicast service.
  • the user or the system can specify the time. The specified time may be a minute or a second.
  • different re-joining modes can be selected, including automatic mode and manual mode.
  • the automatic mode selects the re-joined user terminal to enter the multicast group according to the saved registration mark, when the time is specified before the start of receiving the multicast service content or is suddenly interrupted and received during the receiving process.
  • a method for a user to join a multicast service is further described below.
  • FIG. 3 illustrates a process in which a user of the present invention actively joins a multicast service, as follows: Step 300: A user opens a multicast service list.
  • the multicast service list is usually presented to the terminal user by the user receiving the Service Announcement (also called the service guide). .
  • Step 310 The user selects a multicast service to be joined.
  • the user selects the multicast service to be added on the terminal.
  • the user can select one or more multicast services to join.
  • Step 320 Prompt the user to select whether to re-join the multicast service if the non-user initiates the leave of the multicast group. If the user chooses yes, go to step 330. Otherwise, end the process and continue the normal process.
  • Step 330 The user selects a reason for re-joining automatically, and the terminal saves various reasons for joining the multicast service.
  • the reason for joining includes re-joining in the case of non-terminal abnormality. This is mainly because the terminal receives the leaving message from the network side; or re-joins in the abnormal situation of the terminal. In this case, the terminal is abnormal, including the terminal caused by the terminal shutdown. Leave the multicast situation, etc.
  • Step 340 The user selects whether it needs to join automatically or manually.
  • the terminal determines that if the user chooses to automatically join the multicast service, step 350 is performed, otherwise step 360 is performed;
  • Step 350 The terminal saves the multicast service information required to rejoin, and marks the multicast service to be automatically added and ends.
  • Step 360 The terminal saves the multicast service information required for re-joining, and marks the multicast service to remind the user to manually join and end.
  • the user automatically joins, and the user is in the contracted multicast service.
  • the user actively chooses to join the multicast group.
  • the terminal automatically joins according to the principle of automatic join.
  • the terminal needs to modify the process of receiving the Leaving by the user.
  • the terminal reads the multicast service information stored by the terminal for the multicast service, and if the multicast service needs to be re-joined,
  • the cause of the user leaving the multicast group in the multicast service is the cause of the abnormality of the terminal.
  • the cause of the exception is caused by the release of the user context or the user leaving the multicast group. For a multicast service that needs to be rejoined, if it has been saved If the user leaves the user, the terminal can update to the latest reason for leaving the multicast group as needed, or not update to the latest reason for leaving the multicast group.
  • FIG. 4 illustrates a process in which a user automatically joins a multicast service before receiving a multimedia multicast service, as follows.
  • Step 400 The terminal periodically scans the multicast service list, and searches for a multicast service in which the content has not started yet and needs to be rejoined;
  • the terminal sets up a timer, and the scheduled scan content has not yet started, and the multicast service list needs to be rejoined.
  • the terminal can consider that the multicast service that should start but does not start and has not sent the active exit message before is considered to be abnormally exiting the multicast service. If the Leaving message on the network side is received, the terminal considers it to be the network side cause, otherwise it is considered as the terminal cause. .
  • Step 410 Select a multicast service that needs to be automatically re-joined from the list with the join flag.
  • the list includes the multicast service that needs to be manually added, and the multicast service that is automatically re-joined. Broadcast business.
  • Step 420 Determine whether the reason for the terminal leaving the multicast group is the same as the reason why the terminal needs to re-automatically join, if yes, go to step 430, otherwise, go to step 440;
  • Step 430 The terminal automatically generates a join message to send to the BM-SC, and the user rejoins the multicast service.
  • the parameter encapsulation and transmission method of the join message is the same as the parameter encapsulation and transmission method when the user selects the service from the service guide to add.
  • Step 440 Determine whether the scan is completed. If yes, the task ends, otherwise step 410 is performed. The terminal determines whether the scanning of the multicast service list that needs to be rejoined is completed. If yes, the current scheduled scanning task ends. Otherwise, step 410 is performed.
  • FIG. 5 illustrates a process in which a user automatically joins a multicast service during a multimedia multicast service receiving process, as follows.
  • Step 500 When the terminal status changes from abnormal to normal, read a multicast service list that the terminal needs to automatically rejoin; Step 510: Determine whether there is a multicast service that is being delivered and needs to be received, if yes, go to step 520, otherwise, go to step 540;
  • the service guide contains information about each multicast service, including the start time of the multicast service content and the end time of the content.
  • the BM-SC will establish a session a few seconds or minutes before the start time of the multicast service content.
  • Step 520 Determine whether the reason for the terminal leaving the multicast group is the same as the reason why the terminal needs to re-automatically join, if yes, go to step 530, otherwise, go to step 540;
  • Step 530 The terminal automatically generates a join message to send to the BM-SC, and the user rejoins the multicast service.
  • the parameter encapsulation and transmission method of the join message is the same as the parameter encapsulation and transmission method when the user selects the service from the service guide to add.
  • Step 540 Determine whether the multicast service list that needs to be rejoined is read, and if yes, end the task. Otherwise, go to step 510.
  • the terminal determines whether the multicast service list that needs to be rejoined is read. If yes, the task is completed. Otherwise, step 510 is performed.
  • Figure 6 depicts the process of prompting users to join the multicast service before the content of the multimedia multicast service starts.
  • the user does not know which multicast services need to be re-joined in a timely manner. By means of the reminder, the user can actively select the multicast to be joined again.
  • Business as follows,
  • Step 600 The terminal periodically scans the list with the added tag to find a multicast service in which the content has not started yet and needs to be reminded to rejoin the user;
  • the terminal setup timing ⁇ the scheduled scan has no content that has not started, and needs to remind the user to re-add the multicast service list.
  • Step 610 Determine a multicast service that needs to be prompted to manually join the user.
  • the terminal selects a service list that meets various joining reasons according to various reasons for joining, and needs to remind the user to manually join the service list at that time. Specifically, it is to select a multicast service that needs to be manually re-joined due to the abnormality of the terminal, and to select a multicast service that needs to be manually re-joined due to a non-terminal abnormality.
  • Step 620 The terminal reminds the user whether to manually rejoin the multicast service.
  • the terminal generates a reminder message or sends a prompt tone to remind the user whether to manually rejoin the multicast service.
  • Figure 7 illustrates the process of manually adding a multimedia multicast service to the user.
  • the user does not have to know which services need to be re-joined.
  • the user can actively select the multicast service to join again. details as follows,
  • Step 700 When the terminal status changes from abnormal to normal, read a multicast service list that needs to be prompted to rejoin the user;
  • Step 710 Determine a multicast service that needs to be prompted to manually join the user.
  • Step 720 The terminal reminds the user whether to manually rejoin the multicast service.
  • the terminal generates a reminder message or sends a prompt tone to remind the user whether to manually rejoin the multicast service.
  • the present invention considers that a user does not actively leave a multicast group, which may be caused by a network abnormality or a terminal abnormality, and the user is subjectively reluctant to exit the multicast group.
  • the method of the present invention is designed such that the user terminal You can rejoin the multicast group that you have joined when you log out abnormally, which increases the robustness of the system and enables users to obtain more excellent services.

Landscapes

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

Abstract

Cette invention se rapporte à un procédé permettant à un utilisateur d'accéder à un service de multidiffusion. Il prévoit une solution permettant d'accéder à nouveau au service de multidiffusion, en cas d'abandon d'un groupe de multidiffusion par initiative, sans désir de la part de l'utilisateur. Le procédé comprend les étapes suivantes : a) pour le service de multidiffusion auquel accède un utilisateur, un terminal le sauvegarde et crée une signature d'accès ; b) en cas d'abandon du groupe de multidiffusion par initiative, sans désir de la part de l'utilisateur, en fonction de la signature d'accès sauvegardée, le terminal utilisateur accède à nouveau au BM-SC par initiative, et accède au service de multidiffusion avec la signature d'accès.
PCT/CN2007/003946 2007-06-28 2007-12-29 Procédé permettant à un utilisateur d'accéder à un service de multidiffusion WO2009000127A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007101272075A CN101335635B (zh) 2007-06-28 2007-06-28 一种用户加入组播业务的方法
CN200710127207.5 2007-06-28

Publications (1)

Publication Number Publication Date
WO2009000127A1 true WO2009000127A1 (fr) 2008-12-31

Family

ID=40185165

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/003946 WO2009000127A1 (fr) 2007-06-28 2007-12-29 Procédé permettant à un utilisateur d'accéder à un service de multidiffusion

Country Status (2)

Country Link
CN (1) CN101335635B (fr)
WO (1) WO2009000127A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1203695C (zh) * 2002-08-13 2005-05-25 北京三星通信技术研究有限公司 临时移动组标识的产生与分配方法
CN1756212A (zh) * 2004-09-29 2006-04-05 华为技术有限公司 一种用户重新加入多媒体广播/组播业务的方法
CN1756162A (zh) * 2004-09-27 2006-04-05 华为技术有限公司 一种用户加入多媒体广播/组播业务的方法
CN1894988A (zh) * 2003-12-19 2007-01-10 国际商业机器公司 无线局域网中客户端的自发重新关联
CN101047588A (zh) * 2006-06-26 2007-10-03 华为技术有限公司 一种加入广播/多播业务服务方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1203695C (zh) * 2002-08-13 2005-05-25 北京三星通信技术研究有限公司 临时移动组标识的产生与分配方法
CN1894988A (zh) * 2003-12-19 2007-01-10 国际商业机器公司 无线局域网中客户端的自发重新关联
CN1756162A (zh) * 2004-09-27 2006-04-05 华为技术有限公司 一种用户加入多媒体广播/组播业务的方法
CN1756212A (zh) * 2004-09-29 2006-04-05 华为技术有限公司 一种用户重新加入多媒体广播/组播业务的方法
CN101047588A (zh) * 2006-06-26 2007-10-03 华为技术有限公司 一种加入广播/多播业务服务方法及装置

Also Published As

Publication number Publication date
CN101335635B (zh) 2012-03-07
CN101335635A (zh) 2008-12-31

Similar Documents

Publication Publication Date Title
KR101148801B1 (ko) 방송 통신 시스템에서의 시그널링 방법 및 시스템
JP4426591B2 (ja) セルラー通信システムにおけるブロードキャスト又はマルチキャストサービスに関連したメッセージを送信する方法
TWI321281B (en) Method and system for a multicast service initiation in a communication system
EP1739876B1 (fr) Procédé, dispositif et système de terminaison d'une session utilisateur dans un service de multidiffusion
EP1715699B1 (fr) Procédé de notification de la modification de l'information de cellule dans un service multimedia multidiffuse
CN101136814B (zh) 一种支持mbms业务的方法和装置
CN100442701C (zh) 网络侧获知用户接收多媒体广播/组播业务情况的方法
JP2008529447A (ja) マルチメディア・ブロードキャスト・マルチキャスト方式サービス（ｍｂｍｓ）のための改良されたリソース活用
JP2005236988A (ja) マルチメディア・ブロードキャスト／マルチキャストサービスのための制御情報を効率的に送信する方法
JP2006526352A (ja) 無線通信ネットワークにおける無線端末機の移動性をサポートするための装置及び方法
EP1761079A1 (fr) Methode de simplification de procede de transmission de message
WO2006015553A1 (fr) Procede de transmission de service de serveur de diffusion/multi-diffusion multimedia
EP2260651B1 (fr) Changement de porteuse pour prendre part à une session en multidiffusion dans un réseau de communications sans fil
WO2007010983A1 (fr) Procédé de fourniture de contenus multimédia et station mobile
WO2006015555A1 (fr) Procede permettant d'informer un utilisateur d'un equipement radio au sujet de parametres de configuration d'un service de diffusion/multi-diffusion multimedia
WO2006032215A1 (fr) Procede pour commander un terminal utilisateur selectionnant une cellule dans un systeme de radiocommunications
CN101175252A (zh) 多媒体广播组播服务中建立会话的方法和网络系统
KR101095422B1 (ko) 하나의 그룹 대화 중 광고 플레잉을 제어하기 위한 방법 및 시스템, 및 광고 플레이
WO2007022712A1 (fr) Procede, dispositif d'abonnement et dispositif reseau de transmission de message multimedia de service diffusion/multidiffusion
JP4422763B2 (ja) マルチメディアブロードキャスト・マルチキャストサービスの起動方法
JP4047888B2 (ja) マルチメディア・ブロードキャスト・マルチキャスト・サービスの加入者にセッションデータを提供するための方法および装置
CN101039454A (zh) 无线通讯系统中停止一点对多点多媒体广播的方法及装置
JP5185384B2 (ja) 無線通信ネットワーク内の同報オーバーヘッド・メッセージ規制
WO2009000127A1 (fr) Procédé permettant à un utilisateur d'accéder à un service de multidiffusion
WO2006034636A1 (fr) Procede permettant a un utilisateur d'acceder a un service de diffusion/multidiffusion multimedia

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

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

Country of ref document: EP

Kind code of ref document: A1