WO2005107155A1 - Procede de determination du nombre total d'utilisateur dans un systeme de service de diffusion/multidiffusion (mbms) - Google Patents

Procede de determination du nombre total d'utilisateur dans un systeme de service de diffusion/multidiffusion (mbms) Download PDF

Info

Publication number
WO2005107155A1
WO2005107155A1 PCT/CN2005/000582 CN2005000582W WO2005107155A1 WO 2005107155 A1 WO2005107155 A1 WO 2005107155A1 CN 2005000582 W CN2005000582 W CN 2005000582W WO 2005107155 A1 WO2005107155 A1 WO 2005107155A1
Authority
WO
WIPO (PCT)
Prior art keywords
bsc
mbms
rnc
session
ues
Prior art date
Application number
PCT/CN2005/000582
Other languages
English (en)
Chinese (zh)
Inventor
Hai Zhang
Original Assignee
Huawei Techonologies 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 Techonologies Co., Ltd. filed Critical Huawei Techonologies Co., Ltd.
Publication of WO2005107155A1 publication Critical patent/WO2005107155A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • 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
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the invention relates to an implementation method for transmitting multimedia broadcast / multicast services, and in particular, to a method for determining the number of receiving users in a multimedia broadcast / multicast service (MBMS).
  • MBMS multimedia broadcast / multicast service
  • the third-generation mobile communication can provide services with higher data rates than the second-generation mobile communication, thereby supporting a variety of business forms. Such as video calls, picture downloads, high-speed Internet browsing and other services.
  • One type of service is characterized by: The service can be sent to users who have subscribed to the service in the wireless network at the same time. For example, weather forecasts, news clips, sports competition highlights, and so on. Taking advantage of the simultaneous transmission of these services, the third-generation mobile communication introduced the concept of multicast / broadcast.
  • Figure 1 shows the working principle of MBMS.
  • an intermediate node for example: 10 or 101 or 102 in the figure, its upstream node always sends a copy of data to the intermediate node; after receiving the data, the intermediate node expects to receive data according to the number of downstream nodes Copy the data, and distribute the data to each downstream node that expects to receive the data.
  • each branch of the multicast / broadcast service data transmission tree has only one copy of data to transmit, occupying one copy of transmission resources, and the root node and its The same is true for data transmission from downstream nodes.
  • the difference between the multicast service and the broadcast service is only that: the multicast service only sends corresponding information to users who have subscribed to certain information, and the broadcast service sends information to all users in the wireless network. It can be seen from the above description that, by providing the same information to a large number of users at the same time through the multicast / broadcast service, network resources can be greatly saved.
  • FIG. 2 is a schematic diagram of a wireless network structure supporting a multicast / broadcast service.
  • the wireless supporting multicast / broadcast services in the existing 3rd Generation Partnership Project (3GPP)
  • the network structure is a broadcast / multicast service center (BM-SC) 201 connected to a gateway general packet radio service (GPRS) support node (GGSN, Gateway GPRS Support Node) 202 through a Gmb interface or a Gi interface.
  • GPRS general packet radio service
  • One BM-SC 201 can communicate with Multiple GGSN 202 is connected; GGSN 202 is connected to a serving GPRS support node (SGSN, Serving GPRS Support Node) 203 through a Gn / Gp interface, one GGSN 202 can be connected to multiple SGSN 203; SGSN 203 can be connected to general mobile via Iu interface Communication System (UMTS) Land Radio Access Network (UTRAN) 204 is connected, and then UTRAN 204 is connected to a communication terminal 206 through a Uu interface. SGSN 203 can also enhance wireless access with the Global System for Mobile Communications (GSM) through an Iu / Gb interface. A network (GERAN) 205 is connected, and then the GERAN 205 is connected to the communication terminal 206 through a Um interface.
  • GSM Global System for Mobile Communications
  • the MBMS bearer context is used to save the MBMS bearer capability, and the context contains definitions. All information descriptions of an MBMS service bearer are created at all nodes carrying MBMS data. As shown in Table 1, the MBMS bearer context includes: IP multicast address, APN, TMGI, State, required MBMS bearer capacity, QoS, MBMS service area, downstream node list, number of UEs, etc.
  • the IP multicast address identifier is the MBMS bearer described by the MBMS bearer context;
  • APN is the access point name for which the IP multicast address has been defined;
  • TMGI is the temporary mobile group identifier assigned to the MBMS bearer;
  • State is the MBMS bearer
  • the active state ('stationary, or' active, ') identifies whether a bearer plane resource for MBMS data transmission is required to be established; the required MBMS bearer capability identifies the minimum bearer capability that the UE needs to support.
  • QoS is the quality of service required by the MBMS bearer
  • MBMS service area is the area where MBMS services need to be sent
  • the downstream node list is a list of downstream nodes to which the MBMS bearer is requested and MBMS data must be delivered
  • the number of UEs is owned by the node The number of UEs that have joined the multicast service.
  • IP multicast address identifies the MBMS bearer described by the MBMS bearer context X X X X address
  • the active state carried by the MBMS ('stationary, or to be studied X X X
  • MBMS data must be downloaded X X X point list List of downstream nodes sent to
  • An existing MBMS session process includes two parts: first, the core network part informs the RNC that an MBMS session is about to start; then the BSC / RNC establishes the necessary radio resources for transmitting MBMS data to the UE of interest. Among them, whether the BSC RNC establishes a radio bearer, whether to establish a point-to-point radio bearer, or a point-to-multipoint radio bearer is determined by the BSC / RNC by performing a counting process.
  • the MBMS session start process is triggered when the BM-SC is ready to send data.
  • the session initiation process activates all required bearer resources for transmitting MBMS data in the network, and notifies the interested UE that data transmission is about to begin.
  • the BM-SC provides session attributes such as QoS of MBMS 10, MBMS service domain, and estimated session length parameters (if any) to relevant network nodes of interest.
  • session attributes such as QoS of MBMS 10, MBMS service domain, and estimated session length parameters (if any) to relevant network nodes of interest.
  • related RNCs will be triggered to perform session notifications on the access network, cell user counting, radio bearer type selection, and establishment of wireless and wired bearer planes.
  • FIG. 3 is a schematic diagram of a prior art MBMS session initiation process. The process includes the following steps:
  • Step 301 The BM-SC sends a session start request (Session Start Request) to the GGSN stored in the "downstream node list" parameter in the corresponding MBMS bearer context to indicate the transmission to be started, and sets the status attribute of the MBMS bearer context to "activation".
  • the request provides session attributes such as QoS, MBMS service domain, and estimated length of the session.
  • Step 302 After receiving the session start request message, the GGSN saves the session attributes provided in the message in the MBMS bearer context, sets the status attribute of the MBMS bearer context to "active", and sends a session start response message to the BM-SC ( Session Start Response).
  • the BM-SC Session Start Response
  • Step 303 The GGSN sends an MBMS Session Start Request message (MBMS Session Start Request) to the SGSN stored in the "downstream node list" parameter in the corresponding MBMS bearer context.
  • MBMS Session Start Request MBMS Session Start Request
  • step 304 after receiving the MBMS session start request message, the SGSN saves the session attributes in the MBMS bearer context, and sets the status attribute of the MBMS bearer context to "active", and sends an MBMS Session Start Response message (MBMS Session Start Response) to the GGSN. ), The message provides a tunnel termination point identifier (TEID) for the bearer plane, and is used for the GGSN to send MBMS data.
  • TEID tunnel termination point identifier
  • Step 305 The SGSN sends an MBMS Session Start Request message (MBMS Session Start Request) to each BSC / RNC connected to the SGSN, where the message includes a session attribute.
  • MBMS Session Start Request MBMS Session Start Request
  • Step 306 The BSC / RNC determines whether it is in the MBMS service domain. If the BSC / RNC is in the MBMS service domain, first save the session attributes in the MBMS bearer context, set the status attribute of the MBMS bearer context to "active", and then execute the step. 307; otherwise Go directly to step 307.
  • Step 307 The BSC RNC sends an MBMS Session Start Response message (MBMS Session Start Request) to the SGSN.
  • MBMS Session Start Request MBMS Session Start Request
  • a BSC / RNC receives multiple MBMS session start request messages, which carry .Iu bearer plane parameters, and only returns one MBMS session start response message, which is used to establish an Iu plane bearer that reaches an SGSN.
  • the BSC / RNC includes the TEID in the MBMS session start response message, which is used by the SGSN for the Iu bearer. Plane used to send MBMS data.
  • the MBMS session start response message it sends to the SGSN indicates that the BSC / RNC is not in the MBMS service domain.
  • the BSC / RNC can establish the necessary radio resources for transmitting MBMS data to the UE of interest in the MBMS service domain.
  • the BSC / RNC After the BSC / RNC receives the MBMS session start message from the SGSN, it counts the number of users in each cell in the BSC / RNC who expect to receive the MBMS session, so as to decide whether to send in the cell. MBMS session data.
  • FIG. 4 is a flowchart of a prior art BSC / RNC performing statistics on receiving users. The process includes the following five steps:
  • Step 401 The BSC / RNC sends a count request message to the UE in the cell that has activated the MBMS service.
  • Step 402 The UE returns a count response message to the BSC / RNC to establish a connection.
  • Step 403 The BSC / RNC sends an inquiry message to the UE in the cell that has activated the MBMS service through the connection, and asks whether the UE receives the MBMS session.
  • Step 404 The UE that agrees to receive the MBMS session returns a query response ⁇ message to the BSC / RNC.
  • Step 405 The BSC / RNC performs statistics on the UEs that have returned the consent to receive a response, and determines the number of receiving users according to the statistical result. The specific method is as follows: if the inquired UE agrees to receive the MBMS session, the BSC / RNC records the UE that has returned the consent reception response to the number of users who expect to receive the MBMS session; otherwise, the BSC / RNC will not count the UE Enter the number of users who expect to receive the MBMS session.
  • the BSC / RNC sets a user count threshold in advance. If all the UEs that return a response are counted, the total number of users who expect to receive the MBMS session does not reach the user count threshold. The total number is determined to be established. Number of receiving users in radio bearer mode. If the total number of users expecting to receive the MBMS session reaches the user number threshold during the statistics of the UEs that responded, the BSC / RNC stops receiving query response messages returned by other UEs.
  • the user count threshold is The number of receiving users who decide to establish a radio bearer.
  • the BSC / RNC decides whether to send based on the number of users who expect to receive the MBMS session. If it is sent, the corresponding way of establishing a radio resource bearer is also determined according to the number of users who expect to receive the MBMS session and other RRM algorithms.
  • a point-to-point transmission method is adopted; when the number of users is relatively large, that is, the number of users reaches the counting threshold, Adopt point-to-multipoint transmission.
  • MBMS services can carry a variety of services, including services that require users to confirm receipt, such as video and audio; and services that do not require users to confirm receipt, such as text, small pictures, file downloads, and advertisements. And if the BSC / RNC also continues to inquire about those service users who do not need the user to confirm the reception, it will increase the complexity of the wireless interface 'load and network signaling interaction. At the same time, the response process of the UE is increased, which consumes more power. Summary of the invention
  • the main object of the present invention is to provide a method for determining the number of receiving users in a multimedia broadcast / multicast service, reduce unnecessary waste of radio interface resources, and simplify the network signaling process.
  • a method for determining the number of receiving users in a multimedia broadcast / multicast service MBMS includes the following steps:
  • the core network side sends a query identifier to the base station controller BSC / radio network controller RNC, where the query identifier is used to instruct the BSC / RNC to ask the user whether to receive the MBMS session;
  • the BSC / RNC judges whether the query identifier received from the core network side is valid, and if it is valid, it asks the user equipment UE whether to receive the MBMS session, and determines according to the UE willing to receive the session Number of receiving users; otherwise, the number of receiving users is determined according to the willingness of all users who have activated the MBMS service to receive the session.
  • step 1) may include:
  • the broadcast / multicast service center BM-SC sets according to the nature of the service to indicate whether the query identifier of the BSC / RNC is valid;
  • the BM-SC initiates a session start request to the serving GPRS support node SGSN through the gateway GPRS support node GGSN, and the session start request includes the query identifier;
  • the SGSN After receiving the session start request sent by the GGSN, the SGSN sends a MBMS session start request to the BSC / RNC, where the session start request includes the query identifier.
  • the step 12) may be: the BM-SC sends a session start request message including the query identifier to the GGSN; after receiving the session start request, the GGSN sends an MBMS session start request message including the query identifier to the SGSN.
  • Step 2) The method for determining whether the query identifier is valid may be: obtaining the query identifier from the session start request, and determining whether the query identifier is valid.
  • Step 2) The process in which the BSC / RNC asks the UE whether to receive the MBMS session may include:
  • the BSC / RNC sends an inquiry request to the UE in the cell that has activated the MBMS service;
  • the UE that agrees to receive the MBMS session returns a query response message to the BSC / RNC.
  • the method for determining the number of receiving users according to the UEs willing to receive the session may be: Counting the UEs returning the query response message, and determining the number of receiving users according to the counted UEs.
  • the specific method is as follows: if the BSC / RNC collects statistics on all UEs that return a query response, and the counted UE number does not reach a predetermined user count threshold, the counted UE number is determined as the number of receiving users; During the RNC statistics on the UEs that returned the query response, the number of counted UEs reached the predetermined user count threshold, the BSC / RNC stopped receiving the query response returned by the UE, and determined the predetermined user count threshold as the receiving user. Number of.
  • Step 2) The process of determining the number of receiving users according to the willingness of all users who have activated the MBMS service to receive the session may include:
  • the BSC / RNC sends a counting request to the UE in the cell where the MBMS service is activated;
  • the BSC / RNC performs statistics on the UEs whose feedback counts are responded; and determines the number of receiving users according to the counted UE numbers.
  • the step 25) may be:
  • the counted UE number is determined as the number of receiving users
  • the BSC / RNC performs statistics on the UE that responds to the feedback count, the statistical If the number of UEs reaches a predetermined user count threshold, the BSC / RNC stops receiving the counting response fed back by the UE, and determines the predetermined user count threshold as the number of receiving users.
  • the method for determining the number of receiving users in the multimedia broadcast / multicast service of the present invention carries an inquiry identifier in the MBMS session start request message sent to the BSC / RNC, and the inquiry identifier is used for Instruct the BSC / RNC to ask the user whether to receive the MBMS session before establishing the radio resource.
  • the BSC / RNC decides whether to ask the user whether to receive the MBMS session when determining the count based on the identifier. If it is indicated that the user is not required to receive the MBMS session, the BSC / RNC determines the number of receiving users according to the willingness of all users who have activated the MBMS service to receive the session.
  • Figure 1 is a schematic diagram of the working principle of MBMS
  • FIG. 2 is a schematic diagram of a wireless network structure supporting multicast / broadcast services
  • FIG. 3 is a schematic diagram of a prior art MBMS session initiation process
  • FIG. 4 is a flow chart of statistics of receiving users by the BSC / RNC in the prior art
  • FIG. 5 is a flowchart of BSC / RNC establishing radio resources in a preferred embodiment of the present invention. Mode of Carrying Out the Invention
  • a message sent by the core network side to the access network includes a related identifier, and the access network root Based on the identification, it is determined whether to ask the user whether to receive the MBMS session. If the indication is not required. Asking the user whether to receive the MBMS session, the BSC / RNC determines the number of receiving users according to the willingness of all users who have activated the MBMS service to receive the session.
  • the following describes the process of sending a weather forecast service in text format to MBMS users subscribed to the service as a preferred embodiment in detail.
  • the BM-SC decides that when the BSC / RNC counts the number of receiving users, the BSC / RNC is not required to ask the user whether to receive the MBMS session, so it will instruct the BSC / RNC to ask the user
  • the query ID for whether to receive this MBMS session is set to invalid.
  • the session start process of this embodiment is the same as that shown in FIG. 3 for the prior art MBMS session start process, except that the BM-SC sends a session start request message to the GGSN, the GGSN sends the MBMS session start request message to the SGSN, and the SGSN sends the BSC / RNC
  • the MBMS session start request message carries the query ID set as invalid as described above.
  • the process includes the following steps:
  • Step 301 The BM-SC sends a Session Start Request message to the GGSN stored in the "downstream node list" parameter in the corresponding MBMS bearer context, indicating a transmission to be started, and sets the status of the MBMS bearer context attribute. Is "activated".
  • the request provides session attributes such as QoS, MBMS service domain, and estimated length of the session.
  • the message also carries a query identifier set to invalid.
  • Step 302 After receiving the session start request message, the GGSN saves the session attributes provided in the MBMS bearer context, sets the status attribute of the MBMS bearer context to "active", and sends a session start response to the BM-SC. Message (Session Start Response).
  • Step 303 The GGSN sends an MBMS session start request message (MBMS) to the SGSN stored in the "downstream node list" parameter in its corresponding MBMS bearer context. Session Start Request), this message also carries a query ID set to invalid.
  • the SGSN After receiving the MBMS session start request message, the SGSN saves the session attributes in the MBMS bearer context and sets the status attribute of the MBMS bearer context to "active", and sends an MBMS session start response message (MBMS Session Start) to the GGSN. Response), the message provides a tunnel termination point identifier (TEID) for the bearer plane, and is used for the GGSN to send MBMS data.
  • TEID tunnel termination point identifier
  • Step 305 The SGSN sends a .MBMS Session Start Request message (MBMS Session Start Request) to each BSC / RNC connected to the SGSN.
  • the message contains the session attributes, and the message also carries a query set to invalid. logo.
  • Step 306 The BSC / RNC determines whether it is in the MBMS service domain. If the BSC / RNC is in the MBMS service domain, first save the session attributes in the MBMS bearer context, set the status attribute of the MBMS bearer context to "activated", and then execute the step. 307; Otherwise, go directly to step 307.
  • Step 307 The BSC / RNC sends an MBMS Session Start Response message (MBMS Session Start Request) to the SGSN.
  • MBMS Session Start Request MBMS Session Start Request
  • a BSC / RNC receives multiple MBMS session start request messages, which carry Iu bearer plane parameters. Only one MBMS session start response message is returned, which is used to establish an Iu plane bearer that reaches an SGSN.
  • the BSC / RNC includes the TEID in the MBMS session start response message for the Iu bearer plane that the SGSN uses to send MBMS data.
  • the MBMS session start response message sent to the SGSN indicates that the BSC / RNC is not in the MBMS service domain. 'Then, the BSC / RNC can establish the necessary radio resources for transmitting MBMS data to the UE of interest in the MBMS service domain.
  • the BSC / RNC receives the MBMS session start message sent by the SGSN, it counts the number of users in each cell in the BSC / RNC who expect to receive the MBMS session, so as to decide whether to send MBMS session data in the cell.
  • FIG. 5 is a flowchart of BSC / RNC establishing wireless resources in a preferred embodiment of the present invention.
  • the BSC / RNC sets a user count threshold value in advance according to a method of setting a user count threshold value in the prior art.
  • the process includes the following steps: Step 501: The BSC / RNC receives an MBMS session start message sent by the SGSN.
  • step 502 the BSC / RNC judges whether the query identifier in the received MBMS session start message is valid, and if it is valid, step 503 is performed; otherwise, step 504 is performed.
  • the BM-SC sets the query identifier to invalid according to the nature of the service, so this embodiment directly performs step 504.
  • Step 503 Perform the prior art process to perform statistics on the UEs that return the query response message, and determine the number of receiving users according to the counted UEs. Then proceed to step 505.
  • the existing process described here is the process for the BSC / RNC to perform statistics on receiving users as shown in FIG. 4.
  • Step 504 Determine the number of receiving users according to the willingness of all users who have activated the MBMS service to receive the session. It includes the following steps:
  • the BSC / RNC sends a counting request to the UE in the cell that has activated the MBMS service; b. All UEs that have received the counting request feed back the counting response to the BSC / RNC and establish a connection;
  • the BSC / RNC collects statistics on the UEs that have responded to the count and determines the number of receiving users according to the counted UEs.
  • the counted UE number is determined as the number of receiving users; If during the BSC / RNC statistics on the UEs that responded to the feedback count, the number of counted UEs reaches a predetermined user count threshold, the BSC / RNC stops receiving the count response from the UE and sets the predetermined user count threshold Determined as the number of receiving users.
  • Step 505 The BSC / RNC determines a transmission mode to establish a radio resource bearer according to the number of users who expect to receive the MBMS session.
  • a corresponding method for establishing a radio resource bearer is also determined according to the number of users who expect to receive the MBMS session and other RRM algorithms.
  • the point-to-point transmission method is adopted; when the number of users is relatively large, that is, the user count threshold is reached, the Point-to-multipoint transmission.
  • the MBMS service in the present invention refers to a multicast service. Since the multicast service only sends corresponding information to users who have subscribed to certain information, and the broadcast service sends information to all users in the wireless network, the multicast service needs to count the receiving users, and the broadcast service does not need to statistics.
  • the wireless network interface resources are reduced. Waste, simplifying the network signaling process. The unnecessary UE response process is avoided, the UE is more power-saving, and the standby time of the UE is increased.

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 procédé de détermination du nombre total d'utilisateurs récepteurs dans un système de diffusion/multidiffusion (MBMS). Ce procédé englobe les opérations suivantes: (1) au cours de la procédure de lancement de session, le réseau principal envoie un identifiant de recherche au contrôleur de station de base (BSC)/contrôleurs de réseau radio (RNC), ledit identifiant indiquant si les BSC/RNC s'informent ou non auprès de tous les utilisateurs sur les conditions de la session; (2)avant de définir des ressources radio, les BSC/RNC déterminent si l'identifiant envoyé par le réseau principal est valide ou non. Si l'identifiant est valide, les BSC/RNC s'informent si les équipements utilisateurs (UE) reçoivent la session MBMS et déterminent le nombre total des utilisateurs récepteurs en fonction des réponses renvoyées par les UE. Sinon, il est possible de déterminer le nombre total d'utilisateurs récepteurs en partant de l'hypothèse que tous les utilisateurs qui sollicitent le service MBSM souhaitent recevoir la session. Le procédé de l'invention permet de réduire le gaspillage de ressources du réseau radio, de simplifier le processus de signalisation du réseau, d'où économie de réponse UE superflues, économie sensible d'énergie et augmentation du temps de veille des UE.
PCT/CN2005/000582 2004-04-30 2005-04-27 Procede de determination du nombre total d'utilisateur dans un systeme de service de diffusion/multidiffusion (mbms) WO2005107155A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2004100372814A CN100484147C (zh) 2004-04-30 2004-04-30 多媒体广播/组播业务中确定接收用户数目的方法
CN200410037281.4 2004-04-30

Publications (1)

Publication Number Publication Date
WO2005107155A1 true WO2005107155A1 (fr) 2005-11-10

Family

ID=35242015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/000582 WO2005107155A1 (fr) 2004-04-30 2005-04-27 Procede de determination du nombre total d'utilisateur dans un systeme de service de diffusion/multidiffusion (mbms)

Country Status (2)

Country Link
CN (1) CN100484147C (fr)
WO (1) WO2005107155A1 (fr)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100389557C (zh) * 2006-02-07 2008-05-21 华为技术有限公司 多媒体广播多播业务中的用户计数方法
EP1892978B1 (fr) * 2006-08-22 2019-01-02 Mitsubishi Electric R&D Centre Europe B.V. Méthode et appareil pour l'implémentation de transfert de contenu multimédia dans une cellule d'un réseau de télécommunication sans fil
CN101227635B (zh) * 2007-01-15 2012-07-04 上海贝尔股份有限公司 长期演进中多媒体广播/多播业务的听众测量方法及设备
CN101296396B (zh) * 2007-04-24 2010-12-08 中兴通讯股份有限公司 一种获取小区多媒体广播组播业务支持能力的方法
CN101350946A (zh) * 2007-07-19 2009-01-21 华为技术有限公司 一种多播/广播业务负载统计的方法及相关设备
CN101364884A (zh) * 2007-08-10 2009-02-11 华为技术有限公司 发送多媒体广播与组播服务数据包的方法及装置
CN101374271B (zh) * 2007-08-24 2012-02-29 中兴通讯股份有限公司 一种多媒体广播及组播业务计数的方法
JP2010157124A (ja) * 2008-12-27 2010-07-15 Canon Inc データ格納装置、データ格納装置の制御方法、プログラム、及び、記録媒体
CN101931870B (zh) * 2009-06-22 2015-08-19 电信科学技术研究院 一种信息上报方法及装置
GB2491335A (en) * 2011-03-24 2012-12-05 Wireless Tech Solutions Llc A relay node receives broadcast data on a first channel and retransmits the broadcast data on a second channel
CN111556540B (zh) * 2020-05-13 2024-05-17 腾讯科技（深圳）有限公司 Smf实体执行的方法及smf实体、pcf实体执行的方法及pcf实体
CN113676846B (zh) * 2020-05-15 2023-04-11 大唐移动通信设备有限公司 一种传输方式确定方法、装置、设备及存储介质
CN113972963B (zh) * 2020-07-22 2023-06-09 维沃移动通信有限公司 确定目标状态信息的方法和网络设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002076019A1 (fr) * 2001-02-19 2002-09-26 Telefonaktiebolaget Lm Ericsson (Publ) Procede et systeme d'acheminement aleatoire a des hotes multiples
WO2003039068A1 (fr) * 2001-10-29 2003-05-08 Nokia Corporation Procede permettant de fournir des services multidestination et/ou d'emission a des terminaux d'utilisateur
EP1359774A1 (fr) * 2002-05-03 2003-11-05 Samsung Electronics Co., Ltd. Appareil et procédé pour "multimedia broadcast/multicast service" dans un système de communication mobile
EP1401152A2 (fr) * 2002-09-19 2004-03-24 Samsung Electronics Co. Ltd. Procédé de détermination d'un schema de transmission pour un service MBMS dans un système de communication mobile

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002076019A1 (fr) * 2001-02-19 2002-09-26 Telefonaktiebolaget Lm Ericsson (Publ) Procede et systeme d'acheminement aleatoire a des hotes multiples
WO2003039068A1 (fr) * 2001-10-29 2003-05-08 Nokia Corporation Procede permettant de fournir des services multidestination et/ou d'emission a des terminaux d'utilisateur
EP1359774A1 (fr) * 2002-05-03 2003-11-05 Samsung Electronics Co., Ltd. Appareil et procédé pour "multimedia broadcast/multicast service" dans un système de communication mobile
EP1401152A2 (fr) * 2002-09-19 2004-03-24 Samsung Electronics Co. Ltd. Procédé de détermination d'un schema de transmission pour un service MBMS dans un système de communication mobile

Also Published As

Publication number Publication date
CN100484147C (zh) 2009-04-29
CN1691676A (zh) 2005-11-02

Similar Documents

Publication Publication Date Title
WO2005107155A1 (fr) Procede de determination du nombre total d'utilisateur dans un systeme de service de diffusion/multidiffusion (mbms)
US8325641B2 (en) Method and apparatus for service identifying and routing in multimedia broadcast/multicast service system
WO2005101737A1 (fr) Procede de demarrage de session d'un service de multiplexage de programmes de diffusion multimedia
JP4427576B2 (ja) マルチメディアブロードキャスト／マルチキャストサービスにおけるセル情報の変化の通知方法
EP1802049B1 (fr) Procede et systeme permettant de commander une session d'un service de diffusion/multidiffusion multimedia
EP1440537B1 (fr) Support multidiffusion dans des reseaux sans fil a commutation par paquets
US8032147B2 (en) Apparatus and method for supporting mobility of wireless terminal in wireless communication network
JP4576415B2 (ja) 無線通信システムのユーザー端末において動作周波数を選択する方法及び装置
TWI330019B (en) Method and apparatus of acquiring point-to-multipoint mbms service information in a wireless communications system
WO2005069646A1 (fr) Procede d'enregistrement pour service multidestination a diffusion multimedia
WO2006015553A1 (fr) Procede de transmission de service de serveur de diffusion/multi-diffusion multimedia
WO2004017581A1 (fr) Diffusion multimedia et recherche de personne service multi-diffusion
WO2018006279A1 (fr) Procédé, dispositif et système de traitement de service
WO2007012280A1 (fr) Procédé, système et dispositif d'émission et de réception d'un service de diffusion/multidiffusion multimédia
US7277706B2 (en) Provision of service contexts in a communication system
WO2008098497A1 (fr) Système de service de diffusion multimedia et procédé de début de session, procédé de fin de session
WO2005109915A1 (fr) Procede de mise a jour de zone d'acheminement dans mbms
KR20070061132A (ko) Ｍｂｍｓ 제공 시스템 및 그 방법
CN101175252B (zh) 多媒体广播组播服务中建立会话的方法和网络***
WO2004043025A1 (fr) Procede d'etablissement de support d'acces radio (rab) pour un service de multidiffusion et diffusion multimedia (mbms)
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
WO2006076865A1 (fr) Procede de desactivation du service de diffusion multidiffusion multimedias
US20090270026A1 (en) Method of controlling multimedia broadcast and multicast service bearer in mobile
WO2004034655A1 (fr) Procede d'etablissement et de suppression d'un service de multi-diffusion mbms dans des installations reseau sgsn et ggsn
WO2005053331A1 (fr) Procede de mise en oeuvre d'un service de multidiffusion

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase