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

一种通信方法及通信装置 Download PDF

Info

Publication number
WO2022227971A1
WO2022227971A1 PCT/CN2022/083109 CN2022083109W WO2022227971A1 WO 2022227971 A1 WO2022227971 A1 WO 2022227971A1 CN 2022083109 W CN2022083109 W CN 2022083109W WO 2022227971 A1 WO2022227971 A1 WO 2022227971A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
message
state
access network
mbs
Prior art date
Application number
PCT/CN2022/083109
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 EP22794444.4A priority Critical patent/EP4322608A1/en
Priority to BR112023022715A priority patent/BR112023022715A2/pt
Publication of WO2022227971A1 publication Critical patent/WO2022227971A1/zh
Priority to US18/496,231 priority patent/US20240064864A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method and a communication device.
  • Multicast broadcast service (multicast and broadcast service, MBS) is a service transmitted by access network equipment to multiple terminal equipment.
  • MBS includes live broadcast service, public safety service, and batch software update service.
  • the MBS data comes from the data server, is sent to the access network device via the core network device, and is then sent by the access network device to at least one terminal device.
  • the network access device provides services, and the second cell is served by the target access network device.
  • the source access network device supports the multicast broadcast transmission mode and provides MBS for the terminal device, but when the target access network device does not have the MBS required by the terminal device, or when the target access network device does not support the multicast broadcast transmission mode How to ensure the transmission of MBS data in the handover process is an urgent problem to be solved.
  • the communication method and device provided by the embodiments of the present application can ensure the normal transmission of the MBS in the handover process and avoid unnecessary waste of resources.
  • a communication method is provided, and the method can be executed by a second access network device or a chip in the second access network device.
  • the method includes: receiving a first message from a first access network device, wherein the first message indicates that a first state of an MBS session is activated or deactivated; sending the first message to the first access network device The first confirmation message corresponding to the message.
  • the first message is used to indicate the first state of the MBS session, and the second access network device may determine whether to request the core network to establish the UP tunnel according to the first state.
  • the second access network device can trigger a new UP tunnel to ensure the normal transmission of the MBS during the handover process; if the first state of the MBS session is deactivated, the second access network device It is not necessary to trigger the creation of a new UP tunnel or to request a new suspended UP tunnel to avoid the problem of wasting resources.
  • the first message indicates that the first state of the MBS session of the multicast broadcast service is active, and the method further includes: sending a first request message to the core network device, where the first request message is used to request the establishment of the the user plane tunnel corresponding to the MBS session; or, the first message indicates that the first state of the multicast broadcast service MBS session is deactivated, and the method further includes: determining that the user plane tunnel corresponding to the MBS session does not need to be established currently; or, The first message indicates that the first state of the MBS session of the multicast broadcast service is deactivated, and the method further includes: sending a first request message to the core network device, where the first request message is used to request the establishment of the corresponding MBS session The user plane tunnel is suspended.
  • the first message is a handover request message
  • the first confirmation message is a handover request confirmation message
  • the first message includes first status information, and the first status information indicates that the first status is activated or deactivated; activate or deactivate.
  • a communication method in a second aspect, can be executed by a first access network device or a chip in the first access network device.
  • the method includes: sending a first message to a second access network device, wherein the first message indicates that a first state of the MBS session is activated or deactivated; receiving the first message from the second access network device The first confirmation message corresponding to the message.
  • the first message is a handover request message
  • the first confirmation message is a handover request confirmation message
  • the method before sending the first message to the second access network device, the method further includes: receiving third information sent by the core network device, where the third information indicates the first state of the MBS session.
  • the third information is information contained in the MBS session modification message; or, the third information is information contained in the PDU session modification message, wherein the PDU session is associated with the MBS session or, the third information is information in an information field in the header of the data packet of the MBS service.
  • a communication method is provided, and the method can be performed by a second access network device or a chip in the second access network device.
  • the method includes: sending a second message to a core network device; receiving a second confirmation message corresponding to the second message from the core network device; wherein the second message indicates that the first state of the MBS session is active or deactivation; and/or, the second confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • the state of the MBS session is the first state or the second state, wherein the first state is the state of the MBS session before the terminal device is switched, and the second state is the state of the MBS session after the terminal device is switched.
  • the MBS that the terminal device is interested in or is receiving.
  • the second access network device can learn the status of the MBS session. If the status of the MBS session is active, the second access network device can trigger the creation of a new UP tunnel to ensure that during the handover process Normal transmission of MBS; if the state of the MBS session is deactivated, the second access network device may not trigger the creation of a new UP tunnel or request to create a new suspended UP tunnel to avoid the problem of resource waste. On the other hand, during the handover process, the state of the MBS session may change, and this solution can avoid the problem of behavior mismatch caused by the change of the MBS session state.
  • the state of the MBS session is activated, and the method further includes: sending a first request message to a core network device, where the first request message is used to request the establishment of a user plane tunnel corresponding to the MBS session; or , the state of the MBS session is deactivated, and the method further includes: determining that there is currently no need to establish a user plane tunnel corresponding to the MBS session; or, the state of the MBS session is deactivated, and the method further includes: to the The core network device sends a first request message, where the first request message is used to request the establishment of a user plane tunnel corresponding to the MBS session, and the user plane tunnel is suspended.
  • the method further includes: determining that the state of the MBS session is the second state.
  • the first state is activated, the second state is deactivated, and it is determined that the state of the MBS session is deactivated.
  • the second message is a path switch request message
  • the second confirmation message is a path switch request confirmation message
  • the second message includes first state information, and the first state information indicates that the first state is activation or deactivation; or, the second message indicates the first state by indicating whether the first state information is included.
  • the second confirmation message includes second state information, and the second state information indicates that the second state is activated or deactivated; or, the second confirmation message indicates the second state by whether or not the second state information is included.
  • a communication method is provided, and the method can be executed by a core network device or a chip in the core network device.
  • the method includes: receiving a second message from a second access network device; sending a second confirmation message corresponding to the second message to the second access network device; wherein the second message indicates the MBS session The first state of the MBS session is activated or deactivated; and/or the second confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • the state of the MBS session is active, and the method further includes: receiving a first request message from a second access network device, where the first request message is used to request establishment of a user plane corresponding to the MBS session tunnel; or, the status of the MBS session is deactivated, and the method further includes: determining that the user plane tunnel corresponding to the MBS session does not need to be established at present; or, the status of the MBS session is deactivated, and the method further includes: A first request message is received from the second access network device, where the first request message is used to request to establish a user plane tunnel corresponding to the MBS session, and the user plane tunnel is suspended.
  • a communication method is provided, and the method can be executed by a second access network device or a chip in the second access network device.
  • the method includes: sending a fourth message to a core network device, where the fourth message is used to request the establishment of a user plane tunnel corresponding to an MBS session; receiving a fourth confirmation message corresponding to the fourth message from the core network device, where the The fourth confirmation message indicates that the state of the MBS session is activated or deactivated.
  • the second access network device may learn the management of the UP tunnel by the core network device according to the fourth confirmation message.
  • the second access network device can trigger a new UP tunnel to ensure the normal transmission of the MBS during the handover process; if the first state of the MBS session is deactivated, the second access network device You can not trigger the creation of an UP tunnel or suspend the newly created UP tunnel to avoid wasting resources.
  • the fourth confirmation message includes information on establishing the user plane tunnel and indicating that the state of the MBS session is active; or, the fourth confirmation message includes information on refusing to establish the user plane tunnel; or , the fourth confirmation message includes the information of establishing the user plane tunnel and indicating that the status of the MBS session is deactivated.
  • a communication method is provided, and the method can be executed by a core network device or a chip in the core network device.
  • the method includes: receiving a fourth message from a second access network device, where the fourth message is used to request the establishment of a user plane tunnel corresponding to an MBS session; and sending a message corresponding to the fourth message to the second access network device
  • the fourth confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • the second access network device can learn the management of the UP tunnel by the core network device according to the fourth confirmation message, so as to ensure the normal transmission of the MBS during the handover process and avoid resource waste.
  • a communication method is provided, and the method can be executed by a core network device or a chip in the core network device.
  • the method includes: determining a first state of the MBS session; sending third information to a first access network device, the third information indicating the first state of the MBS session.
  • the solution can be applied before handover, so that the first access network device can know the status of the MBS session, and then specify the operation of MBS transmission, so as to ensure the normal transmission of the MBS after the subsequent handover.
  • the third information is information contained in the MBS session modification message; or, the third information is information contained in a first PDU session modification message or a setup message, wherein the first PDU The session is associated with the MBS session; or, the third information is information in an information field in the header of the data packet of the MBS service.
  • a communication method is provided, and the method can be executed by a first access network device or a chip in the first access network device.
  • the method includes: receiving third information, wherein the third information indicates a first state of the MBS session; and saving the MBS state information in the context of the MBS and/or the terminal device.
  • the solution can be applied to before handover, the first access network device learns the state of the MBS session according to the third information, and then specifies the operation of MBS transmission, and guarantees the normal transmission of the MBS after the subsequent handover.
  • a communication method is provided, and the method can be executed by a first access network device or a chip in the first access network device.
  • the method includes: determining that the state of the MBS session is deactivated, and the MBS session is associated with a first PDU session; sending a fifth message to a core network device, where the fifth message is used to request to release the first PDU session, wherein, The first PDU session is only used for the MBS session; or, a fifth message is sent to the core network device, where the fifth message is used to request to delete the information of the MBS session from the first PDU session, Wherein, the first PDU session is used to transmit unicast services, and/or the first PDU session is also associated with other activated MBS sessions.
  • the fifth message is used to request to release the first PDU session, and the method further includes: releasing the RRC connection of the terminal device.
  • the fifth message is used to request to delete the information of the MBS session from the first PDU session, and the method further includes: sending handover indication information to the terminal device, and the handover The indication information is used to instruct the terminal device to switch the target cell, and the target cell does not support the MBS session.
  • the first access network device is a source access network device serving the terminal device.
  • a communication method is provided, and the method can be executed by a core network device or a chip in the core network device.
  • the method includes: receiving a fifth message from a first access network device, where the fifth message is used to request the release of a first PDU session, wherein the first PDU session is only used for the MBS session; or, from the first PDU session An access network device receives a fifth message, where the fifth message is used to request that the information of the MBS session be deleted from the first PDU session, wherein the first PDU session is used to transmit unicast services, and/ Or, the first PDU session is also associated with other activated MBS sessions. The state of the MBS session is deactivated, and the MBS session is associated with the first PDU session.
  • a communication system may include a first access network device and a second access network device.
  • the second access network device may be configured to execute the method in any possible implementation manner of the first aspect
  • the first access network device may be configured to execute any possible implementation manner of the second aspect method in .
  • a twelfth aspect provides a communication system, where the communication system may include a second access network device and a core network device.
  • the second access network device may be used to execute the method in any possible implementation manner of the third aspect
  • the core network device may be configured to execute the method in any possible implementation manner of the fourth aspect
  • the second access network device may be used to perform the method in any possible implementation manner of the fifth aspect
  • the core network device may be used to perform the method in any possible implementation manner of the sixth aspect method.
  • a thirteenth aspect provides a communication system, where the communication system may include a first access network device and a core network device.
  • the first access network device may be used to execute the method in any possible implementation manner of the eighth aspect
  • the core network device may be configured to execute the method in any possible implementation manner of the seventh aspect
  • the first access network device may be used to perform the method in any possible implementation manner of the ninth aspect
  • the core network device may be used to perform the method in any possible implementation manner of the tenth aspect method.
  • a fourteenth aspect provides a communication system, where the communication system may include a first access network device, a second access network device, and a core network device.
  • the second access network device may be configured to execute the method in any possible implementation manner of the first aspect, the third aspect, and/or the fifth aspect, and the first access network device may use
  • the core network device may be used to perform any of the fourth aspect, the sixth aspect, and/or any of the seventh aspect. A method in a possible implementation.
  • a fifteenth aspect provides a communication apparatus, including each module or unit for performing the method in any possible implementation manner of the first aspect, the third aspect, or the fifth aspect.
  • a sixteenth aspect provides a communication apparatus, including each module or unit for performing the method in any possible implementation manner of the second aspect, the eighth aspect, or the ninth aspect.
  • a seventeenth aspect provides a communication apparatus, including each module or unit for performing the method in any possible implementation manner of the fourth aspect, the sixth aspect, the seventh aspect, or the tenth aspect.
  • a communication apparatus including a processor.
  • the processor is coupled to the memory and can be configured to execute instructions in the memory, so that the communication apparatus performs the method in any possible implementation manner of the first aspect, the third aspect, or the fifth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a transceiver and/or an antenna.
  • the communication apparatus may be a second access network device or a chip configured in the second access network device.
  • a communication apparatus including a processor.
  • the processor is coupled to the memory and can be configured to execute instructions in the memory, so that the communication apparatus executes the method in any possible implementation manner of the second aspect, the eighth aspect, or the ninth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a transceiver and/or an antenna.
  • the communication apparatus may be the first access network device or a chip configured in the first access network device.
  • a communication apparatus including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory, so that the communication apparatus performs the method in any possible implementation manner of the fourth aspect, the sixth aspect, the seventh aspect, or the tenth aspect.
  • the communication device further includes a memory.
  • the communication apparatus may be a core network device or a chip configured in the core network device.
  • a twenty-first aspect provides an access network device, and the access network device can implement the method in any possible implementation manner of the first aspect, the third aspect, or the fifth aspect, or, the The access network device may implement the method in any possible implementation manner of the second aspect, the eighth aspect, or the ninth aspect.
  • the access network device may be a chip (such as a baseband chip, or a communication chip, etc.) or a base station device, and the above method may be implemented by software, hardware, or by executing corresponding software by hardware.
  • the access network device includes a processor and a memory.
  • the processor is configured to support the access network device to perform the method in any of the possible implementation manners of the first aspect, the third aspect, or the fifth aspect; or, the processor is configured to support the access network device to perform the above-mentioned method
  • the memory is used to store instructions and/or data.
  • the access network device further includes a radio frequency unit and an antenna.
  • the access network device includes a baseband unit and a transceiver unit.
  • the baseband unit is configured to perform the actions performed by the access network device in any of the possible implementation methods of the first aspect, the third aspect, or the fifth aspect, or the baseband unit is configured to perform the aforementioned actions.
  • Any of the second aspect, the eighth aspect, or any one of the possible implementation methods of the ninth aspect implements the action internally implemented by the access network device.
  • the transceiver unit is used for performing the actions of the access network device sending to or receiving from the outside.
  • the access network device includes a processor and a transceiver.
  • the processor is configured to support the access network device to perform the method in any of the possible implementation manners of the first aspect, the third aspect, or the fifth aspect, or the processor is configured to support the access network device to perform the aforementioned method.
  • the transceiver may be an input-output unit, such as an input-output circuit or an input-output interface.
  • the access network device may include a unit module that performs corresponding actions in any of the possible implementation methods of the first aspect, the third aspect, or the fifth aspect, or, The access network device may include a unit module that performs any one of the second aspect, the eighth aspect, or the ninth aspect, which may implement the corresponding actions in the method.
  • a twenty-second aspect provides a core network device, which can implement the method in any possible implementation manner of the fourth aspect, the sixth aspect, the seventh aspect, or the tenth aspect.
  • the core network device may be a chip (such as a baseband chip, or a communication chip, etc.) or a core network device, and the above method may be implemented through software, hardware, or by executing corresponding software through hardware.
  • the core network device includes a processor and a memory.
  • the processor is configured to support the core network device to perform the method in any possible implementation manner of the fourth aspect, the sixth aspect, the seventh aspect, or the tenth aspect.
  • the memory is used to store instructions and/or data.
  • the core network device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the above-mentioned fourth aspect, sixth aspect, and seventh aspect Aspect, or, the method in any possible implementation manner of the tenth aspect.
  • the core network device includes a processing unit, where the processing unit may be used to perform some internal operations of the core network device.
  • the functions performed by the processing unit may correspond to the operations involved in the fourth aspect, the sixth aspect, the seventh aspect, or the tenth aspect.
  • the core network device may include a unit module that performs the corresponding actions in any of the above-mentioned fourth aspect, sixth aspect, seventh aspect, or any one of the possible implementation methods of the tenth aspect .
  • a twenty-third aspect provides a computer-readable storage medium storing a computer program or instruction, when the computer program or instruction is executed, any one of the first aspect, the third aspect, or the fifth aspect is implemented.
  • a twenty-fourth aspect provides a computer-readable storage medium storing a computer program or instruction.
  • the computer program or instruction When executed, any one of the second aspect, the eighth aspect, or the ninth aspect can be realized.
  • a twenty-fifth aspect provides a computer-readable storage medium storing a computer program or instruction.
  • the fourth aspect, the sixth aspect, the seventh aspect, or the first aspect can be realized.
  • the method in any possible implementation manner of the ten aspects.
  • a twenty-sixth aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that the processor performs any of the above aspects or the method in any of the possible implementations of this aspect.
  • the above-mentioned processor is a chip
  • the input circuit is an input pin
  • the output circuit is an output pin
  • the processing circuit is a transistor, a gate circuit, a flip-flop and/or various logic circuits.
  • a twenty-seventh aspect provides a computer program product comprising a computer program or instruction, which, when the computer program or instruction is executed, causes a computer to execute any one of the first aspect, the third aspect, or the fifth aspect method in one possible implementation.
  • a twenty-eighth aspect provides a computer program product comprising a computer program or instruction, which, when the computer program or instruction is executed, causes the computer to execute any one of the second aspect, the eighth aspect, or the ninth aspect method in one possible implementation.
  • a twenty-ninth aspect provides a computer program product comprising a computer program or instruction, which, when the computer program or instruction is executed, causes a computer to execute the above-mentioned fourth aspect, sixth aspect, seventh aspect, or tenth aspect A method in any of the possible implementations of an aspect.
  • Fig. 1 is the schematic diagram of the communication system of this application.
  • Fig. 2 is a kind of handover flow schematic diagram provided by this application.
  • 3A is a schematic diagram of a switching scenario provided by the present application.
  • 3B is a schematic diagram of another switching scenario provided by the present application.
  • FIG. 11 is a schematic structural diagram of a communication device provided by the application.
  • FIG. 12 is a schematic structural diagram of a communication device provided by the application.
  • FIG. 13 is a schematic structural diagram of an access network device provided by this application.
  • FIG. 14 is a schematic structural diagram of a core network device provided by this application.
  • the methods and apparatuses provided in the embodiments of the present application can be applied to various communication systems, for example, a long term evolution (LTE) system, a fifth generation (5G) system, and a new radio (NR) system , wireless fidelity (wireless-fidelity, WiFi) system, 3rd generation partnership project (3rd generation partnership project, 3GPP) related communication systems, other communication systems or multiple communication fusion systems that may appear in the future.
  • the core network of the 4G system may be called an evolved packet core (EPC), and the access network may be called long term evolution (LTE).
  • the core network of the 5G system can be called 5GC (5G core), and the access network can be called New Wireless.
  • 5G core 5GC
  • the communication system in this application includes access network equipment, core network equipment and terminal equipment, which are described below.
  • An access network device is a network-side device with wireless transceiver functions.
  • An access network device may be a device in a radio access network (radio access network, RAN) that provides a wireless communication function for a terminal device, so it may also be referred to as a RAN device.
  • the access network device may be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a next generation NodeB (gNB) in a 5G mobile communication system, a transmission reception point (transmission reception point, TRP), 3GPP subsequent evolution base stations, access nodes in WiFi systems, wireless relay nodes, wireless backhaul nodes, etc.
  • An access network device may include one or more co-sited or non-co-sited sending and receiving points.
  • the access network device may include one or more centralized units (central units, CUs), one or more distributed units (distributed units, DUs), or one or more CUs and one or more DUs.
  • the functions of the CU may be implemented by one entity or by different entities.
  • the functions of the CU are further divided, that is, the control plane and the user plane are separated and implemented by different entities, namely the control plane CU entity (ie CU-CP entity) and the user plane CU entity (ie CU-UP entity),
  • the CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the access network equipment.
  • part of the functions of the radio access network equipment can be implemented through multiple network function entities.
  • These network function entities may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • the access network device may be a road side unit (RSU).
  • the multiple access network devices in the communication system may be base stations of the same type, or may be base stations of different types.
  • the base station can communicate with the terminal equipment, and can also communicate with the terminal equipment through the relay station.
  • the device for implementing the function of the access network device may be the access network device itself, or may be a device capable of supporting the access network device to realize the function, such as a chip system or a device capable of realizing the function of the access network device
  • the combination device and component of the device can be installed in the access network equipment.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the technical solution is described by taking an access network device as an example.
  • Core network equipment is used to implement functions such as mobility management, data processing, session management, policy and charging.
  • the names of devices implementing core network functions in systems with different access technologies may be different, which are not limited in this application.
  • the logical network elements of 5GC include: access and mobility management function (AMF), session management function (SMF), or user plane function (UPF) Wait.
  • AMF is a network element used for access and mobility management of terminal equipment, mainly involving functions such as location update, network registration, and handover control of terminal equipment.
  • SMF is a network element used to manage sessions of terminal equipment, mainly involving functions such as session establishment, modification and release.
  • UPF is a network element used to receive and forward user data. UPF is controlled by SMF.
  • Different logical network elements of 5GC can be deployed on the same or different physical devices.
  • AMF and SMF can be deployed on the same physical device or on two physical devices.
  • the logical network elements of the 5GC can be deployed on the same physical device as the network elements of the 4G core network.
  • the device for realizing the function of the core network equipment may be the core network device, or it may be a device capable of supporting the core network device to realize the function, such as a chip system or a combined device or component that can realize the function of the core network device. Installed in the core network equipment.
  • the technical solution is described by taking the core network device as an example.
  • a terminal device is a user-side device with wireless transceiver function, which can be a fixed device, a mobile device, a handheld device (such as a mobile phone), a wearable device, a vehicle-mounted device, or a wireless device (such as a communication module) built into the above-mentioned device. , modem, or system-on-a-chip, etc.).
  • Terminal devices are used to connect people, things, machines, etc., and can be widely used in various scenarios, such as: cellular communication, device-to-device (D2D) communication, V2X communication, machine-to-machine/machine class Communication (M2M/MTC) communication, Internet of things (IoT), virtual reality (VR), augmented reality (AR), industrial control ( industrial control), unmanned driving (self driving), telemedicine (remote medical), smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation, smart city, drone, robot etc. scene.
  • D2D device-to-device
  • V2X machine-to-machine/machine class Communication
  • M2M/MTC machine-to-machine/machine class Communication
  • IoT Internet of things
  • VR virtual reality
  • AR augmented reality
  • industrial control industrial control
  • unmanned driving self driving
  • telemedicine remote medical
  • smart grid smart furniture, smart office, smart wear, smart transportation, smart city, drone, robot etc. scene.
  • the terminal device may be a handheld terminal in cellular communication, a communication device in D2D, an IoT device in MTC, a surveillance camera in smart transportation and smart city, or a communication device on drones, etc.
  • Terminal equipment may sometimes be referred to as user equipment (UE), user terminal, user equipment, subscriber unit, subscriber station, terminal, access terminal, access station, UE station, remote station, mobile device, or wireless communication device, etc. Wait.
  • the device for realizing the function of the terminal device may be the terminal device, or it may be a device capable of supporting the terminal device to realize the function, such as a chip system or a combined device or component capable of realizing the function of the terminal device. Can be installed in terminal equipment.
  • a terminal device is taken as an example to describe the technical solution.
  • FIG. 1 is a schematic diagram of a communication system suitable for the present application.
  • the communication system 100 includes: a core network device 110 , a first access network device 120 , a second access network device 130 , and a terminal device 140 .
  • the core network device 110 receives the MBS from the server, and sends the MBS to the access network device (the first access network device 120 or the second access network device 130).
  • the first access network device 120 may be referred to as a source access network device, such as a source gNB (source gNB).
  • source gNB source gNB
  • the first cell provided by the first access network device 120 may be referred to as a source cell.
  • the first access network device 120 provides network services for the terminal device 140 .
  • the first access network device 120 is configured to receive the MBS from the core network device 110 and send the MBS to the terminal device 140 .
  • the second access network device 130 may be referred to as a target access network device, such as a target gNB (target gNB).
  • target gNB target gNB
  • the second cell is served by the second access network device 130 and may be referred to as a target cell.
  • the second access network device After the terminal device 140 performs the cell handover, the second access network device provides the terminal device 140 with a network service.
  • the second access network device 130 is configured to receive the MBS from the core network device 110 and send the MBS to the terminal device 140 .
  • the terminal device 140 is configured to communicate with the access network device, receive data from the access network device, or send data to the access network device.
  • the terminal device 140 is used to receive MBS from the access network device.
  • the terminal device is moving away from the currently accessed first cell.
  • the strength of the signal sent by the first access network device to the terminal device is reduced to a certain value, if the terminal device continues to camp in the first cell and the first access network device provides services, the communication quality will be reduced.
  • the terminal device determines that the signal strength of the second cell is greater than that of the first cell, the terminal device needs to report the event to the first access network device to trigger the first access network device to initiate In the handover process, the terminal equipment is handed over from the first cell to the second cell.
  • the terminal device will be described by taking the UE as an example in the following application.
  • MBS is a service transmitted to multiple UEs, such as a live broadcast service, a public safety service, and a batch software update service.
  • MBS may also be referred to as a multimedia broadcast multicast service (multimedia broadcast multicast service, MBMS).
  • the description information of the MBS includes the description information of one or more MBS flows, wherein the description information of the MBS flow includes at least one of the following: the quality of service identifier (QoS flow identifier, QFI) of the MBS flow, the characteristic information of the MBS flow, the MBS flow The quality of service (QoS) requirements of the flow.
  • QFI quality of service identifier
  • the data packets of the MBS flow can be identified by the QoS flow sequence number (QFI sequence number, QFI SN) or the user plane of the general packet radio service (general packet radio service, GPRS) tunneling protocol user plane (GPRS Tunneling Protocol user plane, GTP-U) Sequence number (GTP-U sequence number, GTP-U SN) identification.
  • QFI sequence number QFI SN
  • GPRS general packet radio service
  • GTP-U GPRS Tunneling Protocol user plane
  • GTP-U sequence number GTP-U sequence number, GTP-U SN
  • unicast refers to sending service data to the UE through a protocol data unit (protocol data unit, PDU) session.
  • the unicast mode of MBS refers to sending MBS data to the UE through the PDU session, or sending MBS data to the UE through the UE-level user plane tunnel, which can be called the 5GC independent multicast broadcast service traffic delivery method (5G core individual MBS traffic delivery method ), which can be referred to as unicast in the following.
  • the unicast service is a service oriented to a single UE.
  • the unicast transmission mode point-to-point, PTP mainly refers to the transmission mode of data packets on the air interface side, which is oriented to a single UE.
  • Multicast/broadcast refers to sending MBS data to terminal devices through multicast/broadcast sessions, or sending MBS data to UEs through a shared user plane tunnel, also known as 5GC shared multicast broadcast service traffic delivery method (5G core shared MBS traffic delivery method), which can be referred to as multicast broadcast method in the future.
  • 5G core shared MBS traffic delivery method 5G core shared MBS traffic delivery method
  • Protocol data unit session The PDU session provides data connectivity between the UE and a data network (DN). Therefore, before the UE sends data traffic, a PDU session should be established first.
  • the creation is initiated by the UE, and the UE can transmit data with the DN only after the core network accepts the request of the UE and allocates corresponding control plane and user plane resources.
  • the PDU session is at the UE level, that is to say, a certain PDU session is only used for a certain UE.
  • a PDU session tunnel is established.
  • the UE requests the core network to create a PDU session, and the core network can create one or more PDU sessions according to its service requirements.
  • Multicast broadcast session The MBS session is used to transmit MBS services.
  • the MBS can be transmitted between the core network device and the access network device through a common transmission channel MBS session.
  • Each MBS session includes at least one MBS quality of service (quality of service, QoS) flow.
  • QoS quality of service
  • MBS sessions are oriented to multiple UEs.
  • For a UE that transmits MBS services through an MBS session there is also a PDU session associated with the MBS session.
  • the PDU session includes: the QoS flow of the MBS service and the MBS ID. That is to say, the QoS flow of the MBS service and the MBS ID exist in the UE context.
  • the PDU session associated with the MBS session can be any of the following: the PDU session only includes the QoS flow of the MBS; the PDU session only includes the QoS flow of multiple MBSs, one of which is the QoS flow of the MBS; or, the PDU session Contains the QoS flow of the unicast service and the QoS flow of the MBS.
  • the states of the MBS session include activation and deactivation, which are triggered and managed by the core network. Regardless of the activated or deactivated state, the MBS information (QoS flow and MBS ID) included in the PDU session can still be stored in the UE context, thus avoiding the need for multiple modifications to increase and Delete MBS information.
  • UP tunnel that is, the GPRS Tunneling Protocol user plane (GTP-U) tunnel, which is used for the connection between the UPF network element of the core network and the access network equipment. data transmission.
  • GTP-U GPRS Tunneling Protocol user plane
  • MBS can be transmitted through the UP tunnel corresponding to the MBS session.
  • the deactivated state the UP tunnel corresponding to the MBS session will be deleted, and when the MBS session is activated again, the tunnel corresponding to the MBS session can be rebuilt.
  • FIG. 2 is a schematic diagram of a handover (HO) process.
  • the handover process is briefly described below with reference to FIG. 2 .
  • the UE accesses the first access network device.
  • the UE camps on the first cell and enters a radio resource control (radio resource control, RRC) connected state.
  • the core network device sends service data of the UE to the first access network device, for example, the service is MBS.
  • the first access network device receives the service data, and sends the service data to the UE.
  • RRC radio resource control
  • a first access network device sends a measurement configuration parameter to a UE.
  • the UE receives the measurement configuration parameter from the first access network device.
  • the measurement configuration parameters include at least one of the following: measurement frequency/cell information, reporting threshold configuration, filtering parameter configuration, timer duration configuration and other information.
  • the UE in the RRC connected state sends a measurement report (measurement report).
  • the first access network device receives the measurement report.
  • the UE measures the signal strength of the frequency point or the cell according to the measurement configuration parameter, and determines the measurement result; then, the UE determines and reports the measurement report according to the measurement result.
  • the first access network device determines the second access network device according to the measurement report, the operation policy, or the PLMN supported by the UE.
  • the second access network device is an access network device to which the UE is about to be handed over, such as a target base station; the first access network device is an access network device currently serving the UE, such as a source base station.
  • the first access network device sends a handover request message (handover request message) to the second access network device, and sends the context (UE context) information of the UE to the second access network device along with the handover request message.
  • the second access network device receives the handover request message from the first access network device.
  • the second access network device sends a handover request acknowledgement (handover request acknowledge) message to the first access network device.
  • the first access network device receives the handover request confirmation message from the second access network device.
  • the second access network device determines that the UE can be allowed to access, and sends a handover request confirmation message to the first access network device.
  • the handover request confirmation message includes at least one of the following: a cell radio network temporary identifier (cell radio network temporary identifier, C-RNTI), and a security algorithm of the second access network device.
  • the first access network device sends an RRC reconfiguration message (RRC reconfiguration message) to the UE.
  • the UE receives the RRC reconfiguration message from the first access network device.
  • the RRC reconfiguration message includes at least one of the following: a physical cell identifier (PCI) of the second cell, a new C-RNTI, and a security algorithm identifier (security algorithm identifiers) of the second access network device ), the random access channel (RACH) resource information (such as dedicated RACH resources and/or public RACH resources) required to access the second cell, the system information block (SIB) of the second cell .
  • PCI physical cell identifier
  • SIB system information block
  • the UE synchronizes to the second cell, and sends an RRC reconfiguration complete message (RRC reconfiguration complete message) to the second access network device, indicating that the RRC handover is completed, that is, the RAN handover is completed.
  • RRC reconfiguration complete message RRC reconfiguration complete message
  • the second access network device sends a path switch request message (path switch request message) to the core network device.
  • the core network device receives the path switching request message sent by the second access network device.
  • the path switching request message is used to trigger switching of the downlink data path to the second access network device, and establish a control plane interface between the core network device and the second access network device.
  • the core network device switches the downlink data path to the second access network device.
  • the core network device sends a path switch request acknowledgement (path switch request acknowledge) message to the second access network device.
  • the second access network device receives the path switching request confirmation message sent by the core network device.
  • the core network device in S208 and S210 is AMF.
  • the purpose of the path switching request is to request the core network to switch the terminal point (some) of the user plane transmission bearer of the UE under the first access network device to the second access network device, so that the core network can pass the first access network device.
  • the second access network device continues to transmit data to the UE.
  • the second access network device sends a UE context release (UE context release) message to the first access network device.
  • the first access network device receives the UE context release message sent by the second access network device.
  • UE context release UE context release
  • the release message indicates that the handover is successful, and further, the first access network device releases the context-related radio resources and control plane resources of the UE.
  • the embodiment of the present application involves two switching scenarios, wherein the first scenario is shown in FIG. 3A , and the second scenario is shown in FIG. 3B .
  • an access network device that supports an MBS session may be referred to as an MBS access network device, and a cell served by the MBS access network device may be referred to as an MBS cell. Session transfer MBS.
  • an access network device that does not support MBS sessions may be referred to as a non-MBS (non-MBS) access network device, such as a legacy base station, and a cell served by a non-MBS access network device may be referred to as
  • MBS is transmitted between the core network device and the non-MBS access network device through a unicast PDU session.
  • the first access network device is an MBS access network device. Before the UE is handed over to the second cell, the first access network device has the MBS that the UE is transmitting or is interested in.
  • the second access network device is an MBS access network device, but before the UE switches to the second cell, the second access network device does not have the MBS that the UE is transmitting or is interested in.
  • the second cell is a serving cell of the second access network device.
  • the second access network device since the second access network device does not have the MBS required by the UE before the handover, and does not know the status of the MBS session, the second access network device will trigger the The core network device establishes an UP tunnel for the MBS for transmitting MBS data. However, if the current state of the MBS session is deactivated, that is, no MBS data needs to be transmitted, the newly created UP tunnel will be deleted after a period of time. The newly created UP tunnel is deleted before being used, which wastes resources and is useless.
  • the first access network device is an MBS access network device.
  • the second access network device is a non-MBS access network device.
  • the second access network device cannot identify the MBS session and its status, so the second access network device will trigger the core network device to establish an UP tunnel for the PDU session associated with the MBS session for transmitting MBS data.
  • the newly created UP tunnel will be deleted after a period of time because there is no MBS data, and the That is, the newly created UP tunnel is deleted before it is used, which wastes resources and is useless.
  • the core network device, the access network device and the terminal device are used as examples for description, and the core network device mentioned in the method embodiment can also be replaced by Executed by the chip configured in the core network device, the access network device mentioned in the method embodiment may also be replaced by a chip configured in the access network device, and the terminal device may also be replaced by a device configured in the terminal device. chip implementation.
  • the core network equipment, the access network equipment and the terminal equipment may specifically be in the various forms mentioned above.
  • the access network device may be a device with an RRC connection control function, such as a base station, a CU, or a CU-CP.
  • the core network device may be a device with an AMF function, or a device with an AMF function and a UPF function, or the core network device may be a device with an AMF function and an SMF function, or the core network device may be a device with an AMF function , UPF capable and SMF capable devices.
  • FIG. 4 is a schematic flowchart of a communication method provided in Embodiment 1 of the present application.
  • the communication system provided in the first embodiment includes: a first access network device and a second access network device, where the first access network device may be used to execute any possible implementation of the first embodiment
  • the method in the manner, the second access network device may be used to execute the method in any possible implementation manner of Embodiment 1.
  • Embodiment 1 a possible implementation will be described by taking the scenario 1 shown in FIG. 3A as an example.
  • the method includes the following steps.
  • a first access network device sends a first message.
  • the second access network device receives the first message.
  • the first message indicates that the first state of the MBS session is activation or deactivation.
  • the second access network device sends a first confirmation message.
  • the first access network device receives the first confirmation message.
  • the first confirmation message is a confirmation message corresponding to the first message.
  • the MBS is the service that the UE is interested in or is receiving.
  • the first state is the state of the MBS session before the UE is switched, that is, the state of the MBS session that the core network device notifies the first access network device before the UE is switched.
  • the MBS context managed by the first access network device includes the first state of the MBS session.
  • the first access network device may save the MBS state information for subsequent use, and the information is stored in the MBS context and/or in the UE context.
  • the second access network device saves the state of the MBS session in the MBS context and/or the UE context.
  • the first message indicates the first state of the MBS session, specifically the following method 1, method 2 or method 3:
  • Method 1 The first message includes first state information, where the first state information indicates that the first state is activated or deactivated.
  • Method 2 The first message indicates the first state by whether or not the first state information is included. For example, the first message includes the first state information, and the first message indicates that the first state is activated; or, the first message does not include the first state information, and the first message indicates that the first state is deactivated.
  • the first state information is activation information of the MBS session.
  • Method 3 The first message indicates the first state by whether or not the first state information is included. For example, the first message includes the first state information, and the first message indicates that the first state is deactivated; or, the first message does not include the first state information, and the first message indicates that the first state is active.
  • the first state information is deactivation information of the MBS session.
  • the first message is a handover request message
  • the first confirmation message is a handover request confirmation message.
  • a new information element information element, IE
  • IE information element
  • the first message is a new message
  • the first confirmation message is also a new message.
  • the first message is newly introduced to indicate the first state of the MBS session.
  • the method further includes: the second access network device acquires the state of the MBS session as the first state according to the first message.
  • the state of the MBS session is active, and the second access network device sends a first request message to the core network device, where the first request message is used to request the establishment of the UP tunnel corresponding to the MBS session.
  • the core network device receives the first request message sent by the second access network device.
  • the state of the MBS session is deactivated, and the processing method of the second access network device is one of the following two processing methods: first, the second access network device determines that the current UP tunnel corresponding to the MBS session does not need to be established. That is, the second access network device determines that there is no need to request the core network device to establish the UP tunnel corresponding to the MBS session. Then, after the MBS session is activated, the establishment of the UP tunnel is requested again.
  • the core network device determines that the UP tunnel corresponding to the MBS session does not need to be established currently. That is, the core network device does not need to receive the message sent by the second access network device for requesting to establish the UP tunnel.
  • the second access network device sends a first request message to the core network device, where the first request message is used to request the establishment of an UP tunnel corresponding to the MBS session, and the UP tunnel is suspended.
  • the UP tunnel is suspended (suspended) or the tunnel is in a deactivated state. That is, the UP tunnel is reserved and is not used for transmitting MBS data.
  • the core network device receives a message sent by the second access network device for requesting to establish the UP tunnel.
  • the first message is used to indicate the first state of the MBS session, and the second access network device may determine whether to request the core network to establish an UP tunnel according to the first state. If the first state of the MBS session is active, the second access network device can trigger a new UP tunnel to ensure the normal transmission of the MBS during the handover process; if the first state of the MBS session is deactivated, the second access network device It is not necessary to trigger the creation of a new UP tunnel or to request a new suspended UP tunnel to avoid the problem of wasting resources.
  • FIG. 5 is a schematic flowchart of a communication method provided in Embodiment 2 of the present application.
  • the communication system provided in the second embodiment includes: a second access network device and a core network device, where the second access network device may be used to execute any of the possible implementations of this embodiment.
  • the core network device may be used to execute the method in any possible implementation manner of this embodiment.
  • a possible implementation will be described by taking the scenario 1 shown in FIG. 3A as an example. The method includes the following steps.
  • a second access network device sends a second message.
  • the core network device receives the second message.
  • the core network device sends a second confirmation message.
  • the second access network device receives the second confirmation message.
  • the second confirmation message is a confirmation message corresponding to the second message.
  • the second message indicates that the first state of the MBS session is activated or deactivated, wherein, for the description of the first state, refer to Embodiment 1, which is not repeated here; and/or, the second confirmation message indicates the second state of the MBS session.
  • the state is activated or deactivated, wherein the second state is the state of the MBS session after the UE is switched, that is, the core network device notifies the MBS session of the second access network device through a second confirmation message after the UE is switched. state.
  • the second message indicates the first state of the MBS session, specifically the following method 1, method 2 or method 3:
  • Method 1 The second message includes first state information, where the first state information indicates that the first state is activated or deactivated.
  • Method 2 The second message indicates the first state by whether or not the first state information is included. For example, the second message includes the first state information, and the second message indicates that the first state is activated; or, the second message does not include the first state information, and the second message indicates that the first state is deactivated.
  • the first state information is activation information of the MBS session.
  • Method 3 The second message indicates the first state by whether or not the first state information is included. For example, the second message includes the first state information, and the second message indicates that the first state is deactivated; or, the second message does not include the first state information, and the second message indicates that the first state is active.
  • the first state information is deactivation information of the MBS session.
  • the second confirmation message indicates the second state of the MBS session, specifically the following method 1, method 2 or method 3:
  • the second confirmation message includes second state information, where the second state information indicates that the second state is activated or deactivated.
  • the second confirmation message indicates the second state by whether or not the second state information is included.
  • the second confirmation message includes the second state information, and the second confirmation message indicates that the second state is active; or, the second confirmation message does not include the second state information, and the second confirmation message indicates that the second state is deactivated.
  • the second state information is activation information of the MBS session.
  • the second confirmation message indicates the second state by whether or not the second state information is included.
  • the second confirmation message includes the second state information, and the second confirmation message indicates that the second state is deactivated; or, the second confirmation message does not include the second state information, and the second confirmation message indicates that the second state is active.
  • the second state information is deactivation information of the MBS session.
  • the second confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • the second access network device acquires the state of the MBS session as the second state.
  • the second message indicates that the first state of the MBS session is activated or deactivated.
  • the state in which the second access network device acquires the MBS session is the first state.
  • the second confirmation message may not carry information indicating the second state, or the second confirmation message may confirm that the current state of the MBS session is first state.
  • the second message indicates that the first state of the MBS session is activated or deactivated
  • the second confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • the second access network device determines that the state of the MBS session is the second state. For example, the first state is activated, the second state is deactivated, and the second access network device determines that the state of the MBS session is deactivated.
  • the second message is a path switching request message
  • the second confirmation message is a path switching request confirmation message.
  • a new information element needs to be added to the existing path switch request message, and/or, in order to indicate the second state of the MBS session, it needs to be added to the existing path switch request confirmation message. new cell.
  • the second message is a new message
  • the second confirmation message is also a new message.
  • the second message is newly introduced to indicate the first state of the MBS session
  • the second confirmation message is newly introduced to indicate the second state of the MBS session.
  • the state of the MBS session is active, and the second access network device sends a first request message to the core network device, where the first request message is used to request the establishment of the UP tunnel corresponding to the MBS session.
  • the core network device receives the first request message sent by the second access network device.
  • the state of the MBS session is deactivated, and the processing method of the second access network device may refer to the description of Embodiment 1, and details are not repeated here.
  • the second access network device can learn the status of the MBS session. If the status of the MBS session is active, the second access network device can trigger the creation of a new UP tunnel to ensure that during the handover process Normal transmission of MBS; if the state of the MBS session is deactivated, the second access network device may not trigger the creation of a new UP tunnel or request to create a new suspended UP tunnel to avoid the problem of resource waste.
  • the state of the MBS session may change, that is, the first state may be different from the second state. If the first state is still processed, the problem of behavior mismatch caused by the change of the MBS session state may be caused. For example, if the MBS session changes from activation to deactivation, if the first access network device still processes the activation according to the activation, it will cause waste of resources. For example, when the MBS session changes from deactivation to activation, if the first access network device still performs the deactivation process, the UP tunnel cannot be established, and the MBS data cannot be received normally. Then, by adopting the method of this embodiment, the problem of behavior mismatch caused by the change of the MBS session state can be avoided.
  • FIG. 5 is a schematic flowchart of a communication method provided in Embodiment 3 of the present application.
  • the communication system provided in the third embodiment includes: a second access network device and a core network device, where the second access network device may be used to execute any of the possible implementations of this embodiment.
  • the core network device may be used to execute the method in any possible implementation manner of this embodiment.
  • Embodiment 3 a possible implementation will be described by taking the scenario 1 shown in FIG. 3A as an example. The method includes the following steps.
  • the second access network device sends a fourth message.
  • the core network device receives the fourth message.
  • the fourth message is used for requesting to establish a user plane tunnel corresponding to the MBS session, that is, the user plane tunnel is used for data transmission of the MBS session.
  • the core network device sends a fourth confirmation message.
  • the second access network device receives the fourth confirmation message.
  • the fourth confirmation message is a confirmation message corresponding to the fourth message.
  • the fourth confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • the second state is the state of the MBS session after the UE is switched, that is, the second state of the MBS session that the core network device notifies the second access network device through a fourth confirmation message after the UE is switched.
  • the fourth confirmation message includes information on establishing a user plane tunnel and indicating that the second state of the MBS session is active.
  • the fourth confirmation message includes information of refusing to establish the user plane tunnel.
  • the state of the MBS session may be deactivated, so as to avoid the waste of resources caused by the release of the newly created tunnel.
  • the fourth confirmation message includes information on establishing a user plane tunnel and indicating that the state of the MBS session is deactivated.
  • the UP tunnel is suspended (suspended) or in a deactivated state, that is, the UP tunnel is reserved, but is not used for transmitting MBS data.
  • the advantage of reserving the UP tunnel is that when the MBS session is subsequently activated, the UP tunnel can continue to be used, avoiding the procedures related to UP tunnel deletion and UP tunnel reconstruction, saving signaling overhead, and avoiding the delay caused by UP tunnel reconstruction. .
  • the second access network device may learn the management of the UP tunnel by the core network device according to the fourth confirmation message. If the first state of the MBS session is deactivated, the second access network device may not trigger the newly created UP tunnel or suspend the newly created UP tunnel to avoid waste of resources. If the first state of the MBS session is active, the second access network device may trigger a new UP tunnel to ensure normal transmission of the MBS during the handover process.
  • FIG. 6 is a schematic flowchart of a detailed communication method provided by Embodiment 4 of the present application.
  • the communication system provided in the fourth embodiment includes: a second access network device and a core network device, where the second access network device may be used to execute any of the possible implementations of this embodiment.
  • the core network device may be used to execute the method in any possible implementation manner of this embodiment.
  • Embodiment 4 a possible implementation will be described by taking the scenario 1 shown in FIG. 3A as an example. It should be noted that, for the fourth embodiment, reference may be made to the descriptions of the second and third embodiments, and the same parts will not be repeated.
  • the method includes the following steps.
  • a second access network device sends a second message.
  • the core network device receives the second message.
  • the core network device sends a second confirmation message.
  • the second access network device receives the second confirmation message.
  • the second confirmation message is a confirmation message corresponding to the second message.
  • the second message indicates the first state of the MBS session, and/or the second confirmation message indicates the second state of the MBS session.
  • the second message is a path switching request message
  • the second confirmation message is a path switching request confirmation message.
  • the second access network device sends a fourth message.
  • the core network device receives the fourth message.
  • the fourth message is used for requesting to establish a user plane tunnel corresponding to the MBS session.
  • the core network device sends a fourth confirmation message.
  • the second access network device receives the fourth confirmation message.
  • the fourth confirmation message is a confirmation message corresponding to the fourth message.
  • the fourth confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • the second message indicates that the first state of the MBS session is active
  • the fourth message requests to establish an UP tunnel associated with the MBS session
  • the fourth confirmation message includes information to establish the UP tunnel and indicates that the second state of the MBS session is active.
  • the second message indicates that the first state of the MBS session is active
  • the fourth message requests the establishment of an UP tunnel associated with the MBS session
  • the fourth confirmation message includes information about refusing to establish the user plane tunnel, or, the fourth confirmation message Including the information of establishing the UP tunnel and indicating that the state of the MBS session is deactivated, the UP tunnel is suspended.
  • the second confirmation message indicates that the second state of the MBS session is active
  • the fourth message requests the establishment of an UP tunnel associated with the MBS session
  • the fourth confirmation message includes information for establishing the UP tunnel and indicates that the second state of the MBS session is active.
  • the second message indicates that the first state of the MBS session is deactivated
  • the second confirmation message indicates that the second state of the MBS session is active
  • the fourth message requests to establish an UP tunnel associated with the MBS session
  • the fourth confirmation message includes establishing The information of the UP tunnel and the second state indicating that the MBS session is active.
  • the state of the MBS session may change. Through the multiple interactions between the second access network device and the core network device on the MBS session state and the clear behavior of establishing the UP tunnel, it is possible to avoid problems caused by the change of the MBS session state. behavior mismatch problem. If the MBS session state is active, a new UP tunnel may be created between the second access network device and the core network device, so as to ensure the normal transmission of the MBS during the handover process.
  • FIG. 7 is a schematic flowchart of a detailed communication method provided by Embodiment 5 of the present application.
  • the communication system provided in Embodiment 5 includes: a first access network device, a second access network device, and a core network device, where the first access network device can be used to perform any of the steps in this embodiment.
  • the method in a possible implementation manner the second access network device may be used to execute the method in any possible implementation manner of this embodiment, and the core network device may be used to execute any possible implementation manner of this embodiment method in .
  • the steps indicated by dotted lines in FIG. 7 are optional, and will not be repeated in the following.
  • the fifth embodiment a possible implementation will be described by taking the scenario 1 shown in FIG. 3A as an example. It should be noted that, for the fifth embodiment, reference may be made to the descriptions of the first, second, third and fourth embodiments, and the same parts will not be repeated.
  • the method includes the following steps.
  • the core network device determines the first state of the MBS session.
  • the state of the MBS session is managed by the core network, that is, the state change of the MBS session is triggered by the core network.
  • the description of the first state refers to Embodiment 1, and details are not repeated here.
  • the core network device sends third information.
  • the first access network device receives the third information.
  • the third information indicates the first state of the MBS session.
  • the third information is information contained in the MBS session modification message; or, the third information is information in an information field in the header of the data packet of the MBS service.
  • the third information is information contained in the first PDU session modification message or the establishment message, where the first PDU session is associated with the MBS session.
  • the UE notifies the first access network device of the service that the UE is interested in, or in other words applies for joining the MBS session (MBS session join), so that the first access network device determines to send the MBS data to the UE.
  • MBS session join the MBS session join
  • the first access network device After receiving the request of the UE to join the MBS, the first access network device will establish and allocate corresponding resources for the UE for subsequent MBS transmission, such as the first PDU session for transmitting the MBS.
  • the state of the MBS session can be in an active or deactivated state. Therefore, the core network may notify the first access network device of the status of the MBS session through the first PDU session modification message or the establishment message.
  • the first access network device may acquire the status of the MBS session, and further specify the operation of MBS transmission. Further, the first access network device may store the MBS state information in the MBS context and/or the UE context.
  • S701 and S702 are also applicable to non-switching scenarios.
  • the first access network device determines to switch the UE to a cell served by the second access network device according to the measurement report sent by the UE. For a specific description, refer to the handover process shown in FIG. 2 , which will not be repeated here.
  • the first access network device sends the first message.
  • the second access network device receives the first message.
  • the first message indicates that the first state of the MBS session is activation or deactivation.
  • the second access network device sends a first confirmation message.
  • the first access network device receives the first confirmation message.
  • the first confirmation message is a confirmation message corresponding to the first message.
  • the first message is a handover request message
  • the first confirmation message is a handover request confirmation message
  • the core network device determines the second state of the MBS session.
  • the second state is the state of the MBS session after the UE is handed over.
  • this embodiment includes steps S707 and S708.
  • the second access network device sends a second message.
  • the core network device receives the second message.
  • the core network device sends a second confirmation message.
  • the second access network device receives the second confirmation message.
  • the second confirmation message is a confirmation message corresponding to the second message.
  • the second message indicates the first state of the MBS session, and/or the second confirmation message indicates the second state of the MBS session.
  • the second message is a path switching request message
  • the second confirmation message is a path switching request confirmation message.
  • this embodiment includes steps S709 and S710.
  • the second access network device sends a fourth message.
  • the core network device receives the fourth message.
  • the fourth message is used for requesting to establish a user plane tunnel corresponding to the MBS session.
  • the core network device sends a fourth confirmation message.
  • the second access network device receives the fourth confirmation message.
  • the fourth confirmation message is a confirmation message corresponding to the fourth message.
  • the fourth confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • this embodiment includes steps S707 , S708 , S709 and S710 .
  • steps S707 , S708 , S709 and S710 for a specific description, refer to Embodiment 4, which will not be repeated here.
  • the state of the MBS session is unclear, and the behavior of the second access network device and the core network device is unclear.
  • This embodiment provides a complete flow of MBS session state interaction and how to establish an UP tunnel.
  • the behavior of the second access network device and the core network device is clarified; if the MBS session state is active, a new UP tunnel can be created between the second access network device and the core network device to ensure the handover process normal transmission of the MBS in the middle; if the state of the MBS session is deactivated, the second access network device may not trigger the creation of a new UP tunnel or request to create a new suspended UP tunnel, so as to avoid the problem of resource waste.
  • the problem of behavior mismatch caused by the change of the MBS session state during the handover process can be solved.
  • FIG. 8 is a schematic flowchart of a detailed communication method provided by Embodiment 6 of the present application.
  • the communication system provided in Embodiment 6 includes: a first access network device, a second access network device, and a core network device, where the first access network device can be used to perform any of the steps in this embodiment.
  • the method in a possible implementation manner the second access network device may be used to execute the method in any possible implementation manner of this embodiment, and the core network device may be used to execute any possible implementation manner of this embodiment method in .
  • the steps represented by dotted lines in FIG. 8 are optional, and will not be repeated in the following.
  • Embodiment 6 a possible implementation will be described by taking the scenario 1 shown in FIG. 3A as an example. It should be noted that, for the sixth embodiment, reference may be made to the descriptions of the first, second, third and fourth embodiments, and the same parts will not be repeated.
  • the access network device serving the UE is switched from the first access network device to the second access network device, and needs to pass through the core network. The method includes the following steps.
  • the core network device determines the first state of the MBS session.
  • the core network device sends third information.
  • the first access network device receives the third information.
  • the third information indicates the first state of the MBS session.
  • the first access network device determines to switch the UE to a cell served by the second access network device according to the measurement report sent by the UE.
  • the first access network device sends a first handover request message.
  • the core network device receives the first handover request message.
  • the first handover request message indicates to handover the UE to a cell served by the second access network device.
  • the core network device sends a second handover request message.
  • the second access network device receives the second handover request message.
  • the second handover request message indicates to handover the UE to a cell served by the second access network device.
  • the second handover request message further indicates that the first state of the MBS session is activated or deactivated.
  • the first handover request message and the second handover request message belong to different messages, but both instruct the UE to handover to the cell served by the second access network device.
  • the second handover request message indicates the first state of the MBS session. For details, reference may be made to method 1, method 2 or method 3 in which the first message indicates the first state of the MBS session in Embodiment 1, which will not be repeated here.
  • the second access network device sends a second handover request confirmation message.
  • the core network device receives the second handover request confirmation message.
  • the second handover request confirmation message is a confirmation message of the second handover request message.
  • the core network device sends a first handover request confirmation message.
  • the first access network device receives the first handover request confirmation message.
  • the first handover request confirmation message is a confirmation message of the first handover request message.
  • the core network device determines the second state of the MBS session. For a specific description, refer to Embodiment 5, which will not be repeated here.
  • this embodiment includes steps S809 and S810.
  • the second access network device sends a second message.
  • the core network device receives the second message.
  • the core network device sends a second confirmation message.
  • the second access network device receives the second confirmation message.
  • the second confirmation message is a confirmation message of the second message.
  • the second message indicates the first state of the MBS session, and/or the second confirmation message indicates the second state of the MBS session.
  • the second message is a path switching request message
  • the second confirmation message is a path switching request confirmation message.
  • this embodiment includes steps S811 and S812.
  • the second access network device sends a fourth message.
  • the core network device receives the fourth message.
  • the fourth message is used for requesting to establish a user plane tunnel corresponding to the MBS session.
  • the core network device sends a fourth confirmation message.
  • the second access network device receives the fourth confirmation message.
  • the fourth confirmation message is a confirmation message of the fourth message.
  • the fourth confirmation message indicates that the second state of the MBS session is activated or deactivated.
  • this embodiment includes steps S809, S810, S811 and S812.
  • steps S809, S810, S811 and S812. For a specific description, refer to Embodiment 4, which will not be repeated here.
  • the state of the MBS session is unclear, and the behavior of the second access network device and the core network device is unclear.
  • This embodiment provides a complete flow of MBS session state interaction and how to establish an UP tunnel.
  • the behavior of the second access network device and the core network device is clarified; if the MBS session state is active, a new UP tunnel can be created between the second access network device and the core network device to ensure the handover process normal transmission of the MBS in the middle; if the state of the MBS session is deactivated, the second access network device may not trigger the creation of a new UP tunnel or request to create a new suspended UP tunnel, so as to avoid the problem of resource waste.
  • the problem of behavior mismatch caused by the change of the MBS session state during the handover process can be solved.
  • FIG. 9 is a schematic flowchart of a communication method according to Embodiment 7 of the present application.
  • the communication system provided in this embodiment includes: a first access network device and a core network device, where the first access network device may be used to execute any of the possible implementations of this embodiment.
  • the core network device may be used to execute the method in any possible implementation manner of this embodiment.
  • the steps represented by dotted lines in FIG. 9 are optional, and will not be repeated in the following.
  • a possible implementation will be described by taking the second scenario shown in FIG. 3B as an example. The method includes the following steps.
  • the first access network device determines that the state of the MBS session is deactivated, and the MBS session is associated with the first PDU session. Wherein, the first PDU session is only used for the MBS session.
  • the first PDU session is a PDU session configured by the terminal device, and the first PDU session is only used for the MBS.
  • S901, S701, S702 and S703 in Embodiment 5 may also be included.
  • the core network notifies the first access network device to delete the first PDU session. Therefore, this embodiment includes steps S902 and S903.
  • the first access network device replies to the core network device, that is, S905 is also included.
  • the first access network device sends a fifth message to the core network device.
  • the core network device receives the fifth message.
  • the fifth message is used to request to release the first PDU session, or in other words, the fifth message includes a release request message of the first PDU session.
  • the fifth message further includes a cause value of the release, for example, because the UE wants to switch to a non-MBS base station, the MBS related information needs to be released.
  • the core network device sends a fifth confirmation message corresponding to the fifth message.
  • the first access network device receives the fifth confirmation message of the fifth message sent by the core network device.
  • the fifth acknowledgement message includes release information of the first PDU session.
  • the method further includes: the core network device releases the first PDU session, for example, the resources occupied by the first PDU session.
  • the first access network device releases the first PDU session. For example, the resources occupied by the first PDU session, etc.
  • the first access network device notifies the core network device after deleting the first PDU session. Therefore, this embodiment includes step S905.
  • the core network device will reply with confirmation information, that is, S906 is also included.
  • the first access network device sends a release message of the first PDU session.
  • the core network device receives the release message of the first PDU session.
  • the core network device sends a release confirmation message of the first PDU session.
  • the first access network device receives the release confirmation message of the first PDU session.
  • the first access network device releases the RRC connection of the UE. Accordingly, the UE receives the RRC release message.
  • the UE can enter the RRC idle state (idle)/inactive state (inactive).
  • the first one is step S907, informing the UE to enter the RRC idle state/inactive state.
  • the UE enters the RRC idle state/inactive state by itself.
  • the RRC idle state/inactive state can be determined by the configuration information received by the UE, such as cell-level configuration information, or the NAS non-access stratum information received by the UE about releasing the PDU session. After the UE enters the RRC idle state/inactive state, it can perform cell selection, reselection and other behaviors to meet its mobility requirements.
  • the MBS session of the MBS service that the UE is interested in has been deactivated. However, the MBS ID and &Qos flow still exist in the UE's PDU session. Therefore, when the HO occurs, the second access network device will establish an UP tunnel and a corresponding DRB for the MBS ID that the UE is interested in. If the current state of the MBS session is deactivated, and the PDU session associated with the MBS session only contains the QoS flow of the MBS, then after a period of time, the newly created UP tunnel will be deleted because there is no MBS data, that is, the The newly created UP tunnel is deleted before it is used, which wastes resources and is useless. By adopting the method of this embodiment, the waste of resources caused by the deletion of the newly created UP tunnel before it is used can be avoided.
  • FIG. 10 is a schematic flowchart of a communication method according to Embodiment 8 of the present application.
  • the communication system provided in this embodiment includes: a first access network device and a core network device, where the first access network device may be used to execute any of the possible implementations of this embodiment.
  • the core network device may be used to execute the method in any possible implementation manner of this embodiment.
  • the steps indicated by dotted lines in FIG. 10 are optional, and will not be repeated in the following.
  • a possible implementation will be described by taking the second scenario shown in FIG. 3B as an example. The method includes the following steps.
  • the first access network device determines that the state of the MBS session is deactivated, and the MBS session is associated with the first PDU session.
  • the first PDU session is used for transmitting unicast services and/or the first PDU session is also associated with other activated MBS sessions.
  • the first PDU session is a PDU session configured by the terminal device, the first PDU session is used for the MBS, and the first PDU session is also used for unicast services and/or other activated MBS sessions.
  • S1001, S701, S702 and S703 in the fifth embodiment may also be included.
  • the core network notifies the first access network device to modify the first PDU session. Therefore, this embodiment includes steps S1002 and S1003.
  • the first access network device modifies the first PDU session, it replies to the core network device, that is, S1005 is also included.
  • the first access network device sends a fifth message to the core network device, where the fifth message is used to request to delete the information of the MBS session from the first PDU session, or in other words, the fifth message includes the information of the first PDU session.
  • a modification request message which requests to delete the information of the MBS session.
  • the fifth message further includes a cause value of the modification, for example, because the UE wants to switch to a non-MBS base station, MBS related information needs to be released.
  • the first access network device receives a fifth confirmation message corresponding to the fifth message sent by the core network device, where the fifth confirmation message includes modification information of the first PDU session.
  • the method further includes: the core network device modifies the first PDU session.
  • the first access network device deletes the information of the MBS session included in the first PDU session.
  • the first access network device notifies the core network device after modifying the first PDU session. Therefore, this embodiment includes step S1005.
  • the core network device will reply with confirmation information, that is, S1006 is also included.
  • the first access network device sends a modification message of the first PDU session.
  • the core network device receives the modification message of the first PDU session.
  • the core network device sends a modification confirmation message of the first PDU session.
  • the first access network device receives the modification confirmation message of the first PDU session.
  • the first access network device sends handover indication information to the terminal device, where the handover indication information is used to instruct the terminal device to switch the target cell. That is, the first access network device notifies the UE to switch to the cell served by the second access network device, which does not support MBS sessions. Correspondingly, the terminal device receives the handover indication information.
  • the first/second/third/fourth/fifth confirmation message may also be referred to as the first/second/third/fourth/fifth response message or the first/second/third
  • the /fourth/fifth feedback message is the response message or feedback message of the first/second/third/fourth/fifth message.
  • the names of the first/second/third/fourth/fifth confirmation messages are not limited.
  • "release" may also be referred to as "deletion”.
  • the size of the sequence numbers of the above processes does not imply the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic.
  • the various numerical numbers or serial numbers involved in the above processes are only for the convenience of description, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • S704 and S705 are before the RAN handover is completed; if the first message is not a handover request message, the first confirmation message is not a handover request confirmation message, S704 And S705 can be before, during or after the RAN handover is completed.
  • FIG. 11 is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application. It should be noted that the part indicated by the dotted box in FIG. 11 is optional, and will not be described in detail in the following.
  • Communication device 1100 includes one or more processors 1101 .
  • the processor 1101 can be used to perform the internal processing of the device and realize certain control processing functions.
  • processor 1101 includes instructions 1103 .
  • the processor 1101 may store data.
  • the processor 1101 may be a general-purpose processor or a special-purpose processor or the like. For example, including at least one of the following: baseband processor, central processing unit, application processor, modem processor, graphics processor, image signal processor, digital signal processor, video codec processor, controller, and/or Or neural network processors, etc.
  • the different processors may be stand-alone devices or may be integrated in one or more processors, eg, on one or more application specific integrated circuits.
  • the communication device 1100 includes one or more memories 1102 for storing the instructions 1104 .
  • the memory 1102 may also store data.
  • the processor and the memory can be provided separately or integrated together.
  • the communication device 1100 may further include a transceiver 1105 .
  • the transceiver 1105 can be used to send information to or receive information from other devices.
  • the transceiver 1105 may be referred to as a transceiver, a transceiver circuit, an input and output interface, and the like.
  • the communication device 1100 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, an internal memory, a universal serial bus (USB) interface, a power management module, an antenna, Speakers, microphones, I/O modules, sensor modules, motors, cameras, or displays, etc.
  • a wireless communication module an audio module
  • an external memory interface an internal memory
  • a universal serial bus (USB) interface a power management module
  • an antenna a radio frequency division multiplex, etc.
  • Speakers microphones, I/O modules, sensor modules, motors, cameras, or displays, etc.
  • the processor 1101 executes the instructions (sometimes may also be referred to as computer programs or codes) stored by the communication device 1100, that is, the instructions stored in the communication device can be executed on the processor 1101, so that the communication device 1100 executes the above-mentioned embodiments. method described.
  • the instruction is the instruction 1103 in the processor 1101, or the instruction is the instruction 1104 in the memory.
  • the communication apparatus 1100 may be used to implement the method corresponding to the first access network device in the above application embodiment.
  • the communication apparatus 1100 includes a processor 1101, where the processor 1101 is configured to execute a computer program or instructions, so that the method corresponding to the first access network device in the above application embodiments is executed.
  • the processor 1101 may communicate with other network entities through the transceiver 1105, eg, communicate with the second access network device or the core network device.
  • the memory 1102 is used for storing instructions and data of the first access network device.
  • the communication apparatus 1100 may be used to implement the method corresponding to the second access network device in the above application embodiment.
  • the communication apparatus 1100 includes a processor 1101, where the processor 1101 is configured to execute a computer program or an instruction, so that the method corresponding to the second access network device in the above application embodiment is executed.
  • the processor 1101 may communicate with other network entities through the transceiver 1105, for example, with the first access network device or the core network device.
  • the memory 1102 is used for storing instructions and data of the first access network device.
  • the communication apparatus 1100 may be used to implement the method corresponding to the core network device in the above application embodiment.
  • the communication apparatus 1100 includes a processor 1101, where the processor 1101 is configured to execute computer programs or instructions, so that the methods corresponding to the core network equipment in the above application embodiments are executed.
  • the processor 1101 may communicate with other network entities through the transceiver 1105, eg, with the first access network device or the second access network device.
  • the memory 1102 is used to store instructions and data of the core network device.
  • the processor 1101 and transceiver 1105 described in this application may be implemented in integrated circuits (ICs), analog ICs, radio frequency identifications (RFIDs), mixed-signal ICs, application specific integrated circuits (application specific integrated circuits) , ASIC), printed circuit board (printed circuit board, PCB), or electronic equipment, etc.
  • ICs integrated circuits
  • RFIDs radio frequency identifications
  • mixed-signal ICs application specific integrated circuits
  • ASIC application specific integrated circuits
  • PCB printed circuit board
  • electronic equipment etc.
  • it may be an independent device (eg, an independent integrated circuit, a mobile phone, etc.), or may be a part of a larger device (eg, a module that can be embedded in other devices). The description of the core network equipment and the access network equipment will not be repeated here.
  • FIG. 12 is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the apparatus 1200 may include: a processing unit 1202 and a communication unit 1203 .
  • the processing unit 1202 is used to control and manage the actions of the device 1200 .
  • the communication unit 1203 is used to support the communication between the apparatus 1200 and other devices.
  • the communication unit 1203 is also referred to as a transceiving unit, and may include a receiving unit and/or a sending unit, which are respectively configured to perform receiving and sending operations.
  • the apparatus 1200 may further include a storage unit 1201 for storing instructions and/or data of the apparatus 1200 .
  • the communication apparatus 1200 may be used to implement the method corresponding to the first access network device or the second access network device in the above application embodiment.
  • the processing unit 1202 may support the apparatus 1200 to perform the actions of the first access network device or the second access network device in each method example above.
  • the processing unit 1202 mainly executes the internal actions of the first access network device or the second access network device in the method example, and the communication unit 1203 may support communication between the apparatus 1200 and other devices.
  • the support apparatus 1200 communicates with the second access network device or the core network device, or the support apparatus 1200 communicates with the first access network device or the core network device.
  • the communication apparatus 1200 may be used to implement the method corresponding to the core network device in the above application embodiment.
  • the processing unit 1202 may support the apparatus 1200 to perform the actions of the core network device in each method example above.
  • the processing unit 1202 mainly performs the internal actions of the core network device in the method example, and the communication unit 1203 may support the communication between the apparatus 1200 and other devices.
  • the support apparatus 1200 communicates with the first access network device or the second access network device.
  • FIG. 13 is a simplified schematic structural diagram of an access network device provided by an embodiment of the present application, which may be, for example, a simplified structural schematic diagram of a base station.
  • the access network device 1300 can be applied to the first access network device or the second access network device in the foregoing embodiments, and performs the operations of the first access network device or the second access network device in the foregoing method embodiments or For details, refer to the descriptions in the foregoing method embodiments, and details are not repeated here.
  • the access network device 1300 includes: a processor 1311 , a memory 1312 , a radio frequency unit 1321 and an antenna 1322 .
  • the processor 1311 is also called a processing unit, and is configured to support executing the functions of the first access network device or the second access network device in the foregoing method embodiments.
  • the processor 1311 may be one or more processors.
  • the one or more processors may support radio access technologies of the same standard, or may support radio access technologies of different standards (eg, LTE and NR).
  • the processor 1311 is an integrated circuit, such as one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form chips.
  • Memory 1312 also referred to as a storage unit, stores instructions (which may also sometimes be referred to as computer programs or code) and/or data.
  • the memory 1312 may be one memory, or may be a collective term for multiple memories or storage elements.
  • the memory 1312 and the processor 1311 may be located in the same chip or on different chips.
  • the radio frequency unit 1321 may be one or more radio frequency units.
  • the antenna 1322 is mainly used to send and receive radio frequency signals in the form of electromagnetic waves, for example, for the access network device 1300 to send or receive signals to terminal devices.
  • the access network device 1300 further includes: a communication unit, where the communication unit is used to support communication between the access network device 1300 and other devices.
  • the communication unit is configured to support the access network device 1300 to communicate with the second access network device or the core network device.
  • the communication unit is used to support the access network device 1300 to communicate with the first access network device or the core network device.
  • the communication unit may include a receiving unit and/or a sending unit for performing receiving and sending operations, respectively.
  • the baseband unit 1310 (baseband unit, BBU) includes a processor 1311 and a memory 1312, and is mainly used for baseband processing of signals, managing wireless resources, providing transmission management and interfaces, and providing functions such as clock signals.
  • the BBU 2100 can be composed of one or more single boards, and multiple single boards can jointly support a wireless access network (such as an LTE network) of a single access standard, or can respectively support wireless access systems of different access standards. Access network (such as LTE network, 5G network or other network).
  • the memory 1312 and processor 1311 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.
  • the BBU 1310 may be configured to perform the actions described in the foregoing method embodiments that are implemented internally by the first access network device or the second access network device.
  • the radio frequency unit 1321 is a remote radio unit (remote radio unit, RRU), and the RRU and the BBU may be physically set together, or may be physically set apart, that is, a distributed base station.
  • RRU remote radio unit
  • the unit 1320 may be an active antenna unit (Active Antenna Unit, AAU), which is a hardware product that integrates a radio frequency function with an antenna.
  • AAU Active Antenna Unit
  • the radio frequency unit 1321 in the AAU refers to a radio frequency module dedicated to the AAU, and has the same function as the RRU.
  • the AAU may also include part of the baseband processing function.
  • the core network device may be a device with an AMF function, or a device with an AMF function and a UPF function, or the core network device may be A device with AMF function and SMF function, or the core network device may be a device with AMF function, UPF function and SMF function.
  • the core network device 1400 may include a processor 1401 , a memory 1402 and an interface circuit 1403 .
  • the processor 1401 can be used to process the communication protocol and communication data, and control the communication device.
  • the memory 1402 may be used to store programs and data, and the processor 1401 may execute the method executed by the core network device in this embodiment of the present application based on the program.
  • the interface circuit 1403 can be used for the core network device 1400 to communicate with other devices, and the communication can be wired communication or wireless communication.
  • the interface circuit can be a service-oriented communication interface.
  • the above memory 1402 may also be externally connected to the core network device 1400 .
  • the core network device 1400 may include an interface circuit 1403 and a processor 1401 .
  • the above interface circuit 1403 may also be externally connected to the core network device 1400 .
  • the core network device 1400 may include a memory 1402 and a processor 1401 .
  • the communication device 1400 may include a processor 1401 .
  • the core network device shown in FIG. 14 can implement each process involving the core network device in the foregoing embodiment.
  • the operations and/or functions of each module in the core network device shown in FIG. 14 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • the terminal device and/or the network device may perform some or all of the steps in the embodiments of the present application, these steps or operations are only examples, and the embodiments of the present application may also perform other operations or various Variation of operations.
  • various steps may be performed in different orders presented in the embodiments of the present application, and may not be required to perform all the operations in the embodiments of the present application.
  • the present application also provides a computer-readable storage medium, where a computer program or instruction is stored, and when the computer program or instruction is executed, the first access network device, A method performed by a second access network device or core network device.
  • the present application also provides a computer program product comprising a computer program or instruction, when the computer program or instruction is run on a computer, the computer is made to perform any of the foregoing method embodiments by the first access network device, the second access network device, the second access network device A method performed by a network access device or a core network device.
  • the computer program or instruction when executed, it causes the computer to execute the method executed by the first access network device in the foregoing embodiment; or, when the computer program or instruction is executed by the first access network device When running, the computer is made to execute the method executed by the second access network device in the foregoing embodiment; or, when the computer program or instruction is executed, the computer is made to execute the method executed by the core network device in the foregoing embodiment.
  • the computer-readable storage medium or the computer program product includes: an instruction for implementing receiving a first message from a first access network device and sending a first confirmation message to the first access network device; An instruction for implementing sending the second message to the core network device and receiving the second acknowledgment message from the core network device; and/or an instruction for implementing the sending of the fourth message to the core network device and receiving the fourth acknowledgment message from the core network device instruction.
  • the computer-readable storage medium or the computer program product includes: instructions for implementing sending the first message to the second access network device and receiving the first confirmation message from the second access network device; an instruction for receiving the third information and saving the MBS state information in the context of the MBS and/or the terminal device; and/or, for determining that the state of the MBS session is deactivated, and sending the third message to the core network device Five message instructions.
  • the computer-readable storage medium or the computer program product includes: an instruction for implementing receiving a second message from a second access network device and sending a second confirmation message to the second access network device; Implementing an instruction to receive a fourth message from the second access network device and send a fourth confirmation message to the second access network device; for implementing the determination of the first state of the MBS session and sending the first state to the first access network device and/or, an instruction for implementing receiving a fifth message from the first access network device.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes, magnetic disks), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state drives). disc, SSD)) etc.
  • magnetic media eg, floppy disks, hard disks, magnetic tapes, magnetic disks
  • optical media eg, high-density digital video discs (DVDs)
  • semiconductor media eg, solid state drives). disc, SSD
  • An embodiment of the present application further provides a processing apparatus, including a processor and an interface; the processor is configured to execute the method executed by the terminal device or the network device involved in any of the foregoing method embodiments.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the division of this unit is only for one logical function division.
  • multiple units or components may be combined or integrated into another system, or some features may be ignored or not implement.
  • the shown or discussed mutual coupling, or direct coupling, or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • the ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of multiple objects. degree, etc.
  • the configuration information of the first signal and the configuration information of the second signal may be the same configuration information or different configuration information, and this name does not indicate the information size, content, priority, or importance.
  • At least one refers to one or more, and "a plurality” refers to two or more.
  • At least one item(s) or similar expressions, refers to one item(s) or multiple item(s), ie any combination of these items, including any combination of single item(s) or plural item(s).
  • at least one (a) of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c.
  • an item includes one or more of the following: A, B, and C
  • a total of three elements of A, B and C are used as examples above to illustrate the optional items of the item.
  • B corresponding to A indicates that B is associated with A, and B can be determined according to A.
  • determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.

Landscapes

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

Abstract

本申请提供了一种通信方法和通信装置，第二接入网设备从第一接入网设备接收第一消息，其中，所述第一消息指示MBS会话的第一状态为激活或去激活；第二接入网设备向所述第一接入网设备发送所述第一消息对应的第一确认消息。该方案中，第一消息用于指示MBS会话的第一状态，第二接入网设备可以根据该第一状态确定是否向核心网请求建立UP隧道。若该MBS会话的第一状态为激活，第二接入网设备可以触发新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的第一状态为去激活，第二接入网设备可以不触发新建UP隧道或者请求新建挂起的UP隧道，避免资源浪费问题。

Description

一种通信方法及通信装置
本申请要求在2021年04月30日提交国家专利局、申请号为202110484672.4、发明名称为“一种通信方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法和通信装置。
背景技术
多播广播业务(multicast and broadcast service，MBS)是接入网设备向多个终端设备传输的业务，常见的MBS包括直播业务，公共安全业务，批量软件更新业务等。MBS数据来自数据服务器，经由核心网设备发送到接入网设备，再由接入网设备发送给至少一个终端设备。
终端设备在移动过程中，随着各小区信号强度的变化，为了防止由于小区的信号质量变差造成的通信质量下降，需要从第一小区切换到第二小区，其中，第一小区由源接入网设备提供服务，第二小区由目标接入网设备提供服务。源接入网设备支持多播广播传输方式且为该终端设备提供MBS，但是当目标接入网设备没有该终端设备所需的MBS时，或者当目标接入网设备不支持多播广播传输方式时，如何保证切换过程中MBS数据的传输是一个亟待解决的问题。
发明内容
本申请实施例提供的通信方法和装置，能够保证切换过程中MBS的正常传输以及避免不必要的资源浪费。
第一方面，提供了一种通信方法，该方法可以由第二接入网设备或者第二接入网设备中的芯片执行。该方法包括：从第一接入网设备接收第一消息，其中，所述第一消息指示MBS会话的第一状态为激活或去激活；向所述第一接入网设备发送所述第一消息对应的第一确认消息。该方案中，第一消息用于指示MBS会话的第一状态，第二接入网设备可以根据该第一状态确定是否向核心网请求建立UP隧道。若该MBS会话的第一状态为激活，第二接入网设备可以触发新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的第一状态为去激活，第二接入网设备可以不触发新建UP隧道或者请求新建挂起的UP隧道，避免资源浪费问题。
结合第一方面，第一消息指示多播广播业务MBS会话的第一状态为激活，该方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道；或者，第一消息指示多播广播业务MBS会话的第一状态为去激活，该方法还包括：确定当前无需建立所述MBS会话对应的用户面隧道；或者，第一消息指示多播广播业务MBS会话的第一状态为去激活，该方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道，所述用户面隧道被挂起。
可选地，第一消息为切换请求消息，第一确认消息为切换请求确认消息。
可选地，第一消息包含第一状态信息，所述第一状态信息指示所述第一状态为激活或去激活；或者，第一消息通过是否包含第一状态信息指示所述第一状态为激活或去激活。
第二方面，提供了一种通信方法，该方法可以由第一接入网设备或者第一接入网设备中的芯片执行。该方法包括：向第二接入网设备发送第一消息，其中，所述第一消息指示MBS会话的第一状态为激活或去激活；从所述第二接入网设备接收所述第一消息对应的第一确认消息。该方案中可以保证切换过程中MBS的正常传输以及避免资源浪费问题。
可选地，第一消息为切换请求消息，第一确认消息为切换请求确认消息。
结合第二方面，向第二接入网设备发送第一消息之前，还包括：接收核心网设备发送的第三信息，所述第三信息指示所述MBS会话的第一状态。
可选地，所述第三信息为所述MBS会话更改消息中包含的信息；或者，所述第三信息为PDU会话更改消息中包含的信息，其中，所述PDU会话与所述MBS会话关联；或者，所述第三信息为所述MBS业务的数据包的包头中的一个信息域中的信息。
第三方面，提供了一种通信方法，该方法可以由第二接入网设备或者第二接入网设备中的芯片执行。该方法包括：向核心网设备发送第二消息；从所述核心网设备接收所述第二消息对应的第二确认消息；其中，所述第二消息指示所述MBS会话的第一状态为激活或去激活；和/或，所述第二确认消息指示所述MBS会话的第二状态为激活或去激活。MBS会话的状态为第一状态或第二状态，其中，第一状态为终端设备被切换前所述MBS会话的状态，第二状态为终端设备被切换后所述MBS会话的状态，所述MBS为所述终端设备感兴趣或正在接收的MBS。通过第二消息和/或第二确认消息，第二接入网设备可以获知MBS会话的状态，若该MBS会话的状态为激活，第二接入网设备可以触发新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的状态为去激活，第二接入网设备可以不触发新建UP隧道或者请求新建挂起的UP隧道，避免资源浪费问题。另一方面，在切换过程中，MBS会话的状态可能发生变化，该方案可以避免由于MBS会话状态发生变化而引起的行为不匹配的问题。
结合第三方面，所述MBS会话的状态为激活，该方法还包括：向核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道；或者，所述MBS会话的状态为去激活，该方法还包括：确定当前无需建立所述MBS会话对应的用户面隧道；或者，所述MBS会话的状态为去激活，该方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道，所述用户面隧道被挂起。
结合第三方面，从核心网设备接收第二确认消息后，还包括：确定MBS会话的状态为第二状态。可选地，第一状态为激活，第二状态为去激活，确定所述MBS会话的状态为去激活。
可选地，所述第二消息为路径切换请求消息，所述第二确认消息为路径切换请求确认消息。
可选地，第二消息包含第一状态信息，该第一状态信息指示第一状态为激活或去激活；或者，第二消息通过是否包含第一状态信息指示来指示所述第一状态。
可选地，第二确认消息包含第二状态信息，该第二状态信息指示第二状态为激活或去激活；或者，第二确认消息通过是否包含第二状态信息来指示第二状态。
第四方面，提供了一种通信方法，该方法可以由核心网设备或者核心网设备中的芯片执行。该方法包括：从第二接入网设备接收第二消息；向所述第二接入网设备发送所述第二消息对应的第二确认消息；其中，所述第二消息指示所述MBS会话的第一状态为激活或去激活；和/或，所述第二确认消息指示所述MBS会话的第二状态为激活或去激活。通过该方案，可以保证切换过程中MBS的正常传输，避免资源浪费问题，另外，还可以避免切换过程中MBS会话状态发生变化而引起的行为不匹配的问题。
结合第四方面，所述MBS会话的状态为激活，该方法还包括：从第二接入网设备接收第 一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道；或者，所述MBS会话的状态为去激活，该方法还包括：确定当前无需建立所述MBS会话对应的用户面隧道；或者，所述MBS会话的状态为去激活，该方法还包括：从第二接入网设备接收第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道，所述用户面隧道被挂起。
第五方面，提供了一种通信方法，该方法可以由第二接入网设备或者第二接入网设备中的芯片执行。该方法包括：向核心网设备发送第四消息，所述第四消息用于请求建立MBS会话对应的用户面隧道；从所述核心网设备接收所述第四消息对应的第四确认消息，所述第四确认消息指示所述MBS会话的状态为激活或去激活。该方案中，第二接入网设备可以根据第四确认消息来获知核心网设备对UP隧道的管理。若该MBS会话的第一状态为激活，第二接入网设备可以触发新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的第一状态为去激活，第二接入网设备可以不触发新建UP隧道或者挂起新建的UP隧道，避免资源浪费。
可选地，所述第四确认消息包括建立所述用户面隧道的信息以及指示所述MBS会话的状态为激活；或者，所述第四确认消息包括拒绝建立所述用户面隧道的信息；或者，所述第四确认消息包括建立所述用户面隧道的信息以及指示所述MBS会话的状为去激活。
第六方面，提供了一种通信方法，该方法可以由核心网设备或者核心网设备中的芯片执行。该方法包括：从第二接入网设备接收第四消息，所述第四消息用于请求建立MBS会话对应的用户面隧道；向所述第二接入网设备发送所述第四消息对应的的第四确认消息，所述第四确认消息指示所述MBS会话的第二状态为激活或去激活。该方案中，第二接入网设备可以根据第四确认消息来获知核心网设备对UP隧道的管理，保证切换过程中MBS的正常传输和避免资源浪费。
第七方面，提供了一种通信方法，该方法可以由核心网设备或者核心网设备中的芯片执行。该方法包括：确定MBS会话的第一状态；向第一接入网设备发送第三信息，所述第三信息指示所述MBS会话的第一状态。该方案可以应用于切换之前，让第一接入网设备获知MBS会话的状态，进而明确MBS传输的操作，保障后续切换后MBS的正常传输。
可选地，所述第三信息为所述MBS会话更改消息中包含的信息；或者，所述第三信息为第一PDU会话更改消息或建立消息中包含的信息，其中，所述第一PDU会话与所述MBS会话关联；或者，所述第三信息为所述MBS业务的数据包的包头中的一个信息域中的信息。
第八方面，提供了一种通信方法，该方法可以由第一接入网设备或者第一接入网设备中的芯片执行。该方法包括：接收第三信息，其中，第三信息指示所述MBS会话的第一状态；将MBS状态信息保存于MBS上文中和/或终端设备的上下文中。该方案可以应用于切换之前，第一接入网设备根据第三信息获知MBS会话的状态，进而明确MBS传输的操作，且保障后续切换后MBS的正常传输。
第九方面，提供了一种通信方法，该方法可以由第一接入网设备或者第一接入网设备中的芯片执行。该方法包括：确定MBS会话的状态为去激活，所述MBS会话关联第一PDU会话；向核心网设备发送第五消息，所述第五消息用于请求释放所述第一PDU会话，其中，所述第一PDU会话仅用于所述MBS会话；或者，向核心网设备发送第五消息，所述第五消息用于请求将所述MBS会话的信息从所述第一PDU会话中删除，其中，所述第一PDU会话用于传输单播业务，和/或，所述第一PDU会话还关联其它激活的MBS会话。通过该方案，可以避免新建的UP隧道还未使用就被删除造成的资源浪费。
在一种实现方式中，所述第五消息用于请求释放所述第一PDU会话，所述方法还包括：释放所述终端设备的RRC连接。
在另一种实现方式中，所述第五消息用于请求将所述MBS会话的信息从所述第一PDU会话中删除，所述方法还包括：向终端设备发送切换指示信息，所述切换指示信息用于指示所述终端设备切换目标小区，所述目标小区不支持MBS会话。其中，所述第一接入网设备为为终端设备服务的源接入网设备。
第十方面，提供了一种通信方法，该方法可以由核心网设备或者核心网设备中的芯片执行。该方法包括：从第一接入网设备接收第五消息，所述第五消息用于请求释放第一PDU会话，其中，所述第一PDU会话仅用于所述MBS会话；或者，从第一接入网设备接收第五消息，所述第五消息用于请求将所述MBS会话的信息从第一PDU会话中删除，其中，所述第一PDU会话用于传输单播业务，和/或，所述第一PDU会话还关联其它激活的MBS会话。其中，MBS会话的状态为去激活，所述MBS会话关联所述第一PDU会话。
第十一方面，提供了一种通信系统，该通信系统可以包括第一接入网设备和第二接入网设备。其中，所述第二接入网设备可以用于执行第一方面的任一种可能实现方式中的方法，所述第一接入网设备可以用于执行第二方面的任一种可能实现方式中的方法。
第十二方面，提供了一种通信系统，该通信系统可以包括第二接入网设备和核心网设备。其中，所述第二接入网设备可以用于执行第三方面的任一种可能实现方式中的方法，所述核心网设备可以用于执行第四方面的任一种可能实现方式中的方法；或者，所述第二接入网设备可以用于执行第五方面的任一种可能实现方式中的方法，所述核心网设备可以用于执行第六方面的任一种可能实现方式中的方法。
第十三方面，提供了一种通信系统，该通信系统可以包括第一接入网设备和核心网设备。其中，所述第一接入网设备可以用于执行第八方面的任一种可能实现方式中的方法，所述核心网设备可以用于执行第七方面的任一种可能实现方式中的方法；或者，所述第一接入网设备可以用于执行第九方面的任一种可能实现方式中的方法，所述核心网设备可以用于执行第十方面的任一种可能实现方式中的方法。
第十四方面，提供了一种通信系统，该通信系统可以包括第一接入网设备，第二接入网设备和核心网设备。其中，所述第二接入网设备可以用于执行第一方面，第三方面，和/或，第五方面的任一种可能实现方式中的方法，所述第一接入网设备可以用于执行第二方面，和/或，第八方面的任一种可能实现方式中的方法，所述核心网设备可以用于执行第四方面，第六方面，和/或，第七方面的任一种可能实现方式中的方法。
第十五方面，提供了一种通信装置，包括用于执行上述第一方面，第三方面，或，第五方面的任一种可能实现方式中的方法的各个模块或单元。
第十六方面，提供了一种通信装置，包括用于执行上述第二方面，第八方面，或，第九方面的任一种可能实现方式中的方法的各个模块或单元。
第十七方面，提供了一种通信装置，包括用于执行上述第四方面，第六方面，第七方面，或，第十方面的任一种可能实现方式中的方法的各个模块或单元。
第十八方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以使得该通信装置执行上述第一方面，第三方面，或，第五方面的任一种可能实现方式中的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括收发器和/或天线。可选地，该通信装置可以为第二接入网设备或配置于第二接入网设备中的芯片。
第十九方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以使得该通信装置执行上述第二方面，第八方面，或，第九方面的任一种可能实现方式中的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括收发器和/或天线。可选地，该通信装置可以为第一接入网设备或配置于第一接入网设备中的芯片。
第二十方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以使得该通信装置执行上述第四方面，第六方面，第七方面，或，第十方面的任一种可能实现方式中的方法。可选地，该通信装置还包括存储器。可选地，该通信装置可以为核心网设备或配置于核心网设备中的芯片。
第二十一方面，提供了一种接入网设备，该接入网设备可以实现上述第一方面，第三方面，或，第五方面的任一种可能实现方式中的方法，或者，该接入网设备可以实现上述第二方面，第八方面，或，第九方面的任一种可能实现方式中的方法。可选地，所述接入网设备可以是芯片(如基带芯片，或通信芯片等)或者基站设备，可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
在一种可能的实现方式中，所述接入网设备包括处理器和存储器。所述处理器用于支持接入网设备执行上述第一方面，第三方面，或，第五方面的任一种可能实现方式中的方法；或者，所述处理器用于支持接入网设备执行上述第二方面，第八方面，或，第九方面的任一种可能实现方式中的方法。所述存储器用于存储指令和/或数据。可选地，所述接入网设备还包括射频单元和天线。
在另一种可能的实现方式中，所述接入网设备包括基带单元和收发单元。所述基带单元用于执行上述第一方面，第三方面，或，第五方面的任一种可能实现方法中的由接入网设备内部实现的动作，或者，所述基带单元用于执行上述第二方面，第八方面，或，第九方面的任一种可能实现方法中的由接入网设备内部实现的动作。所述收发单元用于执行接入网设备向外部发送或从外部接收的动作。
在又一种可能的实现方式中，所述接入网设备包括处理器和收发器。所述处理器用于支持接入网设备执行上述第一方面，第三方面，或，第五方面的任一种可能实现方式中的方法，或者，所述处理器用于支持接入网设备执行上述第二方面，第八方面，或，第九方面的任一种可能实现方式中的方法。当所述接入网设备为芯片时，收发器可以是输入输出单元，比如输入输出电路或者输入输出接口。
在又一种可能的实现方式中，所述接入网设备可以包括执行上述第一方面，第三方面，或，第五方面的任一种可能实现方法中的相应动作的单元模块，或者，所述接入网设备可以包括执行上述第二方面，第八方面，或，第九方面的任一种可能实现方法中的相应动作的单元模块。
第二十二方面，提供了一种核心网设备，该核心网设备可以实现上述第四方面，第六方面，第七方面，或，第十方面的任一种可能实现方式中的方法。可选地，所述核心网设备可以是芯片(如基带芯片，或通信芯片等)或者核心网设备，可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
在一种可能的实现方式中，所述核心网设备包括处理器和存储器。所述处理器用于支持核心网设备执行上述第四方面，第六方面，第七方面，或，第十方面的任一种可能实现方式中的方法。所述存储器用于存储指令和/或数据。
在另一种可能的实现方式中，所述核心网设备包括处理器和接口电路，其中，处理器用 于通过所述接口电路与其它装置通信，并执行上述第四方面，第六方面，第七方面，或，第十方面的任一种可能实现方式中的方法。
在又一种可能的设计中，所述核心网设备包括处理单元，其中，处理单元可以用于执行该核心网设备的一些内部操作。处理单元执行的功能可以和上述第四方面，第六方面，第七方面，或，第十方面涉及的操作相对应。
在又一种可能的实现方式中，所述核心网设备可以包括执行上述第四方面，第六方面，第七方面，或，第十方面的任一种可能实现方法中的相应动作的单元模块。
第二十三方面，提供了一种计算机可读存储介质，存储有计算机程序或指令，当该计算机程序或指令被运行时，实现上述第一方面，第三方面，或，第五方面的任一种可能实现方式中的方法。
第二十四方面，提供了一种计算机可读存储介质，存储有计算机程序或指令，当该计算机程序或指令被运行时，实现上述第二方面，第八方面，或，第九方面的任一种可能实现方式中的方法。
第二十五方面，提供了一种计算机可读存储介质，存储有计算机程序或指令，当该计算机程序或指令被运行时，实现上述第四方面，第六方面，第七方面，或，第十方面的任一种可能实现方式中的方法。
第二十六方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。该处理电路用于通过该输入电路接收信号，并通过该输出电路发射信号，使得该处理器执行上述任一方面或该方面中任一种可能实现方式中的方法。可选地，上述处理器为芯片，输入电路为输入管脚，输出电路为输出管脚，处理电路为晶体管、门电路、触发器和/或各种逻辑电路等。
第二十七方面，提供了一种包含计算机程序或指令的计算机程序产品，当该计算机程序或指令被运行时，使得计算机执行上述第一方面，第三方面，或，第五方面中任一种可能实现方式中的方法。
第二十八方面，提供了一种包含计算机程序或指令的计算机程序产品，当该计算机程序或指令被运行时，使得计算机执行上述第二方面，第八方面，或，第九方面中任一种可能实现方式中的方法。
第二十九方面，提供了一种包含计算机程序或指令的计算机程序产品，当该计算机程序或指令被运行时，使得计算机执行上述第四方面，第六方面，第七方面，或，第十方面中任一种可能实现方式中的方法。
附图说明
图1为本申请的通信系统的示意图；
图2为本申请提供的一种切换流程示意图；
图3A为本申请提供的一种切换场景示意图；
图3B为本申请提供的又一种切换场景示意图；
图4为本申请提供的一种通信方法的流程图；
图5为本申请提供的又一种通信方法的流程图；
图6为本申请提供的又一种通信方法的流程图；
图7为本申请提供的又一种通信方法的流程图；
图8为本申请提供的又一种通信方法的流程图；
图9为本申请提供的又一种通信方法的流程图；
图10为本申请提供的又一种通信方法的流程图；
图11为本申请提供的通信装置的示意性结构图；
图12为本申请提供的通信装置的示意性结构图；
图13为本申请提供的接入网设备的示意性结构图；
图14为本申请提供的核心网设备的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提供的方法和装置可应用于各种通信系统，例如，长期演进(long term evolution，LTE)系统，第五代(5th generation，5G)系统，新无线(new radio，NR)系统，无线保真(wireless-fidelity，WiFi)系统，第三代合作伙伴计划(3rd generation partnership project，3GPP)相关的通信系统，未来可能出现的其他通信系统或多种通信融合系统。4G系统的核心网可以称为演进分组核心网(evolved packet core，EPC)，接入网可以称为长期演进(long term evolution，LTE)。5G系统的核心网可以称为5GC(5G core)，接入网可以称为新无线。为了方便描述，本申请以5G系统为例说明，但是可以理解的是，本申请同样适用于4G系统等。本申请中的通信系统包括接入网设备，核心网设备和终端设备，下面分别说明。
接入网设备是一种具有无线收发功能的网络侧设备。接入网设备可以为无线接入网(radio access network，RAN)中为终端设备提供无线通信功能的装置，因此，也可以称为RAN设备。例如，该接入网设备可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、发送接收点(transmission reception point，TRP)、3GPP后续演进的基站、WiFi系统中的接入节点、无线中继节点、无线回传节点等。在采用不同的无线接入技术(radio access technology，RAT)的通信系统中，具备基站功能的设备的名称可能会有所不同。例如，LTE系统中可以称为eNB或eNodeB，5G系统或NR系统中可以称为gNB，本申请对基站的具体名称不作限定。接入网设备可以包含一个或多个共站址或非共站址的发送接收点。再如，接入网设备可以包括一个或多个集中式单元(central unit，CU)、一个或多个分布式单元(distributed unit，DU)、或一个或多个CU和一个或多个DU。示例性地，CU的功能可以由一个实体或者不同的实体来实现。例如，CU的功能进行进一步切分，即将控制面和用户面分离并通过不同实体来实现，分别为控制面CU实体(即CU-CP实体)和用户面CU实体(即CU-UP实体)，CU-CP实体和CU-UP实体可以与DU相耦合，共同完成接入网设备的功能。这样可以通过多个网络功能实体来实现无线接入网设备的部分功能。这些网路功能实体可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。又如，车到一切(vehicle to everything，V2X)技术中，接入网设备可以为路侧单元(road side unit，RSU)。通信系统中的多个接入网设备可以为同一类型的基站，也可以为不同类型的基站。基站可以与终端设备进行通信，也可以通过中继站与终端设备进行通信。本申请实施例中，用于实现接入网设备功能的装置可以是接入网设备本身，也可以是能够支持接入网设备实现该功能的装置，例如芯片系统或可实现接入网设备功能的组合器件、部件，该装置可以被安装在接入网设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例中，以接入网设备为例，描述技术方案。
核心网设备用于实现移动管理，数据处理，会话管理，策略和计费等功能。不同接入技术的系统中实现核心网功能的设备名称可以不同，本申请并不对此进行限定。以5G网络为 例，5GC的逻辑网元包括：访问和移动管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、或用户面功能(user plane function，UPF)等。AMF是一种用于对终端设备进行接入和移动性管理的网元，主要涉及终端设备的位置更新、网络注册、切换控制等功能。SMF是一种用于对终端设备的会话进行管理的网元，主要涉及会话建立、修改和释放等功能。UPF是一种用于对用户的数据进行接收和转发的网元。UPF受SMF的控制。5GC的不同逻辑网元可以部署在相同或者不同的物理设备上。例如，可以将AMF和SMF部署在同一个物理设备上，也可以部署在两个物理设备上。另外，5GC的逻辑网元可以和4G核心网的网元部署在同一物理设备上。用于实现核心网设备的功能的装置可以是核心网设备，也可以是能够支持核心网设备实现该功能的装置，例如芯片系统或可实现核心网设备功能的组合器件、部件，该装置可以被安装在核心网设备中。在本申请实施例中，以核心网设备为例，描述技术方案。
终端设备是一种具有无线收发功能的用户侧设备，可以是固定设备，移动设备、手持设备(例如手机)、可穿戴设备、车载设备，或内置于上述设备中的无线装置(例如，通信模块，调制解调器，或芯片系统等)。终端设备用于连接人，物，机器等，可广泛用于各种场景，例如：蜂窝通信、设备到设备(device-to-device，D2D)通信、V2X通信中的、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)通信、物联网(internet of things，IoT)、虚拟现实(virtual reality，VR)、增强现实(augmented reality，AR)、工业控制(industrial control)、无人驾驶(self driving)、远程医疗(remote medical)、智能电网(smart grid)、智能家具、智能办公、智能穿戴、智能交通，智慧城市(smart city)、无人机、机器人等场景。示例性的，终端设备可以是蜂窝通信中的手持终端，D2D中的通信设备，MTC中的物联设备，智能交通和智慧城市中的监控摄像头，或，无人机上的通信设备等。终端设备有时可称为用户设备(user equipment，UE)、用户终端、用户装置、用户单元、用户站、终端、接入终端、接入站、UE站、远方站、移动设备或无线通信设备等等。本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或可实现终端设备功能的组合器件、部件，该装置可以被安装在终端设备中。本申请实施例中，以终端设备为例，描述技术方案。
图1为适用于本申请的一种通信系统示意图。该通信系统100中包括：核心网设备110、第一接入网设备120、第二接入网设备130、终端设备140。
核心网设备110接收来自服务器的MBS，并向接入网设备(第一接入网设备120或者第二接入网设备130)发送该MBS。
第一接入网设备120可以称为源接入网设备，例如源gNB(source gNB)。相应地，第一接入网设备120提供服务的第一小区，可以称为源小区。在终端设备140进行小区切换之前，该第一接入网设备120为该终端设备140提供网络服务。例如，在小区切换之前，第一接入网设备120用于接收来自核心网设备110的MBS，并向终端设备140发送该MBS。
第二接入网设备130可以称为目标接入网设备，例如目标gNB(target gNB)。相应地，第二小区由第二接入网设备130提供服务，可以称为目标小区。在终端设备140进行小区切换之后，第二接入网设备为终端设备140提供网络服务。例如，在小区切换之后，第二接入网设备130用于接收来自核心网设备110的MBS，并向终端设备140发送该MBS。
终端设备140用于与接入网设备通信，接收来自接入网设备的数据，或者向接入网设备发送数据。例如，终端设备140用于接收来自接入网设备的MBS。终端设备在移动过程中，随着各小区信号强度的变化，为了防止由于小区的信号质量变差造成的通信质量下降，需要 从第一小区切换到第二小区。如图1所示，终端设备正在远离当前接入的第一小区。当第一接入网设备向该终端设备发送的信号的强度降低到一定值的情况下，如果终端设备继续驻留在第一小区，由第一接入网设备提供服务，将会导致通信质量下降，业务无法正常传输，甚至掉线等情况。为了保证终端设备的正常通信，若终端设备确定第二小区的信号强度大于第一小区的信号强度，则终端设备需要向第一接入网设备上报该事件，以触发第一接入网设备发起切换流程，将终端设备从第一小区切换到第二小区。
为了便于理解，首先对本申请中涉及的一些术语进行说明。为描述方便，后续本申请中将终端设备以UE为例进行说明。
一、多播广播业务(multicast and broadcast service，MBS)：MBS是面向多个UE传输的业务，例如，直播业务，公共安全业务，批量软件更新业务等。MBS也可以称为多媒体广播多播业务(multimedia broadcast multicast service，MBMS)。MBS的描述信息包括一个或多个MBS流的描述信息，其中，MBS流的描述信息包括下列至少一项：该MBS流的服务质量标识(QoS flow identifier，QFI)、MBS流的特征信息、MBS流的服务质量(quality of service，QoS)需求。MBS流的数据包可以用QoS流标识序列号(QFI sequence number,QFI SN)或用户面通用分组无线业务(general packet radio service，GPRS)隧道协议用户面(GPRS Tunneling Protocol user plane，GTP-U)序列号(GTP-U sequence number，GTP-U SN)标识。
二、单播：在核心网层面，单播是指通过协议数据单元(protocol data unit，PDU)会话向UE发送业务数据。MBS的单播方式指通过PDU会话向UE发送MBS数据，或者说通过UE级别的用户面隧道向UE发送MBS数据，可以称作5GC单独多播广播业务流量传送方式(5G core individual MBS traffic delivery method)，后续可以简称为单播方式。单播业务为面向单个UE的业务。单播传输方式(point-to-point，PTP)，主要是空口侧数据包的传输方式是面向单个UE。
三、多播/广播：在核心网层面，多播/广播是指通过多播/广播会话向终端设备发送MBS的数据，或者说通过共享的用户面隧道向UE发送MBS数据，也可以称作5GC共享多播广播业务流量传送方式(5G core shared MBS traffic delivery method)，后续可以简称为多播广播方式。
四、协议数据单元会话(protocol data unit session，PDU session)：PDU会话为UE与数据网络(data network，DN)之间提供数据连通性。因此，UE发送数据流量之前，应当先建立PDU会话。由UE发起创建，核心网接受UE的请求并分配相应的控制面和用户面资源后，UE才可以与DN之间传输数据。PDU会话为UE级别的，也就是说某一个PDU会话只用于某一个UE。一个PDU会话建立后，也就是建立了一条PDU会话隧道。UE向核心网请求创建PDU会话，核心网可以根据其业务需求创建一个或多个PDU会话。
五、多播广播会话(MBS session)：MBS会话用于传输MBS业务。核心网设备与接入网设备之间可以通过公共的传输通道MBS会话传输MBS。每个MBS会话中包括至少一个MBS服务质量(quality of service，QoS)流(flow)。与PDU会话不同的是，MBS会话是面向多个UE的。对于一个通过MBS会话传输MBS业务的UE而言，还存在一个与该MBS会话关联的PDU会话。该PDU会话中包括：该MBS业务的QoS流以及MBS ID。也就是说MBS业务的QoS流以及MBS ID存在于UE上下文中。对于与该MBS会话关联的PDU会话可以是以下任意一项：PDU会话仅包含该MBS的QoS流；PDU会话仅包含多个MBS的QoS流，其中一个是该MBS的QoS流；或者，PDU会话包含单播业务的QoS流和该MBS的QoS流。MBS会话的状态包括激活(activation)和去激活(deactivation)，由核心网触发 和管理。无论激活还是去激活状态下，PDU会话中包括的MBS信息(QoS流以及MBS ID)仍然可以保存于UE上下文中，这样避免在激活和去激活的MBS会话状态变化中需要多次修改来增加和删除MBS信息。
六、用户面隧道(user plane tunnel，UP tunnel)：也就是GPRS隧道协议用户面(GPRS Tunneling Protocol user plane，GTP-U)隧道，用于核心网的UPF网元与接入网设备之间进行数据传输。激活状态下，可以通过MBS会话对应的UP隧道传输MBS。去激活状态下，MBS会话对应的UP隧道会被删除，当MBS会话再次被激活时，可重建MBS会话对应的隧道。
图2为一种切换(handover，HO)流程示意图。下面结合图2对切换流程进行简单描述。
在S201之前，UE接入到第一接入网设备。示例性地，UE驻留在第一小区，并进入无线资源控制(radio resource control，RRC)连接态。核心网设备向第一接入网设备发送该UE的业务数据，例如，该业务为MBS。相应地，第一接入网设备接收该业务数据，并将该业务数据发送至该UE。
S201，第一接入网设备向UE发送测量配置参数。相应的，UE接收来自第一接入网设备的测量配置参数。
测量配置参数包括以下至少一项：测量频点/小区信息、上报门限配置、滤波参数配置，定时器时长配置等信息。
S202，处于RRC连接态的UE发送测量报告(measurement report)。相应地，第一接入网设备接收测量报告。
示例性地，UE根据测量配置参数测量频点或小区的信号强度，确定测量结果；然后，UE根据测量结果，确定测量报告并上报。
S203，第一接入网设备根据测量报告、运营策略或UE支持的PLMN等确定第二接入网设备。其中，第二接入网设备为UE即将切换到的接入网设备，例如目标基站；第一接入网设备为当前为UE服务的接入网设备，例如源基站。
S204，第一接入网设备向第二接入网设备发送切换请求消息(handover request message)，并将UE的上下文(UE context)信息随切换请求消息发送至第二接入网设备。相应地，第二接入网设备接收来自第一接入网设备的切换请求消息。
S205，第二接入网设备向第一接入网设备发送切换请求确认(handover request acknowledge)消息。相应的，第一接入网设备接收来自第二接入网设备的切换请求确认消息。
示例性地，第二接入网设备确定能够允许UE接入，并向第一接入网设备发送切换请求确认消息。可选的，切换请求确认消息中包括以下至少一项：小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)，第二接入网设备的安全算法。
S206，第一接入网设备向UE发送RRC重配置消息(RRC reconfiguration message)。相应的，UE接收来自第一接入网设备的RRC重配置消息。
可选地，RRC重配置消息中包括以下至少一项：第二小区的物理小区标识(physical cell identifier，PCI)，新的C-RNTI，第二接入网设备的安全算法标识(security algorithm identifiers)，接入第二小区所需的随机接入信道(random access channel，RACH)资源信息(如专用RACH资源和/或公共RACH资源)，第二小区的系统信息块(system information block，SIB)。
S207，UE同步到第二小区，并向第二接入网设备发送RRC重配置完成消息(RRC reconfiguration complete message)，指示RRC切换完成，也就是RAN切换完成。
S208，第二接入网设备向核心网设备发送路径切换请求消息(path switch request message)。相应地，核心网设备接收第二接入网设备发送的路径切换请求消息。
该路径切换请求消息用于触发切换下行数据路径到第二接入网设备，并建立核心网设备与第二接入网设备的控制面接口。
S209，核心网设备切换下行数据路径到第二接入网设备。
S210，核心网设备向第二接入网设备发送路径切换请求确认(path switch request acknowledge)消息。相应地，第二接入网设备接收核心网设备发送的路径切换请求确认消息。
可选地，S208和S210中的核心网设备为AMF。
综上，路径切换请求的目的是：请求核心网将该UE在第一接入网设备下的(一些)用户面传输承载的终结点切换至第二接入网设备，从而核心网可以通过第二接入网设备向此UE继续传输数据。
S211，第二接入网设备向第一接入网设备发送UE上下文释放(UE context release)消息。相应地，第一接入网设备接收第二接入网设备发送的UE上下文释放消息。
该释放消息指示切换成功，进一步地，第一接入网设备释放该UE的上下文关联的无线资源和控制面资源。
本申请实施例中涉及两个切换场景，其中，场景一如图3A所示，场景二如图3B所示。本申请实施例中，支持MBS会话的接入网设备可以称为MBS接入网设备，MBS接入网设备服务的小区可以称为MBS小区，核心网设备与MBS接入网设备之间通过MBS会话传输MBS。本申请实施例中，不支持MBS会话的接入网设备可以称为非MBS(non-MBS)接入网设备，例如传统(legacy)基站，non-MBS接入网设备服务的小区可以称为non-MBS小区，核心网设备与non-MBS接入网设备之间通过单播PDU会话传输MBS。
(1)场景一
第一接入网设备为MBS接入网设备。在UE切换到第二小区之前，该第一接入网设备有该UE正在传输或感兴趣的MBS。第二接入网设备为MBS接入网设备，但是，在UE切换到第二小区之前，该第二接入网设备没有该UE正在传输或感兴趣的MBS。第二小区为第二接入网设备的服务小区。
场景一中，由于第二接入网设备在切换前无该UE所需的MBS，并不清楚该MBS会话的状态，所以第二接入网设备在发现存在MBS信息的PDU会话后，会触发核心网设备为该MBS建立UP隧道，用于传输MBS数据。但是，若该MBS会话的当前状态为去激活，也就是没有MBS数据需要传输，那么一段时间后，该新建的UP隧道就会被删除。该新建的UP隧道还未使用就被删除，浪费资源且毫无用处。
(2)场景二
第一接入网设备为MBS接入网设备。第二接入网设备为non-MBS接入网设备。
场景二中，第二接入网设备无法识别MBS会话及其状态，因此第二接入网设备会触发核心网设备为该MBS会话关联的PDU会话建立UP隧道，用于传输MBS数据。但是，若该MBS会话的当前状态为去激活，且该MBS会话关联的PDU会话仅包含该MBS的QoS流时，那么一段时间后，该新建的UP隧道会因为没有MBS数据而被删除，也就是该新建的UP隧道还未使用就被删除，浪费资源且毫无用处。若该MBS会话的当前状态为去激活，且该MBS会话关联的PDU会话包含该MBS的QoS流和其他业务的QoS流时，那么新建UP隧道过程中会引入冗余消息，例如，该MBS会话关联的QoS流信息等，浪费信令资源且毫无用处。
为解决上述技术问题，下面结合附图对本申请实施例提供的方法进行说明。可以理解的是，下文所描述的方法实施例中仅以执行主体为核心网设备，接入网设备和终端设备为例进行说明，该方法实施例中提到的核心网设备还可以替换为由配置于核心网设备中的芯片执行， 该方法实施例中提到的接入网设备还可以替换为由配置于接入网设备中的芯片执行，终端设备也可以替换为由配置于终端设备中的芯片执行。核心网设备，接入网设备和终端设备具体可以是上文中提到的各种形态。例如，接入网设备可以为基站、CU或CU-CP等具有RRC连接控制功能的设备。例如，核心网设备可以是具有AMF功能的设备，或是具有AMF功能和UPF功能的设备，或者，核心网设备可以是具有AMF功能和SMF功能的设备，或者，核心网设备可以是具有AMF功能，UPF功能和SMF功能的设备。
图4是本申请实施例一提供的一种通信方法的流程示意图。如图4所示，实施例一提供的通信系统包括：第一接入网设备和第二接入网设备，其中，第一接入网设备可以用于执行实施例一的任一种可能实现方式中的方法，第二接入网设备可以用于执行实施例一的任一种可能实现方式中的方法。在实施例一中，将以图3A所示的场景一为例，描述一种可能的实现。该方法包括如下步骤。
S401，第一接入网设备发送第一消息。相应地，第二接入网设备接收第一消息。其中，第一消息指示MBS会话的第一状态为激活或去激活。
S402，第二接入网设备发送第一确认消息。相应地，第一接入网设备接收第一确认消息。其中，第一确认消息为第一消息对应的确认消息。
MBS是UE感兴趣或正在接收的业务。第一状态为该UE被切换前该MBS会话的状态，也就是核心网设备在UE被切换前通知第一接入网设备的MBS会话的状态。
可选的，第一接入网设备管理的MBS上下文中包含MBS会话的第一状态。第一接入网设备从核心网设备获知MBS状态后，可以将MBS状态信息保存供后续使用，该信息保存于MBS上文中和/或UE上下文中。
可选的，第二接入网设备保存MBS会话的状态至MBS上下文和/或UE上下文中。
第一消息指示MBS会话的第一状态，具体为如下方法1，方法2或方法3：
方法1：第一消息包含第一状态信息，该第一状态信息指示第一状态为激活或去激活。
方法2：第一消息通过是否包含第一状态信息来指示第一状态。例如，第一消息包含第一状态信息，第一消息指示第一状态为激活；或者，第一消息不包含第一状态信息，第一消息指示第一状态为去激活。可选地，第一状态信息为MBS会话的激活信息。
方法3：第一消息通过是否包含第一状态信息来指示第一状态。例如，第一消息包含第一状态信息，第一消息指示第一状态为去激活；或者，第一消息不包含第一状态信息，第一消息指示第一状态为激活。可选地，第一状态信息为MBS会话的去激活信息。
可选地，第一消息为切换请求消息，第一确认消息为切换请求确认消息。为了指示MBS会话的第一状态，需要在现有的切换请求消息里增加新的信元(information element，IE)。
可选地，第一消息是新消息，第一确认消息也是新消息。例如，第一消息就是为了指示MBS会话的第一状态而新引入的。
作为一种可能的实现方式，在步骤S401之后，还包括：第二接入网设备根据第一消息获取MBS会话的状态为第一状态。
MBS会话的状态为激活，第二接入网设备向核心网设备发送第一请求消息，该第一请求消息用于请求建立该MBS会话对应的UP隧道。相应地，核心网设备接收第二接入网设备发送的第一请求消息。
MBS会话的状态为去激活，第二接入网设备的处理方式为下列2种处理方式中的一种：第一种，第二接入网设备确定当期无需建立MBS会话对应的UP隧道。也就是，第二接入网设备确定无需向核心网设备请求建立MBS会话对应的UP隧道。那么，当MBS会话被激活 后，再请求建立UP隧道。相应地，核心网设备确定当前无需建立MBS会话对应的UP隧道。也就是，核心网设备不用接收第二接入网设备发送的请求建立该UP隧道的消息。第二种，第二接入网设备向核心网设备发送第一请求消息，该第一请求消息用于请求建立该MBS会话对应的UP隧道，该UP隧道被挂起。可以理解，在MBS会话被激活前，该UP隧道被挂起(suspended)或者说该隧道处于去激活状态。也就是该UP隧道被保留，不用于传输MBS数据，当MBS会话后续被激活后，可以继续使用该UP隧道，避免UP隧道删除的流程。相应地，核心网设备接收第二接入网设备发送的请求建立该UP隧道的消息。
第一消息用于指示MBS会话的第一状态，第二接入网设备可以根据该第一状态确定是否向核心网请求建立UP隧道。若该MBS会话的第一状态为激活，第二接入网设备可以触发新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的第一状态为去激活，第二接入网设备可以不触发新建UP隧道或者请求新建挂起的UP隧道，避免资源浪费问题。
图5是本申请实施例二提供的一种通信方法的流程示意图。如图5所示，实施例二提供的通信系统包括：第二接入网设备和核心网设备，其中，第二接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，核心网设备可以用于执行本实施例的任一种可能实现方式中的方法。在实施例二中，将以图3A所示的场景一为例，描述一种可能的实现。该方法包括如下步骤。
S501，第二接入网设备发送第二消息。相应地，核心网设备接收第二消息。
S502，核心网设备发送第二确认消息。相应地，第二接入网设备接收第二确认消息。其中，第二确认消息为第二消息对应的确认消息。
其中，第二消息指示MBS会话的第一状态为激活或去激活，其中，第一状态的描述参见实施例一，在此不再赘述；和/或，第二确认消息指示MBS会话的第二状态为激活或去激活，其中，第二状态为该UE被切换后该MBS会话的状态，也就是核心网设备在UE被切换后通过第二确认消息通知第二接入网设备的MBS会话的状态。
第二消息指示MBS会话的第一状态，具体为如下方法1，方法2或方法3：
方法1：第二消息包含第一状态信息，该第一状态信息指示第一状态为激活或去激活。
方法2：第二消息通过是否包含第一状态信息来指示第一状态。例如，第二消息包含第一状态信息，第二消息指示第一状态为激活；或者，第二消息不包含第一状态信息，第二消息指示第一状态为去激活。可选地，第一状态信息为MBS会话的激活信息。
方法3：第二消息通过是否包含第一状态信息来指示第一状态。例如，第二消息包含第一状态信息，第二消息指示第一状态为去激活；或者，第二消息不包含第一状态信息，第二消息指示第一状态为激活。可选地，第一状态信息为MBS会话的去激活信息。
第二确认消息指示MBS会话的第二状态，具体为如下方法1，方法2或方法3：
方法1：第二确认消息包含第二状态信息，该第二状态信息指示第二状态为激活或去激活。
方法2：第二确认消息通过是否包含第二状态信息来指示第二状态。例如，第二确认消息包含第二状态信息，第二确认消息指示第二状态为激活；或者，第二确认消息不包含第二状态信息，第二确认消息指示第二状态为去激活。可选地，第二状态信息为MBS会话的激活信息。
方法3：第二确认消息通过是否包含第二状态信息来指示第二状态。例如，第二确认消息包含第二状态信息，第二确认消息指示第二状态为去激活；或者，第二确认消息不包含第二状态信息，第二确认消息指示第二状态为激活。可选地，第二状态信息为MBS会话的去激 活信息。
一种可能的实现方式，第二确认消息指示MBS会话的第二状态为激活或去激活。可选地，在S502后，第二接入网设备获取MBS会话的状态为第二状态。
另一种可能的实现方式，第二消息指示MBS会话的第一状态为激活或去激活。可选地，在S501前，第二接入网设备获取MBS会话的状态为第一状态。核心网接收到第二消息后，若发现MBS会话当前的状态就是第一状态，那么第二确认消息可以不携带指示第二状态的信息，或者，第二确认消息可以确认MBS会话当前的状态就是第一状态。
又一种可能的实现方式，第二消息指示MBS会话的第一状态为激活或去激活，第二确认消息指示MBS会话的第二状态为激活或去激活。可选地，在S502后，第二接入网设备确定MBS会话的状态为第二状态。例如，第一状态为激活，第二状态为去激活，第二接入网设备确定所述MBS会话的状态为去激活。
可选地，第二消息为路径切换请求消息，第二确认消息为路径切换请求确认消息。为了指示MBS会话的第一状态，需要在现有的路径切换请求消息里增加新的信元，和/或，为了指示MBS会话的第二状态，需要在现有的路径切换请求确认消息里增加新的信元。
可选地，第二消息是新消息，第二确认消息也是新消息。例如，第二消息就是为了指示MBS会话的第一状态而新引入的，和/或，第二确认消息就是为了指示MBS会话的第二状态而新引入的。
MBS会话的状态为激活，第二接入网设备向核心网设备发送第一请求消息，该第一请求消息用于请求建立该MBS会话对应的UP隧道。相应地，核心网设备接收第二接入网设备发送的第一请求消息。
MBS会话的状态为去激活，第二接入网设备的处理方式可以参见实施例一的描述，在此不再赘述。
通过第二消息和/或第二确认消息，第二接入网设备可以获知MBS会话的状态，若该MBS会话的状态为激活，第二接入网设备可以触发新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的状态为去激活，第二接入网设备可以不触发新建UP隧道或者请求新建挂起的UP隧道，避免资源浪费问题。
在切换过程中，MBS会话的状态可能发生变化，也就是第一状态可能不同于第二状态，如果仍然按照第一状态处理，会造成由于MBS会话状态发生变化而引起的行为不匹配的问题。例如，MBS会话从激活变为去激活，若第一接入网设备还按照激活处理，会造成资源浪费。例如，MBS会话从去激活变为激活，若第一接入网设备还按照去激活处理，会造成UP隧道无法建立，MBS数据无法正常接收。那么采用本实施例的方法可以避免由于MBS会话状态发生变化而引起的行为不匹配的问题。
图5是本申请实施例三提供的一种通信方法的流程示意图。如图5所示，实施例三提供的通信系统包括：第二接入网设备和核心网设备，其中，第二接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，核心网设备可以用于执行本实施例的任一种可能实现方式中的方法。在实施例三中，将以图3A所示的场景一为例，描述一种可能的实现。该方法包括如下步骤。
S501，第二接入网设备发送第四消息。相应地，核心网设备接收第四消息。其中，第四消息用于请求建立MBS会话对应的用户面隧道，也就是，该用户面隧道用于MBS会话的数据传输。
S502，核心网设备发送第四确认消息。相应地，第二接入网设备接收第四确认消息。其 中，第四确认消息为第四消息对应的确认消息。其中，第四确认消息指示MBS会话的第二状态为激活或去激活。
第二状态为该UE被切换后该MBS会话的状态，也就是核心网设备在UE被切换后通过第四确认消息通知第二接入网设备的MBS会话的第二状态。
可选地，第四确认消息包括建立用户面隧道的信息以及指示MBS会话的第二状态为激活。
可选地，第四确认消息包括拒绝建立所述用户面隧道的信息。此时，MBS会话的状态可以是去激活，避免新建隧道后又释放导致的资源浪费。
可选地，第四确认消息包括建立用户面隧道的信息以及指示MBS会话的状态为去激活。此时，该UP隧道被挂起(suspended)或者说处于去激活状态，也就是该UP隧道被保留，只是不用于传输MBS数据。保留UP隧道的好处是，当MBS会话后续又被激活后，可以继续使用该UP隧道，避免UP隧道删除和UP隧道重建相关的流程，节省信令开销，避免UP隧道重建而带来的延时。
场景一中，第二接入网设备可以根据第四确认消息来获知核心网设备对UP隧道的管理。若该MBS会话的第一状态为去激活，第二接入网设备可以不触发新建UP隧道或者挂起新建的UP隧道，避免资源浪费。若该MBS会话的第一状态为激活，第二接入网设备可以触发新建UP隧道，保证切换过程中MBS的正常传输。
基于实施例二和实施例三的方案，图6是本申请实施例四提供的一种详细的通信方法的流程示意图。如图6所示，实施例四提供的通信系统包括：第二接入网设备和核心网设备，其中，第二接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，核心网设备可以用于执行本实施例的任一种可能实现方式中的方法。在实施例四中，将以图3A所示的场景一为例，描述一种可能的实现。需要说明的是，实施例四可以参见实施例二和三的描述，相同部分不再赘述。该方法包括如下步骤。
S601，第二接入网设备发送第二消息。相应地，核心网设备接收第二消息。
S602，核心网设备发送第二确认消息。相应地，第二接入网设备接收第二确认消息。其中，第二确认消息为第二消息对应的确认消息。
其中，第二消息指示MBS会话的第一状态，和/或，第二确认消息指示MBS会话的第二状态。可选地，第二消息为路径切换请求消息，第二确认消息为路径切换请求确认消息。
S601和S602的具体描述参见实施例二，在此不再赘述。
S603，第二接入网设备发送第四消息。相应地，核心网设备接收第四消息。其中，第四消息用于请求建立MBS会话对应的用户面隧道。
S604，核心网设备发送第四确认消息。相应地，第二接入网设备接收第四确认消息。其中，第四确认消息为第四消息对应的确认消息。其中，第四确认消息指示MBS会话的第二状态为激活或去激活。
S603和S604的具体描述参见实施例三，在此不再赘述。
示例性地，第二消息指示MBS会话的第一状态为激活，第四消息请求建立MBS会话关联的UP隧道，第四确认消息包括建立UP隧道的信息以及指示MBS会话的第二状态为激活。
示例性地，第二消息指示MBS会话的第一状态为激活，第四消息请求建立MBS会话关联的UP隧道，第四确认消息包括拒绝建立所述用户面隧道的信息，或者，第四确认消息包括建立UP隧道的信息以及指示MBS会话的状态为去激活，该UP隧道被挂起。
示例性地，第二确认消息指示MBS会话的第二状态为激活，第四消息请求建立MBS会话关联的UP隧道，第四确认消息包括建立UP隧道的信息以及指示MBS会话的第二状态为 激活。
示例性地，第二消息指示MBS会话的第一状态为去激活，第二确认消息指示MBS会话的第二状态为激活，第四消息请求建立MBS会话关联的UP隧道，第四确认消息包括建立UP隧道的信息以及指示MBS会话的第二状态为激活。
在切换过程中，MBS会话的状态可能发生变化，通过第二接入网设备和核心网设备对MBS会话状态的多次交互以及UP隧道建立的行为明确，可以避免由于MBS会话状态发生变化而引起的行为不匹配的问题。若该MBS会话状态为激活，第二接入网设备和核心网设备之间可以新建UP隧道，保证切换过程中MBS的正常传输。
基于实施例一，实施例二，实施例三，和/或，实施例四的方案，图7是本申请实施例五提供的一种详细的通信方法的流程示意图。如图7所示，实施例五提供的通信系统包括：第一接入网设备，第二接入网设备和核心网设备，其中，第一接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，第二接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，核心网设备可以用于执行本实施例的任一种可能实现方式中的方法。图7中用虚线表示的步骤是可选的，后文中不再赘述。在实施例五中，将以图3A所示的场景一为例，描述一种可能的实现。需要说明的是，实施例五可以参见实施例一，二，三和四的描述，相同部分不再赘述。该方法包括如下步骤。
S701，核心网设备确定MBS会话的第一状态。
MBS会话的状态是核心网管理的，也就是MBS会话的状态变化都是核心网触发的。其中，第一状态的描述参见实施例一，在此不再赘述。
S702，核心网设备发送第三信息。相应地，第一接入网设备接收第三信息。第三信息指示所述MBS会话的第一状态。
可选地，第三信息为MBS会话更改消息中包含的信息；或者，第三信息为MBS业务的数据包的包头中的一个信息域中的信息。
可选地，第三信息为第一PDU会话更改消息或建立消息中包含的信息，其中，第一PDU会话与该MBS会话关联。UE通知第一接入网设备该UE感兴趣的业务，或者说申请加入该MBS会话(MBS session join)，从而第一接入网设备确定向该UE发送该MBS数据。第一接入网设备收到UE加入MBS的请求后，会为UE进行建立、分配相应的资源用于后续MBS的传输，比如用于传输MBS的第一PDU会话。当UE加入MBS会话时，MBS会话的状态可以处于激活或去激活态。因此，核心网可以通过第一PDU会话更改消息或建立消息通知第一接入网设备该MBS会话的状态。
第一接入网设备接收到该第三消息后，可以获取该MBS会话的状态，进而明确MBS传输的操作。进一步地，第一接入网设备可以将MBS状态信息保存于MBS上文中和/或UE上下文中。
需要说明的是，S701和S702也适用于非切换场景。
S703，第一接入网设备根据UE发送的测量报告确定切换该UE到第二接入网设备服务的小区。具体描述参见图2所示的切换流程，在此不再赘述。
S704，第一接入网设备发送第一消息。相应地，第二接入网设备接收第一消息。其中，第一消息指示MBS会话的第一状态为激活或去激活。
S705，第二接入网设备发送第一确认消息。相应地，第一接入网设备接收第一确认消息。其中，第一确认消息为第一消息对应的确认消息。
可选地，第一消息为切换请求消息，第一确认消息为切换请求确认消息。
S706，核心网设备确定MBS会话的第二状态。其中，第二状态为该UE被切换后该MBS会话的状态，具体参见上述实施例。
作为第一种可能的实现方式，本实施例包括步骤S707和S708。
S707，第二接入网设备发送第二消息。相应地，核心网设备接收第二消息。
S708，核心网设备发送第二确认消息。相应地，第二接入网设备接收第二确认消息。其中，第二确认消息为第二消息对应的确认消息。
其中，第二消息指示MBS会话的第一状态，和/或，第二确认消息指示MBS会话的第二状态。可选地，第二消息为路径切换请求消息，第二确认消息为路径切换请求确认消息。
S707和S708的具体描述参见实施例二，在此不再赘述。
作为第二种可能的实现方式，本实施例包括步骤S709和S710。
S709，第二接入网设备发送第四消息。相应地，核心网设备接收第四消息。其中，第四消息用于请求建立MBS会话对应的用户面隧道。
S710，核心网设备发送第四确认消息。相应地，第二接入网设备接收第四确认消息。其中，第四确认消息为第四消息对应的确认消息。其中，第四确认消息指示MBS会话的第二状态为激活或去激活。
S709和S710的具体描述参见实施例三，在此不再赘述。
作为第三种可能的实现方式，本实施例包括步骤S707，S708，S709和S710，具体描述参见实施例四，在此不再赘述。
切换过程中，MBS会话的状态不明确，第二接入网设备和核心网设备的行为不明确，本实施例提供了一套MBS会话状态交互及其UP隧道如何建立的完整流程。通过本实施例的方法，明确了第二接入网设备和核心网设备的行为；若该MBS会话状态为激活，第二接入网设备和核心网设备之间可以新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的状态为去激活，第二接入网设备可以不触发新建UP隧道或者请求新建挂起的UP隧道，避免资源浪费问题。另外，通过第二接入网设备和核心网设备对MBS会话状态的多次交互以及UP隧道建立的行为明确，可以解决由于切换过程中MBS会话状态发生变化而引起的行为不匹配的问题。
基于实施例一，实施例二，实施例三，和/或，实施例四的方案，图8是本申请实施例六提供的一种详细的通信方法的流程示意图。如图8所示，实施例六提供的通信系统包括：第一接入网设备，第二接入网设备和核心网设备，其中，第一接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，第二接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，核心网设备可以用于执行本实施例的任一种可能实现方式中的方法。图8中用虚线表示的步骤是可选的，后文中不再赘述。在实施例六中，将以图3A所示的场景一为例，描述一种可能的实现。需要说明的是，实施例六可以参见实施例一，二，三和四的描述，相同部分不再赘述。和实施例五相比，本实施例中，服务UE的接入网设备从第一接入网设备切换到第二接入网设备，需要经过核心网。该方法包括如下步骤。
S801，核心网设备确定MBS会话的第一状态。
S802，核心网设备发送第三信息。相应地，第一接入网设备接收第三信息。第三信息指示所述MBS会话的第一状态。
S803，第一接入网设备根据UE发送的测量报告确定切换该UE到第二接入网设备服务的小区。
S801，S802和S803具体描述参见实施例五，在此不再赘述。
S804，第一接入网设备发送第一切换请求消息。相应地，核心网设备接收该第一切换请求消息。该第一切换请求消息指示切换该UE到第二接入网设备服务的小区。
S805，核心网设备发送第二切换请求消息。相应地，第二接入网设备接收该第二切换请求消息。该第二切换请求消息指示切换该UE到第二接入网设备服务的小区。其中，该第二切换请求消息还指示MBS会话的第一状态为激活或去激活。
第一切换请求消息和第二切换请求消息属于不同的消息，但是都指示切换该UE到第二接入网设备服务的小区。第二切换请求消息指示MBS会话的第一状态，具体可以参照实施例一中第一消息指示MBS会话的第一状态的方法1，方法2或方法3，在此不再赘述。
S806，第二接入网设备发送第二切换请求确认消息。相应地，核心网设备接收该第二切换请求确认消息。其中，第二切换请求确认消息为第二切换请求消息的确认消息。
S807，核心网设备发送第一切换请求确认消息。相应地，第一接入网设备接收第一切换请求确认消息。其中，第一切换请求确认消息为第一切换请求消息的确认消息。
S808，核心网设备确定MBS会话的第二状态。具体描述参见实施例五，在此不再赘述。
作为第一种可能的实现方式，本实施例包括步骤S809和S810。
S809，第二接入网设备发送第二消息。相应地，核心网设备接收第二消息。
S810，核心网设备发送第二确认消息。相应地，第二接入网设备接收第二确认消息。其中，第二确认消息为第二消息的确认消息。
其中，第二消息指示MBS会话的第一状态，和/或，第二确认消息指示MBS会话的第二状态。可选地，第二消息为路径切换请求消息，第二确认消息为路径切换请求确认消息。
S809和S810的具体描述参见实施例二，在此不再赘述。
作为第二种可能的实现方式，本实施例包括步骤S811和S812。
S811，第二接入网设备发送第四消息。相应地，核心网设备接收第四消息。其中，第四消息用于请求建立MBS会话对应的用户面隧道。
S812，核心网设备发送第四确认消息。相应地，第二接入网设备接收第四确认消息。其中，第四确认消息为第四消息的确认消息。其中，第四确认消息指示MBS会话的第二状态为激活或去激活。
S811和S812的具体描述参见实施例三，在此不再赘述。
作为第三种可能的实现方式，本实施例包括步骤S809，S810，S811和S812，具体描述参见实施例四，在此不再赘述。
切换过程中，MBS会话的状态不明确，第二接入网设备和核心网设备的行为不明确，本实施例提供了一套MBS会话状态交互及其UP隧道如何建立的完整流程。通过本实施例的方法，明确了第二接入网设备和核心网设备的行为；若该MBS会话状态为激活，第二接入网设备和核心网设备之间可以新建UP隧道，保证切换过程中MBS的正常传输；若该MBS会话的状态为去激活，第二接入网设备可以不触发新建UP隧道或者请求新建挂起的UP隧道，避免资源浪费问题。另外，通过第二接入网设备和核心网设备对MBS会话状态的多次交互以及UP隧道建立的行为明确，可以解决由于切换过程中MBS会话状态发生变化而引起的行为不匹配的问题。
图9是本申请实施例七的一种通信方法的流程示意图。如图9所示，本实施例提供的通信系统包括：第一接入网设备和核心网设备，其中，第一接入网设备可以用于执行本实施例的任一种可能实现方式中的方法，核心网设备可以用于执行本实施例的任一种可能实现方式中的方法。图9中用虚线表示的步骤是可选的，后文中不再赘述。在实施例七中，将以图3B 所示的场景二为例，描述一种可能的实现。该方法包括如下步骤。
S901，第一接入网设备确定MBS会话的状态为去激活，该MBS会话关联第一PDU会话。其中，该第一PDU会话仅用于该MBS会话。
该第一PDU会话为终端设备被配置的一个PDU会话，该第一PDU会话仅用于该MBS。
即使MBS会话去激活，第一PDU会话中仍存在MBS ID和QoS flow。
可选地，在S901之前，还可以包括实施例五中的S701，S702和S703。
作为第一种可能的实现方式，核心网通知第一接入网设备删除第一PDU会话。因此，本实施例包括步骤S902和S903。可选地，第一接入网设备释放第一PDU会话后，回复核心网设备，也就是还包括S905。
S902，第一接入网设备向核心网设备发送第五消息。相应地，核心网设备接收第五消息。第五消息用于请求释放所述第一PDU会话，或者说，该第五消息包括第一PDU会话的释放请求消息。
可选地，该第五消息还包括释放的原因(cause value)，例如，由于UE要切换至non-MBS基站，需要释放MBS相关信息。
S903，核心网设备发送第五消息对应的第五确认消息。相应地，第一接入网设备接收核心网设备发送的第五消息的第五确认消息。该第五确认消息包含第一PDU会话的释放信息。
在S903之前或同时，还包括：核心网设备释放第一PDU会话，例如，第一PDU会话占用的资源等。
S904，第一接入网设备释放第一PDU会话。例如，第一PDU会话占用的资源等。
作为第二种可能的实现方式，第一接入网设备删除第一PDU会话后告知核心网设备。因此，本实施例包括步骤S905。可选地，核心网设备会回复确认信息，也就是还包括S906。
S905，第一接入网设备发送第一PDU会话的释放消息。相应地，核心网设备接收该第一PDU会话的释放消息。
S906，核心网设备发送第一PDU会话的释放确认消息。相应地，第一接入网设备接收该第一PDU会话的释放确认消息。
S907，第一接入网设备释放UE的RRC连接。相应地，UE接收RRC释放消息。
因为UE没有PDU会话，无法进行HO，因此，UE可以进入RRC空闲态(idle)/非激活态(inactive)。此时，有2种可选方法：第一种为步骤S907，通知UE进入RRC空闲态/非激活态。第二种，UE自行进入RRC空闲态/非激活态。RRC空闲态/非激活态可以由UE收到的配置信息决定，比如小区级别的配置信息，或者UE接收到的关于释放PDU session的NAS non-access stratum非接入层信息等。UE进入RRC空闲态/非激活态后，可进行小区选择、重选等行为，满足其移动性要求。
在UE发生HO之前，该UE感兴趣的MBS业务的MBS会话已经被去激活。但是，该UE的PDU会话中仍存在MBS ID和&Qos flow。因此，当发生HO后，第二接入网设备会为UE感兴趣的MBS ID建立UP tunnel和相应的DRB。若该MBS会话的当前状态为去激活，且该MBS会话关联的PDU会话仅包含该MBS的QoS流时，那么一段时间后，该新建的UP隧道会因为没有MBS数据而被删除，也就是该新建的UP隧道还未使用就被删除，浪费资源且毫无用处。采用本实施例的方法，可以避免新建的UP隧道还未使用就被删除造成的资源浪费。
图10是本申请实施例八的一种通信方法的流程示意图。如图10所示，本实施例提供的通信系统包括：第一接入网设备和核心网设备，其中，第一接入网设备可以用于执行本实施 例的任一种可能实现方式中的方法，核心网设备可以用于执行本实施例的任一种可能实现方式中的方法。图10中用虚线表示的步骤是可选的，后文中不再赘述。在实施例八中，将以图3B所示的场景二为例，描述一种可能的实现。该方法包括如下步骤。
S1001，第一接入网设备确定MBS会话的状态为去激活，该MBS会话关联第一PDU会话。其中，该第一PDU会话用于传输单播业务和/或所述第一PDU会话还关联其它激活的MBS会话。
该第一PDU会话为终端设备被配置的一个PDU会话，该第一PDU会话用于该MBS，该第一PDU会话还用于单播业务和/或其它激活的MBS会话。
可选地，在S1001之前，还可以包括实施例五中的S701，S702和S703。
作为第一种可能的实现方式，核心网通知第一接入网设备修改第一PDU会话。因此，本实施例包括步骤S1002和S1003。可选地，第一接入网设备修改第一PDU会话后，回复核心网设备，也就是还包括S1005。
S1002，第一接入网设备向核心网设备发送第五消息，该第五消息用于请求将该MBS会话的信息从第一PDU会话中删除，或者说，第五消息包括第一PDU会话的修改请求消息，该修改请求消息请求删除MBS会话的信息。
可选地，该第五消息还包括修改的原因(cause value)，例如，由于UE要切换至non-MBS基站，需要释放MBS相关信息。
S1003，第一接入网设备接收核心网设备发送的第五消息对应的第五确认消息，该第五确认消息包含第一PDU会话的修改信息。
在S1003之前或同时，还包括：核心网设备修改第一PDU会话。
S1004，第一接入网设备删除第一PDU会话包含的该MBS会话的信息。
作为第二种可能的实现方式，第一接入网设备修改第一PDU会话后告知核心网设备。因此，本实施例包括步骤S1005。可选地，核心网设备会回复确认信息，也就是还包括S1006。
S1005，第一接入网设备发送第一PDU会话的修改消息。相应地，核心网设备接收该第一PDU会话的修改消息。
S1006，核心网设备发送第一PDU会话的修改确认消息。相应地，第一接入网设备接收该第一PDU会话的修改确认消息。
S1007，第一接入网设备向终端设备发送切换指示信息，该切换指示信息用于指示终端设备切换目标小区。也就是，第一接入网设备通知UE切换到第二接入网设备服务的小区，该第二接入网设备不支持MBS会话。相应地，终端设备接收切换指示信息。
若该MBS会话的当前状态为去激活，且该MBS会话关联的PDU会话包含该MBS的QoS流和其他业务的QoS流时，那么新建UP隧道过程中会引入冗余消息，例如，该MBS会话关联的QoS流信息等，浪费信令资源且毫无用处。采用本实施例的方法，可以避免新建的UP隧道还未使用就被删除造成的资源浪费。
需要说明的是，在本申请的各种实施例中，第一/二/三/四/五确认消息也可以称为第一/二/三/四/五应答消息或第一/二/三/四/五反馈消息，即为第一/二/三/四/五消息的应答消息或反馈消息。本申请实施例中，对于第一/二/三/四/五确认消息的名称不做限制。另外，本发明实施例中，“释放”也可以称为“删除”。
需要说明的是，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。上述各个过程涉及的各种数字编号或序号仅为描述方便进行的区分，而不应对本申请实施例的实施过程构成任何限定。例如， 若第一消息为切换请求消息，第一确认消息为切换请求确认消息，S704和S705在RAN切换完成之前；若第一消息并非切换请求消息，第一确认消息并非切换请求确认消息，S704和S705可以在RAN切换完成之前，期间或之后。
图11给出了本申请实施例提供的一种通信装置的结构示意图。需要说明的是，图11中虚线框表示的部分是可选，在后文中不多赘述。
通信装置1100包括一个或多个处理器1101。处理器1101可用于进行装置的内部处理，实现一定的控制处理功能。可选地，处理器1101包括指令1103。可选地，处理器1101可存储数据。所述处理器1101可以是通用处理器或者专用处理器等。例如，包括以下至少一个：基带处理器，中央处理器，应用处理器，调制解调处理器，图形处理器，图像信号处理器，数字信号处理器，视频编解码处理器，控制器，和/或神经网络处理器等。不同的处理器可是独立的器件，也可集成在一个或多个处理器中，例如，集成在一个或多个专用集成电路上。
可选地，通信装置1100包括一个或多个存储器1102，用以存储指令1104。可选地，所述存储器1102中还可以存储有数据。所述处理器和存储器可以单独设置，也可以集成在一起。
可选地，通信装置1100还可以包括收发器1105。其中，收发器1105可以用于向其他装置发送信息或从其他装置接收信息。所述收发器1105可以称为收发机、收发电路、输入输出接口等。
可选地，通信装置1100还可以包括以下一个或多个部件：无线通信模块，音频模块，外部存储器接口，内部存储器，通用串行总线(universal serial bus，USB)接口，电源管理模块，天线，扬声器，麦克风，输入输出模块，传感器模块，马达，摄像头，或显示屏等等。这些部件可以是硬件，软件，或者软件和硬件的组合实现。
处理器1101执行通信装置1100存储的指令(有时也可称为计算机程序或代码)，即通信装置存储的指令可以在所述处理器1101上被运行，使得所述通信装置1100执行上述实施例中描述的方法。可选地，所述指令为处理器1101中的指令1103，或者，所述指令为存储器中的指令1104。
在一种实现方式中，该通信装置1100可以用于实现上述申请实施例中对应于第一接入网设备的方法，具体功能参见上述实施例中的说明，在此不再赘述。示例性的，通信装置1100包括处理器1101，所述处理器1101用于执行计算机程序或指令，使得上述申请实施例中对应于第一接入网设备的方法被执行。可选地，处理器1101可以通过收发器1105与其它网络实体通信，例如，与第二接入网设备或核心网设备通信。可选地，存储器1102用于存储第一接入网设备的指令和数据。
在另一种实现方式中，该通信装置1100可以用于实现上述申请实施例中对应于第二接入网设备的方法，具体功能参见上述实施例中的说明，在此不再赘述。示例性的，通信装置1100包括处理器1101，所述处理器1101用于执行计算机程序或指令，使得上述申请实施例中对应于第二接入网设备的方法被执行。可选地，处理器1101可以通过收发器1105与其它网络实体通信，例如，与第一接入网设备或核心网设备通信。可选地，存储器1102用于存储第一接入网设备的指令和数据。
在又一种实现方式中，该通信装置1100可以用于实现上述申请实施例中对应于核心网设备的方法，具体功能参见上述实施例中的说明，在此不再赘述。示例性的，通信装置1100包括处理器1101，所述处理器1101用于执行计算机程序或指令，使得上述申请实施例中对应于核心网设备的方法被执行。可选地，处理器1101可以通过收发器1105与其它网络实体通信，例如，与第一接入网设备或第二接入网设备通信。可选地，存储器1102用于存储核心网 设备的指令和数据。
本申请中描述的处理器1101和收发器1105可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路(radio frequency identification，RFID)、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、或电子设备等上。实现本文描述的通信装置，可以是独立设备(例如，独立的集成电路，手机等)，或者可以是较大设备中的一部分(例如,可嵌入在其他设备内的模块)，具体可以参照前述关于核心网设备以及接入网设备的说明，在此不再赘述。
图12给出了本申请实施例提供的一种通信装置的结构示意图。如图12所示，装置1200可以包括：处理单元1202和通信单元1203。处理单元1202用于对装置1200的动作进行控制管理。通信单元1203用于支持装置1200与其他设备的通信。可选地，通信单元1203也称为收发单元，可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。装置1200还可以包括存储单元1201，用于存储装置1200的指令和/或数据。
在一种实现方式中，该通信装置1200可以用于实现上述申请实施例中对应于第一接入网设备或第二接入网设备的方法，具体功能参见上述实施例中的说明，在此不再赘述。处理单元1202可以支持装置1200执行上文中各方法示例中第一接入网设备或第二接入网设备的动作。或者，处理单元1202主要执行方法示例中的第一接入网设备或第二接入网设备的内部动作，通信单元1203可以支持装置1200与其它设备之间的通信。例如，支持装置1200与第二接入网设备或核心网设备通信，或者，支持装置1200与第一接入网设备或核心网设备通信。
在另一种实现方式中，该通信装置1200可以用于实现上述申请实施例中对应于核心网设备的方法，具体功能参见上述实施例中的说明，在此不再赘述。处理单元1202可以支持装置1200执行上文中各方法示例中核心网设备的动作。或者，处理单元1202主要执行方法示例中的核心网设备的内部动作，通信单元1203可以支持装置1200与其它设备之间的通信。例如，支持装置1200与第一接入网设备或第二接入网设备通信。
图13是本申请实施例提供的一种接入网设备的简化结构示意图，例如可以为基站的简化结构示意图。该接入网设备1300可应用于上述实施例中的第一接入网设备或第二接入网设备，执行上述方法实施例中第一接入网设备或第二接入网设备的操作或功能，具体可参见上述方法实施例中的描述，此处不再赘述。
该接入网设备1300包括：处理器1311，存储器1312，射频单元1321和天线1322。处理器1311也称为处理单元，用于支持执行上述方法实施例中第一接入网设备或第二接入网设备的功能。所述处理器1311可以是一个或多个处理器。所述一个或多个处理器可以支持同一种制式的无线接入技术，也可以支持不同种制式的无线接入技术(例如LTE和NR)。在一种实现中，所述处理器1311为集成电路，例如一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。存储器1312也称为存储单元，用于存储指令(有时也可称为计算机程序或代码)和/或数据。存储器1312可以是一个存储器，也可以是多个存储器或存储元件的统称。存储器1312与处理器1311可以位于同一个芯片中或不同芯片上。射频单元1321可以是一个或多个射频单元。天线1322主要用于收发电磁波形式的射频信号，例如，用于接入网设备1300向终端设备发送信号或接收信号。另外，接入网设备1300还包括：通信单元，其中，该通信单元用于支持接入网设备1300与其他设备的通信。例如，接入网设备1300用于实现上述申请实施例中对应于第一接入网设备的方法，那么通信单元用于支持接入网设备1300与第二接入网设备或核心网设备通信。例如，接入网设备1300用于实现上述申请实施例中对应于第二接入网 设备的方法，那么通信单元用于支持接入网设备1300与第一接入网设备或核心网设备通信。可选地，通信单元可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。
可选地，基带单元1310(baseband unit，BBU)包括处理器1311和存储器1312，主要用于信号的基带处理，管理无线资源，提供传输管理及接口，提供时钟信号等功能。可选地，所述BBU 2100可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述存储器1312和处理器1311可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。BBU1310可以用于执行前面方法实施例中描述的由第一接入网设备或第二接入网设备内部实现的动作。
可选地，射频单元1321为远端射频单元(remote radio unit，RRU)，所述RRU与BBU可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
可选地，单元1320可以是有源天线单元(Active Antenna Unit，AAU)，即将射频功能与天线集成在一起的硬件产品。AAU中的射频单元1321是指专用于AAU的射频模块，与RRU功能相同。可选地，该AAU还可以包括部分基带处理功能。
图14是本申请实施例提供的一种核心网设备的简化结构示意图，其中，核心网设备可以是具有AMF功能的设备，或是具有AMF功能和UPF功能的设备，或者，核心网设备可以是具有AMF功能和SMF功能的设备，或者，核心网设备可以是具有AMF功能，UPF功能和SMF功能的设备。
该核心网设备1400可包括处理器1401、存储器1402以及接口电路1403。处理器1401可用于对通信协议以及通信数据进行处理，以及对通信装置进行控制。存储器1402可用于存储程序和数据，处理器1401可基于该程序执行本申请实施例中由核心网设备执行的方法。接口电路1403可用于核心网设备1400与其他设备进行通信，该通信可以为有线通信或无线通信，该接口电路例如可以是服务化通信接口。
以上存储器1402也可以是外接于核心网设备1400的，此时核心网设备1400可包括接口电路1403以及处理器1401。以上接口电路1403也可以是外接于核心网设备1400的，此时核心网设备1400可包括存储器1402以及处理器1401。当接口电路1403以及存储器1402均外接于核心网设备1400时，通信装置1400可包括处理器1401。
图14所示的核心网设备能够实现上述实施例中涉及核心网设备的各个过程。图14所示的核心网设备中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，此处不再赘述。
可以理解的，本申请实施例中，终端设备和/或网络设备可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被运行时，实现前述方法实施例中由第一接入网设备、第二接入网设备或核心网设备所执行的方法。
本申请还提供一种包含计算机程序或指令的计算机程序产品，当该计算机程序或指令在计算机上运行时，使得该计算机执行前述任一方法实施例中由第一接入网设备、第二接入网设备或核心网设备所执行的方法。
对于上述计算机可读存储介质或计算机程序产品，当该计算机程序或指令被运行时，使得计算机执行上述实施例中由第一接入网设备所执行的方法；或者，当该计算机程序或指令被运行时，使得计算机执行上述实施例中由第二接入网设备所执行的方法；或者，当该计算机程序或指令被运行时，使得计算机执行上述实施例中由核心网设备所执行的方法。
示例性地，该计算机可读存储介质或者该计算机程序产品包括：用于实现从第一接入网设备接收第一消息，并向第一接入网设备发送第一确认消息的指令；用于实现向核心网设备发送第二消息，并从核心网设备接收第二确认消息的指令；和/或，用于实现向核心网设备发送第四消息，并从核心网设备接收第四确认消息的指令。示例性地，该计算机可读存储介质或者该计算机程序产品包括：用于实现向第二接入网设备发送第一消息，并从第二接入网设备接收第一确认消息的指令；用于实现接收第三信息，并将MBS状态信息保存于MBS上文中和/或终端设备的上下文中的指令；和/或，用于实现确定MBS会话的状态为去激活，且向核心网设备发送第五消息的指令。示例性地，该计算机可读存储介质或者该计算机程序产品包括：用于实现从第二接入网设备接收第二消息，并向第二接入网设备发送第二确认消息的指令；用于实现从第二接入网设备接收第四消息，并向第二接入网设备发送第四确认消息的指令；用于实现确定MBS会话的第一状态，并向第一接入网设备发送第三信息的指令；和/或，用于实现从第一接入网设备接收第五消息的指令。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带、磁盘)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例所涉及的终端设备或网络设备所执行的方法。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如，多个单元或部件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。所显示或讨论的相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
应理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包 括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
还应理解，本申请中所有节点、消息的名称仅仅是本申请为描述方便而设定的名称，在实际网络中的名称可能不同，不应理解本申请限定各种节点、消息的名称，相反，任何具有和本申请中用到的节点或消息具有相同或类似功能的名称都视作本申请的方法或等效替换，都在本申请的保护范围之内，以下不再赘述。
应理解，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的大小、内容、顺序、时序、优先级或者重要程度等。例如，第一信号的配置信息和第二信号的配置信息，可以是同一个配置信息，也可以是不同的配置信息，且，这种名称也并不是表示这两个配置信息的信息量大小、内容、优先级或者重要程度等的不同。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下网元会做出相应的处理，并非是限定时间，且也不要求网元实现时一定要有判断的动作，也不意味着存在其它限定。
还应理解，在本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“至少一项(个)”或其类似表达，是指一项(个)或多项(个)，即这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，表示：a,b,c,a和b,a和c,b和c,或a和b和c。
还应理解，本申请中出现的类似于“项目包括如下中的一项或多项：A，B，以及C”表述的含义，如无特别说明，通常是指该项目可以为如下中任一个：A；B；C；A和B；A和C；B和C；A，B和C；A和A；A，A和A；A，A和B；A，A和C，A，B和B；A，C和C；B和B，B，B和B，B，B和C，C和C；C，C和C，以及其他A，B和C的组合。以上是以A，B和C共3个元素进行举例来说明该项目的可选用条目，当表达为“项目包括如下中至少一种：A，B，……，以及X”时，即表达中具有更多元素时，那么该项目可以适用的条目也可以按照前述规则获得。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。例如，A/B，表示：A或B。
还应理解，在本申请各实施例中，“A对应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种通信方法，其特征在于，所述方法应用于第二接入网设备或者所述第二接入网设备中的芯片，所述方法包括：
    从第一接入网设备接收第一消息，所述第一消息指示多播广播业务MBS会话的第一状态为激活或去激活；
    向所述第一接入网设备发送所述第一消息对应的第一确认消息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一消息指示多播广播业务MBS会话的第一状态为激活，所述方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道；或者，
    所述第一消息指示多播广播业务MBS会话的第一状态为去激活，所述方法还包括：确定当前无需建立所述MBS会话对应的用户面隧道；或者，
    所述第一消息指示多播广播业务MBS会话的第一状态为去激活，所述方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道，所述用户面隧道被挂起。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述第一消息包含第一状态信息，所述第一状态信息指示所述第一状态为激活或去激活；或者，
    所述第一消息通过是否包含第一状态信息指示所述第一状态为激活或去激活。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述第一消息为切换请求消息，所述第一确认消息为切换请求确认消息。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述接收第一接入网设备发送的第一消息之后，还包括：
    向核心网设备发送第二消息；
    从所述核心网设备接收所述第二消息对应的第二确认消息；
    其中，所述第二消息指示所述第一状态，和/或，所述第二确认消息指示所述MBS会话的第二状态为激活或去激活。
  6. 根据权利要求5所述的方法，其特征在于，所述第二消息为路径切换请求消息，所述第二确认消息为路径切换请求确认消息。
  7. 根据权利要求5或6所述的方法，其特征在于，所述第一状态为终端设备被切换前所述MBS会话的状态，所述第二状态为终端设备被切换后所述MBS会话的状态，所述MBS为所述终端设备感兴趣或正在接收的MBS。
  8. 根据权利要求5至7任一项所述的方法，其特征在于，所述第二确认消息指示所述MBS会话的第二状态为激活或去激活，所述接收第一接入网设备发送的第一消息之后，所述方法还包括：
    确定所述MBS会话的状态为所述第二状态。
  9. 根据权利要求5至8任一项所述的方法，其特征在于，所述第一状态为激活，所述第二状态为去激活，所述接收所述核心网设备发送的所述第二消息的第二确认消息之后，还包括：
    确定所述MBS会话的状态为去激活。
  10. 根据权利要求8所述的方法，其特征在于，
    所述MBS会话的状态为激活，所述方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道；或者，
    所述MBS会话的状态为去激活，所述方法还包括：确定当前无需建立所述MBS会话对应的用户面隧道；或者，
    所述MBS会话的状态为去激活，所述方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道，所述用户面隧道被挂起。
  11. 一种通信方法，其特征在于，所述方法应用于第一接入网设备或者所述第一接入网设备中的芯片，所述方法包括：
    向第二接入网设备发送第一消息，所述第一消息指示多播广播业务MBS会话的第一状态为激活或去激活；
    从所述第二接入网设备接收所述第一消息对应的第一确认消息。
  12. 根据权利要求11所述的方法，其特征在于，
    所述第一消息包含第一状态信息，所述第一状态信息指示所述第一状态为激活或去激活；或者，
    所述第一消息通过是否包含第一状态信息指示所述第一状态为激活或去激活。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第一消息为切换请求消息，所述第一确认消息为切换请求确认消息。
  14. 根据权利要求11至13任一项所述的方法，其特征在于，所述向第二接入网设备发送第一消息之前，还包括：
    从核心网设备接收第三信息，所述第三信息指示所述MBS会话的第一状态。
  15. 根据权利要求14所述的方法，其特征在于，
    所述第三信息为所述MBS会话更改消息中包含的信息；或者，
    所述第三信息为PDU会话更改消息中包含的信息，或者，所述所述第三信息为PDU会话建立消息中包含的信息，其中，所述PDU会话与所述MBS会话关联；或者，
    所述第三信息为所述MBS业务的数据包的包头中的一个信息域中的信息。
  16. 一种通信方法，其特征在于，所述方法应用于核心网设备或者所述核心网设备中的芯片，所述方法包括：
    从第二接入网设备接收第二消息；
    向所述第二接入网设备发送所述第二消息对应的第二确认消息；
    其中，所述第二消息指示MBS会话的第一状态为激活或去激活；和/或，所述第二确认消息指示所述MBS会话的第二状态为激活或去激活。
  17. 根据权利要求16所述的方法，其特征在于，所述第一状态为终端设备被切换前所述MBS会话的状态，所述第二状态为终端设备被切换后所述MBS会话的状态，所述MBS为所述终端设备感兴趣或正在接收的MBS。
  18. 根据权利要求16或17所述的方法，其特征在于，所述第二消息为路径切换请求消息，所述第二确认消息为路径切换请求确认消息。
  19. 根据权利要求16至18任一项所述的方法，其特征在于，所述MBS会话的状态为第一状态或第二状态，
    所述MBS会话的状态为激活，所述方法还包括：从所述第二接入网设备接收第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道；或者，
    所述MBS会话的状态为去激活，所述方法还包括：确定当前无需建立所述MBS会话对应的用户面隧道；或者，
    所述MBS会话的状态为去激活，所述方法还包括：从所述第二接入网设备接收第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道，所述用户面隧道被挂起。
  20. 一种通信方法，其特征在于，所述方法应用于第二接入网设备或者所述第二接入网设备中的芯片，所述方法包括：
    向核心网设备发送第二消息；
    从所述核心网设备接收所述第二消息对应的第二确认消息；
    其中，所述第二消息指示所述MBS会话的第一状态为激活或去激活；和/或，所述第二确认消息指示所述MBS会话的第二状态为激活或去激活。
  21. 根据权利要求20所述的方法，其特征在于，所述MBS会话的状态为第一状态或第二状态，
    所述MBS会话的状态为激活，所述方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道；或者，
    所述MBS会话的状态为去激活，所述方法还包括：确定当前无需建立所述MBS会话对应的用户面隧道；或者，
    所述MBS会话的状态为去激活，所述方法还包括：向所述核心网设备发送第一请求消息，所述第一请求消息用于请求建立所述MBS会话对应的用户面隧道，所述用户面隧道被挂起。
  22. 一种通信方法，其特征在于，所述方法应用于第二接入网设备或者所述第二接入网设备中的芯片，所述方法包括：
    向核心网设备发送第四消息，所述第四消息用于请求建立MBS会话对应的用户面隧道；
    从所述核心网设备接收所述第四消息对应的第四确认消息，所述第四确认消息指示所述MBS会话的状态为激活或去激活。
  23. 根据权利要求22所述的方法，其特征在于，
    所述第四确认消息包括建立所述用户面隧道的信息以及指示所述MBS会话的状态为激活；或者，
    所述第四确认消息包括拒绝建立所述用户面隧道的信息；或者，
    所述第四确认消息包括建立所述用户面隧道的信息以及指示所述MBS会话的状态为去激活。
  24. 一种通信方法，其特征在于，所述方法应用于核心网设备或者所述核心网设备中的芯片，所述方法包括：
    从第二接入网设备接收第四消息，所述第四消息用于请求建立MBS会话对应的用户面隧道；
    向所述第二接入网设备发送所述第四消息对应的的第四确认消息，所述第四确认消息指示所述MBS会话的第二状态为激活或去激活。
  25. 根据权利要求24所述的方法，其特征在于，
    所述第四确认消息包括建立所述用户面隧道的信息以及指示所述MBS会话的第二状态为激活；或者，
    所述第四确认消息包括拒绝建立所述用户面隧道的信息；或者，
    所述第四确认消息包括建立所述用户面隧道的信息以及指示所述MBS会话的第二状态为 去激活。
  26. 一种通信装置，其特征在于，所述通信装置包括处理器和存储器，所述存储器用于存储计算机程序或指令，所述处理器用于执行存储器中的所述计算机程序或指令，使得权利要求1至10中任一项所述的方法被执行，或，使得权利要求20或21所述的方法被执行，或，使得权利要求22或23所述的方法被执行。
  27. 一种通信装置，其特征在于，所述通信装置包括处理器和存储器，所述存储器用于存储计算机程序或指令，所述处理器用于执行存储器中的所述计算机程序或指令，使得权利要求11至15中任一项所述的方法被执行。
  28. 一种通信装置，其特征在于，所述通信装置包括处理器和存储器，所述存储器用于存储计算机程序或指令，所述处理器用于执行存储器中的所述计算机程序或指令，使得权利要求16至19中任一项所述的方法被执行，或，使得权利要求24或25所述的方法被执行。
  29. 一种计算机可读存储介质，其特征在于，存储有计算机程序或指令，所述计算机程序或指令用于实现权利要求1至10中任一项所述的方法，或，用于实现权利要求20或21所述的方法，或，用于实现权利要求22或23所述的方法，或，用于实现权利要求11至15中任一项所述的方法，或，用于实现权利要求16至19中任一项所述的方法，或，用于实现权利要求24或25所述的方法。
  30. 一种通信系统，其特征在于，包括如权利要求26所述的通信装置，如权利要求27所述的通信装置和如权利要求28所述的通信装置；或者，包括如权利要求26所述的通信装置和如权利要求28所述的通信装置。
PCT/CN2022/083109 2021-04-30 2022-03-25 一种通信方法及通信装置 WO2022227971A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP22794444.4A EP4322608A1 (en) 2021-04-30 2022-03-25 Communication method and communication apparatus
BR112023022715A BR112023022715A2 (pt) 2021-04-30 2022-03-25 Método de comunicação e aparelho de comunicação
US18/496,231 US20240064864A1 (en) 2021-04-30 2023-10-27 Communication method and communication apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110484672.4A CN115278790A (zh) 2021-04-30 2021-04-30 一种通信方法及通信装置
CN202110484672.4 2021-04-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/496,231 Continuation US20240064864A1 (en) 2021-04-30 2023-10-27 Communication method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2022227971A1 true WO2022227971A1 (zh) 2022-11-03

Family

ID=83746106

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/083109 WO2022227971A1 (zh) 2021-04-30 2022-03-25 一种通信方法及通信装置

Country Status (5)

Country Link
US (1) US20240064864A1 (zh)
EP (1) EP4322608A1 (zh)
CN (1) CN115278790A (zh)
BR (1) BR112023022715A2 (zh)
WO (1) WO2022227971A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118042420A (zh) * 2022-11-02 2024-05-14 北京三星通信技术研究有限公司 支持组播业务传输的方法和设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163260A (zh) * 2006-10-14 2008-04-16 华为技术有限公司 一种控制承载变化的系统、装置和方法
CN101267593A (zh) * 2007-03-15 2008-09-17 华为技术有限公司 对目标小区进行组播广播多媒体业务激活的方法及基站
CN102137430A (zh) * 2011-04-02 2011-07-27 电信科学技术研究院 一种上报mbms业务状态的方法及装置
US20130242845A1 (en) * 2012-03-19 2013-09-19 Htc Corporation Method and Apparatus of Handling MBMS service in a Wireless Communication System
CN104937963A (zh) * 2013-10-28 2015-09-23 三星电子株式会社 具有鲁棒移动性的用于组通信的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163260A (zh) * 2006-10-14 2008-04-16 华为技术有限公司 一种控制承载变化的系统、装置和方法
CN101267593A (zh) * 2007-03-15 2008-09-17 华为技术有限公司 对目标小区进行组播广播多媒体业务激活的方法及基站
CN102137430A (zh) * 2011-04-02 2011-07-27 电信科学技术研究院 一种上报mbms业务状态的方法及装置
US20130242845A1 (en) * 2012-03-19 2013-09-19 Htc Corporation Method and Apparatus of Handling MBMS service in a Wireless Communication System
CN104937963A (zh) * 2013-10-28 2015-09-23 三星电子株式会社 具有鲁棒移动性的用于组通信的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "KI#1: Evaluation and conclusion for MBS session activation and deactivation", 3GPP DRAFT; S2-2008734, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20201116 - 20201120, 9 November 2020 (2020-11-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051952771 *

Also Published As

Publication number Publication date
BR112023022715A2 (pt) 2024-01-02
EP4322608A1 (en) 2024-02-14
CN115278790A (zh) 2022-11-01
US20240064864A1 (en) 2024-02-22

Similar Documents

Publication Publication Date Title
US11122413B2 (en) Method and apparatus for efficiently transmitting small amounts of data in wireless communication systems
CN107645779B (zh) 一种数据发送、传输方法及装置
CN104812070B (zh) 一种ue资源维护和释放的方法和设备
JP6656361B2 (ja) 無線リソース制御（ｒｒｃ）接続を解放する方法および装置
CN108521880B (zh) 切换基站的方法、装置及系统
CN109819485B (zh) 一种通信方法、装置及系统
CN109417699B (zh) 一种状态切换方法及装置
JP6976362B2 (ja) 通信方法および通信装置
JP2020506623A (ja) 通信ネットワークにおけるページングのための方法、基地局及び通信デバイス
JP6243021B2 (ja) ワイヤレス・セッションにおいてモードを切り換えるためのシステム
US20230143942A1 (en) Managing a ue preferred configuration
CN111510977B (zh) 一种移动性管理方法及装置
US20240064864A1 (en) Communication method and communication apparatus
KR20230041066A (ko) 데이터 송신 방법, 장치, 및 시스템
KR20220038103A (ko) 핸드오버 방법 및 장치
WO2016061791A1 (zh) 接口建立方法及装置
CN109314889B (zh) 一种建立用户面承载的方法、装置及系统
EP3018963B1 (en) Method and apparatus for controlling of ddn message, and computer readable medium for the same
CN109819487B (zh) 一种连接管理方法及设备
JP2022506330A (ja) データ転送方法、装置、マスタ基地局及びスレーブ基地局
JP2023500939A (ja) 通信方法及び装置
CN113163349A (zh) 用于语音业务的通信方法、装置和系统
WO2023120174A1 (en) Base station, network node, first core network node, second core network node, and methods performed by them
JP2021514566A (ja) サービス伝送方法および装置、コンピュータ記憶媒体
WO2023182189A1 (en) Communication system for the provision of multicast and broadcast services in cellular mobile radio networks

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

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023022715

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2022794444

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022794444

Country of ref document: EP

Effective date: 20231110

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112023022715

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20231030