WO2008046348A1 - Système, dispositif et procédé permettant de commander le changement de mode de transmission - Google Patents

Système, dispositif et procédé permettant de commander le changement de mode de transmission Download PDF

Info

Publication number
WO2008046348A1
WO2008046348A1 PCT/CN2007/070881 CN2007070881W WO2008046348A1 WO 2008046348 A1 WO2008046348 A1 WO 2008046348A1 CN 2007070881 W CN2007070881 W CN 2007070881W WO 2008046348 A1 WO2008046348 A1 WO 2008046348A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
multicast
entity
bearer change
change notification
Prior art date
Application number
PCT/CN2007/070881
Other languages
English (en)
French (fr)
Inventor
Jianfeng Zhong
Geng Wang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP07817072A priority Critical patent/EP2066077A4/en
Publication of WO2008046348A1 publication Critical patent/WO2008046348A1/zh
Priority to US12/420,318 priority patent/US20090196213A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • 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/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1868—Measures taken after transmission, e.g. acknowledgments
    • 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/1895—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for short real-time information, e.g. alarms, notifications, alerts, updates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information

Definitions

  • the present invention relates to mobile communication technologies, and more particularly to a system, apparatus and method for controlling bearer changes. Background of the invention
  • MBMS multicast and broadcast services
  • Multicast services refer to multiple data sources.
  • the method can save bandwidth and realize network resource sharing, including resource sharing between the mobile core network and the access network, especially the air interface resource sharing.
  • MBMS defined by 3GPP can not only achieve plain text low-rate message-like multicast and broadcast, but also enable high-speed multimedia service multicast and broadcast.
  • the MBMS service is implemented by adding some new network functional entities and adding MBMS functional support to existing network entities.
  • a functional entity broadcast multicast service center (BM-SC) is added; and an existing network entity involved, such as a GPRS service support node (SGSN), is added.
  • SGSN GPRS service support node
  • GGSN GPRS Service Gateway Node
  • RNC/BSC Radio Network Controller/Base Station Controller
  • RAN Radio Access Network
  • UE User Equipment
  • MBMS IP Multimedia Subsystem
  • the service will be terminated, so that the session cannot be continued, or the user feels that the quality of the multicast communication is degraded.
  • the user wants to convert the multicast to the unicast mode for communication, or the user is willing to convert the unicast bearer into a multicast bearer, or the system has many If the broadcast bearer resource is abnormal, the system needs to convert the multicast bearer into a unicast bearer to keep the user service going.
  • embodiments of the present invention provide a system, apparatus, and method for controlling bearer changes in order to meet the need for a bearer to be converted when a terminal or network multicast capability or user desire changes.
  • the bearer change notification entity is configured to learn information that the bearer needs to be changed, and send a change notification to the bearer change control entity;
  • a bearer change control entity configured to determine, according to the received bearer change notification, a transition of the bearer mode between unicast and multicast.
  • a bearer change learning module configured to learn information that the bearer needs to be changed, and send a bearer change indication to the sending module
  • a sending module configured to send a bearer change notification to the bearer change control entity according to the received bearer change indication.
  • a receiving module configured to receive a bearer change notification from the bearer change notification entity, and send the received bearer change notification to the single/multicast establishment control module;
  • the single/multicast establishment control module is configured to determine and control the conversion of the bearer mode between unicast and multicast according to the bearer change notification from the receiving module.
  • the bearer change control entity receives the bearer change notification sent by the bearer change notification entity when the bearer needs to change the information
  • the bearer change control entity determines and controls the conversion of the bearer mode between unicast and multicast according to the received bearer change notification.
  • the bearer change notification entity learns that the bearer needs to be changed, such as the terminal multicast capability and/or the network multicast capability and/or the user's will change, and sends the change to the bearer change control entity. And the bearer change control entity determines, according to the received bearer change notification, the transition from the multicast bearer mode to the unicast bearer mode, or the unicast bearer mode to the multicast bearer mode. The data transmission of the unicast or multicast bearer mode is established for the UE.
  • the smooth transition of the multicast bearer mode to the unicast bearer mode, or reverse conversion enables the bearer mode to be appropriately adjusted according to the terminal multicast capability or the network multicast capability or the user's will, and the service continuity capability is provided. At the same time, it also meets the individual needs of users.
  • FIG. 1 is an exemplary flowchart of a method for controlling bearer change according to an embodiment of the present invention
  • FIG. 2 is an exemplary structural diagram of a system for controlling bearer change according to an embodiment of the present invention
  • FIG. 3 is a specific application of an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for controlling bearer change according to Embodiment 1 of the present invention
  • FIG. 5 is a flowchart of a method for controlling bearer change according to Embodiment 2 of the present invention
  • FIG. 7 is a flowchart of a method for controlling bearer change according to Embodiment 4 of the present invention
  • 8 is a flowchart of a method for controlling bearer change according to Embodiment 5 of the present invention
  • FIG. 10 is a flowchart of a method for controlling bearer change according to Embodiment 7 of the present invention. Mode for carrying out the invention
  • the bearer change notification entity learns that the bearer needs to be changed, such as the terminal multicast capability and/or the network multicast capability and/or the change of the user's will, and sends a bearer change notification to the bearer change control entity;
  • the control entity determines, according to the received bearer change notification, the transition from the multicast bearer mode to the unicast bearer mode, or the unicast bearer mode to the multicast bearer mode.
  • the bearer change notification may be a multicast deactivation notification, or may be a multicast activation notification or the like.
  • the capability of business continuity can be provided, and the personalized requirements of the user can also be satisfied.
  • the bearer change notification entity learns that the multicast capability is lost, that is, the bearer mode needs to be changed from the multicast bearer to the unicast bearer, and then the multicast change deactivation notification is sent to the bearer change control entity; Broadcasting the activation notification, determining the transition from the multicast bearer mode to the unicast bearer mode, and controlling the establishment of the unicast bearer mode data transmission; or, the bearer change notification entity is informed of the multicast capability condition permission and demand, that is, the bearer mode needs to be If the broadcast bearer is changed to a multicast bearer, the multicast change notification is sent to the bearer change control entity; the bearer change control entity determines, according to the received multicast activation notification, that the unicast bearer mode is converted to the multicast bearer mode, and the control establishment is performed. Data transmission in the broadcast mode.
  • the multicast deactivation notification may be a multicast deactivation message, a media re-negotiation request, or other internal notification messages.
  • the multicast activation notification may be a multicast activation message, a media renegotiation request, or other internal notification messages.
  • the manner in which the bearer change notification entity learns that the bearer needs to be changed may also be in various manners, such as a change in the user's will, an access network report, and a bearer change notification entity itself.
  • FIG. 1 there is shown an exemplary flow chart of a method for performing a change in the embodiment of the present invention.
  • the process includes the following steps:
  • Step 101 The bearer change notification entity learns that the bearer needs to be changed, and sends a change notification to the bearer change control entity.
  • the information that needs to be changed by the bearer includes: terminal multicast capability and/or network multicast capability and/or change information of the user's will, and the like.
  • the bearer change notification entity obtains the change of the terminal multicast capability and/or the network multicast capability and/or the user's will.
  • the user may select the bearer mode by using the UE according to the individual's will, and the UE further sends the bearer change information to the bearer change notification entity.
  • the notification entity learns the change of the user's will from the bearer change information, and the bearer needs to be changed; or when the UE moves from one area to another, the bearer change control entity can learn from the network whether the new area supports the multicast capability information, such as the UE.
  • the access network senses that the target network does not support the multicast capability, and sends a multicast deactivation message to the bearer change notification entity, and the bearer change notification entity goes according to the received multicast.
  • the bearer change notification entity may default to the multicast capability loss, and the bearer needs to be changed.
  • the terminal determines the quality status of the multicast bearer, and accordingly sends the bearer change information to the bearer change notification entity.
  • the change notification entity learns that the bearer needs to be changed according to the bearer change information; or when the network multicast bearer resource is congested or abnormal, the network resource management device sends the bearer change information to the bearer change notification entity, and the bearer change notification entity learns according to the bearer change information. Bearer needs Change and so on.
  • the foregoing area may be an area covered by an SGSN, or an area covered by a RAN unit (such as an RNC).
  • the application of the MBMS in the IMS service is taken as an example.
  • the 7-load change notification entity may be the UE, and the change control entity may be the AS or the UE; or the change notification entity may also be the BM-SC, and the change control entity may For AS.
  • Manner 1 The change notification entity is a UE, and the change control entity is an AS or
  • the method for the UE to know the information that needs to be changed is: the UE receives the bearer change operation from the user; or the UE receives the bearer change information from the network, such as the capability information of whether the network from the SGSN or the RAN supports the multicast; or the UE itself generates Bear the change operation.
  • the UE learns the bearer change according to the foregoing method, and sends a bearer change notification to the bearer change control entity AS or UE.
  • Example 1 When RAN migration occurs, to ensure service continuity, the unicast handover in the prior art is used to determine the pre- bearer mode.
  • the multicast bearer is converted to the unicast bearer mode.
  • the serving RAN Before the handover is performed, the serving RAN first sends a multicast deactivation indication to the UE. If the UE initiates a media renegotiation message to the network side, and after the negotiation is completed, the control will multicast.
  • the bearer mode is converted to the unicast bearer mode. In this case, the UE is both the bearer change notification entity and the bearer change control entity.
  • the UE sends the bearer change notification to the AS
  • the UE is the bearer change notification entity
  • the AS is ⁇ ⁇ Load change control entity.
  • the serving SGSN sends a multicast deactivation message to the GGSN, and simultaneously sends a multicast deactivation message to the UE through the RAN, and the UE goes according to the multicast. Activate the message and send a bearer change notification to the AS.
  • the UE is a bearer change notification entity.
  • the AS is a bearer change control entity.
  • Example 2 The user finds that the signal transmitted by the multicast is not good, and manually initiates the operation of switching to unicast; or the UE determines according to the quality of the network transmission, and decides to perform the transition from multicast to unicast.
  • the control converts the multicast bearer mode into a unicast bearer mode.
  • the UE is both a bearer change notification entity and a bearer change control entity; if the UE sends a bearer change to the AS Notification, at this time, the UE is a bearer change notification entity, and the AS is a bearer change control entity.
  • the bearer change notification may be a multicast capability change message, for example, the user equipment sends information to the AS whether it supports the multicast capability, and the information supporting the multicast capability is used to request the multicast bearer, and does not support the multicast capability information. Used to request the use of unicast bearers.
  • the bearer change notification entity is a BM-SC
  • the bearer change control entity is an AS.
  • the method for the BM-SC to learn the information that needs to be changed is: the BM-SC receives an activation or deactivation request operation of the multicast bearer from the terminal; or the BM-SC receives the bearer change operation from the access network; or the BM-SC generates The operation that carries the change.
  • the BM-SC learns the bearer change according to the above method, and sends a bearer change notification to the bearer change control entity.
  • Example a The user finds that the signal transmitted by the multicast is not good, and manually initiates the handover to the unicast operation; or the UE judges according to the network transmission quality. A decision is made to perform a multicast-to-unicast transition, and a multicast deactivation notification is sent to the BM-SC, and the BM-SC reports a multicast deactivation notification to the AS.
  • Example b When the SGSN migration occurs, the target SGSN indicates the multicast capability information of the target access network to the serving SGSN. If the multicast capability information of the target access network does not support the multicast capability, the serving SGSN sends the SGSN to the GGSN. Multicast deactivation message, the GGSN sends the received multicast deactivation message to the BM-SC, and the BM-SC sends a multicast deactivation notification to the AS according to the multicast deactivation message, and the multicast deactivation notification Can go for multicast The message is activated and can be transmitted using an Initial Session Protocol (SIP) message.
  • SIP Initial Session Protocol
  • Example c The BM-SC autonomously generates a bearer change operation and sends a multicast deactivation notification to the AS.
  • the multicast deactivation notification is a bearer change notification.
  • the specific process for the serving SGSN to send the multicast deactivation message to the UE by using the RAN may be: the serving SGSN first sends the multicast deactivation message to the RNC/BSC in the RAN, and the RNC/BSC sends the multicast deactivation message to the UE. .
  • the multicast capability information of the target access network may include: multicast capability information of the target SGSN; or multicast capability information of the target radio access network RAN; or target SGSN and target
  • Multicast capability information of the RAN Multicast capability information of the RAN.
  • the case of transitioning from a unicast bearer mode to a multicast bearer mode is similar to the case of transitioning from a multicast bearer mode to a unicast bearer mode.
  • Step 102 The bearer change control entity determines, according to the received notification, the transition from the multicast bearer mode to the unicast bearer mode, or the unicast bearer mode to the multicast bearer mode.
  • the bearer change control entity may further detect a service such as a session, and if the service is in progress, control the bearer conversion.
  • the AS may determine, according to the received bearer change notification, the transition from the multicast mode to the unicast mode, and control to re-establish the transmission of the unicast bearer mode, and maintain the service. Continued; or determine the transition from the unicast bearer mode to the multicast bearer mode, and control to re-establish the transmission of the multicast bearer mode.
  • the user equipment may initiate media renegotiation to the bearer change control entity, notify the bearer change control entity of the bearer change, and request to establish a single/multicast bearer.
  • the UE may change according to the received bearer.
  • the notification is changed, and the transition from the multicast bearer mode to the unicast bearer mode is determined, or the unicast bearer mode is determined to be converted to the multicast bearer mode.
  • the unicast bearer mode is converted to the unicast bearer mode, or the unicast bearer mode is converted to the multicast bearer mode.
  • Fig. 2 is an exemplary structural diagram of a system for performing a change in the embodiment of the present invention. As shown in FIG. 2, the system includes: a bearer change notification entity 200, and a bearer change control entity 210.
  • the bearer change notification entity 200 is configured to learn the information that the bearer needs to be changed, and send a change notification to the bearer change control entity 210.
  • the bearer change control entity 210 is configured to receive the bearer change notification from the bearer change notification entity, determine and control the transition from the multicast bearer mode to the unicast bearer mode, or the unicast bearer mode to the multicast bearer according to the received bearer change notification. Way to convert.
  • the bearer change notification entity 200 can have many specific implementation manners, as long as the foregoing functions can be implemented. Only one specific implementation is listed below. As shown in FIG. 2, the bearer change notification entity 200 may include a bearer change learning module 201 and a sending module 202.
  • the bearer change learning module 201 is configured to learn information that the bearer needs to be changed, and send a bearer change indication to the sending module 202.
  • the sending module 202 is configured to receive the bearer change indication from the bearer change learning module 201, and send a bearer change notification to the bearer change control entity 210 according to the received bearer change indication.
  • the bearer change learning module 201 and the sending module 202 may be integrated to receive information about the bearer that needs to be changed, and send a bearer change notification to the bearer change control entity 210.
  • the bearer change control entity 210 can have many specific implementation manners, as long as the foregoing functions can be implemented. Only one specific implementation is listed below, as shown in FIG. 2,
  • the bearer change control entity 210 may include: a receiving module 211 and a single/multicast establishing control module 212, where
  • the receiving module 211 is configured to receive the bearer change notification from the bearer change notification entity, and send the received bearer change notification to the single/multicast setup control module 212;
  • the unicast/multicast setup control module 212 is configured to determine and control the transition from the multicast bearer mode to the unicast bearer mode according to the bearer change notification from the receiving module 211, or to convert the unicast bearer mode to the multicast bearer mode.
  • the receiving module 211 and the single/multicast establishing control module 212 may be integrated to receive a bearer change notification from the bearer change notification entity, and determine and control the multicast bearer mode to the unicast bearer according to the received notification. Mode conversion, or conversion from unicast bearer mode to multicast bearer mode.
  • the specific implementation of the single/multicast bearer control module 212 may include: a single/multicast bearer mode establishing module and a data transmission converting module.
  • the single/multicast bearer mode establishing module is configured to determine, according to the bearer change notification from the receiving module, the transition from the multicast bearer mode to the unicast bearer mode, and initiate the unicast bearer mode establishment process, or by unicast The mode is switched to the multicast mode, and a unicast established notification message is sent to the data transmission conversion module when the establishment is completed, or the multicast established notification message is generated.
  • the data transmission conversion module is configured to convert the data transmission from the multicast channel to the unicast channel according to the received unicast established notification message, or the multicast established notification message.
  • the labor can be transformed into a plurality of specific implementation forms of the bearer change notification entity 200 and the bearer change control entity 210, such as splitting or merging the above modules, which are not repeated here.
  • the system can further include: an access network entity 220.
  • the access network entity 220 is configured to notify the bearer change when the bearer needs to be changed.
  • the body 200 transmits bearer change information; the bearer change notification entity 200 receives bearer change information from the access network entity 220, and performs an operation of learning that the bearer needs to be changed, and transmits a multicast deactivation notification to the sending module.
  • the specific implementation may be completed by the bearer change learning module 201 in the bearer change notification entity 200.
  • the access network entity 220 may include: a target SGSN, a serving SGSN, and a GGSN.
  • the target SGSN is configured to send multicast capability information of the target access network to the service SGSN.
  • the serving SGSN is configured to receive the multicast capability information of the target SGSN, and according to the received multicast capability information, determine that the bearer needs to be changed, and send a bearer change message to the GGSN.
  • the GGSN is configured to receive a bearer change message from the serving SGSN, and send a 7-layer change notification to the BM-SC according to the received 7-load change message.
  • the access network entity 220 may include: a target SGSN, a serving SGSN.
  • the target SGSN is configured to send multicast capability information of the target access network to the service SGSN.
  • the serving SGSN is configured to receive the multicast capability information of the target SGSN, and according to the received multicast capability information, when determining that the bearer needs to be changed, the bearer may send a bearer change message to the UE by using the RAN.
  • the access network entity 220 may also be a RAN.
  • the RAN is used to determine that the bearer change message is sent to the UE in the multicast bearer mode when the network area is migrated.
  • the process for the serving SGSN to send the bearer change message to the UE by using the RAN may include: the serving SGSN first sending the bearer change message to the RNC/BSC in the RAN, where The RNC/BSC sends a bearer change message to the UE.
  • the load change control entity 210 may be an AS.
  • the load change control entity 210 may also be a UE.
  • a SIP interface may be employed between the bearer change notification entity 200 and the bearer change control entity 210.
  • FIG. 3 is a schematic structural diagram of a networking system of a specific application according to an embodiment of the present invention.
  • the networking system includes: UE301, RAN302, SGSN303, GGSN304, BM-SC305, AS306, Call Session Control Function Entity (CSCFs) 307, and Home Subscriber Server (HSS) 308.
  • CSCFs Call Session Control Function Entity
  • HSS Home Subscriber Server
  • the UE 301 supports activation and deactivation of the MBMS multicast service.
  • the AS 306 is configured to control the IMS service that uses the MBMS multicast, and is configured to receive the multicast capability information from the UE, and determine, according to the received multicast capability information, the unicast bearer mode or the multicast bearer mode of the UE 301, and the control network. Establish a corresponding bearer mode for data transmission.
  • the BM-SC 305 is an entry for content providers to authorize and initiate MBMS multicast bearer services and to deliver MBMS content on a scheduled schedule. Its functions include: (1) authentication, authorization, and accounting for third-party content providers; (2) providing MBMS transmission-related parameters, such as QoS, multicast broadcast areas; initiating and terminating MBMS transmission resources; The external data source receives and transmits the MBMS content, schedules the MBMS session transmission and informs the user; Retransmission, etc.; (4) Service statement, including media description, session description such as multicast service identity, address, transmission time, etc.
  • the RAN 302 includes a Universal Terrestrial Radio Access Network (UTRAN) and a Global System for Mobile Communications (GSM)/Enhanced GSM (EDGE) Access Network (GERAN), etc., and transmits MBMS data in a predetermined multicast or broadcast service area through the RNC/BSC.
  • UTRAN Universal Terrestrial Radio Access Network
  • GSM Global System for Mobile Communications
  • EDGE Enhanced GSM
  • GERAN Global System for Mobile Communications
  • GERAN Global System for Mobile Communications
  • GERAN Global System for Mobile Communications
  • GERAN Global System for Mobile Communications
  • GERAN Global System for Mobile Communications
  • the SGSN 303 performs network control on the user, supports the movement of the MBMS receiver between the SGSNs, and establishes or releases the bearer connection with the RAN and the GGSN according to the notification sent by the GGSN.
  • the GGSN 304 acts as an IP multicast service node of the MBMS data, and establishes or releases a user plane bearer for the multicast service transmission according to the BM-SC notification request; receives the IP multicast content from the BM-SC or other data source, and performs routing.
  • CSCFs 307 and HSS 308 are used to complete session establishment and authentication.
  • the CSCFs include: Proxy CSCF (P-CSCF), Query CSCF (I-CSCF), and Monthly CSCF (S-CSCF).
  • the BM-SC 305 and the UE 301 can also function as the bearer change notification entity 200, and the AS 306 can serve as the bearer change control entity 210.
  • the BM-SC 305 or the UE 301 is further configured to learn that the bearer needs to be changed, and send a bearer change notification to the AS 306.
  • the AS 306 is further configured to receive a bearer change notification from the BM-SC 305 or the UE 301, and determine, according to the received bearer change notification, The multicast bearer mode is switched to the unicast bearer mode, and the data transmission of the unicast bearer mode is controlled.
  • the unicast bearer mode is determined to be converted to the multicast bearer mode, and the data transmission of the multicast bearer mode is controlled.
  • the BM-SC 305 or the UE 301 may include the load change learning module 201 and the sending module 202 shown in FIG. 2, and the function may also be consistent with the description in FIG. 2.
  • the AS 306 may include the receiving module 211 and the single/multiple shown in FIG.
  • the broadcast establishment control module 212 the function can also be consistent with the description in FIG. 2.
  • the target SGSN 303 can access the network to the target.
  • the multicast capability information is sent to the serving SGSN 303.
  • the serving SGSN 303 receives the multicast capability information of the target access network, and according to the received multicast capability, determines that the bearer needs to be changed, and sends a bearer change message to the GGSN 304, and then the GGSN 304 sends the BMSN to the BM.
  • the SC 305 transmits a bearer change message; or the serving SGSN 303 transmits a bearer change message to the UE 301 through the RAN 302.
  • the RAN determines to convert the multicast mode into a unicast bearer mode in advance, and sends a bearer change message to the UE 301 in the multicast bearer mode.
  • the multicast capability information of the target access network includes: multicast capability information of the target SGSN 303; or multicast capability information of the target radio access network RAN 302; or multicast capability information of the target SGSN 303 and the target RAN 302.
  • the UE 301 can also function as the bearer change control entity 210. Then, the RAN 302 determines that the bearer needs to be changed, and sends a bearer change notification to the UE 301 through the RNC/BSC. The UE 301 is further configured to receive the bearer change notification from the RAN 302, and determine, according to the received bearer change notification, the transition from the multicast bearer mode to the unicast bearer mode. Controlling the establishment of data transmission in the unicast bearer mode, or converting from the unicast bearer mode to the multicast bearer mode, and controlling the data transmission of the multicast bearer mode.
  • the UE 301 may include the bearer change learning module 201 and the single/multicast setup control module 212 shown in FIG. 2, that is, since the UE 301 is both a change notification notification entity and a change control entity, the FIG. 2 is shown in FIG.
  • the bearer change notification entity and the bearer change control entity are combined.
  • the bearer change learning module 201 and the sending module 202 are integrated, and the receiving module 211 and the single I multicast establishing control module 212 are integrated.
  • the function of each module can be consistent with the description in Figure 2.
  • the bearer change notification may be a multicast deactivation message or a multicast deactivation notification.
  • Embodiment 1 Corresponding to the case of the example b in the step 101 shown in FIG. 1, and the case when the SGSN migration occurs in the example 1.
  • the UE has a multicast capability
  • the service access network that initially establishes the session has a multicast capability
  • the multicast bearer mode is established.
  • the target access network does not have the network.
  • Multicast capability that is, the UE moves from a supported multicast area to an area that does not support multicast.
  • the service RAN in the service access network is recorded as RAN0
  • the service SGSN is recorded as SGSN0
  • the target RAN in the target access network is recorded as RAN1
  • the target SGSN is recorded as SGSN1.
  • FIG. 4 is a flowchart of a method for controlling bearer change according to Embodiment 1 of the present invention. Some steps in the process are the existing steps in the prior art, and for the sake of highlighting the flow of the present invention, some of the same processes in the prior art are not described in detail in FIG.
  • the information exchange is represented by a hexagonal overlay, the entity covered by the hexagon is represented by the interaction process, and the other method flow diagrams in this paper are also processed in this way.
  • the process includes the following steps:
  • Step 401 The multicast bearer mode session is in progress.
  • Step 402 The network area migration occurs, and the UE moves from the RAN0, SGSN0 area to the RAN1, SGSN1 area, that is, the UE moves from the service access network to the target access network.
  • Step 406 to step 407 the RAN1 establishes a radio resource according to the received migration request, and returns a migration confirmation message to the SGSN1 to confirm that the radio resource has been established.
  • Step 408 After receiving the migration confirmation message from RAN1, the SGSN1 sends a migration response message to the SGSN0.
  • the migration response message sent by the SGSN1 to the SGSN0 carries the target connection.
  • the multicast capability information of the network may include: multicast capability information of the SGSN1; or multicast capability information of the RAN1; or multicast capability information of the SGSN1 and the RAN1.
  • the multicast capability information of the target access network does not support multicast, that is, does not have multicast capability.
  • Step 409 to step 410 after receiving the migration response message from the SGSN1, the SGSN0 sends a migration command to the RAN1, and the RAN1 controls the migration process.
  • Step 411 The SGSN0 obtains, from the migration response message in step 408, that the target access network does not have multicast capability, and then initiates a multicast deactivation process, and sends a multicast deactivation message to the GGSN.
  • Step 412 After receiving the multicast deactivation message, the GGSN sends a multicast deactivation message to the BM-SC, that is, a multicast deactivation notification.
  • Step 413 The BM-SC sends a multicast deactivation message to the AS according to the received multicast deactivation notification.
  • the BM-SC sends a multicast deactivation notification to the AS according to the received multicast deactivation message.
  • the multicast deactivation message may be sent to the AS.
  • the indicated SIP protocol message can be deactivated for carrying the multicast.
  • Step 414 The AS control network establishes a unicast bearer mode for data transmission.
  • the AS may further determine whether the current session still exists, that is, whether the session termination notification message is received. If the session still exists, that is, the session termination notification message is not received, then the multicast mode is determined to be In the unicast mode, the control network establishes a unicast bearer mode for data transmission, thereby maintaining the continuity of services such as sessions.
  • the unicast bearer mode is established, and when the unicast bearer mode is established, the data transmission is performed from the multicast.
  • the channel is switched to a unicast channel.
  • steps 411 to 414 and steps 409 to 410 can be performed simultaneously.
  • the step 411 further includes: when the SGSN0 sends the multicast deactivation message to the GGSN, the multicast deactivation message may be sent to the UE by using the RAN0.
  • the UE sends a bearer change notification to the AS according to the received multicast deactivation message.
  • the UE may send a change notification to the AS through a SIP protocol message, where the change notification may be multicast. Capability change notification message.
  • the BM-SC still processes according to the prior art, that is, terminates the multicast transmission resource without sending a multicast deactivation notification to the AS.
  • the functions performed by the RAN0 and the RAN1 control are all completed by the RNC/BSC control in the RAN.
  • Embodiment 2 Corresponding to the case where the RAN migration occurs in the example 1 in the step 101 shown in FIG. 1, the UE is both a bearer change notification entity and a bearer change control entity.
  • the application scenario is still the same as in the first embodiment. That is, the UE has the multicast capability, and the service access network that initially establishes the session has the multicast capability, and the multicast bearer mode has been established.
  • the target access network does not have the multicast capability. That is, the UE moves from a supported multicast area to an area that does not support multicast.
  • FIG. 5 is a flowchart of a method for controlling bearer change according to Embodiment 2 of the present invention. The process includes the following steps:
  • Steps 501 to 502 are the same as steps 401 to 402 in the flow shown in FIG. 4, that is, the multicast bearer mode session is in progress, network area migration occurs, and the UE moves from the RAN0 and SGSN0 areas to the RANI and SGSN1 areas, that is, the UE The service access network moves to the target access network.
  • Step 503 The RAN0 sends a multicast deactivation notification to the UE.
  • the RAN0 learns that the UE wants to perform network migration. To ensure the continuity of the service, the unicast to unicast switching in the prior art is implemented, and the operation of step 403 in the process shown in FIG. 4 is not performed temporarily.
  • the SGSN0 sends a migration request, but first sends a multicast deactivation notification to the UE, and the notification can be sent through a SIP message.
  • Steps 504 to 505 the UE receives the multicast deactivation notification from the RAO, determines the transition from the multicast bearer mode to the unicast bearer mode, initiates a media renegotiation process, and converts the multicast bearer mode into a unicast bearer mode, and establishes After unicast, data is received on a unicast channel.
  • the process of initiating the unicast bearer mode is to initiate a media renegotiation process, and when the unicast bearer mode is established, the data transmission is switched from the multicast channel to the unicast channel, that is, the data is received on the unicast channel.
  • Step 506 After the unicast establishment is completed, send a unicast bearer mode setup response to the RAN0. Steps 507 to 515 are the same as steps 403 to 410 in the flow shown in FIG. 4, and the migration process is completed.
  • the functions performed by the RAN0 and the RAN1 control are all completed by the RNC/BSC control in the RAN.
  • Embodiment 3 In the example 2 in step 101 shown in FIG. 1, the UE is a 7-load change notification entity, and the AS is a bearer change control entity.
  • the UE has the multicast capability, and the service access network that initially establishes the session has the multicast capability, and the multicast bearer mode is established.
  • the user decides according to the user's will or the network transmission quality. To perform a multicast to unicast transition.
  • FIG. 6 is a flowchart of a method for controlling bearer change according to Embodiment 3 of the present invention. The process includes the following steps:
  • Step 601 the session is in progress.
  • Step 602 The user finds that the signal transmitted by the multicast is not good, and manually initiates the operation of switching to the unicast. Or the UE judges according to the quality of the network transmission, and decides to perform the transition from multicast to unicast.
  • Step 603 The UE sends a bearer change notification to the AS.
  • the bearer change notification may be a multicast capability change notification message.
  • the multicast capability change notification message may be sent to the AS through the SIP protocol message.
  • the information about whether the UE supports the multicast capability is included in the broadcast capability change notification message.
  • the information supporting the multicast capability is used to request the use of the multicast bearer, and the information that does not support the multicast capability is used to request the unicast bearer.
  • the multicast capability change notification message carries information that the UE does not currently support the multicast capability.
  • Step 604 After receiving the bearer change notification, the AS determines that it needs to control the transition of the multicast to the unicast bearer.
  • Step 605 The AS initiates a unicast establishment process.
  • Step 606 After the unicast is successfully established, the UE receives the downlink data on the unicast channel.
  • Embodiment 4 Corresponding to the example 2 in step 101 shown in FIG. 1, the UE is both a 7-load change notification entity and a load change control entity.
  • the application scenario is still the same as in the first embodiment. That is, the UE has multicast capability, and the service access network that initially establishes the session has multicast capability, and has established a multicast bearer mode. During the session, according to the user's will or according to the network transmission quality, it is decided to perform multicast. The transition to unicast.
  • FIG. 7 is a flowchart of a method for controlling bearer change according to Embodiment 4 of the present invention. The process includes the following steps:
  • Step 701 the session is in progress.
  • Step 702 The user finds that the signal transmitted by the multicast is not good, and manually initiates the operation of switching to the unicast. Or the UE judges according to the quality of the network transmission, and decides to perform the transition from multicast to unicast.
  • Step 703 The UE initiates a unicast establishment process by initiating media renegotiation.
  • Step 704 After the unicast is successfully established, the UE receives downlink data on the unicast channel.
  • Step 705 The UE initiates an MBMS deactivation process to release the multicast resource.
  • Embodiment 5 Corresponding to the case in the example a in the step 101 shown in FIG.
  • the UE has the multicast capability, and the service access network that initially establishes the session has the multicast capability, and the multicast bearer mode is established.
  • the user decides according to the user's will or the network transmission quality. To perform a multicast to unicast transition.
  • FIG. 8 is a flowchart of a method for controlling bearer change according to Embodiment 5 of the present invention. The process includes the following steps:
  • Step 801 the session is in progress.
  • step 802 the user finds that the signal transmitted by the multicast is not good, and manually initiates the operation of switching to unicast. Or the UE judges according to the quality of the network transmission, and decides to perform the transition from multicast to unicast.
  • Step 803 The UE initiates a deactivation process of the MBMS.
  • the UE initiates the MBMS deactivation process as an existing process, and thus can be processed according to the prior art.
  • Step 804 After receiving the deactivation message, the BM-SC reports the bearer change notification to the AS. In this step, the BM-SC sends a bearer change notification to the AS after receiving the activation message according to the MBMS deactivation procedure in the prior art.
  • Step 805 After receiving the bearer change notification, the AS finds that the user does not issue a disconnect request, and determines that the transition to multicast to the unicast bearer needs to be controlled.
  • Step 806 The AS initiates a unicast establishment process according to the process of the existing call.
  • Step 807 After the unicast is successfully established, the UE receives the downlink data on the unicast channel.
  • Embodiment 6 Corresponding to the case in the example c in the step 101 shown in Fig. 1.
  • the UE has the multicast capability
  • the service access network that initially establishes the session has the multicast capability
  • the multicast bearer mode is established.
  • an abnormality occurs inside the BM-SC, and a change notification of the bearer is initiated. .
  • FIG. 9 is a flowchart of a method for controlling bearer change according to Embodiment 6 of the present invention. The process includes the following steps:
  • step 901 the multicast session is in progress.
  • Step 902 An abnormality occurs inside the BM-SC, and a change notification of the load is initiated.
  • Step 903 The BM-SC sends a bearer change notification message to the AS.
  • Step 904 After receiving the bearer change notification, the AS finds that the user does not issue a disconnect request, and determines that the transition to multicast to the unicast bearer needs to be controlled.
  • Step 905 The AS initiates a unicast establishment process according to the process of the existing call.
  • Step 906 After the unicast is successfully established, the UE receives the downlink data on the unicast channel.
  • the above is a case of converting the multicast bearer mode to the unicast bearer mode, and the method and system for controlling the bearer change are described in detail.
  • the case of converting from the unicast bearer mode to the multicast bearer mode is similar. No longer - a detailed description. Only a specific embodiment will be described below for the case of switching from a unicast bearer mode to a multicast bearer mode.
  • the bearer change notification may be a multicast activation message or a multicast activation notification.
  • the UE has a multicast capability, and the unicast bearer mode established when the session is initially established. During the session, the UE determines whether to perform the unicast-to-multicast transition according to the user's will or the network transmission quality.
  • the UE is both a bearer change notification entity and a bearer change control entity.
  • FIG. 10 is a flowchart of a method for controlling bearer change according to Embodiment 7 of the present invention. The process includes the following steps:
  • step 1001 a unicast session is in progress.
  • Step 1002 The user manually initiates an operation of switching to multicast.
  • Step 1003 The UE initiates a process of multicast establishment by initiating media renegotiation.
  • Step 1004 The UE initiates an MBMS activation process to establish a multicast bearer.
  • Step 1005 The multicast resource is successfully established, and the UE receives downlink data on the multicast channel.
  • the access network may also be other networks, such as a wireless local area network (WLAN) network, and the application of the MBMS service may not be used.
  • WLAN wireless local area network
  • the corresponding multicast capability loss reporting entity and the service continuity control entity may be changed.

Landscapes

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

Description

一种控制承载变化的系统、 装置和方法 技术领域
本发明涉及移动通信技术， 尤其涉及一种控制承载变化的系统、 装 置和方法。 发明背景
为了有效地利用移动网络资源， 第三代合作组织（3GPP )提出了组 播和广播业务（MBMS ), 即实现点到多点的多播业务， 多播业务是指 从一个数据源向多个目标传送数据报的方式， 与以前的点到点的单播方 式相比， 可以节约带宽， 实现网络资源共享， 包括移动核心网和接入网 的资源共享， 尤其是空口资源共享。 3GPP定义的 MBMS不仅能够实现 纯文本低速率的消息类组播和广播， 而且能够实现高速率的多媒体业务 组播和广播。 MBMS业务通过增加一些新的网络功能实体和在已有网络 实体中增加 MBMS 功能支持来实现。 如对于接入网络中的通用分组无 线业务（GPRS ) 网络， 增加了功能实体广播组播业务中心 （BM-SC ) 等；并对涉及到的已有网络实体，如 GPRS服务支持节点（ SGSN )、 GPRS 业务网关节点 （GGSN )、 无线接入网络（RAN ) 中的无线网络控制器 / 基站控制器（RNC/BSC ) 以及用户设备 ( UE )等实体增加了 MBMS功 能支持。
为了节约带宽等网络资源， 目前很多系统中的业务开始应用 MBMS，如为了节约 IP多媒体子系统（ IMS )中的带宽等网络资源， 3GPP 提出在 IMS业务中应用 MBMS ( IMSoMBMS ) 的解决方案。 但现有技 术中， 未对应用 MBMS 的此类业务在终端或网络多播能力或用户意愿 发生改变时， 如何做单 /多播承载转换进行规定， 当多播能力丢失时， 如 UE从支持多播区域迁移至不支持多播区域， 即由多播覆盖区域迁移至 非多播覆盖区域时， 由于非多播区域无法继续为 UE建立多播承载方式 的数据传输， 因此会话等业务便会终止， 从而无法继续进行会话， 或用 户感受多播通讯质量下降， 主观上希望将多播转换为单播方式进行通 讯， 或用户愿意将单播承载转换为多播承载， 或系统多播承载资源发生 异常， 系统需将多播承载转换为单播承载以保持用户业务能够继续进行 等。 发明内容
有鉴于此， 本发明实施例提供一种控制承载变化的系统、 装置及方 法， 以便满足因终端或网络多播能力或用户意愿发生改变时， 对承载进 行转换的需求。
本发明实施例中所提供的系统， 包括：
承载变化通知实体， 用于获知承载需要改变的信息， 向承载变化控 制实体发送^载改变通知；
承载变化控制实体， 用于根据接收到的所述承载改变通知， 确定并 控制承载方式在单播和多播之间的转换。
本发明实施例中所提供的承载变化通知实体包括：
承载变化获知模块， 用于获知承载需要改变的信息， 向发送模块发 送承载改变指示；
发送模块， 用于根据接收到的承载改变指示， 向承载变化控制实体 发送承载改变通知。
本发明实施例中所提供的承载变化控制实体包括：
接收模块， 用于接收来自承载变化通知实体的承载改变通知， 并将 所接收的承载改变通知发送给单 /多播建立控制模块； 单 /多播建立控制模块， 用于根据来自接收模块的所述承载改变通 知， 确定并控制承载方式在单播和多播之间的转换。
本发明实施例中所提供的控制承载变化的方法， 包括：
A、 承载变化控制实体接收承载变化通知实体在获知承载需要改变 的信息时发送的承载改变通知；
B、 承载变化控制实体根据接收到的所述承载改变通知， 确定并控 制承载方式在单播和多播之间的转换。
从上述方案可以看出， 本发明实施例中承载变化通知实体获知承载 需要改变的信息， 如终端多播能力和 /或网络多播能力和 /或用户意愿的 变化等， 向承载变化控制实体发送承载改变通知； 承载变化控制实体根 据所接收的承载改变通知， 确定并控制由多播承载方式向单播承载方式 转换， 或由单播承载方式向多播承载方式转换。 为 UE相应建立起单播或 多播承载方式的数据传输。 从而实现多播承载方式向单播承载方式的顺 利转换， 或反向转换， 使得能够根据终端多播能力或网络多播能力或用 户意愿的变化适当调整承载的方式， 提供业务连续性的能力， 同时也满 足用户个性化的需求。 附图简要说明
图 1为本发明实施例中控制承载变化的方法的示例性流程图； 图 2为本发明实施例中控制承载变化的系统的示例性结构图； 图 3为本发明实施例中一个具体应用的组网系统结构示意图； 图 4为本发明实施例一中的控制承载变化的方法流程图； 图 5为本发明实施例二中的控制承载变化的方法流程图； 图 6为本发明实施例三中的控制承载变化的方法流程图； 图 7为本发明实施例四中的控制承载变化的方法流程图； 图 8为本发明实施例五中的控制承载变化的方法流程图；
图 9为本发明实施例六中的控制承载变化的方法流程图；
图 10为本发明实施例七中的控制承载变化的方法流程图。 实施本发明的方式
本发明实施例中， 承载变化通知实体获知承载需要改变的信息， 如 终端多播能力和 /或网络多播能力和 /或用户意愿的变化等， 向承载变化 控制实体发送承载改变通知； 承载变化控制实体根据所接收的承载改变 通知， 确定并控制由多播承载方式向单播承载方式转换， 或由单播承载 方式向多播承载方式转换。其中，承载改变通知可以为多播去激活通知， 也可以为多播激活通知等。
并且控制建立起单播承载方式的数据传输时， 可提供业务连续性的 能力， 同时也满足用户个性化的需求。
例如： 承载变化通知实体获知到多播能力丢失， 即承载方式需要由 多播承载改变为单播承载， 则向承载变化控制实体发送多播去激活通 知； 承载变化控制实体， 根据接收到的多播去激活通知， 确定由多播承 载方式向单播承载方式转换，控制建立单播承载方式的数据传输；或者， 承载变化通知实体获知到多播能力条件允许及需求， 即承载方式需要由 单播承载改变为多播承载， 则向承载变化控制实体发送多播激活通知； 承载变化控制实体， 根据接收到的多播激活通知， 确定由单播承载方式 向多播承载方式转换， 控制建立多播承载方式的数据传输。
具体实现时， 多播去激活通知可以是多播去激活消息， 也可以是媒 体重协商请求， 还可以是其它的内部通知消息等。 同理， 多播激活通知 可以是多播激活消息， 也可以是媒体重协商请求， 还可以是其它的内部 通知消息等。 其中， 承载变化通知实体获知承载需要改变的信息的方式也可以有 很多种， 如用户意愿改变， 接入网络上报， 以及承载变化通知实体自身 决定等。
参见图 1 , 图 1为本发明实施例中进行^载变化的方法的示例性流 程图。 该流程包括如下步骤：
步骤 101 , 承载变化通知实体获知承载需要改变的信息， 向承载变 化控制实体发送^载改变通知。
本实施例中， 承载需要改变的信息包括： 终端多播能力和 /或网络多 播能力和 /或用户意愿的变化信息等。承载变化通知实体获知终端多播能 力和 /或网络多播能力和 /或用户意愿的变化包括： 用户可根据个人意愿 通过 UE选择承载方式， UE进而向承载变化通知实体发送承载改变信 息， 承载变化通知实体从该承载改变信息中获知用户意愿的变化， 承载 需要改变； 或者 UE从一个区域移动到另一个区域时， 承载变化控制实 体可从网络获知新区域是否支持多播能力的信息， 如 UE从支持多播区 域移动至不支持多播区域时， 接入网络感知到目标网络不支持多播能 力， 向承载变化通知实体发送多播去激活消息， 承载变化通知实体根据 所接收的多播去激活消息， 获知多播能力丢失， 承载需要改变； 或者 UE在从一个网络区域移动至另一个网络区域， 如从一个小区移动至另 一个小区， 发生网络区域迁移时， 为确保业务连续性， 利用现有技术中 的单播切换， 确定预先由多播承载方式转换为单播承载方式， 因此承载 变化通知实体可默认为多播能力丢失， 承载需要改变； 或者终端判断多 播承载的质量状况， 据此向承载变化通知实体发送承载改变信息， 承载 变化通知实体根据该承载改变信息获知承载需要改变； 或者当网络多播 承载资源发生拥塞或异常时， 网络资源管理设备向承载变化通知实体发 送承载改变信息， 承载变化通知实体根据该承载改变信息获知承载需要 改变等。
其中， 上述区域可以是一个 SGSN 下所覆盖的区域， 也可以一个 RAN单元（如 RNC )所覆盖的区域。
以在 IMS业务中应用 MBMS为例， 此时， 7 载改变通知实体可以 为 UE, 载改变控制实体可以为 AS或 UE; 或者^载改变通知实体也 可以为 BM-SC, 载改变控制实体可以为 AS。
下面分别进行介绍：
方式一： 载改变通知实体为 UE, 载改变控制实体为 AS 或为
UE。
UE获知承载需要改变的信息的方法有： UE接收来自用户的承载改 变操作；或 UE接收来自网络的承载改变信息，如接收来自 SGSN或 RAN 的网络是否支持多播的能力信息； 或 UE 本身产生承载改变操作。 UE 根据上述的方法获知承载改变， 将承载改变通知发送给承载变化控制实 体 AS或 UE。
下面以多播承载转换为单播承载的情况为例， 列举几个示例： 示例 1: 在发生 RAN迁移时， 为确保业务连续性， 利用现有技术中 的单播切换， 确定预先将承载方式由多播承载方式转换为单播承载方 式， 服务 RAN在实行切换之前， 先向 UE发送多播去激活指示， 若 UE 向网络侧发起媒体重协商消息， 并在协商完成后， 控制将多播承载方式 转换为单播承载方式， 则此时， UE 既是承载改变通知实体， 又是承载 改变控制实体； 若 UE向 AS发送承载改变通知， 则此时， UE是承载改 变通知实体， AS是^ ^载改变控制实体。 或者在发生 SGSN迁移时， 若 目标接入网络不支持多播能力，则服务 SGSN向 GGSN发送多播去激活 消息， 同时通过 RAN向 UE也发送多播去激活消息， 由 UE根据该多播 去激活消息，向 AS发送承载改变通知。此时， UE是承载改变通知实体， AS是承载改变控制实体。
示例 2: 用户发现多播传输的信号不好， 手动发起切换到单播的操 作； 或者 UE根据网络传输质量进行判断， 决定要执行多播到单播的转 变， 此时， 若 UE向网络侧发起媒体重协商消息， 并在协商完成后， 控 制将多播承载方式转换为单播承载方式， 则此时， UE 既是承载改变通 知实体， 又是承载改变控制实体； 若 UE向 AS发送承载改变通知， 则 此时， UE是承载改变通知实体， AS是承载改变控制实体。
其中，承载改变通知可以为多播能力改变消息， 如： 用户设备向 AS 发送自身是否支持多播能力的信息， 支持多播能力的信息用于请求采用 多播承载， 不支持多播能力的信息用于请求采用单播承载。
方式二： 承载变化通知实体为 BM-SC, 承载改变控制实体为 AS。 BM-SC获知承载需要改变的信息的方法有： BM-SC接收来自终端 的多播承载的激活或去激活请求操作； 或 BM-SC接收来自接入网的承 载改变操作； 或 BM-SC产生承载改变的操作。 BM-SC根据上述的方法 获知承载改变， 将承载改变通知发送给承载变化控制实体。
下面以多播承载转换为单播承载的情况为例， 列举几个示例： 示例 a: 用户发现多播传输的信号不好， 手动发起切换到单播的操 作； 或者 UE根据网络传输质量进行判断， 决定要执行多播到单播的转 变， 并向 BM-SC发送多播去激活通知， 由 BM-SC向 AS上报多播去激 活通知。
示例 b: 在发生 SGSN迁移时， 目标 SGSN会将目标接入网络的多 播能力信息指示给服务 SGSN, 若目标接入网络的多播能力信息为不支 持多播能力， 则服务 SGSN向 GGSN发送多播去激活消息， GGSN将所 接收的多播去激活消息发送给 BM-SC, 由 BM-SC根据该多播去激活消 息， 向 AS发送多播去激活通知， 并且该多播去激活通知可以为多播去 激活消息 , 并且可采用初始会话协议（ SIP ) 消息进行传送。
示例 c: BM-SC 自主产生承载改变的操作， 向 AS发送多播去激活 通知。
上述方式一和方式二中， 多播去激活通知即为承载改变通知。此外， 服务 SGSN通过 RAN向 UE发送多播去激活消息的具体过程可以为： 服务 SGSN 先将多播去激活消息发送给 RAN 中的 RNC/BSC , 由 RNC/BSC向 UE发送多播去激活消息。
目标接入网络的多播能力信息可以包括： 目标 SGSN的多播能力信 息； 或目标无线接入网络 RAN的多播能力信息； 或目标 SGSN和目标
RAN的多播能力信息。
对于从单播承载方式到多播承载方式转换的情况， 与从多播承载方 式向单播承载方式转换的情况类似。
步骤 102, 承载变化控制实体根据所接收的通知， 确定并控制由多 播承载方式向单播承载方式转换， 或由单播承载方式向多播承载方式转 换。
本步骤中， 承载变化控制实体在接收到承载改变通知后， 可进一步 对会话等业务进行检测， 若该业务正在进行， 则控制承载的转换。
对于承载变化控制实体为 AS的情况， 则 AS可根据接收的承载改 变通知， 确定由多播^ ^载方式向单播^ ^载方式转换， 控制重新建立起单 播承载方式的传输， 保持业务持续进行； 或确定由单播承载方式向多播 承载方式转换， 控制重新建立起多播承载方式的传输。
此时， 当用户设备为承载变化通知实体时， 则用户设备可向承载变 化控制实体发起媒体重协商， 通知承载变化控制实体承载改变， 请求建 立单 /多播承载。
对于承载变化控制实体为 UE的情况， 则 UE可根据接收的承载改 变通知， 确定由多播承载方式向单播承载方式转换， 或确定由单播承载 方式向多播承载方式转换。并向网络侧发起媒体重协商，在协商完成后， 控制将多播承载方式转换为单播承载方式， 或将单播承载方式转换为多 播承载方式。
参见图 2, 图 2为本发明实施例中进行^载变化的系统的示例性结 构图。 如图 2所示， 该系统包括： 承载变化通知实体 200、 承载变化控 制实体 210。
其中， 承载变化通知实体 200用于获知承载需要改变的信息， 向承 载变化控制实体 210发送^ ^载改变通知。
承载变化控制实体 210用于接收来自承载变化通知实体的承载改变 通知， 根据接收的承载改变通知， 确定并控制由多播承载方式向单播承 载方式转换， 或由单播承载方式向多播承载方式转换。
具体实现时， 承载变化通知实体 200可有很多种具体实现方式， 只 要能实现上述功能即可。 下面仅列举一种具体实现方式， 如图 2所示， 承载变化通知实体 200可包括：承载变化获知模块 201和发送模块 202。
其中， 承载变化获知模块 201用于获知承载需要改变的信息， 向发 送模块 202发送承载改变指示。
发送模块 202用于接收来自承载变化获知模块 201的承载改变指示， 并根据所接收的承载改变指示向承载变化控制实体 210发送承载改变通 知。
其中， 承载变化获知模块 201和发送模块 202可以集成在一起， 用 于获知承载需要改变的信息， 向承载改变控制实体 210发送承载改变通 知。
具体实现时， 承载改变控制实体 210可有很多种具体实现方式， 只 要能实现前述功能即可。 下面仅列举一种具体实现方式， 如图 2所示， 承载变化控制实体 210可包括： 接收模块 211 和单 /多播建立控制模块 212, 其中，
接收模块 211用于接收来自承载变化通知实体的承载改变通知， 并 将所接收的承载改变通知发送给单 /多播建立控制模块 212;
单 /多播建立控制模块 212用于根据来自接收模块 211的承载改变通 知， 确定并控制由多播承载方式向单播承载方式转换， 或由单播承载方 式向多播承载方式转换。
其中， 接收模块 211和单 /多播建立控制模块 212可以集成在一起， 用于接收来自承载变化通知实体的承载改变通知， 根据所接收的通知， 确定并控制由多播承载方式向单播承载方式转换， 或由单播承载方式向 多播承载方式转换。
此外， 单 /多播建立控制模块 212在具体实现时， 可具体包括： 单 / 多播承载方式建立模块和数据传输转换模块。
其中， 单 /多播承载方式建立模块， 用于根据来自接收模块的承载改 变通知， 确定由多播承载方式向单播承载方式转换， 发起单播承载方式 建立过程， 或由单播^ ^载方式向多播^ ^载方式转换， 并在建立完成时向 数据传输转换模块发送单播已建立通知消息， 或多播已建立通知消息。
数据传输转换模块， 用于根据接收到的单播已建立通知消息， 或多 播已建立通知消息， 将数据传输从多播通道转换至单播通道。 造性劳动， 可变换出承载变化通知实体 200以及承载改变控制实体 210 的多种具体实现形式， 如对上述模块进行拆分或合并等， 此处不再—— 赘述。
此外， 如图 2所示， 该系统可进一步包括： 接入网络实体 220。 接入网络实体 220用于在确定承载需要改变时， 向承载变化通知实 体 200发送承载改变信息； 承载变化通知实体 200接收来自接入网络实 体 220的承载改变信息， 并执行获知承载需要改变的信息， 向发送模块 发送多播去激活通知的操作。 具体实现时， 可由承载变化通知实体 200 中的承载变化获知模块 201来完成。
若^^载变化通知实体 200为 BM-SC,则接入网络实体 220可以包括： 目标 SGSN、 服务 SGSN以及 GGSN。
其中， 目标 SGSN, 用于将目标接入网络的多播能力信息发送给服 务 SGSN。
服务 SGSN, 用于接收目标 SGSN的多播能力信息， 根据所接收的 多播能力信息， 确定承载需要改变时， 向 GGSN发送承载改变消息。
GGSN, 用于接收来自服务 SGSN的承载改变消息， 并根据所接收 的 7 载改变消息向 BM-SC发送 7 载改变通知。
若^载改变通知实体 200为 UE, 则接入网络实体 220可以包括： 目标 SGSN、 服务 SGSN。
其中， 目标 SGSN, 用于将目标接入网络的多播能力信息发送给服 务 SGSN。
服务 SGSN, 用于接收目标 SGSN的多播能力信息， 根据所接收的 多播能力信息，确定承载需要改变时，可通过 RAN向 UE发送承载改变 消息。
或者， 若^ ^载改变通知实体 200为 UE, 则接入网络实体 220还可 以 RAN。
其中， RAN, 用于在发生网络区域迁移时， 确定预先由多播^载方 式转换为单播承载方式，向处于多播承载方式的 UE发送承载改变消息。
其中，服务 SGSN通过 RAN向 UE发送承载改变消息的过程可以包 括： 服务 SGSN 先将承载改变消息发送给 RAN 中的 RNC/BSC, 由 RNC/BSC向 UE发送承载改变消息。
当^载改变通知实体 200为 BM-SC或 UE时， 载改变控制实体 210可以为 AS。 当^ ^载改变通知实体 200为 UE时， 载改变控制实体 210还可以为 UE。
其中， 各功能实体及模块的具体实现过程可与图 1所示流程中的描 述一致。
承载改变通知实体 200和承载改变控制实体 210之间可以采用 SIP 接口。
下面将结合具体应用对上述方法、 系统及系统中的装置实体的实施 例进行详细描述。 以接入网络为 GPRS网络， 在 IMS中应用 MBMS业 务的情况为例。
参见图 3, 图 3为本发明实施例中一个具体应用的组网系统结构示 意图。 如图 3 所示， 该组网系统包括： UE301、 RAN302、 SGSN303、 GGSN304、 BM-SC305、 AS306、 呼叫会话控制功能实体（ CSCFs ) 307 以及归属签约用户服务器（HSS ) 308。
其中， UE301支持激活、 去激活 MBMS多播业务。
AS306用于对使用 MBMS多播的 IMS业务进行控制， 用于接收来 自 UE的多播能力信息， 根据所接收的多播能力信息， 确定对 UE301采 用单播承载方式或多播承载方式， 控制网络建立起相应的承载方式进行 数据传输。
BM-SC305为内容提供者的入口，用来授权和发起 MBMS多播承载 业务， 并按预定时间计划传送 MBMS 内容。 其功能包括： （1 )对第三 方内容提供商的鉴权、 授权和计费； （2 )提供 MBMS传输相关参数， 如 QoS、 组播广播区域； 发起和终止 MBMS传输资源； （3 )从外部数 据源接收并传送 MBMS内容， 安排 MBMS会话传送并告知用户； 会话 重传等； （4 )业务声明， 包括媒体描述、 会话描述如组播业务标识、 地 址、 传送时间等。
RAN302包括通用地面无线接入网（UTRAN )以及全球移动通信系 统（ GSM ) /增强的 GSM ( EDGE )接入网（ GERAN )等，通过 RNC/BSC 在预定的组播或广播业务区域传送 MBMS数据； 支持核心网发起和终 止 MBMS传送； 支持 MBMS接收者在 RNC/BSC间的移动。
SGSN303对用户进行网络控制， 支持 MBMS接收者在 SGSN间的 移动；根据 GGSN发送的通知建立或释放与 RAN及 GGSN的承载连接。
GGSN304作为 MBMS数据的 IP组播业务节点， 根据 BM-SC的通 知请求为多播业务传送建立或释放用户面承载； 从 BM-SC或其它数据 源接收 IP组播内容， 并进行路由。
CSCFs307以及 HSS308用于配合完成会话建立和鉴权。其中 CSCFs 包括： 代理 CSCF ( P-CSCF )、 查询 CSCF ( I-CSCF ) 以及月 ^务 CSCF ( S-CSCF )。
上述各功能实体在具体实现时， BM-SC305以及 UE301还可作为承 载改变通知实体 200, 则 AS306可作为承载改变控制实体 210。 此时， BM-SC305或 UE301 进一步用于获知承载需要改变的信息， 向 AS306 发送承载改变通知， AS306进一步用于接收来自 BM-SC305或 UE301 的承载改变通知， 根据接收的承载改变通知， 确定由多播承载方式向单 播承载方式转换， 控制建立单播承载方式的数据传输； 或确定由单播承 载方式向多播承载方式转换，控制建立多播承载方式的数据传输。其中， BM-SC305或 UE301可包括图 2所示的 载改变获知模块 201和发送模 块 202, 功能也可与图 2中的描述一致， AS306可包括图 2所示的接收 模块 211和单 /多播建立控制模块 212, 功能也可与图 2中的描述一致。 此时，在 UE发生网络区域切换时，可由目标 SGSN303将目标接入网络 的多播能力信息发送给服务 SGSN303; 服务 SGSN303接收到目标接入 网络的多播能力信息， 根据所接收的多播能力， 确定承载需要改变时， 向 GGSN304发送承载改变消息， 由 GGSN304再向 BM-SC305发送承 载改变消息； 或者服务 SGSN303通过 RAN302向 UE301发送承载改变 消息。 或者， 在发生网络区域迁移时， RAN确定预先由多播^载方式转 换为单播承载方式， 向处于多播承载方式的 UE301发送承载改变消息。
其中， 目标接入网络的多播能力信息包括： 目标 SGSN303 的多播 能力信息； 或目标无线接入网络 RAN302 的多播能力信息； 或目标 SGSN303和目标 RAN302的多播能力信息。
图 2所示系统中的各功能实体在具体实现时， UE301也可作为承载 变化控制实体 210。 则 RAN302确定承载需要改变时， 通过 RNC/BSC 向 UE301发送承载改变通知， UE301进一步用于接收来自 RAN302的 承载改变通知， 根据接收的承载改变通知， 确定由多播承载方式向单播 承载方式转换， 控制建立单播承载方式的数据传输， 或由单播承载方式 向多播承载方式转换，控制建立多播承载方式的数据传输。其中， UE301 可包括图 2所示的承载改变获知模块 201和单 /多播建立控制模块 212, 即由于此时 UE301既是^ ^载变化通知实体又是 载变化控制实体，因此 将图 2所示的承载变化通知实体和承载变化控制实体合设在一起， 此时 承载变化获知模块 201和发送模块 202集成在一起， 接收模块 211和单 I多播建立控制模块 212集成在一起。各模块功能可与图 2中的描述一致。
下面对基于图 3所示组网系统的控制承载变化的方法列举几个具体 实施例。
首先以由多播承载方式向单播承载方式转换的情况为例， 对控制承 载变化的方法及系统进行详细描述。 此时， 承载改变通知可以为多播去 激活消息或多播去激活通知。 实施例一： 对应图 1所示步骤 101中示例 b的情况， 以及示例 1中 发生 SGSN迁移时的情况。
本实施例中， UE具有多播能力， 且初始建立会话的服务接入网络 具有多播能力， 并已建立起多播承载方式， 会话进行中 UE发生网络区 域移动时， 目标接入网络不具有多播能力， 即 UE由支持多播区域移动 至不支持多播的区域。 其中， 服务接入网络中的服务 RAN记为 RAN0, 服务 SGSN记为 SGSN0 , 目标接入网络中的目标 RAN记为 RAN1 , 目 标 SGSN记为 SGSN1。
参见图 4, 图 4为本发明实施例一中控制承载变化的方法流程图。 该流程中有些步骤为现有技术中已有的步骤， 为筒便起见， 同时为突出 本发明的流程， 图 4中对某些与现有技术中相同的一些流程不再进行详 细介绍， 而用六边形覆盖的方式表示信息交互， 被六边形覆盖的实体， 表示参与了交互流程， 并且本文中其它方法流程图也采用此方式处理。 该流程包括如下步骤：
步骤 401 , 多播承载方式会话进行中。
步骤 402,发生网络区域迁移， UE从 RAN0、 SGSN0区域向 RAN1、 SGSN1区域移动， 即 UE从服务接入网络向目标接入网络移动。
步骤 403~步骤 405 , RAN0向 SGSN0发送迁移请求， SGSN0根据 所收到的迁移请求， 向 SGSN1发送迁移请求， SGSN1再根据所收到的 迁移请求向 RAN1发送迁移请求。
步骤 406~步骤 407, RAN1根据所收到的迁移请求， 建立起无线资 源， 并向 SGSN1返回迁移确认消息， 确认已建立无线资源。
步骤 408, SGSN1接收到来自 RAN1的迁移确认消息后， 向 SGSN0 发送迁移响应消息。
本步骤中， SGSN1向 SGSN0发送的迁移响应消息中携带有目标接 入网络的多播能力信息， 该多播能力信息可以包括： SGSN1的多播能力 信息； 或 RAN1的多播能力信息； 或 SGSN1和 RAN1的多播能力信息。
本应有实施例中， 目标接入网络的多播能力信息为不支持多播， 即 不具有多播能力。
步骤 409~步骤 410, SGSN0接收到来自 SGSN1的迁移响应消息后， 向 RAN1发送迁移命令， 由 RAN1控制完成迁移过程。
步骤 411 , SGSN0从步骤 408的迁移响应消息中获取目标接入网络 不具有多播能力， 于是发起多播去激活过程， 并向 GGSN发送多播去激 活消息。
步骤 412, GGSN接收到多播去激活消息后， 向 BM-SC发送多播去 激活消息， 即多播去激活通知。
步骤 413, BM-SC根据所接收的多播去激活通知， 向 AS发送多播 去激活消息。
本步骤中， BM-SC终止 MBMS多播传输资源后， 根据所接收的多 播去激活消息， 向 AS发送多播去激活通知， 具体实现时， 可向 AS发 送多播去激活消息，该消息可以为携带多播去激活指示的 SIP协议消息。
步骤 414, AS控制网络建立起单播承载方式进行数据传输。
本步骤中， AS可以进一步判断， 当前会话是否仍然存在， 即是否收 到会话终止的通知消息， 如果会话仍然存在， 即未收到会话终止的通知 消息， 则确定由多播 ^^载方式向单播^ ^载方式转换， 控制网络建立起单 播承载方式进行数据传输， 从而可保持会话等业务的连续性。
具体实现时， 根据接收的多播去激活消息， 确定由多播承载方式向 单播承载方式转换， 发起单播承载方式建立过程， 并在单播承载方式建 立完成时， 将数据传输从多播通道转换至单播通道。
在上述图 4所示方法流程中， 步骤 411~步骤 414与步骤 409~步骤 410可以同时进行。 并且步骤 411中进一步包括： SGSN0向 GGSN发送 多播去激活消息时，可通过 RAN0向 UE发送多播去激活消息。步骤 413 中， UE根据所接收的多播去激活消息， 向 AS发送承载改变通知， 具体 实现时， 可通过 SIP协议消息向 AS发送^ ^载改变通知， 该^ ^载改变通 知可以为多播能力改变通知消息。 此时 BM-SC仍按现有技术处理， 即 终止多播传输资源， 而无需向 AS发送多播去激活通知。
本实施例中， RAN0以及 RAN1控制完成的功能， 均为 RAN中的 RNC/BSC控制完成的。
实施例二： 对应图 1所示步骤 101中示例 1中发生 RAN迁移时， UE既是承载改变通知实体， 又是承载改变控制实体的情况。
本实施例中， 应用场景仍然与实施例一中相同。 即 UE具有多播能 力， 且初始建立会话的服务接入网络具有多播能力， 并已建立起多播承 载方式， 会话进行中 UE发生网络区域移动时， 目标接入网络不具有多 播能力， 即 UE由支持多播区域移动至不支持多播的区域。
参见图 5, 图 5为本发明实施例二中控制承载变化的方法流程图。 该流程包括如下步骤：
步骤 501~步骤 502与图 4所示流程中的步骤 401~步骤 402相同， 即多播承载方式会话进行中，发生网络区域迁移， UE从 RAN0、 SGSN0 区域向 RANI、 SGSN1区域移动， 即 UE从服务接入网络向目标接入网 络移动。
步骤 503 , RAN0向 UE发送多播去激活通知。
本步骤中， RAN0获知 UE欲发生网络迁移， 为确保业务连续性， 实现现有技术中单播到单播的顺畅切换， 暂不执行图 4所示流程中步骤 403的操作， 即暂不向 SGSN0发送迁移请求， 而是先向 UE发送多播去 激活通知， 并且该通知可以通过 SIP消息发送。 步骤 504~步骤 505, UE接收到来自 RANO的多播去激活通知， 确 定由多播承载方式向单播承载方式转换， 发起媒体重协商过程， 由多播 承载方式转换为单播承载方式， 建立单播后， 在单播信道上接收数据。
此处， 发起单播承载方式建立过程为发起媒体重协商过程， 并在单 播承载方式建立完成时， 将数据传输从多播通道转换至单播通道， 即在 单播信道上接收数据。
步骤 506, 单播建立完成后， 向 RAN0发送单播承载方式建立响应。 步骤 507~步骤 515与图 4所示流程中步骤 403~步骤 410相同， 完 成迁移过程。
本实施例中， RAN0以及 RAN1控制完成的功能， 均为 RAN中的 RNC/BSC控制完成的。
实施例三： 对应图 1所示步骤 101 中示例 2中， UE是 7 载改变通 知实体， AS是承载改变控制实体的情况。
本实施例中， UE具有多播能力， 且初始建立会话的服务接入网络 具有多播能力， 并已建立起多播承载方式， 会话进行中， 根据用户意愿 或根据网络传输质量进行判断， 决定要执行多播到单播的转变。
参见图 6, 图 6为本发明实施例三中控制承载变化的方法流程图。 该流程包括如下步骤：
步骤 601 , 会话进行之中。
步骤 602, 用户发现多播传输的信号不好， 手动发起切换到单播的 操作。 或者 UE根据网络传输质量进行判断， 决定要执行多播到单播的 转变。
步骤 603, UE发送承载改变通知给 AS。
本步骤中， 承载改变通知可以为多播能力改变通知消息， 具体实现 时， 可通过 SIP协议消息向 AS发送多播能力改变通知消息。 其中， 多 播能力改变通知消息中携带 UE是否支持多播能力的信息， 支持多播能 力的信息用于请求采用多播承载， 不支持多播能力的信息用于请求采用 单播承载。
本实施例中多播能力改变通知消息中携带有 UE当前不支持多播能 力的信息。
步骤 604, AS收到承载改变通知后， 判断出需要控制多播到单播承 载的转变。
步骤 605 , AS发起单播建立的流程。
步骤 606, 单播建立成功后， UE在单播信道上接收下行数据。 步骤 607, UE发起 MBMS的去激活流程， 释放多播资源。
实施例四： 对应图 1所示步骤 101 中示例 2中， UE既是 7 载改变 通知实体， 又是^载改变控制实体的情况。
本实施例中， 应用场景仍然与实施例一中相同。 即 UE具有多播能 力， 且初始建立会话的服务接入网络具有多播能力， 并已建立起多播承 载方式， 会话进行中， 根据用户意愿或根据网络传输质量进行判断， 决 定要执行多播到单播的转变。
参见图 7, 图 7为本发明实施例四中控制承载变化的方法流程图。 该流程包括如下步骤：
步骤 701 , 会话进行之中。
步骤 702, 用户发现多播传输的信号不好， 手动发起切换到单播的 操作。 或者 UE根据网络传输质量进行判断， 决定要执行多播到单播的 转变。
步骤 703, UE通过发起媒体重协商发起单播建立的流程。
步骤 704, 单播建立成功后， UE在单播信道上接收下行数据。 步骤 705, UE发起 MBMS的去激活流程， 释放多播资源。 实施例五： 对应图 1所示步骤 101中示例 a中的情况。
本实施例中， UE具有多播能力， 且初始建立会话的服务接入网络 具有多播能力， 并已建立起多播承载方式， 会话进行中， 根据用户意愿 或根据网络传输质量进行判断， 决定要执行多播到单播的转变。
参见图 8, 图 8为本发明实施例五中控制承载变化的方法流程图。 该流程包括如下步骤：
步骤 801 , 会话进行之中。
步骤 802, 用户发现多播传输的信号不好， 手动发起切换到单播的 操作。 或者 UE根据网络传输质量进行判断， 决定要执行多播到单播的 转变。
步骤 803, UE发起 MBMS的去激活流程。
本步骤中， UE发起 MBMS去激活流程为现有流程， 因此可按现有 技术进行处理。
步骤 804, BM-SC接收到去激活消息后， 上报承载改变通知给 AS。 本步骤中， BM-SC按现有技术中的 MBMS去激活流程接收到激活 消息后， 向 AS发送承载改变通知。
步骤 805, AS收到承载改变通知后， 发现用户没有发出拆线请求， 判断出需要控制多播到单播承载的转变。
步骤 806, AS按现有呼叫的流程发起单播建立的流程。
步骤 807, 单播建立成功后， UE在单播信道上接收下行数据。
实施例六： 对应图 1所示步骤 101中示例 c中的情况。
本实施例中， UE具有多播能力， 且初始建立会话的服务接入网络 具有多播能力， 并已建立起多播承载方式， 会话进行中， BM-SC内部发 生异常， 发起承载的改变通知。
参见图 9, 图 9为本发明实施例六中控制承载变化的方法流程图。 该流程包括如下步骤：
步骤 901 , 多播会话进行之中。
步骤 902, BM-SC内部发生异常， 发起^ ^载的改变通知。
步骤 903, BM-SC发送承载改变通知消息给 AS。
步骤 904, AS收到承载改变通知后， 发现用户没有发出拆线请求， 判断出需要控制多播到单播承载的转变。
步骤 905, AS按现有呼叫的流程发起单播建立的流程。
步骤 906, 单播建立成功后， UE在单播信道上接收下行数据。
以上以由多播承载方式向单播承载方式转换的情况为例， 对控制承 载变化的方法及系统进行详细描述， 对于由单播承载方式向多播承载方 式转换的情况与之类似， 本文中不再——详细描述。 下面仅列举一个具 体实施例对由单播承载方式向多播承载方式转换的情况进行描述。 此 时， 承载改变通知可以为多播激活消息或多播激活通知。
实施例七：
本实施例中， UE具有多播能力， 初始建立会话时建立的单播承载 方式， 会话进行中， 根据用户意愿或根据网络传输质量进行判断， 决定 要执行单播到多播的转变。 并且本实施例中， UE 既是承载变化通知实 体， 又是^ ^载变化控制实体。
参见图 10, 图 10为本发明实施例七中控制承载变化的方法流程图。 该流程包括如下步骤：
步骤 1001 , 单播会话进行之中。
步骤 1002, 用户手动发起切换到多播的操作。
步骤 1003 , UE通过发起媒体重协商发起多播建立的流程。
步骤 1004, UE发起 MBMS的激活流程， 建立多播承载。
步骤 1005, 多播资源建立成功， UE在多播信道上接收下行数据。 以上所述各实施例均以接入网络为 GPRS网络为例进行了描述， 实 际应用中， 接入网络还可以为其它的网络， 如无线局域网 （WLAN ) 网 络等， 应用 MBMS的业务也可以不限于 IMS等， 相应的多播能力丢失 上报实体及业务连续性控制实体都会有所改变， 凡是本领域的普通技术 人员， 均可以依据本发明实施例的思想， 在其它系统中进行等同实施。 因此可以理解的是， 以上所述仅为本发明的具体实施例而已， 并不用于 限定本发明的保护范围， 凡在本发明的精神和原则之内， 所做的任何修 改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种控制承载变化的系统， 其特征在于， 该系统至少包括： 承载变化通知实体， 用于获知承载需要改变的信息， 向承载变化控 制实体发送^载改变通知；
承载变化控制实体， 用于根据接收到的所述承载改变通知， 确定并 控制承载方式在单播和多播之间的转换。
2、如权利要求 1所述的系统， 其特征在于， 所述承载变化通知实体 包括：
承载变化获知模块， 用于获知承载需要改变的信息， 向发送模块发 送承载改变指示；
发送模块， 用于根据接收到的承载改变指示， 向承载变化控制实体 发送承载改变通知。
3、如权利要求 1所述的系统， 其特征在于， 所述承载变化控制实体 包括：
接收模块， 用于接收来自承载变化通知实体的承载改变通知， 并将 所接收的承载改变通知发送给单 /多播建立控制模块；
单 /多播建立控制模块， 用于根据来自接收模块的所述承载改变通 知， 确定并控制承载方式在单播和多播之间的转换。
4、 如权利要求 1所述的系统， 其特征在于， 所述承载变化通知实体 为： 用户设备。
5、 如权利要求 1所述的系统， 其特征在于， 该系统进一步包括： 接 入网络实体， 用于确定承载需要改变时， 向承载变化通知实体发送承载 改变信息。
6、如权利要求 5所述的系统， 其特征在于， 所述承载变化通知实体 为： 用户设备；
所述接入网络实体包括：
目标 SGSN , 用于将目标接入网络的多播能力信息发送给服务 SGSN;
服务 SGSN, 用于接收目标 SGSN的所述多播能力信息， 根据所接 收的多播能力信息， 确定承载需要改变时， 通过无线接入网络 RAN向 UE发送 7|载改变通知。
7、如权利要求 5所述的系统， 其特征在于， 所述承载变化通知实体 为： 广播组播业务中心；
所述接入网络实体包括：
目标通用分组无线业务 GPRS服务支持节点 SGSN, 用于将目标接 入网络的多播能力信息发送给服务 SGSN;
服务 SGSN, 用于接收目标 SGSN的所述多播能力信息， 根据所接 收的多播能力信息，确定承载需要改变时，向 GGSN发送承载改变消息；
GPRS业务网关节点 GGSN, 用于接收来自服务 SGSN的承载改变 消息， 并根据所接收的承载改变消息向 BM-SC发送承载改变通知。
8、 如权利要求 1所述的系统， 其特征在于， 所述承载变化通知实体 为： 广播组播业务中心。
9、 如权利要求 1至 8中任一项所述的系统， 其特征在于， 所述承载 变化控制实体为应用服务器。
10、 如权利要求 1至 6中任一项所述的系统， 其特征在于， 所述承 载变化控制实体为用户设备。
11、 一种承载变化通知实体， 其特征在于， 该通知实体包括： 承载变化获知模块， 用于获知承载需要改变的信息， 向发送模块发 送承载改变指示； 发送模块， 用于根据接收到的承载改变指示， 向承载变化控制实体 发送承载改变通知。
12、 如权利要求 11所述的承载变化通知实体， 其特征在于， 所述承 载变化获知模块和发送模块集成在一起。
13、 如权利要求 11或 12所述的 载变化通知实体， 其特征在于， 该承载变化通知实体包括： 用户设备 UE和 /或广播组播业务中心。
14、 一种承载变化控制实体， 其特征在于， 该控制实体包括： 接收模块， 用于接收来自承载变化通知实体的承载改变通知， 并将 所接收的承载改变通知发送给单 /多播建立控制模块；
单 /多播建立控制模块， 用于根据来自接收模块的所述承载改变通 知， 确定并控制承载方式在单播和多播之间的转换。
15、 一种控制承载变化的方法， 其特征在于， 该方法包括：
A、 承载变化控制实体接收承载变化通知实体在获知承载需要改变 的信息时发送的承载改变通知；
B、 承载变化控制实体根据接收到的所述承载改变通知， 确定并控 制承载方式在单播和多播之间的转换。
16、 如权利要求 15所述的方法， 其特征在于， 所述承载变化通知实 体为用户设备；
所述承载变化通知实体在获知承载需要改变的信息时发送的承载改 变通知包括： 用户设备通过接收来自用户的承载改变操作， 或接收来自 网络的承载改变信息， 或用户设备自身产生承载改变操作获知承载需要 改变时发送的 7|载改变通知。
17、如权利要求 16所述的方法， 其特征在于， 所述用户设备接收来 自网络的承载改变信息为： 用户设备接收关于 SGSN和 RAN中的一个 或两个的网络是否支持多播的能力信息。
18、 如权利要求 15至 17中任一项所述的方法， 其特征在于， 所述 承载变化控制实体为用户设备；
所述步骤 B为： 用户设备根据接收的承载改变通知， 确定由多播承 载方式向单播承载方式转换， 或确定由单播承载方式向多播承载方式转 换， 并向网络侧发起媒体重协商， 在协商完成后， 控制将多播承载方式 转换为单播承载方式， 或将单播承载方式转换为多播承载方式。
19、 如权利要求 16所述的方法， 其特征在于， 所述承载改变通知包 括： UE是否支持多播能力的信息， 用于请求是否采用多播承载。
20、 如权利要求 15所述的方法， 其特征在于， 所述承载变化通知实 体在获知承载需要改变的信息时发送的承载改变通知包括：
广播组播业务中心通过产生承载改变操作， 或接收来自 SGSN 的 MBMS承载操作请求，或处理来自终端的多播承载的激活或去激活请求 操作获知承载需要改变时发送的承载改变通知。
21、 如权利要求 15、 16、 17、 19、 20中任一项所述的方法， 其特征 在于， 所述承载变化控制实体为应用服务器。
PCT/CN2007/070881 2006-10-14 2007-10-12 Système, dispositif et procédé permettant de commander le changement de mode de transmission WO2008046348A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07817072A EP2066077A4 (en) 2006-10-14 2007-10-12 SYSTEM, DEVICE AND METHOD FOR CONTROLLING TRANSMISSION MODE CHANGE
US12/420,318 US20090196213A1 (en) 2006-10-14 2009-04-08 System, device and method for controlling a bearer change

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200610139152 2006-10-14
CN200610139152.5 2006-10-14
CN2007100056083A CN101163260B (zh) 2006-10-14 2007-03-01 一种控制承载变化的系统、装置和方法
CN200710005608.3 2007-03-01

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/420,318 Continuation US20090196213A1 (en) 2006-10-14 2009-04-08 System, device and method for controlling a bearer change

Publications (1)

Publication Number Publication Date
WO2008046348A1 true WO2008046348A1 (fr) 2008-04-24

Family

ID=39298068

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070881 WO2008046348A1 (fr) 2006-10-14 2007-10-12 Système, dispositif et procédé permettant de commander le changement de mode de transmission

Country Status (4)

Country Link
US (1) US20090196213A1 (zh)
EP (1) EP2066077A4 (zh)
CN (1) CN101163260B (zh)
WO (1) WO2008046348A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110083153A1 (en) * 2008-06-05 2011-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and Equipment for Providing Unicast Preparation for IPTV
CN102711276A (zh) * 2008-06-13 2012-10-03 上海华为技术有限公司 一种数据通讯方法及通讯系统以及相关装置
US8661155B2 (en) * 2008-12-30 2014-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Service layer assisted change of multimedia stream access delivery

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8295200B2 (en) * 2009-03-31 2012-10-23 Motorola Mobility Llc Discovering multicast routing capability of an access network
US8897256B2 (en) * 2009-04-07 2014-11-25 Qualcomm Incorporated Methods and apparatus for providing broadcast content over a unicast channel
KR101626617B1 (ko) * 2009-09-29 2016-06-01 삼성전자주식회사 Ｉｍｓ 망에서 ｉｐ-ｃａｎ 세션 변경 장치 및 방법
CN101778440B (zh) * 2010-01-08 2012-11-21 华为技术有限公司 一种用户面从Iur-g接口向A接口迁移的方法、及相应的装置
WO2012089368A1 (en) * 2010-12-30 2012-07-05 Nokia Siemens Networks Oy A method and apparatuses for multimedia priority service
US9173192B2 (en) 2011-03-17 2015-10-27 Qualcomm Incorporated Target cell selection for multimedia broadcast multicast service continuity
US8867388B2 (en) 2011-11-19 2014-10-21 Motorola Solutions, Inc. Distributing content to a plurality of mobile stations using a downlink point-to-multipoint (PTM) bearers and downlink point-to-point (PTP) bearers
US8699398B2 (en) * 2011-11-19 2014-04-15 Motorola Solutions, Inc. Dynamically switching mobile stations between point-to-point and point-to-multipoint operating modes
JP5991059B2 (ja) * 2012-07-27 2016-09-14 富士通株式会社 オフロード装置、ネットワークシステムおよびマルチキャストトラヒックのハンドオーバ方法
EP2942984B1 (en) * 2013-02-06 2019-08-21 Huawei Technologies Co., Ltd. Method, base station and user equipment for data transmission and acquisition
ITTO20130163A1 (it) * 2013-02-28 2014-08-29 Inst Rundfunktechnik Gmbh Empfangsvorrichtung und sendevorrichtung zum empfangen bzw. senden von signalen und verfahren zum senden von signalen
EP3017616B1 (en) * 2013-07-01 2018-12-05 NEC Corporation Method for providing multicast/broadcast service continuity for mobile terminals
CN104640077B (zh) * 2013-11-08 2019-10-11 中兴通讯股份有限公司 一种集群通信的方法及系统、用户设备和网络侧设备
CN104754522B (zh) * 2013-12-25 2018-05-29 电信科学技术研究院 一种保持组通信业务连续性的方法、装置和系统
CN104754519B (zh) * 2013-12-25 2018-11-27 电信科学技术研究院 一种组通信业务的处理方法、用户设备和网络侧设备
GB2522043A (en) * 2014-01-10 2015-07-15 Samsung Electronics Co Ltd Multicast user service delivery
CN104955086A (zh) 2014-03-24 2015-09-30 中兴通讯股份有限公司 Mbms差错处理方法、通信节点及通信系统
CN105099721B (zh) * 2014-04-28 2018-12-07 华为技术有限公司 维护组播成员的方法及设备
EP2995146B1 (en) * 2014-05-02 2017-08-09 Telefonaktiebolaget LM Ericsson (publ) Elimination of muting during evolved multicast broadcast service (embs) service change
WO2016070380A1 (en) * 2014-11-06 2016-05-12 Qualcomm Incorporated Embms session suspend/stop notification
US9763130B1 (en) * 2014-11-26 2017-09-12 Sprint Spectrum L.P. Systems and methods for managing congestion in a wireless communication network
CN105992155B (zh) * 2015-01-30 2020-02-07 中国移动通信集团公司 一种网络中单组播动态切换的方法、装置和系统
CN106465065B (zh) * 2015-04-10 2019-11-19 华为技术有限公司 一种多播业务传输装置及方法
CN106211261B (zh) * 2015-04-10 2020-10-16 中兴通讯股份有限公司 信息处理方法及通信节点
US11259225B2 (en) * 2015-10-16 2022-02-22 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for cell frequency change procedure signal timing selection
CN114401533A (zh) 2016-08-18 2022-04-26 康维达无线有限责任公司 用于服务和会话连续性的网络服务暴露
BR112019008045B1 (pt) * 2016-11-01 2023-12-26 Telefonaktiebolaget Lm Ericsson (Publ) Método para relato da interrupção de serviço de uma portadora de difusão seletiva para comunicações em grupo, nó cliente, nó de controle, e, mídias de armazenamento não-transitórias legíveis por computador
CN109769150B (zh) * 2017-11-09 2021-02-23 华为技术有限公司 一种传输组播业务的方法和设备
US11259360B2 (en) * 2018-02-26 2022-02-22 Nokia Technologies Oy Multicast traffic area management and mobility for wireless network
CN108650640A (zh) * 2018-03-05 2018-10-12 海能达通信股份有限公司 集群通信方法及相关设备
CN111800734A (zh) * 2019-08-14 2020-10-20 维沃移动通信有限公司 数据传输方法、装置、设备及介质
CN110809299B (zh) * 2019-11-07 2021-07-27 腾讯科技（深圳）有限公司 一种广播业务的模式切换方法以及相关装置
CN113068133A (zh) * 2020-01-02 2021-07-02 维沃移动通信有限公司 多播用户操作通知方法及装置、通信设备
CN113067793B (zh) * 2020-01-02 2022-08-12 维沃移动通信有限公司 多播业务的传输方法、传输处理方法及相关设备
CN113068132A (zh) * 2020-01-02 2021-07-02 维沃移动通信有限公司 多播用户操作的通知方法、装置和通信设备
CN113068134B (zh) * 2020-01-02 2022-06-10 维沃移动通信有限公司 多播业务会话操作的方法、装置和通信设备
CN113891253B (zh) * 2020-07-02 2023-03-24 大唐移动通信设备有限公司 多播处理方法、配置方法、装置、终端及网络侧设备
CN116134840A (zh) * 2020-08-06 2023-05-16 联想(北京)有限公司 用于多播及广播服务的方法及设备
CN114095989B (zh) * 2020-08-25 2023-09-12 大唐移动通信设备有限公司 一种传输方式转换方法及装置
CN115278790A (zh) * 2021-04-30 2022-11-01 华为技术有限公司 一种通信方法及通信装置
WO2024083617A1 (en) * 2022-10-20 2024-04-25 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for feature support notification

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1751303A (zh) * 2001-12-06 2006-03-22 诺基亚公司 用于有效分配可多播服务的系统和方法
CN1809008A (zh) * 2005-01-21 2006-07-26 捷讯研究有限公司 在无线网络中作为单播业务来处理广播和组播业务

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060039344A1 (en) * 2004-08-20 2006-02-23 Lucent Technologies, Inc. Multiplexing scheme for unicast and broadcast/multicast traffic
US20060227772A1 (en) * 2005-03-30 2006-10-12 Fujitsu Limited Method and system for packet data communication between networks
US7889732B2 (en) * 2005-12-22 2011-02-15 Alcatel-Lucent Usa, Inc. Method for converting between unicast sessions and a multicast session

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1751303A (zh) * 2001-12-06 2006-03-22 诺基亚公司 用于有效分配可多播服务的系统和方法
CN1809008A (zh) * 2005-01-21 2006-07-26 捷讯研究有限公司 在无线网络中作为单播业务来处理广播和组播业务

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110083153A1 (en) * 2008-06-05 2011-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and Equipment for Providing Unicast Preparation for IPTV
US8973057B2 (en) * 2008-06-05 2015-03-03 Telefonaktiebolaget L M Ericsson (Publ) Method and equipment for providing unicast preparation for IPTV
EP2294733B1 (en) * 2008-06-05 2019-12-18 Telefonaktiebolaget LM Ericsson (publ) A method and equipment for providing unicast preparation for iptv
CN102711276A (zh) * 2008-06-13 2012-10-03 上海华为技术有限公司 一种数据通讯方法及通讯系统以及相关装置
US8838168B2 (en) 2008-06-13 2014-09-16 Huawei Technologies Co., Ltd. Method for data communication, system for communication and related devices
US9060358B2 (en) 2008-06-13 2015-06-16 Huawei Technologies Co., Ltd. Method for data communication, system for communication and related devices
US9369860B2 (en) 2008-06-13 2016-06-14 Huawei Technologies Co., Ltd. Method for data communication, system for communication and related devices
US10009934B2 (en) 2008-06-13 2018-06-26 Huawei Technologies Co., Ltd. Method for data communication, system for communication and related devices
US10334639B2 (en) 2008-06-13 2019-06-25 Huawei Technologies Co., Ltd. Method for data communication, system for communication and related devices
US10652937B2 (en) 2008-06-13 2020-05-12 Huawei Technologies Co., Ltd. Method for data communication, system for communication and related devices
US8661155B2 (en) * 2008-12-30 2014-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Service layer assisted change of multimedia stream access delivery

Also Published As

Publication number Publication date
US20090196213A1 (en) 2009-08-06
CN101163260A (zh) 2008-04-16
CN101163260B (zh) 2011-04-13
EP2066077A1 (en) 2009-06-03
EP2066077A4 (en) 2012-05-16

Similar Documents

Publication Publication Date Title
WO2008046348A1 (fr) Système, dispositif et procédé permettant de commander le changement de mode de transmission
KR100947741B1 (ko) 이동통신 시스템에서의 ｒｒｃ연결설정 방법
JP4977721B2 (ja) ダウンリンクマルチキャストサービス（例えばｍｂｍｓ）を用いることによる双方向サービス（ｉｍｓ，例えばｐｏｃ，会議）のサービスデータの提供
WO2008046339A1 (fr) Procédé, système et appareil pour déterminer le mode de portée
JP4284357B2 (ja) 無線通信ネットワークにおける無線端末機の移動性をサポートするための装置及び方法
US8031735B2 (en) Method and apparatus of selecting operating frequency for user equipment in a wireless communications system
JP6409914B2 (ja) 専用無線リソース制御
US8355353B2 (en) Efficient multicast service data provision in a mobile communication system
JP2009530928A (ja) ドメイン間グループ通信
WO2006083093A1 (en) Method and system for servicing full duplex call in push-to-talk over cellular
WO2009067866A1 (fr) Procédé et système de réseau pour établir des sessions dans un service de diffusion/multidiffusion multimédia
EP1898659A2 (en) Method of reporting MBMS service information for user equipment in a wireless communications system and related apparatus
US20070230380A1 (en) System And Method For Selecting A Point-To-Point Or Point-To-Multipoint Transmission Mode
EP1611714A1 (en) Method and communication system for notifying a station of a wireless data transmission session
JPWO2018029939A1 (ja) 端末、基地局及び通信方法

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007817072

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE