WO2020156258A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2020156258A1
WO2020156258A1 PCT/CN2020/072858 CN2020072858W WO2020156258A1 WO 2020156258 A1 WO2020156258 A1 WO 2020156258A1 CN 2020072858 W CN2020072858 W CN 2020072858W WO 2020156258 A1 WO2020156258 A1 WO 2020156258A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
multicast service
access device
data
target access
Prior art date
Application number
PCT/CN2020/072858
Other languages
English (en)
French (fr)
Inventor
李欢
靳维生
诸华林
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20748976.6A priority Critical patent/EP3908042A4/en
Publication of WO2020156258A1 publication Critical patent/WO2020156258A1/zh
Priority to US17/389,782 priority patent/US20210360488A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • the process of handover between the two base stations of the terminal equipment usually involves the corresponding mobility management entity (MME) and the serving gateway (S-GW). Switch, so as to realize the switch from the source side device to the target side device.
  • MME mobility management entity
  • S-GW serving gateway
  • P-GW packet data network gateway
  • a fixed anchor point is not necessary.
  • a fixed anchor point must be deployed to allow the fixed anchor point to participate in the switching of terminal equipment. This is obviously inflexible in terminal equipment switching. And cause waste of resources.
  • the present application provides a communication method and device, which are used to realize a flexible switching process of a terminal device in a multicast service scenario.
  • the present application provides a communication method applied to a multicast service scenario.
  • the method includes: a source access device sends a first message to an access controller, and receives a fifth message from the access controller, Wherein, the first message is used to request the terminal device to switch to the target access device, and the first message includes the multicast service context of the terminal device; the fifth message is used to respond to the terminal device switching to the target access device.
  • the fifth message includes the indication information of whether to forward the multicast service data.
  • the terminal device can flexibly perform the switching process during the switch between the access devices, and the continuity of the multicast service can be ensured without the need for a fixed anchor point to participate in the switch of the terminal device, which can avoid the deployment of fixed anchors.
  • the source access device determines, according to the fifth message, whether the target access device subscribes to the multicast service currently performed by the terminal device. In this way, the target access device can be subsequently notified to join the multicast service currently performed by the terminal device.
  • the source access device when the target access device does not subscribe to the multicast service currently performed by the terminal device, notifies the terminal device to subscribe to the terminal device currently performing the service through the target access device Multicast business. In this way, the subscription to the multicast service of the target access device can be realized.
  • the source access device determines whether the target access device subscribes to the multicast service currently performed by the terminal device according to the fifth message, which may specifically include the following three situations:
  • the source access device subscribes to the current subscription or carried multicast service according to the target access device. Identifying whether the target access device subscribes to the multicast service currently performed by the terminal device; or
  • the source access device determines according to the information that the target access device has not subscribed to the multicast service.
  • the multicast service currently performed by the terminal device or
  • the source access device determines that the target access device has not subscribed to the terminal device's current performance Multicast business.
  • the source access device can accurately determine that the target access device is not subscribed to the multicast service currently performed by the terminal device.
  • the method further includes: the fifth message further includes the forwarding tunnel endpoint identifier of the target access device, and the source access device Establish a tunnel for forwarding multicast service data according to the target access device forwarding tunnel endpoint identifier; or, the fifth message further includes the forwarding tunnel endpoint identifier of the access controller, and the source access device The forwarding tunnel endpoint identifier of the access controller establishes a tunnel for forwarding multicast service data.
  • the source access device can implement subsequent forwarding of multicast service data according to actual conditions.
  • the source access device when the indication information indicates to forward the multicast service data, the source access device receives the eighth message from the access controller and deletes the tunnel for forwarding the multicast service data.
  • the eighth message is used to request to stop data transmission. In this way, the source access device can stop transmitting multicast service data to the target access device.
  • the indication information indicates to forward multicast service data
  • a data forwarding timer is started; when the data is forwarded When the timer expires, the source access device sends a ninth message to the target access device and deletes the tunnel for forwarding multicast service data; wherein, the ninth message is used to indicate the completion of data forwarding; or, when the When the data forwarding timer expires, the source access device sends a tenth message to the target access device through the access controller and deletes the tunnel for forwarding multicast service data; wherein, the tenth message is used To indicate the completion of data forwarding.
  • the present application provides a communication method applied to a multicast service scenario.
  • the method includes: an access controller receives a first message from a source access device, sends a second message to the target access device, After receiving the fourth message, the target access device sends a fifth message to the source access device; wherein, the first message is used to request to switch the terminal device to the device, and the first message includes the terminal device.
  • the second message is used to request to switch the terminal device to the target access device, and the second message includes the multicast service context of the terminal device; the fourth message is used to respond to A request message for switching the terminal device to the target access device; the fifth message is used to respond to the request message for switching the terminal device to the target access device, and the fifth message includes indication information whether to forward the multicast service data.
  • the terminal device can flexibly perform the switching process during the switch between the access devices, and the continuity of the multicast service can be ensured without the need for a fixed anchor point to participate in the switch of the terminal device, which can avoid the deployment of fixed anchors.
  • the fifth message includes the indication information whether to forward the multicast service data, which may specifically include: the fourth message includes the indication information whether to forward the multicast service data, and the connection
  • the access controller includes the indication information of whether to forward the multicast service data contained in the fourth message in the fifth message; or, the access controller according to whether the target access device subscribes to the For the multicast service currently performed by the terminal device, the fifth message includes the indication information of whether to forward the multicast service data.
  • the access controller can flexibly implement that the fifth message includes the indication information of whether to forward the multicast service data, so that the subsequent source access device executes the corresponding process operation according to the indication information.
  • the access controller adds the target access device to the current multicast service performed by the terminal device. Multicast business.
  • the second message when the access controller determines that the protocol of the tunnel through which the access controller and the target access device transmit multicast service data is GTP-U, the second message also includes The first multicast tunnel establishment information, where the first multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the fourth message when the indication information indicates to forward multicast service data, the fourth message also includes the forwarding tunnel endpoint identifier of the target access device, and the fifth message also includes the The forwarding tunnel endpoint identifier of the target access device; or the fourth message further includes the forwarding tunnel endpoint identifier of the target access device, and the fifth message also includes the forwarding tunnel endpoint identifier of the access controller .
  • the source access device can implement subsequent forwarding of multicast service data according to actual conditions.
  • the access controller when the indication information indicates to forward multicast service data, the access controller receives an eighth message from the target access device, where the eighth message is used to request to stop data transmission; The access controller sends the eighth message to the source access device.
  • the source access device can stop transmitting multicast service data to the target access device.
  • the access controller when the indication information indicates to forward multicast service data, the access controller receives a tenth message from the source access device, where the tenth message is used to indicate that the data forwarding is completed; The access controller forwards the tenth message to the target access device.
  • the forwarding of multicast service data between the source access device and the target access device can be stopped.
  • the present application provides a communication method applied to a multicast service scenario.
  • the method includes: a target access device receives a second message from an access controller, and sends a fourth message to the access controller Wherein, the second message is used to request the terminal device to be handed over to the target access device, and the second message includes the multicast service context of the terminal device; the fourth message is used to respond to the handover of the terminal device Request message to the target access device.
  • the terminal device can flexibly perform the switching process during the switch between the access devices, and the continuity of the multicast service can be ensured without the need for a fixed anchor point to participate in the switch of the terminal device, which can avoid the deployment of fixed anchors The waste of resources caused by points.
  • the fourth message includes indication information whether to forward the multicast service data.
  • the source access device can determine whether the multicast service data needs to be forwarded according to the instruction information in the subsequent process.
  • the second message further includes first multicast tunnel establishment information, and the first multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data. In this way, a tunnel for transmitting multicast service data between the access controller and the target access device can be established.
  • the fourth message further includes second multicast tunnel establishment information, and the second multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data. In this way, a tunnel for transmitting multicast service data between the access controller and the target access device can be established.
  • the fourth message also includes the forwarding tunnel endpoint identifier of the target access device.
  • the access controller may forward the forwarding tunnel endpoint identifier of the target access device to the source access device according to the actual situation, or the access controller may forward the forwarding tunnel endpoint identifier of the target access device according to the actual situation.
  • the target access device after the target access device receives the second message from the access controller, when the target access device determines that it is not using the multicast service context of the terminal device When subscribing to the multicast service currently performed by the terminal device, the target access device sends a third message to the multicast source device, where the third message is used to subscribe to the multicast service currently performed by the terminal device.
  • the target access device when the target access device receives multicast service data from the source access device, it starts a data forwarding timer; when the data forwarding timer times out, the target access device Start the tunnel deletion timer, and send an eighth message to the access controller, the eighth message is used to request to stop data transmission; when the tunnel deletion timer expires, the target access device deletes the forwarding group A tunnel for broadcasting business data.
  • the forwarding of multicast service data between the source access device and the target access device can be stopped.
  • the target access device after the target access device receives the ninth message from the source access device, it deletes the tunnel for forwarding the multicast service data, where the ninth message is used to indicate that the data forwarding is completed; or After the target access device receives the tenth message from the source access device from the access controller, it deletes the tunnel that forwards the multicast service data, where the tenth message is used to indicate that the data forwarding is complete.
  • the forwarding of multicast service data between the source access device and the target access device can be stopped.
  • the target access device when the target access device receives multicast service data from the source access device, it starts a data forwarding timer; when the data forwarding timer times out, the target access device Delete the tunnel for forwarding multicast service data.
  • the forwarding of multicast service data between the source access device and the target access device can be stopped.
  • this application provides a communication method applied to a multicast service scenario.
  • the method includes: a terminal device receives a sixth message from a source access device, and the sixth message includes the current subscription of the terminal device Notification information of the multicast service; the terminal device sends a seventh message to the target access device, the seventh message is used to indicate that the target access device has not subscribed to the multicast service currently performed by the terminal device, or Request the target access device to subscribe to the multicast service currently performed by the terminal device; the target access device sends a nineteenth message to the multicast source device, and the nineteenth message is used to indicate the multicast The source device joins the target access device to the multicast service currently performed by the terminal device.
  • the target access device that is not subscribed to the multicast service currently performed by the terminal device can be added to the corresponding multicast service, so as to realize service continuity.
  • this application provides a method for configuring multicast service information.
  • the method includes: an access device sends a thirteenth message to an access controller, and the thirteenth message includes information supported by the access device. Protocol of a tunnel for transmitting multicast service data; the access device receives a fourteenth message from the access controller, the fourteenth message is used to respond to the thirteenth message, and the fourteenth message includes The protocol of the tunnel for transmitting multicast service data supported by the access controller.
  • the thirteenth message when the protocol of the tunnel for transmitting multicast service data supported by the access device is GTP-U, the thirteenth message also includes the tunnel endpoint identifier of the access device. In this way, a tunnel for transmitting multicast service data between the access device and the access controller can be realized.
  • the fourteenth message when the protocol of the tunnel for transmitting multicast service data supported by the access controller is GTP-U, the fourteenth message also includes the tunnel endpoint identifier of the access controller . In this way, a tunnel for transmitting multicast service data between the access device and the access controller can be realized.
  • this application provides a method for establishing a multicast service.
  • the method includes: an access device receives a fifteenth message from a terminal device, the fifteenth message is used to request the establishment of a multicast service, and the first The fifteenth message includes the address of the multicast service and the identification of the terminal device; the access device sends a sixteenth message to the access controller, and the sixteenth message is used to request the establishment of the multicast Service, the sixteenth message includes the identification of the terminal device and the address of the multicast service; the access device receives the seventeenth message from the access controller, and the seventeenth message uses To indicate that the terminal device is allowed to establish the multicast service, the seventeenth message includes the identifier of the terminal device and the address of the multicast service.
  • the establishment of the multicast service can be realized, so that the subsequent terminal equipment can perform the required multicast service.
  • the sixteenth message further includes first multicast tunnel establishment information, and the first multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data. In this way, the establishment of a tunnel for transmitting multicast service data between the access device and the access controller can be realized in the subsequent process.
  • the seventeenth message further includes second multicast tunnel establishment information, and the second multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the establishment of a tunnel for transmitting multicast service data between the access device and the access controller can be realized in the subsequent process.
  • the access device when the access device determines that it has not subscribed to the multicast service, the access device sends an eighteenth message to the access controller or the multicast source, and the eighteenth message The message is used to subscribe to the multicast service.
  • the target access device that is not subscribed to the multicast service currently performed by the terminal device can be added to the corresponding multicast service, so as to realize service continuity.
  • this application provides a method for establishing a multicast service.
  • the method includes: an access controller receives a sixteenth message from an access device, where the sixteenth message is used to request the establishment of a multicast service.
  • the sixteenth message includes the identification of the terminal device and the address of the multicast service; the access controller sends a seventeenth message to the access device, and the seventeenth message is used to indicate permission
  • the terminal device establishes the multicast service, and the seventeenth message includes the identifier of the terminal device and the address of the multicast service.
  • the establishment of the multicast service can be realized, so that the subsequent terminal equipment can perform the required multicast service.
  • the sixteenth message further includes first multicast tunnel establishment information, and the first multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data. In this way, the establishment of a tunnel for transmitting multicast service data between the access device and the access controller can be realized in the subsequent process.
  • the seventeenth message further includes second multicast tunnel establishment information, and the second multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the establishment of a tunnel for transmitting multicast service data between the access device and the access controller can be realized in the subsequent process.
  • the access controller receives an eighteenth message from the access device, and the eighteenth message is used to subscribe to the multicast service; the access controller sends the access The incoming device joins the multicast service.
  • the target access device that is not subscribed to the multicast service currently performed by the terminal device can be added to the corresponding multicast service, so as to realize service continuity.
  • this application also provides a source access device, which has the function of realizing the behavior of the source access device in the method example of the first aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the source access device includes a sending unit, a receiving unit, and a processing unit. These units can perform the corresponding functions in the method example of the first aspect. For details, refer to the detailed description in the method example. Do not repeat them here.
  • the structure of the source access device includes a transceiver and a processor, and optionally also includes a memory.
  • the transceiver is used to send and receive data and to communicate with other devices in the communication system.
  • the processor is configured to support the source access device to perform the corresponding function in the above-mentioned method in the first aspect.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the source access device.
  • the present application also provides an access controller, which has the function of realizing the behavior of the access controller in the method example of the second aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the access controller includes a receiving unit, a sending unit, and a processing unit. These units can perform the corresponding functions in the method example of the second aspect. For details, refer to the detailed description in the method example. Do not repeat them here.
  • the structure of the access controller includes a transceiver, a processor, and optionally a memory, and the transceiver is used to send and receive data, and to communicate with other devices in the communication system
  • the processor is configured to support the access controller to perform the corresponding function in the above-mentioned second aspect method.
  • the memory is coupled with the processor, and stores program instructions and data necessary for the access controller.
  • this application also provides a target access device, which has the function of realizing the behavior of the target access device in the method example of the third aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the target access device includes a receiving unit, a sending unit, and a processing unit. These units can perform the corresponding functions in the method examples of the third aspect. For details, refer to the detailed description in the method examples. Do not repeat them here.
  • the structure of the target access device includes a transceiver and a processor, and optionally also includes a memory, the transceiver is used to send and receive data, and to communicate with other devices in the communication system Interactively, the processor is configured to support the target access device to perform the corresponding function in the method of the third aspect.
  • the memory is coupled with the processor, and stores the program instructions and data necessary for the target access device.
  • this application also provides a terminal device that has the function of implementing the behavior of the terminal device in the method example of the fourth aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the terminal device includes a receiving unit, a sending unit, and a processing unit. These units can perform the corresponding functions in the method example of the fourth aspect. For details, please refer to the detailed description in the method example. Do not repeat it.
  • the structure of the terminal device includes a transceiver, a processor, and optionally a memory.
  • the transceiver is used for sending and receiving data and for communicating and interacting with other devices in the communication system
  • the processor is configured to support the terminal device to perform the corresponding function in the above-mentioned fourth aspect method.
  • the memory is coupled with the processor, and stores the necessary program instructions and data of the terminal device.
  • this application also provides an access device that has the function of implementing the behavior of the access device in the method example of the fifth aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the access device includes a receiving unit, a sending unit, and a processing unit. These units can perform the corresponding functions in the method example of the fifth aspect. For details, refer to the detailed description in the method example. I won’t repeat it here.
  • the structure of the access device includes a transceiver and a processor, and optionally also includes a memory, the transceiver is used for sending and receiving data, and for communicating and interacting with other devices in the communication system
  • the processor is configured to support the access device to perform the corresponding function in the above-mentioned fifth aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the access device.
  • this application also provides an access controller, which has the function of realizing the behavior of the access controller in the method example of the fifth aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the access controller includes a receiving unit, a sending unit, and a processing unit. These units can perform the corresponding functions in the method example of the fifth aspect. For details, refer to the detailed description in the method example. Do not repeat them here.
  • the structure of the access controller includes a transceiver, a processor, and optionally a memory, and the transceiver is used to send and receive data, and to communicate with other devices in the communication system
  • the processor is configured to support the access controller to perform the corresponding function in the above-mentioned fifth aspect method.
  • the memory is coupled with the processor, and stores program instructions and data necessary for the access controller.
  • this application also provides an access device that has a function of implementing the behavior of the access device in the method example of the sixth aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the access device includes a receiving unit, a sending unit, and a processing unit. These units can perform the corresponding functions in the method example of the sixth aspect. For details, please refer to the detailed description in the method example. I won’t repeat it here.
  • the structure of the access device includes a transceiver and a processor, and optionally also includes a memory, the transceiver is used for sending and receiving data, and for communicating and interacting with other devices in the communication system
  • the processor is configured to support the access device to perform the corresponding function in the above-mentioned fifth aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the access device.
  • this application also provides an access controller, which has the function of realizing the behavior of the access controller in the method example of the seventh aspect.
  • the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the access controller includes a receiving unit, a sending unit, and a processing unit. These units can perform the corresponding functions in the method example of the seventh aspect. For details, refer to the detailed description in the method example. Do not repeat them here.
  • the structure of the access controller includes a transceiver, a processor, and optionally a memory, and the transceiver is used to send and receive data, and to communicate with other devices in the communication system
  • the processor is configured to support the access controller to perform the corresponding function in the above-mentioned seventh aspect method.
  • the memory is coupled with the processor, and stores program instructions and data necessary for the access controller.
  • the present application also provides a system that includes a source access device, and the source access device can be used to execute the first aspect and any one of the methods in the first aspect.
  • the system may further include an access controller, and the access controller may be used to execute the steps performed by the access controller in the first aspect and any of the methods of the first aspect.
  • the system may further include a target access device, and the target access device may be used to execute the steps performed by the target access device in the first aspect and any method of the first aspect.
  • the system may also include other devices, such as terminal devices, that interact with one or more of the source access device, access controller, and target access device in the solution provided in the embodiments of this application. Wait.
  • the present application also provides a system that includes an access controller, and the access controller can be used to execute the second aspect and any one of the methods in the second aspect described above.
  • the system may further include a source access device, and the source access device may be used to execute the steps performed by the source access device in any of the foregoing second aspect and the method of the second aspect.
  • the system may further include a target access device, and the target access device may be used to execute the steps performed by the target access device in the second aspect and any method of the second aspect.
  • the system may also include other devices, such as terminal devices, that interact with one or more of the source access device, access controller, and target access device in the solution provided in the embodiments of this application. Wait.
  • the present application also provides a system that includes a target access device, and the target access device can be used to execute the third aspect and any one of the methods in the third aspect.
  • the system may further include a source access device, and the source access device may be used to execute the steps performed by the source access device in any of the third aspect and the third aspect.
  • the system may further include an access controller, and the access controller may be used to execute the steps performed by the access controller in the third aspect and any method of the third aspect.
  • the system may also include other devices, such as terminal devices, that interact with one or more of the source access device, access controller, and target access device in the solution provided in the embodiments of this application. Wait.
  • the present application also provides a system that includes a terminal device, and the terminal device can be used to execute the steps performed by the terminal device in any of the foregoing fourth aspect and the fourth aspect.
  • the system may further include a target access device, and the target access device may be used to execute the steps performed by the target access device in any of the foregoing fourth aspect and the fourth aspect.
  • the system may also include other devices that interact with one or more of the terminal device and/or the target access device in the solution provided in the embodiments of the present application.
  • this application also provides a system, which includes an access device that can be used to perform any one of the fifth aspect and the fifth aspect, or the sixth and sixth aspects. Steps performed by the access device in any method of the aspect.
  • the system may further include an access controller, and the access controller may be used to perform any of the above-mentioned fifth aspect and the fifth aspect, or the sixth aspect and the sixth aspect. Steps executed by the access controller in any method.
  • the system may also include other devices, such as terminal devices, that interact with one or more of the access controller and/or access devices in the solution provided in the embodiments of the present application.
  • this application also provides a system that includes an access controller, and the access controller can be used to perform any of the fifth aspect and the fifth aspect, or the seventh aspect And the steps executed by the access controller in any method of the seventh aspect.
  • the system may further include an access device, and the access device may be used to perform any one of the fifth aspect and the fifth aspect, or any one of the seventh aspect and the seventh aspect. The steps performed by the access device in the method.
  • the system may also include other devices, such as terminal devices, that interact with one or more of the access controller and/or access devices in the solution provided in the embodiments of the present application.
  • the present application also provides a computer storage medium that stores computer-executable instructions, and the computer-executable instructions are used to make the computer execute when called by the computer Any of the methods mentioned above.
  • this application also provides a computer program product containing instructions that, when run on a computer, causes the computer to execute any of the methods mentioned above.
  • the present application also provides a chip, which is coupled with a memory, and is configured to read and execute program instructions stored in the memory to implement any of the above-mentioned methods.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by this application.
  • Figure 2 is a schematic diagram of a multicast structure provided by this application.
  • FIG. 3 is a schematic diagram of another multicast architecture provided by this application.
  • FIG. 4 is a flowchart of a communication method provided by this application.
  • FIG. 5 is a flowchart of an example of a communication method provided by this application.
  • FIG. 6 is a flowchart of an example of another communication method provided by this application.
  • FIG. 7 is a flowchart of an example of another communication method provided by this application.
  • FIG. 8 is a flowchart of an example of another communication method provided by this application.
  • FIG. 9 is a flowchart of an example of another communication method provided by this application.
  • FIG. 10 is a flowchart of an example of another communication method provided by this application.
  • FIG. 11 is a flowchart of a method for configuring multicast service information provided by this application.
  • FIG. 12 is a flowchart of a method for establishing a multicast service provided by this application.
  • FIG. 13 is a schematic structural diagram of a device provided by this application.
  • FIG. 14 is a schematic structural diagram of another device provided by this application.
  • Figure 15 is a schematic structural diagram of another device provided by this application.
  • FIG. 16 is a structural diagram of a source access device provided by this application.
  • FIG. 17 is a structural diagram of an access controller provided by this application.
  • FIG. 18 is a structural diagram of a target access device provided by this application.
  • the embodiments of the present application provide a communication method and device, which are used to realize a flexible switching process of a terminal device in a multicast service scenario.
  • the method and device described in the present application are based on the same inventive concept, and because the method and the device have similar principles for solving the problem, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • the source access device and target access device can provide terminal device access management functions, authentication functions, mobility management functions, session management functions, etc.; the source access device, the target access device
  • the incoming device can be used as an egress gateway for locally forwarded data connections to contact an external public data network (PDN) network, and can also be used as an anchor point for data connections when the terminal device moves.
  • PDN public data network
  • the source access device and the target access device may not be limited to wireless broadband access points (wireless broadband access point, WBAP), and support the WB-Uu interface with the terminal device , Supports the WB-1 interface with the access controller; can terminate air interface signaling and non-access stratum (NAS) messages.
  • WBAP wireless broadband access point
  • NAS non-access stratum
  • the access controller can provide user subscription storage and management functions, mobility management functions, policy control functions, access device configuration management functions, etc.; the access controller can be used as an exit for centralized forwarding data connections
  • the gateway communicates with the external PDN network and serves as the anchor point for the data connection when the terminal device moves.
  • the access controller described in this application may, but is not limited to, a wireless broadband access controller (WBAC), which may support a WB-1 interface with an access device (for example, WBAP).
  • WBAC wireless broadband access controller
  • FIG. 1 shows the architecture of a possible communication system to which the communication method provided in an embodiment of the present application is applicable.
  • the architecture of the communication system may include an access controller, at least one access device, and at least one terminal device.
  • the access controller and the at least one access device can be connected through a WB-1 interface
  • the access device and the terminal device can be connected through a WB-Uu interface.
  • the interface name is only an example description, and the embodiment of the present application does not specifically limit this. It should be understood that the embodiments of the present application are not limited to the communication system shown in FIG. 1.
  • the name of the device shown in FIG. 1 is only used as an example here, and is not used as a communication system architecture applicable to the communication method of the present application. Of the equipment.
  • the function of each network element or device in the communication system is described in detail below:
  • the terminal device is a device that provides voice and/or data connectivity to users.
  • the terminal device can support NAS messages defined by 3GPP.
  • the terminal device may be a wireless broadband customer-premises equipment (WBCPE).
  • WBCPE wireless broadband customer-premises equipment
  • future communications such as 6G, the terminal device may still be WBCPE or have other names, which is not limited by this application.
  • the access device can provide access management functions, authentication functions, mobility management functions, session management functions, and the like for the terminal device.
  • the access device can be used as the egress gateway of the locally forwarded data connection to contact the external PDN network, and can also be used as the anchor point of the data connection when the terminal device moves.
  • the access device can terminate air interface signaling and NAS messages.
  • the access device may be WBAP.
  • future communications, such as 6G the access device may still be WBAP or have other names, which is not limited by this application.
  • the access controller can provide user subscription storage and management functions, mobility management functions, policy control functions, access device configuration management functions, and so on.
  • the access controller can be used as an egress gateway for centralized forwarding of data connections to communicate with an external PDN network, and as an anchor point for data connections when the terminal device moves.
  • the access controller may be WBAC.
  • future communications, such as 6G the access controller may still be WBAC or have other names, which is not limited in this application.
  • FIG. 1 is not limited to only include the devices shown in the figure, and may also include other devices not shown in the figure, which are not specifically listed here in this application.
  • the communication system shown in FIG. 1 does not constitute a limitation of the communication system applicable to the embodiments of the present application.
  • the communication system architecture shown in FIG. 1 is a 5G system architecture.
  • the method in the embodiment of the present application is also applicable to various future communication systems, such as 6G or other communication networks.
  • the embodiment of the present application provides two multicast architectures, as shown in Figures 2 and 3, respectively.
  • the access device is WBAP as an example.
  • the access controller is WBAC as an example
  • the terminal device is WBCPE as an example.
  • a multicast channel is established between WBAC and WBAP, WBAC forwards the multicast service data to WBAP in a centralized manner, and then WBAP forwards the multicast service data to the corresponding WBCPE.
  • the multicast service data is sent to the WBAP through the external multicast source device, and then the WBAP forwards the multicast service data to the corresponding WBCPE.
  • the WBAC can be regarded as a multicast source device, which has the function of forwarding multicast service data by the multicast source device.
  • the multicast service data involved in this application may also be referred to as a multicast service data packet.
  • the communication method provided by an embodiment of the present application is suitable for the communication system shown in FIG. 1 and the multicast architecture shown in FIG. 2 or FIG. 3.
  • the specific process of the method may include:
  • Step 401 The source access device sends a first message to the access controller, where the first message is used to request the terminal device to be switched to the target access device, and the first message includes the multicast service context of the terminal device.
  • the first message may be a relocation request (Relocation Request) (that is, a handover request) sent by the source access device to the access controller.
  • Relocation Request that is, a handover request
  • the multicast service context of the terminal device may include, but is not limited to, the identifier of the multicast group that the terminal device requests to join, and the multicast address (that is, the destination of the multicast packet that needs to be forwarded). Address), multicast source address and other information.
  • the access controller may determine the target access device according to the multicast service context of the terminal device in the first message Whether the terminal device is subscribed to the multicast service currently performed by the terminal device, when it is determined that the target access device is not subscribed to the multicast service currently performed by the terminal device, the target access device is added to the terminal device currently performing Multicast business.
  • the access controller may determine the multicast service performed by the terminal device according to the identifier of the multicast group that the terminal device requests to join included in the first message, and then according to the locally stored information about the target access The relevant information of the incoming device obtains the status that the target access device has subscribed to the multicast service, and based on this, it is determined whether the target access device subscribes to the multicast service currently performed by the terminal device.
  • the first message may also carry first information, and the first information may include one or more of the following information: the connection context information of the connection established by the terminal device on the source access device, The mobility management context of the terminal device, the container from the source access device to the target access device (Source WBAP to Target WBAP container), the Source WBAP to Target WBAP container may include one or more first parameters, The first parameter may be a parameter required when the terminal device performs handover.
  • the first message may also carry the identification of the target access device.
  • the first message may also carry other information, and the embodiments of the present application will not list them one by one here.
  • the connection context information involved in the embodiments of the present application may include one or more of the following information: PDN context information, PDU context information, and bearer context information.
  • the specific protocol type of the message involved in the embodiments of this application can be control and provisioning of wireless access points (CAPWAP), or simple network management protocol (SNMP) , It may also be other protocols, and the embodiment of the present application does not specifically limit the message protocol type here.
  • CAPWAP wireless access point
  • SNMP simple network management protocol
  • the embodiment of the present application does not specifically limit the message protocol type here.
  • the CAPWAP protocol is used as an example to describe the message in the embodiment of the present application.
  • the messages involved in the embodiments of this application may have two formats.
  • One format is CAPWAP Message (Vendor Specific (List of 3GPP specific message container)), where List of 3GPP specific message container can be the target node ID (Target Node ID) + message body (message container), where Target Node ID Indicates the destination receiver of the information in the message container.
  • the Target Node ID may also be an optional information element. For example, if the Target Node ID is not included in the message, it means that the receiving end of the information carried in the corresponding message container is the preset target node, such as WBAC.
  • the message container carries specific information.
  • CAPWAP Message Vendor Specific (Forward container, Direct container)
  • Forward container represents a message that the access controller does not need to parse but can directly forward the message
  • the format is the same as List of 3GPP specific message container.
  • Direct container indicates the message that the access controller needs to parse, and the format can be the same as List of 3GPP specific message container, or the same as message container.
  • the first message may be a wireless termination point (wireless termination points, WTP) event request (Event Request) message in the CAPWAP protocol.
  • the format of the first message can be WTP Event Request (V[Target WBAP ID, Relocation Request]), Target WBAP ID can be the identifier of the access controller, and Relocation Request is used to notify the receiving end terminal device to switch to the target connection. Enter the device, the Relocation Request can carry the first information.
  • the first message may be a Relocation Request. Therefore, the source access device can send the first message to the access controller through WTP Event Request (V[Target WBAP ID, Relocation Request]).
  • the source access device may determine the target access device according to the second information.
  • the second information may include one or more of the following information: a measurement report sent by the terminal device to the source access device, load information of multiple access devices, and the mobility management context of the terminal device.
  • the source access device may obtain load information of the multiple access devices from the access controller. Specifically, the source access device may periodically query the access controller for load information of multiple access devices, or the access controller may also periodically push the load information of multiple access devices to the source access device.
  • the multiple access devices may be any multiple access devices in the communication system, multiple adjacent access devices of the source access device, or all access devices in the communication system.
  • the source access device may also determine the target access device according to other information, which is not specifically limited in the embodiment of the present application.
  • Step 402 The access controller sends a second message to the target access device, where the second message includes the multicast service context of the terminal device.
  • the second message may be used to request to switch the terminal device to the target access device, and the second message may be a Relocation Request sent by the access controller to the target access device.
  • the access controller may determine whether it is necessary to carry the first multicast tunnel establishment information in the second message according to the actual situation, wherein the first multicast tunnel establishment information is used for To establish a tunnel for transmitting multicast service data.
  • the tunnel is a tunnel established between the target access device and the access controller, and is mainly used by the access controller to transmit data related to the multicast service to the target access device.
  • the tunnel established can be control and provisioning of wireless access points (CAPWAP) data (DATA) channel information, or other protocols, such as GTP-U tunnel endpoints Information, etc., are not specifically limited in this application.
  • the access controller may determine whether it is necessary to carry the first multicast tunnel establishment information according to the following conditions:
  • the access controller determines that the protocol of the tunnel for transmitting multicast service data between the access controller and the target access device is GTP-U
  • the access controller The second message carries the first multicast tunnel establishment information.
  • the first multicast tunnel establishment information may be the GTP- allocated by the access controller for the multicast service.
  • U tunnel endpoint information In this case, the access controller has determined that the target access device has not subscribed to the multicast service currently performed by the terminal device.
  • the access controller determines that the CAPWAP DATA channel or other pre-established channels can be used between the access controller and the target access device to transmit multicast service data .
  • the access controller does not need to carry the first multicast tunnel establishment information in the second message.
  • the target access device after the target access device receives the second message from the access controller, when the target access device uses the multicast service context of the terminal device When it is determined that it has not subscribed to the multicast service currently performed by the terminal device, the target access device sends a third message to the multicast source device, and the third message is used to subscribe to the multicast service currently performed by the terminal device .
  • the exemplary third message may be an Internet group management protocol (Internet group management protocol, IGMP) join message sent by the target access device to the multicast source device.
  • the multicast source device may be, but not limited to, a router. It should be noted that all the multicast source devices involved in this application may be routers, which are not limited in this application.
  • the second message may also carry first information.
  • the access controller may send the first information to the target access device through the second message according to the identifier of the target access device carried in the first message.
  • the second message may also carry other information, which is not listed here in the embodiment of the present application.
  • the second message may be a Station Configuration Request (Station Configuration Request) message in the CAPWAP protocol.
  • the format of the second message may be Station Configuration Request (V[Target WBAP ID, Relocation Request]), and Target WBAP ID may be the identification of the target access device.
  • the second message may be a Relocation Request. Therefore, the access controller can send the second message to the target access device through Station Configuration Request (V[Target WBAP ID, Relocation Request]).
  • Step 403 The target access device sends a fourth message to the access controller, where the fourth message is used to respond to a request message for switching the terminal device to the target access device.
  • the fourth message may be a relocation response (Relocation Response) (that is, a handover response) sent by the target access device to the access controller.
  • relocation Response that is, a handover response
  • the fourth message may include information indicating whether to forward the multicast service data. Specifically, when the target access device determines that it has subscribed to the multicast service currently performed by the terminal device, the fourth message may include a multicast group subscribed indication, indicating that it does not Need to forward multicast service data.
  • the fourth message may also include the forwarding tunnel endpoint identifier of the target access device, so that the access controller can send the forwarding tunnel endpoint of the target access device to After the identifier is forwarded to the source access device, the source access device may directly forward the multicast service data to the target access device according to the forwarding tunnel identifier of the target access device.
  • the process in which the source access device can directly forward multicast service data to the target access device according to the forwarding tunnel identifier of the target access device is that the source access device according to the target access device After establishing a tunnel for forwarding multicast service data and forwarding the multicast service data to the target access device, the endpoint identifier of the forwarding tunnel is established.
  • the fourth message may also include the forwarding tunnel endpoint identifier of the target access device, so that the access controller can be based on the forwarding tunnel of the target access device
  • the endpoint identifier forwards the multicast service data received from the source access device to the target access device.
  • the source access device may forward the multicast service data to the target access device through the access controller.
  • the access controller obtains the forwarding tunnel endpoint identifier of the target access device, it determines the connection between the access controller and the target access device according to the forwarding tunnel endpoint identifier of the target access device
  • the multicast data service tunnel is forwarded to the target access device when the multicast service data forwarded by the source access device is received.
  • the target access The device may also carry second multicast tunnel establishment information in the fourth message, and the second multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the second multicast tunnel establishment information is the multicast tunnel establishment information of the target access device, and is used to establish a tunnel for transmitting multicast service data with the access controller, where the establishment The tunnel for transmitting multicast service data is used for the target access device to transmit multicast service-related data to the access controller when the target access device performs the multicast service. In this way, a tunnel for transmitting multicast service data can be established between the target access device and the access controller, and the multicast service data can be subsequently transmitted through the tunnel.
  • Step 404 The access controller sends a fifth message to the source access device, where the fifth message is used to respond to a request message for switching the terminal device to the target access device.
  • the fifth message Contains information indicating whether to forward multicast service data.
  • the fifth message may be a Relocation Response sent by the access controller to the source access device.
  • the fifth message includes indication information whether to forward the multicast service data, which can be specifically divided into the following two situations:
  • the fourth message mentioned above includes the indication information of whether to forward multicast service data, and the access controller may directly determine whether to forward the multicast service data included in the fourth message.
  • the indication information of is included in the fifth message.
  • the indication information of whether to forward multicast service data may be implicit indication information or displayed indication information. Specifically, it may be: when the target access device needs to forward multicast service data, the indication information includes The identifier of the tunnel endpoint allocated by the target access device for forwarding the multicast service data.
  • the optional indication information also carries an indication for forwarding the multicast service data.
  • the value of the indication may be "forward multicast service data "Or “not subscribed to the multicast service", etc., this application does not restrict this.
  • the indication information does not carry the tunnel identifier allocated by the target access device for forwarding the multicast service data, and optionally may carry a non-forwarding group
  • the value of the instruction can be "do not forward multicast service data" or "subscribed to the multicast service", etc. This application does not limit this.
  • the access controller includes the indication information of whether to forward the multicast service data in the second message according to whether the target access device subscribes to the multicast service currently performed by the terminal device. In this case a2, the access controller does not parse whether the fourth message contains the indication information of whether to forward the multicast service data, and directly determines whether the target access device subscribes to the terminal device by itself The current multicast service.
  • the indication information of whether to forward the multicast service data may be implicit indication information or displayed indication information. Specifically, it may be: when the target access device does not subscribe to the multicast service currently performed by the terminal device At this time, the indication information may not carry any indication, or may carry an indication to forward multicast service data, and the value of the indication may be "forward multicast service data" or "unsubscribed multicast service” or multicast service The present invention does not limit this.
  • the indication information may carry an indication not to forward the multicast service data, and the value of the indication may be "Do not forward the multicast service "Data” or “Subscribed to multicast service data", etc., the optional indication information may also carry the identifier of the multicast service, which is not limited in this application.
  • the fifth message may also have the following two situations:
  • the fifth message also includes the forwarding tunnel endpoint identifier of the target access device, that is, the forwarding tunnel endpoint of the target access device included in the fourth message described in step 403 above
  • the identifier is included in the fifth message. In this way, the source access device can directly forward the multicast service data to the target access device.
  • the fifth message may also include the forwarding tunnel endpoint identifier of the access controller, so that the source access device can report to the access controller according to the forwarding tunnel identifier of the access controller.
  • the incoming controller sends the data of the multicast service.
  • the source access device may forward multicast service data to the access controller according to the forwarding tunnel identifier of the access controller, that is, the source access device according to the access controller After establishing a forwarding tunnel endpoint identifier of the source access device and the access controller, a tunnel for forwarding multicast service data is established, and the multicast service data is forwarded to the access controller.
  • the source access device indirectly forwards the multicast service data to the target access controller through the access controller.
  • the source access device forwards the multicast service data to the access controller.
  • the access controller forwards the multicast service data to the target access device (specifically, the access controller described in step 403 may be used according to the fourth message
  • the source access device after the source access device receives the fifth message, it decides whether to forward the multicast service data according to the indication information of whether to forward the multicast service data. Specifically, when the indication information of whether to forward the multicast service data indicates that the multicast service data needs to be forwarded, the source access device performs the forwarding according to the target access device's forwarding information contained in the fifth message.
  • the tunnel endpoint identifier is used to establish a tunnel for forwarding multicast service data, and forward the multicast service data directly to the target access device through the tunnel for forwarding multicast service data; or, the source access device according to the fifth
  • the forwarding tunnel endpoint identifier of the access controller included in the message establishes a tunnel for forwarding multicast service data between the source access device and the access controller, and passes the multicast service data through the source
  • the tunnel for forwarding multicast service data between the access device and the access controller is forwarded to the access controller, and then the access controller forwards the multicast service data to the target access device .
  • the source access device When the indication information of whether to forward the multicast service data indicates that the multicast service data does not need to be forwarded, the source access device does not matter whether it receives the forwarding tunnel endpoint identifier or connection assigned by the target access device. When entering the controller's forwarding tunnel endpoint identifier, no multicast service data is forwarded.
  • the communication between the source access device and the target access device can be called a direct forwarding tunnel.
  • the source access device can directly forward any data related to the multicast service to the target access device through the direct forwarding tunnel; when the source access device passes through
  • the tunnel between the source access device and the access controller for forwarding multicast service data and the access
  • the tunnel for forwarding multicast service data between the controller and the target access device may be referred to as an indirect forwarding tunnel.
  • the source access device may indirectly communicate to the target through the access controller through the indirect forwarding tunnel.
  • the access device forwards any data related to the multicast service.
  • the source access device may determine according to the fifth message whether the target access device subscribes to the The current multicast service performed by the terminal device.
  • the source access device when the target access device does not subscribe to the multicast service currently performed by the terminal device, notifies the terminal device to subscribe to the terminal device through the target access device The current multicast service performed by the terminal device.
  • the source access device determines whether the target access device subscribes to the multicast service currently performed by the terminal device according to the fifth message, which specifically can be divided into the following situations:
  • the source access device may base on the group currently subscribed to or carried by the target access device
  • the identifier of the broadcast service determines whether the target access device subscribes to the multicast service currently performed by the terminal device.
  • Case b2 When the fifth message contains the information that the target access device has not subscribed to the multicast service currently performed by the terminal device, the source access device determines the target access device according to the information Not subscribing to the multicast service currently performed by the terminal device.
  • Case b3 When the indication information of whether to forward multicast service data included in the fifth message indicates to forward multicast service data, the source access device determines that the target access device does not subscribe to the terminal Multicast services currently performed by the device.
  • the source access device notifies the terminal device to subscribe to the multicast service currently performed by the terminal device through the target access device.
  • the specific method may be:
  • the multicast source device adds the target access device to the multicast service currently performed by the terminal device. Specifically, the terminal device sends a seventh message to the target access device, where the seventh message is used to indicate that the target access device does not subscribe to the multicast service currently performed by the terminal device, or to the target The access device requests to subscribe to the multicast service currently performed by the terminal device;
  • the target access device sends a nineteenth message to the multicast source device, where the nineteenth message is used to instruct the multicast source device to add the target access device to the multicast service currently performed by the terminal device .
  • the sixth message may be a handover command (handover command) message sent by the source access device to the terminal device.
  • the seventh message may be an IGMP Join message.
  • the process of forwarding multicast service data between the source access device and the target access device may be terminated according to different settings.
  • a specific example may be as follows:
  • Example c1 In the case that the target access device has set a data forwarding timer, the target access device starts the data forwarding timer when receiving multicast service data from the source access device When the data forwarding timer expires, the target access device starts the tunnel deletion timer, and sends an eighth message to the access controller, the eighth message is used to request to stop data transmission; The access controller forwards the eighth message to the source access device, so that the source access device stops forwarding multicast service data to the target access device, and causes the source access device to delete the forwarding group When the tunnel deletion timer expires, the target access device deletes the tunnel for forwarding multicast service data.
  • Example c2 When the source access device sets a data forwarding timer, when the source access device sends multicast service data to the target access device for the first time, the data forwarding timer is started; When the data forwarding timer expires, the source access device sends a ninth message to the target access device and deletes the tunnel for forwarding multicast service data; wherein, the ninth message is used to indicate that the data forwarding is complete; After the target access device receives the ninth message from the source access device, it deletes the tunnel for forwarding the multicast service data.
  • Example c3 When the source access device sets a data forwarding timer, when the source access device sends multicast service data to the target access device for the first time, the data forwarding timer is started; when When the data forwarding timer expires, the source access device sends a tenth message to the target access device through the access controller, and deletes the tunnel for forwarding multicast service data; wherein, the tenth message The message is used to indicate the completion of data forwarding; the access controller forwards the tenth message to the target access device, and the target access device deletes the tunnel for forwarding multicast service data after receiving the tenth message .
  • Example c4 In the case that the target access device and the source access device respectively set data forwarding timers, when the source access device sends multicast service data to the target access device for the first time, the set Data forwarding timer; when the target access device receives multicast service data from the source access device, it starts the set data forwarding timer; the target access device and the source access device are at When their respective forwarding timers expire, their respective tunnels for transmitting multicast service data are deleted.
  • the terminal device can flexibly perform the switching process during the switching between the access devices, and the continuity of the multicast service can be guaranteed without the need for a fixed anchor point to participate in the switching of the terminal device.
  • the waste of resources caused by the deployment of fixed anchor points can be avoided.
  • the terminal device is WBCPE
  • the access controller is WBAC
  • the access device is WBAP (where the source access device is S WBAP, and the target access device is T WBAP) as an example.
  • the multicast source device is the router as an example.
  • the embodiment of the present application also provides an example of a communication method.
  • This example can be applied to the multicast architecture shown in FIG. 2.
  • the process of this example may include:
  • Step 501 S WBAP sends a first message to WBAC, the first message is used to request to switch WBCPE to T WBAP, and the first message includes the multicast service context of WBCPE.
  • Step 502 The WBAC judges whether TWBAP subscribes to the multicast service currently performed by the WBCPE according to the multicast service context of the WBCPE, and when it is determined that the TWBAP does not subscribe to the multicast service currently performed by the WBCPE The T WBAP joins the multicast service currently performed by the WBCPE.
  • the WBAC adds the TWBAP to the multicast service currently performed by the WBCPE in specific implementation, it means that the WBAC adds the TWBAP to the multicast group of the multicast service currently performed by the WBCPE That is, the subsequent WBAC will send the multicast service data (that is, the data packet of the multicast service) to the TWBAP.
  • the subsequent process when multicast service data is transmitted between the WBAC and the TWBAP, it is established through the first multicast tunnel according to the access controller involved in the embodiment shown in FIG. 4 Information about the tunnel for transmitting multicast service data established with the target access device, and the transmission of multicast services established between the target access device and the access controller through the second multicast tunnel establishment information The data tunnel realizes the transmission of multicast service data.
  • Step 503 The WBAC sends a second message to the TWBAP, the second message is used to request to switch the WBCPE to the TWBAP, and the second message includes the multicast service context of the WBCPE.
  • Step 504 The TWBAP sends a fourth message to the WBAC, where the fourth message is used to respond to a request message for switching WBAP for the WBCPE.
  • Step 505 The WBAC sends a fifth message to the S WBAP, the fifth message is used to respond to a request message for switching WBAP for the WBCPE, and the fifth message includes indication information whether to forward multicast service data .
  • Step 506 The S WBAP sends an eleventh message to the WBCPE, where the eleventh message is used to instruct the WBCPE to perform handover.
  • the eleventh message may be a handover command (Handover Command) message sent by the S WBAP to the WBCPE.
  • Handover Command handover command
  • Step 507 The SWBAP forwards the multicast service data to the TWBAP.
  • Step 508 The TWBAP starts a data forwarding timer.
  • Step 509 When the data forwarding timer expires, the TWBAP starts a tunnel deletion timer.
  • Step 510 The TWBAP sends an eighth message to the WBAC, where the eighth message is used to request to stop data transmission.
  • the eighth message may be a stop data forwarding request (stop data forwarding request) sent by the TWBAP to the WBAC.
  • Step 511 The WBAC forwards the eighth message to the SWBAP.
  • Step 512 When the tunnel deletion timer expires, the TWBAP deletes the tunnel for forwarding multicast service data.
  • Step 513 The S WBAP sends a twelfth message to the WBAC, and deletes the tunnel for forwarding multicast service data, and the twelfth message is used to respond to the data stop forwarding request of the eighth message.
  • the twelfth message may be a stop data forwarding response (stop data forwarding response).
  • Step 514 The WBAC forwards the twelfth message to the TWBAP.
  • step 513 and step 514 is an optional step, which is not limited in this application.
  • WBCPE can flexibly perform the handover process during the handover process between the access devices, and the continuity of the multicast service can be guaranteed without the need for a fixed anchor point to participate in the WBCPE handover. This can be caused by the deployment of fixed anchor points. Waste of resources.
  • the embodiment of the present application also provides an example of a communication method.
  • This example can be applied to the multicast architecture shown in FIG. 2.
  • the process of this example may include:
  • Step 601 to step 607 are similar to step 501 to step 507 in the embodiment shown in FIG. 5, and can refer to each other for details, and will not be repeated here.
  • the following steps 608 to 610 may be performed:
  • Step 608 The S WBAP starts the data forwarding timer.
  • Step 609 When the data forwarding timer expires, the SWBAP sends a ninth message to the TWBAP, where the ninth message is used to indicate that the data forwarding is complete.
  • the ninth message may be in the form of an end marker (end marker) packet generated by the S WBAP.
  • Step 610 The S WBAP deletes the tunnel for forwarding multicast service data.
  • Step 611 The TWBAP deletes the tunnel for forwarding multicast service data.
  • Step 612 The SWBAP starts the data forwarding timer.
  • Step 613 When the data forwarding timer expires, the S WBAP sends a tenth message to the WBAC, where the tenth message is used to indicate that the data forwarding is completed.
  • the tenth message may be in the form of an end marker (end marker) packet generated by the S WBAP, or may be a control plane message.
  • Step 614 The S WBAP deletes the tunnel for forwarding multicast service data.
  • Step 615 The WBAC forwards the tenth message to the TWBAP.
  • Step 616 The TWBAP deletes the tunnel for forwarding multicast service data.
  • the following steps 617 to 620 may be performed:
  • Step 617 The S WBAP starts a data forwarding timer.
  • Step 618 The TWBAP starts a data forwarding timer.
  • Step 619 When the data forwarding timer set by the SWBAP expires, the SWBAP deletes the tunnel for forwarding the multicast service data.
  • Step 620 When the data forwarding timer set by the TWBAP expires, the TWBAP deletes the tunnel for forwarding the multicast service data.
  • WBCPE can flexibly perform the handover process during the handover process between the access devices.
  • the continuity of the multicast service can be ensured without the need for a fixed anchor point to participate in the WBCPE handover. This can be caused by the deployment of fixed anchor points. Waste of resources.
  • the embodiment of the present application also provides an example of a communication method, which can be applied to the multicast architecture shown in FIG. 3. Specifically, the flow of this example may include:
  • Step 701 is similar to step 501 in the embodiment shown in FIG. 5, and reference may be made to each other for details, and details are not repeated here.
  • Step 702 is similar to step 503 in the embodiment shown in FIG. 5, and reference may be made to each other for details, and details are not repeated here.
  • Step 703 When the TWBAP determines that it has not subscribed to the multicast service currently performed by the WBCPE according to the context of the multicast service of the WBCPE, it sends a third message to the router, and the third message is used to subscribe to the currently performed WBCPE. Multicast business.
  • the router After receiving the third message, the router adds the TWBAP to the multicast service currently performed by the WBCPE.
  • Steps 704 to 714 are similar to steps 50 to 514 in the embodiment shown in FIG. 5, and can refer to each other for details, and will not be repeated here.
  • the embodiment of the present application also provides an example of a communication method, which can be applied to the multicast architecture shown in FIG. 3. Specifically, the process of this example may include:
  • Step 801 is similar to step 601 in the embodiment shown in FIG. 6, and reference may be made to each other for details, and details are not repeated here.
  • Step 802 is similar to step 603 in the embodiment shown in FIG. 6, and reference may be made to each other for details, and details are not repeated here.
  • Step 803 When the TWBAP determines that it has not subscribed to the multicast service currently performed by the WBCPE according to the multicast service context of the WBCPE, it sends a third message to the router, and the third message is used to subscribe to the current multicast service performed by the WBCPE. Multicast business.
  • the router After receiving the third message, the router adds the TWBAP to the multicast service currently performed by the WBCPE.
  • Steps 804 to 820 are similar to steps 604 to 620 in the embodiment shown in FIG.
  • the embodiment of the present application also provides an example of a communication method, which can be applied to the multicast architecture shown in FIG. 3. Specifically, the flow of this example may include:
  • Step 901 and step 902 are similar to step 701 and step 702 in the embodiment shown in FIG. 7, and reference may be made to each other for details, and details are not repeated here.
  • Step 903 and step 904 are similar to step 704 to step 705 in the embodiment shown in FIG.
  • Step 905 The S WBAP determines that the T WBAP has not subscribed to the multicast service currently performed by the WBCPE, and the S WBAP sends a sixth message to the WBCPE, and the sixth message includes the current subscription to the WBCPE. Notification information of the multicast service.
  • the SWBAP determines that the TWBAP has not subscribed to the multicast service currently performed by the WBCPE, refer to the source access device involved in step 404 in the embodiment shown in FIG. 4 for determining the target access according to the fifth message.
  • the inbound device has not subscribed to the relevant description of the multicast service currently performed by the terminal device, which will not be repeated here.
  • the sixth message is used to instruct the WBCPE to switch, and may be a handover command sent by the S WBAP to the WBCPE.
  • Step 906 When the WBCPE determines that the TWBAP has not subscribed to the multicast service currently performed by the WBCPE, the WBCPE sends a seventh message to the TWBAP, and the seventh message is used to indicate that the TWAAP is not Subscribe to the multicast service currently performed by the WBCPE, or request the TWAAP to subscribe to the multicast service currently performed by the WBCPE.
  • Step 907 The TWBAP sends a nineteenth message to the router, where the nineteenth message is used to instruct the router to add the TWBAP to the multicast service currently performed by the WBCPE.
  • Steps 908 to 915 are similar to steps 707 to 714 in the embodiment shown in FIG.
  • an embodiment of the present application also provides an example of a communication method, which can be applied to the multicast architecture shown in Fig. 3. Specifically, the process of this example may include:
  • Step 1001 and step 1002 are similar to step 801 and step 802 in the embodiment shown in FIG. 8, and reference may be made to each other for details, and details are not repeated here.
  • Step 1003 and step 1004 are similar to step 804 to step 805 in the embodiment shown in FIG. 8, and reference may be made to each other for details, and details are not repeated here.
  • Step 1005 The S WBAP determines that the T WBAP has not subscribed to the multicast service currently performed by the WBCPE, and the S WBAP sends a sixth message to the WBCPE.
  • the sixth message includes the current subscription to the WBCPE. Notification information of the multicast service.
  • the sixth message is used to instruct the WBCPE to switch, and may be a handover command sent by the S WBAP to the WBCPE.
  • Step 1006 When the WBCPE determines that the TWBAP has not subscribed to the multicast service currently performed by the WBCPE, the WBCPE sends a seventh message to the TWBAP, and the seventh message is used to indicate that the TWAAP is not Subscribe to the multicast service currently performed by the WBCPE, or request the TWAAP to subscribe to the multicast service currently performed by the WBCPE.
  • Step 1007 The TWBAP sends a nineteenth message to the router, where the nineteenth message is used to instruct the router to add the TWBAP to the multicast service currently performed by the WBCPE.
  • Step 1008 to step 1021 are similar to step 807 to step 820 in the embodiment shown in FIG. 8, and reference may be made to each other for details, and details are not repeated here.
  • an embodiment of the present application provides a method for configuring multicast service information, which describes the negotiation process of a tunnel protocol used to transfer multicast service data between an access device and an access controller.
  • the process of this method can include:
  • Step 1101 The access device sends a thirteenth message to the access controller, where the thirteenth message includes the protocol of the tunnel for transmitting multicast service data supported by the access device.
  • the thirteenth message may be a join request (join request) message sent by the access device to the access controller.
  • the protocol of the tunnel for transmitting the multicast service data supported by the access device may be CAPWAP Data or GTP-U or other protocol types.
  • the thirteenth message when the protocol of the tunnel for transmitting multicast service data supported by the access device is GTP-U, the thirteenth message also includes the tunnel endpoint of the access device Identifier, such as the GTP-U tunnel endpoint identifier.
  • Step 1102 The access controller sends a fourteenth message to the access device, where the fourteenth message is used to respond to the thirteenth message, and the fourteenth message includes the access control The protocol of the tunnel to transmit multicast service data supported by the router.
  • the fourteenth message may be a join response (join response) message sent by the access controller to the access device.
  • the protocol of the tunnel for transmitting multicast service data supported by the access controller may be CAPWAP Data or GTP-U or other protocol types.
  • the fourteenth message when the protocol of the tunnel for transmitting multicast service data supported by the access controller is GTP-U, the fourteenth message also includes the access controller's Tunnel endpoint identifier, such as GTP-U tunnel endpoint identifier.
  • an embodiment of the present application provides a method for establishing a multicast service.
  • the process of the method may include:
  • Step 1200 The terminal device has completed network registration and established a PDN/PDU session connection.
  • Step 1201 The terminal device sends a fifteenth message to the access device, the fifteenth message is used to request the establishment of a multicast service, and the fifteenth message includes the address of the multicast service and the terminal device Logo.
  • Step 1202 The access device sends a sixteenth message to the access controller, where the sixteenth message is used to request the establishment of the multicast service, and the sixteenth message includes the identification of the terminal device and The address of the multicast service.
  • the sixteenth message further includes third multicast tunnel establishment information, and the third multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the third multicast tunnel establishment information may be a multicast service tunnel endpoint identifier.
  • Step 1203 The access controller sends a seventeenth message to the access device, where the seventeenth message is used to indicate that the terminal device is allowed to establish the multicast service, and the seventeenth message includes The identifier of the terminal device and the address of the multicast service.
  • the access controller determines that the terminal device can use the multicast service according to the subscription information and configuration information of the terminal device, and then sends the seventeenth message.
  • the seventeenth message may be a WTP Event Response message.
  • the seventeenth message further includes fourth multicast tunnel establishment information, and the fourth multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the fourth multicast tunnel establishment information may be a multicast service tunnel endpoint identifier.
  • Step 1204 When the access device determines that it has not subscribed to the multicast service, the access device sends an eighteenth message to the access controller or the multicast source device, where the eighteenth message is used for Subscribe to the multicast service.
  • Step 1205 The access controller or the multicast source device adds the access device to the multicast service.
  • step 1203 the access controller may add the access device to the multicast service when it is determined that the access device has not subscribed to the multicast service. business.
  • the establishment of a multicast service can be realized, so that subsequent terminal devices can perform the required multicast service.
  • an embodiment of the present application also provides a device, which is applied to a source access device.
  • the apparatus 1300 may specifically be a processor in a source access device, or a chip or a chip system, or a functional module.
  • the apparatus 1300 may include a sending unit 1301, a receiving unit 1302, and a processing unit 1303.
  • the sending unit 1301 is used for the device 1300 to send information
  • the receiving unit 1302 is used for the device 1300 to receive information
  • the processing unit 1303 is used for controlling and managing the actions of the device 1300.
  • the processing unit 1303 may also be used to indicate the processing procedure of the source access device (for example, S WBAP) in any of the foregoing embodiments and/or other procedures of the technical solution described in this application. Specifically, the processing unit 1303 may control the steps performed by the sending unit 1301 and the receiving unit 1302. For details, please refer to the above-mentioned embodiment, and the repetitions will not be repeated here.
  • S WBAP processing procedure of the source access device
  • the aforementioned processing unit 1303 can be a processor or a processing circuit, etc.; the sending unit 1301 can be a transmitter or a sending circuit, etc., the receiving unit 1302 can be a receiver or a receiving circuit, etc., and the sending unit 1301 and the receiving unit 1302 can be Form a transceiver.
  • an embodiment of the present application also provides a device, which is applied to an access controller.
  • the apparatus 1400 may specifically be a processor in a source access device, or a chip or a chip system, or a functional module.
  • the apparatus 1400 may include a sending unit 1401, a receiving unit 1402, and a processing unit 1403.
  • the sending unit 1401 is used for the device 1400 to send information
  • the receiving unit 1402 is used for the device 1400 to receive information
  • the processing unit 1403 is used for controlling and managing the actions of the device 1400.
  • the processing unit 1403 may also be used to indicate the processing procedure involving the access controller (for example, WBAC) in any of the foregoing embodiments and/or other procedures of the technical solution described in this application. Specifically, the processing unit 1403 may control the steps performed by the sending unit 1401 and the receiving unit 1402. For details, please refer to the above-mentioned embodiment, and the repetitive parts will not be repeated here.
  • WBAC access controller
  • the aforementioned processing unit 1403 can be a processor or a processing circuit, etc.; the sending unit 1401 can be a transmitter or a sending circuit, etc., the receiving unit 1402 can be a receiver or a receiving circuit, etc., and the sending unit 1401 and the receiving unit 1402 can be Form a transceiver.
  • the embodiment of the present application also provides a device, which is applied to the target access device.
  • the apparatus 1500 may specifically be a processor in a source access device, or a chip or a chip system, or a functional module.
  • the apparatus 1500 may include a sending unit 1501, a receiving unit 1502, and a processing unit 1503.
  • the sending unit 1501 is used for the device 1500 to send information
  • the receiving unit 1502 is used for the device 1500 to receive information
  • the processing unit 1503 is used for controlling and managing the actions of the device 1500.
  • the processing unit 1503 may also be used to indicate the processing procedure of the target access device (for example, TWBAP) in any of the foregoing embodiments and/or other procedures of the technical solution described in this application. Specifically, the processing unit 1503 may control the steps performed by the sending unit 1501 and the receiving unit 1502. For details, please refer to the above-mentioned embodiment, and the repetitive parts will not be repeated here.
  • TWBAP target access device
  • the aforementioned processing unit 1503 can be a processor or a processing circuit, etc.; the sending unit 1501 can be a transmitter or a sending circuit, etc., the receiving unit 1502 can be a receiver or a receiving circuit, etc., and the sending unit 1501 and the receiving unit 1502 can be Form a transceiver.
  • the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including a number of instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .
  • the embodiment of the present application also provides another source access device for implementing the communication method.
  • the source access device 1600 may include a transceiver 1601 and a processor 1602.
  • the source access device 1600 may further include a memory 1603.
  • the memory 1603 may be provided inside the source access device 1600, and may also be provided outside the source access device 1600.
  • the processor 1602 controls the transceiver 1601 to receive and send data, and is used to implement the method executed by the source access device (for example, S WBAP) in FIGS. 4-10.
  • the processor 1602 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor 1602 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
  • the transceiver 1601, the processor 1602, and the memory 1603 are connected to each other.
  • the transceiver 1601, the processor 1602, and the memory 1603 are connected to each other through a bus 1604;
  • the bus 1604 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard Structure (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in FIG. 16, but it does not mean that there is only one bus or one type of bus.
  • the source access device when the source access device implements the communication method shown in FIG. 4, it may specifically include:
  • the transceiver 1601 is used to receive and send data
  • the processor 1602 is configured to control the transceiver 1601 to send a first message to the access controller, where the first message is used to request to switch the terminal device to the target access device, and the first message includes the terminal The multicast service context of the device; and controlling the transceiver 1601 to receive a fifth message from the access controller, where the fifth message is used to respond to a request message for the terminal device to switch to the target access device, the first Five messages contain the indication information of whether to forward the multicast service data.
  • the processor 1602 is further configured to determine, according to the fifth message, whether the target access device subscribes to the multicast service currently performed by the terminal device.
  • the processor 1602 is further configured to: when the target access device does not subscribe to the multicast service currently performed by the terminal device, notify the terminal device to subscribe through the target access device The current multicast service performed by the terminal device.
  • processor 1602 determines according to the fifth message whether the target access device subscribes to the multicast service currently performed by the terminal device, it is specifically configured to:
  • the target access device is determined according to the identifier of the multicast service currently subscribed or carried by the target access device. Whether the incoming device subscribes to the multicast service currently performed by the terminal device; or
  • the fifth message also includes information that the target access device has not subscribed to the multicast service currently performed by the terminal device, it is determined according to the information that the target access device has not subscribed to the current multicast service performed by the terminal device.
  • Multicast service or
  • the indication information included in the fifth message indicates to forward multicast service data, it is determined that the target access device has not subscribed to the multicast service currently performed by the terminal device.
  • the processor 1602 when the indication information indicates to forward multicast service data, the processor 1602 is further configured to:
  • the fifth message also includes the forwarding tunnel endpoint identifier of the target access device, and a tunnel for forwarding multicast service data is established according to the forwarding tunnel endpoint identifier of the target access device;
  • the fifth message also includes the forwarding tunnel endpoint identifier of the access controller, and a tunnel for forwarding multicast service data is established according to the forwarding tunnel endpoint identifier of the access controller.
  • the processor 1602 when the indication information indicates to forward multicast service data, the processor 1602 is further configured to: control the transceiver 1601 to receive the eighth message from the access controller, The eighth message is used to request to stop data transmission; delete the tunnel for forwarding multicast service data.
  • the processor 1602 when the indication information indicates to forward multicast service data, the processor 1602 is further configured to:
  • control the transceiver 1601 When the data forwarding timer expires, control the transceiver 1601 to send a ninth message to the target access device and delete the tunnel for forwarding multicast service data; wherein, the ninth message is used to indicate the completion of data forwarding; or
  • control the transceiver 1601 When the data forwarding timer times out, control the transceiver 1601 to send a tenth message to the target access device through the access controller, and delete the tunnel for forwarding multicast service data; wherein, the first Ten messages are used to indicate the completion of data forwarding.
  • the memory 1603 is used to store programs and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1603 may include RAM, or may also include non-volatile memory, such as one or more disk memories.
  • the processor 1602 executes the application program stored in the memory 1603 to implement the above-mentioned functions, thereby implementing the communication method provided in the embodiment of the present application.
  • the embodiment of the present application also provides another access controller for implementing the above communication method.
  • the access controller 1700 may include a transceiver 1701 and a processor 1702.
  • the access controller 1700 may further include a memory 1703.
  • the memory 1703 may be provided inside the access controller 1700, and may also be provided outside the access controller 1700.
  • the processor 1702 controls the transceiver 1701 to receive and send data, and is used to implement the method executed by the access controller (for example, WBAC) in FIGS. 4-10.
  • the processor 1702 may be a CPU, an NP, or a combination of a CPU and NP.
  • the processor 1702 may further include a hardware chip.
  • the above hardware chip may be ASIC, PLD or a combination thereof.
  • the above PLD can be CPLD, FPGA, GAL or any combination thereof.
  • the transceiver 1701, the processor 1702, and the memory 1703 are connected to each other.
  • the transceiver 1701, the processor 1702, and the memory 1703 are connected to each other through a bus 1704;
  • the bus 1704 may be a PCI bus or an EISA bus.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 17, but it does not mean that there is only one bus or one type of bus.
  • the access controller 1700 when the access controller 1700 implements the communication method shown in FIG. 4, it may specifically include:
  • the transceiver 1701 is used to receive and send data
  • the processor 1702 is configured to control the transceiver 1701 to receive a first message from the source access device, the first message is used to request to switch the terminal device to the target access device, and the first message includes the terminal The multicast service context of the device;
  • Control the transceiver 1701 to send a fifth message to the source access device the fifth message is used to respond to a request message for switching the terminal device to the target access device, and the fifth message includes whether to forward multicast Instructions for business data.
  • the fifth message includes indication information of whether to forward multicast service data, including:
  • the fourth message includes the indication information of whether to forward the multicast service data
  • the processor 1702 includes the indication information of whether to forward the multicast service data included in the fourth message in the fifth message.
  • the processor 1702 includes the indication information of whether to forward the multicast service data in the fifth message according to whether the target access device subscribes to the multicast service currently performed by the terminal device.
  • the processor 1702 is further configured to: if it is determined that the target access device has not subscribed to the multicast service currently performed by the terminal device, add the target access device to The current multicast service performed by the terminal device.
  • the processor 1702 is further configured to: when the protocol of the tunnel for transmitting the multicast service data between the access controller and the target access device is GTP-U, the The second message also includes first multicast tunnel establishment information, and the first multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the fourth message when the indication information indicates to forward multicast service data, the fourth message further includes the forwarding tunnel endpoint identifier of the target access device, and the fifth message also includes Includes the forwarding tunnel endpoint identifier of the target access device; or the fourth message also includes the forwarding tunnel endpoint identifier of the target access device, and the fifth message also includes the forwarding of the access controller Tunnel endpoint identifier.
  • the processor 1702 when the indication information indicates to forward multicast service data, the processor 1702 is further configured to: control the transceiver 1701 to receive the eighth message from the target access device, The eighth message is used to request to stop data transmission; control the transceiver 1701 to send the eighth message to the source access device.
  • the processor 1702 when the indication information indicates to forward multicast service data, is further configured to: control the transceiver 1701 to receive the tenth message from the source access device, The tenth message is used to indicate that the data forwarding is completed; the transceiver 1701 is controlled to forward the tenth message to the target access device.
  • the memory 1703 is used to store programs and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1703 may include RAM, or may also include non-volatile memory, such as one or more disk memories.
  • the processor 1702 executes the application program stored in the memory 1703 to realize the above-mentioned functions, thereby realizing the communication method provided by the embodiment of the present application.
  • the embodiment of the present application also provides another target access device for implementing the foregoing communication method.
  • the target access device 1800 may include a transceiver 1801 and a processor 1802.
  • the target access device 1800 may further include a memory 1803.
  • the memory 1803 may be provided inside the target access device 1800, and may also be provided outside the target access device 1800.
  • the processor 1802 controls the transceiver 1801 to receive and send data, and is used to implement the method executed by the target access device (for example, TWBAP) in FIGS. 4-10.
  • the processor 1802 may be a CPU, NP, or a combination of CPU and NP.
  • the processor 1802 may further include a hardware chip.
  • the above hardware chip may be ASIC, PLD or a combination thereof.
  • the above PLD can be CPLD, FPGA, GAL or any combination thereof.
  • the transceiver 1801, the processor 1802, and the memory 1803 are connected to each other.
  • the transceiver 1801, the processor 1802, and the memory 1803 are connected to each other through a bus 1804; the bus 1804 may be a PCI bus or an EISA bus.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in FIG. 18 to represent, but it does not mean that there is only one bus or one type of bus.
  • the target access device when the target access device implements the communication method shown in FIG. 4, it may specifically include:
  • the transceiver 1801 is used to receive and send data
  • the processor 1802 is configured to control the transceiver 1801 to receive a second message from the access controller, where the second message includes the multicast service context of the terminal device;
  • the fourth message includes information indicating whether to forward the multicast service data.
  • the second message further includes first multicast tunnel establishment information, and the first multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the fourth message further includes second multicast tunnel establishment information, and the second multicast tunnel establishment information is used to establish a tunnel for transmitting multicast service data.
  • the fourth message further includes the forwarding tunnel endpoint identifier of the target access device.
  • the processor 1802 is further configured to:
  • the transceiver 1801 When it is determined according to the multicast service context of the terminal device that it is not subscribed to the multicast service currently performed by the terminal device, the transceiver 1801 is controlled to send a third message to the multicast source device, where the third message is used for Subscribe to the multicast service currently performed by the terminal device.
  • the processor 1802 is further configured to: when controlling the transceiver 1801 to receive multicast service data from the source access device, start a data forwarding timer;
  • the tunnel deletion timer expires, the tunnel for forwarding multicast service data is deleted.
  • processor 1802 is further configured to:
  • processor 1802 is further configured to:
  • the data forwarding timer is started; when the data forwarding timer expires, the tunnel for forwarding the multicast service data is deleted.
  • the memory 1803 is used to store programs and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1803 may include RAM, or may also include non-volatile memory, such as one or more disk memories.
  • the processor 1802 executes the application program stored in the memory 1803 to implement the foregoing functions, thereby implementing the communication method provided in the embodiment of the present application.
  • the embodiments of the present application also provide a computer storage medium, the storage medium stores a software program, and when the software program is read and executed by one or more processors, any one or more of the above The method provided by the embodiment.
  • the computer storage medium may include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.
  • the embodiments of the present application also provide a chip.
  • the chip includes a processor for implementing the functions involved in any one or more of the above embodiments, such as acquiring or processing the information involved in the above method or news.
  • the chip further includes a memory, and the memory is used for necessary program instructions and data executed by the processor.
  • the chip can be composed of a chip, or it can include a chip and other discrete devices.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

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

Abstract

一种通信方法及装置，用以实现在组播业务场景中终端设备灵活地进行切换流程。该方法包括：源接入设备向接入控制器发送第一消息，所述第一消息用于请求将终端设备切换到目标接入设备，所述第一消息中包括终端设备的组播业务上下文；所述接入控制器向目标接入设备发送第二消息，所述第二消息中包括终端设备的组播业务上下文；所述接入控制器从所述目标接入设备接收第四消息，所述第四消息用于响应将终端设备切换到目标接入设备的请求消息；所述接入控制器向所述源接入设备发送第五消息，所述第五消息用于响应将终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。

Description

一种通信方法及装置
本申请要求在2019年01月31日提交中国专利局、申请号为201910097448.2、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在现有的4G通信系统中，终端设备在两个基站之间进行切换的过程中，通常会涉及到相应的移动管理实体(mobility management entity，MME)和服务网关(serving gateway S-GW)的切换，从而实现由源侧设备到目标侧设备的切换。
目前，在上述切换过程中，存在一个固定的锚点，例如分组数据网网关(packet data network gateway，P-GW)，利用所述固定的锚点对终端设备的业务数据进行转发，以保证终端设备业务连续性。
但是实际中，组播业务场景下，固定锚点是非必需的，但是由于现有通信系统的限制还必须部署固定锚点，使固定锚点参与终端设备的切换，这样明显终端设备切换不灵活，并且造成资源浪费。
发明内容
本申请提供一种通信方法及装置，用以实现在组播业务场景中终端设备灵活地进行切换流程。
第一方面，本申请提供了一种通信方法，应用于组播业务场景，该方法包括：源接入设备向接入控制器发送第一消息，从所述接入控制器接收第五消息，其中，所述第一消息用于请求将终端设备切换到目标接入设备，所述第一消息中包括终端设备的组播业务上下文；所述第五消息用于响应为终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
通过上述方法，终端设备在接入设备之间切换的过程中，可以灵活地进行切换流程，无需固定锚点参与终端设备的切换就可以保证组播业务的连续性，这样可以避免因部署固定锚点造成的资源浪费。
在一个可能的设计中，所述源接入设备根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务。这样可以后续通知将所述目标接入设备加入所述终端设备当前进行的组播业务。
在一个可能的设计中，所述目标接入设备未订阅所述终端设备当前进行的组播业务时，所述源接入设备通知所述终端设备通过目标接入设备订阅所述终端设备当前进行的组播业务。这样可以实现所述目标接入设备对组播业务的订阅。
在一个可能的设计中，所述源接入设备根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务，具体可以包括以下三种情况：
当所述第五消息中还包括所述目标接入设备当前订阅或承载的组播业务的标识时，所述源接入设备根据所述目标接入设备订当前阅或承载的组播业务的标识确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务；或者
当所述第五消息中还包括所述目标接入设备未订阅所述终端设备当前进行的组播业务的信息，所述源接入设备根据所述信息确定所述目标接入设备未订阅所述终端设备当前进行的组播业务；或者
当所述第五消息中包含的所述是否转发组播业务数据的指示信息指示转发组播业务数据时，所述源接入设备确定所述目标接入设备未订阅所述终端设备当前进行的组播业务。
通过上述方法，所述源接入设备可以准确地确定所述目标接入设备未订阅所述终端设备当前进行的组播业务。
在一个可能的设计中，当所述指示信息指示转发组播业务数据时，所述方法还包括：所述第五消息中还包括目标接入设备的转发隧道端点标识，所述源接入设备根据所述目标接入设备转发隧道端点标识建立转发组播业务数据的隧道；或者，所述第五消息中还包括所述接入控制器的转发隧道端点标识，所述源接入设备根据所述接入控制器的转发隧道端点标识建立转发组播业务数据的隧道。
通过上述方法，所述源接入设备可以根据实际情况实现后续组播业务数据的转发。
在一个可能的设计中，当所述指示信息指示转发组播业务数据时，所述源接入设备从所述接入控制器接收第八消息，并删除转发组播业务数据的隧道，所述第八消息用于请求停止数据传输。这样，所述源接入设备可以停止向目标接入设备传输组播业务数据。
在一个可能的设计中，当所述指示信息指示转发组播业务数据时，所述源接入设备首次向目标接入设备发送组播业务数据时，启动数据转发定时器；当所述数据转发定时器超时时，所述源接入设备向目标接入设备发送第九消息，并删除转发组播业务数据的隧道；其中，所述第九消息用于指示数据转发完成；或者，当所述数据转发定时器超时时，所述源接入设备通过所述接入控制器向所述目标接入设备发送第十消息，并删除转发组播业务数据的隧道；其中，所述第十消息用于指示数据转发完成。
通过上述方法，可以实现所述源接入设备和目标接入设备之间的组播业务数据的停止转发。
第二方面，本申请提供了一种通信方法，应用于组播业务场景，该方法包括：接入控制器从源接入设备接收第一消息，向目标接入设备发送第二消息，从所述目标接入设备接收第四消息后，向所述源接入设备发送第五消息；其中，所述第一消息用于请求将终端设备切换接入设备，所述第一消息中包括终端设备的组播业务上下文；所述第二消息用于请求将所述终端设备切换到目标接入设备，所述第二消息中包括终端设备的组播业务上下文；所述第四消息用于响应将终端设备切换到目标接入设备的请求消息；所述第五消息用于响应将终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
通过上述方法，终端设备在接入设备之间切换的过程中，可以灵活地进行切换流程，无需固定锚点参与终端设备的切换就可以保证组播业务的连续性，这样可以避免因部署固定锚点造成的资源浪费。
在一个可能的设计中，所述第五消息中包含是否转发组播业务数据的指示信息，具体可以包括：所述第四消息中包含所述是否转发组播业务数据的指示信息，所述接入控制器 将所述第四消息中包含的所述是否转发组播业务数据的指示信息包含在所述第五消息中；或者，所述接入控制器根据所述目标接入设备是否订阅所述终端设备当前进行的组播业务，在所述第五消息中包含所述是否转发组播业务数据的指示信息。
通过上述方法，所述接入控制器可以灵活实现在所述第五消息中包含是否转发组播业务数据的指示信息，以使后续源接入设备根据所述指示信息执行相应流程操作。
在一个可能的设计中，若所述目标接入设备未订阅所述终端设备当前进行的组播业务时，所述接入控制器则将所述目标接入设备加入所述终端设备当前进行的组播业务。
通过上述方法，可以实现将未订阅所述终端设备当前进行的组播业务的目标接入设备加入相应的组播业务，以实现业务连续。
在一个可能的设计中，所述接入控制器确定所述接入控制器与所述目标接入设备传输组播业务数据的隧道的协议为GTP-U时，所述第二消息中还包括第一组播隧道建立信息，所述第一组播隧道建立信息用于建立传输组播业务数据的隧道。
通过上述方法，实现后续所述接入控制器和所述目标接入设备之间传输组播业务数据的隧道的建立。
在一个可能的设计中，当所述指示信息指示转发组播业务数据时，所述第四消息中还包括所述目标接入设备的转发隧道端点标识，所述第五消息中还包括所述目标接入设备的转发隧道端点标识；或者所述第四消息中还包括所述目标接入设备的转发隧道端点标识，所述第五消息中还包括所述接入控制器的转发隧道端点标识。
通过上述方法，可以使所述源接入设备可以根据实际情况实现后续组播业务数据的转发。
在一个可能的设计中，当所述指示信息指示转发组播业务数据时，所述接入控制器从所述目标接入设备接收第八消息，所述第八消息用于请求停止数据传输；所述接入控制器向所述源接入设备发送所述第八消息。
通过上述方法，所述源接入设备可以停止向目标接入设备传输组播业务数据。
在一个可能的设计中，当所述指示信息指示转发组播业务数据时，所述接入控制器从所述源接入设备接收第十消息，所述第十消息用于指示数据转发完成；所述接入控制器向所述目标接入设备转发所述第十消息。
通过上述方法，可以使所述源接入设备和所述目标接入设备之间的组播业务数据的转发停止。
第三方面，本申请提供了一种通信方法，应用于组播业务场景，该方法包括：目标接入设备从接入控制器接收第二消息，并向所述接入控制器发送第四消息；其中，所述第二消息用于请求将所述终端设备切换到目标接入设备，所述第二消息中包括终端设备的组播业务上下文；所述第四消息用于响应将终端设备切换到目标接入设备的请求消息。
通过上述方法，终端设备在接入设备之间切换的过程中，可以灵活地进行切换流程，无需固定锚点参与终端设备的切换就可以保证组播业务的连续性，这样可以避免因部署固定锚点造成的资源浪费。
在一个可能的设计中，所述第四消息中包含是否转发组播业务数据的指示信息。这样可以在后续过程中使源接入设备根据所述指示信息判断是否需要转发组播业务数据。
在一个可能的设计中，所述第二消息中还包括第一组播隧道建立信息，所述第一组播隧道建立信息用于建立传输组播业务数据的隧道。这样可以实现所述接入控制器和所述目 标接入设备之间传输组播业务数据的隧道的建立。
在一个可能的设计中，所述第四消息中还包括第二组播隧道建立信息，所述第二组播隧道建立信息用于建立传输组播业务数据的隧道。这样可以实现所述接入控制器和所述目标接入设备之间传输组播业务数据的隧道的建立。
在一个可能的设计中，所述第四消息中还包括所述目标接入设备的转发隧道端点标识。这样可以在后续过程中接入控制器根据实际情况将所述目标接入设备的转发隧道端点标识转发给源接入设备或者所述接入控制器根据所述目标接入设备的转发隧道端点标识建立转发组播业务数据的隧道，以实现后续源接入设备转发组播业务数据。
在一个可能的设计中，在所述目标接入设备从所述接入控制器接收到所述第二消息之后，当所述目标接入设备根据所述终端设备的组播业务上下文确定自身未订阅所述终端设备当前进行的组播业务时，所述目标接入设备向组播源设备发送第三消息，所述第三消息用于订阅所述终端设备当前进行的组播业务。
通过上述方法，可以实现将未订阅所述终端设备当前进行的组播业务的目标接入设备加入相应的组播业务，以实现业务连续。
在一个可能的设计中，所述目标接入设备在接收到来自源接入设备的组播业务数据时，启动数据转发定时器；当所述数据转发定时器超时时，所述目标接入设备启动隧道删除定时器，并向所述接入控制器发送第八消息，所述第八消息用于请求停止数据传输；当所述隧道删除定时器超时时，所述目标接入设备删除转发组播业务数据的隧道。
通过上述方法，可以停止所述源接入设备和所述目标接入设备之间的组播业务数据的转发。
在一个可能的设计中，所述目标接入设备从源接入设备接收第九消息后，删除转发组播业务数据的隧道，其中，所述第九消息用于指示数据转发完成；或者，所述目标接入设备从所述接入控制器接收到来自所述源接入设备的第十消息后，删除转发组播业务数据的隧道，其中，所述第十消息用于指示数据转发完成。
通过上述方法，可以停止所述源接入设备和所述目标接入设备之间的组播业务数据的转发。
在一个可能的设计中，所述目标接入设备在接收到来自源接入设备的组播业务数据时，启动数据转发定时器；当所述数据转发定时器超时时，所述目标接入设备删除转发组播业务数据的隧道。
通过上述方法，可以停止所述源接入设备和所述目标接入设备之间的组播业务数据的转发。
第四方面，本申请提供了一种通信方法，应用于组播业务场景，该方法包括：终端设备从源接入设备接收第六消息，所述第六消息中包括订阅所述终端设备当前进行的组播业务的通知信息；所述终端设备向目标接入设备发送第七消息，所述第七消息用于指示所述目标接入设备未订阅所述终端设备当前进行的组播业务，或者向所述目标接入设备请求订阅所述终端设备当前进行的组播业务；所述目标接入设备向组播源设备发送第十九消息，所述第十九消息用于指示所述组播源设备将所述目标接入设备加入所述终端设备当前进行的组播业务。
通过上述方法，可以将未订阅所述终端设备当前进行的组播业务的目标接入设备加入相应的组播业务，以实现业务连续。
第五方面，本申请提供了一种组播业务信息配置方法，该方法包括：接入设备向接入控制器发送第十三消息，所述第十三消息中包括所述接入设备支持的传输组播业务数据的隧道的协议；所述接入设备从所述接入控制器接收第十四消息，所述第十四消息用于响应第十三消息，所述第十四消息中包括所述接入控制器支持的传输组播业务数据的隧道的协议。
通过上述方法，可以实现接入设备和接入控制器之间用来传输组播业务数据的隧道的协议的协商，以使后续可以建立传输组播业务数据的隧道。
在一个可能的设计中，当所述接入设备支持的传输组播业务数据的隧道的协议为GTP-U时，所述第十三消息中还包括所述接入设备的隧道端点标识。这样可以实现所述接入设备和所述接入控制器之间的传输组播业务数据的隧道。
在一个可能的设计中，当所述接入控制器支持的传输组播业务数据的隧道的协议为GTP-U时，所述第十四消息中还包括所述接入控制器的隧道端点标识。这样可以实现所述接入设备和所述接入控制器之间的传输组播业务数据的隧道。
第六方面，本申请提供了一种组播业务建立方法，该方法包括：接入设备从终端设备接收第十五消息，所述第十五消息用于请求建立一个组播业务，所述第十五消息中包括所述组播业务的地址和所述终端设备的标识；所述接入设备向接入控制器发送第十六消息，所述第十六消息用于请求建立所述组播业务，所述第十六消息中包括所述终端设备的标识和所述组播业务的地址；所述接入设备从所述接入控制器接收第十七消息，所述第十七消息用于指示允许所述终端设备建立所述组播业务，所述第十七消息中包括所述终端设备的标识和所述组播业务的地址。
通过上述方法，可以实现组播业务的建立，以使后续终端设备进行需要的组播业务。
在一个可能的设计中，所述第十六消息中还包括第一组播隧道建立信息，所述第一组播建立隧道信息用于建立传输组播业务数据的隧道。这样可以在后续过程中实现所述接入设备和所述接入控制器之间的传输组播业务数据的隧道的建立。
在一个可能的设计中，所述第十七消息中还包括第二组播隧道建立信息，所述第二组播建立隧道信息用于建立传输组播业务数据的隧道。这样可以在后续过程中实现所述接入设备和所述接入控制器之间的传输组播业务数据的隧道的建立。
在一个可能的设计中，当所述接入设备确定自身未订阅所述组播业务，所述接入设备向所述接入控制器或者组播源发送第十八消息，所述第十八消息用于订阅所述组播业务。
通过上述方法，可以将未订阅所述终端设备当前进行的组播业务的目标接入设备加入相应的组播业务，以实现业务连续。
第七方面，本申请提供了一种组播业务建立方法，该方法包括：接入控制器从接入设备接收第十六消息，所述第十六消息用于请求建立一个组播业务，所述第十六消息中包括所述终端设备的标识和所述组播业务的地址；所述接入控制器向所述接入设备发送第十七消息，所述第十七消息用于指示允许所述终端设备建立所述组播业务，所述第十七消息中包括所述终端设备的标识和所述组播业务的地址。
通过上述方法，可以实现组播业务的建立，以使后续终端设备进行需要的组播业务。
在一个可能的设计中，所述第十六消息中还包括第一组播隧道建立信息，所述第一组播建立隧道信息用于建立传输组播业务数据的隧道。这样可以在后续过程中实现所述接入设备和所述接入控制器之间的传输组播业务数据的隧道的建立。
在一个可能的设计中，所述第十七消息中还包括第二组播隧道建立信息，所述第二组播建立隧道信息用于建立传输组播业务数据的隧道。这样可以在后续过程中实现所述接入设备和所述接入控制器之间的传输组播业务数据的隧道的建立。
在一个可能的设计中，所述接入控制器从所述接入设备接收第十八消息，所述第十八消息用于订阅所述组播业务；所述接入控制器将所述接入设备加入所述组播业务。
通过上述方法，可以将未订阅所述终端设备当前进行的组播业务的目标接入设备加入相应的组播业务，以实现业务连续。
第八方面，本申请还提供了一种源接入设备，该源接入设备具有实现上述第一方面方法实例中源接入设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述源接入设备的结构中包括发送单元、接收单元和处理单元，这些单元可以执行上述第一方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述源接入设备的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述源接入设备执行上述第一方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述源接入设备必要的程序指令和数据。
第九方面，本申请还提供了一种接入控制器，该接入控制器具有实现上述第二方面方法实例中接入控制器行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述接入控制器的结构中包括接收单元、发送单元和处理单元，这些单元可以执行上述第二方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述接入控制器的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述接入控制器执行上述第二方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述接入控制器必要的程序指令和数据。
第十方面，本申请还提供了一种目标接入设备，该目标接入设备具有实现上述第三方面方法实例中目标接入设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述目标接入设备的结构中包括接收单元、发送单元和处理单元，这些单元可以执行上述第三方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述目标接入设备的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述目标接入设备执行上述第三方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述目标接入设备必要的程序指令和数据。
第十一方面，本申请还提供了一种终端设备，该终端设备具有实现上述第四方面方法实例中终端设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述终端设备的结构中包括接收单元、发送单元和处理单元，这些单元可以执行上述第四方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述终端设备的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述终端设备执行上述第四方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述终端设备必要的程序指令和数据。
第十二方面，本申请还提供了一种接入设备，该接入设备具有实现上述第五方面方法实例中接入设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述接入设备的结构中包括接收单元、发送单元和处理单元，这些单元可以执行上述第五方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述接入设备的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述接入设备执行上述第五方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述接入设备必要的程序指令和数据。
第十三方面，本申请还提供了一种接入控制器，该接入控制器具有实现上述第五方面方法实例中接入控制器行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述接入控制器的结构中包括接收单元、发送单元和处理单元，这些单元可以执行上述第五方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述接入控制器的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述接入控制器执行上述第五方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述接入控制器必要的程序指令和数据。
第十四方面，本申请还提供了一种接入设备，该接入设备具有实现上述第六方面方法实例中接入设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述接入设备的结构中包括接收单元、发送单元和处理单元，这些单元可以执行上述第六方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述接入设备的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述接入设备执行上述第五方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述接入设备必要的程序指令和数据。
第十五方面，本申请还提供了一种接入控制器，该接入控制器具有实现上述第七方面方法实例中接入控制器行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述接入控制器的结构中包括接收单元、发送单元和处理单元，这些单元可以执行上述第七方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述接入控制器的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述接入控制器执行上述第七方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述接入控制器必要的程序指令和数据。
第十六方面，本申请还提供了一种系统，该系统包括源接入设备，所述源接入设备可用于执行上述第一方面及第一方面的任一方法中由源接入设备执行的步骤。在一个可能的设计中，所述系统还可以包括接入控制器，所述接入控制器可用于执行上述第一方面及第一方面的任一方法中由接入控制器执行的步骤。在一个可能的设计中，所述系统还可以包括目标接入设备，所述目标接入设备可用于执行上述第一方面及第一方面的任一方法中目标接入设备执行的步骤。在一个可能的设计中，该系统还可以包括本申请实施例提供的方案中与源接入设备、接入控制器、目标接入设备中一个或多个进行交互的其他设备，例如终端设备等等。
第十七方面，本申请还提供了一种系统，该系统包括接入控制器，所述接入控制器可用于执行上述第二方面及第二方面的任一方法中由接入控制器执行的步骤。在一个可能的设计中，所述系统还可以包括源接入设备，所述源接入设备可用于执行上述第二方面及第二方面的任一方法中由源接入设备执行的步骤。在一个可能的设计中，所述系统还可以包括目标接入设备，所述目标接入设备可用于执行上述第二方面及第二方面的任一方法中目标接入设备执行的步骤。在一个可能的设计中，该系统还可以包括本申请实施例提供的方案中与源接入设备、接入控制器、目标接入设备中一个或多个进行交互的其他设备，例如终端设备等等。
第十八方面，本申请还提供了一种系统，该系统包括目标接入设备，所述目标接入设备可用于执行上述第三方面及第三方面的任一方法中由目标接入设备执行的步骤。在一个可能的设计中，所述系统还可以包括源接入设备，所述源接入设备可用于执行上述第三方面及第三方面的任一方法中由源接入设备执行的步骤。在一个可能的设计中，所述系统还可以包括接入控制器，所述接入控制器可用于执行上述第三方面及第三方面的任一方法中接入控制器执行的步骤。在一个可能的设计中，该系统还可以包括本申请实施例提供的方案中与源接入设备、接入控制器、目标接入设备中一个或多个进行交互的其他设备，例如终端设备等等。
第十九方面，本申请还提供了一种系统，该系统包括终端设备，所述终端设备可用于执行上述第四方面及第四方面的任一方法中由终端设备执行的步骤。在一个可能的设计中，所述系统还可以包括目标接入设备，所述目标接入设备可用于执行上述第四方面及第四方面的任一方法中由目标接入设备执行的步骤。在一个可能的设计中，该系统还可以包括本申请实施例提供的方案中与终端设备和/或目标接入设备中一个或多个进行交互的其他设备。
第二十方面，本申请还提供了一种系统，该系统包括接入设备，所述接入设备可用于执行上述第五方面及第五方面的任一方法中，或第六方面及第六方面的任一方法中由接入设备执行的步骤。在一个可能的设计中，所述系统还可以包括接入控制器，所述接入控制 器可用于执行上述第五方面及第五方面的任一方法中，或第六方面及第六方面的任一方法中接入控制器执行的步骤。在一个可能的设计中，该系统还可以包括本申请实施例提供的方案中与接入控制器和/或接入设备中一个或多个进行交互的其他设备，例如终端设备等等。
第二十一方面，本申请还提供了一种系统，该系统包括接入控制器，所述接入控制器可用于执行上述第五方面及第五方面的任一方法中，或第七方面及第七方面的任一方法中由接入控制器执行的步骤。在一个可能的设计中，所述系统还可以包括接入设备，所述接入设备可用于执行上述第五方面及第五方面的任一方法中，或第七方面及第七方面的任一方法中由接入设备执行的步骤。在一个可能的设计中，该系统还可以包括本申请实施例提供的方案中与接入控制器和/或接入设备中一个或多个进行交互的其他设备，例如终端设备等等。
第二十二方面，本申请还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述提及的任一种方法。
第二十三方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述提及的任一种方法。
第二十四方面，本申请还提供了一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现上述提及的任一种方法。
附图说明
图1为本申请提供的一种通信系统的架构示意图；
图2为本申请提供的一种组播结构的示意图；
图3为本申请提供的另一种组播架构的示意图；
图4为本申请提供的一种通信方法的流程图；
图5为本申请提供的一种通信方法的示例的流程图；
图6为本申请提供的另一种通信方法的示例的流程图；
图7为本申请提供的另一种通信方法的示例的流程图；
图8为本申请提供的另一种通信方法的示例的流程图；
图9为本申请提供的另一种通信方法的示例的流程图；
图10为本申请提供的另一种通信方法的示例的流程图；
图11为本申请提供的一种组播业务信息配置方法的流程图；
图12为本申请提供的一种组播业务建立方法的流程图；
图13为本申请提供的一种装置的结构示意图；
图14为本申请提供的另一种装置的结构示意图；
图15为本申请提供的另一种装置的结构示意图；
图16为本申请提供的一种源接入设备的结构图；
图17为本申请提供的一种接入控制器的结构图；
图18为本申请提供的一种目标接入设备的结构图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种通信方法及装置，用以实现在组播业务场景中终端设备灵活地进行切换流程。其中，本申请所述方法和装置基于同一发明构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
以下，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
1)、源接入设备、目标接入设备，可以提供终端设备的接入管理功能，鉴权认证功能，移动性管理功能，会话管理功能等等；所述源接入设备、所述目标接入设备可以作为本地转发的数据连接的出口网关与外部公用数据网(public data network，PDN)网络联系，还可以作为终端设备移动时候数据连接的锚点。在本申请实施例中，所述源接入设备和所述目标接入设备可以点不限于是无线宽带接入点(wireless broadband access point，WBAP)，支持与终端设备之间的WB-Uu接口，支持与接入控制器之间的WB-1接口；可以终结空口信令以及非接入层(non-access stratum，NAS)消息。
2)、接入控制器，可以提供用户签约存储及管理功能，移动性管理功能，策略控制功能，接入设备配置管理功能等等；所述接入控制器可以作为集中转发的数据连接的出口网关与外部PDN网络联系，并作为终端设备移动时候数据连接的锚点。在本申请中所述接入控制器可以但不限于为无线宽带接入控制器(wireless broadband access controller，WBAC)，可以支持与接入设备(例如WBAP)之间的WB-1接口。
3)、在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的通信方法及装置进行详细说明。
图1示出了本申请实施例提供的通信方法适用的一种可能的通信系统的架构，所述通信系统的架构中可以包括接入控制器，至少一个接入设备和至少一个终端设备。其中，所述接入控制器与所述至少一个接入设备之间可以通过WB-1接口相连，接入设备与所述终端设备之间可以通过WB-Uu接口相连。接口名称只是一个示例说明，本申请实施例对此不作具体限定。应理解，本申请实施例并不限于图1所示通信系统，图1中所示的设备的名称在这里仅作为一种示例说明，并不作为对本申请的通信方法适用的通信系统架构中包括的设备的限定。下面对所述通信系统中的各个网元或设备的功能进行详细描述：
所述终端设备，是一种向用户提供语音和/或数据连通性的设备。所述终端设备可以支持3GPP定义的NAS消息。例如，在5G中，所述终端设备可以是无线宽带用户驻地设备(wireless broadband customer-premises equipment，WBCPE)。在未来通信，如6G中，所述终端设备仍可以是WBCPE，或有其它的名称，本申请不做限定。
所述接入设备，可以为所述终端设备提供接入管理功能，鉴权认证功能，移动性管理功能，会话管理功能等等。所述接入设备可以作为本地转发的数据连接的出口网关与外部PDN网络联系，还可以作为所述终端设备移动时候数据连接的锚点。所述接入设备可以终结空口信令以及NAS消息。例如，在5G中，所述接入设备可以是WBAP。在未来通信，如6G中，所述接入设备仍可以是WBAP，或有其它的名称，本申请不做限定。
所述接入控制器，可以提供用户签约存储及管理功能，移动性管理功能，策略控制功能，接入设备配置管理功能等等。所述接入控制器可以作为集中转发的数据连接的出口网 关与外部PDN网络联系，并作为所述终端设备移动时候数据连接的锚点。例如，在5G中，所述接入控制器可以是WBAC，在未来通信，如6G中，所述接入控制器仍可以是WBAC，或有其它的名称，本申请不做限定。
需要说明的是，图1所示的通信系统的架构中不限于仅包含图中所示的设备，还可以包含其它未在图中表示的设备，具体本申请在此处不再一一列举。
需要说明的是，本申请实施例并不限定各个设备的分布形式，图1所示的分布形式只是示例性的，本申请不作限定。
需要说明的是，图1所示的通信系统并不构成本申请实施例能够适用的通信系统的限定。图1所示的通信系统架构为5G系统架构，可选的，本申请实施例的方法还适用于未来的各种通信系统，例如6G或者其他通信网络等。
基于图1所示的通信系统，本申请实施例提供了两种组播架构，分别如图2和图3所示，其中在图2和图3中分别以接入设备为WBAP为例，以接入控制器为WBAC为例，以终端设备为WBCPE为例进行说明。具体的，图2所示的组播架构中，WBAC和WBAP之间建立了组播通道，WBAC集中转发组播业务数据到WBAP，然后WBAP再将组播业务数据转发到相应的WBCPE。图3所示的组播架构中，通过外部组播源设备发送组播业务数据到WBAP，然后WBAP再将组播业务数据转发到相应的WBCPE。其中，需要说明的是，在图2所示的组播架构中，所述WBAC可以看作是组播源设备，具有组播源设备转发组播业务数据的功能。需要说明的是，本申请涉及的组播业务数据也可以称为组播业务数据包。
本申请实施例提供的一种通信方法，适用于如图1所示的通信系统，以及适用于图2或者图3所示的组播架构。参阅图4所示，该方法的具体流程可以包括：
步骤401：源接入设备向接入控制器发送第一消息，所述第一消息用于请求将终端设备切换到目标接入设备，所述第一消息中包括终端设备的组播业务上下文。
其中，所述第一消息可以为所述源接入设备向所述接入控制器发送的重定位请求(Relocation Request)(也即切换请求)。
在一种可选的实施方式中，所述终端设备的组播业务上下文可以但不限于包括所述终端设备请求加入的组播组标识，组播地址(也即组播报文需要转发的目的地址)，组播源地址等等信息。
在一种可选的实施方式中，所述接入控制器接收到所述第一消息之后，可以根据所述第一消息中的所述终端设备的组播业务上下文判断所述目标接入设备是否订阅了所述终端设备当前进行的组播业务，当确定所述目标接入设备未订阅所述终端设备当前进行的组播业务时，将所述目标接入设备加入所述终端设备当前进行的组播业务。例如，所述接入控制器可以根据所述第一消息中包括的所述终端设备请求加入的组播组标识确定所述终端设备进行的组播业务，然后根据本地保存的关于所述目标接入设备的相关信息得到所述目标接入设备已订阅组播业务情况，基于此判断所述目标接入设备是否订阅了所述终端设备当前进行的组播业务。
具体的：所述第一消息中还可以携带第一信息，第一信息可以包括如下信息中的一个或多个：所述终端设备在所述源接入设备所建立连接的连接上下文信息、所述终端设备的移动性管理上下文、所述源接入设备到所述目标接入设备的容器(Source WBAP to Target WBAP container)，Source WBAP to Target WBAP container可以包括一个或多个第一参数， 该第一参数可以为终端设备进行切换时所需要的参数。所述第一消息中还可以携带目接入设备的标识。当然，所述第一消息中也可以携带其他信息，本申请实施例在这里不再一一列举。本申请实施例中所涉及的连接上下文信息可以包括如下信息中的一个或多个：PDN上下文信息、PDU上下文信息、承载上下文信息。
本申请实施例中所涉及的消息的具体协议类型可以为无线接入点的控制和配置(control and provisioning of wireless access points，CAPWAP)，也可以为简单网络管理协议(simple network management protocol，SNMP)，也可以为其他协议，本申请实施例在这里消息的协议类型不做具体限定。为了方便描述，本申请实施例中以CAPWAP协议为例对消息进行描述。
以CAPWAP协议为例时，本申请实施例中所涉及的消息可以有两种格式。一种格式为CAPWAP Message(Vendor Specific(List of 3GPP specific message container))，其中，List of 3GPP specific message container可以为目标节点标识(Target Node ID)+消息体(message container)，其中，Target Node ID表示message container中的信息的目的接收端。Target Node ID也可以是可选信元，例如，如果消息中不包括Target Node ID，则表示是相应message container中携带的信息的接收端为预设的目标节点，如WBAC等。message container中携带具体的信息。
另一种格式为CAPWAP Message(Vendor Specific(Forward container，Direct container))，其中，Forward container表示接入控制器不需要解析而可以直接转发的消息，其中格式同List of 3GPP specific message container。Direct container表示接入控制器需要解析的消息，其中格式可以同List of 3GPP specific message container，也可以同message container。
一种实现方式中，第一消息可以为CAPWAP协议中的无线终结点(wireless termination points，WTP)事件请求(Event Request)消息。第一消息的格式可以为WTP Event Request(V[Target WBAP ID，Relocation Request])，Target WBAP ID可以为接入控制器的标识，Relocation Request用于通知接收端终端设备准备切换到所述目标接入设备，Relocation Request可以携带第一信息。
另一种实现方式中，第一消息可以为Relocation Request。因此，源接入设备可以通过WTP Event Request(V[Target WBAP ID，Relocation Request])向接入控制器发送第一消息。
在一种可能的实施方式中，源接入设备可以根据第二信息确定目标接入设备。其中，第二信息可以包括如下信息中的一个或多个：终端设备向源接入设备发送的测量报告、多个接入设备的负载信息、终端设备的移动性管理上下文。源接入设备可以从接入控制器获取所述多个接入设备的负载信息。具体的，源接入设备可以周期性向接入控制器查询多个接入设备的负载信息，或者，接入控制器也可以周期性向源接入设备推送多个接入设备的负载信息。多个接入设备可以为通信系统中任意多个接入设备，也可以为源接入设备的多个邻接入设备，也可以为通信系统中的所有接入设备。
当然，源接入设备也可以根据其他信息确定目标接入设备，本申请实施例在这里不做具体限定。
步骤402：所述接入控制器向目标接入设备发送第二消息，所述第二消息中包括所述终端设备的组播业务上下文。
其中，所述第二消息可以用于请求将所述终端设备切换到目标接入设备，所述第二消息可以为所述接入控制器向所述目标接入设备发送的Relocation Request。
在一种可选的实施方式中，所述接入控制器可以根据实际情况决定是否需要在所述第二消息中携带第一组播隧道建立信息，其中所述第一组播隧道建立信息用于建立传输组播业务数据的隧道。具体的，该隧道是建立在所述目标接入设备和所述接入控制器之间的隧道，主要用于所述接入控制器向所述目标接入设备传输组播业务的相关数据。可选的，建立的所述隧道可以是无线接入点的控制和配置(control and provisioning of wireless access points，CAPWAP)数据(DATA)通道信息，也可以是其他的协议，如GTP-U隧道端点信息等等，本申请具体不作限定。具体的，所述接入控制器可以根据以下情况判断是否需要携带所述第一组播隧道建立信息：
在一种具体的示例中，所述接入控制器在确定所述接入控制器与所述目标接入设备传输组播业务数据的隧道的协议为GTP-U时，所述接入控制器在所述第二消息中携带所述第一组播隧道建立信息，此时，可选的，所述第一组播隧道建立信息可以为所述接入控制器为组播业务分配的GTP-U隧道端点信息。在这种情况下，所述接入控制器已经确定所述目标接入设备未订阅所述终端设备当前进行的组播业务。
在另一种具体的示例中，所述接入控制器确定所述接入控制器和所述目标接入设备之间可以使用CAPWAP DATA通道或者其他预先建立好的通道来传递多播业务数据时，所述接入控制器就不需要在所述第二消息中携带所述第一组播隧道建立信息。
在一种可选的实施方式中，在所述目标接入设备从所述接入控制器接收到所述第二消息之后，当所述目标接入设备根据所述终端设备的组播业务上下文确定自身未订阅所述终端设备当前进行的组播业务时，所述目标接入设备向组播源设备发送第三消息，所述第三消息用于订阅所述终端设备当前进行的组播业务。其中，示例性的所述第三消息可以是所述目标接入设备向所述组播源设备发送的因特网组管理协议(Internet group management protocol，IGMP)加入(Join)消息。在一种可选的实施方式中，所述组播源设备可以但不限于是路由器(router)。需要说明的是，本申请涉及的组播源设备均可以是router，本申请对此不作限定。
所述第二消息还可以携带第一信息。接入控制器可以根据第一消息中携带的目标接入设备的标识将第一信息通过第二消息发送到目标接入设备。当然，第二消息中也可以携带其他信息，本申请实施例在这里不再一一列举。
一种实现方式中，第二消息可以为CAPWAP协议中的站配置请求(Station Configuration Request)消息。第二消息的格式可以为Station Configuration Request(V[Target WBAP ID，Relocation Request])，Target WBAP ID可以为目标接入设备的标识。
另一种实现方式中，第二消息可以为Relocation Request。因此，接入控制器可以通过Station Configuration Request(V[Target WBAP ID，Relocation Request])向目标接入设备发送第二消息。
步骤403：所述目标接入设备向所述接入控制器发送第四消息，所述第四消息用于响应将所述终端设备切换到目标接入设备的请求消息。
其中，所述第四消息可以是所述目标接入设备向所述接入控制器发送的重定位响应(Relocation Response)(也即切换响应)。
在一种可选的实施方式中，所述第四消息中可以包括是否转发组播业务数据的指示信息。其中具体的，当所述目标接入设备确定自身已经订阅过所述终端设备当前进行的组播业务时，所述第四消息中可以包含订阅了组播组(multicast group subscribed)指示，表示 不需要转发组播业务数据。
在一种可选的实施方式中，所述第四消息中还可以包括所述目标接入设备的转发隧道端点标识，以使所述接入控制器将所述目标接入设备的转发隧道端点标识转发给所述源接入设备后，所述源接入设备可以根据所述目标接入设备的转发隧道标识向所述目标接入设备直接转发组播业务数据。其中所述源接入设备可以根据所述目标接入设备的转发隧道标识向所述目标接入设备直接转发组播业务数据的过程，即为所述源接入设备根据所述目标接入设备的转发隧道端点标识建立转发组播业务数据的隧道后并向所述目标接入设备转发组播业务数据。
在一种可选的实施方式中，所述第四消息中还可以包括所述目标接入设备的转发隧道端点标识，以使所述接入控制器可以根据所述目标接入设备的转发隧道端点标识向所述目标接入设备转发从源接入设备收到的组播业务数据。具体的，在此情况下，所述源接入设备可以通过接入控制器向所述目标接入设备转发组播业务数据。所述接入控制器在获取到所述目标接入设备的转发隧道端点标识时，根据所述目标接入设备的转发隧道端点标识确定所述接入控制器与所述目标接入设备之间的转发组播数据业务隧道，从而在接收到所述源接入设备转发的组播业务数据时后转发给所述目标接入设备。
在一种可选的实施方式中，当所述目标接入设备从所述接入控制器接收的所述第二消息中包含了所述第一组播隧道建立信息时，所述目标接入设备在所述第四消息中还可以携带第二组播隧道建立信息，所述第二组播隧道建立信息用于建立传输组播业务数据的隧道。具体的，所述第二组播隧道建立信息是所述目标接入设备的组播隧道建立信息，用于建立与所述接入控制器之间的传输组播业务数据的隧道，其中，建立的传输组播业务数据的隧道用于所述目标接入设备在进行组播业务时，向所述接入控制器传输组播业务相关的数据。这样所述目标接入设备和所述接入控制器之间就可以建立传输组播业务数据的隧道，后续通过该隧道传输组播业务数据。
步骤404：所述接入控制器向所述源接入设备发送第五消息，所述第五消息用于响应将所述终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
其中，所述第五消息可以是所述接入控制器向所述源接入设备发送的Relocation Response。
在一种可选的实施方式中，所述第五消息中包含是否转发组播业务数据的指示信息，具体可以分为以下两种情况：
情况a1：上述涉及的所述第四消息中包含所述是否转发组播业务数据的指示信息，所述接入控制器可以直接将所述第四消息中包含的所述是否转发组播业务数据的指示信息包含在所述第五消息中。
所述是否转发组播业务数据的指示信息可以是隐式的指示信息也可以是显示的指示信息，具体可以为：当所述目标接入设备需要转发组播业务数据时，所述指示信息包含目标接入设备分配的用于转发该组播业务数据的隧道端点标识，可选的所述指示信息还携带一个转发组播业务数据的指示，该指示的取值可以是“转发组播业务数据”或者“未订阅组播业务”等，本申请对此不做限制。当所述目标接入设备不需要转发组播业务数据时，则所述指示信息不携带目标接入设备分配的用于转发该组播业务数据的隧道标识，可选的可以携带一个不转发组播业务数据的指示，该指示的取值可以是“不转发组播业务数据” 或者“已订阅组播业务”等，本申请对此不做限制。
情况a2：所述接入控制器根据所述目标接入设备是否订阅所述终端设备当前进行的组播业务，在所述第二消息中包含所述是否转发组播业务数据的指示信息。在此情况a2中，所述接入控制器不解析所述第四消息中是否包含有所述是否转发组播业务数据的指示信息，直接自己判断所述目标接入设备是否订阅所述终端设备当前进行的组播业务。
其中所述是否转发组播业务数据的指示信息可以是隐式的指示信息也可以是显示的指示信息，具体可以为：当所述目标接入设备未订阅所述终端设备当前进行的组播业务时，所述指示信息可以不携带任何指示，或者可以携带一个转发组播业务数据的指示，该指示的取值可以是“转发组播业务数据”或者“未订阅组播业务”或者组播业务的标识等，本发明对此不做限制。当所述目标接入设备已订阅所述终端设备当前进行的组播业务时，所述指示信息可以携带一个不转发组播业务数据的指示，该指示的取值可以是“不转发组播业务数据”或者“已订阅组播业务数据”等，可选的所述指示信息还可以携带该组播业务的标识，本申请对此不做限制。
在一种可选的实施方式中，根据转发组播业务数据的情况不同，所述第五消息还可以有如下两种情况：
第一种情况：所述第五消息中还包括所述目标接入设备的转发隧道端点标识，即将上述步骤403中描述的所述第四消息中包含的所述目标接入设备的转发隧道端点标识包含在所述第五消息中。这样后续所述源接入设备可以直接向所述目标接入设备转发组播业务数据。
第二种情况：所述第五消息中还可以包括所述接入控制器的转发隧道端点标识，以使所述源接入设备可以根据所述接入控制器的转发隧道标识向所述接入控制器发送组播业务的数据。其中，所述源接入设备可以根据所述接入控制器的转发隧道标识向所述接入控制器转发组播业务数据的过程，即为所述源接入设备根据所述接入控制器的转发隧道端点标识建立所述源接入设备和所述接入控制器之间的转发组播业务数据的隧道后并向所述接入控制器转发组播业务数据。所述在这种情况中，所述源接入设备通过所述接入控制器间接向所述目标接入控制器转发组播业务数据，具体的，所述源接入设备向所述接入控制器转发组播业务数据后，由所述接入控制器将组播业务数据转发给所述目标接入设备(具体可以通过上述步骤403描述的所述接入控制器根据所述第四消息中的所述目标接入设备的转发隧道端点标识，建立的所述接入控制器与所述目标接入设备之间的转发组播数据业务隧道转发)。
在一种实现方式中，当所述源接入设备接收到第五消息后，根据所述是否转发组播业务数据的指示信息决定是否进行该组播业务数据的转发。具体地，当所述是否转发组播业务数据的指示信息指示需要进行该组播业务数据的转发时，所述源接入设备根据所述第五消息中包含的所述目标接入设备的转发隧道端点标识，建立转发组播业务数据的隧道，并将组播业务数据直接通过转发组播业务数据的隧道转发至所述目标接入设备；或者，所述源接入设备根据所述第五消息中包含的所述接入控制器的转发隧道端点标识，建立所述源接入设备和所述接入控制器之间转发组播业务数据的隧道，并将组播业务数据通过所述源接入设备和所述接入控制器之间转发组播业务数据的隧道转发给所述接入控制器，后续由所述接入控制器将组播业务数据转发送给所述目标接入设备。当所述是否转发组播业务数据的指示信息指示不需要进行该组播业务数据的转发时，所述源接入设备则不管是否收到 所述目标接入设备分配的转发隧道端点标识或者接入控制器的转发隧道端点标识时，都不进行组播业务数据转发。
需要说明的是，在本申请实施例中，当所述源接入设备直接向所述目标接入设备转发组播业务数据时，所述源接入设备和所述目标接入设备之间的转发组播业务数据的隧道可以称为直接转发隧道，所述源接入设备可以通过直接转发隧道直接向所述目标接入设备转发组播业务相关的任何数据；当所述源接入设备通过所述接入控制器向所述目标接入设备像转发组播业务数据时，所述源接入设备和所述接入控制器之间的转发组播业务数据的隧道，以及所述接入控制器和所述目标接入设备之间的转发组播业务数据的隧道可以称之为间接转发隧道，所述源接入设备可以通过间接转发隧道通过所述接入控制器间接向所述目标接入设备转发组播业务相关的任何数据。
在一种可选的实施方式中，所述源接入设备在接收到所述第五消息后，所述源接入设备可以根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务。
在一种可选的实施方式中，当所述目标接入设备未订阅所述终端设备当前进行的组播业务时，所述源接入设备通知所述终端设备通过目标接入设备订阅所述终端设备当前进行的组播业务。
其中，所述源接入设备根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务，具体可以分为以下几种情况：
情况b1：当所述第五消息中包含了所述目标接入设备当前订阅的或承载的组播业务的标识时，源接入设备可以根据所述目标接入设备当前订阅的或承载的组播业务的标识判断所述目标接入设备是否订阅所述终端设备当前进行的组播业务。
情况b2：当所述第五消息中包含了所述目标接入设备未订阅所述终端设备当前进行的组播业务的信息，所述源接入设备根据所述信息确定所述目标接入设备未订阅所述终端设备当前进行的组播业务。
情况b3：当所述第五消息中包含的所述是否转发组播业务数据的指示信息指示转发组播业务数据时，所述源接入设备则判定所述目标接入设备未订阅所述终端设备当前进行的组播业务。
在一种可选的实施方式中，所述源接入设备通知所述终端设备通过所述目标接入设备订阅所述终端设备当前进行的组播业务，具体方法可以为：
所述源接入设备向所述终端设备发送第六消息，所述第六消息中包括订阅所述终端设备当前进行的组播业务的通知信息；
所述组播源设备将所述目标接入设备加入所述终端设备当前进行的组播业务。具体的所述终端设备向所述目标接入设备发送第七消息，所述第七消息用于指示所述目标接入设备未订阅所述终端设备当前进行的组播业务，或者向所述目标接入设备请求订阅所述终端设备当前进行的组播业务；
所述目标接入设备向组播源设备发送第十九消息，所述第十九消息用于指示所述组播源设备将所述目标接入设备加入所述终端设备当前进行的组播业务。
示例性的，所述第六消息可以是所述源接入设备向所述终端设备发送的切换命令(handover command)消息。所述第七消息可以是IGMP Join消息。
在实际情况中，所述源接入设备和所述目标接入设备之间转发组播业务数据的过程， 可以根据不同设置实现转发过程的终止，具体示例可以如下：
示例c1：在所述目标接入设备设置了数据转发定时器的情况下，所述目标接入设备在接收到来自所述源接入设备的组播业务数据时，启动所述数据转发定时器；当所述数据转发定时器超时时，所述目标接入设备启动隧道删除定时器，并向所述接入控制器发送第八消息，所述第八消息用于请求停止数据传输；所述接入控制器向所述源接入设备转发所述第八消息，以使所述源接入设备停止向所述目标接入设备转发组播业务数据，使所述源接入设备删除转发组播业务数据的隧道；当所述隧道删除定时器超时时，所述目标接入设备删除转发组播业务数据的隧道。
示例c2：在所述源接入设备设置了数据转发定时器的情况下，所述源接入设备首次向目标接入设备发送组播业务数据时，启动所述数据转发定时器；当所述数据转发定时器超时时，所述源接入设备向所述目标接入设备发送第九消息，并删除转发组播业务数据的隧道；其中，所述第九消息用于指示数据转发完成；所述目标接入设备从所述源接入设备接收所述第九消息后，删除转发组播业务数据的隧道。
示例c3：在所述源接入设备设置了数据转发定时器的情况下，所述源接入设备首次向所述目标接入设备发送组播业务数据时，启动所述数据转发定时器；当所述数据转发定时器超时时，所述源接入设备通过所述接入控制器向所述目标接入设备发送第十消息，并删除转发组播业务数据的隧道；其中，所述第十消息用于指示数据转发完成；所述接入控制器向所述目标接入设备转发所述第十消息，所述目标接入设备接收到所述第十消息后删除转发组播业务数据的隧道。
示例c4：在所述目标接入设备和所述源接入设备分别设置了数据转发定时器的情况下，所述源接入设备首次向目标接入设备发送组播业务数据时，启动设置的数据转发定时器；所述目标接入设备接收到来自所述源接入设备的组播业务数据时，启动设置的数据转发定时器；所述目标接入设备和所述源接入设备分别在各自设置的转发定时器超时时，分别删除各自的传输组播业务数据的隧道。
采用本申请实施例提供的通信方法，终端设备在接入设备之间切换的过程中，可以灵活地进行切换流程，无需固定锚点参与终端设备的切换就可以保证组播业务的连续性，这样可以避免因部署固定锚点造成的资源浪费。
基于以上实施例，下面以具体的示例，如下图5-图10所示的实施例，对本申请实施例中提供的通信方法进行详细说明。在以下示例中，以终端设备为WBCPE，接入控制器为WBAC，接入设备为WBAP(其中源接入设备为S WBAP，目标接入设备为T WBAP)为例进行说明。当涉及到组播源设备时，以组播源设备为router为例进行说明。
基于以上实施例，如图5所示，本申请实施例还提供了一种通信方法的示例，该示例可以应用于图2所示的组播架构，具体的，该示例的流程可以包括：
步骤501：S WBAP向WBAC发送第一消息，所述第一消息用于请求将WBCPE切换到T WBAP，所述第一消息中包括WBCPE的组播业务上下文。
步骤502：所述WBAC根据WBCPE的组播业务上下文判断T WBAP是否订阅了所述WBCPE当前进行的组播业务，当确定所述T WBAP未订阅所述WBCPE当前进行的组播业务时，将所述T WBAP加入所述WBCPE当前进行的组播业务。
具体的，所述WBAC将所述T WBAP加入所述WBCPE当前进行的组播业务在具体实现时，是指所述WBAC将所述T WBAP加入所述WBCPE当前进行的组播业务的组播 组中，即后续所述WBAC会将该组播业务数据(即该组播业务的数据包)发送给所述T WBAP。其中，在后续过程中所述WBAC和所述T WBAP之间进行传输组播业务数据时，是根据上述图4所示的实施例中涉及的所述接入控制器通过第一组播隧道建立信息与所述目标接入设备建立的传输组播业务数据的隧道，以及所述目标接入设备通过所述第二组播隧道建立信息与所述接入控制器之间建立的传输组播业务数据的隧道实现组播业务数据的传输的。
步骤503：所述WBAC向所述T WBAP发送第二消息，所述第二消息用于请求将所述WBCPE切换到T WBAP，所述第二消息中包括所述WBCPE的组播业务上下文。
步骤504：所述T WBAP向所述WBAC发送第四消息，所述第四消息用于响应为所述WBCPE切换WBAP的请求消息。
步骤505：所述WBAC向所述S WBAP发送第五消息，所述第五消息用于响应为所述WBCPE切换WBAP的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
需要说明的是，后续步骤均为所述指示信息指示转发组播业务数据的情况下的执行的步骤。
步骤506：所述S WBAP向所述WBCPE发送第十一消息，所述第十一消息用于指示所述WBCPE进行切换。
其中，所述第十一消息可以为所述S WBAP向所述WBCPE发送的切换命令(Handover Command)消息。
步骤507：所述S WBAP向所述T WBAP转发组播业务数据。
步骤508：所述T WBAP启动数据转发定时器。
步骤509：当所述数据转发定时器超时时，所述T WBAP启动隧道删除定时器。
步骤510：所述T WBAP向所述WBAC发送第八消息，所述第八消息用于请求停止数据传输。
具体的，所述第八消息可以为所述T WBAP向所述WBAC发送的停止数据转发请求(stop data forwarding request)。
步骤511：所述WBAC向所述S WBAP转发所述第八消息。
步骤512：当所述隧道删除定时器超时时，所述T WBAP删除转发组播业务数据的隧道。
步骤513：所述S WBAP向所述WBAC发送第十二消息，并删除转发组播业务数据的隧道，所述第十二消息用于响应所:述第八消息的数据停止转发请求。
其中，所述第十二消息可以为停止数据转发响应(stop data forwarding response)。
步骤514：所述WBAC向所述T WBAP转发所述第十二消息。
需要说明的是，上述步骤513和步骤514中第十二消息的发送步骤为可选的步骤，本申请对此不作限定。
基于以上示例，WBCPE在接入设备之间切换的过程中，可以灵活地进行切换流程，无需固定锚点参与WBCPE的切换就可以保证组播业务的连续性，这样可以因部署固定锚点造成的资源浪费。
基于以上实施例，如图6所示，本申请实施例还提供了一种通信方法的示例，该示例可以应用于图2所示的组播架构，具体的，该示例的流程可以包括：
步骤601-步骤607与图5所示的实施例中的步骤501-步骤507类似，具体可以相互参 见，此处不再一一赘述。
一种可能的示例中，当所述S WBAP设置了数据转发定时器时，可以执行以下步骤608-步骤610：
步骤608：所述S WBAP启动所述数据转发定时器。
步骤609：当所述数据转发定时器超时时，所述S WBAP向所述T WBAP发送第九消息，所述第九消息用于指示数据转发完成。
其中，所述第九消息可以是所述S WBAP生成的结束标记(end marker)包的形式存在。
步骤610：所述S WBAP删除转发组播业务数据的隧道。
步骤611：所述T WBAP删除转发组播业务数据的隧道。
另一种可能的示例中，当所述S WBAP设置了数据转发定时器时，可以执行以下步骤612-步骤616：
步骤612：所述S WBAP启动所述数据转发定时器。
步骤613：当所述数据转发定时器超时时，所述S WBAP向所述WBAC发送第十消息，所述第十消息用于指示数据转发完成。
其中，所述第十消息可以是所述S WBAP生成的结束标记(end marker)包的形式存在，也可以是一条控制面消息。
步骤614：所述S WBAP删除转发组播业务数据的隧道。
步骤615：所述WBAC向所述T WBAP转发所述第十消息。
步骤616：所述T WBAP删除转发组播业务数据的隧道。
另一种可能的示例中，当所述T WBAP和所述S WBAP分别设置了数据转发定时器时，可以执行以下步骤617-步骤620：
步骤617：所述S WBAP启动数据转发定时器。
步骤618：所述T WBAP启动数据转发定时器。
步骤619：当所述S WBAP设置的数据转发定时器超时时，所述S WBAP删除转发组播业务数据的隧道。
步骤620：当所述T WBAP设置的数据转发定时器超时时，所述T WBAP删除转发组播业务数据的隧道。
基于以上示例，WBCPE在接入设备之间切换的过程中，可以灵活地进行切换流程，无需固定锚点参与WBCPE的切换就可以保证组播业务的连续性，这样可以因部署固定锚点造成的资源浪费。
基于以上实施例，如图7所示，本申请实施例还提供了一种通信方法的示例，该示例可以应用于图3所示的组播架构，具体的，该示例的流程可以包括：
步骤701与图5所示的实施例中的步骤501类似，具体可以相互参见，此处不再一一赘述。
步骤702与图5所示的实施例中的步骤503类似，具体可以相互参见，此处不再一一赘述。
步骤703：所述T WBAP根据WBCPE的组播业务上下文判断确定自身未订阅所述WBCPE当前进行的组播业务时，向router发送第三消息，所述第三消息用于订阅所述WBCPE当前进行的组播业务。
所述router在接收到所述第三消息后，将所述T WBAP加入所述WBCPE当前进行的组播业务。
步骤704-步骤714与图5所示的实施例中的步骤504-步骤514类似，具体可以相互参见，此处不再一一赘述。
基于以上实施例，如图8所示，本申请实施例还提供了一种通信方法的示例，该示例可以应用于图3所示的组播架构，具体的，该示例的流程可以包括：
步骤801与图6所示的实施例中的步骤601类似，具体可以相互参见，此处不再一一赘述。
步骤802与图6所示的实施例中的步骤603类似，具体可以相互参见，此处不再一一赘述。
步骤803：所述T WBAP根据WBCPE的组播业务上下文判断确定自身未订阅所述WBCPE当前进行的组播业务时，向router发送第三消息，所述第三消息用于订阅所述WBCPE当前进行的组播业务。
所述router在接收到所述第三消息后，将所述T WBAP加入所述WBCPE当前进行的组播业务。
步骤804-步骤820与图6所示的实施例中的步骤604-步骤620类似，具体可以相互参见，此处不再一一赘述。
基于以上实施例，如图9所示，本申请实施例还提供了一种通信方法的示例，该示例可以应用于图3所示的组播架构，具体的，该示例的流程可以包括：
步骤901和步骤902与图7所示的实施例中的步骤701和步骤702类似，具体可以相互参见，此处不再一一赘述。
步骤903和步骤904与图7所示的实施例中的步骤704-步骤705类似，具体可以相互参见，此处不再一一赘述。
步骤905：所述S WBAP确定所述T WBAP未订阅所述WBCPE当前进行的组播业务，所述S WBAP向所述WBCPE发送第六消息，所述第六消息中包括订阅所述WBCPE当前进行的组播业务的通知信息。
其中，所述S WBAP确定所述T WBAP未订阅所述WBCPE当前进行的组播业务具体可参见图4所示的实施例中步骤404涉及的所述源接入设备根据第五消息确定目标接入设备未订阅终端设备当前进行的组播业务的相关描述，此处不再重复赘述。
其中，所述第六消息用于指示所述WBCPE切换，可以是所述S WBAP向所述WBCPE发送的handover command。
步骤906：所述WBCPE确定所述T WBAP未订阅所述WBCPE当前进行的组播业务时，所述WBCPE向所述T WBAP发送第七消息，所述第七消息用于指示所述T WAAP未订阅所述WBCPE当前进行的组播业务，或者向T WAAP请求订阅所述WBCPE当前进行的组播业务。
步骤907：所述T WBAP向所述router发送第十九消息，所述第十九消息用于指示router将所述T WBAP加入所述WBCPE当前进行的组播业务。
步骤908-步骤915与图7所示的实施例中的步骤707-步骤714类似，具体可以相互参见，此处不再一一赘述。
基于以上实施例，如图10所示，本申请实施例还提供了一种通信方法的示例，该示 例可以应用于图3所示的组播架构，具体的，该示例的流程可以包括：
步骤1001和步骤1002与图8所示的实施例中的步骤801和步骤802类似，具体可以相互参见，此处不再一一赘述。
步骤1003和步骤1004与图8所示的实施例中的步骤804-步骤805类似，具体可以相互参见，此处不再一一赘述。
步骤1005：所述S WBAP确定所述T WBAP未订阅所述WBCPE当前进行的组播业务，所述S WBAP向所述WBCPE发送第六消息，所述第六消息中包括订阅所述WBCPE当前进行的组播业务的通知信息。
其中，所述第六消息用于指示所述WBCPE切换，可以是所述S WBAP向所述WBCPE发送的handover command。
步骤1006：所述WBCPE确定所述T WBAP未订阅所述WBCPE当前进行的组播业务时，所述WBCPE向所述T WBAP发送第七消息，所述第七消息用于指示所述T WAAP未订阅所述WBCPE当前进行的组播业务，或者向T WAAP请求订阅所述WBCPE当前进行的组播业务。
步骤1007：所述T WBAP向所述router发送第十九消息，所述第十九消息用于指示router将所述T WBAP加入所述WBCPE当前进行的组播业务。
步骤1008-步骤1021与图8所示的实施例中的步骤807-步骤820类似，具体可以相互参见，此处不再一一赘述。
需要说明的是，在上述图4-图10所示的示例中涉及的步骤的具体详细描述均可以参见图4所示的实施中涉及的相应描述，在上述示例中不再重复赘述。
在实现上述图4-图10所示的实施例中的方法之前，需要对组播业务信息进行配置，以及建立组播业务，之后才会涉及在组播业务进行过程中进行终端设备的接入设备的切换流程。以下通过图11所示的实施例对组播业务信息配置过程进行说明，以及通过图12所示的实施例对组播业务建立过程进行说明。
如图11所示，本申请实施例提供了一种组播业务信息配置方法，描述了接入设备和接入控制器之间用来传递组播业务数据的隧道协议的协商过程，具体的，该方法的流程可以包括：
步骤1101：接入设备向接入控制器发送第十三消息，所述第十三消息中包括所述接入设备支持的传输组播业务数据的隧道的协议。
具体的，所述第十三消息可以是所述接入设备向所述接入控制器发送的加入请求(join request)消息。
所述接入设备支持的传输组播业务数据的隧道的协议可以是CAPWAP Data或GTP-U或其他协议类型。
在一种可选的实施方式中，当所述接入设备支持的传输组播业务数据的隧道的协议为GTP-U时，所述第十三消息中还包括所述接入设备的隧道端点标识，例如GTP-U隧道端点标识。
步骤1102：所述接入控制器向所述接入设备发送第十四消息，所述第十四消息用于响应所述第十三消息，所述第十四消息中包括所述接入控制器支持的传输组播业务数据的隧道的协议。
具体的，所述第十四消息可以为所述接入控制器向所述接入设备发送的加入响应(join  response)消息。
所述接入控制器支持的传输组播业务数据的隧道的协议可以是CAPWAP Data或GTP-U或其他协议类型。
在一种可选的实施方式中，当所述接入控制器支持的传输组播业务数据的隧道的协议为GTP-U时，所述第十四消息中还包括所述接入控制器的隧道端点标识，例如GTP-U隧道端点标识。
采用本申请实施例提供的组播业务信息配置方法，可以实现接入设备和接入控制器之间用来传输组播业务数据的隧道的协议的协商，以使后续可以建立传输组播业务数据的隧道。
如图12所示，本申请实施例提供了一种组播业务建立方法，具体的，该方法的流程可以包括：
步骤1200：终端设备已经完成网络注册，并建立了PDN/PDU会话连接。
步骤1201：终端设备向接入设备发送第十五消息，所述第十五消息用于请求建立一个组播业务，所述第十五消息中包括所述组播业务的地址和所述终端设备的标识。
步骤1202：所述接入设备向接入控制器发送第十六消息，所述第十六消息用于请求建立所述组播业务，所述第十六消息中包括所述终端设备的标识和所述组播业务的地址。
在一种可选的实施方式中，所述第十六消息中还包括第三组播隧道建立信息，所述第三组播建立隧道信息用于建立传输组播业务数据的隧道。例如，所述第三组播隧道建立信息可以为组播业务隧道端点标识。
步骤1203：所述接入控制器向所述接入设备发送第十七消息，所述第十七消息用于指示允许所述终端设备建立所述组播业务，所述第十七消息中包括所述终端设备的标识和所述组播业务的地址。
具体的，所述接入控制器根据所述终端设备的签约信息、配置信息等判断所述终端设可以使用该组播业务，则发送所述第十七消息。
其中，所述第十七消息可以是WTP Event Response消息。
在一种可选的实施方式中，所述第十七消息中还包括第四组播隧道建立信息，所述第四组播建立隧道信息用于建立传输组播业务数据的隧道。例如，所述第四组播隧道建立信息可以为组播业务隧道端点标识。
步骤1204：当所述接入设备确定自身未订阅所述组播业务，所述接入设备向所述接入控制器或者组播源设备发送第十八消息，所述第十八消息用于订阅所述组播业务。
步骤1205：所述接入控制器或者所述组播源设备将所述接入设备加入所述组播业务。
需要说明的是，上述步骤1204和步骤1205是可选的步骤。在一种可选的实施方式中，在步骤1203中，所述接入控制器可以在确定所述接入设备未订阅过所述组播业务时，将所述接入设备加入所述组播业务。
采用本申请实施例提供的组播业务建立方法，可以实现组播业务的建立，以使后续终端设备进行需要的组播业务。
基于与方法实施例同样的发明构思，本申请实施例还提供了一种装置，该装置应用于源接入设备。该装置1300具体可以是源接入设备中的处理器，或者芯片或者芯片系统，或者是一个功能模块等。参阅图13所示，该装置1300可以包括发送单元1301、接收单元1302和处理单元1303。所述发送单元1301用于所述装置1300发送信息，所述接收单元 1302用于所述装置1300接收信息，所述处理单元1303用于对所述装置1300的动作进行控制管理。所述处理单元1303还可以用于指示上述任意实施例中涉及源接入设备(例如S WBAP)的处理过程和/或本申请所描述的技术方案的其他过程。具体的，所述处理单元1303可以控制所述发送单元1301和所述接收单元1302执行的步骤，具体可以参见上述实施例，重复之处此处不再赘述。
在硬件实现上，上述处理单元1303可以为处理器或者处理电路等；发送单元1301可以为发送器或者发送电路等，接收单元1302可以为接收器或者接收电路等，发送单元1301和接收单元1302可以构成收发器。
基于与方法实施例同样的发明构思，本申请实施例还提供了一种装置，该装置应用于接入控制器。该装置1400具体可以是源接入设备中的处理器，或者芯片或者芯片系统，或者是一个功能模块等。参阅图14所示，该装置1400可以包括发送单元1401、接收单元1402和处理单元1403。所述发送单元1401用于所述装置1400发送信息，所述接收单元1402用于所述装置1400接收信息，所述处理单元1403用于对所述装置1400的动作进行控制管理。所述处理单元1403还可以用于指示上述任意实施例中涉及接入控制器(例如WBAC)的处理过程和/或本申请所描述的技术方案的其他过程。具体的，所述处理单元1403可以控制所述发送单元1401和所述接收单元1402执行的步骤，具体可以参见上述实施例，重复之处此处不再赘述。
在硬件实现上，上述处理单元1403可以为处理器或者处理电路等；发送单元1401可以为发送器或者发送电路等，接收单元1402可以为接收器或者接收电路等，发送单元1401和接收单元1402可以构成收发器。
基于与方法实施例同样的发明构思，本申请实施例还提供了一种装置，该装置应用于目标接入设备。该装置1500具体可以是源接入设备中的处理器，或者芯片或者芯片系统，或者是一个功能模块等。参阅图15所示，该装置1500可以包括发送单元1501、接收单元1502和处理单元1503。所述发送单元1501用于所述装置1500发送信息，所述接收单元1502用于所述装置1500接收信息，所述处理单元1503用于对所述装置1500的动作进行控制管理。所述处理单元1503还可以用于指示上述任意实施例中涉及目标接入设备(例如T WBAP)的处理过程和/或本申请所描述的技术方案的其他过程。具体的，所述处理单元1503可以控制所述发送单元1501和所述接收单元1502执行的步骤，具体可以参见上述实施例，重复之处此处不再赘述。
在硬件实现上，上述处理单元1503可以为处理器或者处理电路等；发送单元1501可以为发送器或者发送电路等，接收单元1502可以为接收器或者接收电路等，发送单元1501和接收单元1502可以构成收发器。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备 (可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例还提供另外一种源接入设备，用于实现通信方法。参阅图16所示，所述源接入设备1600中可以包括收发器1601和处理器1602。可选的，所述源接入设备1600中还可以包括存储器1603。其中，所述存储器1603可以设置于所述源接入设备1600内部，还可以设置于所述源接入设备1600外部。其中，所述处理器1602控制所述收发器1601接收和发送数据，并用于实现图4～图10中所述源接入设备(例如S WBAP)所执行的方法。
具体的，所述处理器1602可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器1602还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
其中，所述收发器1601、所述处理器1602和所述存储器1603之间相互连接。可选的，所述收发器1601、所述处理器1602和所述存储器1603通过总线1604相互连接；所述总线1604可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
示例性的，所述源接入设备在实现图4所示的通信方法时，具体可以包括：
所述收发器1601，用于接收和发送数据；
所述处理器1602，用于控制所述收发器1601向接入控制器发送第一消息，所述第一消息用于请求将终端设备切换到目标接入设备，所述第一消息中包括终端设备的组播业务上下文；以及控制所述收发器1601从所述接入控制器接收第五消息，所述第五消息用于响应为终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
在一种可选的实施方式中，所述处理器1602还用于：根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务。
在一种可选的实施方式中，所述处理器1602还用于：所述目标接入设备未订阅所述终端设备当前进行的组播业务时，通知所述终端设备通过目标接入设备订阅所述终端设备当前进行的组播业务。
在一种可选的实施方式中，所述处理器1602根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务时，具体用于：
当所述第五消息中还包括所述目标接入设备当前订阅或承载的组播业务的标识时，根据所述目标接入设备订当前订阅或承载的组播业务的标识确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务；或者
当所述第五消息中还包括所述目标接入设备未订阅所述终端设备当前进行的组播业务的信息，根据所述信息确定所述目标接入设备未订阅所述终端设备当前进行的组播业务；或者
当所述第五消息中包含的所述指示信息指示转发组播业务数据时，确定所述目标接入设备未订阅所述终端设备当前进行的组播业务。
在一种可选的实施方式中，当所述指示信息指示转发组播业务数据时，所述处理器1602还用于：
所述第五消息中还包括目标接入设备的转发隧道端点标识，根据所述目标接入设备转发隧道端点标识建立转发组播业务数据的隧道；或者
所述第五消息中还包括所述接入控制器的转发隧道端点标识，根据所述接入控制器的转发隧道端点标识建立转发组播业务数据的隧道。
在一种可选的实施方式中，当所述指示信息指示转发组播业务数据时，所述处理器1602还用于：控制所述收发器1601从所述接入控制器接收第八消息，所述第八消息用于请求停止数据传输；删除转发组播业务数据的隧道。
在一种可选的实施方式中，当所述指示信息指示转发组播业务数据时，所述处理器1602还用于：
控制所述收发器1601首次向目标接入设备发送组播业务数据时，启动数据转发定时器；
当所述数据转发定时器超时时，控制所述收发器1601向目标接入设备发送第九消息，并删除转发组播业务数据的隧道；其中，所述第九消息用于指示数据转发完成；或者
当所述数据转发定时器超时时，控制所述收发器1601通过所述接入控制器向所述目标接入设备发送第十消息，并删除转发组播业务数据的隧道；其中，所述第十消息用于指示数据转发完成。
在一种可选的实施方式中，所述存储器1603，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1603可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器1602执行所述存储器1603所存放的应用程序，实现上述功能，从而实现本申请实施例提供的通信方法。
基于以上实施例，本申请实施例还提供另外一种接入控制器，用于实现上述通信方法。参阅图17所示，所述接入控制器1700中可以包括收发器1701和处理器1702。可选的，所述接入控制器1700中还可以包括存储器1703。其中，所述存储器1703可以设置于所述接入控制器1700内部，还可以设置于所述接入控制器1700外部。其中，所述处理器1702控制所述收发器1701接收和发送数据，并用于实现图4～图10中所述接入控制器(例如WBAC)所执行的方法。
具体的，所述处理器1702可以是CPU，NP或者CPU和NP的组合。所述处理器1702还可以进一步包括硬件芯片。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
其中，所述收发器1701、所述处理器1702和所述存储器1703之间相互连接。可选的，所述收发器1701、所述处理器1702和所述存储器1703通过总线1704相互连接；所述总线1704可以是PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总 线等。为便于表示，图17中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
示例性的，所述接入控制器1700在实现图4所示的通信方法时，具体可以包括：
所述收发器1701，用于接收和发送数据；
所述处理器1702，用于控制所述收发器1701从源接入设备接收第一消息，所述第一消息用于请求将终端设备切换到目标接入设备，所述第一消息中包括终端设备的组播业务上下文；
控制所述收发器1701向目标接入设备发送第二消息，所述第二消息中包括终端设备的组播业务上下文；
控制所述收发器1701从所述目标接入设备接收第四消息，所述第四消息用于响应将终端设备切换到目标接入设备的请求消息；
控制所述收发器1701向所述源接入设备发送第五消息，所述第五消息用于响应将终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
在一种可选的实施方式中，所述第五消息中包含是否转发组播业务数据的指示信息，包括：
所述第四消息中包含所述是否转发组播业务数据的指示信息，所述处理器1702将所述第四消息中包含的所述是否转发组播业务数据的指示信息包含在所述第五消息中；或者
所述处理器1702根据所述目标接入设备是否订阅所述终端设备当前进行的组播业务，在所述第五消息中包含所述是否转发组播业务数据的指示信息。
在一种可选的实施方式中，所述处理器1702还用于：若确定所述目标接入设备未订阅所述终端设备当前进行的组播业务时，则将所述目标接入设备加入所述终端设备当前进行的组播业务。
在一种可选的实施方式中，所述处理器1702还用于：确定所述接入控制器与所述目标接入设备传输组播业务数据的隧道的协议为GTP-U时，所述第二消息中还包括第一组播隧道建立信息，所述第一组播隧道建立信息用于建立传输组播业务数据的隧道。
在一种可选的实施方式中，当所述指示信息指示转发组播业务数据时，所述第四消息中还包括所述目标接入设备的转发隧道端点标识，所述第五消息中还包括所述目标接入设备的转发隧道端点标识；或者所述第四消息中还包括所述目标接入设备的转发隧道端点标识，所述第五消息中还包括所述接入控制器的转发隧道端点标识。
在一种可选的实施方式中，当所述指示信息指示转发组播业务数据时，所述处理器1702还用于：控制所述收发器1701从所述目标接入设备接收第八消息，所述第八消息用于请求停止数据传输；控制所述收发器1701向所述源接入设备发送所述第八消息。
在一种可选的实施方式中，当所述指示信息指示转发组播业务数据时，所述处理器1702还用于：控制所述收发器1701从所述源接入设备接收第十消息，所述第十消息用于指示数据转发完成；控制所述收发器1701向所述目标接入设备转发所述第十消息。
在一种可选的实施方式中，所述存储器1703，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1703可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器1702执行所述存储器1703所存放的应用程序，实现上述功能，从而实现本申请实施例提 供的通信方法。
基于以上实施例，本申请实施例还提供另外一种目标接入设备，用于实现上述通信方法。参阅图18所示，所述目标接入设备1800中可以包括收发器1801和处理器1802。可选的，所述目标接入设备1800中还可以包括存储器1803。其中，所述存储器1803可以设置于所述目标接入设备1800内部，还可以设置于所述目标接入设备1800外部。其中，所述处理器1802控制所述收发器1801接收和发送数据，并用于实现图4～图10中所述目标接入设备(例如T WBAP)所执行的方法。
具体的，所述处理器1802可以是CPU，NP或者CPU和NP的组合。所述处理器1802还可以进一步包括硬件芯片。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
其中，所述收发器1801、所述处理器1802和所述存储器1803之间相互连接。可选的，所述收发器1801、所述处理器1802和所述存储器1803通过总线1804相互连接；所述总线1804可以是PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
示例性的，所述目标接入设备在实现图4所示的通信方法时，具体可以包括：
所述收发器1801，用于接收和发送数据；
所述处理器1802，用于控制所述收发器1801从接入控制器接收第二消息，所述第二消息中包括终端设备的组播业务上下文；
控制所述收发器1801向所述接入控制器发送第四消息，所述第四消息用于响应将终端设备切换到目标接入设备的请求消息。
在一种可选的实施方式中，所述第四消息中包含是否转发组播业务数据的指示信息。
在一种可选的实施方式中，所述第二消息中还包括第一组播隧道建立信息，所述第一组播隧道建立信息用于建立传输组播业务数据的隧道。
在一种可选的实施方式中，所述第四消息中还包括第二组播隧道建立信息，所述第二组播隧道建立信息用于建立传输组播业务数据的隧道。
在一种可选的实施方式中，所述第四消息中还包括所述目标接入设备的转发隧道端点标识。
在一种可选的实施方式中，所述处理器1802，在控制所述收发器1801从所述接入控制器接收到所述第二消息之后，还用于：
当根据所述终端设备的组播业务上下文确定自身未订阅所述终端设备当前进行的组播业务时，控制所述收发器1801向组播源设备发送第三消息，所述第三消息用于订阅所述终端设备当前进行的组播业务。
在一种可选的实施方式中，所述处理器1802还用于：在控制所述收发器1801接收到来自源接入设备的组播业务数据时，启动数据转发定时器；
当所述数据转发定时器超时时，启动隧道删除定时器，并控制所述收发器1801向所述接入控制器发送第八消息，所述第八消息用于请求停止数据传输；
当所述隧道删除定时器超时时，删除转发组播业务数据的隧道。
在一种可选的实施方式中，所述处理器1802还用于：
控制所述收发器1801从源接入设备接收第九消息后，删除转发组播业务数据的隧道， 其中，所述第九消息用于指示数据转发完成；或者
控制所述收发器1801从所述接入控制器接收到来自所述源接入设备的第十消息后，删除转发组播业务数据的隧道，其中，所述第十消息用于指示数据转发完成。
在一种可选的实施方式中，所述处理器1802还用于：
在控制所述收发器1801接收到来自源接入设备的组播业务数据时，启动数据转发定时器；当所述数据转发定时器超时时，删除转发组播业务数据的隧道。
在一种可选的实施方式中，所述存储器1803，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1803可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器1802执行所述存储器1803所存放的应用程序，实现上述功能，从而实现本申请实施例提供的通信方法。
基于以上实施例，本申请实施例还提供了一种计算机存储介质，该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现上述任意一个或多个实施例提供的方法。所述计算机存储介质可以包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例还提供了一种芯片，该芯片包括处理器，用于实现上述任意一个或多个实施例所涉及的功能，例如获取或处理上述方法中所涉及的信息或者消息。可选地，所述芯片还包括存储器，所述存储器，用于处理器所执行必要的程序指令和数据。该芯片，可以由芯片构成，也可以包含芯片和其他分立器件。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实 施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (56)

  1. 一种通信方法，应用于组播业务场景，其特征在于，包括：
    源接入设备向接入控制器发送第一消息，所述第一消息用于请求将终端设备切换到目标接入设备，所述第一消息中包括终端设备的组播业务上下文；
    所述源接入设备从所述接入控制器接收第五消息，所述第五消息用于响应将终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述源接入设备根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    所述目标接入设备未订阅所述终端设备当前进行的组播业务时，所述源接入设备通知所述终端设备通过目标接入设备订阅所述终端设备当前进行的组播业务。
  4. 如权利要求2或者3所述的方法，其特征在于，所述源接入设备根据所述第五消息确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务，包括：
    当所述第五消息中还包括所述目标接入设备当前订阅或承载的组播业务的标识时，所述源接入设备根据所述目标接入设备订当前订阅或承载的组播业务的标识确定所述目标接入设备是否订阅所述终端设备当前进行的组播业务；或者
    当所述第五消息中还包括所述目标接入设备未订阅所述终端设备当前进行的组播业务的信息，所述源接入设备根据所述信息确定所述目标接入设备未订阅所述终端设备当前进行的组播业务；或者
    当所述第五消息中包含的所述指示信息指示转发组播业务数据时，所述源接入设备确定所述目标接入设备未订阅所述终端设备当前进行的组播业务。
  5. 如权利要求1-4任一项所述的方法，其特征在于，当所述指示信息指示转发组播业务数据时，所述方法还包括：
    所述第五消息中还包括目标接入设备的转发隧道端点标识，所述源接入设备根据所述目标接入设备转发隧道端点标识建立转发组播业务数据的隧道；或者
    所述第五消息中还包括所述接入控制器的转发隧道端点标识，所述源接入设备根据所述接入控制器的转发隧道端点标识建立转发组播业务数据的隧道。
  6. 如权利要求5所述的方法，其特征在于，当所述指示信息指示转发组播业务数据时，所述方法还包括：
    所述源接入设备从所述接入控制器接收第八消息，所述第八消息用于请求停止数据传输；
    所述源接入设备删除转发组播业务数据的隧道。
  7. 如权利要求5所述的方法，其特征在于，当所述指示信息指示转发组播业务数据时，所述方法还包括：
    所述源接入设备首次向目标接入设备发送组播业务数据时，启动数据转发定时器；
    当所述数据转发定时器超时时，所述源接入设备向目标接入设备发送第九消息，并删除转发组播业务数据的隧道；其中，所述第九消息用于指示数据转发完成；或者
    当所述数据转发定时器超时时，所述源接入设备通过所述接入控制器向所述目标接入 设备发送第十消息，并删除转发组播业务数据的隧道；其中，所述第十消息用于指示数据转发完成。
  8. 一种通信方法，应用于组播业务场景，其特征在于，包括：
    接入控制器从源接入设备接收第一消息，所述第一消息用于请求将终端设备切换到目标接入设备，所述第一消息中包括终端设备的组播业务上下文；
    所述接入控制器向目标接入设备发送第二消息，所述第二消息中包括终端设备的组播业务上下文；
    所述接入控制器从所述目标接入设备接收第四消息，所述第四消息用于响应将终端设备切换到目标接入设备的请求消息；
    所述接入控制器向所述源接入设备发送第五消息，所述第五消息用于响应将终端设备切换到目标接入设备的请求消息，所述第五消息中包含是否转发组播业务数据的指示信息。
  9. 如权利要求8所述的方法，其特征在于，所述第五消息中包含是否转发组播业务数据的指示信息，包括：
    所述第四消息中包含所述是否转发组播业务数据的指示信息，所述接入控制器将所述第四消息中包含的所述是否转发组播业务数据的指示信息包含在所述第五消息中；或者
    所述接入控制器根据所述目标接入设备是否订阅所述终端设备当前进行的组播业务，在所述第五消息中包含所述是否转发组播业务数据的指示信息。
  10. 如权利要求8或9所述的方法，其特征在于，所述方法还包括：
    若所述目标接入设备未订阅所述终端设备当前进行的组播业务时，所述接入控制器则将所述目标接入设备加入所述终端设备当前进行的组播业务。
  11. 如权利要求10所述的方法，其特征在于，所述方法还包括：
    所述接入控制器确定所述接入控制器与所述目标接入设备传输组播业务数据的隧道的协议为GTP-U时，所述第二消息中还包括第一组播隧道建立信息，所述第一组播隧道建立信息用于建立传输组播业务数据的隧道。
  12. 如权利要求8-11任一项所述的方法，其特征在于，当所述指示信息指示转发组播业务数据时，
    所述第四消息中还包括所述目标接入设备的转发隧道端点标识，所述第五消息中还包括所述目标接入设备的转发隧道端点标识，或者
    所述第四消息中还包括所述目标接入设备的转发隧道端点标识，所述第五消息中还包括所述接入控制器的转发隧道端点标识。
  13. 如权利要求12所述的方法，其特征在于，当所述指示信息指示转发组播业务数据时，所述方法还包括：
    所述接入控制器从所述目标接入设备接收第八消息，所述第八消息用于请求停止数据传输；
    所述接入控制器向所述源接入设备发送所述第八消息。
  14. 如权利要求12所述的方法，其特征在于，当所述指示信息指示转发组播业务数据时，所述方法还包括：
    所述接入控制器从所述源接入设备接收第十消息，所述第十消息用于指示数据转发完成；
    所述接入控制器向所述目标接入设备转发所述第十消息。
  15. 一种通信方法，应用于组播业务场景，其特征在于，包括：
    目标接入设备从接入控制器接收第二消息，所述第二消息中包括终端设备的组播业务上下文；
    所述目标接入设备向所述接入控制器发送第四消息，所述第四消息用于响应将终端设备切换到目标接入设备的请求消息。
  16. 如权利要求15所述的方法，其特征在于，所述第四消息中包含是否转发组播业务数据的指示信息。
  17. 如权利要求15或16所述的方法，其特征在于，所述第二消息中还包括第一组播隧道建立信息，所述第一组播隧道建立信息用于建立传输组播业务数据的隧道。
  18. 如权利要求16或17所述的方法，其特征在于，所述第四消息中还包括第二组播隧道建立信息，所述第二组播隧道建立信息用于建立传输组播业务数据的隧道。
  19. 如权利要求16-18任一项所述的方法，其特征在于，所述第四消息中还包括所述目标接入设备的转发隧道端点标识。
  20. 如权利要求15-18任一项所述的方法，其特征在于，在所述目标接入设备从所述接入控制器接收到所述第二消息之后，所述方法还包括：
    当所述目标接入设备根据所述终端设备的组播业务上下文确定自身未订阅所述终端设备当前进行的组播业务时，所述目标接入设备向组播源设备发送第三消息，所述第三消息用于订阅所述终端设备当前进行的组播业务。
  21. 如权利要求15-20任一项所述的方法，其特征在于，所述方法还包括：
    所述目标接入设备在接收到来自源接入设备的组播业务数据时，启动数据转发定时器；
    当所述数据转发定时器超时时，所述目标接入设备启动隧道删除定时器，并向所述接入控制器发送第八消息，所述第八消息用于请求停止数据传输；
    当所述隧道删除定时器超时时，所述目标接入设备删除转发组播业务数据的隧道。
  22. 如权利要求15-20任一项所述的方法，其特征在于，所述方法还包括：
    所述目标接入设备从源接入设备接收第九消息后，删除转发组播业务数据的隧道，其中，所述第九消息用于指示数据转发完成；或者
    所述目标接入设备从所述接入控制器接收到来自所述源接入设备的第十消息后，删除转发组播业务数据的隧道，其中，所述第十消息用于指示数据转发完成。
  23. 如权利要求15-20任一项所述的方法，其特征在于，所述方法还包括：
    所述目标接入设备在接收到来自源接入设备的组播业务数据时，启动数据转发定时器；
    当所述数据转发定时器超时时，所述目标接入设备删除转发组播业务数据的隧道。
  24. 一种通信方法，应用于组播业务场景，其特征在于，包括：
    终端设备从源接入设备接收第六消息，所述第六消息中包括订阅所述终端设备当前进行的组播业务的通知信息；
    所述终端设备向目标接入设备发送第七消息，所述第七消息用于指示所述目标接入设备未订阅所述终端设备当前进行的组播业务，或者向所述目标接入设备请求订阅所述终端设备当前进行的组播业务。
  25. 一种通信方法，应用于组播业务场景，其特征在于，包括：
    目标接入设备向组播源设备发送第十九消息，所述第十九消息用于指示所述组播源设备将所述目标接入设备加入所述终端设备当前进行的组播业务。
  26. 一种组播业务信息配置方法，其特征在于，包括：
    接入设备向接入控制器发送第十三消息，所述第十三消息中包括所述接入设备支持的传输组播业务数据的隧道的协议；
    所述接入设备从所述接入控制器接收第十四消息，所述第十四消息用于响应第十三消息，所述第十四消息中包括所述接入控制器支持的传输组播业务数据的隧道的协议。
  27. 一种组播业务信息配置方法，其特征在于，包括：
    接入设备从终端设备接收第十五消息，所述第十五消息用于请求建立一个组播业务，所述第十五消息中包括所述组播业务的地址和所述终端设备的标识；
    所述接入设备向接入控制器发送第十六消息，所述第十六消息用于请求建立所述组播业务，所述第十六消息中包括所述终端设备的标识和所述组播业务的地址；
    所述接入设备从所述接入控制器接收第十七消息，所述第十七消息用于指示允许所述终端设备建立所述组播业务，所述第十七消息中包括所述终端设备的标识和所述组播业务的地址。
  28. 一种组播业务信息配置方法，其特征在于，包括：
    接入控制器从接入设备接收第十六消息，所述第十六消息用于请求建立一个组播业务，所述第十六消息中包括所述终端设备的标识和所述组播业务的地址；
    所述接入控制器向所述接入设备发送第十七消息，所述第十七消息用于指示允许所述终端设备建立所述组播业务，所述第十七消息中包括所述终端设备的标识和所述组播业务的地址。
  29. 一种装置，所述装置为源接入设备，其特征在于，包括：发送单元、接收单元和处理单元；
    所述发送单元，用于执行权利要求1-7任一项所述的方法中在所述装置侧进行数据的发送操作；
    所述接收单元，用于执行权利要求1-7任一项所述的方法中在所述装置侧进行数据的接收操作；
    所述处理单元，用于执行权利要求1-7任一项所述的方法。
  30. 一种装置，所述装置为接入控制器，其特征在于，包括：接收单元、发送单元和处理单元；
    所述接收单元，用于执行权利要求8-14任一项所述的方法中在所述装置侧进行数据的接收操作；
    所述发送单元，用于执行权利要求8-14任一项所述的方法中在所述装置侧进行数据的发送操作；
    所述处理单元，用于执行权利要求8-14任一项所述的方法。
  31. 一种装置，所述装置为目标接入设备，其特征在于，包括：接收单元、发送单元和处理单元；
    所述接收单元，用于执行权利要求15-23任一项所述的方法中在所述装置侧进行数据的接收操作；
    所述发送单元，用于执行权利要求15-23任一项所述的方法中在所述装置侧进行数据的发送操作；
    所述处理单元，用于执行权利要求15-23任一项所述的方法。
  32. 一种装置，所述装置为终端设备，其特征在于，包括：
    接收单元，用于从源接入设备接收第六消息，所述第六消息中包括订阅所述终端设备当前进行的组播业务的通知信息；
    发送单元，用于向目标接入设备发送第七消息，所述第七消息用于指示所述目标接入设备未订阅所述终端设备当前进行的组播业务，或者向所述目标接入设备请求订阅所述终端设备当前进行的组播业务；
    处理单元，用于控制所述接收单元和所述发送单元执行操作。
  33. 一种装置，所述装置为目标接入设备，其特征在于，包括：
    发送单元，用于向组播源设备发送第十九消息，所述第十九消息用于指示所述组播源设备将所述目标接入设备加入所述终端设备当前进行的组播业务；
    处理单元，用于控制所述发送单元执行操作。
  34. 一种装置，所述装置为接入设备，其特征在于，包括：
    发送单元，用于向接入控制器发送第十三消息，所述第十三消息中包括所述接入设备支持的传输组播业务数据的隧道的协议；
    接收单元，用于从所述接入控制器接收第十四消息，所述第十四消息用于响应第十三消息，所述第十四消息中包括所述接入控制器支持的传输组播业务数据的隧道的协议；
    处理单元，用于控制所述接收单元和所述发送单元执行操作。
  35. 一种装置，所述装置为接入设备，其特征在于，包括：
    接收单元，用于从终端设备接收第十五消息，所述第十五消息用于请求建立一个组播业务，所述第十五消息中包括所述组播业务的地址和所述终端设备的标识；
    发送单元，用于向接入控制器发送第十六消息，所述第十六消息用于请求建立所述组播业务，所述第十六消息中包括所述终端设备的标识和所述组播业务的地址；
    所述接收单元，还用于从所述接入控制器接收第十七消息，所述第十七消息用于指示允许所述终端设备建立所述组播业务，所述第十七消息中包括所述终端设备的标识和所述组播业务的地址；
    处理单元，用于控制所述接收单元和所述发送单元执行操作。
  36. 一种装置，所述装置为接入控制器，其特征在于，包括：
    接收单元，用于从接入设备接收第十六消息，所述第十六消息用于请求建立一个组播业务，所述第十六消息中包括所述终端设备的标识和所述组播业务的地址；
    发送单元，用于向所述接入设备发送第十七消息，所述第十七消息用于指示允许所述终端设备建立所述组播业务，所述第十七消息中包括所述终端设备的标识和所述组播业务的地址；
    处理单元，用于控制所述接收单元和所述发送单元执行操作。
  37. 一种装置，所述装置为源接入设备，应用于组播业务场景，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求1-7任一项所述的方法。
  38. 一种装置，所述装置为接入控制器，应用于组播业务场景，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求8-14任一项所述的方法。
  39. 一种装置，所述装置为目标接入设备，应用于组播业务场景，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求15-23任一项所述的方法。
  40. 一种装置，所述装置为终端设备，应用于组播业务场景，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求24所述的方法。
  41. 一种装置，所述装置为目标接入设备，应用于组播业务场景，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求25所述的方法。
  42. 一种装置，所述装置为接入设备，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求26所述的方法。
  43. 一种装置，所述装置为接入设备，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求27所述的方法。
  44. 一种装置，所述装置为接入控制器，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于执行上述权利要求28所述的方法。
  45. 一种装置，其特征在于，用于执行权利要求1-7任一项所述的方法。
  46. 一种装置，其特征在于，用于执行权利要求8-14任一项所述的方法。
  47. 一种装置，其特征在于，用于执行权利要求15-23任一项所述的方法。
  48. 一种装置，其特征在于，用于执行权利要求24所述的方法。
  49. 一种装置，其特征在于，用于执行权利要求25所述的方法。
  50. 一种装置，其特征在于，用于执行权利要求26所述的方法。
  51. 一种装置，其特征在于，用于执行权利要求27所述的方法。
  52. 一种装置，其特征在于，用于执行权利要求28所述的方法。
  53. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得计算机执行如权利要求1-28任一项所述的方法。
  54. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，所述计算机程序被计算机执行时，使得所述计算机执行如权利要求1-28任一项所述的方法。
  55. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如权利要求1-28任一项所述的方法。
  56. 一种系统，其特征在于，包括如权利要求29-52任一项所述的装置中的一个或多个。
PCT/CN2020/072858 2019-01-31 2020-01-17 一种通信方法及装置 WO2020156258A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20748976.6A EP3908042A4 (en) 2019-01-31 2020-01-17 COMMUNICATION METHOD AND DEVICE
US17/389,782 US20210360488A1 (en) 2019-01-31 2021-07-30 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910097448.2A CN111510964B (zh) 2019-01-31 2019-01-31 一种通信方法及装置
CN201910097448.2 2019-01-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/389,782 Continuation US20210360488A1 (en) 2019-01-31 2021-07-30 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2020156258A1 true WO2020156258A1 (zh) 2020-08-06

Family

ID=71841623

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/072858 WO2020156258A1 (zh) 2019-01-31 2020-01-17 一种通信方法及装置

Country Status (4)

Country Link
US (1) US20210360488A1 (zh)
EP (1) EP3908042A4 (zh)
CN (1) CN111510964B (zh)
WO (1) WO2020156258A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4275393A1 (en) * 2021-01-08 2023-11-15 Lenovo (Beijing) Limited Method and apparatus for multicast and broadcast services

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050075627A (ko) * 2004-01-17 2005-07-21 삼성전자주식회사 모바일 아이피를 사용하는 이동통신 시스템에서멀티캐스트 제공 시스템 및 방법
US20080146230A1 (en) * 2006-12-18 2008-06-19 Cisco Technology, Inc. Fast handoff for wireless devices in a wired-wireless network
CN101237393A (zh) * 2007-01-30 2008-08-06 华为技术有限公司 一种实现快速组播业务切换的方法及设备及系统
CN101242340A (zh) * 2007-02-08 2008-08-13 华为技术有限公司 一种终端设备切换组播服务的方法、装置及系统
CN101547408A (zh) * 2008-03-28 2009-09-30 华为技术有限公司 移动节点的上下文信息传输方法、移动通信系统及设备
CN102264154A (zh) * 2010-05-26 2011-11-30 中兴通讯股份有限公司 一种回程网络中的用户业务控制方法和系统

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4429815B2 (ja) * 2004-06-09 2010-03-10 株式会社エヌ・ティ・ティ・ドコモ マルチキャストグループ作成方法および作成装置、並びにコンテンツ選択方法および選択装置
US8711803B1 (en) * 2006-02-21 2014-04-29 Apple Inc. Fast base station switching method and system, and hierarchical zone-based fast handoff approach
CN101094512A (zh) * 2006-09-07 2007-12-26 中兴通讯股份有限公司 一种在组播业务中建立用户上下文和承载上下文的方法
WO2008040238A1 (fr) * 2006-09-19 2008-04-10 Huawei Technologies Co., Ltd. Procédé d'ajout à un terminal d'un service de diffusion sélective dans un réseau sans fil et système de mise en oeuvre associé
US8279829B2 (en) * 2006-10-10 2012-10-02 Futurewei Technologies, Inc. Multicast fast handover
EP1928133B1 (en) * 2006-12-01 2013-12-25 Electronics and Telecommunications Research Institute Method of transmitting data in handover between base stations in wireless communication system
US20080273503A1 (en) * 2007-05-02 2008-11-06 Lg Electronics Inc. Method and terminal for performing handover in mobile communications system of point-to-multipoint service
US9686770B2 (en) * 2010-06-15 2017-06-20 Mediatek Inc. Methods to support MBMS service continuity and counting and localized MBMS service
US9185682B2 (en) * 2010-06-15 2015-11-10 Mediatek Inc. Methods to support continuous MBMS reception without network assistance
CA2833787C (en) * 2011-04-19 2017-08-01 Fujitsu Limited Information acquiring method and base station
CN103067865B (zh) * 2011-10-19 2017-05-17 中兴通讯股份有限公司 在组播接收端切换场景下建立优化路径的方法及系统
JP5882493B2 (ja) * 2011-11-15 2016-03-09 京セラ株式会社 セルラ通信ネットワークにおけるノード検出
US9445243B2 (en) * 2013-03-22 2016-09-13 Mediatek Inc. Service continuity for group communication over LTE eMBMS
WO2015000912A1 (en) * 2013-07-01 2015-01-08 Nec Europe Ltd. Method for providing multicast/broadcast service continuity for mobile terminals
KR20150048611A (ko) * 2013-10-28 2015-05-07 삼성전자주식회사 이동성에 강인한 그룹 통신을 위한 방법 및 장치
WO2015080407A1 (en) * 2013-11-29 2015-06-04 Lg Electronics Inc. Method and apparatus for transmitting unicast request indication in wireless communication system
CN104754622A (zh) * 2013-12-31 2015-07-01 中兴通讯股份有限公司 指示信息的发送方法、装置及用户设备
KR101866619B1 (ko) * 2015-01-08 2018-06-14 주식회사 케이티 단일 셀 멀티전송 데이터를 송수신하는 방법 및 그 장치
US10397836B2 (en) * 2016-10-27 2019-08-27 Ofinno, Llc Handover for UE with V2X service
US10237874B2 (en) * 2016-11-03 2019-03-19 Samsung Electronics Co., Ltd. Method and apparatus for supporting vehicle to everything service
US10716039B2 (en) * 2016-12-02 2020-07-14 Ofinno, Llc Handover procedure for a UE with V2X services
WO2018162947A1 (en) * 2017-03-06 2018-09-13 Telefonaktiebolaget Lm Ericsson (Publ) Bit indexed explicit replication based multicast for locator identifier separation protocol
CN115486101A (zh) * 2020-02-13 2022-12-16 交互数字专利控股公司 用于5g网络中的多播和广播服务的递送模式切换的方法
KR20230132815A (ko) * 2021-01-14 2023-09-18 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Sn-간 및 sn-내 cpc의 공존
US11792693B2 (en) * 2021-05-04 2023-10-17 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for redirecting users of multimedia priority services
US11804215B1 (en) * 2022-04-29 2023-10-31 Apple Inc. Sonic responses

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050075627A (ko) * 2004-01-17 2005-07-21 삼성전자주식회사 모바일 아이피를 사용하는 이동통신 시스템에서멀티캐스트 제공 시스템 및 방법
US20080146230A1 (en) * 2006-12-18 2008-06-19 Cisco Technology, Inc. Fast handoff for wireless devices in a wired-wireless network
CN101237393A (zh) * 2007-01-30 2008-08-06 华为技术有限公司 一种实现快速组播业务切换的方法及设备及系统
CN101242340A (zh) * 2007-02-08 2008-08-13 华为技术有限公司 一种终端设备切换组播服务的方法、装置及系统
CN101547408A (zh) * 2008-03-28 2009-09-30 华为技术有限公司 移动节点的上下文信息传输方法、移动通信系统及设备
CN102264154A (zh) * 2010-05-26 2011-11-30 中兴通讯股份有限公司 一种回程网络中的用户业务控制方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3908042A4 *

Also Published As

Publication number Publication date
CN111510964A (zh) 2020-08-07
EP3908042A4 (en) 2022-06-08
EP3908042A1 (en) 2021-11-10
CN111510964B (zh) 2021-09-07
US20210360488A1 (en) 2021-11-18

Similar Documents

Publication Publication Date Title
US11943789B2 (en) Communication system
EP3834384B1 (en) Control plane based configuration for time sensitive networking
EP3694234B1 (en) Communication system, communication method and device thereof
WO2020001572A1 (zh) 通信方法及装置
US10924294B2 (en) Evolved multimedia broadcast/multicast service (EMBMS) system and EMBMS system management method
WO2020147761A1 (zh) 一种pdu会话切换方法及其装置
US10009187B2 (en) Method and device for group communication, having robust mobility
US8656029B2 (en) Multicast session setup in networks by determining a multicast session parameter based on a pre-existing unicast session parameter
CN109673026B (zh) 数据转发方法、装置和系统
WO2022170819A1 (zh) 用于实现多播广播业务切换的方法及相关设备
WO2017201722A1 (zh) 一种通信控制的方法及相关网元
CN111919502A (zh) 用于处理网络的装置和方法
WO2015018232A1 (zh) 设备到设备连接管理方法、装置及基站
JP2022521088A (ja) ポリシー管理方法及び装置
US7554940B2 (en) Mobile communication system, method of controlling operation thereof, and node used for the system
WO2022166559A1 (zh) 通信方法及装置
WO2020156258A1 (zh) 一种通信方法及装置
KR20070093369A (ko) 무선통신 시스템에서 일대다 ｍｂｍｓ 서비스를 정지하는방법 및 장치
WO2020078288A1 (zh) 一种直接通信的方法和设备
WO2015035648A1 (zh) 一种应用管理的方法及装置
WO2022151265A1 (zh) 一种通信方法、终端设备和网络设备
KR102393322B1 (ko) 5g 코어망에서 네트워크 슬라이스 식별자를 결정하여 전달하는 방법
KR20240004483A (ko) Mbs 세션의 핸드오버 방법, 및 그 시스템 및 장치
GB2617541A (en) Communication system
JP2024517916A (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: 20748976

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020748976

Country of ref document: EP

Effective date: 20210805