[go: up one dir, main page]

WO2009021467A1 - Procédé et système de réseau de transmission de service de diffusion multimédia multidestinataire (mbms) - Google Patents

Procédé et système de réseau de transmission de service de diffusion multimédia multidestinataire (mbms) Download PDF

Info

Publication number
WO2009021467A1
WO2009021467A1 PCT/CN2008/072014 CN2008072014W WO2009021467A1 WO 2009021467 A1 WO2009021467 A1 WO 2009021467A1 CN 2008072014 W CN2008072014 W CN 2008072014W WO 2009021467 A1 WO2009021467 A1 WO 2009021467A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
multicast
layer
slave
primary
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2008/072014
Other languages
English (en)
Chinese (zh)
Inventor
Junwei Wang
Jie Ma
Qufang Huang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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 WO2009021467A1 publication Critical patent/WO2009021467A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and a network system for multicast multicast service transmission.
  • Multicast Broadcast Multicast Service is one of the important contents of 3GPP (The 3rd Generation Partnership Project) business development.
  • MBMS refers to sending the same multimedia service data at the same time on the network side. Give multiple recipients in the network.
  • HSPA+ High Speed Packet Access
  • the network side needs to transmit the same MBMS data in multiple cells at the same time, and use the same coding mode to strictly transmit synchronously to enable the user equipment.
  • UE User Equipment
  • RAKE multipath diversity
  • BM-SC Broadcast Multicast- Service Center
  • GGSN Gateway GPRS Support Node
  • SGSN Serving GPRS Support Node
  • RNC Radio Network Controller
  • the technical problem to be solved by the embodiments of the present invention is to provide a method and a network system for transmitting multicast multicast services, which can implement synchronous transmission of MBMS services.
  • a multicast multicast service transmission method where the method includes:
  • the primary entity receives the multicast multicast MBMS service data; the primary entity controls the RLC layer and the medium access control MAC layer through the radio link control RLC layer, and controls the RLC layer and the media via the radio link.
  • the data block and the air interface sending time flag obtained by the access control MAC layer are sent to the auxiliary device of the primary entity; and the air interface sending time flag is added to the data block obtained in the process to form a data packet. Concurrently issued to the entity;
  • a multicast multicast service transmission method comprising:
  • the primary entity receives the multicast multicast service MBMS data
  • the master entity processes the multicast multicast service data by the radio link control RLC layer, and sends the air interface transmission time flag and the data block processed by the radio link control RLC layer to the slave entity;
  • the data processed by the radio link control RLC layer is processed by the MAC layer, and the air interface transmission time stamp and the data block processed by the MAC layer are sent to the auxiliary device of the main entity; the slave entity sends the time stamp and the location of the air interface.
  • the data block obtained by the RLC layer processed by the radio link control is processed by the MAC layer and sent to the accessory device of the slave entity;
  • the slave device of the slave entity and the attached entity sends the data block processed by the MAC layer processing.
  • a network system comprising: a primary entity, an auxiliary device of a primary entity, a secondary device, and an auxiliary device of the secondary entity; the primary entity, configured to receive multicast multicast service data, and control the service data by using a wireless link
  • the RLC layer and the medium access control MAC layer are processed, and the data block and the air interface transmission time flag processed by the radio link control RLC layer and the medium access control MAC layer are sent to the auxiliary device of the main entity; And sending the air interface sending time flag to the data block obtained by the radio link control RLC layer and the medium access control MAC layer processing process, and sending the time stamp to the slave entity; And the air interface sending time stamp and the data block obtained by the radio link control RLC layer and the medium access control MAC layer are sent to an auxiliary device of the slave entity; Transmitting, by the radio link control RLC layer, the media access control MAC layer, the data block obtained when the air interface transmission time arrives; the primary entity Ancillary equipment, when the air interface for transmission time arrives, the transmission over
  • a network system comprising: a primary entity, an attached device of a primary entity, a secondary device, and an attached device of the physical entity;
  • the primary entity is configured to receive multicast multicast service data, process the multicast multicast service data by using a radio link control RLC layer, and send the air interface time stamp and the radio link control RLC.
  • the data block obtained in the processing of the layer is sent to the slave entity;
  • the master entity is further configured to: process the data processed by the radio link control RLC layer through the MAC layer, and send the air interface time stamp and the MAC layer to process The data block is sent to the attached device of the main entity;
  • the slave entity configured to send the air interface time stamp and the data block processed by the radio link control RLC layer to the accessory device of the slave entity after being processed by the MAC layer;
  • the slave device of the slave entity configured to send, when the air interface sending time arrives, the data block processed by the MAC layer;
  • An accessory device of the primary entity configured to send the time when the air interface sending time arrives
  • the MAC layer processes the resulting data block.
  • the technical solution of the foregoing technical solution has the following beneficial effects:
  • the data entity and the air interface sending time flag obtained by processing at least the RLC layer are sent to the auxiliary device of the main entity, and the processing is processed by itself.
  • the data block plus the air interface transmission time flag is sent to the slave entity, and the slave entity sends the data block and the air interface transmission time flag processed through at least the RLC layer to the slave device of the slave entity, and when the air interface time arrives, the master entity
  • the accessory device and the slave device from the entity send the data block processed by the MAC layer to the air interface, and can synchronously transmit the transmitted data block to achieve the synchronous transmission of the MBMS service data.
  • FIG. 1 is a network architecture for implementing MBMS transmission provided by the prior art
  • FIG. 2A is a structural diagram of a network system according to an embodiment of the present invention.
  • 2B is a structural diagram of a network system according to an embodiment of the present invention.
  • 2C is a structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for transmitting MBMS services according to Embodiment 1 of the present invention
  • FIG. 4A is a structural diagram of a protocol stack when air interface is merged according to Embodiment 1 of the present invention
  • 4B is a structural diagram of a protocol stack when an air interface is merged according to Embodiment 1 of the present invention
  • FIG. 5 is a schematic diagram of an IP multicast address notified by a core network according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of an IP multicast address notified by a core network according to an embodiment of the present invention
  • FIG. 8A is a data structure diagram according to Embodiment 1 of the present invention
  • Embodiment 8B is a data structure diagram according to Embodiment 1 of the present invention.
  • FIG. 9 is a flowchart of a method for transmitting MBMS service according to Embodiment 2 of the present invention
  • FIG. 10A is a structural diagram of a protocol stack for soft combining according to Embodiment 2 of the present invention
  • 10B is a structural diagram of a protocol stack in a soft combining manner according to Embodiment 2 of the present invention
  • FIG. 11 is a flowchart of a method for MBMS service transmission according to Embodiment 3 of the present invention
  • FIG. 12 is a selective merge according to Embodiment 2 of the present invention
  • Protocol stack structure diagram
  • FIG. 13 is a structural diagram of a protocol stack when selective combining is provided according to Embodiment 2 of the present invention.
  • FIG. 14 is a flowchart of a method for MBMS service transmission according to Embodiment 4 of the present invention
  • FIG. 15 is a flowchart of a method for MBMS service transmission according to Embodiment 5 of the present invention
  • FIG. 16A is a structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 16B is a structural diagram of a network system according to an embodiment of the present invention.
  • 16C is a structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 17 is a structural diagram of a network system of a control plane according to an embodiment of the present invention.
  • FIG. 18 is a structural diagram of a first embodiment of a network system according to the present invention.
  • FIG. 19 is a structural diagram of a second embodiment of a network system according to an embodiment of the present invention.
  • the physical configuration is on each RNC.
  • the PDCP layer has a module responsible for header compression processing. If a RNC loses a packet, it will affect the value of the PDCP state variable on the RNC, and will affect the next or multiple packets. The header compression process and the result have an impact, resulting in inconsistent data content sent by the RNC and other RNCs at the physical layer.
  • an air interface transmission time flag is added to a part of the data packet sent by the SGSN to the RNC, and the air interface transmission time flag is not added to the partial data packet, so that the transmission of the MBMS service cannot achieve temporal synchronization.
  • the first data packet is added with the air interface transmission time flag
  • the second to the 10th data packet is not added with the air interface transmission time flag
  • the eleventh data packet is added with the air interface transmission time flag.
  • the first time can be sent.
  • the 2-10th data packet is arbitrarily transmitted, and the 2-10th data packet cannot be sent at the same time as other RNCs, for the MBMS service. The transmission cannot achieve synchronization in time.
  • An embodiment of the present invention provides a multicast multicast service transmission method, where the method includes: a primary entity receives multicast multicast service data; and the primary entity controls the service data through a radio link control RLC layer and media access control. Processing of the MAC layer, and sending the data block and the air interface transmission time flag processed by the MAC layer to the accessory device of the primary entity; and sending the air interface to the data block obtained in the process Time stamping, to form a data packet, and sending the data packet to the slave entity; the slave entity sends the air interface transmission time stamp and the data block processed by the MAC layer to the slave device of the slave entity; sending the air interface at the air interface When the time arrives, the slave node of the entity and the accessory device of the master entity send the data block processed by the MAC layer.
  • the primary entity is an evolved base station
  • the secondary device of the primary entity is a physical layer of the evolved base station, or the primary entity is a radio network controller, and the accessory device of the primary entity is a base station.
  • the slave entity is an evolved base station, and the slave device of the slave entity is a physical layer of the evolved base station, or the slave entity is a radio network controller, and the slave device of the slave entity is a base station.
  • the embodiment of the invention further provides a multicast multicast service transmission method, including:
  • the primary entity receives the multicast multicast service MBMS data
  • the master entity processes the multicast multicast service data by the radio link control RLC layer, and sends the air interface transmission time flag and the data block processed by the radio link control RLC layer to the slave entity;
  • the data processed by the radio link control RLC layer is processed by the MAC layer, and the air interface transmission time stamp and the data block processed by the MAC layer are sent to the auxiliary device of the main entity; the slave entity sends the time stamp and the location of the air interface.
  • the data block obtained by the RLC layer processed by the radio link control is processed by the MAC layer and sent to the accessory device of the slave entity;
  • the slave device of the slave entity and the slave device of the master entity send the data block processed by the MAC layer processing.
  • the use of resources can only use static configuration, so the physical layer used by the RNC, the RLC layer, The resources of the MAC layer and the PDCP layer are statically configured.
  • the physical layer resources configured for the RNC regardless of whether the RNC needs to be used, the resources of the physical layer are always occupied, and the physical layer resources cannot be adjusted according to the system operation. It will reduce the efficiency of resource use. For systems with frequent business changes or a large variety of services, the task of resource allocation is very large and error-prone.
  • the physical layer resource configured by the RNC is configured on the base station NodeB connected to the RNC.
  • the MBMS service transmission method provided by the foregoing embodiment of the present invention can implement synchronous transmission of the MBMS service, and timely adjust physical layer resources according to system operation.
  • the first embodiment of the present invention provides a method for MBMS service transmission, where the method is applicable to air interface merging, and the method specifically includes:
  • Step 301 Determine one or more primary RNCs.
  • the primary RNC is determined in the following three manners, but is not limited to the three manners.
  • the first manner is: The SGSN sends a session start message session start carrying the primary RNC identifier to all RNCs, if the SGSN does not receive the primary RNC.
  • the response message resends the session start to the determined primary RNC until the response of the primary RNC is received;
  • the second way is: each RNC in the MBMS service area negotiates to generate a primary RNC, and the primary generated by the negotiation
  • the RNC sends a notification message to the SGSN that is the primary RNC.
  • the third mode is: determining, by the SGSN, the primary RNC according to a certain preset measurement, or by using the preset one of the secondary RNCs in the MBMS service area. Determine the primary RNC.
  • Step 302 The primary RNC specifies the combination mode of the service data, or generates the configuration information of the PDCP layer, the RLC layer, and the MAC layer according to the combination mode specified by the core network, and configures the PDCP layer, the RLC layer, and the MAC layer. Entity resources.
  • the merge mode determined in this embodiment is an air interface merge mode.
  • the method for merging the service data by the primary RNC is specifically as follows: the primary RNC specifies the merging mode of the service data according to the quality of service (QoS) requirements of the MBMS service, and the primary RNC according to the resource usage of the slave RNC. And/or load conditions specify how the business data is combined.
  • the COUNTING policy includes: periodically performing, participating in the UE feature specification of the COUNTING.
  • Step 304 The slave RNC that is designated to perform the COUNTING process performs COUNTING according to the received COUNTING policy, and finds that the UE that is not interested in the MBMS service according to the result of the COUNTING sends a notification message to the primary RNC that the UE does not receive the service. It is assumed in the present embodiment that there is no notification message that the UE receives the UE-free service from the RNC to the primary RNC.
  • Step 305 The primary RNC specifies a physical layer resource for transmitting service data, or the primary RNC negotiates with each RNC to determine a physical layer resource for transmitting service data.
  • the specific implementation manner is as follows: If the specified physical layer resource does not conflict with the physical resource used by the RNC itself for other services, the RNC uses the specified physical layer resource to transmit the MBMS service. If the specified physical layer resource conflicts with the physical resource used by the RNC itself for other services, the RNC sends a conflict indication to the primary RNC. The physical layer resource is again coordinated by the primary RNC until the physical layer resource specified by the primary RNC does not conflict with all the physical resources used by the RNC for other services, and all the specified physical layer resources are allocated from the RNC to transmit the MBMS. business. All slave RNCs in this step are managed from the RNC in the master RNC.
  • the primary RNC indicates resource preemption from the RNC according to the MBMS service priority.
  • Step 306 The primary RNC notifies the RNC of the air interface merge mode, the physical layer resource configuration information, the PDCP layer, the RLC layer, and the MAC layer configuration information through the Iur interface.
  • Step 307 After receiving the merge mode from the RNC, it is learned that the merge mode of the MBMS service transmission is air interface merge, and the physical layer is configured according to the configuration information of the physical layer resources received in the foregoing step, and the physical layer cannot be configured autonomously, and the protocol when the air interface is merged
  • the stack is shown in Figure 4A, Figure 4B.
  • Step 308 The primary RNC and the secondary RNC notify the UE of the radio bearer configuration RB corresponding to the MBMS service through the MBMS service control channel MCCH.
  • the RB configuration information sent by the primary RNC includes: an air interface merge mode, a PDCP layer, and a MAC address.
  • the configuration information of the layer, the RLC layer, and the physical layer resource; the RB configuration information transmitted from the RNC is the configuration information of each layer received from the primary RNC in step 306.
  • the RB configuration information sent from the RNC may be generated from the RLC layer of the RNC according to the RB configuration information carried by the primary RNC, or may be generated by the primary RNC to generate a MAC-m packet on the MCCH, and scheduled and transmitted from the RNC according to the predetermined scheduling information.
  • the specified scheduling information is the same as the scheduled MCCH data transmission on the primary RNC. It can be sent by the primary RNC to the secondary RNC.
  • Step 309 The primary RNC notifies the IP multicast address corresponding to the MBMS service from the RNC, and the RNC sends the request information of the join multicast group to the multicast router according to the IP multicast address.
  • the primary RNC can notify the IP multicast address from the RNC by the following four methods, but is not limited to the following four methods:
  • the first method notify the slave RNC by sending a separate multicast address notification message
  • the second method the primary RNC notifies the configuration information of the physical layer, the configuration information of the physical layer, the configuration information of the PDCP layer, the RLC layer, and the MAC layer from the RNC, and notifies the IP multicast address from the RNC;
  • the third method Notifying the slave RNC through the transport channel resource request procedure;
  • the fourth method the primary RNC notifies the core network of the IP multicast address, and then the core network notifies the slave RNC through the Iu process.
  • the core network notifies the IP multicast address from the RNC.
  • the first way is: the primary RNC forwards the session start signaling carrying the IP multicast address to the secondary RNC; the second way is: the SGSN first obtains the session start process with the primary RNC.
  • the SGSN first obtains the IP multicast address in the session start process with the primary RNC, and then performs the IP multicast address from the RNC.
  • the IP multicast address is notified from the RNC during the session update session update process.
  • the step of notifying the slave multicast entity of the IP multicast address is specifically:
  • the master entity notifies the core network of the IP multicast address, and the core network notifies the slave entity through the Iu process.
  • Step 310 The primary RNC notifies the multicast router of the IP multicast address, and the multicast router establishes a multicast group according to the IP multicast address, and determines the members of the multicast group according to the request information from the joining multicast group from the RNC. The routing information corresponding to the members of the broadcast group.
  • Step 311 When the MBMS service data transmission time expires, the SGSN sends the service data to the primary RNC, and the primary RNC passes at least the PDCP layer, and the RLC layer may perform the MAC layer processing to obtain the data block, and the data block RLC PDU layer or MAC.
  • the PDU processed by PDCP+RLC+MAC
  • the air interface transmission time stamp is used to obtain the data packet, and the data packet is sent to the base station NodeB connected to the primary RNC; the primary RNC is based on the TNL layer.
  • the IP multicast address corresponding to the MBMS service, and the transport layer protocol header above the IP layer are sent to the multicast router.
  • Step 312 The multicast router forwards the received data packet to the slave RNC according to the routing information corresponding to the member of the multicast group.
  • Step 313 Strip the transport layer header of the data packet from the RNC, and send the data block obtained by the MAC or RLC layer to perform necessary processing from the RNC to obtain a MAC PDU and an air interface transmission time flag, and send the data packet to the base station connected to the slave RNC.
  • the base station is a physical layer resource configured from the RNC, where the transport layer header includes an IP multicast address and a transport layer protocol header above the IP layer; the base station connected to the primary RNC and the base station connected to the slave RNC cache the MAC
  • the data block obtained by the layer processing waits until the air interface transmission time expires, and uses the same time-frequency domain resource to send the data block processed by the MAC layer to the air interface.
  • step 313 the data structure sent by the primary RNC to the physical layer, the data structure sent by the primary RNC to the multicast router IP Router, the data structure sent by the IP router to the secondary RNC, the physical layer of the primary RNC, and the secondary RNC are sent to the RNC.
  • FIG. 8A and FIG. 8B for the data structure of the UE.
  • Step 314 After the MBMS service data ends, the SGSN sends a session stop to each RNC in the MBMS service area. After receiving the message, the primary RNC deletes the physical resource configuration of the PDCP layer, the RLC layer, and the MAC layer corresponding to the MBMS service, and releases the physical resource configuration. Physical layer occupied by the MBMS service Source, and respond to the SGSN session stop response. After the RNC reaches the message, the physical layer resource occupied by the MBMS service is released, and the response information session stop response is returned to the SGSN.
  • Embodiment 1 of the present invention uses a conventional RNC as a primary entity and a secondary entity, and may also use an evolved base station as a primary entity and a secondary entity. Referring to FIG. 2B, the implementation of the present invention is not affected.
  • the primary evolved base station directly sends the MAC PDU to the physical layer of the primary evolved base station, and sends control information carrying the air interface transmission time stamp to the physical layer of the primary evolved base station. .
  • step 313 the transport layer header and air interface transmission time flag of the data packet are stripped from the evolved base station, the physical layer of the primary evolved base station and the service data received from the evolved base station buffer, and the same time-frequency domain resource is used until the air interface transmission time expires. , send business data to the air interface.
  • the session sto can be sent to the primary RNC and the secondary RNC in other ways.
  • the SGSN only sends a session stop to the primary RNC, and the primary RNC forwards the session sto to the secondary RNC without affecting the implementation of the present invention.
  • a second embodiment of the present invention provides a method for MBMS service transmission, where the method is applicable to a soft combining mode, and the method specifically includes:
  • Step 901 is the same as step 301;
  • Step 902 The primary RNC determines the merging mode according to the QoS requirement in the session start, or generates the configuration information of the PDCP layer, the RLC layer, and the MAC layer according to the merging mode specified by the core network, and configures the PDCP layer and the RLC.
  • the physical resources of the layer and the MAC layer are allocated physical layer resources for transmitting the MBMS service data.
  • Step 903 The primary RNC notifies the RNC of the configuration information of the soft combining mode, the PDCP layer, the RLC layer, and the MAC layer through the Iur interface.
  • Step 904 After receiving the merge mode from the RNC, it is learned that the merge mode of the MBMS service transmission is a soft merge mode, and the physical layer resource is configured autonomously, and the protocol stack in the soft merge is shown in FIG. 10A and FIG. 10B.
  • Step 905 The primary RNC notifies the UE by using the radio bearer configuration RB corresponding to the MBMS service of the MBMS service control channel MCCH, where the RB configuration information includes: a soft combining mode, a PDCP layer, Configuration information of the MAC layer, the RLC layer, and the physical layer resource; the RNC combines the received soft combining mode, the PDCP layer, the RLC layer, the MAC layer configuration information, and the self-configured physical layer resource configuration information to form a complete
  • the radio bearer configuration message is sent to the UE through the MCCH.
  • Step 906 - Step 909 is the same as step 309 - step 312.
  • Step 910 The transport layer header of the data packet is stripped from the RNC, and the MAC layer or the data packet is processed as necessary to obtain a data block and an air interface transmission time identifier of the MAC PDU, and the base station is sent to the base station connected to the slave RNC.
  • a physical layer resource configured by the RNC, where the transport layer header includes an IP multicast address, and a transport layer protocol header above the IP layer; the base station connected to the primary RNC and the base station connected to the RNC cache the MAC layer processed
  • the data block when the air interface transmission time expires, sends the data block processed by the MAC layer to the air interface.
  • Step 911 is the same as step 314.
  • the conventional RNC is used as the primary entity and the secondary entity
  • the evolved base station may be used as the primary entity and the secondary entity.
  • the implementation of the present invention is not affected.
  • the master evolved base station directly sends the MAC PDU to the physical layer of the primary evolved base station, and sends control information carrying the air interface transmission time flag to the physical layer of the primary evolved base station. .
  • step 910 the transport layer header and the air interface transmission time flag of the data packet are stripped from the evolved base station, the physical layer of the primary evolved base station and the service data received from the evolved base station buffer, and the same time-frequency domain resource is used until the air interface transmission time expires. , send business data to the air interface.
  • the second embodiment of the present invention may further include the following process: the primary RNC specifies whether part or all of the slave RNC performs the COUNTING process, and sends a COUNTING policy to the slave RNC that specifies the COUNTING process, where the COUNTING policy includes : Periodically, participate in the UE feature specification of COUNTING.
  • the slave RNC designated to perform the COUNTING process performs COUNTING according to the received COUNTING policy, and finds that the UE that is not interested in the MBMS service according to the result of the COUNTING sends a notification message to the primary RNC that the UE does not receive the service.
  • a third embodiment of the present invention provides a method for MBMS service transmission, where the method is applicable to selective merging, and the method specifically includes:
  • Step 1101 Determine one or more primary RNCs.
  • Step 1102 The primary RNC determines that the merge mode is selective merge according to the QoS requirement in the session start, or configures the physical resources of the PDCP layer, the RLC layer, and the MAC layer according to the selective merge mode specified when the core network sends the information. Allocating physical layer resources for transmitting the MBMS service.
  • Step 1103 The primary RNC notifies the RNC of the configuration information of the selective combining mode, the PDCP layer, and the RLC layer through the Iur interface.
  • Step 1104 Configure a MAC layer resource and a physical layer resource from the RNC.
  • Step 1105 The primary RNC notifies the UE of the RB corresponding to the MBMS service by using the MCCH, where the RB configuration information includes: a selective combining mode, a configuration information of a PDCP layer, an RLC layer, a MAC layer, and a physical layer resource;
  • the configuration information of the merge mode, the PDCP layer, and the RLC layer is combined with the configuration information of the MAC layer and the physical layer resource of the self-configuration to form a complete radio bearer configuration message UB, which is sent to the UE through the MCCH.
  • Step 1106 - Step 1107 is the same as step 309 - step 310.
  • Step 1108 When the MBMS service transmission time expires, the SGSN or the GGSN sends the service data to the primary RNC.
  • the air interface After the primary RNC is processed by the PDCP layer, the RLC layer, and the MAC layer, the air interface sends a time stamp to the base station connected to the primary RNC based on the MAC PDU.
  • the base station is the physical layer resource configured by the primary RNC.
  • the air interface transmission time stamp is added, and the IP multicast address corresponding to the MBMS service and the transport layer protocol header above the IP layer are sent to the IP Router.
  • Step 1109 The multicast router forwards the received data packet to the slave RNC according to the routing information corresponding to the member of the multicast group.
  • Step 1110 The base station connected to the primary RNC caches the received MAC layer processing The data block, when the air interface transmission time expires, sends the data block processed by the MAC layer to the air interface.
  • the transport layer header is stripped from the RNC, and the air interface transmission time stamp and the MAC layer processed data block are sent to the base station connected to the slave RNC, and when the air interface transmission time expires, the base station connected with the slave RNC is processed by the MAC layer.
  • the data block is sent to the air interface.
  • Step 1111 After the MBMS service data transmission ends, the SGSN sends a session sto to each RNC in the MBMS service area.
  • the primary RNC deletes the resource configuration of the PDCP layer, the RLC layer, and the MAC layer corresponding to the MBMS service, and releases the resource configuration.
  • the physical layer resource occupied by the MBMS service and responds to the session stop response to the SGSN.
  • the RNC deletes the resource configuration of the MAC layer corresponding to the MBMS service, releases the physical layer resource occupied by the MBMS service, and returns a response message session stop response to the SGSN.
  • the IP router deletes the routing entry corresponding to the IP multicast address of the MBMS service.
  • the receiving, by the entity, the service end instruction is: the receiving entity receives the service end instruction directly sent by the core network, or the slave entity receives the service end instruction forwarded by the primary entity.
  • the protocol stack in the selective merging in this embodiment is shown in FIG. 12, and the protocol stack in the selective merging as shown in FIG. 13 may also be selected, which does not affect the implementation of the present invention.
  • the RNC configures its own RLC layer resource according to the RLC layer configuration information, and configures the MAC layer resource and the physical layer resource autonomously.
  • the RNC selects the received selective combining mode, the configuration information of the PDCP layer, and the RLC layer configuration information, and the configuration information of the autonomously configured MAC layer and the physical layer resource to form a complete control message UB.
  • the MCCH is sent to the UE.
  • the primary RNC adds the time stamp of the air interface to the PDCP PDU, plus the IP multicast address corresponding to the MBMS service, and the transport layer protocol header above the IP layer, and sends the packet to the multicast router.
  • step 1110 the received packet transmission layer header and the air interface transmission time stamp are stripped from the RNC, and the data packet is processed by the RLC layer and the MAC layer to obtain a data block, and waits until the air interface is sent. At that time, the data block is sent to the air interface through the physical layer.
  • the resource configuration of the RLC layer and the MAC corresponding to the MBMS service is deleted, and the physical layer resource occupied by the MBMS service is released.
  • the traditional RNC is used as the primary entity and the secondary entity
  • the evolved base station may be used as the primary entity and the secondary entity. Referring to FIG. 2B, the implementation of the present invention is not affected.
  • the third embodiment of the present invention may further include the following process:
  • the primary RNC specifies whether the partial or full COUNTING process is performed from the RNC, and sends a COUNTING policy to the secondary RNC that specifies the COUNTING process, where the COUNTING policy includes : Periodically, participate in the UE feature specification of COUNTING.
  • the slave RNC designated for the COUNTING process performs COUNTING according to the received COUNTING policy. According to the result of COUNTING, it is found that the UE that is not interested in the MBMS service sends a notification message to the primary RNC that no UE receives the service. It is assumed in the present embodiment that no notification message is sent from the RNC to the primary RNC for UE-free reception. The implementation of the invention is not affected.
  • a third embodiment of the present invention provides a method for MBMS service transmission.
  • the primary RNC finds that air interface merging cannot be performed or The soft merge is combined, and the MBMS service can be selectively merged based on current resource conditions and operating conditions. Therefore, the primary RNC notifies all the RMCs to change the merge mode, and notifies the new configuration of the PDCP layer and the RLC layer and the requirements for the configuration of the MAC layer and/or the RLC layer from the RNC, and also notifies the core network or the operation and maintenance controller OMC.
  • the MBMS service has been selectively merged.
  • the method specifically includes: Step 1401: The primary RNC determines that the MBMS service can be selectively merged according to the current resource status and the running status, and the primary RNC regenerates the PDCP layer configuration information and the RLC. Layer configuration information, and configure resources of the PDCP layer and the RLC layer.
  • Step 1402 The primary RNC sends the selective combining mode and the new configuration information of the PDCP layer and the RLC layer to the slave RNC.
  • Step 1403 Configure its own MAC layer resource and physical layer resource from the RNC.
  • Step 1404 The primary RNC sends, to the UE, the control message UB that carries the configuration information of the PDCP layer and the RLC layer that is changed by the selective merge mode, and the selective RMU mode that is received by the RNC, the changed PDCP layer, and the RLC layer configuration.
  • the information and the self-configured MAC layer and physical layer resource configuration information are combined to form a complete control message UB, which is sent to the UE through the MCCH.
  • Step 1405 After all the RNCs are set according to the new configuration, the MBMS service continues to be sent, and the SGSN sends the service data to the primary RNC.
  • the primary RNC is processed by the PDCP, the RLC, and the MAC, the air interface is added to the MAC PDU.
  • the send time stamp is sent to the physical layer of the primary RNC.
  • the air interface transmission time stamp is added, and the IP multicast address corresponding to the MBMS service and the transport layer protocol header above the IP layer are sent to the multicast router.
  • Step 1406 - Step 1408 is the same as steps 1109 - 1111.
  • the selective combining in the embodiment of the present invention may also select a protocol stack when selectively combining as shown in FIG. 13, and does not affect the implementation of the present invention.
  • the primary RNCs of the respective services may be the same or different, and the IP multicast addresses corresponding to the respective services are different. That is to say: 1) When different primary RNCs transmit different MBMS services, the corresponding IP multicast addresses cannot be the same; 2) when different primary RNCs transmit the same MBMS service, they can correspond to the same IP multicast address; When the same primary RNC transmits different MBMS services, the corresponding IP multicast addresses cannot be the same; 4) When all the same MBMS services are transmitted from the RNC managed by the same primary RNC, these services correspond to the same IP multicast address, but The port used by the IP layer's bearer protocol, User Datagram Protocol (UDP), must be different. If multiple primary RNCs are determined in the service transmission range, the user plane parameters configured by these primary RNCs are the same. The user plane parameters refer to: PDCP layer, RLC layer, part or all configuration parameters of the MAC layer.
  • the conventional RNC is used as the primary entity and the secondary entity
  • the evolved base station may be used as the primary entity and the secondary entity. Referring to FIG. 2B, the implementation of the present invention is not affected.
  • a fifth embodiment of the present invention provides a method for MBMS service transmission, which is introduced.
  • the COUNTING process starts from the RNC without UE reception, and then has the service transmission situation when the UE receives, and the method specifically includes:
  • Step 1501 - Step 1503 is the same as step 301 - step 303;
  • Step 1504 The slave RNC designated to perform the COUNTING process performs COUNTING according to the received COUNTING policy, and finds that the UE that is not interested in the MBMS service according to the result of the COUNTING sends a notification message to the primary RNC that the UE does not receive the service.
  • a notification message of no UE reception service is transmitted from the RNC 3 and the RNC 4 to the primary RNC.
  • Step 1505 The primary RNC negotiates with the RNC to determine a physical layer resource for transmitting service data.
  • the specific manner in which the primary RNC negotiates with the RNC to determine the physical layer resources for transmitting the service data is the same as the step 305.
  • the RNC 3 and the slave RNC 4 may not participate in the negotiation, and the implementation of the present invention is not affected.
  • Step 1506 - Step 1513 is the same as Step 306 - Step 313, but the slave RNCs in these steps do not include RNC3, RNC4.
  • Step 1514 RNC3 and RNC4 perform the second and third CONUTING according to the COUNTING period specified by the primary RNC. After the third COUNTING, both RNCs receive the response of the UE indicating that the MBMS service is received, RNC3 and RNC4. A notification is sent to the primary RNC that the UE receives the MBMS service.
  • Step 1515 After receiving the foregoing notification, the primary RNC establishes a transmission channel of the Iur with the RNC3 and the RNC4, and notifies the RNC3 and the RNC4 of the multicast address, the air interface combination mode, and the corresponding RB configuration information, and instructs the RNC3 and the RNC4 to preempt the MBMS service. Resources.
  • Step 1516 The RNC3 and the RNC4 configure the physical layer resources of the owning device NodeB according to the RB configuration information given by the primary RNC, and send the RB configuration information to the UE through the MCCH channel.
  • RNC3 and RNC4 join the multicast group, and begin to receive the data packet sent by the primary RNC with the air interface transmission time stamp, the IP multicast address, and the transport layer protocol header above the IP layer, and send the air interface transmission time stamp and the MAC PDU.
  • the NodeB sent by the NodeB at the physical layer.
  • Step 1517 After the COUNTING is performed for the sixth time, the RNC3 finds that there is no UE response, and sends a notification to the primary RNC that the UE does not receive the service again.
  • the RNC3 exits the multicast group and also stops broadcasting the RB configuration information of the MBMS service on the MCCH, and notifies the NodeB to release the physical layer resources allocated for it.
  • the primary entity of the first embodiment to the fifth embodiment may also use the primary RNC, and the secondary entity may also use the evolved base station, as shown in FIG. 2C, without affecting the implementation of the present invention.
  • a multicast router may be used between the SGSN and each of the main RNCs to transmit service data from the SGSN to each of the main RNCs.
  • the IP router deletes the routing entry corresponding to the IP multicast address, the multicast group, and the multicast group member.
  • control plane data in the above embodiments may also be forwarded by the primary RNC to the secondary RNC through the multicast router, without affecting the implementation of the present invention.
  • the primary entity may not configure the PDCP layer resource, and the service data received from the SGSN may not be processed by the PDCP layer, whether the PDCP layer is configured in the control message for the UE, or the PDCP parameter is carried on the MCCH. Indicates that the PDCP parameter does not need to be configured.
  • the sixth embodiment of the present invention provides a network system, where the network system includes: a main entity 11, an auxiliary device 12 of the main entity, a slave entity 13, and an attached device 14 of the entity;
  • the main entity 11 is configured to receive multicast multicast service data, and process the service data by using a radio link control RLC layer, a media access control MAC layer, and processing the data block obtained by the MAC layer.
  • the air interface sending time stamp is sent to the auxiliary device 12 of the main entity; the time stamp is sent on the data block processed by the main entity to form a data packet, and is sent to the slave entity 13;
  • the slave entity 13 is configured to perform corresponding processing on the received data packet according to the merge mode, and send the air interface sending time flag and the processed data block to be sent to the slave Auxiliary equipment of the body;
  • the slave device 12 of the slave entity is configured to send the data block to be sent when the air interface sending time arrives;
  • the auxiliary device 14 of the primary entity is configured to send the data block processed by the MAC layer when the air interface sending time arrives.
  • the primary entity is a radio network controller
  • an auxiliary device of the primary entity the secondary entity is a radio network controller
  • the secondary device of the secondary entity is a base station.
  • the primary entity is an evolved base station
  • the secondary device of the primary entity is a physical layer of the evolved base station
  • the secondary entity is an evolved base station
  • the secondary device of the secondary entity is the physical of the evolved base station.
  • the primary entity is a radio network controller, and the secondary device of the primary entity is a base station; the secondary entity is an evolved base station, and the secondary device of the secondary entity is a physical layer of the evolved base station.
  • the primary entity is an evolved base station
  • the secondary device of the primary entity is a physical layer of the evolved base station
  • the primary entity and the attached device of the primary entity are located on one physical entity.
  • the slave entity is an evolved base station, and the slave device of the slave entity is a physical layer of the evolved base station, and the slave device and the slave device of the slave entity are located on one physical entity.
  • the primary entity is further configured to: when the merge mode is an air interface merge, the primary entity specifies a physical layer resource that transmits the service data, or the primary entity negotiates with each slave entity to determine a transport location. a physical layer resource of the service data, and configuration information of the physical layer resource, and configuration information of the RLC layer and the MAC layer, and sent to the slave entity or configuration information according to the physical layer resource, and The configuration information of the RLC layer and the MAC layer is sent to the slave entity.
  • the merge mode is a soft merge
  • the soft merge mode and the configuration information of the RLC layer and the MAC layer are sent to the slave interface through the Iur interface.
  • the slave entity is further configured to: when the merge mode is an air interface merge, configure a physical layer resource according to configuration information of the physical layer resource, and configure configuration information of the physical layer resource and the received
  • the configuration information of the RLC layer and the MAC layer is combined to form a control message or a control message formed by the received primary RNC (the difference is that: the former is processed from the RRC of the entity, and the latter is unreasonable as long as it is unreasonable
  • the layer sends the control information to the UE; when the merge mode is the soft merge mode, the configuration information of the physical layer is configured autonomously, and the configuration information of the autonomously configured physical layer and the received RLC layer and the MAC layer are The configuration information is combined to form a control message, and the control information is sent to the UE through the Iur interface.
  • the main entity 11 adds an air interface transmission time stamp to the data block processed by the main entity, and adds an IP multicast address to form a data packet, and sends the data packet with the IP multicast address to the data packet.
  • the multicast router 15 is configured to forward the data packet with the IP multicast address to the slave entity 13 according to the routing information of the multicast group member corresponding to the IP multicast address.
  • an embodiment of the present invention further provides a network system, including: a main entity 11, an auxiliary device 12 of a main entity, a slave entity 13, and an attached device 14 of the entity;
  • the primary entity 11 is configured to receive multicast multicast service data, process the multicast multicast service data by using a radio link control RLC layer, and send the air interface sending time flag and the radio link control.
  • the data block obtained in the processing of the RLC layer is sent to the slave entity 13; the master entity processes the data processed by the radio link control RLC layer through the MAC layer, and sends the time stamp and the data processed by the MAC layer.
  • the block is sent to the accessory device 12 of the main entity;
  • the slave entity 13 is configured to send the air interface transmission time flag and the data block processed by the radio link control RLC layer to the accessory device of the slave entity after being processed by the MAC layer; the slave entity The accessory device 12 is configured to send, when the air interface sending time arrives, the data block processed by the MAC layer;
  • FIG. 17 is a structural diagram of a control plane for implementing an MBMS service data transmission process in the foregoing embodiment, where the SGSN may perform a session start process with an evolved base station or an RNC.
  • the seventh embodiment of the present invention provides a network element device, where the network element device may be an evolved base station or an RNC, and the device includes:
  • a receiving unit configured to receive multicast multicast service data
  • a processing unit configured to process the service data by using a radio link control RLC layer and media access control MAC layer;
  • a first sending unit configured to send the data block and the air interface sending time stamp processed by the MAC layer to its own accessory device
  • a second sending unit configured to add the air interface sending time flag to the data block obtained during the processing to form a data packet, and send the data packet.
  • the processing of the PDCP layer, the RLC layer, and the MAC layer of the MBMS service data is performed on the primary RNC, so that even if a packet is lost from the RNC, the PDCP state variable is not affected. The value does not affect subsequent packages.
  • the primary RNC sends the data packet to the physical layer of the primary RNC and the secondary RNC after the air interface transmission time stamp is added to each processed data block.
  • the physical layer of the primary RNC and the secondary RNC send the data block when the air interface transmission time arrives.
  • the transmission of the MBMS service can achieve temporal synchronization.
  • the resources of the control plane can be dynamically configured.
  • the resources of the physical layer occupied by the primary RNC and the RNC can be released when not in use. Therefore, the physical layer resources can be adjusted in time according to the system operation. The utilization efficiency is increased. For systems with frequent business changes or a large variety of services, the dynamic configuration of control plane resources is not prone to errors.

Landscapes

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

Abstract

La présente invention concerne un procédé de transmission de service de diffusion multimédia multidestinataire (MBMS), comprenant les étapes suivantes : une entité principale reçoit les données du MBMS; ces données de service sont traitées par l'entité principale par le biais d'une couche de contrôle de liaison radio (RLC) et d'une couche de contrôle d'accès au support (MAC), le bloc de données traité par la couche MAC et le signal horaire d'envoi de l'interface radio sont envoyés à un équipement auxiliaire de l'entité principale; le bloc de données reçu durant ce processus auquel est ajouté le signal horaire d'envoi de l'interface radio, pour la formation d'un paquet de données, est ensuite envoyé à une sous-entité; cette sous-entité envoie ce signal horaire d'envoi de l'interface radio et ce bloc de données traité par la couche MAC à un équipement auxiliaire de la sous-entité; à l'heure d'envoi de l'interface radio, l'équipement auxiliaire de la sous-entité et l'équipement auxiliaire de l'entité principale envoient le bloc de données traité par la couche MAC. En utilisant la solution de cette application, on réalise la transmission synchrone du service MBMS.
PCT/CN2008/072014 2007-08-15 2008-08-15 Procédé et système de réseau de transmission de service de diffusion multimédia multidestinataire (mbms) Ceased WO2009021467A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007100450249A CN101370156B (zh) 2007-08-15 2007-08-15 多播组播业务传输的方法和网络系统
CN200710045024.9 2007-08-15

Publications (1)

Publication Number Publication Date
WO2009021467A1 true WO2009021467A1 (fr) 2009-02-19

Family

ID=40350404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072014 Ceased WO2009021467A1 (fr) 2007-08-15 2008-08-15 Procédé et système de réseau de transmission de service de diffusion multimédia multidestinataire (mbms)

Country Status (2)

Country Link
CN (1) CN101370156B (fr)
WO (1) WO2009021467A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056084B (zh) * 2009-11-04 2016-02-10 中兴通讯股份有限公司 多媒体广播组播业务系统及其同步方法
EP3509329B1 (fr) 2016-09-29 2021-04-07 Huawei Technologies Co., Ltd. Procédé et système d'émission de service en multidiffusion
CN109982266B (zh) 2017-12-28 2021-05-11 华为技术有限公司 一种通信方法、及相关产品
CN115484553A (zh) * 2021-05-31 2022-12-16 华为技术有限公司 一种通信方法及装置
CN118708694B (zh) * 2024-07-08 2025-01-10 广东联想懂的通信有限公司 一种人工智能汽车自动问答方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1457165A (zh) * 2002-05-03 2003-11-19 三星电子株式会社 移动通信系统中多媒体广播/多播服务的设备和方法
CN1496139A (zh) * 2002-07-31 2004-05-12 ���ǵ�����ʽ���� 移动通信系统中提供多媒体广播/多播业务的设备和方法
CN1684414A (zh) * 2004-04-14 2005-10-19 华为技术有限公司 一种多媒体广播/组播业务的会话开始方法
WO2007029708A1 (fr) * 2005-09-08 2007-03-15 Ntt Docomo, Inc. Système d’émission de données, nœud de communication et méthode d’émission de données
CN101043641A (zh) * 2007-03-07 2007-09-26 中兴通讯股份有限公司 一种rnc间mbms数据同步方法及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450199C (zh) * 2004-10-21 2009-01-07 华为技术有限公司 实现无线广播多播业务同步发送的系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1457165A (zh) * 2002-05-03 2003-11-19 三星电子株式会社 移动通信系统中多媒体广播/多播服务的设备和方法
CN1496139A (zh) * 2002-07-31 2004-05-12 ���ǵ�����ʽ���� 移动通信系统中提供多媒体广播/多播业务的设备和方法
CN1684414A (zh) * 2004-04-14 2005-10-19 华为技术有限公司 一种多媒体广播/组播业务的会话开始方法
WO2007029708A1 (fr) * 2005-09-08 2007-03-15 Ntt Docomo, Inc. Système d’émission de données, nœud de communication et méthode d’émission de données
CN101043641A (zh) * 2007-03-07 2007-09-26 中兴通讯股份有限公司 一种rnc间mbms数据同步方法及系统

Also Published As

Publication number Publication date
CN101370156A (zh) 2009-02-18
CN101370156B (zh) 2012-05-23

Similar Documents

Publication Publication Date Title
US12323855B2 (en) TSC-5G QoS mapping with consideration of assistance traffic information and PCC rules for TSC traffic mapping and 5G QoS flows binding
EP2074842B1 (fr) Distribution efficace de services mbms sur une épine dorsale en utilisant une approche sur un seul tunnel
US8656029B2 (en) Multicast session setup in networks by determining a multicast session parameter based on a pre-existing unicast session parameter
KR100943901B1 (ko) 방송 및 멀티캐스트를 위한 무선 프로토콜 엔터티 공유방식
KR101065448B1 (ko) 무선통신시스템에 사용되는 일대다 ｍｂｍｓ 처리방법 및 장치
JP2022535385A (ja) ＴＳＮおよび５ＧＳ ＱｏＳマッピング－ユーザプレーンベースの方法
US8411680B2 (en) IP multicasting system and a method based on the mobile network
CN111556540B (zh) Smf实体执行的方法及smf实体、pcf实体执行的方法及pcf实体
WO2008043297A1 (fr) Procédé, système et noeud de réseau pour commande de support, suppression de support et transmission de données
WO2009039777A1 (fr) Procédé, système et appareil destinés à organiser des données
WO2007112696A1 (fr) Procédé et système permettant de créer un service de multidiffusion/radiodiffusion multimédia
JP2012054990A (ja) 移動通信システム、マルチキャストデータ配信方法、コアネットワークノード、アクセスネットワークノード、および端末
WO2009076864A1 (fr) Méthode et dispositif de réseau servant à établir un tunnel gtp point à multipoint
CN111901764A (zh) 广播/组播业务的管理方法、装置、电子设备和存储介质
CN101304550B (zh) 提供多媒体广播/组播业务的方法及系统
CN114374993B (zh) 一种5g-tsn终端网关
WO2009021467A1 (fr) Procédé et système de réseau de transmission de service de diffusion multimédia multidestinataire (mbms)
KR100956817B1 (ko) 패킷 데이터를 처리하는 방법 및 이를 위한 장치
US20230189364A1 (en) Signaling for multicast broadcast services
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
WO2010124421A1 (fr) Procédé, bm-sc et station de base pour multiplexage de services mbms dans mbsfn
CN115734170B (zh) 一种组播/广播会话管理方法及通信装置
WO2009009939A1 (fr) Procédé de synchronisation de la diffusion/multidiffusion multimédia
WO2009062436A1 (fr) Procédé de réglage de synchronisation pour service multidiffusion de radiodiffusion multimédia et station de base améliorée
WO2008040202A1 (fr) Procédé, appareil et système de transmission de services mbms dans un réseau de trafic ip

Legal Events

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

Ref document number: 08784005

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08784005

Country of ref document: EP

Kind code of ref document: A1