[go: up one dir, main page]

WO2006122509A1 - Procede de multidiffusion de donnees de trafic fonde sur le reseau mobile - Google Patents

Procede de multidiffusion de donnees de trafic fonde sur le reseau mobile Download PDF

Info

Publication number
WO2006122509A1
WO2006122509A1 PCT/CN2006/001045 CN2006001045W WO2006122509A1 WO 2006122509 A1 WO2006122509 A1 WO 2006122509A1 CN 2006001045 W CN2006001045 W CN 2006001045W WO 2006122509 A1 WO2006122509 A1 WO 2006122509A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
data
cell
multicast
service
Prior art date
Application number
PCT/CN2006/001045
Other languages
English (en)
Chinese (zh)
Inventor
Jian Chen
Jun Hu
Junhai Miao
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 WO2006122509A1 publication Critical patent/WO2006122509A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to the field of mobile network technologies, and in particular to a method for implementing multicast service data based on a mobile network. Background of the invention
  • FIG. 1 is a schematic diagram of the implementation principle of point-to-point transmission.
  • Each user terminal interacts with a radio access network (RAN) and a core network (CN), respectively, to establish a dedicated IP data transmission channel for connection with an external network.
  • the streaming server transmits streaming media service data to the UE through the dedicated Internet Protocol (IP) data transmission channel. That is, each UE and the streaming server establish a dedicated IP data transmission channel for transmitting streaming media service data, and the streaming media server must also send a separate data for each UE.
  • IP Internet Protocol
  • the user's UE passes through the network side, including a General Packet Radio Service (GPRS) Service Support Point (SGSN), a GPRS Gateway Support Node (GGSN), and an IP transmission network.
  • the media server sends a streaming media play request, and the insert-and-drop request can pass the real-time streaming protocol (RTSP, Realtime Streaming). Protocol) or other streaming media real-time interactive protocol to carry, the request contains the program identifier selected by the user, that is, the selected channel, and the network side establishes a dedicated IP data transmission channel between the UE and the streaming media server, and the IP data.
  • RTSP Realtime streaming protocol
  • Protocol Realtime Streaming
  • the streaming server After the transmission channel is established, the streaming server notifies the UE of the received attribute information.
  • the attribute information includes information such as the IP address, port number, rate, and encoding format of the data transmission channel.
  • the streaming media server copies a data corresponding to the program identifier, and sends the data to the UE through the established dedicated IP data transmission channel, and the UE decodes the received data according to the received attribute information.
  • the video information is presented to the user.
  • the foregoing is a method for describing data transmission based on a mobile network by using streaming media service data as an example.
  • the service data transmitted in the mobile network includes but is not limited to streaming media service data, and the transmitted service data may also be a media file.
  • Business data such as Music Television (MTV), Motion Picture Experts Group (MPEG) Audio Layer-3 (MP3) music files, video files, e-books, pictures, electronic newspapers, etc. It can be seen that the existing methods for transmitting service data have the following drawbacks:
  • a dedicated IP data transmission channel needs to be established between the application server and each UE.
  • the application server must be the same regardless of whether the service data received by each UE is the same.
  • Each UE sends a data, so that the same service data is transmitted multiple times, which makes the resource utilization low.
  • the number of users accessing is limited due to network resources on the network side.
  • NodeBs Due to the wide distribution of base stations (NodeBs), not all NodeBs have the conditions to lay fiber or multiple cables, and even if they are laid, the cost of laying is very high. For operators without transmission resources, the price of leased transmission channels It is very high. Generally, an operator only provides several live channels (such as several TV programs). If dozens of users under one NodeB in the RAN receive the same service data, such as watching the same TV channel, under the current implementation scheme. , it needs to be on the IUB interface between the RNC and the NodeB for each UE.
  • BM-SC Broadcast Multicast-Service Center
  • MBMS multimedia broadcast multicast service
  • an object of the present invention is to provide a method for implementing multicast service data based on a mobile network, so that a data source for providing data on the network side only needs to send a data to
  • a method for implementing multicast service data based on a mobile network a multicast proxy module is set on the radio access network RAN, and the UE to receive the service data interacts with the CN to activate the PDP.
  • the method further includes the following steps:
  • a multicast proxy module in the RAN detects an access request from the UE that includes the destination information, and determines that the destination information in the request is the destination information of the data source for providing the data service service in advance, and then performs the connection.
  • the control device obtains the service data content identifier to be received by the UE that initiates the access request, and establishes a control connection with the UE; the UE acquires the receiving attribute information from the establishment process of the control connection;
  • the root After the multicast proxy module in the RAN receives the start play request from the UE, the root And sending, according to the obtained service data content identifier, the service data corresponding to the service data content identifier from the data source to the UE;
  • the UE receives the service data in the established transmission channel according to the received receiving attribute information.
  • the multicast proxy module is composed of a control proxy CA and a data proxy DA; the operation of step a is performed by a CA in the multicast proxy module;
  • the CA After the CA establishes a control connection with the UE, the CA notifies the DA to start the operation of transmitting the service data; after receiving the notification from the CA, the DA receives the service data corresponding to the service data content identifier from the data source. Issued to the UE.
  • the established transmission channel is a dedicated data transmission channel established for each UE between the transport layer RAN and the UE;
  • the process for the DA to deliver the service data corresponding to the service data content identifier from the data source to the UE is: when the DA receives the notification from the CA for transmitting the service data, the UE starts to send the request to the UE.
  • the service data is transmitted on the downlink dedicated data transmission channel.
  • the established transmission channel is a pre-established shared data transmission channel for each service data content identifier for each cell in the transport layer RAN;
  • the process of sending the service data corresponding to the service data content identifier from the data source to the UE is: when the DA receives the notification from the CA to send the service data, the current UE that initiates the play request is currently located. The number of users receiving the service data requested by the UE in the cell, and determining whether the number of users changes from zero to non-zero. If yes, the DA starts to send the service data required by the UE on the downlink public transmission channel, otherwise DA does not process; or,
  • the SACU in the RAN Counting, by the SACU in the RAN, the number of users that receive the service data requested by the UE in the current cell of the UE in which the play request is initiated, and determining whether the number of users is changed from zero. It is non-zero. If yes, the DA is sent a notification to start transmitting data. After receiving the notification, the DA starts to send the service data required by the UE on the downlink public transmission channel, otherwise the SACU in the RAN does not process.
  • the establishing process of the pre-established shared data transmission channel includes the following steps:
  • the CA in the multicast proxy module indicates that the SACU in the RA performs reconfiguration, and the reconfiguration indication includes the service data content identifier selected by the UE.
  • the SACU After receiving the indication in step 01), the SACU disconnects the established downlink IP data channel, performs reconfiguration on itself, and then obtains the service data content identifier from the reconfiguration indication, according to the service data content identifier according to the existing Recalculating the wireless network identifier of the UE; and then transmitting information to the UE that changes the UTRAN, where the information includes the recalculated wireless network identifier;
  • the UE After receiving the change information in step 02), the UE updates its own wireless network identifier, and then returns the change confirmation information to the SACU;
  • the SACU sends a reconfiguration command to the UE; after receiving the command, the UE returns a reconfiguration command response to the SACU after performing reconfiguration itself;
  • the SACU releases the channel resources occupied by the current UE.
  • the SACU is RRC
  • the wireless network identifier is a URNTI and a CRNTI
  • the reconfiguration indication and the reconfiguration command are a D2F reconfiguration indication and a D2F reconfiguration command, respectively
  • the channel resource occupied by the current UE is a dedicated channel resource.
  • the UE interacts with the CN, and the method for activating the PDP includes at least establishing a radio resource control connection. If the network is pre-configured to encrypt the air interface data, the method further includes:
  • the "multicast service request" is included.
  • the RAN detects the cause value of the RRC connection request as "Multicast Service Request”
  • the air interface data of the UE is not encrypted and directly transmitted.
  • the manner in which the DA in the multicast proxy module receives the service data from the data source is:
  • the multicast proxy module directly receives the service data from the data source, or
  • the multicast proxy module receives the service data from the data source via a network other than the CN, or
  • a channel dedicated to transmitting multicast service data is established, and the multicast proxy module receives the service data from the data source via the dedicated transmission channel in the CN.
  • the DA in the multicast proxy module receives the service data from the data source as unicast data or multicast data. If the unicast data is received, the unicast data is converted into multicast data, and then executed. Follow-up actions.
  • the method further comprises:
  • the UE initiates a release request, where the request includes the destination information; the destination information is a destination IP address, or a destination IP address and a port number;
  • the multicast proxy module in the RAN monitors the release request containing the destination information from the UE, and determines that the destination information in the request is the destination information of the data source for providing the data service service, and intercepts the request. , performing a resource release operation; after that, returning a release response to the UE.
  • the multicast proxy module is composed of a CA and a DA;
  • the resource release operation includes the following steps:
  • the CA notifies the DA to stop transmitting service data to the downlink dedicated transmission channel of the UE, and the CA releases the control connection between the network side and the UE side and the radio resource control; the DA receives After the above notification, the service data is stopped from being sent to the downlink dedicated transmission channel of the UE.
  • the multicast proxy module is composed of a CA and a DA;
  • the release request initiated by the UE further includes a service data content identifier.
  • the resource release operation includes the following steps:
  • the CA controls the network side to perform reconfiguration, and notifies the DA to stop transmitting service data on the shared data transmission channel, and the CA releases the control connection occupied by the UE side and the radio resource control; after receiving the foregoing notification, the DA receives the current information in the cell.
  • the number of users receiving the content of the service data is decreased by one, and then it is determined whether the number of users receiving the service data is changed from non-zero to zero. If yes, the DA stops sending service data to the cell, otherwise the DA does not process; or
  • the resource release operation includes the following steps:
  • the CA controls the network side to perform reconfiguration.
  • the SACU in the RAN decrements the number of users currently receiving the service data content in the cell by one, and then determines whether the number of users receiving the service data is changed from non-zero to zero. Then, the DA is sent a notification to stop sending data. After receiving the notification, the DA stops transmitting the service data required by the UE on the downlink public transmission channel, otherwise the SACU in the RAN does not process.
  • the operation of the CA to control the reconfiguration of the network includes the following steps: the CA in the multicast proxy module instructs the SACU to perform reconfiguration; after receiving the reconfiguration indication, the SACU performs reconfiguration on itself, and then proceeds to the UE. Send a reconfiguration command;
  • the UE reconfigures itself according to the received command.
  • the SACU is RRC; and the reconfiguration indication and reconfiguration commands are F2D re-matching instructions and F2D reconfiguration commands, respectively.
  • control connection is a service control connection and a TCP connection
  • service control connection may be a streaming media control connection, including but not limited to RTSP
  • service control connection The connection may also be a control connection for file transfer, including but not limited to a point-to-multipoint File Delivery over Unidirectional Transport (FLUTE).
  • FLUTE point-to-multipoint File Delivery over Unidirectional Transport
  • the method further includes the process of the UE performing cross-cell update.
  • the cell update process includes the following steps: i) After receiving the cell update request from the UE that includes the target cell identity information, the SACU determines whether the common channel data carried by the target cell and the source cell is the same. If the same, directly perform step iii. ), if not the same, then perform step ii);
  • the SACU recalculates the radio network identifier of the UE, and then sends information to the UE that changes the UTRAN, where the information includes the recalculated radio network identifier, and the UE returns the change UTRAN to the SACU after the update is completed according to the received information.
  • the DA adds one to the number of users corresponding to the service data content identifier received by the UE in the target cell; and then determines whether the number of users in the transmission channel corresponding to the service data content identifier received by the UE is changed from zero to non-zero. Zero, if yes, start to send data to the public transmission channel carrying the service data in the target cell, and then perform step V), otherwise, directly execute step V);
  • the DA reduces the number of users corresponding to the service data content identifier received by the UE in the source cell by one; and then determines whether the number of users in the data transmission channel corresponding to the service data content identifier received by the UE in the source cell is non- Zero, if yes, directly perform step vi), otherwise, the DA stops sending service data in the data transmission channel corresponding to the service data content identifier received by the UE in the source cell, and then performs step vi);
  • DA notifies the CA that the operation is completed, and the CA returns the operation completion response letter to the SACU. After receiving the response, the SACU returns a cell update response to the UE.
  • the method further includes the process of the UE performing cross-cell update.
  • the cell update process includes the following steps: i.) After receiving the cell update request from the UE, including the target cell identity information, the SACU determines whether the common channel data carried by the target cell and the source cell is the same. Iii, ), if not, perform step ii, );
  • the SACU recalculates the radio network identifier of the UE, and then sends information to the UE that changes the UTRAN, where the information includes the recalculated radio network identifier, and the UE returns the change to the SACU after the update is completed according to the received information.
  • the UTRAN acknowledges the information; iii, the SACU increments the number of users corresponding to the service data content identifier received by the UE in the target cell, and then determines whether the number of users in the transmission channel corresponding to the service data content identifier received by the UE is To change from zero to non-zero, if yes, execute step iv'), if no, "J, then directly perform step ⁇ ');
  • the SACU notifies the DA in the multicast proxy module to start transmitting data, and after receiving the notification, the DA starts to send data to the public transmission channel carrying the service data in the target cell, and returns a response message for performing the operation to the SACU, and then Then perform step v, );
  • the SACU reduces the number of users corresponding to the service data content identifier received by the UE in the source cell by one, and then determines whether the number of users in the data transmission channel corresponding to the service data content identifier received by the UE in the source cell is Non-zero, if yes, no processing is performed. Otherwise, the DA in the multicast proxy module is notified to stop transmitting data. After receiving the notification, the DA stops the data corresponding to the service data content identifier received by the UE in the source cell. Transmitting service data in the transmission channel, and returning the operation completion response information to the SACU;
  • the SACU returns a cell update response to the UE.
  • the SACU is an RC
  • the Line network identifiers are UR TI and CR TI.
  • the DA in the multicast proxy module is composed of a single-level processing unit, or is composed of two or more processing units;
  • the LDAU When the DA in the multicast proxy module is composed of two levels of processing units, if the low-level multicast data proxy unit LDAU receives the play notification from the CA, the LDAU will receive the service data content in the current cell and the UE that initiated the request. And identifying the number of corresponding users plus one, and then determining whether the number of users corresponding to the service data content identifier received by the UE that initiated the request in the current cell is changed from zero to non-zero, and if yes, to the high-level multicast data proxy unit.
  • the HDAU sends an access request, and the HDAU starts to send data to the public transmission channel that carries the service data, otherwise the LDAU does not process;
  • the LDAU decrements the number of users corresponding to the service data content identifier received by the UE that initiated the request in the current cell, and then determines the service received by the UE in the current cell and the requesting UE. Whether the number of corresponding users of the data content identifier changes from non-zero to zero. If yes, the LDAU notifies the HDAU to stop transmitting the service data in the data transmission channel corresponding to the service data content identifier received by the UE in the cell, otherwise, Do the processing.
  • the multicast proxy module uses the hardware-based multicast function in the RNC to forward the service data from the high-level multicast data.
  • the proxy unit sends the low-level multicast data proxy unit; the hardware is a hardware platform of the IP switching function, or an ATM switching platform or a multi-service platform.
  • the method further includes: setting, in the NodeB, a multicast data distribution agent MDDA module having a service data distribution function, the MDDA module receiving The service data from the RC is copied and distributed to each cell as needed.
  • the multicast proxy module is set in the RNC in the RAN, or is set in the NodeB in the RAN; if it is a CDMA network, the multicast proxy module is set on the CBSC in the RAN. Or set on the CBTS in the RAN; if it is a GSM network, the multicast proxy module is set on the GBSC in the RAN or on the GBTS in the RAN.
  • the destination information is a destination IP address, or a destination IP address and a port number; and the receiving attribute information in step b includes at least an IP address, a port number, a rate, and a data corresponding to the content identifier of the service data to be received. Encoding format.
  • the data source includes but is not limited to a streaming media server
  • the service data includes but is not limited to streaming media service data
  • the key of the present invention is that the multicast proxy module in the RAN monitors an access request from the UE that includes the destination information, and determines that the destination information in the request is a pre-specified destination information for providing a data source for the data service.
  • the service data content identifier to be received by the UE that initiates the access request is obtained, and a control connection with the UE is established; the UE obtains the receiving attribute information from the establishment process of the control connection;
  • the proxy module After receiving the start play request from the UE, the proxy module sends the service data corresponding to the service data content identifier from the data source to the UE according to the acquired service data content identifier; ⁇ according to the received receiving attribute information Received service data in the established transmission channel.
  • QoS Quality of Service
  • the RAN can obtain the current service data rate due to the existence of the multicast proxy module, so that the related entity in the RA assigns or reconfigures the bearer channel of the corresponding rate according to the current rate of the service data, for example, when a program source When the rate is 50Kbits/sec, you only need to give It is sufficient for the user to allocate a 64K transmission channel, so that limited air interface resources can be applied more efficiently and scientifically.
  • the data source is a streaming media server
  • the number of concurrently on-demand or live broadcasts by a high-performance streaming media server is about 1000, and the streaming media server can support simultaneous online after using the method of the present invention.
  • the live broadcast users can reach tens of thousands, and the resources on the core network side and the application layer are also greatly saved.
  • the method of the present invention can be well combined with a mobile network, such as combining with the RAN in the current R99, R4, and R5, which has little change to the existing network, and provides a service that can greatly reduce the operation of the operator. Cost, especially the way to reduce the transmission costs on the air interface and IUB interface. At the same time, operators can use this technology to reduce the cost of watching live streaming media from mobile phones, so that operators can handle very favorable positions in the competition.
  • the multicast proxy module that receives the data source service data can receive the service data by using the bypass technology of the multicast data, so that the multicast service data is carried by the dedicated channel, which greatly improves the QoS of the multicast data.
  • Figure 1 shows a schematic diagram of the implementation principle of point-to-point transmission
  • FIG. 2a is a schematic diagram showing an implementation principle of implementing multicast by applying the present invention
  • FIG. 2b is a schematic diagram showing another implementation principle of implementing multicast by using the present invention
  • FIG. 3a is a diagram showing a protocol hierarchy when a CA is acting as a proxy for a streaming media server;
  • Figure 3b shows a protocol hierarchy diagram of the DA when the CA acts as a proxy for the streaming media server
  • Figure 4 is a flowchart showing the overall implementation of establishing service data multicast in an embodiment
  • FIG. 5 is a flowchart showing an implementation of configuring a shared data transmission channel in a transport layer. The implementation process is described by taking a FACH channel as an example.
  • FIG. 6a is a schematic diagram of relationship between entities of an existing network side air interface
  • 6b is a schematic diagram of relationship between entities of a network side air interface when a UE that initiates an access request according to the present invention uses a dedicated channel;
  • 6c is a schematic diagram of relationship between entities of a network side air interface when a UE that initiates an access request according to the present invention uses a shared channel;
  • FIG. 7 is a schematic diagram showing an implementation manner of a service data of a DA receiving data source in a multicast proxy module in the RAN;
  • FIG. 8 is a flowchart showing an overall implementation of releasing service data multicast in an embodiment
  • FIG. 9 is a flowchart showing an implementation of reconfiguring a transport layer when a shared multicast transmission channel is released;
  • Figure 10 is a schematic flow chart of cell update
  • Figure 11 is a flow chart showing the process of switching when performing RNC across RNC
  • Figure 12 shows the implementation principle of the two-stage DA in the multicast proxy module.
  • Figure 13 shows the implementation principle of setting MDDA in the NodeB. Mode for carrying out the invention
  • the basic implementation of the present invention is that when the service data is transmitted between the application server and the UE, the original point-to-point transmission mode is changed to a point-to-multipoint transmission mode, that is, multicast of the service data is implemented.
  • FIG. 2a is a schematic diagram showing an implementation principle of implementing multicast according to the present invention.
  • a multicast proxy module is set in the RAN, and each UE interacts with the RAN and the CN to activate a Packet Data Protocol (PDP).
  • PDP Packet Data Protocol
  • the data is sent by the router to the multicast proxy module in the RAN, and the existing transmission mode is still used for transmission between the UE and the RAN, that is, a dedicated data transmission channel is established between each UE and the RAN.
  • the multicast proxy module in the RAN sends the received service data from the data source to each UE. In this way, for the core network part of the network side, there is only one channel between the data source and the RAN, which greatly saves resources of the core network part, improves resource utilization, and reduces cost.
  • FIG. 2b is a schematic diagram showing another implementation principle of implementing multicast according to the present invention.
  • the implementation manner of the data source to the RAN is the same as that shown in FIG. 2a.
  • the multicast proxy module establishes only one data transmission channel for each service data content identifier in each cell, so that All UEs that receive the same service data content in the same cell need only one channel, thereby further saving network resources of the network side access network part, improving resource utilization, and reducing cost.
  • the data source of the present invention includes, but is not limited to, a streaming media server, and the service data includes but is not limited to streaming media service data, and may also be media file service data such as MTV, MP3 music files, e-books, pictures, and electronic newspapers. .
  • a multicast proxy module needs to be set up in the RAN, and the multicast proxy module is composed of a control proxy (CA) entity and a data proxy (DA) entity, and the CA entity and the DA entity may be the same physical entity. , can also be different physical entities.
  • CA control proxy
  • DA data proxy
  • the CA mainly handles the service control connection and the Transmission Control Protocol (TCP) connection with the UE.
  • the service control connection may be a streaming control connection, including but not limited to Real Time Streaming Protocol (RTSP); the service control connection may also be a control connection of file transfer, including but not limited to point-to-multipoint One-way file transfer protocol (FLUTE, File Delivery over Unidirectional Transport).
  • RTSP Real Time Streaming Protocol
  • FLUTE point-to-multipoint One-way file transfer protocol
  • the DA mainly processes specific multicast service data distribution processing, and receives service data from the data source in the CA or Signal and Control Unit (SACU). Under the control, the data is sent to the UE through the RAN established traffic channel.
  • SACU Signal and Control Unit
  • WCDMA Wideband Code Division Multiple Access
  • J is a Radio Resource Control (RRC) entity.
  • RRC Radio Resource Control
  • the following is an example of a proxy streaming media server in the RAN.
  • the CA in the MA proxies the TCP/IP protocol layer and the RTSP protocol layer of the streaming media server, and the DA proxyes the real-time media data of the streaming media server.
  • Figure 3a and Figure 3b show the protocol hierarchy diagram when CA and DA are acting as proxy for streaming media server respectively.
  • the protocol layers of the CA are: a physical layer (PHY), which may be a DPCH or a second common control physical channel (SCCPCH); a medium access control (MAC) layer, the MAC layer There is a dedicated channel (DCH) or a forward access channel (FACH); a radio link control (RLC) layer, which may be an acknowledgement (AM) mode or a non-acknowledgement (UM) mode; packet data convergence Protocol (PDCP) layer; IP layer; TCP layer; and streaming media control layer, such as RTSP or Multimedia Information Service (MMS) protocol.
  • PHY physical layer
  • SCCPCH second common control physical channel
  • MAC medium access control
  • DCH dedicated channel
  • FACH forward access channel
  • RLC radio link control
  • AM acknowledgement
  • UM non-acknowledgement
  • PDCP packet data convergence Protocol
  • IP layer IP layer
  • TCP layer TCP layer
  • streaming media control layer such as RTSP or Multimedia Information Service (MMS) protocol.
  • MMS Multimedia
  • the protocol layer of the DA is: PHY, the PHY may be DPCH or SCCPCH; MAC layer, the MAC layer may be DCH or FACH; RLC layer, the layer may be in AM mode or UM Mode; PDCP layer; IP layer; UDP layer; RTP layer; A/V Stream, such as AMR, H.263, H.264, MPEG4, etc.
  • DA implements the distribution function of streaming media data and processes the data accordingly. These processes include: If the IP address is a unicast address, it is converted into a multicast address, and the UDP port number is changed. The checksum of the UDP packet is recalculated and then sent to the UE by the PDCP on the dedicated or common channel.
  • PDCP and the following protocol layers are the protocol layers inherent to the RAN.
  • FIG. 4 is a flow chart showing an overall implementation of establishing service data multicast according to an embodiment.
  • an MA composed of CA and DA has been set in the RAN.
  • the "RAN/Multicast Proxy Module” is applied in the figure to represent the MA that has been set in the RAN.
  • Step 401 The UE interacts with the RAN in the idle mode, and establishes an RRC connection with the R C entity in the RAN.
  • Step 402 The UE interacts with the CN to activate the PDP.
  • Step 403 The control connection is established between the UE and the CA in the MA. Because the streaming media service data is taken as an example, the control connection includes a TCP/IP connection and an RTSP control connection, where TCP The /IP connection is used to carry the RTSP protocol or other streaming real-time interactive protocols.
  • the process of establishing a control connection is as follows: The UE initiates an access request, and the request includes the destination information. After the CA in the multicast proxy module in the RAN detects the access request from the UE, determines whether the destination IP address in the request is The pre-specified IP address of the data source used to provide the data service service. If yes, the access control is performed to establish a control connection with the UE. Otherwise, the CA in the multicast proxy module does not process.
  • the above destination information is the destination IP address, or the destination IP address and port number.
  • the UE Since the above control connection includes a TCP/IP connection and a control connection of the RTSP, after the TCP/IP connection is established, the UE interacts with the CA in the multicast proxy module in the RAN through the RTSP protocol to obtain the receiving service.
  • the receiving attribute information of the data includes at least a service data content identifier to be received, an IP address, a port number, a video and an audio encoding format of the multicast data carrying the service content. Since it is required by the standard RTSP protocol, it will not be described in detail here.
  • Steps 404 - 405 the UE initiates an RTSP play request (PLAY), and the request is mainly used to trigger the service data to start playing.
  • the CA in the RAN After detecting the play request, the CA in the RAN returns a play request confirmation message to the UE, and then sends a notification to the DA. The message, to notify the DA to start the operation of sending the streaming media service data.
  • DA is used to receive directly from the data source Business data, such as streaming media business data, is released.
  • Step 406 After receiving the message, the UE receives the service data in the established data transmission channel.
  • the data source only needs to send one data to the DA in the RAN, thereby greatly saving resources of the network side core network part.
  • the processing speed of the process is greatly accelerated, so that the user obviously feels the speed of the connection speed and improves the service quality.
  • the established data transmission channel may be a dedicated data transmission channel established for each UE, that is, a dedicated data transmission channel, such as a DCH channel, is established between the RAN and each UE. It is also possible to establish only one data transmission channel for each service data content identifier in each cell, that is, each service data in the same cell only establishes a common data transmission channel, such as a FACH channel, so that the same cell can be A user receiving a certain service receives service data on the same channel.
  • a dedicated data transmission channel such as a DCH channel
  • the mentioned established data transmission channel is a dedicated channel established for each UE separately, after the DA receives the notification from the CA to start the operation of transmitting the streaming media service data, the DA starts to initiate the playback request.
  • the downlink dedicated transmission channel where the UE is located such as the DCH, sends service data.
  • the process of establishing the downlink dedicated transmission channel DCH is exactly the same as that of the prior art, and the description thereof will not be repeated here.
  • the shared multicast transmission channel is pre-configured when the cell is established, but only after the configuration is completed. No service data is sent, and no service data is used, which does not occupy the resources of the air interface. It only occupies the code resources, and the service data is sent when the user requests to receive. Further, in the case that multiple UEs use the shared transmission channel in the same cell, when the DA receives the notification from the CA to start the operation of transmitting the streaming media service data, the DA counts the The number of users who receive the service data requested by the UE in the current cell of the UE in which the play request is initiated.
  • the DA starts to transmit the UE in the downlink common transmission channel, such as FACH.
  • Required service data if the number of users is not changed from zero to non-zero, the operation of starting to send the service data is not performed, because the DA has already sent the service data for the cell, that is, the DA only performs statistical operations at this time. .
  • the number of users accessing a certain service data in each cell can also be counted by the RRC in the RAN, and the RRC directly informs the DA to start the bearer of the service according to the number of users accessing the service data in the cell.
  • the common channel transmits traffic, that is, when the number of users changes from zero to non-zero, the RRC informs the DA to initiate transmission of traffic to the common channel carrying the service of the cell.
  • the UE initiates an RRC connection request when interacting with the RAN, and includes an extended cause value (Multicast Service Request),
  • the RRC performs special processing on the encryption process of the UE, that is, the "encryption algorithm" in the RRC encryption command sent to the UE is set to Algorithm zero, that is, does not activate the air interface (UU interface) encryption function.
  • the reason value in the user's initiation of the RRC connection request has been specified in the 3rd Generation Partnership Project (3GPP) 25331, and the provision also defines the reason value of the sparel to sparel2 system reservation.
  • Any one of the spares 1 to spare 12 may be used to carry a "multicast service request", and in this application, sparelO is defined as a "multicast service request”.
  • the shared data transmission channel is pre-configured at the transport layer.
  • the following describes the process of configuring the transport layer by taking FACH as an example.
  • Figure 5 is a flow chart showing the implementation of configuring a shared data transmission channel at the transport layer. This implementation The flow uses the FACH channel as an example for description.
  • the UE selects the FACH rule: when the UE is in the idle mode, the UE selects according to the number of SCCPCHs broadcasted in the system message 5 and its own International Mobile Subscriber Identity (IMSI).
  • the selection mode is that the IMSI takes the SCCPCH number. If the modulo is equal to the number, the FACH configured in the SCCPCH is selected; when the UE is in the connected mode, the network side allocates to the UE according to the number of SCCPCHs broadcasted in the system message 6, and the selection mode is a universal mobile communication system ( UMTS) Radio Access Network (UTRAN)
  • the Radio Network Temporary Identifier (UTNTI) takes the modulus of the SCCPCH number. If the modulus is equal to the number, the FACH configured in the SCCPCH is selected. This is the standard protocol for selecting the FACH channel. More description.
  • the RAN Before reconfiguration, the RAN needs to re-allocate the URNTI of the mobile phone according to the service data content identification number selected by the UE on the multicast proxy module in the RAN, and notify the UE to change the URNTI through the UTRAN information change message of the WCDMA standard protocol.
  • the process is shown in Figure 5.
  • Step 501 The CA in the multicast proxy module in the RAN indicates that the RRC is configured in the FACH channel mode. Because the existing network usually uses the DCH channel mode to transmit service data, the RRC is configured to be in the FACH channel mode, that is, Instructing the RC to reconfigure the DCH channel mode to the FACH channel mode, the configuration indication is generally abbreviated as D2F (DCH to FACH) reconfiguration, and the configuration indication includes the service data content identifier selected by the UE.
  • D2F DCH to FACH
  • Step 502 After receiving the foregoing indication, the RRC disconnects the established downlink IP data channel, performs reconfiguration on itself, and then obtains the service data content identifier from the D2F reconfiguration indication, and recalculates the IJE according to the service data content identifier. Wireless network identity.
  • the specific calculation method is the same as the prior art.
  • the above wireless network identifier includes URNTI. And cell radio network temporary identification (CRNTI).
  • Step 503 The RRC sends, to the UE, information that changes the UTRAN, where the information includes the recalculated URNTI and CR TL.
  • Step 504 After receiving the change information in step 503, the UE changes its URNTI and CR TI to the received URNTI and CR TI. After the change is completed, the UTRAN confirmation message is returned to the RRC.
  • Steps 505 ⁇ 506 the RRC sends a D2F reconfiguration command to the UE. After receiving the command, the UE performs reconfiguration on itself, and then the UE returns a D2F reconfiguration command response to the R C.
  • Step 507 The R C releases the dedicated channel resource currently occupied by the UE, and returns a response of the D2F reconfiguration indication to the CA in the multicast proxy module.
  • Figure 6 & ⁇ Figure 6c shows the relationship between entities on the network side air interface.
  • Figure 6a is a schematic diagram of the relationship between the entities of the existing network side air interface
  • Figure 6b is a schematic diagram of the relationship between the entities of the network side air interface when the UE that initiates the access request using the dedicated data transmission channel of the present invention uses the dedicated data transmission channel
  • Figure 6c A schematic diagram of the relationship between the entities of the network side air interface when the UE that initiates the access request by using the shared data transmission channel receives the service data.
  • a broken line (-%) indicates uplink data
  • a solid line (1) indicates downlink data
  • a dotted line (_._._) indicates a control message.
  • each UE has a Medium Access Control Dedicated (MACD) entity and five Radio Link Control Entities (RCCs), where RLC1 to RLC4 are signaling RLCs, and RLC5 is a service RLC. .
  • RLCl and RLC5 are non-acknowledgement (UM) modes, and RLC2, RLC3, and RLC4 are acknowledgement (AM) modes.
  • RLC1 ⁇ 4 are both used to carry RRC messages.
  • RLC5 is used to carry application layer control messages.
  • the to-be-received service data of each UE is transmitted on the respective dedicated DCHs through the respective RLCs 5, and the uplink data transmitted by the UEs is also transmitted to the network side via the DCH.
  • each UE has one MACD entity and five RLCs, where RLC1 to RLC4 are signaling RLCs and RLC5 is a service RLC.
  • RLC1 and RLC5 are in UM mode
  • RLC2, RLC3, and RLC4 are in AM mode
  • RLC1 ⁇ 4 are used to carry R C messages.
  • RLC5 is used to carry application layer control messages. Since the service data is transmitted for each UE by using the existing dedicated data transmission channel in this embodiment, the DA receives the received data from the CA after receiving the notification from the CA to start the transmission of the data.
  • the service data of the source is transmitted to the designated UE, and the service data is respectively mapped to the dedicated DCH channel for transmission by the RLC 5 of each UE, and the uplink data transmitted by the UE is also transmitted to the network side through the DCH.
  • the above DA is composed of an entity having a distribution function, and each service data, that is, each streaming television program provided by the streaming server, corresponds to an entity having a distribution function. That is, the DA needs to copy one service data for each UE. Since each UE in the transport layer corresponds to one data transmission channel, it is not necessary to count the number of received users of each service data.
  • RLC1 to RLC4 are signaling RLCs
  • RLC5 is a service RLC.
  • RLC1 and RLC5 are in UM mode
  • RLC2, RLC3, and RLC4 are in AM mode
  • RLC1 - 4 are used to carry RC messages.
  • RLC5 is used to carry application layer control messages.
  • the CA in the multicast proxy module controls each UE in the RRC module to disconnect the downlink IP data channel, control the RRC module to perform D2F reconfiguration, and then notify the DA to enable the DA to start performing operations.
  • the DA in the multicast proxy module in this embodiment is used to carry the downlink service data flow and the number of statistically received users, and the received service data from the data source is sent through the shared FACH channel.
  • the next The transmitted service data is transmitted on the FACH channel shared by multiple UEs after being mapped by the Medium Access Control Common (MACC).
  • the uplink data transmitted by the UE is transmitted to the network side through a random access channel (RACH, Random Access Channel).
  • the above DA is composed of a radio link control entity (RLC5') shared by a plurality of UEs in the UM mode and a plurality of access control dedicated multicast (MACDm, MACD Multicast) functional entities, and each service data identifier is each streaming television.
  • the programs correspond to one RLC5, and one MACDm. In this way, it is possible to establish only one transmission channel for each service data in each cell, that is, for each program. That is, the DA needs to replicate one service data for each cell for each service data.
  • the RLC5 in the DA is used to implement access control.
  • the MACDm is used to count the number of users in the cell corresponding to the service data content identifiers in each cell and to start sending service data. If the UE that initiated the play request is currently located, The data transmission channel corresponding to the service data content identifier required by the UE already exists in the cell, and the MACDm no longer starts sending service data for the cell, and only counts the number of users; if the UE that initiated the play request is not in the current cell, If there is service data corresponding to the service data content identifier required by the UE, the MACDm sends the service data to the cell, and counts the number of users.
  • the transmission of the service data is started.
  • the release request is sent by the RACH, and the DA in the multicast proxy module decrements the number of users currently receiving the service data content in the cell by one, and determines whether the number of users receiving the service data is non-zero. If it is, it indicates that no user currently receives the service data in the cell.
  • the DA in the multicast proxy module stops sending service data to the cell, and notifies the CA to release the resources occupied by the UE; otherwise The DA in the multicast proxy module only informs the CA to release the resources occupied by the UE.
  • the number of users accessing a certain service data per cell can also be used by the RAN.
  • the RRC performs statistics, and the RRC directly informs the DA to start or stop sending services to the common channel carrying the service in the cell according to the number of users accessing the service data in the cell, that is, when the number of users changes from zero to non-zero,
  • the RC notifies the DA to initiate transmission of traffic to the common channel carrying the service in the cell.
  • the RRC notifies the DA to stop transmitting traffic to the common channel carrying the service of the cell.
  • one implementation manner is: establishing a data transmission channel for each UE at the transport layer;
  • the method is: establishing, at the transport layer, a data transmission channel for each service data content identifier, that is, each program in each cell.
  • the main function of the DA in the multicast proxy module is to receive the service data from the data source and deliver the service data.
  • the DA in the multicast proxy module in the RAN it can receive the service data of the data source in multiple ways.
  • Figure 7 is a schematic diagram showing the implementation of the service data of the DA receiving data source in the multicast proxy module in the RAN.
  • the DA in the multicast proxy module can directly receive the service data from the data source, as shown by the thin solid line in FIG. 7; the network data from the data source can also be received through the network other than the CN, that is, the bypass technology is received.
  • the service data from the data source is shown by the thick solid line in Figure 7; the routing function in the CN can also be used to pre-establish a channel dedicated to transmitting multicast service data, and the DA in the multicast proxy module passes through the CN.
  • the dedicated data transmission channel receives the service data from the data source, such as the GGSN and the SGSN in the CN, and receives the service data from the data source, as indicated by the chain line in FIG.
  • the DA in the multicast proxy module in the RAN since it has the protocol layer as shown in FIG. 3b, the DA can receive both unicast data and multicast data, if it receives unicast data. After the unicast data address is converted into a multicast data address, subsequent distribution processing is performed.
  • FIG. 8 is a flowchart showing an overall implementation of a multicast transmission channel for releasing service data according to an embodiment. This embodiment is still described by taking an MA proxy streaming media server as an example.
  • Step 801 The UE initiates a release request, where the request includes the destination information.
  • the destination information is a destination IP address, or a destination IP address and a port number.
  • Step 802 After the CA in the multicast proxy module in the RAN monitors the release request from the UE, it determines whether the destination information in the request is the destination information of the data source for providing the data service monthly service. If yes, go to step 803. Otherwise, the CA in the multicast proxy module does not process.
  • Step 803 The CA in the multicast proxy module performs a release operation, and then returns a release response to the UE.
  • the release operation performed by the CA described in the foregoing step 803 is: the CA notifies the DA to stop sending service data to the downlink dedicated transmission channel of the UE, and releases the network side.
  • the control connection with the UE side and the radio resource control release the downlink data transmission channel dedicated to the UE.
  • the control connection is a streaming media control connection and a TCP connection.
  • the streaming media control connection is an RTSP protocol.
  • the process of specifically releasing the channel is the same as the prior art and will not be described in detail herein.
  • the DA in the MA stops transmitting the service data to the downlink dedicated transmission channel of the UE. Since a data transmission channel is established for each UE, it is not necessary to count the number of users received.
  • the release request described in the foregoing step 801 further includes a service data content identifier;
  • the release operation performed by the CA is as follows:
  • the CA controls the network side to perform reconfiguration.
  • the control connection is a streaming control connection and
  • the streaming control connection is an RTSP protocol. This is because the public data transmission channel is pre-configured. When there is a UE requesting to receive data, data is transmitted on the transmission channel. When no UE receives data, the data is not transmitted on the transmission channel. Therefore, When receiving the release request from the UE, it is only necessary to release the resources occupied by the UE.
  • the CA controls the network side to perform reconfiguration, and notifies the DA to stop transmitting the service data on the shared data transmission channel.
  • the DA receives the current information in the cell.
  • the number of users receiving the content of the service data is decreased by one, and it is determined whether the number of users receiving the service data is changed from non-zero to zero. If yes, it indicates that no user currently receives the service data in the cell.
  • the multicast agent The DA in the module stops sending service data to the cell. Otherwise, the DA in the multicast proxy module does not stop sending service data, that is, only the number of users is counted.
  • the RRC in the RAN decrements the number of users currently receiving the service data content in the cell by one, and then determines the user who receives the service data. Whether the number is changed from non-zero to zero. If yes, the DA is notified to stop transmitting the number ,. After receiving the notification, the DA stops transmitting the service data required by the UE on the downlink public transmission channel, otherwise the RAN is The RRC is no longer processed, and the DA does not stop sending service data.
  • Figure 9 shows an implementation flow diagram for reconfiguring the transport layer when the shared multicast transport channel is released.
  • Step 901 The CA in the multicast proxy module indicates that the RRC is configured as a DCH channel mode. Since the current mode is the FACH channel mode, the RRC is configured to be in the DCH channel mode, that is, the RRC is reconfigured to the DCH channel by the current FACH channel mode. Mode, which is usually abbreviated as F2D (FACH to DCH) reconfiguration.
  • Step 902 After receiving the F2D reconfiguration indication, the RRC reconfigures itself, and then configures itself into the DCH mode. After that, the RRC sends an F2D reconfiguration command to the UE. In step 903, after receiving the command, the UE also performs the weighting on itself. Configure, you will configure itself to DCH mode, and then return to the RRC to return the F2D reconfiguration command response.
  • F2D FACH to DCH
  • Step 904 The RRC establishes a DCH channel to release the FACH channel, and the RLC5 entity for carrying the IP data channel in the RAN replies to receive the downlink data from the CN, even if the disconnected downlink IP data channel returns to normal, and is sent to the multicast proxy module.
  • the CA replies to the F2D reconfiguration indication response.
  • the process of cell update is consistent with the processing of the prior art, and is not detailed here. Description: The following focuses on the process of performing cell update when there is one transmission channel for each service content identifier, that is, the program identifier, in each cell in the transport layer.
  • Figure 10 shows the flow chart of the cell update.
  • the cell in which the UE is located is referred to as a source cell
  • the cell to be handed over is referred to as a target cell
  • the statistical operation of the number of users is performed by the DA.
  • Step 1001 The UE initiates a cell update request to the RRC, where the request includes identifier information of the target cell.
  • Step 1002 after receiving the request for cell update from the UE, the RRC determines whether the common channel data carried by the target cell and the source cell is the same. If the same, the process directly proceeds to step 1005. If not, step 1003 is performed;
  • Steps 1003 - 1004 the RRC recalculates the UR TI and CR TI of the UE, and then sends information to the UE to change the UTRAN, where the information includes the recalculated UR TI And the CRNTI, the UE changes its URNTI and CRNTI to the received U NTI and CRNTI according to the received information. After the change is completed, the UE returns a confirmation message of changing the UTRAN to the RC.
  • Step 1005 The RRC notifies the CA in the multicast proxy module that the UE performs the cell update, and the CA notifies the DA, where the notification includes the identifier information of the target cell and the identifier of the UE that initiates the update request.
  • Steps 1006 - 1007 the DA in the multicast proxy module increases the number of users corresponding to the service data content identifier received by the UE in the target cell by one; and then determines that the result received by the UE is, then starts in the target cell.
  • the public transmission channel carrying the service data sends data, and then step 1008 is performed. Otherwise, step 1008 is directly performed.
  • Steps 1008 - 1009 the DA in the multicast proxy module reduces the number of users corresponding to the service data content identifier received by the UE in the source cell by one; and then determines the data corresponding to the service data content identifier received by the UE in the source cell. Whether the number of users in the transmission channel is non-zero, if yes, step 1010 is directly performed; otherwise, the DA stops sending service data to the data transmission channel corresponding to the service data content identifier received by the UE in the source cell, and then Go to step 1010.
  • Step 1010 The DA in the multicast proxy module notifies the CA that the operation is completed, and the CA returns the RRC to return the operation completion response information.
  • Step 1011 After receiving the response, the RRC returns a cell update response to the UE.
  • the RRC adds one to the number of users corresponding to the service data content identifier received by the UE in the target cell, and then determines the service data received by the UE.
  • the content identifier corresponds to whether the number of users in the transmission channel is changed from zero to non-zero. If yes, the DA in the multicast proxy module is notified.
  • the DA starts to send data to the public transmission channel carrying the service data in the target cell, and returns the response information for performing the operation to the SACU; then, step 1008 is performed; otherwise, step 1008 is directly performed;
  • the RC reduces the number of users corresponding to the service data content identifier received by the UE in the source cell by one, and then determines the number of users in the data transmission channel corresponding to the service data content identifier received by the UE in the source cell. Whether it is non-zero, if yes, no processing is performed. Otherwise, the DA in the multicast proxy module is notified to stop transmitting data.
  • the DA After receiving the notification, the DA stops responding to the service data content identifier received by the UE in the source cell.
  • the service data is transmitted in the data transmission channel, and the operation completion response information is returned to the RRC. Finally, the cell update response is still returned by the RC to the UE.
  • the multicast proxy module may be set in the RC in the RAN, or may be set in the NodeB in the RAN. If it is set in the RC, between all the multicast proxy modules and the RRC. The interaction is the internal processing of the RNC. If it is set in the NodeB, the interaction between all the multicast proxy modules and the RRC is the interaction between the NodeB and the RNC. If the multicast proxy module is set in R C, there is a problem of switching across R C. The implementation process across RNC is specifically described below.
  • Figure 11 shows the flow chart of the handover process when performing RNC.
  • the cell in which the UE is currently located is referred to as a source cell
  • the cell to be handed over is referred to as a target cell
  • the current RNC of the UE is referred to as a source RNC
  • the multicast proxy module in the source RNC is referred to as a source multicast proxy module.
  • the RNC to be switched is referred to as a target RNC
  • the multicast proxy module in the target RNC is referred to as a target multicast proxy module.
  • Step 1101 The RRC in the source RNC sends a join request to the RRC in the target RNC. Steps 1102 - 1103, the RRC in the target RNC initiates a join request to the CA in the target multicast proxy module, and the CA notifies the DA that the DA in the target multicast proxy module identifies the service data content to be received in the target cell and the UE.
  • Add the number of corresponding users then Determining whether the number of users in the transmission channel corresponding to the service data content identifier received by the UE is changed from zero to non-zero, and if yes, in the target cell, corresponding to the service data content identifier received by the UE on the transmission channel
  • the transmission of the service data is initiated, and then the response message is returned to the RRC in the target RNC. Otherwise, the response message is directly returned to the RRC in the target RNC.
  • Step 1104 The RRC in the target RNC sends a join request response to the RRC in the source RNC.
  • Steps 1105 - 1106 the RRC in the source RNC sends a release request to the CA in the source multicast proxy module, and the CA notifies the DA, and the DA in the source multicast proxy module identifies the service data content to be received in the source cell and the UE.
  • the number of corresponding users is decremented by one, and then it is determined whether the number of users in the transmission channel corresponding to the service data content identifier received by the UE in the source cell is non-zero. If yes, the RRC returns a response message directly to the source RNC. Otherwise, the transmission service data of the data transmission channel corresponding to the service data content identifier received by the UE in the source cell is stopped, and then the response message is returned to the RRC in the source RNC.
  • the DAs in all the multicast proxy modules mentioned above may exist in a single-level form or in multiple-level forms.
  • the DA exists in multiple levels, refer to FIG.
  • Figure 12 shows the implementation principle of the two-stage DA in the multicast proxy module.
  • the multicast proxy module is divided into two levels: a low-level multicast data agent unit (LDAU) and a high-level multicast data agent unit (HDAU, High Data Agent Unit). And assume that the multicast proxy module is set in the RNC.
  • LDAU low-level multicast data agent unit
  • HDAU High Data Agent Unit
  • the LDAU adds one of the number of users in the current cell corresponding to the service data content identifier received by the UE that initiated the request, and then judges And whether the number of users corresponding to the service data content identifier received by the UE that initiated the request in the current cell is changed from zero to non-zero, and if yes, an access request is sent to the high-level multicast data proxy unit HDAU, and the HDAU starts to The public transmission channel carrying the service data sends data, otherwise 11) enters 11 not processing.
  • the LDAU decrements the number of users corresponding to the service data content identifier received by the UE that initiated the request in the current cell, and then determines the service received by the UE in the current cell and the requesting UE. Whether the number of corresponding users of the data content identifier changes from non-zero to zero. If yes, the LDAU notifies the HDAU to stop transmitting the service data in the data transmission channel corresponding to the service data content identifier received by the UE in the cell, otherwise, Do the processing.
  • Figure 12 is only taken as an example of two levels. Of course, there may be more than two levels of multicast data proxy units. In this case, the HDAU will interact with the higher HDAU as needed. The specific interaction mode is consistent with the characteristics of the LDAU. This is not repeated. Similarly, the above is an example in which the number of users is counted by LDAU or HDAU. Of course, the statistical operation of the number of users may be performed by the RRC.
  • the lowest LDAU is used as the multicast router to manage the following multicast user groups, which reduces the processing load of the HDAU and implements distributed processing, and the HDAU is only responsible for the LDAU. Management, its management method is consistent with the management method of the LDAU management for the cell.
  • the embodiment shown in FIG. 12 is that the multi-level multicast proxy module is set in the RNC. In actual application, the multi-level multicast proxy module can also be set in the NodeB, and the specific implementation and setting are implemented. The implementation is the same in RC.
  • the multicast proxy module can use the hardware-based multicast function in the RNC to implement data distribution functions, such as using the IP multicast switching function, or using the ATM multicast switching function, or utilizing multiple Multicast switching function of the service platform,
  • the multicast service data is distributed from the HDAU to the low-level LDAU, which can implement the multicast data distribution processing in the RNC and provide reliable QoS guarantee.
  • the multicast proxy module is set in the RNC, whether it is single-level or multi-level, there are several implementations for the NodeB.
  • Manner 1 The NodeB side does not perform any processing, that is, the multicast proxy module in the RNC directly establishes a transmission channel for each service data content identifier in each cell.
  • the advantage of this implementation is that NodeB does not require any changes, but it requires a lot of IUB interface resources between RNC and NodeB. See Figure 12 for this method.
  • a multicast data distribution agent (MDDA) module is set in the NodeB, and the function distributed to each cell is implemented by the MDDA in the NodeB.
  • the MDDA module receives the service data from the RNC, copies the received service data as needed, and distributes it to each cell to send a copy. In this way, it is only necessary to establish a data transmission channel between the RNC and the NodeB for the same service data content identifier, and send a service data, thereby saving the IUB interface resource between the RNC and the NodeB.
  • a two-level proxy is set in R C
  • MDDA is set in the NodeB.
  • the multicast proxy module may be set on a base station controller (BSC) in the RAN, and the BSC is usually recorded as CBSC (CDMA BSC), or may be set in a base transceiver station in the RAN ( On the BTS, the BTS is usually recorded as CBTS (CDMA BTS).
  • BSC base station controller
  • CBTS CDMA BTS
  • GSM BSC GBSC
  • GSM BTS GSM BTS
  • SACU Signal and Control Unit

Landscapes

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

Abstract

L'invention concerne un procédé de multidiffusion de données de trafic fondé sur le réseau mobile qui envoie un module d'agent multidestinataire dans le réseau radio RAN. Le module d'agent multidestinataire surveille les demandes d'accès y compris les informations de destination provenant de l'UE. Après que le module d'agent multidestinataire a jugé que les informations de destination de la demande sont les informations de destination de la source de données prédéterminée à utiliser pour fournir un service de données de trafic, il effectue une commande d'accès et établit la connexion de commande avec l'UE. L'UE obtient les informations d'attributs provenant du traitement d'établissement de la connexion de commande. Le module d'agent multidestinataire envoie à l'UE les données de trafic correspondant à l'identification du contenu de données de trafic provenant de la source de données. L'UE reçoit les données de trafic dans le canal de transmission établi en fonction des informations d'attributs de réception obtenues. Du fait que le module d'agent multidestinataire est adopté dans l'invention, un élément de données est transmis uniquement à partir de la source de données vers le module d'agent multidestinataire, en effectuant la multidiffusion des données de trafic, en autorisant un traitement de données plus rapide et plus fluide et en améliorant la disponibilité des ressources du réseau. DRAWIN G:
PCT/CN2006/001045 2005-05-20 2006-05-19 Procede de multidiffusion de donnees de trafic fonde sur le reseau mobile WO2006122509A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2005100711945A CN100421515C (zh) 2005-05-20 2005-05-20 基于移动网络的组播业务数据的实现方法
CN200510071194.5 2005-05-20

Publications (1)

Publication Number Publication Date
WO2006122509A1 true WO2006122509A1 (fr) 2006-11-23

Family

ID=37134014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001045 WO2006122509A1 (fr) 2005-05-20 2006-05-19 Procede de multidiffusion de donnees de trafic fonde sur le reseau mobile

Country Status (2)

Country Link
CN (1) CN100421515C (fr)
WO (1) WO2006122509A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022179500A1 (fr) * 2021-02-26 2022-09-01 华为技术有限公司 Procédé et appareil de communication
WO2024032189A1 (fr) * 2022-08-11 2024-02-15 华为技术有限公司 Procédé et appareil de transmission de données

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101232628B (zh) * 2007-01-22 2013-01-23 华为技术有限公司 查找网络的方法与用于查找网络的用户设备
CN101296407B (zh) * 2007-04-23 2011-07-06 电信科学技术研究院 多载波移动通信系统传输mbms的方法及装置
CN101388811B (zh) * 2007-09-10 2015-03-18 上海中兴软件有限责任公司 基于无线接入网的接入控制方法
CN101610448B (zh) * 2008-06-20 2012-12-19 中兴通讯股份有限公司 一种无线接入设备的动态接入方法
US20100057926A1 (en) * 2008-08-28 2010-03-04 Sycamore Networks, Inc. Digital custom data content injection mechanism for a content delivery network
CN101990192A (zh) * 2009-07-30 2011-03-23 中兴通讯股份有限公司 本地ip访问连接属性的通知方法与装置
CN101860871B (zh) * 2010-04-01 2013-01-02 田兆文 无线通信系统中在下行共享信道上实现多用户共享数据的一种方法及系统
CN101932029A (zh) * 2010-08-13 2010-12-29 华为技术有限公司 数据传输方法、设备及系统
CN103493462B (zh) 2012-12-31 2018-02-02 华为技术有限公司 提供应用服务的系统、方法和设备
CN104601205B (zh) * 2013-10-31 2018-06-05 华为终端（东莞）有限公司 一种内容共享的方法及装置
CN105743663B (zh) * 2014-12-10 2020-06-23 广东恒宇信息科技有限公司 一种数据传输装置和方法
EP4064738A1 (fr) 2016-05-20 2022-09-28 InterDigital Patent Holdings, Inc. Procédé et unité d'émission/réception sans fil pour transmission en multidiffusion
CN109982266B (zh) 2017-12-28 2021-05-11 华为技术有限公司 一种通信方法、及相关产品

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001065817A1 (fr) * 2000-03-02 2001-09-07 Mci Worldcom, Inc. Systeme de communication radio internet
US20040081192A1 (en) * 2001-10-19 2004-04-29 Dimitiris Koulakiotis Transmission of multicast and broadcast multimedia services via a radio interface
CN1592250A (zh) * 2003-09-03 2005-03-09 北京鼎视通软件技术有限公司 一种流媒体数据多点传输方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1476198A (zh) * 2002-08-15 2004-02-18 ��������ͨ�ż����о����޹�˾ 利用小区广播的mbms的业务广告或业务指示的方法
CN1499853A (zh) * 2002-11-05 2004-05-26 北京三星通信技术研究有限公司 支持多媒体广播与组播业务采用共享Iu信令连接的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001065817A1 (fr) * 2000-03-02 2001-09-07 Mci Worldcom, Inc. Systeme de communication radio internet
US20040081192A1 (en) * 2001-10-19 2004-04-29 Dimitiris Koulakiotis Transmission of multicast and broadcast multimedia services via a radio interface
CN1592250A (zh) * 2003-09-03 2005-03-09 北京鼎视通软件技术有限公司 一种流媒体数据多点传输方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022179500A1 (fr) * 2021-02-26 2022-09-01 华为技术有限公司 Procédé et appareil de communication
WO2024032189A1 (fr) * 2022-08-11 2024-02-15 华为技术有限公司 Procédé et appareil de transmission de données

Also Published As

Publication number Publication date
CN100421515C (zh) 2008-09-24
CN1852551A (zh) 2006-10-25

Similar Documents

Publication Publication Date Title
WO2006122509A1 (fr) Procede de multidiffusion de donnees de trafic fonde sur le reseau mobile
CN1625864B (zh) 选择多播/广播服务的分组数据服务节点
KR101019400B1 (ko) 인터넷 프로토콜을 이용하여 무선 통신 시스템에서 데이터 패킷을 전송하는 방법 및 장치
TWI223532B (en) Method and apparatus for data packet transport in a wireless communication system using an Internet Protocol
US7107066B2 (en) Multicast support in packet switched wireless networks
US8411680B2 (en) IP multicasting system and a method based on the mobile network
US7061880B2 (en) Systems and methods for multicast communications
US7509127B2 (en) MBMS PtP and PtM channel change
WO2008113263A1 (fr) Procédé pour supporter un service de diffusion/multidiffusion multimédia dans l'évolution d'une architecture système
KR100733911B1 (ko) Ｍｂｍｓ 제공 시스템 및 그 방법
TW200400725A (en) Method and apparatus for negotiation of transmission parameters for broadcast/multicast services
US20050152392A1 (en) Method and apparatus for converging broadcast service and multicast service a mobile communication system
US20090238107A1 (en) Method for bearer control and deletion, data distribution, and modification
KR100956817B1 (ko) 패킷 데이터를 처리하는 방법 및 이를 위한 장치
CN102821359B (zh) 业务共享传输方法、装置及系统
WO2023029590A1 (fr) Procédé de gestion de session de diffusion/multidiffusion et appareil de communication
US9338488B1 (en) Method and apparatus for providing video optimization for broadcast media
US20220210690A1 (en) Data transmission method and apparatus, system, and storage medium
CN101132392B (zh) 一种单独载频广播系统及其实现业务传送的方法
CN101588537A (zh) WiMAX网络中实现广播/组播的方法、装置和系统
WO2005053331A1 (fr) Procede de mise en oeuvre d'un service de multidiffusion
CN100459557C (zh) 一种实现小区多媒体广播业务的方法及系统
CN1902974A (zh) 在软切换期间使广播流的传输同步的方法
WO2007124633A1 (fr) Procédé de fourniture d'un service multidestination par le côté réseau dans un système de communication mobile wimax
WO2010133027A1 (fr) Procédé, appareil et système pour un service de multidiffusion basé sur un enodeb domestique

Legal Events

Date Code Title Description
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

NENP Non-entry into the national phase

Ref country code: RU

WWW Wipo information: withdrawn in national office

Country of ref document: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06741933

Country of ref document: EP

Kind code of ref document: A1