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

一种通信方法及装置 Download PDF

Info

Publication number
WO2023185328A1
WO2023185328A1 PCT/CN2023/077490 CN2023077490W WO2023185328A1 WO 2023185328 A1 WO2023185328 A1 WO 2023185328A1 CN 2023077490 W CN2023077490 W CN 2023077490W WO 2023185328 A1 WO2023185328 A1 WO 2023185328A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
multicast
access network
network device
base station
Prior art date
Application number
PCT/CN2023/077490
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 华为技术有限公司
Publication of WO2023185328A1 publication Critical patent/WO2023185328A1/zh

Links

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application relates to the field of communication technology, and in particular, to a communication method and device.
  • radio access network (RAN) Equipment such as base stations
  • MBS air interface multicast/broadcast service
  • 3rd generation partnership project (3GPP) researchers have proposed to support terminal equipment (user equipment, UE) receiving in the radio resource control (radio resource control, RRC) deactivated state (RRC-inactive).
  • RRC radio resource control
  • RRC-inactive radio resource control
  • the base station cannot know whether the UE moves out of the range of the base station. It can only know whether the UE moves within a different radio access network notification area (RAN notification area, RNA).
  • RNA radio access network notification area
  • the group The data of the broadcast/broadcast service is transmitted to the UE based on the base station and service granularity. If the UE moves out of the base station range and the RNA where the UE is located has not changed, the base station cannot know the UE's movement, so it cannot effectively manage the multicast/broadcast session. , leading to a decrease in network resource utilization.
  • This application provides a communication method and device for effective management of multicast/broadcast sessions of terminal equipment in the RRC deactivation state and improving network resource utilization.
  • the present application provides a communication method, which may be implemented by a terminal device or a component in the terminal device, such as at least one of a processor, a transceiver, a processing module or a transceiver module.
  • the method includes: the terminal device determines that the access network device is changed to the first access network device, or determines that the cell is changed to the cell of the first access network device, and the terminal device has joined
  • the first multicast/broadcast service is in an RRC deactivated state; the terminal device sends the first message, the second message, the third message, the ninth message or the tenth message to the first access network device.
  • the first message is used to instruct the first access network device to send data of the first multicast/broadcast service; the second message is used to instruct the first access network device to The context of the first multicast/broadcast service is updated; the third message is used to restore the RRC connection of the terminal device; the ninth message is used to activate the user plane connection; and the tenth message is used to request registration.
  • the terminal equipment At least one of the first message, the second message, the third message, the ninth message or the tenth message may be sent to the first access network device.
  • the first access network device may learn that the terminal device moves to its coverage to receive the first multicast according to at least one of the first message, the second message, the third message, the ninth message, or the tenth message.
  • /broadcast service to create the first multicast/broadcast session or update the first multicast/broadcast session context in a timely manner, to achieve effective management of the first multicast/broadcast session and improve network resource utilization.
  • the multicast/broadcast session in this application can be replaced by a multicast/broadcast service; in addition, the multicast/broadcast session can also be used to transmit multicast/broadcast service data or to transmit multicast/broadcast service.
  • the terminal device allows receiving multicast/broadcast in the radio resource control deactivated state.
  • the terminal device may receive first information, where the first information includes an identity of the first access network device and/or an identity of a cell of the first access network device. . The terminal device may also determine, based on the first information, that the access network device is changed to the first access network device, or determine that the cell is changed to the cell of the first access network device.
  • the terminal device can identify whether to send access network equipment or cell changes in the RRC deactivation state, thereby improving the identification accuracy of access network equipment or cell changes during movement.
  • the terminal device may receive second information, where the second information is used to indicate at least one of the following: a portion of the first information occupied by the identity of the access network device. number of bits; or the second information is used to indicate the encoding method of the identity of the access network device in the first information; or the second information is used to indicate the encoding method of the identity of the cell in the first information.
  • the identity of the access network device may include a base station identity
  • the identity of the cell may include a cell ID.
  • the terminal device can correctly interpret the identity of the access network device and the identity of the cell in the first information based on the second information, further improving the accuracy of identifying changes in the access network device or cell.
  • the terminal device may also receive (or receive or determine to receive) data of the first multicast/broadcast service, and send the second data to the first access network device. message and/or the third message, or sending the second message and/or the ninth message, or sending the second message and/or the tenth message.
  • the terminal device can still receive the data of the first multicast/broadcast service after the access network device is changed or the cell is changed, the terminal device can send the second message and/or to the first access network device.
  • the terminal device determines (or discovers) that there is no (or has not received) transmission of the first multicast/broadcast service, and the terminal device sends the first multicast/broadcast service transmission to the first access network device. the first message and/or the third message, or the first message and/or the ninth message, or the first message and/or the tenth message.
  • the terminal device can send the first message and/or the first message to the first access network device.
  • Three messages so that the first access network device establishes the first multicast/broadcast session, or send the reception configuration of the first multicast/broadcast service to the terminal device to resume the transmission of the first multicast/broadcast service of the terminal device and promptly update the first multicast/broadcast session context.
  • At least one of the first message, the second message or the third message includes an identification of the terminal device, the first multicast/broadcast service Identification of the first protocol data unit At least one of a PDU session identifier or a reason for sending the message (or a reason for sending the message), and the first PDU session is associated with the first multicast/broadcast service.
  • the terminal device may also receive information about a first area, where the first area is a service area of the second access network device.
  • the terminal device may also determine to move out of the first area and send the third message.
  • the terminal device moves from the second access network device to the first access network device, or in other words, the access network device of the terminal device is changed from the second access network device to the first access network device. Furthermore, if the terminal device receives the indication information of the service area (i.e., the first area) of the second access network device, then the terminal device can determine that the access network device has changed after moving out of the first area, and therefore can report to the first access network device. The device sends a third message.
  • the indication information of the service area i.e., the first area
  • the terminal device determines that the access network device is changed from the second access network device to the first access network device, then the first message, the second message or the third message At least one of includes the identification and/or address of the second access network device.
  • the terminal device if the terminal device moves from the second access network device to the first access network device, the terminal device in the first message, the second message or the third message sent to the first access network device At least one may include an identifier of the second access network device, used to indicate the second access network device to the first access network device, so that the first access network device promptly notifies the second access network device to update the first group context of the broadcast/broadcast session.
  • the terminal device may determine to move out of the access network notification area, and the terminal device may also send a ninth message. Therefore, the terminal device may send the ninth message when it determines that the data of the first multicast/broadcast service has not been received and determines to move out of the access network notification area.
  • the terminal device may determine to move out of the registration area, and the terminal device may also send a tenth message. Therefore, the terminal device may send the tenth message when it determines that the data of the first multicast/broadcast service has not been received and determines to move out of the registration area.
  • the terminal device receives a seventh message from the first access network device, the seventh message includes the first configuration or first capability information; the first configuration includes for receiving the configuration of the first multicast/broadcast service; the first capability information is used to indicate whether the first access network device supports radio resource control RRC deactivation state reception, or the first capability information is used to indicate Whether the first access network device supports the terminal device to receive the first multicast/broadcast service in the RRC deactivation state, or the first capability information is used to indicate whether the first access network device supports the terminal device in the RRC deactivation state.
  • Receive multicast/broadcast services are used to indicate whether the first access network device supports the terminal device in the RRC deactivation state.
  • the terminal device can obtain the reception configuration of the first multicast/broadcast service according to the seventh message or obtain the configuration indicating whether the first access network device supports receiving the first multicast/broadcast data in the RRC deactivated state. Capability indication information.
  • the present application provides a communication method, which may be implemented by a terminal device or a component in the terminal device, such as at least one of a processor, a transceiver, a processing module or a transceiver module.
  • the method includes: the terminal device determines that data of the first multicast/broadcast service has not been received, and the terminal device has joined the first multicast/broadcast service and is in wireless resource control.
  • the terminal device sends at least one of a first message, a second message, a third message, a ninth message or a tenth message to the first access network device; wherein the first message is used to indicate that the The first access network device sends data of the first multicast/broadcast service; the second message is used to notify/instruct the first access network device to update the context of the first multicast/broadcast service ; The third message is used to restore the RRC connection of the terminal device; the ninth message is used to activate the user plane connection; the tenth message is used to request registration.
  • the terminal device determines that the data of the first multicast/broadcast service has not been received can be replaced by: “the terminal device has not received the configuration of the first multicast/broadcast service", or, "The terminal equipment determines that it has not received the first multicast/broadcast service data or the configuration of the first multicast/broadcast service", or “the terminal equipment determines that it has not received the first multicast/broadcast service data” Configuration", or, "The terminal device determines that the configuration of the first multicast/broadcast service has not been received.”
  • “the terminal device did not receive the configuration of the first multicast/broadcast service” can also be understood as "the configuration of the first multicast/broadcast service is not available/not applicable/does not exist (not available)”.
  • the configuration of the first multicast/broadcast service may be a multicast radio bearer (MRB) configuration of the first multicast/broadcast service.
  • the above-mentioned configuration of the first multicast/broadcast service may include configuration information, for example, configuration information (for example, the identification of the MRB) of the multicast radio bearer (MRB) of the first multicast/broadcast service.
  • configuration information for example, the identification of the MRB
  • MRB multicast radio bearer
  • PTM configuration point To multipoint configuration
  • the configuration of the above data can include multicast service logical channel configuration (multicast traffic channel configuration, MTCH configuration) without limitation.
  • the terminal device that has joined the first multicast/broadcast service and is in the RRC deactivation state can send a request to the first access network when it is determined that the data of the first multicast/broadcast service has not been received.
  • the device sends at least one of the first message, the second message, the third message, the ninth message or the tenth message, so that the first access network device can promptly learn that the terminal device is within the coverage of the first access network device and There is a need to receive the data of the first multicast/broadcast service in the RRC deactivated state, so that the first access network device can promptly create the first multicast/broadcast session or update the first multicast/broadcast session context to implement the first group Effective management of broadcast/broadcast sessions to improve network resource utilization.
  • the terminal device determines that the access network device is changed to the first access network device, or determines that the cell is changed to the cell of the first access network device.
  • the terminal device allows receiving multicast/broadcast in the radio resource control deactivated state.
  • the terminal device may receive first information, where the first information includes an identity of the first access network device and/or an identity of a cell of the first access network device. ; The terminal device determines that the access network device is changed to the first access network device according to the first information, or determines that the cell is changed to the cell of the first access network device.
  • the terminal device may also receive second information, the second information being used to indicate at least one of the following: the first information occupied by the identity of the access network device the number of bits; the second information is used to indicate the encoding method of the identity of the access network device in the first information; the second information is used to indicate the encoding method of the identity of the cell in the first information.
  • the terminal device may also receive (or receive or determine to receive) data of the first multicast/broadcast service, and then the terminal device may send a request to the first access network device. Send the second message and/or the third message, or the terminal device may send the second message and/or the ninth message to the first access network device, or the The first access network device sends the second message and/or the tenth message.
  • the terminal device can send the second message and/or to the first access network device.
  • the third message is used to enable the first access network device to update the context of the first multicast/broadcast session in a timely manner.
  • the terminal device can also send the ninth message or the tenth message to the first access network device, so that the first access network device sends the ninth message or the tenth message to the AMF, and the AMF further sends it to the SMF to trigger Activate the associated PDU session ID, and further trigger the establishment of the first multicast/broadcast session to the first base station.
  • the terminal device may send a request to the first access
  • the network device sends the first message and/or the third message, or the terminal device sends the first message and/or the ninth message to the first access network device, or the The first access network device sends the first message and/or the tenth message.
  • the terminal device can send the first message and/or the first message to the first access network device.
  • Three messages so that the first access network device establishes the first multicast/broadcast session according to the first message and/or the third message, or sends the reception configuration of the first multicast/broadcast service to the terminal device.
  • the terminal device can also send the ninth message or the tenth message to the first access network device, so that the first access network device sends the ninth message or the tenth message to the AMF, and the AMF further sends it to the SMF to trigger Activate the associated PDU session ID, and further trigger the establishment of the first multicast/broadcast session to the first base station.
  • At least one of the first message, the second message, the third message, the ninth message, or the tenth message includes the terminal At least one of the identification of the device, the identification of the first multicast/broadcast service, the first protocol data unit PDU session identification, or the reason for sending the message, the first PDU session and the first group broadcast/broadcast business association.
  • the terminal device may also receive information about a first area, where the first area is a service area of the second access network device.
  • the terminal device may also determine to move out of the first area and send the third message.
  • the terminal device determines that the access network device is changed from the second access network device to the first access network device, then the first message, the second message or the third message At least one of includes the identification and/or address of the second access network device.
  • the terminal device may determine to move out of the access network notification area, and the terminal device may also send a ninth message. Therefore, the terminal device may send the ninth message when it determines that the data of the first multicast/broadcast service has not been received and determines to move out of the access network notification area.
  • the terminal device may determine to move out of the registration area, and the terminal device may also send a tenth message. Therefore, the terminal device may send the tenth message when it determines that the data of the first multicast/broadcast service has not been received and determines to move out of the registration area.
  • the terminal device may receive a seventh message from the first access network device, where the seventh message includes the first configuration or first capability information; the first configuration including configuration for receiving the first multicast/broadcast service; the first capability information is used to indicate whether the first access network device supports radio resource control RRC deactivation state reception, or the first capability information is used to Indicate whether the first access network device supports receiving the first multicast/broadcast service in the RRC deactivation state, or the first capability information is used to indicate whether the first access network device supports the reception of the UE in the RRC deactivation state. Data of the first multicast/broadcast service.
  • the terminal device may send a ninth message according to the first capability information.
  • the first capability information is used to indicate that the first access network device supports the UE in the RRC deactivated state to receive the first multicast/broadcast service
  • the ninth message is sent.
  • the present application provides a communication method, which can be implemented by a first access network device or a component in the first access network device, such as at least one of a processor, a transceiver, a processing module or a transceiver module. kind.
  • the method includes: the first access network device receives the first message, the second message, the third message, the ninth message or the tenth message from the terminal device. At least one, wherein the first message is used to notify/instruct the sending of the first multicast/broadcast data, and the terminal device has joined the first multicast/broadcast service and is in an unavailable state.
  • the second message is used to notify/instruct the first access network device to update the context of the first multicast/broadcast service;
  • the third message is used to restore the context of the terminal device RRC connection;
  • the ninth message is used to activate a user plane connection;
  • the tenth message is used to request registration; at least one of the first message, the second message or the third message includes a second connection The identification and/or address of the network access device;
  • the first access network device sends a fourth message or a fifth message to the second access network device according to the identification and/or address of the second access network device.
  • the fourth message is used to update the context of the first multicast/broadcast service
  • the fifth message is used to extract the context of the terminal device
  • the eighth message is used for authentication Whether the terminal device has joined the first multicast/broadcast service.
  • the first access network device may also send the ninth message or the tenth message to the access management network element, where the ninth message or the tenth message carries A first protocol data unit PDU session identifier.
  • the ninth message or the tenth message carries the first protocol data unit PDU session identifier for activating the first PDU session or for activating the first PDU session.
  • the first PDU session is associated with the first multicast/broadcast service.
  • At least one of the first message, the second message or the third message may include the identification of the terminal device and/or the first multicast/broadcast service logo.
  • the fourth message, the fifth message, or the eighth message includes an identity of the terminal device and/or an identity of the first multicast/broadcast service.
  • the first access network device may also receive a sixth message from the second access network device, where the sixth message includes at least one of the following information: first configuration , the context information of the terminal device, the information of the first multicast/broadcast service, and the first capability information; the first configuration includes a configuration for receiving the first multicast/broadcast service; the third An access network device sends a seventh message, the seventh message includes the first configuration or first capability information; the first capability information is used to indicate whether the first access network device supports the UE in the RRC deactivation state. to receive the data of the first multicast/broadcast service.
  • the present application provides a communication method, which can be implemented by a second access network device or a component in the second access network device, such as at least one of a processor, a transceiver, a processing module or a transceiver module. kind.
  • the method includes: the second access network device receives at least one of the fourth message, the fifth message, or the eighth message from the first access network device, wherein , the fourth message is used to update the context of the first multicast/broadcast service, the fifth message is used to extract the context of the terminal device, and the eighth message is used to authenticate whether the terminal device
  • the first multicast/broadcast service has been joined, and the terminal device has joined the first multicast/broadcast service and is in a radio resource control deactivated state.
  • the first access network device updates the context of the first multicast/broadcast service.
  • the fourth message, the fifth message, or the eighth message includes an identity of the terminal device and/or an identity of the first multicast/broadcast service.
  • the second access network device may also update the number of terminal devices in the first multicast/broadcast service context according to the number of terminal devices.
  • At least one of the fourth message, the fifth message, or the eighth message includes an identification of the terminal device, and the second access network device can also delete (or move (except) the identity of the terminal device in the context of the first multicast/broadcast service.
  • the second access network device may also send a sixth message to the first access network device, where the sixth message includes a first configuration, and the first configuration includes using for receiving the first multicast/broadcast service configuration.
  • the second access network device sends information of a first area to the terminal device, where the first area includes at least one of the following: an identification of the second access network device , the cell included in the second access network device, the tracking area code of the second access network device, the access network area code of the second access network device, and the service area of the second access network device.
  • the second access network device determines that the first timer has expired, and the second access network device releases a first transmission resource, and the first transmission resource is used to transmit the first group of broadcasting/broadcasting business.
  • the first transmission resource includes the first multicast/broadcast session, and may also include shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the present application also provides a communication method, which can be implemented by a third access network device or a component in the third access network device, such as at least one of a processor, a transceiver, a processing module or a transceiver module. A sort of.
  • the method includes: the third access network device establishes a first multicast/broadcast session, and the first multicast/broadcast session is used to transmit the first multicast/broadcast session Service data; the third access network device sends a first instruction to at least one fourth access network device, the first instruction is used to instruct or trigger the fourth access network device to establish the first group broadcast/broadcast service session or shared multicast/broadcast service traffic transmission to establish the first multicast/broadcast session, the fourth access network device and the third access network device are located in or in the same RNA area, The first multicast/broadcast session is used to transmit the first multicast/broadcast service.
  • the third access network device when the third access network device in the RNA area establishes the first multicast/broadcast session, the third access network device can trigger other access network devices in the RNA area (i.e., the third access network device) through the first instruction.
  • the fourth access network device establishes the first multicast/broadcast session. Therefore, even if the terminal device moves from the coverage range of the third access network device to the coverage range of other fourth access network devices, due to the fourth access network device
  • the network device has established the first multicast/broadcast session. Therefore, the terminal device can receive the data of the first multicast/broadcast service from the fourth access network device without the need for the fourth access network device to establish the first multicast/broadcast session. Broadcast sessions can reduce the transmission delay of multicast/broadcast services and improve service quality.
  • the third access network device finds that there is no terminal device receiving the first multicast/broadcast session. For example, there is no terminal in the session context of the first multicast/broadcast service.
  • the identifier of the device, or the number of terminal devices in the session context is 0; the third access network device determines or finds that the fourth access network device does not have a terminal device to receive the first multicast/broadcast session; so The third access network device releases the first multicast/broadcast session or releases the shared multicast/broadcast service traffic transmission of the first multicast/broadcast session, and the fourth access network device communicates with the third access network device.
  • the three access network devices are located or in the same RNA area, and the first multicast/broadcast session is used to transmit the first multicast/broadcast service.
  • the third access network device determines that there is no terminal device among all access network devices in the RNA area, it releases the first multicast/broadcast session or releases the first multicast session.
  • /Broadcast session shared multicast/broadcast service traffic transmission otherwise, there is at least one terminal device in at least one access network device in the RNA to receive the first multicast/broadcast session, and the third access network device will retain the first group multicast/broadcast session or retain the shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the third access network device may receive a second indication from the fourth access network device, where the second indication is used to instruct the fourth access network device There is no terminal device to receive the first multicast/broadcast session, or the second indication may be used to notify that no terminal device has received the first multicast/broadcast session, and the first multicast/broadcast session is used for transmission The first multicast/broadcast session, or the second indication is also used to notify the existing terminal device to receive the first multicast/broadcast session.
  • the third access network device may determine, according to the second instruction from other fourth access network devices, that the fourth access network device does not have a terminal device to receive the first multicast/broadcast session, so The first multicast/broadcast session is used to transmit the first multicast/broadcast service.
  • the third access network device may send a third indication to the fourth access network device, where the third indication is used to indicate that the third access network device does not exist
  • the terminal device receives the first multicast/broadcast session, or the third indication is used to confirm whether there is a terminal device in the fourth access network device that receives the first multicast/broadcast session, and the The first multicast/broadcast session is used to transmit the first multicast/broadcast service.
  • the third access network device may send a third indication after the terminal device receives the first multicast/broadcast session without the presence of the third access network device, to trigger the fourth access network device to send the third instruction to the third access network device according to the third indication.
  • the third access network device sends the second instruction.
  • the third access network device sends a fifth instruction to the fourth access network device, and the fifth instruction is used to trigger the fourth access network device to release the first Multicast/broadcast session.
  • the third access network device can notify other fourth access network devices to release the first multicast/broadcast session when there is no terminal device to receive the first multicast/broadcast session and trigger the release of the first multicast/broadcast session.
  • the first multicast/broadcast session is the last access network device in the RNA area that does not have a terminal device to receive the first multicast/broadcast session.
  • any one of the first indication, the second indication, the third indication, the fourth indication or the fifth indication includes the first multicast/broadcast service
  • any one of the first indication, the second indication, the third indication, the fourth indication or the fifth indication may be carried in an Xn message or an X2 message or an interaction message between base stations or in communication messages.
  • the present application also provides a communication device.
  • the communication device may be a terminal device, an access network device, a component in a terminal device, or a component in an access network device.
  • the communication device has the function of implementing the methods in the above-mentioned first to fifth aspects and their respective possible implementations.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the communication device includes a communication module and a processing module. These modules or units can perform the corresponding functions in the above first to fifth aspects and their respective possible implementations. For details, see The detailed description in the method example will not be repeated here.
  • the communication module may include a receiving module and/or a transmitting module.
  • the structure of the communication device includes a communication interface and a processor, and optionally also includes a memory.
  • the communication interface is used to send and receive information or data, and to communicate with other devices in the communication network.
  • the processor is configured to support the communication device to perform the corresponding functions in the above-mentioned first to fifth aspects and their respective possible implementations.
  • the memory is coupled to the processor and holds program instructions and data necessary for the communications device.
  • embodiments of the present application provide a communication system, which may include a communication device for implementing the method shown in the above first aspect or second aspect and various possible implementations thereof, and include a communication device for implementing The communication device for the communication method shown in the third aspect and its possible implementations may optionally also include a communication device for implementing the method described in the fourth aspect and any possible implementations thereof.
  • the communication system may include a communication device for implementing the method shown in the above first aspect or the second aspect and its various possible implementations, and include a fourth access network in the same RNA area as the communication device. equipment.
  • embodiments of the present application provide a computer-readable storage medium, which stores Program instructions are stored, and when the program instructions are run on the computer, the computer is caused to execute the methods described in the first to fifth aspects of the embodiments of the present application and any possible implementation thereof.
  • computer-readable storage media can be any available media that can be accessed by a computer.
  • computer-readable media may include non-transitory computer-readable media, random-access memory (random-access memory, RAM), read-only memory (read-only memory, ROM), electrically erasable In addition to programmable read-only memory (electrically EPROM, EEPROM), CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or can be used to carry or store the desired program code in the form of instructions or data structures and can Any other media accessed by a computer.
  • random-access memory random-access memory
  • read-only memory read-only memory
  • ROM read-only memory
  • embodiments of the present application provide a computer program product, including computer program code or instructions.
  • the computer program code or instructions When the computer program code or instructions are run on a computer, the above first to fifth aspects or any one of them may be achieved. The methods described in Implementation are executed.
  • the present application also provides a chip, including a processor, the processor being coupled to a memory and configured to read and execute program instructions stored in the memory, so that the chip implements the above first aspect to the method described in the fifth aspect or any possible implementation manner therein.
  • Figure 1A is a schematic architectural diagram of a communication system provided by this application.
  • Figure 1B is an architectural schematic diagram of another communication system provided by this application.
  • FIG. 2 is an architectural schematic diagram of another communication system provided by this application.
  • FIG. 3 is an architectural schematic diagram of another communication system provided by this application.
  • FIG. 4 is a schematic diagram of data transmission provided by this application.
  • FIG. 5 is a schematic diagram of another data transmission provided by this application.
  • Figure 6 is a schematic flow chart of a communication method provided by this application.
  • Figure 7 is a schematic flow chart of another communication method provided by this application.
  • Figure 8 is a schematic flow chart of another communication method provided by this application.
  • Figure 9 is a schematic flow chart of another communication method provided by this application.
  • Figure 10 is a schematic flow chart of another communication method provided by this application.
  • FIG 11 is a schematic flow chart of another communication method provided by this application.
  • Figure 12 is a schematic flow chart of another communication method provided by this application.
  • Figure 13 is a schematic flow chart of another communication method provided by this application.
  • Figure 14 is a schematic structural diagram of a communication device provided by this application.
  • Figure 15 is a schematic structural diagram of another communication device provided by this application.
  • User equipment also called terminal equipment, is a device with wireless transceiver functions that can be accessed through the (wireless) access network equipment (radio access network, (R)AN) (or it can also be called access network equipment).
  • R radio access network
  • Ingress device communicates with one or more core network (CN) devices (or can also be called core devices).
  • CN core network
  • User equipment may also be referred to as an access terminal, terminal, subscriber unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent or user device, etc.
  • User equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons, satellites, etc.).
  • the user equipment may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) website, personal digital assistant (PDA), etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the user equipment may also be a handheld device with wireless communication capabilities, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device or a terminal in the Internet of Things, the Internet of Vehicles, the fifth generation (5th-generation, 5G) mobile communication network and any form of terminals in future networks, relay user equipment, or terminals in the future evolved public land mobile network (PLMN), etc.
  • the relay user equipment may be, for example, a 5G residential gateway (RG).
  • the user equipment can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, or telemedicine Wireless terminals in (remote medical), wireless terminals in smart grid (smart grid), wireless terminals in transportation safety (transportation safety), wireless terminals in smart city (smart city), smart home (smart home) Wireless terminals, etc.
  • VR virtual reality
  • AR augmented reality
  • Wireless terminals in industrial control a wireless terminal in self-driving
  • wireless terminals in smart grid smart grid
  • wireless terminals in transportation safety transportation safety
  • wireless terminals in smart city smart home
  • smart home smart home
  • the user equipment may also include end-side equipment, such as local switch (LSW), and/or customer premise equipment (CPE), etc., or the user equipment may access the network through LSE or CPE.
  • end-side equipment such as local switch (LSW), and/or customer premise equipment (CPE), etc.
  • LSE local switch
  • CPE customer premise equipment
  • the user equipment (UE) registered in the network can be understood as a user.
  • One of the UEs can correspond to a subscriber identity module (SIM) card. That is, when the terminal device is installed with a SIM card, the terminal device corresponds to a user UE. When the terminal device is installed with multiple SIM cards, the terminal device corresponds to Multiple user UE.
  • SIM subscriber identity module
  • network equipment refers to equipment that can provide wireless access functions for terminals, such as (R)AN equipment.
  • the network equipment can support at least one wireless communication technology, such as long term evolution (LTE), new radio (NR), wideband code division multiple access (WCDMA), etc.
  • LTE long term evolution
  • NR new radio
  • WCDMA wideband code division multiple access
  • the network equipment may include core network equipment, and the core network equipment may include, for example, core network elements (network function, NF) such as access and mobility management function (access and mobility management function, AMF).
  • NF core network elements
  • AMF access and mobility management function
  • (wireless) access network equipment can be used to provide network access functions for authorized user equipment in a specific area, and can use transmission tunnels of different qualities according to the level of user equipment, service requirements, etc.
  • (R)AN equipment can manage wireless resources, provide access services to user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network.
  • (R)AN can also be understood as a base station in a traditional network .
  • the access network device in the embodiment of the present application may be any communication device with wireless transceiver functions used to communicate with user equipment.
  • the access network equipment includes but is not limited to: evolved Node B (evolved Node B, eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (home) evolved NodeB, HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless Backhaul node, transmission point (TP) or transmission and reception point (TRP), etc.
  • 5G such as NR, gNB in the system, or transmission point (TRP or TP
  • One or a group (including multiple antenna panels) antenna panels of a base station in a 5G system or it can also be a network node that constitutes a gNB or transmission point, such as a baseband unit (BBU), or a distributed unit. DU) etc.
  • gNB may include centralized units (CUs) and DUs.
  • the gNB may also include an active antenna unit (AAU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB.
  • CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and packet data convergence protocol (PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU can be divided into access network equipment in the radio access network (RAN), or the CU can be divided into access network equipment in the core network, which is not limited in this application.
  • RAN radio access network
  • User plane network element used for packet routing and forwarding and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • the user plane network element may be a user plane function (UPF) network element.
  • UPF user plane function
  • user plane network elements can still be UPF network elements, or they can have other names, which are not limited in this application.
  • Data network element used to provide a network for transmitting data.
  • the data network element may be a data network (DN) network element.
  • DN data network
  • data network elements can still be DN network elements, or they can have other names, which are not limited in this application.
  • Authentication server used to perform user security authentication.
  • the authentication server may be an authentication server function (AUSF).
  • AUSF authentication server function
  • Mobility management network element mainly used for mobility management and access management.
  • the access management network element can be an AMF, which mainly performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transmitting user policies between the terminal and the policy control function (PCF) network element.
  • PCF policy control function
  • Network data analysis network element mainly used to provide network data analysis functions.
  • the network data analysis network element may be a network data analytics function (NWDAF).
  • Session management network element Mainly used for session management, Internet protocol (IP) address allocation and management of user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification, etc. .
  • IP Internet protocol
  • the session management network element can be a session management function (SMF) network element, which completes terminal IP address allocation, UPF selection, accounting and QoS policy control, etc.
  • SMF session management function
  • the application network element can be an application function (AF) network element, which represents the application function of a third party or operator. It is the interface for the 5G network to obtain external application data and is mainly used for Convey the requirements from the application side to the network side.
  • AF application function
  • Unified data management network element responsible for the management of user identification, contract data, authentication data, and user service network element registration management.
  • the unified data management network element may be unified data management (UDM).
  • Unified data storage network element used to store and retrieve UE's subscription data, etc.
  • the unified data storage network element can be a unified data warehousing function (unified data repository, UDR).
  • Policy control network element including user subscription data management function, policy control function, billing policy control function, quality of service (QoS) control, etc. It is a unified policy framework used to guide network behavior and is a control plane functional network element (such as AMF, SMF network elements, etc.) to provide policy rule information, etc.
  • QoS quality of service
  • the policy control network element may be the PCF.
  • Network function repository function network element Provides storage and selection functions for network function entity information for other core network elements.
  • the network element may be a network function repository function (NRF).
  • NEF network function repository function
  • Unstructured data storage network element stores and retrieves its unstructured data, such as UE context.
  • the unstructured data storage network element may be an unstructured data storage network function (UDSF).
  • UDSF unstructured data storage network function
  • Charging network element mainly used to perform charging functions.
  • the charging network element may be a charging network element (Charging Function, CHF).
  • Edge security network element Mainly used for communication between different operator networks. As a border gateway for different operator networks, it is responsible for message filtering and policy management on the control plane interface between operators.
  • the edge security network elements may be security edge protection proxies (SEPP).
  • Service communication agent network element used to support indirect communication and discovery of agent network functions.
  • the service communication proxy network element may include a service communication proxy (SCP).
  • SCP service communication proxy
  • the network open network element can be a network element function (NEF) network element, which is mainly used to expose the services and capabilities of 3GPP network functions to AF, and also allows AF to Provides information to 3GPP network functions.
  • NEF network element function
  • Network slice selection function network element responsible for selecting network slices for UE.
  • the application network element can be a network slice selection function (NSSF) network element.
  • NSSF network slice selection function
  • the above-mentioned network elements or devices can still use their names in the 5G communication system, or they can also have other names. This is the case in the embodiments of this application. Not limited.
  • the functions of the above network elements or devices can be completed by an independent network element, or can be completed by several network elements together.
  • network elements in the core network can be deployed on the same or different physical devices. For example, as a possible deployment, AMF and SMF can be deployed on the same physical device.
  • the network elements of the 5G core network can be deployed on the same physical device as the network elements of the 4th generation (4G) core network. The embodiments of the present application do not limit this.
  • the application network element may be an application function (AF) network element.
  • AF application function
  • future communication systems application network elements can still be AF network elements, or they can have other names, which are not limited in this application.
  • Figure 1A and Figure 1B show a schematic diagram of the fifth generation (5G) network architecture.
  • Figure 1A is a schematic diagram of the 5G network architecture under a non-service architecture
  • Figure 1B is a service-based architecture.
  • Schematic diagram of 5G network architecture under SBA Schematic diagram of 5G network architecture under SBA.
  • service-oriented architecture is the infrastructure of 5G network.
  • Servitization is mainly reflected in the control plane.
  • the essence of SBA is to define network functions as a number of "service” modules that can be flexibly called according to the three principles of "self-contained, reusable, and independent management.” Based on this, operators can flexibly customize the network according to business needs.
  • the interaction between network functions is implemented by service calls.
  • FIG. 1B is a schematic diagram of an exemplary service-oriented architecture of a 5G network.
  • core network elements can communicate with other core network elements through service-oriented interfaces.
  • service-oriented interface corresponding to AMF is It is called Namf interface
  • Nlmf interface the interface corresponding to LMF
  • the 5G network architecture shown in Figure 1A and Figure 1B can include three parts, namely terminal, DN and operator network. The following is a brief introduction to the functions of some of the network elements.
  • the operator network may include but is not limited to one or more of the following network elements: AUSF, PCF, UDM, AF, AMF, SMF network elements, (R)AN) equipment, UPF, NSSF, etc.
  • network elements or equipment other than wireless access network equipment may be called core network elements or core network equipment.
  • the N1 interface is the signaling interface between the AMF and the UE. It is used for exchanging signaling messages between the core network and the UE, such as the UE registering into the network, the UE establishing a protocol data unit (PDU) session, and network side configuration. UE strategy etc.
  • PDU protocol data unit
  • the N2 interface is the interface between the AMF and (R)AN, and is used to transmit wireless bearer control information from the core network to the (R)AN.
  • the N3 interface is the interface between (R)AN and UPF and is used to transmit UE service data between (R)AN and UPF.
  • the N4 interface is the interface between SMF and UPF. It is used to transfer information between the control plane and the user plane, including the control plane terminal equipment completing the network access operation based on the contract information with the operator.
  • the N6 interface is the interface between UPF and DN, and is used to transmit UE service data between UPF and DN.
  • N5 interface is the interface between PCF and AF.
  • the N7 interface is the interface between PCF and SMF and is used to deliver PDU session granularity and service data flow granularity control policies.
  • the N8 interface is the interface between AMF and UDM. It is used by AMF to obtain access and mobility management-related subscription data and authentication data from UDM, and for AMF to register UE's current mobility management-related information with UDM.
  • the N9 interface is the interface between two UPFs.
  • the N9 interface is the interface between the intermediate UPF (intermediate UPF, I-UPF) and the UPF as the PDU session anchor (PSA).
  • I-UPF intermediate UPF
  • PSA PDU session anchor
  • the N10 interface is the interface between SMF and UDM. It is used by SMF to obtain session management-related subscription data from UDM, and by SMF to register UE current session-related information with UDM.
  • the N11 interface is the interface between SMF and AMF. It is used to transfer PDU session tunnel information between (R)AN and UPF, transfer control messages sent to UE, transfer radio resource control information sent to (R)AN, etc. .
  • N12 interface including the interface between AMF and AUSF.
  • N13 interface including the interface between AUSF and UDM.
  • N22 interface including the interface between NSSF and AMF.
  • the above network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the above network element or function can be implemented by one device, or can be implemented by multiple devices together, or can be a functional module in one device, which is not specifically limited in the embodiments of this application.
  • the session management network element, user plane network element, and mobility management network element in this application can be the SMF, UPF, and AMF in Figure 1A respectively, or they can have the functions of the above SMF, UPF, and AMF in future communications such as 6G networks.
  • network element this application is not limited to this.
  • SMF, UPF, and AMF are used as examples of the session management network element, the user plane network element, and the mobility management network element respectively for description.
  • the promotion of multicast/broadcast solutions has encountered greater difficulties.
  • the existing multicast/broadcast solution requires adding dedicated network elements and interfaces that support multicast/broadcast on the basis of the existing communication architecture, and also requires dedicated multicast/broadcast channel support, which not only increases the operational
  • the overhead of business angle also increases the complexity of the terminal.
  • FIG. 2 it is the architecture adopted by the latest technical specifications of 5G multicast/broadcast, which provides a network architecture for supporting multicast/broadcast services.
  • This architecture is expanded on the basis of the architecture shown in Figure 1A.
  • a multicast broadcast session management function network element Multicast Broadcast Session Management Function, MB-SMF
  • a multicast broadcast user plane function network element Multicast Broadcast User Plane Function, MB-UPF
  • MB-UPF Multicast Broadcast User Plane Function
  • MB-SMF can implement the control plane function of multicast/broadcast services and is responsible for the management of multicast/broadcast services/groups/sessions.
  • MB-SMF can be connected to NEF and/or Multicast/Broadcast Service Function (MBSF), for example, used to receive multicast/broadcast service related information (for example, multicast /Description of broadcasting services).
  • MB-SMF can also be connected to PCF, for example, it can extract PCC rules related to multicast/broadcast services.
  • MB-UPF can be connected to the Multicast/Broadcast Service Transport Function (MBSTF) and/or AF/AS to receive multicast/broadcast service business data.
  • MBSTF Multicast/Broadcast Service Transport Function
  • AF/AS AF/AS
  • MB-SMF or MB-UPF is an example.
  • MB-SMF or MB-UPF can also have other names, which is not limited in this application.
  • access network equipment supporting multicast/broadcast functions can be understood as access network equipment supporting the transmission of multicast/broadcast services in the 5GC shared MBS traffic delivery mode.
  • the access network equipment does not support multicast/broadcast functions.
  • the access network equipment does not support the transmission of multicast/broadcast service data in the 5G core network shared multicast/broadcast service traffic transmission mode. That is, it only supports the 5G core network.
  • 5GC Individual MBS traffic delivery is used to transmit multicast/broadcast service data. It should be reasonable Solution: After the multicast/broadcast service data reaches the access network equipment (for example, RAN), it passes through the service data adaptation protocol (SDAP) layer and packet data convergence protocol (PDCP) of the RAN. layer, radio link control (RLC) layer, media access control (MAC) layer, and physical (physical, PHY) layer processing, sent to each receiver that receives multicast/broadcast service data UE.
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • the 5MBS research project only supports group members to receive multicast service data in the RRC-connected state (RRC-connected) in the version 17 (Release-17, R17) stage.
  • the 5MBS research project put forward the requirement to support group members to receive multicast services in the RRC-inactive state in the version 18 stage.
  • the radio access network device cannot effectively manage the multicast/broadcast session, and there is a problem of reduced network resource utilization.
  • the management process of the multicast/broadcast session in this application may include the establishment, release and update of the multicast/broadcast session.
  • the session establishment and release process are mainly described here, but should not be understood as the multicast/broadcast session.
  • the management process of broadcast sessions only includes the establishment and release of multicast/broadcast sessions
  • the multicast/broadcast session tunnel corresponding to the current multicast/broadcast session (MBS sesson) of 5MBS R17 is based on the base station and service (service) granularity. Its establishment is based on the first one to arrive at the base station and join the multicast/broadcast The service is triggered by the UE, and its release is based on the last UE joining the multicast/broadcast service under the base station leaving the multicast group, causing its release.
  • the multicast/broadcast group in this application refers to a UE group composed of UEs under the same base station that join a multicast/broadcast service.
  • the UE Since in 5MBS R17, the UE must receive in the RRC connected state (CM-connected) (hereinafter referred to as the connected state), there is a Ue-granular RRC connection between the UE in the connected state and the base station, and between the UE and the base station There is an N2 connection at the UE granularity. Therefore, the base station can sense whether the UE receives multicast/broadcast service data under its coverage. In other words, the base station can sense whether the UE has moved out of its coverage through the presence of UE-granular RRC messages.
  • CM-connected RRC connected state
  • RNA radio access network notification area
  • Unicast can be understood as "point-to-point" (PTP) communication.
  • unicast service means that the data of this service is sent to a single terminal device.
  • unicast refers to sending service data to terminal devices through PDU sessions. Between network elements (or devices), unicast refers to a unicast tunnel between the source network element and the target network element (that is, the IP address of the target network element is a unicast IP address).
  • the air interface unicast mode (or point-to-point mode) means that the access network device sends service data to a single terminal device. It can be understood that the access network device transmits service data to a single terminal through the wireless bearer of the air interface unicast mode. The device sends service data.
  • Multicast/broadcast refers to multicast (or multicast) or broadcast, which can be understood as "point to multi-point" (PTM) communication.
  • multicast/broadcast service means that the data of this service is sent to multiple terminal devices.
  • multicast/broadcast services refer to sending multicast/broadcast service business data to terminal devices through multicast/broadcast sessions.
  • multicast refers to a multicast tunnel between the source network element and the target network element (that is, the IP address of the target network element is a multicast IP address).
  • the air interface multicast/broadcast mode refers to a piece of service data sent by the access network device, which can be received by multiple terminal devices at the same time and/or on the same frequency. That is, the embodiments in this application can be applied to both multicast service transmission and broadcast service transmission.
  • Multicast/broadcast sessions include unicast tunnels, multicast tunnels, air interface wireless bearers in unicast mode, or air interface wireless bearers in multicast/broadcast mode between network elements.
  • the multicast/broadcast session can be used to send multicast service data to the terminal device (sends multicast broadcast service data), and can also be used to send broadcast service data to the terminal device. This is not limited in the embodiments of the present application. It should be understood that sending multicast service data can also be replaced by sending multicast/broadcast data (sends multicast broadcast data), or sending multicast/broadcast service (sends multicast broadcast service).
  • the current data sending mechanism of a multicast session can be understood as: a piece of data reaches the base station through a service-granularity tunnel, and the base station sends it to the base station in a point-to-multipoint manner through a multicast radio bearer.
  • a piece of data reaches the base station through a service-granularity tunnel, and the base station sends it to the base station in a point-to-multipoint manner through a multicast radio bearer.
  • One or more terminal devices joining the multicast session One or more terminal devices joining the multicast session.
  • a multicast/broadcast session tunnel for multicast services can be established between the access network equipment and the core network equipment.
  • Multicast/broadcast service data is transmitted in the multicast/broadcast session tunnel.
  • the access network equipment transmits multicast/broadcast service data through the multicast/broadcast session tunnel.
  • the multicast/broadcast service data received by the session tunnel can be sent to multiple terminal devices joining the multicast/broadcast service.
  • the multicast/broadcast service data in the multicast/broadcast session tunnel can be transmitted in the form of multicast/broadcast quality of service (QoS) stream.
  • QoS multicast/broadcast quality of service
  • the multicast/broadcast service can be transmitted in the multicast/broadcast session tunnel.
  • the session tunnel is transmitted in the form of one or more multicast/broadcast QoS streams.
  • multicast/broadcast session tunnels can correspond to multicast/broadcast services one-to-one, that is, one multicast/broadcast service corresponds to one multicast/broadcast session tunnel (Per MB service); a multicast/broadcast service can include One or more multicast/broadcast service flows. Multiple multicast/broadcast service flows can correspond to one or more multicast/broadcast QoS flows. A multicast/broadcast session can include one or more multicast/broadcast QoS flows. .
  • the multicast/broadcast session is based on the service granularity rather than the terminal device granularity. At least one terminal device can receive multicast/broadcast service data through the session. In other words, the multicast/broadcast session can Supports session sharing between multiple terminal devices.
  • the multicast/broadcast session or multicast/broadcast session tunnel in this application can be considered as the 5G core network shared multicast/broadcast service traffic transmission, so the multicast/broadcast session or multicast/broadcast session tunnel can be replaced by 5G
  • the core network shares multicast/broadcast service traffic transmission.
  • the shared multicast/broadcast service traffic transmission of the 5G core network can also be referred to as shared delivery.
  • the multicast/broadcast session tunnel may be a GTP-U tunnel shared by multiple terminal devices in the multicast group.
  • Multicast/broadcast services can be described by multicast/broadcast service information.
  • the multicast/broadcast service information at least includes multicast/broadcast service description information.
  • the multicast/broadcast service description information may include one or more multicast/broadcast services.
  • Description information of the service flow where the description information of the multicast/broadcast service flow includes at least one of the following: the quality of service index (QoS flow identifier, QFI) that the multicast/broadcast service flow should have, the Characteristic information (such as destination address, destination port number, source address of multicast/broadcast service, etc.), QoS requirements of multicast/broadcast service flow (such as jitter, delay, packet loss rate, bandwidth, etc.).
  • the QoS requirements of multicast/broadcast service flows are used to establish multicast/broadcast QoS flows.
  • the information of the multicast/broadcast service may also include information of the terminal device. For example, it may include one or more terminals that are allowed (or requested) to join the multicast/broadcast service.
  • multicast/broadcast service in this application can be replaced by a multicast/broadcast session parameter service, or can be replaced by a multicast/broadcast session.
  • the PDU session tunnel corresponds to the UE, and the service data in the PDU session tunnel can be transmitted in the form of unicast QoS flow.
  • the PDU session tunnel can also be used to transmit the unicast QoS flow mapped by the multicast/broadcast QoS flow corresponding to the multicast/broadcast service.
  • the PDU session is at the UE level, and the multicast/broadcast session is at the service level.
  • One PDU session of a UE can be associated with multiple multicast/broadcast services, that is, the UE can join at least one multicast/broadcast service through the PDU session.
  • a multicast/broadcast session can provide services for a multicast/broadcast service.
  • a multicast/broadcast session includes a unicast tunnel or multicast tunnel from the data network to the core network equipment to the access network equipment, and the access network Unicast air interface resources or multicast/broadcast air interface resources allocated by the device for sending the multicast/broadcast service.
  • Figure 4 exemplarily shows a schematic diagram of data transmission through unicast.
  • the transmission process shown in Figure 4 can be used to transmit unicast service data or multicast/broadcast service data.
  • each UE among UE1, UE2 and UE3 corresponds to a different PDU session.
  • the service provider CP/SP
  • the service data of the three UEs are all different
  • the target address can be the IP address of each UE
  • the service data of each UE can be sent to each UE through its own independent transmission path.
  • the service transmission path from CP/SP to RAN may include a transmission path between CP/SP and UPF, and a transmission path between UPF and RAN.
  • the transmission path between UPF and RAN can be called a PDU session tunnel, and different PDU sessions have different PDU session tunnels.
  • RAN can send service data to UE1, UE2 and UE3 in unicast mode, that is, PTP mode.
  • FIG. 5 exemplarily shows a schematic diagram of data transmission through multicast/broadcast mode.
  • the transmission process shown in Figure 5 can be used to transmit multicast/broadcast service data.
  • multicast/broadcast service data can be sent from CP/SP to UE1, UE2 and UE3.
  • the multicast/broadcast service transmission path from CP/SP to RAN may include a transmission path between CP and UPF, and a transmission path between UPF and RAN.
  • the transmission path from UPF to RAN can transmit multicast/broadcast service data through tunnels.
  • a tunnel based on the general tunnel protocol (GTP) is used.
  • the transmission path between UPF and RAN can be called a multicast/broadcast session tunnel, which is shared by UE 1, UE 2 and UE 3.
  • RAN can send multicast/broadcast service data to UE1, UE2 and UE3 through PTM, that is, RAN only needs to send one piece of data, and UE1, UE2 and UE3 can receive it at the same time.
  • multicast mode business data can be transmitted to all target nodes at once, or only to specific objects. Transmit business data. Therefore, in multicast mode, point-to-multipoint transmission can be achieved between a sending node and multiple receiving nodes, thus solving the problem of low efficiency of unicast mode.
  • access network equipment supporting multicast/broadcast functions can be understood as access network equipment supporting the transmission of multicast/broadcast service data in multicast/broadcast mode
  • access network equipment not supporting multicast/broadcast functions can be understood as The access network equipment does not support the transmission of multicast/broadcast service data in multicast/broadcast mode, or the access network equipment only supports the transmission of multicast/broadcast service data or PDU session data in unicast mode.
  • multicast/broadcast services can be sent to terminal devices through PDU sessions, that is, multicast/broadcast services are mapped to PDU sessions.
  • multicast/broadcast service data can be received from the core network through a multicast/broadcast session tunnel and sent to multiple terminal devices joining the multicast/broadcast service.
  • service data adaptation protocol service data adaptation protocol
  • PDCP packet data convergence protocol
  • wireless link control The processing of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer is sent to each UE that receives multicast/broadcast service data.
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • the communication method can be composed of user equipment (or components used to realize the functions of the user equipment, such as chips, processors or communication modules, etc.) and (R)AN equipment (or components used to realize the functions of the user equipment, such as chips, processors or communication module, etc.) implementation.
  • the communication method is explained by taking the user equipment as a UE and the (R)AN equipment as a base station as an example.
  • the communication method can also be used by other types of user equipment and/or (R)AN equipment involved in this application, or that the UE in this application can be replaced by a terminal equipment (or user equipment), and the base station can Replace with access network equipment or (R)AN equipment.
  • a communication method provided by the embodiment of the present application may include the following steps:
  • S101 The terminal determines that the access network device is changed to the first access network device, or determines that the cell is changed to the cell of the first access network device.
  • the UE determines that the base station is changed to the first base station, or determines that the cell is changed to the cell of the first base station.
  • the UE has joined the first multicast/broadcast service and is RRC-inactive.
  • the UE has joined the first multicast/broadcast service and is in the radio resource control inactive state (RRC-inactive); or, the UE has joined the first multicast/broadcast service and is allowed to be in the RRC-inactive state.
  • inactive receives (allowed to receive) multicast/broadcast services, or receives multicast/broadcast, or receives multicast/broadcast data.
  • "join the first multicast/broadcast service” can be replaced by "join the first multicast/broadcast session”.
  • the multicast/broadcast session can be used to transmit multicast/broadcast services.
  • the base station refers to the base station to which the UE is accessed.
  • the base station may also be called the base station to which the UE is attached (camp), or the base station that serves the UE.
  • the UE determines that the base station is changed to the first base station can also be replaced by, the UE "determines/finds that a base station change (or handover) occurs, and the changed base station is the first base station.”
  • the UE accessing the base station may mean that the UE is located within the coverage area of the base station; or it may mean that the UE is located within the coverage area of the base station and the UE is connected to the base station; or it may mean that the UE is located within the coverage area of the base station and There is message interaction between the UE and the base station.
  • the cell refers to the cell that the UE accesses. This cell can also be called the cell of the UE or the cell attached to the UE. A (camp) community.
  • “determine that the cell is changed to the cell of the first base station” can also be replaced by, the UE “determines/finds that a cell change (or handover) occurs, and the changed cell is the cell of the first base station.”
  • the cell change may include: the UE changes from one cell of the first base station to another cell of the first base station, and may also include changing from a cell of another base station to one of the cells of the first base station.
  • the UE accessing a cell or the UE attaching to a cell may mean that the UE is located within the coverage of the cell and the UE establishes a connection with the cell; or it may mean that the UE selects a frequency/frequency point/frequency band supported by the cell.
  • the UE may receive the first information, and determine based on the first information that the base station is changed to the first base station, or determine that the cell is changed to the cell of the first base station based on the first information.
  • the first information may include the identity of the first base station and/or the identity of the cell of the first base station. Therefore, the UE can compare the identification of the first base station with the identification of the base station received previously (which may refer to before receiving the first information) to identify whether a base station change has occurred, and/or the UE can compare the identification of the first base station with the identification of the first base station. The identity of the cell is compared with the identity of the cell received previously (which may refer to before receiving the first information) to identify whether a cell change has occurred.
  • the identity of the base station and/or the identity of the cell previously received by the UE may be carried in the information received by the UE (which may be referred to as third information in this application) before the UE receives the first information.
  • the third information may be sent and received in a manner similar to the first information. The difference is that the third information may come from the first base station or from other base stations. In this application, both the first information and the third information may be referred to as information used to carry the base station identity and/or the cell identity. If the UE receives the third information and the first information in the same location or service area (here it may refer to the signal coverage of the base station and the cell), the first information and the third information may carry the same base station identifier and cell identity.
  • the first information and the third information carry the identity of the first base station and/or the identity of the cell of the first base station.
  • the first information and the third information may carry different The identifier of the base station and/or the identifier of a different cell. That is to say, the identifier of the base station carried in the third information at this time can be the identifier of another base station other than the first base station, and/or the identifier of the cell carried in the third information.
  • the identifier may be different from the identifier of the cell of the first base station in the first information.
  • the third information may be information carrying the base station identity and/or cell identity received by the UE before receiving the first information. It can be understood that if the identity of the base station included in the third information is the identity of the second base station, regardless of whether the identity of the cell in the first information and the identity of the cell in the third information are the same, the UE can use the second base station according to the identity of the second base station. The identifier of the base station and the identifier of the first base station determine that the base station is changed from the second base station to the first base station, or in other words, the UE can determine that the base station change occurs.
  • the UE may The identifiers of these two cells determine that the cell is changed from one cell of the first base station to another cell of the first base station. That is, at this time, only the cell change occurs but no base station change occurs.
  • the UE may also change the area indication information or area information according to the area indication information or area information received from the second base station. Determining to move out of the coverage/service area of the second base station or the coverage/service area of the cell of the second base station.
  • the area indication information or area information may include access network notification area information (RAN-NotificationAreaInfo), and the access network notification area information may include at least one of the following: cell identification (cell ID), cell list (cell list) , area configuration list (ran-AreaConfigList), tracking area code (tracking area code), access network area code (RAN-AreaCode), public land mobile network ID (PLMN ID), the UE can receive from The area indication information or area information in the second base station is the first area. When the UE determines to move out of the first area, the UE may determine that a base station/cell change has occurred.
  • RAN-NotificationAreaInfo access network notification area information
  • the access network notification area information may include at least one of the following: cell identification (cell ID), cell list (cell list) , area configuration list (ran-AreaConfigList), tracking area code (tracking area code), access network area code (RAN-AreaCode), public land mobile network ID (PLMN ID)
  • the UE can receive from The area indication information or area information in
  • the first area may be the access network notification area, and the first area may include the cell identifier included in the second base station, or may include the identifier of the second base station, or may include The cell list of the second base station may include the tracking area code of the second base station, or may include the access network area code of the second base station.
  • the UE may determine that the base station is changed from the second base station to the first base station.
  • the following takes the first information as an example to describe the sending and receiving methods for information carrying base station identifiers and cell identifiers in various embodiments of the present application.
  • the third information can be implemented with reference.
  • the first information may be sent by the first base station.
  • the first information may be received to identify whether a base station change and/or cell change occurs.
  • the first information may be carried in a system message, where the system message may be sent in a broadcast control channel (BCH).
  • BCH broadcast control channel
  • the first information is carried in a system information block (SIB) sent by the cell of the first base station, such as SIB1.
  • SIB1 can be used to carry information or parameters for the UE to access the base station or cell.
  • the first information may include the cell global identity (CGI) in SIB1.
  • CGI cell global identity
  • the first information may be carried in a non-UE granular message, for example, a non-UE granular message sent on a multicast control channel, or a message sent on a multicast channel.
  • the first information may be carried in a multicast control channel (MCCH) or a multicast channel (MCH).
  • MCCH or MCH may be used to carry non-UE granular multicast/broadcast service-related information, such as configuration information for receiving multicast/broadcast service, etc.
  • the first information may be carried in an RRC message.
  • the RRC message may be an RRC reestablishment (RRCReestablishment) message, or may be an RRC reconfiguration (RRCReconfiguration) message, etc.
  • the first information may be carried in a paging message, and the paging message may be sent in a paging channel.
  • the first information may be carried in a group paging message of a multicast/broadcast service, or,
  • the first information is carried in a paging message for the UE.
  • the first base station in this application can also send second information.
  • the second information can be used by the UE to read the identity of the first base station and/or the first base station from the first information.
  • the identification of the neighborhood Because the identity of the first base station and/or the identity of the cell of the first base station in the first information each occupies a number of digits (digits) or a number of bits (bits) or a number of bytes (octet/byte) (octets) /bytes) or hexadecimal numbers (hexadecimals) or decimal numbers (decimals), as well as the identity of the first base station and/or the encoding method of the cell of the first base station, may be unknown to the UE in the RRC-inactive state.
  • the UE may need to assist in reading the identity of the first base station and/or the identity of the cell of the first base station through the second information.
  • the first information as CGI as an example, for different countries or different mobile network operators, the number of digits/digits of the base station identification and the number of digits of the cell identification included in the CGI are different. Therefore, the UE It is necessary to know the method of reading the identity of the first base station and/or the identity of the cell of the first base station from the first information through the second information, so as to correctly identify the identity of the first base station and/or the identity of the cell of the first base station.
  • the second information may be used to indicate the number of occupancies or occupied bits or number of bits or bytes or number of bytes or decimal number or hexadecimal number of the identity of the first base station in the first information, And/or, the second information may be used to indicate placeholder data or occupied bits or number of bits or bytes or number of bytes or decimal number or hexadecimal number indicating the identity of the cell of the first base station in the first information.
  • the second information indicates the number of bits occupied by the identity of the first base station, such as indicating that the identity of the first base station occupies the number of bits, Bits 0-6 in the first information, and/or, indicates the number of bits occupied by the identity of the cell of the first base station. If the identity indicating the first base station occupies bits 7-10 in the first information, the UE may use the second The information obtains the number of occupancies of the identity of the first base station and/or the identity of the cell of the first base station in the first information.
  • the second information also indicates the encoding method of the identity of the first base station and/or the identity of the first cell in the first information, for example, binary, octal, decimal, or hexadecimal. For example, if the second information contains The encoding mode indicates that binary encoding is used.
  • the value may be 010101; for another example, if the encoding mode included in the second information indicates that octal encoding is used, Then, for example, when the identity of the first base station in the first information occupies 0 to 6 bits, its value may be 276510; for another example, if the encoding method contained in the second information indicates decimal encoding, then, for example, when the first When the identity of the first base station in the information occupies 0 to 6 bits, its value may be 123459; for another example, if the encoding method contained in the second information indicates the use of hexadecimal encoding, then, for example, when the first base station in the first information When the base station identification occupies 0 to 6 digits, its value can be 9ABC23.
  • the UE knows the occupancy length of the first base station identity and/or the cell identity of the first base station in the first information, and also knows the encoding method of the base station identity and/or cell identity, the UE can read from the first information. Obtain the identity of the first base station and the identity of the cell of the first base station.
  • the second information may indicate the number of bits and/or encoding method occupied by the identity of the first base station and/or the identity of the cell of the first base station, which is determined by the UE according to the known length of the first information. and/or the number of bits occupied by the identity of the first base station (or the identity of the cell of the first base station) determines the number of bits occupied by the identity of the cell of the first base station (or the identity of the first base station). For example, the UE knows that the length of the first information is 10 bits, and the second information may indicate the number of bits occupied by the identity of the first base station, then the remaining number of bits in the 10 bits is the number of bits occupied by the cell of the first base station. .
  • the UE can accurately read the identity of the first base station according to the number of bits or bits or the number of bits or bytes or the number of bytes occupied by the identity of the first base station in the first information, and/or, according to the first base station Accurately read the number of bits or bits or bits or bytes or bytes occupied by the identity of the cell, and accurately read the identity of the cell of the first base station in the first information.
  • X may be indicated to indicate that the identity of the first base station consists of X bytes (consist of X octets/bytes).
  • the second information may be used to indicate the encoding method of the identity of the first base station in the first information, and/or the second information may be used to indicate the encoding method of the identity of the cell of the first base station in the first information.
  • the coding method of the identity of the first base station is the first coding method
  • the coding method of the cell identity of the first base station is the second coding method
  • the first coding method may be the same as or different from the second coding method
  • the UE may The base station identifier in the first information is decoded according to the first encoding method.
  • the part of the bits or bytes in the first information is the identifier of the first base station; similarly, the UE can The cell identifier in the first information is decoded according to the second encoding method. If part of the bits or bytes in the first information can be successfully decoded, the part of the bits or bytes is the identifier of the cell of the first base station.
  • the above second information may also be obtained by the UE from channels other than the first base station.
  • the UE may obtain the second information from a server (eg, a third-party server or application server or AF).
  • the UE may obtain the second information from the operator's initial configuration information.
  • the UE may obtain the second information from itself, for example, read the second information from factory configuration information or other local configuration information.
  • the UE may obtain the second information from the access network device (eg, the first base station or other base stations).
  • the UE may obtain the second information from the core network element.
  • the core network element may include SMF, UPF, AMF, NWDAF, PCF, UDM, UDR, NEF, MB-SMF, MB-UPF, MBSTF, MBSF, NRF, AUSF, UDSF, NSSF, CHF, SEPP, trusted non-3GPP At least one of gateway function (trusted non-3GPP gateway function, TNGF), SCP, or AF.
  • gateway function trusted non-3GPP gateway function, TNGF
  • SCP trusted non-3GPP gateway function
  • AF trusted non-3GPP gateway function
  • the UE may obtain the second information by receiving or obtaining from local configuration information (such as the operator's initial configuration information and/or factory configuration information) before S101.
  • the present application does not limit the RRC connection state in which the UE obtains the second information.
  • the second information may be received by the UE in the connected state.
  • the UE may obtain the second information from the base station (including but not limited to the third information) during the registration process.
  • a base station) receives the second information.
  • the second information may also be received by the UE after entering the RRC-inactive state.
  • the second information may also be received by the UE in the idle state.
  • the second information may be included in a SIB message or MCCH. This application does not make specific requirements for channel messages, RRC messages, paging messages, or messages sent by the MCH.
  • the UE can interpret the identity of the base station and/or the identity of the cell in the third information through a similar implementation method as interpreting the first information.
  • the identifier of the first base station in the first information and the identifier of the base station in the third information occupy the same number of digits or bits or number of bits or bytes or bytes, and the encoding methods are the same, then the UE The identifier of the corresponding base station in the first information can be read through the second information and the identifier of the base station in the third information can be read.
  • the UE may use the third The fourth information reads the identification of the base station in the third information.
  • the setting method of the fourth information (such as the content indicated by the information, usage method, etc.) and the way the UE obtains the fourth information (or called the acquisition method, including the location where the information is carried) can refer to the setting method of the second information and method of obtaining.
  • the fourth information may indicate that the number of occupied bits or bits or the number of bits or bytes or bytes of the identification of the base station in the third information is the same, as well as the encoding method; for another example, the UE may obtain the information from the base station included in the third information. The base station or other channels to which the identification belongs obtains the third information.
  • the UE can read the identity of the cell of the first base station in the first information through the second information and read the identity of the cell in the third information. If the identity of the cell of the first base station in the first information occupies the same number of digits or bits or the number of bits or bytes or the number of bytes as the identity of the cell in the third information, and the encoding methods are different, the UE may The identity of the cell in the third information is read through the fifth information.
  • the setting method of the fifth information and the method of obtaining the fifth information by the UE may refer to the second information.
  • the fifth information may indicate the number of occupied digits or bits or the number of bits or bytes or the number of bytes or the encoding method of the cell identity in the third information; for another example, the UE may select the cell identity included in the third information to which it belongs. base station or other channels to obtain the third information.
  • S101 can also be replaced by: UE discovers (find/know) that the base station is changed to the first base station (find the NG-RAN is changed), or determines that the cell is changed to the cell of the first base station (find the cell is chnaged) .
  • S101 may also be replaced with: the UE determines/discovers that the data of the first multicast/broadcast service has not been received or that the first multicast/broadcast service has not been received or that the first multicast/broadcast data has not been received.
  • the first multicast/broadcast service has been joined and is in the RRC-inactive state.
  • the terminal sends at least one of the first message, the second message, the third message, the ninth message or the tenth message to the first access network device.
  • the UE may send at least one of the first message, the second message, the third message, the ninth message or the tenth message to the first base station.
  • the first base station receives at least one of the first message, the second message, the third message, the ninth message or the tenth message.
  • the first message, the second message, the third message, the ninth message and the tenth message are respectively described below.
  • the first message may be used to instruct the first base station to send data of the first multicast/broadcast service, or the first message may be used to indicate interest in the first multicast/broadcast service (indicate interest on the related MBS session).
  • the data of the first multicast/broadcast service may be replaced by the first multicast/broadcast service or the first multicast/broadcast data or the data of the first multicast/broadcast session.
  • the first message is used to instruct the first base station to send data of the first multicast/broadcast service.
  • the first message is used to notify the first base station to send data of the first multicast/broadcast service. data.
  • the first message is used to instruct the first base station to send data of the first multicast/broadcast service.
  • the first message is used to notify or instruct the first base station to send the reception configuration of the first multicast/broadcast service.
  • the receiving configuration can also be called the configuration information used to receive the first multicast/broadcast service, such as point-to-multipoint configuration (PTM configuration), reception configuration (reception configuration), etc.
  • PTM configuration point-to-multipoint configuration
  • reception configuration reception configuration
  • the first message may carry data used to instruct or notify the first base station to send the first multicast/broadcast service or information used to notify or instruct the first base station to send the reception configuration of the first multicast/broadcast service
  • the first message may be a message used to instruct or notify the first base station to send data of the first multicast/broadcast service or a message used to notify or instruct the first base station to send a reception configuration of the first multicast/broadcast service.
  • the first message may carry the identifier of the first multicast/broadcast service.
  • the identifier may be the identifier MBS session ID of the multicast/broadcast service or the multicast/broadcast session.
  • the MBS session ID may be the temporary mobile group identifier. identity, TMGI), MBS session ID can also be an IP multicast address (IP pulticast address).
  • being used to instruct or notify the first base station to send the first multicast/broadcast service can also be understood as being used to instruct or notify the first base station to trigger the establishment of a multicast/broadcast session, or can also be understood as triggering the first base station to trigger the establishment of a multicast/broadcast session.
  • 5G core network shared multicast/broadcast service traffic transmission (5GC shared MBS traffic delivery).
  • the UE may send the first message in S102 to instruct the first base station to send the first group Data and/or reception configuration for broadcast/broadcast services.
  • the UE can implicitly instruct the first base station to update the context of the first multicast/broadcast session through the first message, thereby achieving effective management of the first multicast/broadcast session and improving network resource utilization.
  • the second message is used to instruct the first base station to update the context of the first multicast/broadcast service, or the second message can be used to indicate interest in the first multicast/broadcast service;
  • the context of the first multicast/broadcast service may be replaced by the context of the first multicast/broadcast session.
  • the UE may send the second message in S102 to instruct the first base station to update the first multicast service.
  • /Broadcast session context to achieve effective management of the first multicast/broadcast session and improve network resource utilization.
  • the third message is used to restore the RRC connection of the UE.
  • the third message can be used to request to enter the RRC connection state.
  • the third message may include an RRC resume request (RRC resume request) message.
  • RRC resume request RRC resume request
  • the UE may request to return to the RRC connected state through the third message, so that the UE can receive data and/or receive configurations of the first multicast/broadcast service in the RRC connected state.
  • the UE may implicitly instruct the first base station to update the context of the first multicast/broadcast session through the third message, and may also implicitly instruct the first base station to establish the multicast/broadcast session through the third message, thereby implementing the first Effective management of multicast/broadcast sessions to improve network resource utilization.
  • the ninth message is used to activate the user plane connection.
  • the ninth message can be used to request activation of the associated PDU User plane connection of the session (associated PDU session), or used to request activation of the associated PDU session.
  • the association of the associated PDU session with the first multicast/broadcast service can be understood as, the UE can pass the control plane of the associated PDU session Signaling request to join or exit the first multicast/broadcast service. After successfully joining the first multicast/broadcast service, the associated PDU session can also be used to transmit data of the first multicast/broadcast service.
  • the UE can send the ninth message to the first base station, and the ninth message carries the associated The ID of the PDU session, the ninth message may be a service request message, and then the first base station sends the ninth message to the AMF, and the AMF further sends it to the SMF, triggering the activation of the associated PDU session ID, and further triggering the establishment of the first Multicast/broadcast session to the first base station.
  • the tenth message is used to request registration.
  • the tenth message can be used for the UE to request to register with the network. For example, if the UE discovers/determines that the first multicast/broadcast service has not been received and the UE moves out of the registration area (RA), for example, because the changed first base station or cell is outside the registration area, the UE The tenth message can be sent to the base station.
  • the tenth message carries the ID of the associated PDU session.
  • the tenth message can be a registration request message.
  • the first base station sends the tenth message to the AMF, and the AMF further sends it to the SMF. Trigger activation of the associated PDU session ID, and further trigger establishment of a first multicast/broadcast session to the first base station.
  • the above first message, second message or third message may be a radio message, and the radio message may be an RRC message.
  • the RRC message may be an RRC resume request (RRC resume request) message.
  • the wireless message may also be other non-RRC messages.
  • the non-RRC message has a different name from the RRC message, it may have the same or similar functions as the RRC message.
  • the functions here at least include the indicating function of the above first message, the second message or the third message (such as indicating the content indicated by the first message, the second message or the third message) or the notification function (such as notifying the first message, the third message). The content notified by the second message or the third message).
  • the above ninth message or tenth message may be a non-access stratum (NAS) message, and the NAS message may be a service request message, or a registration request message, or it may also be an uplink non-access stratum data transmission (UL NAS transport) message, or other NAS messages, without limitation.
  • NAS non-access stratum
  • UL NAS transport uplink non-access stratum data transmission
  • At least one of the above first message, second message, third message, ninth message or tenth message may include the identity of the UE, the identity of the first multicast/broadcast service or the UE sends the message at least one of the reasons.
  • the identity of the UE includes, for example, the UE's inactive radio network temporary identifier (inactive radio network temporary identifier, I-RNTI) or may be the radio network temporary identifier (radio network temporary identifier, RNTI) or It can be 5G temporary mobile subscription identifier (5G s-temporary mobile subscription identifier, 5G-S-TMSI), user permanent identifier (subscription permanent identifier, SUPI), general public subscription identifier (GPSI), user hidden Identifier (subscription concealed identifier, SUCI), general public subscription identifier (GPSI), permanent equipment identifier (permanent equipment identifier, PEI), international mobile subscriber identity (IMSI), global Unique temporary identity (globally unique temporary identity, GUTI), or NG application layer protocol (NG application protocol, NGAP) identity (NGAP UE ID).
  • the NGAP UE ID may include the RAN NGAP UE ID allocated by the base station and/or
  • the identification of the first multicast/broadcast service may include an identification of the multicast/broadcast session of the first multicast/broadcast service
  • the multicast/broadcast session of the first multicast/broadcast service may also be called the first multicast/broadcast session
  • the identifier of the multicast/broadcast session of the first multicast/broadcast service may also be called the first multicast/broadcast session.
  • Session ID MMS session ID
  • the multicast/broadcast session identifier can be TMGI or a source specific IP address.
  • the source specific IP address can be understood as the address of the multicast/broadcast group that you wish to join.
  • the terminal or network element of the service can send a join request message to the source specific IP address, which can be used as a type of multicast/broadcast service identifier.
  • the reason why the UE sends the message may include that the message is used to request to receive data of the first multicast/broadcast service, or that the message is used to obtain configuration information for receiving the first multicast/broadcast service, or that the message is used to Triggering the establishment of a session of the first multicast/broadcast service (also called a first multicast/broadcast session), or the message is used to indicate that the first multicast/broadcast service is interested, or the message is used to Indicates a request to join the first multicast/broadcast service.
  • the message may carry the identification, cause value, index or indication information corresponding to at least one of the causes in the above examples to indicate the corresponding cause.
  • At least one of the above first message, second message or third message may also include the identification of the second base station.
  • the UE that has joined the first multicast/broadcast service and is in the RRC-inactive state determines that the base station is changed to the first base station, or when the UE determines that the cell is changed to the cell in the first base station, then The UE may send at least one of a first message, a second message, a third message, a ninth message or a tenth message to the first base station.
  • the first base station may learn that the UE moves to its coverage to receive the first multicast/broadcast service according to at least one of the first message, the second message, the third message, the ninth message or the tenth message. , to create the first multicast/broadcast session or update the first multicast/broadcast session context in a timely manner, to achieve effective management of the first multicast/broadcast session and improve network resource utilization.
  • the UE determines that the base station is changed to the first base station, or determines that the cell is changed to the cell of the first base station.
  • the UE has joined the first multicast/broadcast service and is in the RRC-inactive state.
  • the UE determines or finds that the data of the first multicast/MBS data received (no multicast/MBS data received) is not received, and the UE has joined the first multicast/broadcast service and In the RRC-inactive state.
  • the reason why the UE determines that it has not received the data of the first multicast/broadcast service may include that the UE changes the base station, or the UE changes the cell.
  • the UE can determine that the base station has changed and/or determine that the cell has changed according to the method introduced in S101.
  • the conditions that trigger the UE to perform S102 in this application include at least one of the following: the UE determines that the base station is changed to the first base station, for example, a base station different from the first base station is changed to the first base station; or, the UE determines that the base station is changed to the first base station.
  • Cell change for example, a cell that is different from the previously attached cell under the first base station or another cell that is not under the first base station; or the UE determines/finds that the data of the first multicast/broadcast service has not been received; or the UE moves out Registration area.
  • the processing method of the first base station after receiving at least one of the first message, the second message, the third message, the ninth message or the tenth message.
  • the processing method of the first base station at least includes method 1 and method 2 of the following processing methods.
  • the context of the first multicast/broadcast session may be updated through method 1. If at least one of the first message, the second message, the third message, the ninth message or the tenth message received by the first base station includes the identifier of the second base station, it may mean that the base station of the UE receives the information from the second base station. Change to the first base station, then this The context of the first multicast/broadcast session can be updated through method 2.
  • the first base station triggers the establishment of the first multicast/broadcast session.
  • the first base station can The first multicast/broadcast service is established, distributed or established to the cell; if the UE receives the first multicast/broadcast service, the first base station can update the first multicast/broadcast session context .
  • the first base station may receive the first message, the second message, and the third message.
  • the first base station can establish, distribute or establish the first multicast/broadcast service to the cell, so that the cell can learn in time
  • the new UE moves to its coverage area to receive the first multicast/broadcast service.
  • the first base station may update the context of the first multicast/broadcast session in response to the first message. For example, the first base station may add the identity of the UE to the first multicast session. /broadcast session context in the UE identification list of the cell of the first base station. In addition, the first base station may also add 1 to the number of UEs passing through the cell in the first multicast/broadcast session.
  • the first base station may also send the reception configuration of the first multicast/broadcast service to the UE.
  • the UE may send at least the first message in S102.
  • the reason why the UE does not receive the data of the first multicast/broadcast service may be that the UE has moved to the first base station where the first multicast/broadcast session has not been established before, or the UE has not obtained the first group in the current cell. Broadcast/broadcast service reception configuration. In method 1, it is only considered that the UE did not receive the corresponding data because it did not obtain the reception configuration of the first multicast/broadcast service in the current cell, because the UE has joined the first multicast/broadcast service before changing the cell, indicating that the first A base station has established a multicast/broadcast session. Therefore, when the first base station receives the first message from the UE, it may send the reception configuration to the UE, so that the UE receives the data of the first multicast/broadcast service according to the reception configuration.
  • the first base station may update the context of the first multicast/broadcast session in response to the second message.
  • the UE may send at least the second message in S102. Therefore, when receiving the second message, it means that the UE is still able to receive the data of the first multicast/broadcast service.
  • the first base station only needs to update the context of the first multicast/broadcast session and does not need to send the third message to the UE. Reception configuration for multicast/broadcast services.
  • the first base station can either trigger sending the data of the first multicast/broadcast service, or update the context of the first multicast/broadcast service, for example, in
  • the third message also carries a reason value, that is, the reason for sending the third message. In this way, the first base station can distinguish the reason for sending the third message.
  • method 2 can be divided into method 2.1, method 2.2, method 2.3, method 2.4, and method 2.5 according to the type of message sent by the UE in S102.
  • the message sent by the UE in S102 includes the first message; in method 2.2, the message sent by the UE in S102 includes the second message; in method 2.3, the message sent by the UE in S102 includes the third message.
  • the reason may be that the UE does not receive the data of the first multicast/broadcast service.
  • the UE has moved to the first base station where the first multicast/broadcast session has not been established before, or the UE has not obtained the reception configuration of the first multicast/broadcast service under the current base station. Therefore, when the first base station receives the first message from the UE, it needs to determine whether the first multicast/broadcast session has been established (or whether the context of the first multicast/broadcast session has been stored). According to the determination As a result, a different update operation of the context of the first multicast/broadcast session is performed.
  • the update operation of the first base station may include the implementation manner shown in manner 2.1.1 or manner 2.1.2.
  • the first base station can trigger the establishment of the first multicast/broadcast session, and obtain the context of the first multicast/broadcast session through the establishment process of the first multicast/broadcast session. That is to say, in manner 2.1.1, the updating operation of the context of the first multicast/broadcast session includes the first base station obtaining the context of the first multicast/broadcast session during the establishment process of the first multicast/broadcast session.
  • the first base station may also send the reception configuration of the first multicast/broadcast session to the UE after establishing the first multicast/broadcast session, so that the UE can
  • the receiving configuration performs reception of data of the first multicast/broadcast service.
  • the first base station can also authorize or check the UE that sent the first message, that is, because the context of the UE is still in the base station before changing to the first base station. , and the context of the UE also contains information about the first multicast/broadcast service that the UE joined before. Therefore, for example, the first base station can send a message to the base station before changing to the first base station, requesting authentication or checking whether the UE has joined the first multicast/broadcast service.
  • the first base station can trigger the establishment of the first multicast/broadcast session, and obtain the context of the first multicast/broadcast session through the establishment process of the first multicast/broadcast session.
  • the first base station can update the context of the first multicast/broadcast session.
  • the first base station may update the number of UEs joining the multicast/broadcast session in the context of the first multicast/broadcast session, so that the first base station can learn the number of UEs that receive the first multicast/broadcast session data at the base station. .
  • the first base station may also send the reception configuration of the first multicast/broadcast session to the UE, so that the UE performs the first multicast/broadcast service according to the reception configuration of the first multicast/broadcast session. Receipt of data.
  • the first base station can also authorize or check the UE that sent the first message, that is, because the context of the UE is still in the base station before changing to the first base station. , and the context of the UE also contains information about the first multicast/broadcast service that the UE joined before. Therefore, for example, the first base station can send a message to the base station before changing to the first base station, requesting authentication or checking whether the UE has joined the first multicast/broadcast service. If the feedback message is passed or the UE has joined the first multicast/broadcast service, broadcast service, the first base station can trigger an update to the first multicast/broadcast session context.
  • the first base station in S102 includes the second message, it means that the UE is still able to receive the data of the first multicast/broadcast service, that is to say, the first base station has stored the data of the first multicast/broadcast service.
  • the context of the session therefore the first base station only needs to update the stored context of the first multicast/broadcast session and does not need to send the reception configuration of the first multicast/broadcast service to the UE.
  • the process of the first base station updating the context of the first multicast/broadcast session can be found in Method 1 or Method 2.1.2, which will not be further elaborated here.
  • the first base station can also authorize or check the UE that sends the second message, that is, because the context of the UE is still before changing to the first base station. in the base station, and the context of the UE also contains information about the first multicast/broadcast service that the UE has joined before. Therefore, for example, the first base station can send a message to the base station before changing to the first base station, requesting authentication or checking whether the UE has joined the first multicast/broadcast service. If the feedback message is passed or the UE has joined the first multicast/broadcast service, broadcast service, the first base station can trigger an update to the first multicast/broadcast session context.
  • the first base station may update the context of the already stored first multicast/broadcast session in response to the third message.
  • Method 2.3 the process of the first base station updating the context of the first multicast/broadcast session can be found in Method 1 or Method 2.2, which will not be elaborated here.
  • the ninth message may be a service request message, it may indicate that the UE has not received the data of the first multicast/broadcast service, for example, the UE moves to The first base station does not support the UE receiving data of the first multicast/broadcast service in the RRC-inactive state.
  • the UE initiates (invoke) a service request message, carrying The first protocol data unit PDU session identifier is used to request activation of the first PDU session, thereby triggering the establishment of the first multicast/broadcast session.
  • the first PDU session is associated with the first multicast/broadcast service.
  • the association between the first PDU session and the first multicast/broadcast service can be understood as: the UE can request to join or exit the first multicast/broadcast service through the control plane signaling of the first PDU session. After the joining is successful, the first PDU The session can also be used to transmit data of the first multicast/broadcast service.
  • the tenth message may be a registration request message, it may indicate that the first base station to which the UE moves is outside the registration area of the UE. Then the UE initiates (invoke) a registration request message, carrying the first protocol data unit PDU session identifier, for requesting activation of the first PDU session, thereby triggering the establishment of the first multicast/broadcast session.
  • the first PDU session is associated with the first multicast/broadcast service.
  • the association between the first PDU session and the first multicast/broadcast service can be understood as: the UE can request to join or exit the first multicast/broadcast service through the control plane signaling of the first PDU session. After the joining is successful, the first PDU The session can also be used to transmit data of the first multicast/broadcast service.
  • the base station of the UE is changed from the second base station to the first base station. Therefore, in addition to the first base station needing to update the context of the first multicast/broadcast service, the second base station also needs to update the first multicast service. /Broadcast service context because the UE is no longer within the coverage of the second base station.
  • the first base station can send a message to the second base station, so that the second base station updates the context of the first multicast/broadcast service.
  • the fourth message, the fifth message, or the eighth message is An example is introduced. This application is not limited to the function of notifying or instructing the second base station to update the context of the first multicast/broadcast service through other messages.
  • the first base station may send the information of the second base station according to the information carried in the message. identification, and sends a fourth message, a fifth message, or an eighth message to the second base station, so that the second base station updates the context of the first multicast/broadcast session according to the fourth message, the fifth message, or the eighth message. Therefore, it can also be said that the fourth message and/or the fifth message and/or the eighth message are used to trigger the second base station to update the context of the first multicast/broadcast session.
  • the fourth message may be used by the second base station to update the context of the first multicast/broadcast session.
  • This fifth message may be used to extract the context of the UE.
  • the eighth message is used to authenticate whether the UE has joined the first multicast/broadcast service.
  • the fourth message, the fifth message, or the eighth message may be an Xn message, an X2 message, or a message sent between base stations.
  • the fourth message and/or the fifth message and/or the eighth message may include the UE identity and/or the identity of the first multicast/broadcast service.
  • the second base station may update the context of all multicast/broadcast sessions associated with the UE identity. For example, delete the identity of the UE from the context of all multicast/broadcast sessions that include the identity of the UE, and/or subtract the number of UE identities from the number of UEs joining these multicast/broadcast sessions. If the fourth message and/or the fifth message and/or the eighth message includes the identifier of the first multicast/broadcast service, the second base station may associate the first multicast with the identifier of the first multicast/broadcast service.
  • the context of the first multicast/broadcast session such as deleting the UE identity from the context of the first multicast/broadcast session, and/or adding the context of the first multicast/broadcast session to the first multicast/broadcast session.
  • the number of UEs in the session minus the number of UE identifiers. It should be understood that the number of UE identifiers here may be one or more. For example, the method shown in Figure 6 is executed after one or more UEs move.
  • the second base station can also authenticate or check whether the UE has joined the first multicast/broadcast session. For example, only after the authentication or check is successful, the second base station will send the message to the first base station. Sixth news.
  • the second base station When the second base station receives the fourth message and/or the fifth message, it updates the context of the first multicast/broadcast session and updates the resources of the multicast/broadcast session in a timely manner, thereby improving network resource utilization.
  • the second base station updates the context of the first multicast/broadcast service, the number of UEs joining the first multicast/broadcast service in the context is 0, or the number of UEs joining the first multicast/broadcast service
  • the identifier is empty, that is, the identifier of the UE that first joined the first multicast/broadcast service or the UE does not exist, then the second base station can release the first multicast/broadcast session or release the first multicast/broadcast session. Shared multicast/broadcast service traffic transmission.
  • the second base station determines that the first timer has expired, and the second base station can release the first transmission resource, where the first transmission resource is used to transmit the first multicast/broadcast service.
  • the first transmission resource may be a first multicast/broadcast session, or the first transmission resource may be shared multicast/broadcast service traffic transmission.
  • the first timer may be a periodic access network notification area update timer (periodic RAN notification area update, RNAU) Timer).
  • the first base station may send a fifth message to the second base station, and the second base station may send the fifth message to the first base station according to the fifth message.
  • UE context UE context.
  • the second base station may also send a sixth message to the first base station, where the sixth message may include the configuration of the first multicast/broadcast service (which may be referred to as the first configuration) , the first configuration may be used to transmit data of the first multicast/broadcast service.
  • the first configuration may include point-to-multipoint configuration (PTM configuration), and the first configuration may also include point-to-multipoint control information ( PTM control information), the first configuration can also Including multicast/broadcast service configuration (MBS configuration), the first configuration may also include point-to-multipoint control information (PTM control information).
  • the sixth message may also include context information of the UE.
  • the context information of the UE may include related information of the UE.
  • the identification information may be the I-RNTI.
  • the I-RNTI may be the The I-RNTI newly generated by the second base station;
  • the context information of the UE may also include the information of the PDU session of the UE.
  • the information of the PDU session may include the parameter information of the QoS flow included in the PDU session;
  • the context information of the UE may also include the period Periodic access network notification area timer (periodic RNAU timer).
  • the sixth message may further include information about the first multicast/broadcast service.
  • the first base station may send a seventh message to the UE, where the seventh message includes the first configuration or first capability information.
  • the first configuration includes a configuration for receiving the first multicast/broadcast service; the first capability information is used to indicate whether the first base station supports RRC-inactive state reception (or the first capability information is used to Data indicating whether the first base station supports the UE receiving the multicast/broadcast service (or the first multicast/broadcast service) in the RRC-inactive state), the first capability information may be sent when the first base station supports the capability.
  • the first capability information may be in the form of bits. For example, when the value is 1, it indicates that RRC-inactive state reception is supported; when the value is 0, it indicates that RRC-inactive state reception is not supported; or, when the value is 1, it indicates that RRC-inactive state reception is not supported; When the value is 0, it means that RRC-inactive state reception is supported. When the value is 1, it means that RRC-inactive state reception is not supported.
  • the first capability information may be of an enumeration type.
  • the value is a certain integer, it indicates that RRC-inactive reception is supported.
  • the value is another integer, it indicates that RRC-inactive is not supported. State reception.
  • the first capability information may be one or more information elements (IE).
  • IE information elements
  • the indication of whether radio resource control deactivation state reception is supported can be understood as:
  • the UE can learn that the first multicast/broadcast service is going to be transferred and does not need to initiate a service request. (not need perform Service Request) message, the service request message can be understood as a type of ninth message, the service request message.
  • the UE initiates (invoke) a service request message carrying the first protocol data unit PDU session identifier for requesting activation of all Describe the first PDU session, thereby triggering the establishment of the first multicast/broadcast session.
  • the first PDU session is associated with the first multicast/broadcast service. It should be understood that the association of the first PDU session with the first multicast/broadcast service can be understood as the UE can request to join or exit the first multicast/broadcast service through the control plane signaling of the first PDU session. After the join is successful, The first PDU session may also be used to transmit data of the first multicast/broadcast service.
  • a communication method based on the above method 2.1 provided by this application may include the following steps:
  • the UE determines that the base station is changed to the first base station or the cell is changed to the cell of the first base station, and/or the UE determines/finds that the data of the first multicast/broadcast service has not been received.
  • the UE sends a first message to the first base station, where the first message may instruct the first base station to send data of the first multicast/broadcast service, or the first message may instruct the first base station to send the first multicast/broadcast service.
  • the reception configuration of the service, or the first message may be used to indicate interest in the first multicast/broadcast service (indicate interest on the related MBS session).
  • the first base station receives the first message.
  • the first base station determines whether the first multicast/broadcast session has been established, and/or the first base station determines whether the context of the first multicast/broadcast session is stored.
  • S205 and S206 are executed. .
  • the first base station triggers the establishment of the first multicast/broadcast session, and obtains the context of the first multicast/broadcast session during the establishment process of the first multicast/broadcast session.
  • the first base station updates the context of the first multicast/broadcast session.
  • the first base station sends data and/or reception configuration of the first multicast/broadcast service to the UE.
  • the receiving configuration may be obtained in the process of establishing the first multicast/broadcast session through S204. If S205 is performed, the receiving configuration may be obtained by the first base station in the previous process of establishing the first multicast/broadcast session.
  • the first message in S202 may include the identity of the second base station or the identity of the UE.
  • the first base station obtains the identity of the second base station in the first message, or obtains the identity of the UE in the first message and identifies the source base station of the UE according to the identity of the UE (last serving NG-RAN/last serving gNB/source NG -RAN) is the second base station (that is, the base station of the UE is changed from the second base station to the first base station), then after S202 shown in Figure 7, the following steps can also be performed:
  • the first base station may send at least one of the fourth message, the fifth message or the eighth message to the second base station.
  • the fourth message may be used to notify the second base station to update the context of the first multicast/broadcast session.
  • the fifth message can be used to extract the context of the UE.
  • the eighth message may be used to authenticate whether the UE has joined the first multicast/broadcast service, and the eighth message may carry the UE identifier and the first multicast/broadcast service identifier.
  • the fourth message, the fifth message and the eighth message may all be Xn messages or X2 messages, that is, they may all be messages used for communication between base stations.
  • At least one of the fourth message, the fifth message or the eighth message may include the identity of the first multicast/broadcast session and/or the identity of the UE.
  • the second base station receives at least one of the fourth message, the fifth message or the eighth message.
  • the second base station may update the context of the first multicast/broadcast session in the second base station in response to at least one of the fourth message, the fifth message, or the eighth message.
  • the second base station may modify the first multicast/broadcast session based on the identity of the UE carried in at least one of the fourth message, the fifth message, or the eighth message and/or the identity of the first multicast/broadcast service.
  • the context is updated. For details, please refer to the description in this application and will not be repeated here.
  • the second base station may authenticate or check the UE according to the identifier of the UE carried in the eighth message and the identifier of the first multicast/broadcast service, that is, authenticate whether the UE has joined the third group.
  • Multicast/broadcast service for example, if the second base station finds that there is no UE identification in the stored first multicast/broadcast service context or there is no information about the first multicast/broadcast service in the UE context, the authentication fails; If the second base station finds that the stored first multicast/broadcast service context contains the identification of the UE or the UE context contains the information of the first multicast/broadcast service, the authentication is successful.
  • the second base station sends a response message to at least one of the fourth message, the fifth message, or the eighth message to the first base station.
  • the response message may be a sixth message, and the sixth message may be an Xn message or an X2 message or may be a message used for communication between base stations.
  • the sixth message may include context information of the UE.
  • the context information of the UE may include related information of the UE. For example, it may include identification information of the UE, and the identification information may be I-RNTI. For example, this I-RNTI may be a newly generated I-RNTI by the second base station.
  • the context information of the UE may also include information of the PDU session of the terminal device. For example, the PDU session information may include QoS flow parameter information included in the PDU session.
  • the context information of the UE may also include a periodic access network notification area timer (periodic RNAU timer).
  • the sixth message may further include information about the first multicast/broadcast service.
  • the information about the first multicast/broadcast service may include an identifier of the first multicast/broadcast service, a group name of the first multicast/broadcast service.
  • Broadcast/broadcast QoS information, multicast/broadcast QoS information may include multicast/broadcast QoS parameters, etc.
  • the UE may report to the first base station.
  • the base station sends the first message, so that the first base station promptly updates the context of the first multicast/broadcast service according to the second message, triggers the first base station to establish the first multicast/broadcast session, and triggers the second base station to update the first multicast/broadcast session according to the second message.
  • Context for multicast/broadcast services are possible.
  • S201 corresponds to S101 shown in Figure 6, that is to say, S201 is an implementation of S101.
  • S202 in Figure 7 corresponds to S102 in Figure 6, that is to say, S202 is an implementation of S102.
  • a communication method based on the above method 2.2 provided by this application may include the following: step:
  • S301 The UE determines that the base station is changed to the first base station or the cell is changed to the cell of the first base station, and/or the UE determines that data of the first multicast/broadcast service is received.
  • S302 The UE sends a second message to the first base station, where the second message may be used to instruct the first base station to update the context of the first multicast/broadcast service.
  • the first base station receives the second message.
  • the first base station updates the context of the first multicast/broadcast session.
  • the first base station may also send a response message to the second message to the UE.
  • the second message in S302 may include the identity of the second base station or the identity of the UE.
  • S304 The first base station sends at least one of the fourth message, the fifth message or the eighth message to the second base station.
  • the fourth message may be used to notify the second base station to update the context of the first multicast/broadcast session.
  • the fifth message can be used to extract the context of the UE.
  • the eighth message may be used to authenticate whether the UE has joined the first multicast/broadcast service, and the eighth message may carry the UE identifier and the first multicast/broadcast service identifier.
  • the fourth message, the fifth message and the eighth message may all be Xn messages or X2 messages, that is, they may all be messages used for communication between base stations.
  • At least one of the fourth message, the fifth message or the eighth message may include the identity of the first multicast/broadcast session and/or the identity of the UE.
  • the second base station receives at least one of the fourth message, the fifth message or the eighth message.
  • the second base station may update the context of the first multicast/broadcast session in the second base station in response to at least one of the fourth message, the fifth message, or the eighth message.
  • the second base station may modify the first multicast/broadcast session based on the identity of the UE carried in at least one of the fourth message, the fifth message, or the eighth message and/or the identity of the first multicast/broadcast service.
  • the context is updated. For details, please refer to the description in this application and will not be repeated here.
  • the second base station may release the first multicast/broadcast session or release the shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the second base station determines that the first timer has expired, and the second base station may release the first multicast/broadcast session or release the shared multicast/broadcast service traffic of the first multicast/broadcast session. transmission.
  • the first timer may be a periodic access network notification area update timer (periodic RNAU Timer).
  • the second base station sends a response message to at least one of the fourth message, the fifth message, or the eighth message to the first base station.
  • the response message may be a sixth message, and the sixth message may be an Xn message or an X2 message or may be a message used for communication between base stations.
  • the response message may be a sixth message.
  • the sixth message may include context information of the UE, and the context information of the UE may include related information of the UE. For example, it may include identification information of the UE, and the identification information may be I-RNTI. For example, this I-RNTI may be a newly generated I-RNTI by the second base station.
  • the context information of the UE may also include information of the PDU session of the terminal device.
  • the PDU session information may include QoS flow parameter information included in the PDU session.
  • the context information of the UE may also include a periodic access network notification area timer (periodic RNAU timer).
  • the sixth message may also include information about the first multicast/broadcast service, and the information about the first multicast/broadcast service may include an identifier of the first multicast/broadcast service.
  • Multicast/broadcast QoS information, the multicast/broadcast QoS information may include multicast/broadcast QoS parameters, etc.
  • the second base station may release the first multicast/broadcast session or release the shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the UE may send a request to the first base station.
  • the base station sends the second message, so that the first base station promptly updates the context of the first multicast/broadcast service according to the second message, and triggers the second base station to update the context of the first multicast/broadcast service according to the second message.
  • S301 corresponds to S101 shown in Figure 6, that is to say, S301 is an implementation of S101.
  • S302 in Figure 8 corresponds to S102 in Figure 6 , that is to say, S302 is an implementation of S102.
  • the UE determines/finds that it has moved out of the RNA area, and/or the UE determines/finds that the data of the first multicast/broadcast service has not been received (or has not been received). Among them, the UE determines/finds that it has moved out of the RNA area. For example, the base station is changed to the first base station or the cell is changed to the cell of the first base station and the changed first base station or the changed cell of the first base station is outside the RNA area, and the UE determines to receive Data to the first multicast/broadcast service.
  • S401 may be replaced by, the UE determines/finds to move out of the RNA area, for example, the base station is changed to the first base station or the cell is changed to the cell of the first base station and the changed first base station or the changed cell of the first base station is outside the RNA area.
  • S401 can be replaced by: the UE received the data of the first multicast/broadcast service, but found that it moved out of the RNA area.
  • S401 can be replaced by: the UE determines/finds that it has not received the data of the first multicast/broadcast service, and also finds that it has moved out of the RNA area.
  • the UE sends a third message to the first base station, where the third message can be used to restore the RRC connection of the UE.
  • the first base station receives the third message.
  • the first base station updates the context of the first multicast/broadcast session.
  • the second message in S402 may include the identity of the second base station or the identity of the UE.
  • the first base station obtains the identity of the second base station in the second message, or obtains the identity of the UE in the second message and identifies the serving base station of the UE as the second base station according to the identity of the UE, then in S402 shown in Figure 8 Afterwards, you can also perform the following steps:
  • S404 The first base station sends at least one of the fourth message, the fifth message or the eighth message to the second base station.
  • the fourth message may be used to notify the second base station to update the context of the first multicast/broadcast session.
  • the fifth message can be used to extract the context of the UE.
  • the eighth message may be used to authenticate whether the UE has joined the first multicast/broadcast service, and the eighth message may carry the UE identifier and the first multicast/broadcast service identifier.
  • the fourth message, the fifth message and the eighth message may all be Xn messages or X2 messages, that is, they may all be messages used for communication between base stations.
  • At least one of the fourth message, the fifth message or the eighth message may include the identity of the first multicast/broadcast session and/or the identity of the UE.
  • the second base station receives at least one of the fourth message, the fifth message or the eighth message.
  • the second base station may update the context of the first multicast/broadcast session in the second base station in response to at least one of the fourth message, the fifth message, or the eighth message.
  • the second base station may modify the first multicast/broadcast session based on the identity of the UE carried in at least one of the fourth message, the fifth message, or the eighth message and/or the identity of the first multicast/broadcast service.
  • the context is updated. For details, please refer to the description in this application and will not be repeated here.
  • the second base station may release the first multicast/broadcast session or release the shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the second base station determines that the first timer has expired, and the second base station may release the first multicast/broadcast session or release the shared multicast/broadcast service traffic of the first multicast/broadcast session. transmission.
  • the first timer may be a periodic access network notification area update timer (periodic RNAU Timer).
  • the second base station sends a response message to at least one of the fourth message, the fifth message, or the eighth message to the first base station.
  • the response message may be a sixth message, and the sixth message may be an Xn message or an X2 message or may be a message used for communication between base stations.
  • the response message may be a sixth message.
  • the sixth message may also include context information of the UE.
  • the context information of the UE may include related information of the UE. For example, it may include identification information of the UE, and the identification information may be I. -RNTI, for example, this I-RNTI can be the I-RNTI newly generated by the second base station; the context information of the UE can also include the information of the PDU session of the terminal device, for example, the information of the PDU session can include the QoS included in the PDU session. flow parameter information; the context information of the UE may also include a periodic access network notification area timer (periodic RNAU timer).
  • the sixth message may further include information about the first multicast/broadcast service.
  • the information about the first multicast/broadcast service may include an identifier of the first multicast/broadcast service, a group name of the first multicast/broadcast service.
  • Broadcast/broadcast QoS information, multicast/broadcast QoS information may include multicast/broadcast QoS parameters, etc.
  • the first base station sends the seventh message to the UE.
  • the UE can learn the third Groupcast/Broadcast The service is going to be transferred and there is no need to initiate a service request message.
  • the service request message can be understood as a type of ninth message. If the seventh message does not carry the first capability information and the UE has not received the first multicast/broadcast service, the UE initiates a service request message carrying the associated PDU session identifier to request activation of the associated PDU session. This then triggers the establishment of the first multicast/broadcast session.
  • the associated PDU session is associated with the first multicast/broadcast service. It should be understood that the association of the associated PDU session with the first multicast/broadcast service can be understood as the UE can request to join or exit the first multicast/broadcast service through the control plane signaling of the associated PDU session. After the joining is successful, The associated PDU session can also be used to transmit data of the first multicast/broadcast service.
  • the UE when the UE moves out of the RNA area and/or the UE determines that the data of the first multicast/broadcast service has not been received, the UE can send a third message to the first base station, so that the first base station can The third message updates the context of the first multicast/broadcast service in a timely manner, and triggers the second base station to update the context of the first multicast/broadcast service based on the second message.
  • S401 corresponds to S101 shown in Figure 6, that is to say, S401 is an implementation of S101.
  • S402 in Figure 9 corresponds to S102 in Figure 6, that is to say, S402 is an implementation of S102.
  • the embodiment of the present application also provides another communication method to use after the UE moves out of the registration area or moves out of the RNA area, for example, the UE's changed base station or changed cell is registered.
  • the base station can promptly establish the first multicast/broadcast session or update the context of the first multicast/broadcast session to improve network resource utilization.
  • the method can be implemented by terminal equipment (such as UE), mobility management network element (such as AMF), session management network element (such as SMF) and access network equipment (such as base station).
  • terminal equipment such as UE
  • mobility management network element such as AMF
  • session management network element such as SMF
  • access network equipment such as base station.
  • the following description takes the execution subjects as UE, AMF, SMF and base station as an example.
  • the communication method may include the following steps:
  • S501 The UE determines to move out of the registration area or the RNA area, and/or the UE determines that it has not received (or not received) the data of the first multicast/broadcast service.
  • the UE determines to move out of the registration area or out of the RNA area.
  • the base station is changed to the first base station and the first base station is outside the registration area, or the base station is changed to the first base station and the first base station is outside the RNA area, or the cell is changed to The cell of the first base station is outside the registration area, or the cell is changed to the cell of the first base station and the cell is outside the RNA, or the UE determines that data of the first multicast/broadcast service is not received.
  • the UE determines/finds that it has moved out of the registration area or RNA area, for example, the base station is changed to the first base station or the cell is changed to the cell of the first base station and the changed first base station or the changed cell of the first base station is in the registration area or RNA area. outside.
  • the UE receives the data of the first multicast/broadcast service, but finds that it has moved out of the registration area or RNA area.
  • the UE determines/finds that it has not received the data of the first multicast/broadcast service, and also finds that it has moved out of the registration area or RNA area.
  • the UE in S501 has joined the first multicast/broadcast service and is in a deactivated state.
  • S502 The UE sends the ninth message or the tenth message to the first base station.
  • the first base station receives the ninth message or the tenth message.
  • the ninth message may include a service request (service request) or uplink non-access layer data transmission (UL NAS transport); the tenth message may include a registration request (registration request).
  • service request service request
  • UL NAS transport uplink non-access layer data transmission
  • registration request registration request
  • the first message may also include: an identifier of the PDU session used by the UE to join the first multicast/broadcast service.
  • the PDU session used by the UE to join the multicast service may be called an associated PDU session identifier. (associated PDU session ID).
  • the first base station sends the ninth message or the tenth message to the AMF, carrying the associated PDU session identifier.
  • S504 According to the control plane connection corresponding to the associated PDU session, AMF sends a PDU session context update request (Nsmf_PDUSession_UpdateSMContext request) to SMF.
  • Nsmf_PDUSession_UpdateSMContext request a PDU session context update request
  • the PDU session context update request corresponds to the associated PDU session.
  • the SMF receives the PDU session context update request.
  • SMF determines N2 session management information (N2 session management info, N2 SM Info).
  • the N2 session management information may carry information about the first multicast/broadcast service, for example, the identifier of the first multicast/broadcast service and/or the QoS parameter information of the first multicast/broadcast service.
  • the base station here is the base station where the UE is currently located, that is, the first base station.
  • the SMF executes S505.
  • S506 SMF sends N2 SM Info to AMF.
  • the N2 SM Info may be included in the PDU session context update response message.
  • AMF receives the N2 SM Info.
  • AMF sends an N2 message to the base station, which carries the N2 SM Info.
  • the base station receives the N2 message.
  • the first base station determines whether the first multicast/broadcast session has been established based on the information of the first multicast/broadcast service.
  • the first base station triggers the establishment of the first multicast/broadcast session, and obtains the first multicast session in the process of establishing the first multicast/broadcast session. /Context of the broadcast session, and configure the reception of the first multicast/broadcast data according to the QoS information in the context.
  • the first base station may also send the data and/or reception configuration of the first multicast/broadcast service to the UE.
  • the first base station may send data and/or receive configuration of the first multicast/broadcast data.
  • the first base station may send the reception configuration through a non-UE channel.
  • the first base station may send the reception configuration through MCCH or MCH or the like.
  • the first base station may send the reception configuration to the UE through an RRC message.
  • the UE when the UE has joined the first multicast/broadcast service and is in the RRC-inactive state, if the UE determines to move out of the registration area or RNA area, and/or determines that it has not received the first multicast/broadcast service data, the UE may send the ninth message or the tenth message to the AMF, so that the network side notifies the base station to establish a session of the first multicast/broadcast service or sends a reception configuration for receiving data of the first multicast/broadcast service. , enabling the UE to recover/receive data of the first multicast/broadcast service.
  • the embodiment of the present application also provides another communication method to enable the base station to promptly establish the first multicast/broadcast session and/or update the context of the first multicast/broadcast session when the UE moves within the RNA area, so as to Improve network resource utilization.
  • the method may be implemented by a third access network device (eg, a third base station) and a fourth access network device (eg, a fourth base station).
  • a third access network device eg, a third base station
  • a fourth access network device eg, a fourth base station.
  • the following description takes the execution subjects as UE, AMF, SMF and base station as an example.
  • the communication method may include the following steps:
  • the third base station establishes a first multicast/broadcast session, and the first multicast/broadcast session is used to transmit data of the first multicast/broadcast service.
  • the third base station may establish the first multicast/broadcast session based on the UE's request to join the first multicast/broadcast service.
  • the first multicast/broadcast session includes 5G core network shared multicast/broadcast service traffic delivery (5GC shared MBS traffic delivery).
  • the third base station may receive a message requesting to join the first multicast/broadcast service sent from the core network, for example, the SMF, and the request message may carry an identifier of the first multicast/broadcast service.
  • the third base station may establish the first multicast/broadcast session in response to the request message.
  • the third base station sends a first indication to at least one fourth base station, where the first indication is used to instruct or trigger the fourth base station to establish a multicast/broadcast session of the first multicast/broadcast service (ie, the first multicast/broadcast session) or shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the first indication is used to instruct or trigger the fourth base station to establish a multicast/broadcast session of the first multicast/broadcast service (ie, the first multicast/broadcast session) or shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the fourth base station and the third base station are located or in the same RNA region.
  • At least one fourth base station may establish the first multicast/broadcast session in response to the first indication.
  • the third base station can trigger other base stations in the RNA area (ie, the fourth base station) to establish the first group through the first instruction. Therefore, even if the UE moves from the coverage area of the third base station to the coverage area of other fourth base stations, since the fourth base station has established the first multicast/broadcast session, the UE can receive the third multicast/broadcast session from the fourth base station.
  • Multicast/broadcast service data does not require the fourth base station to establish the first multicast/broadcast session, which can reduce the transmission delay of the multicast/broadcast service and improve service quality.
  • the UE can notify the third base station and/or the fourth base station to update the first multicast according to the methods shown in Figures 6 to 10 provided by the embodiments of this application. /broadcast session.
  • process shown in Figure 11 may also include the following steps:
  • the third base station determines or finds that there is no UE receiving the first multicast/broadcast service/session.
  • the non-existence of the UE receiving the first multicast/broadcast session here may be because the UE has exited the service, or the UE has moved out of the coverage of the third base station, etc., without any specific requirements. For example, when there is no identification of any terminal device in the session context of the first multicast/broadcast service, or the number of terminal devices in the session context is 0, the base station determines or finds that there is no UE to receive the first multicast service. /broadcast services/session.
  • the base stations in the RNA (including the third base station and the fourth base station) release the first multicast/broadcast session or release the first multicast/broadcast session. Shared multicast/broadcast service traffic transmission for multicast/broadcast sessions. Otherwise, even if there is no UE in the third base station to receive the first multicast/broadcast service, as long as there is still a UE in any base station in the same RNA to receive the first multicast/broadcast service, the third base station will not release the first multicast service. /Broadcast session or multicast/broadcast service traffic transmission without releasing the first multicast/broadcast session.
  • the third base station may receive a second indication from at least one fourth base station, where the second indication is used to indicate that the fourth access network device does not exist and the UE receives the third A multicast/broadcast service, or the second indication may be used to indicate that there is also data for the UE to receive the first multicast/broadcast service. Therefore, the third base station can determine whether there are UEs in other base stations in the RNA to receive the first multicast/broadcast service according to the second indication, and further can determine based on the second indication. It is determined based on the judgment whether to trigger the release of the first multicast/broadcast session or the shared multicast/broadcast service traffic transmission of the first multicast/broadcast session.
  • the third base station may send a third indication to at least one fourth base station.
  • the third indication may be used to instruct the last UE of the third base station to exit.
  • the first multicast/broadcast service, or the third indication may be used to confirm whether all terminal devices in the fourth access network device exit the first multicast/broadcast service, or the third indication may be used to indicate that there is no third base station.
  • the UE receives the data of the first multicast/broadcast service.
  • the third base station may send a third indication to the fourth base station.
  • any fourth base station may determine whether there is still a UE receiving the first multicast/broadcast service. If there is no UE receiving the first multicast/broadcast service at the fourth base station, it may send a message to the third base station.
  • the second indication otherwise, if there is at least one UE receiving the first multicast/broadcast service, the fourth base station does not send the second indication, and the fourth base station may send the fourth indication to indicate that there is still a UE receiving the first multicast service. /broadcasting business. If the third base station receives the second indication sent by the fourth base station, it may be determined that no UE receives the first multicast/broadcast service in all base stations in the RNA.
  • the second indication may also be obtained by the third base station from other fourth base stations before the third base station sends the third indication.
  • the second indication may be sent by the fourth base station after determining that there is no UE receiving the first multicast/broadcast service. For example, before the third base station discovers that there is no UE receiving the first multicast/broadcast service, it receives a second indication from at least one fourth base station.
  • the second indication from the fourth base station may indicate that there is no UE receiving the first multicast/broadcast service.
  • the third base station can determine the number of all base stations in the RNA after receiving the second indication from the fourth base station and after the third base station does not have a UE receiving the first multicast/broadcast service. There is no UE receiving the first multicast/broadcast service, so the release of the first multicast/broadcast session can be performed/triggered or the shared multicast/broadcast service traffic transmission of the first multicast/broadcast session can be released.
  • the third base station may also send a fifth indication to other fourth base stations. The fifth indication may be used to trigger the fourth base station to release the first multicast/broadcast session of the fourth base station or release the first group. Multicast/broadcast service traffic transmission for multicast/broadcast sessions.
  • any one of the above first indication, second indication, third indication, fourth indication or fifth indication may include the identifier of the first multicast/broadcast service.
  • first instruction, second instruction, third instruction, fourth instruction or fifth instruction can also be implemented by messages, instruction information or logos, etc., and are not specifically limited in this application.
  • embodiments of the present application also provide a communication device.
  • the structure of the device is shown in Figure 14, including a transceiver module (or communication module) 1401 and a processing module 1402.
  • the transceiver module 1401 may include a receiving module. At least one of the module and the sending module is used to implement at least one of receiving and sending information.
  • the processing module 1402 can be used to generate information sent by the transceiving module 1401, or to perform processing on the information received by the transceiving module 1401. deal with.
  • the processing module 1402 may also be used to perform actions other than receiving and sending involved in the above method embodiments.
  • the device 1400 can be applied to terminal equipment, first access network equipment, second access network equipment, mobility management network elements, session management network elements, access network equipment, third access network equipment and fourth access In at least one of the network devices, to implement the communication methods shown in Figures 6 to 13.
  • the communication device may include a terminal equipment.
  • the processing module 1402 may be used to determine that the access network device is changed to the first access network device, or to determine that the cell is changed to the cell of the first access network device, and the terminal device has joined The first multicast/broadcast service is in an RRC deactivated state. And/or, the processing module 1402 may be used to determine that the first multicast/broadcast service is not received The data indicates that the terminal device has joined the first multicast/broadcast service and is in the radio resource control deactivated state.
  • the transceiver module 1401 may be configured to send at least one of a first message, a second message, a third message, a ninth message, or a tenth message to the first access network device; wherein the first message is used to indicate that the The first access network device sends data of the first multicast/broadcast service; the second message is used to instruct the first access network device to update the context of the first multicast/broadcast service; The third message is used to restore the RRC connection of the terminal device; the ninth message is used to activate the user plane connection; and the tenth message is used to request registration.
  • the terminal device allows receiving multicast/broadcast in the radio resource control deactivated state.
  • the transceiver module 1401 may also be configured to receive first information, where the first information includes an identification of the first access network device and/or an identification number of a cell of the first access network device. logo.
  • the processing module 1402 may also be configured to determine, according to the first information, that the access network device is changed to the first access network device, or to determine that the cell is changed to the cell of the first access network device.
  • the transceiver module 1401 may also be configured to receive second information, where the second information is used to indicate at least one of the following: the first information occupied by the identity of the access network device number of bits; or the second information is used to indicate the encoding method of the identity of the access network device in the first information; or the second information is used to indicate the encoding method of the identity of the cell in the first information.
  • the transceiver module 1401 may also be configured to receive (or receive or determine receipt of) data of the first multicast/broadcast service, and send the second data to the first access network device. message and/or the third message, or sending the second message and/or the ninth message, or sending the second message and/or the tenth message.
  • the processing module 1402 can also be used to determine (or discover) that there is no (or not received) transmission of the first multicast/broadcast service, and the transceiver module 1401 can also be used to send a message to the first access
  • the network device sends the first message and/or the third message, or sends the first message and/or the ninth message, or sends the first message and/or the tenth message.
  • At least one of the first message, the second message or the third message includes an identification of the terminal device, the first multicast/broadcast service The identification, the first protocol data unit PDU session identification, or at least one of the reasons for sending the message (or the reasons for sending the message), the first PDU session and the first multicast /broadcast business association.
  • the transceiver module 1401 may also be configured to receive information of a first area, where the first area is a service area of the second access network device.
  • the processing module 1402 can also be used to determine to move out of the first area, and the transceiving module 1401 can also be used to send the third message.
  • the processing module 1402 determines that the access network device is changed from the second access network device to the first access network device, then the first message, the second message or the third message At least one of them includes the identification and/or address of the second access network device.
  • the processing module 1402 can also be used to determine to move out of the access network notification area, and the transceiving module 1401 can also be used to send a ninth message.
  • the processing module 1402 can also be used to determine to move out of the registration area, and the transceiving module 1401 can also be used to send the tenth message. Therefore, the terminal device may send the tenth message when it determines that the data of the first multicast/broadcast service has not been received and determines to move out of the registration area.
  • the transceiver module 1401 may also be configured to receive a seventh message from the first access network device, where the seventh message includes the first configuration or first capability information; the first The configuration includes a configuration for receiving the first multicast/broadcast service; the first capability information is used to indicate whether the first access network device supports wireless resources.
  • the source controls RRC deactivation state reception, or the first capability information is used to indicate whether the first access network device supports receiving the first multicast/broadcast service in the RRC deactivation state, or the first capability information is used to indicate Whether the first access network device supports the UE in receiving the data of the first multicast/broadcast service in the RRC deactivated state.
  • the communication device may include the first access network device.
  • the transceiver module 1401 may be configured to receive at least one of the first message, the second message, the third message, the ninth message or the tenth message from the terminal device, wherein: The first message is used to notify/instruct to send the first multicast/broadcast data that the terminal device has joined the first multicast/broadcast service and is in the wireless resource control deactivation state; the second message is used to Notify/instruct the first access network device to update the context of the first multicast/broadcast service; the third message is used to restore the RRC connection of the terminal device; the ninth message is used to activate the user plane connection; the tenth message is used to request registration; at least one of the first message, the second message or the third message includes the identification and/or address of the second access network device.
  • the transceiver module 1401 may also be configured to send a fourth message, a fifth message, or an eighth message to the second access network device according to the identifier and/or address of the second access network device, where the fourth message is In order to update the context of the first multicast/broadcast service, the fifth message is used to extract the context of the terminal device, and the eighth message is used to authenticate whether the terminal device has joined the first group. broadcasting/broadcasting business.
  • the transceiver module 1401 may also be configured to send the ninth message or the tenth message to the access management network element, where the ninth message or the tenth message carries the first protocol data.
  • Unit PDU session identifier the ninth message or the tenth message carries the first protocol data unit PDU session identifier for activating the first PDU session or for activating the connection of the first PDU session, so The first PDU session is associated with the first multicast/broadcast service.
  • At least one of the first message, the second message or the third message may include the identification of the terminal device and/or the first multicast/broadcast service logo.
  • the fourth message, the fifth message, or the eighth message includes an identity of the terminal device and/or an identity of the first multicast/broadcast service.
  • the transceiver module 1401 may also be configured to receive a sixth message from the second access network device, where the sixth message includes at least one of the following information: first configuration, the terminal Context information of the device, information about the first multicast/broadcast service, and first capability information; the first configuration includes a configuration for receiving the first multicast/broadcast service; the first access network The device sends a seventh message, where the seventh message includes the first configuration or first capability information; the first capability information is used to indicate whether the first access network device supports the UE in the RRC deactivation state to receive the Data for the first multicast/broadcast service.
  • the communication device may include the first access network device.
  • the transceiver module 1401 may be used by the second access network device to receive at least one of the fourth message, the fifth message, or the eighth message from the first access network device, wherein , the fourth message is used to update the context of the first multicast/broadcast service, the fifth message is used to extract the context of the terminal device, and the eighth message is used to authenticate whether the terminal device The first multicast/broadcast service has been joined, and the terminal device has joined the first multicast/broadcast service and is in a radio resource control deactivated state.
  • the processing module 1402 may be used to update the context of the first multicast/broadcast service.
  • the fourth message, the fifth message, or the eighth message includes an identity of the terminal device and/or an identity of the first multicast/broadcast service.
  • the processing module 1402 may also be configured to update all the terminal devices according to the number of terminal devices.
  • At least one of the fourth message, the fifth message, or the eighth message includes an identification of the terminal device, and the second access network device can also delete (or move (except) the identity of the terminal device in the context of the first multicast/broadcast service.
  • the transceiver module 1401 may also be configured to send a sixth message to the first access network device, where the sixth message includes a first configuration, and the first configuration includes a method for receiving Configuration of the first multicast/broadcast service.
  • the transceiver module 1401 may also be configured to send information of a first area to the terminal device, where the first area includes at least one of the following: an identification of the second access network device , the cell included in the second access network device, the tracking area code of the second access network device, the access network area code of the second access network device, and the service area of the second access network device.
  • the processing module 1402 may also be used to determine that the first timer has expired, and the second access network device releases a first transmission resource, and the first transmission resource is used to transmit the first group broadcasting/broadcasting business.
  • the first transmission resource includes a first multicast/broadcast session.
  • the communication device 1500 may include at least one of a transceiver 1501 , a processor 1502 and a memory 1503 .
  • the transceiver 1501, the processor 1502 and the memory 1503 are connected to each other.
  • the transceiver 1501, the processor 1502 and the memory 1503 are connected to each other through a bus 1504.
  • the bus 1504 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in Figure 15, but it does not mean that there is only one bus or one type of bus.
  • the transceiver 1501 is used to receive and send data to implement communication with other devices.
  • the transceiver 1501 may be used to perform the functions of the above transceiver module 1401.
  • the transceiver may include a communication interface.
  • the communication interface may be used for communication with the communication device 1500 .
  • the communication interface can be used to implement the functions shown in the above transceiver module 1401 in a wired manner.
  • the processor 1502 is used to implement the communication methods as shown in the above figures. For details, please refer to the description in the above embodiments. For example, processor 1502 may be configured to perform the functions of processing module 1402 above.
  • the memory 1503 is used to store program instructions, etc.
  • program instructions may include program code including computer operating instructions.
  • the memory 1503 may include random access memory (RAM), and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
  • the processor 1502 executes the program instructions stored in the memory 1503 to implement the above functions, thereby realizing the communication method provided by the above embodiments.
  • transceiver module 1401 and the transceiver 1501 shown above can be used to send information, notifications, or information performed by communication devices or devices such as terminal equipment, first access network equipment, and second access network equipment.
  • the action of the message, and/or the action of receiving the information, notification or message performed by the communication equipment or device such as the terminal equipment, the first access network equipment, the second access network equipment, etc.
  • At least one of the processing module 1402 and the processor 1502 may be used to perform processing actions of the first device or the second device, for example, including the terminal device determining access network equipment changes or cell changes, generating data generated by the transceiver module 1401 and the transceiver module 1401. information, notifications or messages sent by at least one of the transceivers 1501, or process information, notifications or messages received by at least one of the transceiver module 1401 and the transceiver 1501, and so on.
  • transceiver module 1401, transceiver 1501, processing module 1402 and processor 1502 the relevant technical terms, nouns and action implementation methods can be found in the method embodiments of this application in Figure 6 to Figure 13 describe the corresponding technical terms, nouns, and action implementation methods.
  • embodiments of the present application also provide a communication method.
  • the method is implemented by a terminal device and a first access network device.
  • the method can also be implemented by the terminal device, the first access network device and the second access network device.
  • the communication method can also be implemented by terminal equipment, mobility management network elements, session management network elements and access network equipment.
  • the communication method can also be implemented by a third access network device and a fourth access network device.
  • embodiments of the present application also provide a system, which may include the above terminal device and a first access network device, or may include a terminal device, a first access network device and a second access network
  • the equipment implementation may include a terminal device, a mobility management network element, a session management network element and an access network device, or may include a third access network device and a fourth access network device.
  • embodiments of the present application also provide a computer program, which when the computer program is run on a computer, causes the computer to execute the communication method provided in the above embodiments.
  • embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the computer program When the computer program is executed by a computer, it causes the computer to perform the communication provided in the above embodiments. method.
  • embodiments of the present application also provide a chip, which is used to read the computer program stored in the memory and implement the communication method provided in the above embodiments.
  • the chip may include a processor.
  • the chip system includes a processor and is used to support the computer device to implement the terminal equipment, the first access network equipment, the second access network equipment, Functions involved in at least one of the mobility management network element, the session management network element, the access network equipment, the third access network equipment and the fourth access network equipment.
  • the chip system further includes a memory, and the memory is used to store necessary programs and data of the computer device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • “plurality” means two or more.
  • “And/or” describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects before and after are an “or” relationship; in the formula of this application, the character “/” indicates that the related objects before and after are a kind of “division” Relationship.
  • “Including at least one of A, B or C” may mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

Abstract

一种通信方法及装置，用以实现对第一组播/广播会话的有效管理，提高网络资源利用率。根据该方法，当已加入第一组播/广播业务且处于无线资源控制去激活态的UE确定接入网设备变更为第一接入网设备，或者，当该终端设备确定小区变更为第一接入网设备中的小区，则终端设备可以向第一接入网设备发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息。相应的，第一接入网设备可根据第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息，获知该终端设备移动到其覆盖范围下接收第一组播/广播业务，以有效的创建第一组播/广播会话或者更新第一组播/广播会话上下文。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年03月29日提交中国专利局、申请号为202210326256.6、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
随着移动互联网的发展，移动高清视频业务呈现井喷态势。用户逐渐从传统的通过固定电视收看热点节目的方式转变为通过手机终端与移动互联网收看热点节目，因此，视频业务对移动网络的冲击愈发强烈，若无线接入网(radio access network，RAN)设备，如基站，可以通过空口组播/广播(Multicast Broadcast Service，MBS)传输业务数据的方式优化视频业务的传输，将会大幅减少视频流量对移动网络的冲击。
目前，第三代合作伙伴计划(3rd generation partnership project，3GPP)研究人员已提出可支持终端设备(user equipment，UE)在无线资源控制(radio resource control，RRC)去激活态(RRC-inactive)接收组播/广播业务的数据。然而，对于处于RRC去激活态下的UE来说，基站无法获知UE是否移出基站的范围，只能获知UE是否在不同的无线接入网通知区域(RAN notification area，RNA)内移动，但是组播/广播业务的数据是以基站和业务为粒度向UE传输的，若UE移出基站范围，且UE所在RNA未改变，则基站无法获知UE的移动，因此无法对组播/广播会话进行有效管理，导致网络资源利用率下降。
发明内容
本申请提供一种通信方法及装置，用于实现对处于RRC去激活态下的终端设备的组播/广播会话的有效管理，提高网络资源利用率。
第一方面，本申请提供一种通信方法，该方法可由终端设备或终端设备中的组件实施，组件例如处理器、收发器、处理模块或收发模块中的至少一种。以执行主体是终端设备为例，该方法包括：终端设备确定接入网设备变更为第一接入网设备，或者，确定小区变更为第一接入网设备的小区，所述终端设备已加入所述第一组播/广播业务且处于RRC去激活态；所述终端设备向所述第一接入网设备发送第一消息、第二消息、第三消息第九消息或第十消息中的至少一个；其中，所述第一消息用于指示所述第一接入网设备发送所述第一组播/广播业务的数据；所述第二消息用于指示所述第一接入网设备更新所述第一组播/广播业务的上下文；所述第三消息用于恢复所述终端设备的RRC连接；第九消息用于激活用户面连接；第十消息用于请求注册。
基于该方法，当已加入第一组播/广播业务且处于去激活态的UE确定基站变更为第一接入网设备，或者，当该终端设备确定小区变更为第一接入网设备中的小区，则终端设备 可以向第一接入网设备发送第一消息、第二消息、第三消息第九消息或第十消息中的至少一个消息。相应的，第一接入网设备可根据第一消息、第二消息、第三消息第九消息或第十消息中的至少一个消息，获知该终端设备移动到其覆盖范围下接收第一组播/广播业务，以及时创建第一组播/广播会话或者更新第一组播/广播会话上下文，实现对第一组播/广播会话的有效管理，提高网络资源利用率。
应理解，本申请组播/广播会话可以替换为组播/广播业务；此外，组播/广播会话还可以用于传输组播/广播业务数据或者用于传输组播/广播业务。
此外，本申请“确定”可用替换为“发现”。
在一种可能的实现方式中，所述终端设备允许在无线资源控制去激活态接收组播/广播。
在一种可能的实现方式中，所述终端设备可接收第一信息，所述第一信息包括所述第一接入网设备的标识和/或所述第一接入网设备的小区的标识。所述终端设备还可根据第一信息确定接入网设备变更为所述第一接入网设备，或者，确定小区变更为所述第一接入网设备的小区。
基于该实现方式，终端设备可以在RRC去激活态下识别是否发送接入网设备或小区变更，提高移动过程中接入网设备或小区变更的识别准确度。
在一种可能的实现方式中，所述终端设备可接收第二信息，所述第二信息用于指示以下中的至少一项：所述接入网设备的标识占用的所述第一信息的位数；或者，第二信息用于指示所述第一信息中接入网设备的标识的编码方式；或者，第二信息用于指示所述第一信息中小区的标识的编码方式。示例性的，接入网设备的标识可包括基站标识，小区的标识可包括小区标识(cell ID)。
基于该实现方式，终端设备可以根据第二信息正确解读第一信息中的接入网设备的标识和小区的标识，进一步提高接入网设备或小区变更的识别准确度。
在一种可能的实现方式中，所述终端设备还可接收(或收到或确定收到)第一组播/广播业务的数据，并向所述第一接入网设备发送所述第二消息和/或所述第三消息，或发送所述第二消息和/或所述第九消息，或发送所述第二消息和/或所述第十消息。
基于该实现方式，如果终端设备在接入网设备变更或小区变更后仍能够接收到第一组播/广播业务的数据，则终端设备可以向第一接入网设备发送第二消息和/或第三消息，或第二消息和/或第九消息，或第二消息和/或第十消息，以便第一接入网设备及时进行第一组播/广播会话的上下文更新。
在一种可能的实现方式中，所述终端设备确定(或发现)没有(或未收到)第一组播/广播业务的传输，所述终端设备向所述第一接入网设备发送所述第一消息和/或所述第三消息，或发送所述第一消息和/或所述第九消息，或发送所述第一消息和/或所述第十消息。
基于该实现方式，如果终端设备在接入网设备变更或小区变更后未接收到第一组播/广播业务的数据，则终端设备可以向第一接入网设备发送第一消息和/或第三消息，以便第一接入网设备根据第一消息和/或第三消息，或第一消息和/或所述第九消息，或所述第一消息和/或所述第十消息，建立第一组播/广播会话，或向终端设备发送第一组播/广播业务的接收配置，以恢复终端设备的第一组播/广播业务的传输，并及时更新第一组播/广播会话的上下文。
在一种可能的实现方式中，所述第一消息、所述第二消息或所述第三消息中的至少一个消息中，包括所述终端设备的标识、所述第一组播/广播业务的标识，第一协议数据单元 PDU会话标识，或所述消息的发送原因(或称为，发送所述消息的原因)中的至少一项，所述第一PDU会话与所述第一组播/广播业务关联。
在一种可能的实现方式中，所述终端设备还可接收第一区域的信息，所述第一区域为第二接入网设备的服务区域。所述终端设备还可确定移出所述第一区域，并发送所述第三消息。
基于该实现方式，如果终端设备从第二接入网设备移动到第一接入网设备，或者说，终端设备的接入网设备从第二接入网设备变更为第一接入网设备，并且，终端设备接收第二接入网设备的服务区域(即第一区域)的指示信息，则终端设备可在移出第一区域后确定接入网设备发生变更，因此可向第一接入网设备发送第三消息。
在一种可能的实现方式中，如果所述终端设备确定接入网设备从第二接入网设备变更为所述第一接入网设备，则第一消息、第二消息或第三消息中的至少一个中包括第二接入网设备的标识和/或地址。
基于该实现方式，如果终端设备从第二接入网设备移动到第一接入网设备，则终端设备在向第一接入网设备发送的第一消息、第二消息或第三消息中的至少一个中可包括第二接入网设备的标识，用于向第一接入网设备指示第二接入网设备，以便第一接入网设备及时通知第二接入网设备更新第一组播/广播会话的上下文。
在一种可能的实现方式中，终端设备可确定移出接入网通知区域，终端设备还可发送第九消息。因此，终端设备可在确定未接收到第一组播/广播业务的数据并确定移出接入网通知区域的情况下，发送第九消息。
在一种可能的实现方式中，终端设备可确定移出注册区域，所述终端设备还可发送第十消息。因此，终端设备可在确定未接收到第一组播/广播业务的数据并确定移出注册区域的情况下，发送第十消息。
在一种可能的实现方式中，所述终端设备接收来自于第一接入网设备的第七消息，所述第七消息包括所述第一配置或第一能力信息；所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一能力信息用于指示第一接入网设备是否支持无线资源控制RRC去激活态接收，或者，第一能力信息用于指示第一接入网设备是否支持终端设备在RRC去激活态接收所述第一组播/广播业务，或者，第一能力信息用于指示第一接入网设备是否支持终端设备在RRC去激活态接收组播/广播业务。
基于该实现方式，终端设备可根据第七消息获取第一组播/广播业务的接收配置或获得用于指示第一接入网设备是否支持在RRC去激活态接收第一组播/广播数据的能力指示信息。
第二方面，本申请提供一种通信方法，该方法可由终端设备或终端设备中的组件实施，组件例如处理器、收发器、处理模块或收发模块中的至少一种。以执行主体是终端设备为例，该方法包括：终端设备确定未接收到第一组播/广播业务的数据，所述终端设备已加入所述第一组播/广播业务且处于无线资源控制去激活态；所述终端设备向第一接入网设备发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个；其中，所述第一消息用于指示所述第一接入网设备发送所述第一组播/广播业务的数据；所述第二消息用于通知/指示所述第一接入网设备更新所述第一组播/广播业务的上下文；所述第三消息用于恢复所述终端设备的RRC连接；所述第九消息用于激活用户面连接；所述第十消息用于请求注册。
应注意，本申请中，“通知”可用替换为“指示”。
应注意，本申请中，“终端设备确定未接收到第一组播/广播业务的数据”可以替换为：“终端设备未接收到第一组播/广播业务的配置(configuration)”，或者，“终端设备确定未接收到接收第一组播/广播业务数据或未接收到第一组播/广播业务的配置”，或者，“终端设备确定未接收到第一组播/广播业务的数据的配置”，或者，“终端设备确定未接收到第一组播/广播业务的配置”。其中，“终端设备未接收到第一组播/广播业务的配置”，还可以理解为“第一组播/广播业务的配置不可获得/不适用/不存在(not available)”。应理解，上述第一组播/广播业务的配置可以是第一组播/广播业务的组播无线承载(multicast radio bearer，MRB)配置。上述第一组播/广播业务的配置可以包括配置信息，例如，第一组播/广播业务的组播无线承载(multicast radio bearer，MRB)的配置信息(例如，MRB的标识)，再例如，点到多点配置(point To multipoint configuration，PTM configuration)。上述数据的配置可以包括组播业务逻辑信道配置(multicast traffic channel configuration，MTCH configuration)，不予限制。
基于以上方法，已加入所述第一组播/广播业务且处于RRC去激活态的终端设备，可以在确定未接收到第一组播/广播业务的数据的情况下，向第一接入网设备发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个，使得第一接入网设备能够及时获知终端设备在第一接入网设备的覆盖范围内并有需求在RRC去激活态接收第一组播/广播业务的数据，以便第一接入网设备及时创建第一组播/广播会话或者更新第一组播/广播会话上下文，实现对第一组播/广播会话的有效管理，提高网络资源利用率。
在一种可能的实现方式中，终端设备确定接入网设备变更为第一接入网设备，或者，确定小区变更为第一接入网设备的小区。
在一种可能的实现方式中，所述终端设备允许在无线资源控制去激活态接收组播/广播。
在一种可能的实现方式中，所述终端设备可接收第一信息，所述第一信息包括所述第一接入网设备的标识和/或所述第一接入网设备的小区的标识；所述终端设备根据第一信息确定接入网设备变更为所述第一接入网设备，或者，确定小区变更为所述第一接入网设备的小区。
在一种可能的实现方式中，所述终端设备还可接收第二信息，所述第二信息用于指示以下中的至少一项：所述接入网设备的标识占用的所述第一信息的位数；第二信息用于指示所述第一信息中接入网设备的标识的编码方式；第二信息用于指示所述第一信息中小区的标识的编码方式。
在一种可能的实现方式中，所述终端设备还可接收(或收到或确定收到)第一组播/广播业务的数据，则所述终端设备可向所述第一接入网设备发送所述第二消息和/或所述第三消息，或者，所述终端设备可向所述第一接入网设备发送所述第二消息和/或所述第九消息，或者，所述第一接入网设备发送所述第二消息和/或所述第十消息。
基于该实现方式，如果终端设备在接入网设备变更或小区变更后仍能够接收到第一组播/广播业务的数据，则终端设备可以向第一接入网设备发送第二消息和/或第三消息，以便第一接入网设备及时进行第一组播/广播会话的上下文更新。或者，此时也可由终端设备向第一接入网设备发送第九消息或第十消息，使得第一接入网设备将第九消息或第十消息发送至AMF，AMF进一步发送至SMF，触发激活关联的PDU会话ID，并进一步触发建立第一组播/广播会话至第一基站。
在一种可能的实现方式中，所述终端设备确定(或发现)没有(或未收到)第一组播/广播业务的数据的传输，则所述终端设备可向所述第一接入网设备发送所述第一消息和/或所述第三消息，或者，所述终端设备向所述第一接入网设备发送所述第一消息和/或所述第九消息，或者，所述第一接入网设备发送所述第一消息和/或所述第十消息。
基于该实现方式，如果终端设备在接入网设备变更或小区变更后未接收到第一组播/广播业务的数据，则终端设备可以向第一接入网设备发送第一消息和/或第三消息，以便第一接入网设备根据第一消息和/或第三消息建立第一组播/广播会话，或向终端设备发送第一组播/广播业务的接收配置。或者，此时也可由终端设备向第一接入网设备发送第九消息或第十消息，使得第一接入网设备将第九消息或第十消息发送至AMF，AMF进一步发送至SMF，触发激活关联的PDU会话ID，并进一步触发建立第一组播/广播会话至第一基站。
在一种可能的实现方式中，所述第一消息、所述第二消息、所述第三消息、所述第九消息、或所述第十消息中的至少一个消息中，包括所述终端设备的标识、所述第一组播/广播业务的标识，第一协议数据单元PDU会话标识，或所述消息的发送原因中的至少一项，所述第一PDU会话与所述第一组播/广播业务关联。
在一种可能的实现方式中，所述终端设备还可接收第一区域的信息，所述第一区域为第二接入网设备的服务区域。所述终端设备还可确定移出所述第一区域，并发送所述第三消息。
在一种可能的实现方式中，如果所述终端设备确定接入网设备从第二接入网设备变更为所述第一接入网设备，则第一消息、第二消息或第三消息中的至少一个中包括第二接入网设备的标识和/或地址。
在一种可能的实现方式中，终端设备可确定移出接入网通知区域，终端设备还可发送第九消息。因此，终端设备可在确定未接收到第一组播/广播业务的数据并确定移出接入网通知区域的情况下，发送第九消息。
在一种可能的实现方式中，终端设备可确定移出注册区域，所述终端设备还可发送第十消息。因此，终端设备可在确定未接收到第一组播/广播业务的数据并确定移出注册区域的情况下，发送第十消息。
在一种可能的实现方式中，所述终端设备可接收来自于第一接入网设备的第七消息，所述第七消息包括所述第一配置或第一能力信息；所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一能力信息用于指示第一接入网设备是否支持无线资源控制RRC去激活态接收，或者，第一能力信息用于指示第一接入网设备是否支持在RRC去激活态接收所述第一组播/广播业务，或者，第一能力信息用于指示第一接入网设备是否支持UE在RRC去激活态的接收所述第一组播/广播业务的数据。
在一种可能的实现方式中，所述终端设备可根据所述第一能力信息，发送第九消息。例如，在第一能力信息用于指示第一接入网设备支持在RRC去激活态的UE接收所述第一组播/广播业务时，发送第九消息。
第三方面，本申请提供一种通信方法，该方法可由第一接入网设备或第一接入网设备中的组件实施，组件例如处理器、收发器、处理模块或收发模块中的至少一种。以执行主体是第一接入网设备为例，该方法包括：第一接入网设备接收来自于终端设备的第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个，其中，所述第一消息用于通知/指示发送所述第一组播/广播数据，所述终端设备已加入所述第一组播/广播业务且处于无 线资源控制去激活态；所述二消息用于通知/指示所述第一接入网设备更新所述第一组播/广播业务的上下文；所述第三消息用于恢复所述终端设备的RRC连接；所述第九消息用于激活用户面连接；所述第十消息用于请求注册；所述第一消息、所述第二消息或所述第三消息中的至少一个包括第二接入网设备的标识和/或地址；所述第一接入网设备根据所述第二接入网设备的标识和/或地址，向所述第二接入网设备发送第四消息或第五消息或第八消息，所述第四消息用于更新所述第一组播/广播业务的上下文，所述第五消息用于提取所述终端设备的上下文，所述第八消息用于鉴权所述终端设备是否已经加入所述第一组播/广播业务。
在一种可能的实现方式中，所述第一接入网设备还可向接入管理网元发送所述第九消息或所述第十消息，所述第九消息或所述第十消息携带第一协议数据单元PDU会话标识，所述第九消息或所述第十消息携带所述第一协议数据单元PDU会话标识用于激活所述第一PDU会话或用于激活所述第一PDU会话的连接，所述第一PDU会话与所述第一组播/广播业务关联。
在一种可能的实现方式中，所述第一消息、所述第二消息或所述第三消息中的至少一个可包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
在一种可能的实现方式中，所述第四消息或第五消息或第八消息包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
在一种可能的实现方式中，所述第一接入网设备还可接收来自于所述第二接入网设备的第六消息，所述第六消息包括以下至少一项信息：第一配置，所述终端设备的上下文信息、所述第一组播/广播业务的信息、第一能力信息；所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一接入网设备发送第七消息，所述第七消息包括所述第一配置或第一能力信息；所述第一能力信息用于指示第一接入网设备是否支持UE在RRC去激活态的接收所述第一组播/广播业务的数据。
第四方面，本申请提供一种通信方法，该方法可由第二接入网设备或第二接入网设备中的组件实施，组件例如处理器、收发器、处理模块或收发模块中的至少一种。以执行主体是第二接入网设备为例，该方法包括：第二接入网设备接收来自于第一接入网设备的第四消息或第五消息或第八消息中的至少一个，其中，所述第四消息用于更新所述第一组播/广播业务的上下文，所述第五消息用于提取所述终端设备的上下文，所述第八消息用于鉴权所述终端设备是否已经加入所述第一组播/广播业务，所述终端设备已加入所述第一组播/广播业务且处于无线资源控制去激活态。所述第一接入网设备更新所述第一组播/广播业务的上下文。
在一种可能的实现方式中，所述第四消息或第五消息或第八消息包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
在一种可能的实现方式中，所述第二接入网设备还可根据所述终端设备的数量更新所述第一组播/广播业务上下文中的终端设备数量。
在一种可能的实现方式中，所述第四消息或所述第五消息或第八消息中的至少一个包括所述终端设备的标识，所述第二接入网设备还可删除(或移除)所述第一组播/广播业务的上下文中的所述终端设备的标识。
在一种可能的实现方式中，所述第二接入网设备还可向所述第一接入网设备发送第六消息，所述第六消息包括第一配置，所述第一配置包括用于接收所述第一组播/广播业务的 配置。
在一种可能的实现方式中，所述第二接入网设备向所述终端设备发送第一区域的信息，所述第一区域包括以下至少一项：所述第二接入网设备的标识、所述第二接入网设备包括的小区、第二接入网设备的追踪区码、第二接入网设备的接入网区域码、第二接入网设备的服务区域。
在一种可能的实现方式中，第二接入网设备确定第一计时器过期，所述第二接入网设备释放第一传输资源，所述第一传输资源用于传输所述第一组播/广播业务。可选的，第一传输资源包括第一组播/广播会话，还可以包括第一组播/广播会话的共享组播/广播业务流量传输。
第五方面，本申请还提供一种通信方法，该方法可由第三接入网设备或第三接入网设备中的组件实施，组件例如处理器、收发器、处理模块或收发模块中的至少一种。以执行主体是第一接入网设备为例，该方法包括：第三接入网设备建立第一组播/广播会话，所述第一组播/广播会话用于传输第一组播/广播业务的数据；所述第三接入网设备向至少一个第四接入网设备发送第一指示，所述第一指示用于指示或触发所述第四接入网设备建立所述第一组播/广播业务会话或建立所述第一组播/广播会话的共享组播/广播业务流量传输，所述第四接入网设备与所述第三接入网设备位于或处于同一RNA区域，所述第一组播/广播会话用于传输所述第一组播/广播业务。
基于该方法，当RNA区域内的第三接入网设备建立第一组播/广播会话，则该第三接入网设备可通过第一指示触发RNA区域内的其他接入网设备(即第四接入网设备)建立该第一组播/广播会话，因此，即便终端设备从第三接入网设备的覆盖范围移动到其他第四接入网设备的覆盖范围内，由于第四接入网设备已建立第一组播/广播会话，因此，终端设备可从第四接入网设备接收第一组播/广播业务的数据，而不需要第四接入网设备建立第一组播/广播会话，能够降低组播/广播业务的传输时延，可提高业务质量。
在一种可能的实现方式中，所述第三接入网设备发现不存在终端设备接收所述第一组播/广播会话，例如，第一组播/广播业务的会话上下文中不存在任何终端设备的标识，或该会话上下文中的终端设备的数量为0；所述第三接入网设备确定或发现所述第四接入网设备不存在终端设备接收第一组播/广播会话；所述第三接入网设备释放所述第一组播/广播会话或释放所述第一组播/广播会话的共享组播/广播业务流量传输，所述第四接入网设备与所述第三接入网设备位于或处于同一RNA区域，所述第一组播/广播会话用于传输所述第一组播/广播业务。
基于该实现方式，第三接入网设备确定在RNA区域内的全部接入网设备不存在终端设备接收第一组播/广播会话后，释放第一组播/广播会话或释放第一组播/广播会话的共享组播/广播业务流量传输，否则，在RNA内的至少一个接入网设备至少存在一个终端设备接收第一组播/广播会话，第三接入网设备会保留第一组播/广播会话或保留第一组播/广播会话的共享组播/广播业务流量传输。
在一种可能的实现方式中，所述第三接入网设备可接收来自于所述第四接入网设备的第二指示，所述第二指示用于指示所述第四接入网设备不存在终端设备接收所述第一组播/广播会话，或者，第二指示可用于通知已无终端设备接收所述第一组播/广播会话，所述第一组播/广播会话用于传输第一组播/广播会话，或者，第二指示还用于通知存在终端设备接收所述第一组播/广播会话。
基于该实现方式，第三接入网设备可根据来自于其他第四接入网设备的第二指示，确定第四接入网设备不存在终端设备接收所述第一组播/广播会话，所述第一组播/广播会话用于传输第一组播/广播业务。
在一种可能的实现方式中，所述第三接入网设备可向所述第四接入网设备发送第三指示，所述第三指示用于指示所述第三接入网设备不存在终端设备接收所述第一组播/广播会话，或者，所述第三指示用于确认是否所述第四接入网设备中还存在终端设备接收所述第一组播/广播会话，所述第一组播/广播会话用于传输所述第一组播/广播业务。
基于该实现方式，第三接入网设备可在第三接入网设备不存在终端设备接收第一组播/广播会话后发送第三指示，以触发第四接入网设备根据第三指示向第三接入网设备发送该第二指示。
在一种可能的实现方式中，所述第三接入网设备向所述第四接入网设备发送第五指示，所述第五指示用于触发所述第四接入网设备释放第一组播/广播会话。
基于该实现方式，第三接入网设备可在不存在终端设备接收所述第一组播/广播会话并触发释放第一组播/广播会话的情况下，通知其他第四接入网设备释放该第一组播/广播会话。可选的，该第三接入网设备是RNA区域内的最后一个不存在终端设备接收所述第一组播/广播会话的接入网设备。
在一种可能的实现方式中，所述第一指示、所述第二指示、所述第三指示、所述第四指示或第五指示中的任意一个包括所述第一组播/广播业务的标识，此外，所述第一指示、所述第二指示、所述第三指示、所述第四指示或第五指示中的任意一个可携带在Xn消息或X2消息或基站间的交互消息或通信消息中。
第六方面，本申请还提供了一种通信装置，所述通信装置可以是终端设备、接入网设备、终端设备中的组件间或接入网设备中的组件。该通信装置具有实现上述第一方面至第五方面及其各个可能的实现方式中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的实现方式中，所述通信装置的结构中包括通信模块和处理模块，这些模块或单元可以执行上述第一方面至第五方面及其各个可能的实现方式中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。例如，通信模块可包括接收模块和/或发送模块。
在一个可能的实现方式中，所述通信装置的结构中包括通信接口和处理器，可选的还包括存储器，所述通信接口用于收发信息或数据，以及用于与通信网络中的其他设备进行通信交互，所述处理器被配置为支持所述通信装置执行上述第一方面至第五方面及其各个可能的实现方式中的相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第七方面，本申请实施例提供了一种通信系统，可以包括如用于实现上述第一方面或第二方面及其各个可能的实现方式中所示方法的通信装置，以及，包括用于实现所述第三方面及其各个可能的实现方式中所示通信方法的通信装置，可选的，还可包括用于实现第四方面及其任意可能的实现方式中所述方法的通信装置。或者，该通信系统可包括用于实现上述第一方面或第二方面及其各个可能的实现方式中所示方法的通信装置，以及包括与该通信装置处于同一个RNA区域的第四接入网设备。
第八方面，本申请实施例提供的一种计算机可读存储介质，该计算机可读存储介质存 储有程序指令，当程序指令在计算机上运行时，使得计算机执行本申请实施例第一方面至第五方面及其任一可能的实现方式中所述的方法。示例性的，计算机可读存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括非瞬态计算机可读介质、随机存取存储器(random-access memory，RAM)、只读存储器(read-only memory，ROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。
第九方面，本申请实施例提供一种计算机程序产品，包括计算机程序代码或指令的，当计算机程序代码或指令在计算机上运行时，使得上述第一方面至第五方面或其中任一可能的实现方式中所述的方法被执行。
第十方面，本申请还提供了一种芯片，包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以使所述芯片实现上述第一方面至第五方面或其中任一种可能的实现方式中所述的方法。
上述第二方面至第十方面中的各个方面以及各个方面可能达到的技术效果请参照上述针对第一方面至第五方面及其任一可能的实现方式中所述的方法的有益效果说明，这里不再重复赘述。
附图说明
图1A为本申请提供的一种通信系统的架构示意图；
图1B为本申请提供的另一种通信系统的架构示意图；
图2为本申请提供的另一种通信系统的架构示意图；
图3为本申请提供的另一种通信系统的架构示意图；
图4为本申请提供的一种数据传输发送的示意图；
图5为本申请提供的另一种数据传输发送的示意图；
图6为本申请提供的一种通信方法的流程示意图；
图7为本申请提供的另一种通信方法的流程示意图；
图8为本申请提供的另一种通信方法的流程示意图；
图9为本申请提供的另一种通信方法的流程示意图；
图10为本申请提供的另一种通信方法的流程示意图；
图11为本申请提供的另一种通信方法的流程示意图；
图12为本申请提供的另一种通信方法的流程示意图；
图13为本申请提供的另一种通信方法的流程示意图；
图14为本申请提供的一种通信装置的结构示意图；
图15为本申请提供的另一种通信装置的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
为了便于理解本申请的技术方案，下面先对本申请所涉及的技术术语进行简单介绍。
以下对本申请实施例设计的系统架构方面的部分用语进行解释说明，以便于本领域技术人员理解。
用户设备，也称终端设备，是一种具有无线收发功能的设备，可以经(无线)接入网设备(radio access network，(R)AN)中的接入网设备(或者也可以称为接入设备)与一个或多个核心网(core network，CN)设备(或者也可以称为核心设备)进行通信。
用户设备也可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、用户代理或用户装置等。用户设备可以部署(deployed in)在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。用户设备可以是蜂窝电话(cellular phone)、无绳电话、会话启动协议(session initiation protocol，SIP)电话、智能电话(smart phone)、手机(mobile phone)、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)等。或者，用户设备还可以是具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、无人机设备或物联网、车联网中的终端、第五代(5th-generation，5G)移动通信网络以及未来网络中的任意形态的终端、中继用户设备或者未来演进的公共陆地移动网(public land mobile network，PLMN)中的终端等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。例如用户设备可以是虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。本申请实施例对终端设备的类型或种类等并不限定。
所述用户设备还可以包括端侧设备，如本地交换机(local switch，LSW)，和/或客户端设备(customer premise equipment，CPE)等，或者，用户设备可通过LSE或CPE接入网络。
在本申请实施例中注册入网的用户设备(user equipment，UE)可以理解为用户。其中一个UE可以对应一个用户识别模块(subscriber identity module，SIM)卡，即当终端设备安装有一个SIM卡时，终端设备对应一个用户UE，当终端设备安装有多个SIM卡时，终端设备对应多个用户UE。
本申请中，网络设备，指可以为终端提供无线接入功能的设备，如(R)AN设备。其中，网络设备可以支持至少一种无线通信技术，例如长期演进(long term evolution，LTE)、新无线(new radio，NR)、宽带码分多址(wideband code division multiple access，WCDMA)等。
又如，网络设备可以包括核心网设备，核心网设备例如包括接入和移动性管理功能(access and mobility management function，AMF)等核心网网元(network function，NF)。
在本申请中，(无线)接入网设备可用于为特定区域的授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同质量的传输隧道。
(R)AN设备能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，(R)AN也可以理解为传统网络中的基站。
示例性地，本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved Node B， eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，NR，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网中的接入网设备，本申请对此不做限定。
用户面网元：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
数据网络网元：用于提供传输数据的网络。
在5G通信系统中，该数据网络网元可以是数据网络(data network，DN)网元。在未来通信系统中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
认证服务器：用于执行用户的安全认证。在5G通信系统中，该认证服务器可以是认证服务器功能网元(authentication server function，AUSF)。
移动性管理网元：主要用于移动性管理和接入管理等。在5G通信系统中，该接入管理网元可以是AMF，主要进行移动性管理、接入鉴权/授权等功能。此外，还负责在终端与策略控制功能(policy control function，PCF)网元间传递用户策略。
网络数据分析网元：主要用于提供网络数据分析功能。在5G通信系统中，该网络数据分析网元可以是网络数据分析功能(network data analytics function，NWDAF)。
会话管理网元：主要用于会话管理、用户设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能(session management function，SMF)网元，完成终端IP地址分配，UPF选择，及计费与QoS策略控制等。
应用网元：在5G通信系统中，该应用网元可以是应用功能(application function，AF)网元，表示第三方或运营商的应用功能，是5G网络获取外部应用数据的接口，主要用于传递应用侧对网络侧的需求。
统一数据管理网元：负责用户标识、签约数据、鉴权数据的管理、用户的服务网元注册管理。在5G通信系统中，该统一数据管理网元可以是统一数据管理(unified data management，UDM)。
统一数据存储网元：用于存储和检索UE的签约数据等。在5G通信系统中，该统一数据存储网元可以是统一数据仓储功能(unified data repository，UDR)。
策略控制网元：包括用户签约数据管理功能、策略控制功能、计费策略控制功能、服务质量(quality of service，QoS)控制等，用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
在5G通信系统中，该策略控制网元可以是PCF。
网络功能存储库功能网元：为其他核心网元提供网络功能实体信息的存储功能和选择功能。在5G通信系统中，该网元可以是网络功能存储库功能网元(network function repository function，NRF)。
非结构化数据存储网元：存储和检索其非结构化数据，如，UE上下文。在5G通信系统中，该非结构化数据存储网元可以是非结构化数据存储功能(unstructured data storage network function，UDSF)。
计费网元：主要用于执行计费功能。在5G通信系统中，该计费网元可以是计费网元(Charging Function，CHF)。
边缘安全网元：主要用于在不同运营商网络之间的通信，作为不同运营商网络的边界网关负责运营商之间控制平面接口上的消息过滤和策略管理。在5G通信系统中，该边缘安全网元可以是安全边缘保护代理(security edge protection proxies，SEPP)。
服务通信代理网元：用于支持非直接通信和代理网络功能的发现。在5G通信系统中，该服务通信代理网元可包括服务通信代理(service communication proxy，SCP)。
网络开放网元：在5G通信系统中，该网络开放网元可以是网络开放功能(network element function，NEF)网元，主要用于向AF暴露3GPP网络功能的业务和能力，同时也可以让AF向3GPP网络功能提供信息。
网络切片选择功能网元：负责为UE选择网络切片，在5G通信系统中，该应用网元可以是网络切片选择功能(network slice selection function，NSSF)网元。
在未来的通信系统，例如第六代(6th generation，6G)通信系统中，上述网元或设备仍可以使用其在5G通信系统中的名称，或者也可以有其它名称，本申请实施例对此不作限定。上述网元或设备的功能可以由一个独立网元完成，也可以由若干个网元共同完成。在实际部署中，核心网中的网元可以部署在相同或者不同的物理设备上。例如作为一种可能的部署，可以将AMF和SMF部署在同一个物理设备上。又例如，5G核心网的网元可以和第4代(the 4th generation，4G)核心网的网元部署在同一物理设备上。本申请实施例对此不作限定。
在5G通信系统中，该应用网元可以是应用功能(application function，AF)网元。在 未来通信系统中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
如图1A和图1B所示为第五代(5th generation，5G)网络架构示意图，其中，图1A为非服务化架构下的5G网络架构示意图，图1B为服务化架构(service-based architecture，SBA)下的5G网络架构示意图。其中，服务化架构是5G网络的基础架构。服务化主要体现在控制面。SBA的本质是按照“自包含、可重用、独立管理”三原则，将网络功能定义为若干个可被灵活调用的“服务”模块。基于此，运营商可以按照业务需求进行灵活定制组网。网络功能间的交互由服务调用实现，每个网络功能对外呈现通用的服务化接口，可被授权的网络功能或服务调用。如图1B所示为5G网络的一种示例性的服务化架构示意图，该架构中，核心网网元可通过服务化接口与其他核心网网元进行通信，例如，AMF对应的服务化接口被称为Namf接口，LMF对应的接口可称为Nlmf接口。
图1A和图1B所示的5G网络架构中可包括三部分，分别是终端、DN和运营商网络。下面对其中的部分网元的功能进行简单介绍说明。
其中，运营商网络可包括但不限于以下网元中的一个或多个：AUSF、PCF、UDM、AF、AMF、SMF网元、(R)AN)设备、UPF以及NSSF等。上述运营商网络中，除无线接入网设备之外的网元或设备可以称为核心网网元或核心网设备。
此外，图1A所示的部分通信接口包括：
N1接口，为AMF与UE之间的信令面接口，用于核心网与UE之间交换信令消息，如UE注册入网、UE建立协议数据单元(protocol data unit，PDU)会话、网络侧配置UE策略等。
N2接口，为AMF与(R)AN之间的接口，用于传递核心网至(R)AN的无线承载控制信息等。
N3接口，为(R)AN与UPF之间的接口，用于在(R)AN和UPF之间传递UE业务数据。
N4接口，为SMF与UPF之间的接口，用于控制面与用户面之间传递信息，包括控制面终端设备根据与运营商的签约信息完成入网操作。
N6接口，为UPF与DN之间的接口，用于在UPF和DN之间传递UE业务数据。
N5接口，为PCF与AF之间的接口。
N7接口，为PCF与SMF之间的接口，用于下发PDU会话粒度以及业务数据流粒度控制策略。
N8接口，为AMF与UDM间的接口，用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。
N9接口，为两个UPF之间的接口。例如图1A所示，该N9接口为中间UPF(intermediate UPF，I-UPF)与作为PDU会话锚点(PDU session anchor，PSA)的UPF之间的接口。
N10接口，为SMF与UDM间的接口，用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。
N11接口，为SMF与AMF之间的接口，用于传递(R)AN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给(R)AN的无线资源控制信息等。
N12接口，包括AMF与AUSF之间的接口。
N13接口，包括AUSF与UDM之间的接口。
N22接口，包括NSSF与AMF之间的接口。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
本申请中的会话管理网元、用户面网元、移动性管理网元分别可以是图1A中的SMF、UPF、AMF，也可以是未来通信如6G网络中具有上述SMF、UPF、AMF的功能的网元，本申请对此不限定。在本申请的实施例中，以SMF、UPF、AMF分别作为会话管理网元、用户面网元、移动性管理网元的一个举例进行描述。
需要说明的是，图1A和/或图1B中的各个网元以及各个网元之间的接口名字只是一个示例，具体实现中各个网元以及各个网元之间的接口名字可能为其他，本申请实施例对此不作具体限定。
在前几代移动通信技术中，例如第3代(the 3rd generation，3G)移动通信技术和4G移动通信技术，组播/广播方案的推广遇到了较大的困难。具体地，现有组播/广播方案需要在现有的通信架构基础上添加支持组播/广播的专有网元和接口，并且还需要专有的组播/广播信道支持，不但增加了运营商角的开销，还提高了终端的复杂度。
为克服上述困难，在第5代移动通信网络架构的基础上支持组播/广播功能(5G Multicast Broadcast Service，5MBS)成为一个关键研究课题。
如图2所示，其为当前5G组播/广播最新技术规范采用的架构，其提供了用于支撑组播/广播业务的网络架构。该架构是在图1A所示架构的基础上进行扩展，例如，增加了组播广播会话管理功能网元(Multicast Broadcast Session Management Function，MB-SMF)和组播广播用户面功能网元(Multicast Broadcast User Plane Function，MB-UPF)，等两个功能实体，用于支持组播/广播服务/功能。
其中，MB-SMF可以实现组播/广播业务的控制面功能，负责组播/广播业务/组/会话的管理。从控制面来看，MB-SMF可以与NEF和/或组播/广播服务功能(Multicast/Broadcast Service Function，MBSF)相连，例如，用于接收组播/广播业务的相关信息(例如，组播/广播业务的描述)。此外，MB-SMF还可以与PCF相连，例如，可以提取与组播/广播业务相关的PCC规则。从用户面来看，MB-UPF可以与组播/广播服务传输功能(Multicast/Broadcast Service Transport Function，MBSTF)和/或AF/AS相连，用于接收组播/广播业务的业务数据。应注意，MB-SMF与SMF可以合设，也可以单独部署，MB-UPF与UPF可以合设，也可以单独部署，本申请对此不做限定。
应注意的是，上述MB-SMF或MB-UPF的名称是一个示例，在5G网络中，MB-SMF或MB-UPF也可以是其它名称，本申请不做限定。
下文对接入网设备支持组播/广播功能的定义进行解释。
如图3所示，接入网设备支持组播/广播功能可以理解为接入网设备支持以5G核心网共享组播/广播业务流量传输(5GC shared MBS traffic delivery)方式传输组播/广播业务数据，接入网设备不支持组播/广播功能可以理解为接入网设备不支持以5G核心网共享组播/广播业务流量传输方式传输组播/广播业务数据，也即，只支持5G核心网单独组播/广播业务流量传输(5GC Individual MBS traffic delivery)方式传输组播/广播业务数据。应理 解，组播/广播业务数据到达接入网设备(例如，RAN)之后，经过RAN的服务数据适配协议(service data adaptation protocol，SDAP)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层、物理(physical，PHY)层的处理，发送给每个接收组播/广播业务数据的UE。
目前，5MBS研究课题在版本17(Release-17，R17)阶段只支持组成员在RRC连接态(RRC-connected)接收组播业务数据。并且，5MBS研究课题在版本18阶段提出了支持组成员在RRC-inactive态接收组播业务的需求。
然而，目前当UE处于RRC-inactive态时，无线接入网设备无法对组播/广播会话进行有效管理，存在网络资源利用率降低的问题。应理解，本申请中的组播/广播会话的管理过程可包括组播/广播会话的建立、释放和更新等过程，这里主要以会话建立和释放过程进行描述，但不应理解为组播/广播会话的管理过程只包括组播/广播会话的建立和释放
针对5MBS R17的组播/广播会话的管理(MBS session management)流程，当前还存在如下问题：
当前5MBS R17的组播/广播会话(MBS sesson)对应的组播/广播会话隧道是以基站和业务(service)粒度的，其建立是基于第一个到达该基站下且加入该组播/广播业务的UE触发，其释放是基于该基站下最后一个加入该组播/广播业务的UE离开该组播组导致其释放。其中，组播/广播组在本申请中是指，同一个基站下的加入一个组播/广播业务的UE组成的UE组。
由于在5MBS R17，UE必须在RRC连接态(CM-connected)(以下简称为连接态)进行接收，处于连接态下的UE与基站之间存在Ue粒度的RRC连接，并且，UE与基站之间存在UE粒度的N2连接，因此，基站可以感知UE是否在其覆盖范围下接收组播/广播业务数据，或者说，基站可通过UE粒度的RRC消息是否存在来感知UE是否移出其覆盖范围。
然而，针对RRC-inactive态的UE，UE与基站之间的RRC连接是去激活的，基站无法根据RRC连接是否存在判断UE是否移出基站的覆盖范围，因此，当UE在无线接入网通知区域(RAN notification area，RNA)内移动，即便移出基站的覆盖范围，基站也是无法准确感知的，这就导致，基站无法准确判断组播/广播会话建立与释放的准确时机，因此无法有效建立与释放组播会话，会导致网络资源利用率下降问题。此外，现有的其他竞争方案中，若处于RRC-inactive态的UE加入组播/广播业务，则需要将RNA设置为基站覆盖范围粒度，限制了RNA的应用。
以下，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。需要说明的是，这些解释不是对本申请所要求的保护范围的限定。
一、单播
单播可以理解为“点对点”(point to point，PTP)通信。在业务层面，单播业务是指该业务的数据是发送给单个终端设备的。在核心网业务层面，单播是指通过PDU会话向终端设备发送业务数据。在网元(或设备)间，单播是指源网元与目标网元之间为单播隧道(即目标网元的IP地址为单播IP地址)。对于空口而言，空口单播模式(或称为点对点模式)，是指接入网设备向单个终端设备发送业务数据，可以理解为，接入网设备通过空口单播模式的无线承载向单个终端设备发送业务数据。
二、组播/广播
组播/广播，是指组播(multicast)(或称为多播)或广播(broadcast)，可以理解为“点对多点”(point to multi-point，PTM)通信。在业务层面，组播/广播业务是指该业务的数据发送给多个终端设备。在核心网业务层面，组播/广播业务是指通过组播/广播会话向终端设备发送组播/广播业务的业务数据。在网元间，组播是指源网元与目标网元之间为组播隧道(即目标网元的IP地址为组播IP地址)。对于空口而言，空口组播/广播模式是指接入网设备发送的一份业务数据，多个终端设备可同时和/或同频接收。即本申请中的实施例既可以应用于组播业务传输，也可以应用于广播业务传输。
应理解，当本申请中的“组播”单独出现而不以“组播/广播”形式出现时，指示作为一种传输方式的示例，“组播”可替换为“组播/广播”。
三、组播/广播会话、组播/广播会话隧道
组播/广播会话包括网元间的单播隧道、组播隧道、单播模式的空口无线承载、或组播/广播模式的空口无线承载。需要说明的是，组播/广播会话可以用于向终端设备发送组播业务数据(sends multicast broadcast service data)，还可以用于向终端设备发送广播业务数据，本申请实施例对此不作限定。应理解，发送组播业务数据也可替换为发送组播/广播数据(sends multicast broadcast data)，或发送组播/广播业务(sends multicast broadcast service)。
以组播会话为例，目前组播会话的数据发送机制可以理解为，一份数据通过业务粒度的隧道到达基站，基站通过组播无线承载(multicast radio bearer)以点对多点的方式发送给加入该组播会话的一个或多个终端设备。
接入网设备与核心网设备之间可以建立关于组播业务的组播/广播会话隧道，组播/广播会话隧道内传输的是组播/广播业务数据，接入网设备通过组播/广播会话隧道接收到的组播/广播业务数据可以发送给加入该组播/广播业务的多个终端设备。其中，组播/广播会话隧道内的组播/广播业务数据可以以组播/广播服务质量(quality of service，QoS)流的形式传输，具体地，组播/广播业务可以在组播/广播会话隧道中以一条或多条组播/广播QoS流的方式进行传输。
应理解，组播/广播会话隧道可以与组播/广播业务一一对应，即一种组播/广播业务对应一个组播/广播会话隧道(Per MB service)；一个组播/广播业务可以包括一个或多个组播/广播业务流，多个组播/广播业务流可以对应一个或多个组播/广播QoS流，一个组播/广播会话可以包括一个或多个组播/广播QoS流。
也就是说，组播/广播会话是以业务为粒度而不是以终端设备为粒度的，至少一个终端设备可通过该会话接收组播/广播业务的数据，换句话说，组播/广播会话可支持多个终端设备共享会话。
此外，本申请中的组播/广播会话或组播/广播会话隧道可认为是5G核心网共享组播/广播业务流量传输，因此组播/广播会话或组播/广播会话隧道可替换为5G核心网共享组播/广播业务流量传输。5G核心网共享组播/广播业务流量传输也可简称为共享连接(shared delivery)。一种可能的实现方式中，组播/广播会话隧道可以是组播组内的多个终端设备共享的GTP-U隧道。
四、组播/广播业务
组播/广播业务可以通过组播/广播业务的信息来描述。组播/广播业务的信息至少包括组播/广播业务的描述信息，该组播/广播业务的描述信息中可以包括一个或多个组播/广播 业务流的描述信息，其中，组播/广播业务流的描述信息包括下列至少一项：组播/广播业务流应该具备的服务质量索引(QoS flow identifier，QFI)、组播/广播业务流的特征信息(如组播/广播业务的目的地址、目的端口号、源地址等)、组播/广播业务流的QoS需求(如，抖动、时延、丢包率、带宽、等)。组播/广播业务流的QoS需求用于建立组播/广播QoS流。除了组播/广播业务的描述信息之外，组播/广播业务的信息中还可以包含终端设备的信息，例如，可以包括允许(或请求)加入该组播/广播业务的一个或多个终端设备的标识、终端设备组的标识等。
应理解，本申请中的组播/广播业务可以替换为，组播/广播会话参数的业务，或者可以替换为组播/广播会话。
五、PDU会话、PDU会话隧道
PDU会话隧道与UE相对应，PDU会话隧道内的业务数据可以以单播QoS流的形式传输。本申请中，PDU会话隧道还可以用于传输组播/广播业务对应的组播/广播QoS流所映射的单播QoS流。
需要说明的是，PDU会话是UE级别的，组播/广播会话是业务级别的。一个UE的一个PDU会话可以与多个组播/广播业务关联，即，该UE可以通过该PDU会话加入至少一个组播/广播业务。一个组播/广播会话可以为一个组播/广播业务提供服务，一个组播/广播会话包括从数据网络到核心网设备再到接入网设备的单播隧道或组播隧道、以及接入网设备分配的用于发送该组播/广播业务的单播空口资源或组播/广播空口资源。
前文介绍了本申请所涉及到的一些用语，下面介绍本申请涉及的技术特征。需要说明的是，这些解释也不是对本申请所要求的保护范围的限定。
请参考图4，图4示例性地示出了通过单播方式传输数据的示意图。图4所示的传输流程既可以用于传输单播业务数据，也可以用于传输组播/广播业务数据。
在图4中，UE1、UE2和UE3中的每个UE分别对应一个不同的PDU会话。业务提供商(CP/SP)可以通过3条PDU会话，分别向UE1、UE2和UE3发送各自的业务数据。应理解，3个UE的业务数据均不相同，目标地址可分别为各UE的IP地址，各个UE的业务数据可以通过各个UE各自独立的传输路径分别发送给各UE。具体地，从CP/SP至RAN的业务传输路径可以包含CP/SP与UPF之间的传输路径、以及UPF与RAN之间的传输路径。UPF与RAN之间的传输路径可以称为PDU会话隧道，不同的PDU会话具有不同的PDU会话隧道。在空口上，RAN可以以单播的方式，即PTP方式，分别向UE1、UE2和UE3发送业务数据。
请参考图5，图5示例性地示出了通过组播/广播方式传输数据的示意图。图5所示的传输流程可以用于传输组播/广播业务数据。
在图5中，组播/广播业务数据可以从CP/SP发送至UE1、UE2和UE3。其中，从CP/SP至RAN的组播/广播业务传输路径可以包含CP与UPF之间的传输路径、以及UPF与RAN之间的传输路径。UPF到RAN的传输路径可以通过隧道传输组播/广播业务数据。例如，采用基于通用隧道协议(general tunnel protocol，GTP)的隧道。UPF与RAN之间的传输路径可以称为组播/广播会话隧道，该组播/广播会话隧道是UE 1、UE 2和UE 3共享的。在空口上，RAN可以通过PTM方式向UE1、UE2和UE3发送组播/广播业务数据，即RAN只需要发送一份数据，UE1、UE2和UE3可同时接收到。
采用组播方式，既可以实现一次向所有目标节点传输业务数据，也可以只对特定对象 传送业务数据，因此，在组播方式中，一个发送节点和多个接收节点之间可以实现点到多点的传输，从而解决了单播方式效率低的问题。
上述为单播与组播/广播的相关介绍。可以理解地，接入网设备支持组播/广播功能可以理解为接入网设备支持以组播/广播方式传输组播/广播业务数据，接入网设备不支持组播/广播功能可以理解为接入网设备不支持以组播/广播方式传输组播/广播业务数据，或者接入网设备仅支持以单播方式传输组播/广播业务数据或者PDU会话数据。对于不支持组播/广播功能的接入网设备，可以通过PDU会话向终端设备发送组播/广播业务，即将组播/广播业务映射到PDU会话。对于支持组播/广播功能的接入网设备，可以通过组播/广播会话隧道从核心网接收组播/广播业务数据并发送给加入该组播/广播业务的多个终端设备。应理解，组播/广播业务数据到达RAN之后，经过RAN的服务数据适配协议(service data adaptation protocol，SDAP)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层、物理(physical，PHY)层的处理，发送给每个接收组播/广播业务数据的UE。
为了在RRC-inactive态下的UE加入组播/广播业务时有效对组播/广播会话进行管理，以提高网络资源利用率，本申请实施例提供一种通信方法。该通信方法可由用户设备(或用于实现用户设备功能的组件，如芯片、处理器或通信模块等)和(R)AN设备(或用于实现用户设备功能的组件，如芯片、处理器或通信模块等)实施。本申请中以用户设备是UE，(R)AN设备是基站为例对该通信方法进行说明。可以理解的是，该通信方法也可以由本申请中涉及的其他类型的用户设备和/或(R)AN设备，或者说，本申请中的UE可替换为终端设备(或用户设备)，基站可替换为接入网设备或(R)AN设备。
如图6所示，本申请实施例提供的一种通信方法可包括以下步骤：
S101：终端确定接入网设备变更为第一接入网设备，或者，确定小区变更为第一接入网设备的小区。
以终端是UE且第一接入网设备是第一基站为例，UE确定基站变更为第一基站，或者，确定小区变更为第一基站的小区。UE已加入(joined)第一组播/广播业务且处于RRC-inactive。
其中，所述UE已加入(joined)第一组播/广播业务且处于无线资源控制非激活态(RRC-inactive)；或者，所述UE已加入第一组播/广播业务且允许处于RRC-inactive接收(allowed to receive)组播/广播业务，或接收组播/广播，或接收组播/广播数据。应注意，本申请中，“加入第一组播/广播业务”可替换为“加入第一组播/广播会话”，此外，组播/广播会话可以用于传输组播/广播业务。
在S101中，基站是指UE所接入的基站，该基站也可称为UE所附着(camp)的基站，还可以称为为UE服务的基站。S101中，“UE确定基站变更为第一基站”也可替换为，UE“确定/发现发生基站变更(或切换)，变更后的基站为第一基站”。本申请中，UE接入基站可以是指，UE位于基站的覆盖范围内；或者，可以指UE位于基站的覆盖范围内并且UE与该基站存在连接；或者可以指UE位于基站的覆盖范围内并且UE与该基站存在消息交互。
同理，S101中，小区是指UE接入的小区，该小区也可称为UE的小区或者UE所附 着(camp)的小区。在S101中，“确定小区变更为第一基站的小区”也可替换为，UE“确定/发现发生小区变更(或切换)，变更后的小区为第一基站的小区”。其中，小区变更可以包括：UE从第一基站的一个小区变更到第一基站的另一个小区，还可包括从其它基站的小区变更到第一基站的其中一个小区。本申请中，UE接入小区或者UE附着小区可以是指，UE位于小区的覆盖范围内并且UE与该小区建立连接；或者，可以指UE选择到小区支持的频率/频点/频段上。
在S101的一种可能的实现方式中，UE可接收第一信息，并根据第一信息确定基站变更为第一基站，或根据第一信息确定小区变更为第一基站的小区。
可选的，该第一信息可包括第一基站的标识和/或第一基站的小区的标识。因此，UE可根据第一基站的标识与此前(可以是指接收第一信息之前)接收到的基站的标识进行比对，以识别是否发生基站变更，和/或，UE可根据第一基站的小区的标识与此前(可以是指接收第一信息之前)接收到的小区的标识进行比对，以识别是否发生小区变更。
其中，UE此前接收到的基站的标识和/或小区的标识，可以携带在UE接收到第一信息之前，UE接收到的信息(在本申请中可称为第三信息)中。该第三信息的发送和接收方式可以和第一信息的发送和接收方式相类似，区别在于，第三信息可能来自于第一基站也可能来自于其他基站。本申请中，第一信息和第三信息均可称为用于携带基站标识和/或小区标识的信息。如果UE在接收第三信息和接收第一信息的位置或服务区域(这里可以指基站和小区的信号覆盖范围)相同，则第一信息与第三信息中可能携带相同的基站的标识和小区的标识，也就是说，第一信息和第三信息中均携带第一基站的标识和/或第一基站的小区的标识。此外，如果UE在接收第三信息和接收第一信息的位置或服务区域(这里可指基站和小区的覆盖范围中的任一项)不同，则第一信息与第三信息中可能携带不同的基站的标识和/或不同小区的标识，也就是说，此时第三信息中携带的基站的标识可以为第一基站以外的其他基站的标识，和/或，第三信息中携带的小区的标识与第一信息中的第一基站的小区的标识可以不同。
可选的，第三信息可以是UE在接收第一信息之前，接收的用于携带基站标识和/或小区标识的信息。可以理解的是，如果第三信息中包括的基站的标识为第二基站的标识，而无论第一信息中的小区的标识和第三信息中的小区的标识是否相同，UE均可根据第二基站的标识和第一基站的标识，确定基站从第二基站变更为第一基站，或者说，UE可确定发生基站变更。如果第三信息中包括的基站的标识与第一信息中包括的第一基站的标识相同，但第三信息中携带的小区的标识与第一信息中携带的小区的标识不同，则UE可根据这两个小区的标识，确定小区从第一基站的一个小区变更为第一基站的另一个小区，也就是，此时只发生了小区变更而未发生基站变更。
在另一种可能的实现方式中，如果UE附着的基站从第二基站变更为第一基站，UE还可根据从第二基站接收的区域指示信息或区域信息，UE根据区域指示信息或区域信息确定移出第二基站的覆盖范围/服务区域或第二基站的小区的覆盖范围/服务区域。示例性的，区域指示信息或区域信息可以包括接入网通知区域信息(RAN-NotificationAreaInfo)，接入网通知区域信息可以包括以下至少一项：小区标识(cell ID)、小区列表(cell list)、区域配置列表(ran-AreaConfigList)、追踪区码(tracking area code)、接入网区域码(RAN-AreaCode)、公共陆地移动网标识(public land mobile network ID，PLMN ID)，UE可接收来自于第二基站的区域指示信息或区域信息为第一区域。当UE确定移出所述第一 区域时，UE可确定发生基站/小区变更，例如，第一区域可以是接入网通知区域，第一区域可以包括第二基站包括的小区标识，或者可以包括第二基站的标识，或者可以包括第二基站的小区列表，或者可以包括第二基站的追踪区码，或者可以包括第二基站的接入网区域码。可选的，如果UE进一步根据第一区域确定变更后的基站为第一基站，则UE可确定基站从第二基站变更为第一基站。
下面以第一信息为例，说明本申请各个实施例中用于携带基站标识和小区标识的信息的发送方式和接收方式，第三信息可参照实施。
可以理解的是，第一信息可以是第一基站发送的，当UE位于第一基站的小区的覆盖区域内，可接收第一信息以识别是否发生基站变更和/或小区变更。
作为一种可能的实现方式，第一信息可携带在系统消息中，其中系统消息可以在广播控制信道(broadcast control channel，BCH)中发送。例如，第一信息携带在第一基站的小区发送的系统信息块(system information bloack，SIB)中，如携带在SIB1中。应理解，SIB1可用于携带UE接入基站或小区的信息或参数。示例性的，第一信息可以包括SIB1中的小区全局标识(cell global identity，CGI)。
作为另一种实现方式，第一信息可以携带在非UE粒度的消息中，例如，非UE粒度的消息组播控制信道发送的消息，或组播信道发送的消息。例如，第一信息可携带在组播控制信道(multicast control channel，MCCH)或组播信道(multicast channel。MCH)中。本申请中，MCCH或MCH可用于携带非UE粒度的组播/广播业务相关的信息，如用于接收组播/广播业务的配置信息等。
作为另外一种实现方式，第一信息可以携带在RRC消息中，例如，RRC消息可以是RRC重建(RRCReestablishment)消息，或者可以是RRC重配置(RRCReconfiguration)消息，等。
作为另外一种实现方式，第一信息可以携带在寻呼消息中，寻呼消息可以在寻呼信道中发送，例如，第一信息携带在组播/广播业务的组寻呼消息中，或者，例如，第一信息携带在针对UE的寻呼消息中。
可选的，除发送第一信息以外，本申请中的第一基站还可发送第二信息，该第二信息可用于UE从第一信息中读取第一基站的标识和/或第一基站的小区的标识。由于第一信息中的第一基站的标识和/或第一基站的小区的标识各自所占的位数(digits)或比特(bit)数(bits)或字节(octet/byte)数(octets/bytes)或十六进制数(hexadecimals)或十进制数(decimals)，以及第一基站的标识和/或第一基站的小区的编码方式，对于处于RRC-inactive态的UE来说可能是未知的，因此UE可能需要通过第二信息辅助读取第一基站的标识和/或第一基站的小区的标识。以第一信息是CGI为例，对于不同国家或不同移动网络运营商来说，CGI中包括的基站标识的占位数(digit/digits)和小区标识的占位数是不同的，因此，UE需要通过第二信息获知从第一信息中读取第一基站的标识和/或第一基站的小区的标识的方式，以便正确识别第一基站的标识和/或第一基站的小区的标识。
作为一种可能的示例，第二信息可用于指示第一信息中第一基站的标识的占位数或占用的比特或比特数或字节或字节数或十进制数或十六进制数，和/或，第二信息可用于指示第一信息中第一基站的小区的标识的占位数据或占用的比特或比特数或字节或字节数或十进制数或十六进制数。
其中，第二信息如果指示第一基站的标识占用的位数，如指示第一基站的标识占用第 一信息中的0-6位，和/或，指示第一基站的小区的标识占用的位数，如指示第一基站的标识占用第一信息中的7-10位，则UE可以根据第二信息获知第一信息中第一基站的标识和/或第一基站的小区的标识的占位数。
进一步，第二信息还指示第一信息中第一基站的标识和/或第一小区的标识的编码方式，例如，采用二进制还是八进制还是十进制还是十六进制，例如，如果第二信息包含的编码方式指示采用二进制编码，那么，例如，当第一信息中第一基站的标识占0～6位时，其值可以是010101；再例如，若第二信息包含的编码方式指示采用八进制编码，那么，例如，当第一信息中第一基站的标识占0～6位时，其值可以是276510；再例如，若第二信息包含的编码方式指示采用十进制编码，那么，例如，当第一信息中第一基站的标识占0～6位时，其值可以是123459；再例如，若第二信息包含的编码方式指示采用十六进制编码，那么，例如，当第一信息中第一基站的标识占0～6位时，其值可以是9ABC23。因此，如果UE已知第一信息中第一基站标识和/或第一基站的小区标识的占位长度，还知道基站标识和/或小区标识的编码方式，则UE可以从第一信息中读取第一基站的标识和第一基站的小区的标识。
应理解，本申请也不排除第二信息可指示第一基站的标识和/或第一基站的小区的标识)占用的位数和/或编码方式，由UE根据已知的第一信息的长度和/或第一基站的标识(或第一基站的小区的标识)占用的位数确定第一基站的小区的标识(或第一基站的标识)占用的位数。例如，UE已知第一信息的长度为10位，第二信息可指示第一基站的标识所占用的位数，则10个比特中的其余位数为第一基站的小区所占用的位数。
基于该示例，UE可根据第一基站的标识在第一信息中占用的位数或比特或比特数或字节或字节数准确读取第一基站的标识，和/或，根据第一基站的小区的标识占用的位数或/比特或比特数或字节或字节数，准确读取第一信息中的第一基站的小区的标识。
可选的，当第二信息指示第一基站的标识的字节数时，可指示X，以表示第一基站的标识由X个字节组成(consist of X octets/bytes)。
作为另一种示例，第二信息可用于指示第一信息中第一基站的标识的编码方式，和/或，第二信息可用于指示第一信息中第一基站的小区的标识的编码方式。例如，第一基站的标识的编码方式为第一编码方式，第一基站的小区的标识的编码方式为第二编码方式，且第一编码方式可以与第二编码方式相同或不同，则UE可根据第一编码方式对第一信息中的基站标识进行解码，如果能够成功解码第一信息中的部分比特或字节，则该部分比特或字节为第一基站的标识；同理，UE可根据第二编码方式对第一信息中的小区标识进行解码，如果能够成功解码第一信息中的部分比特或字节，则该部分比特或字节为第一基站的小区的标识。
应理解，以上第二信息也可以是UE从第一基站以外的渠道获取的。例如，UE可以从服务器(例如，第三方服务器或应用服务器或AF))获取第二信息。或者，UE可以从运营商的初始配置信息中获取第二信息。或者，UE可以从自身获取第二信息，例如，从出厂配置信息或本地的其他配置信息中读取第二信息。或者，UE可以从接入网设备(例如，第一基站或其他基站)获取第二信息。或者，UE可以从核心网网元获得第二信息，例如，核心网网元可包括SMF、UPF、AMF、NWDAF、PCF、UDM、UDR、NEF、MB-SMF、MB-UPF、MBSTF、MBSF、NRF、AUSF、UDSF、NSSF、CHF、SEPP、受信任的非3GPP 网关功能(trusted non-3GPP gateway function，TNGF)、SCP、或AF中的至少一个。
示例性的，UE可以在S101之前通过接收或从本地的配置信息(如运营商的初始配置信息和/或出厂配置信息)中获取等方式获得第二信息。其中，本申请不限定该第二信息是UE在何种RRC连接状态下获取的，例如，可以是UE在连接态下接收的，例如，UE可以在注册过程中从基站(包括但不限于第一基站)接收第二信息，第二信息也可以是UE在进入RRC-inactive态后接收的，第二信息还可以是UE在空闲态接收的，例如，第二信息可包括在SIB消息、MCCH信道的消息、RRC消息、寻呼消息、或MCH发送的消息中，本申请不作具体要求。
应理解，本申请中，UE可通过与解读第一信息相类似的实现方式，解读第三信息中的基站的标识和/或小区的标识。其中，如果第一信息中的第一基站的标识，与第三信息中的基站的标识的占用的位数或比特或比特数或字节或字节数相同，以及，编码方式相同，则UE可通过第二信息读取第一信息中的对应基站的标识以及读取第三信息中的基站的标识。如果第一信息中的第一基站的标识，与第三信息中的基站的标识的占用的位数或比特或比特数或字节或字节数相同，以及编码方式不同，则UE可通过第四信息读取第三信息中的基站的标识。其中，该第四信息的设置方式(如信息指示的内容、使用方式等)和UE获取第四信息的方式(或称为获取方式，包括信息携带的位置)可以参照第二信息的设置方式和获取方式。例如，第四信息可指示第三信息中的基站的标识的占用的位数或比特或比特数或字节或字节数相同，以及编码方式；又如，UE可从第三信息包括的基站标识所属的基站或其他渠道获取该第三信息。
同理，如果第一信息中的第一基站的小区的标识，与第三信息中的小区的标识的占用的位数或比特或比特数或字节或字节数相同，以及编码方式相同，则UE可通过第二信息读取第一信息中的第一基站的小区的标识以及读取第三信息中的小区的标识。如果第一信息中的第一基站的小区的标识，与第三信息中的小区的标识的占用的位数或比特或比特数或字节或字节数相同，以及编码方式不同，则UE可通过第五信息读取第三信息中的小区的标识。其中，该第五信息的设置方式和UE获取第五信息的方式可以参照第二信息。例如，第五信息可指示第三信息中的小区的标识的占用的位数或比特或比特数或字节或字节数或编码方式；又如，UE可从第三信息包括的小区标识所属的基站或其他渠道获取该第三信息。
应理解，S101也可替换为：UE发现(find/know)基站变更为第一基站(find the NG-RAN is changed)，或者，确定小区变更为第一基站的小区(find the cell is chnaged)。
此外，S101还可以替换为：UE确定/发现未接收到第一组播/广播业务的数据或未收到第一组播/广播业务或未收到第一组播/广播数据，所述UE已加入所述第一组播/广播业务且处于RRC-inactive态。
S102：终端向第一接入网设备发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一项。
以终端是UE且第一接入网设备是第一基站为例，UE可向第一基站发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一项。
相应的，第一基站接收第一消息、第二消息、第三消息、第九消息或第十消息中的至少一项。
下面分别对第一消息、第二消息、第三消息、第九消息和第十消息进行说明。
(1)第一消息可以用于指示第一基站发送第一组播/广播业务的数据，或者第一消息可以用于指示对所述第一组播/广播业务感兴趣(indicate interest on the related MBS session)。
其中，第一组播/广播业务的数据可替换为第一组播/广播业务或第一组播/广播数据或第一组播/广播会话的数据。
可选的，本申请中，第一消息用于指示第一基站发送第一组播/广播业务的数据，可替换为，第一消息用于通知第一基站发送第一组播/广播业务的数据。或者，第一消息用于指示第一基站发送第一组播/广播业务的数据，可替换为，第一消息用于通知或指示第一基站发送第一组播/广播业务的接收配置。其中，接收配置也可称为用于接收第一组播/广播业务的配置信息，如包括点到多点配置(PTM configuration)，接收配置(reception configuration)等。
应理解，第一消息中可携带用于指示或通知第一基站发送第一组播/广播业务的数据或用于通知或指示第一基站发送第一组播/广播业务的接收配置的信息，或者，第一消息可以是用于指示或通知第一基站发送第一组播/广播业务的数据或用于通知或指示第一基站发送第一组播/广播业务的接收配置的消息。例如，第一消息可携带第一组播/广播业务的标识，标识可以是组播/广播业务或组播/广播会话的标识MBS session ID，MBS session ID可以是临时移动组标识(temporary mobile group identity，TMGI)，MBS session ID还可以是IP组播地址(IP pulticast address)。
应理解，用于指示或通知第一基站发送第一组播/广播业务还可以理解为用于指示或通知第一基站触发建立组播/广播会话，或者还可以理解为触发第一基站触发建立5G核心网共享组播/广播业务流量传输(5GC shared MBS traffic delivery)。
示例性的，如果UE在确定基站或小区发生变更后，未接收到第一组播/广播业务的数据，则UE可以在S102中发送该第一消息，以指示第一基站发送该第一组播/广播业务的数据和/或接收配置。同时，UE可通过该第一消息隐式指示第一基站更新第一组播/广播会话的上下文，实现对第一组播/广播会话的有效管理，提高网络资源利用率。
(2)第二消息用于指示第一基站更新第一组播/广播业务的上下文，或者第二消息可以用于指示对所述第一组播/广播业务感兴趣；
其中，第一组播/广播业务的上下文可替换为第一组播/广播会话的上下文。
示例性的，如果UE在确定基站或小区发生变更后，仍然接收到第一组播/广播业务的数据，则UE可以在S102中发送该第二消息，以指示第一基站更新第一组播/广播会话上下文，以实现对第一组播/广播会话的有效管理，提高网络资源利用率。
(3)第三消息用于恢复UE的RRC连接。或者说，第三消息可用于请求进入RRC连接态。
其中，第三消息可包括RRC恢复请求(RRC resume request)消息。
示例性的，如果UE可以在确定基站或小区发生变更后，发送第三消息，而无论是否在确定基站或小区发生变更后接收到第一组播/广播业务的数据。因此，UE可通过第三消息请求恢复到RRC连接态，以便UE在RRC连接态下接收该第一组播/广播业务的数据和/或接收配置。同时，UE可通过该第三消息隐式指示第一基站更新第一组播/广播会话的上下文，还可通过该第三消息隐式指示第一基站建立组播/广播会话，实现对第一组播/广播会话的有效管理，提高网络资源利用率。
(4)第九消息用于激活用户面连接。或者说，第九消息可以用于请求激活关联的PDU 会话(associated PDU session)的用户面连接，或者用于请求激活关联的PDU会话，所述关联的PDU会话与第一组播/广播业务关联可以理解为，UE可以通过关联的PDU会话的控制面信令请求加入或退出第一组播/广播业务。在成功加入第一组播/广播业务后，关联的PDU会话还可以用于传输第一组播/广播业务的数据。示例性的，如果UE发现/确定未收到第一组播/广播业务，例如，原因是变更后的第一基站不支持UE在RRC-inactive态接收数据，或者再例如，如果变更后的基站或小区在RNA之外，也即，UE移出了RNA区域，并且变更后的基站不支持UE在RRC-inactive态接收数据，则UE可以发送第九消息至第一基站，第九消息携带关联的PDU会话的ID，第九消息可以是服务请求(service request)消息，之后第一基站将第九消息发送至AMF，AMF进一步发送至SMF，触发激活关联的PDU会话ID，并进一步触发建立第一组播/广播会话至所述第一基站。
(5)所述第十消息用于请求注册。或者说，第十消息可以用于UE请求注册至网络。示例性的，如果UE发现/确定未收到第一组播/广播业务，并且UE移出注册区域(registration area，RA)，例如，因为变更后的第一基站或小区在注册区域之外，UE可以发送第十消息至基站，第十消息携带关联的PDU会话的ID，第十消息可以是注册请求(registration request)消息，之后第一基站将第十消息发送至AMF，AMF进一步发送至SMF，触发激活关联的PDU会话ID，并进一步触发建立第一组播/广播会话至第一基站。
以上第一消息、第二消息或第三消息可以是无线(radio)消息，无线消息可以是RRC消息。其中，RRC消息可以是RRC恢复请求(RRC resume request)消息。无线消息还可以是其它非RRC消息，例如，非RRC消息虽然与RRC消息名称不同，但是可具有与RRC消息具有相同或者类似的功能。这里的功能至少包括以上第一消息、第二消息或第三消息的指示功能(如指示第一消息、第二消息或第三消息所指示的内容)或通知功能(如通知第一消息、第二消息或第三消息所通知的内容)。
以上第九消息或第十消息可以是非接入层(non-access stratum，NAS)消息，NAS消息可以是服务请求消息，或者可以是注册请求消息，或者还可以是上行非接入层数据传输(UL NAS transport)消息，还可以是其它NAS消息，不限定。
应理解，以上第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息中，可包括UE的标识、第一组播/广播业务的标识或UE发送该消息的原因中的至少一项。
本申请中的各个实施例中，UE的标识例如包括UE的非激活态无线网络临时标识(inactive radio network temporary identifier，I-RNTI)或者可以是无线网络临时标识(radio network temporary identifier，RNTI)或者可以是5G临时移动签约标识(5G s-temporary mobile subscription identifier，5G-S-TMSI)，用户永久标识符(subscription permanent identifier，SUPI)、通用公共用户标识(generic public subscription identifier，GPSI)、用户隐藏标识符(subscription concealed identifier，SUCI)、一般公共订阅标识符(generic public subscription identifier，GPSI)、永久设备标识(permanent equipment identifier，PEI)、国际移动用户识别码(international mobile subscriber identity，IMSI)、全局唯一的临时标识(globally unique temporary identity，GUTI)，或NG应用层协议(NG application protocol，NGAP)标识(NGAP UE ID)。其中，NGAP UE ID可包括基站分配的RAN NGAP UE ID和/或AMF分配的AMF NGAP UE ID。
此外，第一组播/广播业务的标识可包括第一组播/广播业务的组播/广播会话的标识， 第一组播/广播业务的组播/广播会话也可称为第一组播/广播会话，第一组播/广播业务的组播/广播会话的标识也可称为第一组播/广播会话标识(MBS session ID)。本申请中，组播/广播会话标识可以是TMGI，也可以是源特定IP地址(source specific IP address)，源特定IP地址可以理解为组播/广播组的地址，希望加入该组播/广播业务的终端或网元可以向该源特定IP地址发送加入请求消息，其可作为组播/广播业务标识的一种类型。
UE发送该消息的原因可以包括，该消息用于请求接收第一组播/广播业务的数据，或者，该消息用于获取接收第一组播/广播业务的配置信息，或者，该消息用于触发第一组播/广播业务的会话(也可称为第一组播/广播会话)的建立，或者，该消息用于指示该第一组播/广播业务感兴趣，或者，该消息用于指示请求加入该第一组播/广播业务。该消息中可携带以上示例的原因中至少一个原因对应的标识、原因值、索引或指示信息以指示相应的原因。
此外，如果UE确定基站从第二基站变更为第一基站，则以上第一消息、第二消息或第三消息中的至少一个消息中还可包括该第二基站的标识。
基于图6所示流程，当已加入第一组播/广播业务且处于RRC-inactive态的UE确定基站变更为第一基站，或者，当该UE确定小区变更为第一基站中的小区，则UE可以向第一基站发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息。相应的，第一基站可根据第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息，获知该UE移动到其覆盖范围下接收第一组播/广播业务，以及时创建第一组播/广播会话或者更新第一组播/广播会话上下文，实现对第一组播/广播会话的有效管理，提高网络资源利用率。
此外，还应理解，S101中的“UE确定基站变更为第一基站，或者，确定小区变更为第一基站的小区。UE已加入所述第一组播/广播业务且处于RRC-inactive态”，也可以替换为：“UE确定或发现(find)未接收到第一组播/广播业务的数据(no multicast/MBS data received)，所述UE已加入所述第一组播/广播业务且处于RRC-inactive态。可选的，在该替换的描述方式中，UE确定未接收到第一组播/广播业务的数据的原因可能包括，UE发生基站变更，或者，UE发生小区变更。其中，UE可按照S101中介绍的方法确定基站发生变更和/或确定小区发生变更。
也就是说，本申请中触发UE执行S102的条件包括以下中的至少一项：UE确定基站变更为第一基站，例如，由与第一基站不同的基站变更为第一基站；或者，UE确定小区变更，例如，与第一基站下之前附着的小区不同的小区或者不在第一基站下的其它小区；或者，UE确定/发现未接收到第一组播/广播业务的数据；或者，UE移出注册区域。
下面对第一基站在接收到第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息后的处理方式进行说明。其中，根据UE是否发生基站变更，第一基站的处理方式至少包括以下处理方式中的方式1和方式2。
可以理解的是，如果UE的基站未变更而只是UE的小区发生变更，则第一基站接收到的第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息中，可以不包括其他基站的标识，示例性的，此时可通过方式1更新第一组播/广播会话的上下文。如果第一基站接收到的第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息中，包括第二基站的标识，则可以表示UE的基站从第二基站变更为第一基站，则此 时可通过方式2更新第一组播/广播会话的上下文。
方式1
如果UE的基站未变更，而只是UE的小区发生变更，如果UE没有收到第一组播/广播业务，则第一基站触发第一组播/广播会话的建立，例如，第一基站可以将所述第一组播/广播业务向该小区建立或者向该小区发放或者向该小区建立；如果UE收到了第一组播/广播业务，则第一基站可更新第一组播/广播会话上下文。例如，如果第一组播/广播会话上下文中包含通过该基站的小区加入第一组播/广播会话的UE标识与数量，则第一基站可在接收到第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息后，第一基站可以将所述第一组播/广播业务向该小区建立或者向该小区发放或者向该小区建立，使得该小区及时获知新的UE移动到其覆盖区域内接收第一组播/广播业务。
在方式1中，如果第一基站接收到的消息包括第一消息(或包括第一消息和第三消息)，并且第一基站已建立第一组播/广播会话，或者，第一基站已存储有第一组播/广播会话的上下文，则第一基站可响应于第一消息更新第一组播/广播会话的上下文，例如，第一基站可以将所述UE的标识添加至第一组播/广播会话上下文的第一基站的该小区的UE标识列表中，此外，第一基站还可以将通过该小区假如第一组播/广播会话的UE数量加1。
此外在方式1中，第一基站还可向UE发送第一组播/广播业务的接收配置。其中，如前文所述，如果UE在确定基站变更或小区变更后，未接收到第一组播/广播业务的数据，则UE在S102中可以至少发送第一消息。
其中，UE未接收到第一组播/广播业务的数据的原因可能是，UE移动到了此前未建立第一组播/广播会话的第一基站，或者，UE未获得当前小区下的第一组播/广播业务的接收配置。在方式1中，只考虑UE由于未获得当前小区下的第一组播/广播业务的接收配置而没接收到相应数据，因为UE在变更小区前已加入第一组播/广播业务，说明第一基站已建立组播/广播会话。因此，当第一基站接收到来自于UE的第一消息，可向UE发送接收配置，使得UE根据接收配置接收第一组播/广播业务的数据。
另外，如果第一基站在S102中接收的消息包括第二消息(或包括第二消息和第三消息)，则第一基站可响应于第二消息，更新第一组播/广播会话的上下文。其中，如前文所述，如果UE在确定基站变更或小区变更后，未接收到第一组播/广播业务的数据，则UE在S102中可以至少发送第二消息。因此，当接收到第二消息，表示UE目前仍然能够接收到第一组播/广播业务的数据，第一基站只需要对第一组播/广播会话的上下文进行更新可以不需要向UE发送第一组播/广播业务的接收配置。
当第一基站在S102中接收到的消息包括第三消息，第一基站既可以触发发送第一组播/广播业务的数据，也可以进行第一组播/广播业务上下文的更，例如，在第三消息中还携带了原因值的情况，也即，发送第三消息的原因，这样，第一基站可以区分发送第三消息的原因。
方式2
为了方便说明，可根据S102中UE发送消息的类型，将方式2分为方式2.1，方式2.2，方式2.3，方式2.4，和方式2.5。其中，方式2.1中，UE在S102中发送的消息包括第一消息；在方式2.2中，UE在S102中发送的消息包括第二消息；在方式2.3中，UE在S102中发送的消息包括第三消息；在方式2.4中，UE在S102中发送的消息包括第九消息；在方式2.5中，UE在S102中发送的消息包括第十消息。
方式2.1
当UE的基站发生变更，并且第一基站在S102中接收的消息包括第一消息(或包括第一消息和第三消息)，由于UE未接收到第一组播/广播业务的数据的原因可能是，UE移动到了此前未建立第一组播/广播会话的第一基站，或者，UE未获得当前基站下的第一组播/广播业务的接收配置。因此，当第一基站接收到来自于UE的第一消息，需要判断是否已建立该第一组播/广播会话(或判断是否已存储有该第一组播/广播会话的上下文)，根据判断结果进行不同的第一组播/广播会话的上下文的更新操作。
具体的，方式2中，当第一基站在S102中接收到的消息包括第一消息，则第一基站的更新操作可包括方式2.1.1或方式2.1.2所示的实现方式。
方式2.1.1
当UE的基站发生变更，并且第一基站在S102中接收的消息包括第一消息，且第一基站确定未建立第一组播/广播会话，或者说，第一基站未存储有第一组播/广播会话的上下文，则第一基站可以触发第一组播/广播会话的建立，并通过该第一组播/广播会话的建立过程获得第一组播/广播会话的上下文。也就是说，方式2.1.1中，第一组播/广播会话的上下文的更新操作包括第一基站在第一组播/广播会话的建立过程中获得第一组播/广播会话的上下文。
此外在方式2.1.1中，第一基站还可在建立第一组播/广播会话后，向UE发送第一组播/广播会话的接收配置，使得UE根据该第一组播/广播会话的接收配置进行第一组播/广播业务的数据的接收。
此外在方式2.1.1中，第一基站还可以对发送第一消息的UE进行鉴权(authorize)或检查(check)，也即，因为UE的上下文还在变更为第一基站前的基站中，并且UE的上下文中也有UE之前加入的第一组播/广播业务的信息。因此，例如，第一基站可以向变更为第一基站前的基站发送消息，请求鉴权或检查UE是否已经加入第一组播/广播业务，如果通过反馈消息或者UE已经加入第一组播/广播业务，则第一基站可以触发第一组播/广播会话的建立，并通过该第一组播/广播会话的建立过程获得第一组播/广播会话的上下文。
方式2.1.2
当UE的基站发生变更，并且第一基站在S102中接收的消息包括第一消息，且第一基站确定已建立第一组播/广播会话，或者说，第一基站已存储有第一组播/广播会话的上下文，则第一基站可以更新该第一组播/广播会话的上下文。
例如，第一基站可更新第一组播/广播会话上下文中的加入该组播/广播会话的UE的数量，以便第一基站可以获知在该基站接收第一组播/广播会话数据的UE数量。
此外在方式2.1.2中，第一基站还可向UE发送第一组播/广播会话的接收配置，使得UE根据该第一组播/广播会话的接收配置进行第一组播/广播业务的数据的接收。
此外在方式2.1.2中，第一基站还可以对发送第一消息的UE进行鉴权(authorize)或检查(check)，也即，因为UE的上下文还在变更为第一基站前的基站中，并且UE的上下文中也有UE之前加入的第一组播/广播业务的信息。因此，例如，第一基站可以向变更为第一基站前的基站发送消息，请求鉴权或检查UE是否已经加入第一组播/广播业务，如果通过反馈消息或者UE已经加入第一组播/广播业务，则第一基站可以触发对第一组播/广播会话上下文的更新。
方式2.2
如果第一基站在S102中接收到的消息包括第二消息，则表示UE目前仍然能够接收到第一组播/广播业务的数据，也就是说第一基站已经存储有对第一组播/广播会话的上下文，因此第一基站只需要对已经存储的第一组播/广播会话的上下文进行更新而不需要向UE发送第一组播/广播业务的接收配置。第一基站对第一组播/广播会话的上下文进行更新的过程可参见方式1或方式2.1.2，这里不再展开。
此外在方式2.2中，第一基站还可以对发送第二消息的UE进行鉴权(authorize)或检查(check)，鉴权或检查，也即，因为UE的上下文还在变更为第一基站前的基站中，并且UE的上下文中也有UE之前加入的第一组播/广播业务的信息。因此，例如，第一基站可以向变更为第一基站前的基站发送消息，请求鉴权或检查UE是否已经加入第一组播/广播业务，如果通过反馈消息或者UE已经加入第一组播/广播业务，则第一基站可以触发对第一组播/广播会话上下文的更新。
方式2.3
如果第一基站在S102中接收到的消息包括第三消息，则第一基站可响应于第三消息对已经存储的第一组播/广播会话的上下文进行更新。方式2.3中，第一基站对第一组播/广播会话的上下文进行更新的过程可参见方式1或方式2.2，这里不再展开。
方式2.4
如果第一基站在S102中接收到的消息包括第九消息，例如，第九消息可以是服务请求消息，则可以表示UE没有收到第一组播/广播业务的数据，例如，UE移动到的第一基站不支持UE在RRC-inactive态接收第一组播/广播业务的数据。再例如，UE移动到的第一基站在RNA之外，也即，UE移出了RNA区域，并且第一基站不支持UE在RRC-inactive态接收数据，则UE发起(invoke)服务请求消息，携带第一协议数据单元PDU会话标识，用于请求激活所述第一PDU会话，进而触发第一组播/广播会话建立。所述第一PDU会话与所述第一组播/广播业务关联。所述第一PDU会话与第一组播/广播业务关联可以理解为，UE可以通过第一PDU会话的控制面信令请求加入或退出第一组播/广播业务，加入成功之后，第一PDU会话还可以用于传输第一组播/广播业务的数据。
方式2.5
如果第一基站在S102中接收到的消息包括第十消息，例如，第十消息可以是注册请求消息，则可以表示UE移动到的第一基站在UE的注册区域之外。则UE发起(invoke)注册请求消息，携带第一协议数据单元PDU会话标识，用于请求激活所述第一PDU会话，进而触发第一组播/广播会话建立。所述第一PDU会话与所述第一组播/广播业务关联。所述第一PDU会话与第一组播/广播业务关联可以理解为，UE可以通过第一PDU会话的控制面信令请求加入或退出第一组播/广播业务，加入成功之后，第一PDU会话还可以用于传输第一组播/广播业务的数据。
应理解，在方式2中，UE的基站从第二基站变更为第一基站，因此除了需要第一基站更新该第一组播/广播业务的上下文，还需要第二基站更新该第一组播/广播业务的上下文，因为UE已经不在该第二基站的覆盖范围内了。
示例性的，方式2中可由第一基站向第二基站发送消息，使得第二基站更新该第一组播/广播业务的上下文，方式2中以第四消息或第五消息或第八消息为例进行介绍，本申请不限定还可通过其他消息实现通知或指示第二基站更新该第一组播/广播业务的上下文的功能。
示例性的，在第一基站接收到第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个消息后，第一基站可根据该消息中携带的该第二基站的标识，向第二基站发送第四消息或第五消息或第八消息，从而由第二基站根据第四消息或第五消息或第八消息更新第一组播/广播会话的上下文。因此也可以说，第四消息和/或第五消息和/或第八消息用于触发由第二基站更新第一组播/广播会话的上下文。
示例性的，该第四消息可用于第二基站更新第一组播/广播会话的上下文。该第五消息可用于提取所述UE的上下文。该第八消息用于鉴权UE是否已经加入所述第一组播/广播业务。
可选的，第四消息或第五消息或第八消息可以是Xn消息或X2消息或基站之间发送的消息。
可选的，第四消息和/或第五消息和/或第八消息中可包括UE标识和/或第一组播/广播业务的标识。
其中，如果第四消息和/或第五消息和/或第八消息中包括UE的标识，则第二基站可对该UE标识关联的全部组播/广播会话的上下文进行更新。例如，从全部包括该UE标识的组播/广播会话的上下文中，删除该UE的标识，和/或，将加入这些组播/广播会话的UE的数量减去UE的标识的数量。如果第四消息和/或第五消息和/或第八消息中包括第一组播/广播业务的标识，则第二基站可对该第一组播/广播业务的标识关联的第一组播/广播会话的上下文进行更新，如从该第一组播/广播会话的上下文中删除该UE的标识，和/或，将第一组播/广播会话的上下文中加入该第一组播/广播会话的UE的数量减去UE的标识的数量。应理解，这里的UE的标识的数量可以是一个或多个，例如，一个或多个UE发生移动后执行图6所示方法。
可选地，第二基站收到第八消息还可以鉴权或检查(check)UE是否已经加入第一组播/广播会话，例如，只有鉴权或检查成功后，才会向第一基站发送第六消息。
当第二基站接收到第四消息和/或第五消息，则更新第一组播/广播会话的上下文，以及时更新该组播/广播会话的资源，从而提高网络资源利用率。
可选的，如果第二基站更新第一组播/广播业务的上下文后，该上下文中的加入第一组播/广播业务的UE数量为0，或者，加入第一组播/广播业务的UE标识为空，也即，第一加入第一组播/广播业务的UE标识或UE不存在，则第二基站可释放该第一组播/广播会话或者释放该第一组播/广播会话的共享组播/广播业务流量传输。
可选地，第二基站确定第一计时器过期(expired)，所述第二基站可释放该第一传输资源，所述第一传输资源用于传输所述第一组播/广播业务。其中，第一传输资源可以是第一组播/广播会话，或者第一传输资源可以是共享组播/广播业务流量传输。此外，第一计时器可以是周期性接入网通知区域更新计时器(periodic RAN notification area update，RNAU)Timer)。
此外，如果第一基站根据UE的标识，确定未存储有该UE的上下文，则第一基站可向第二基站发送第五消息，第二基站可根据该第五消息，向第一基站发送该UE的上下文。
可选的，本申请的各个实施例中，还可由第二基站向第一基站发送第六消息，其中第六消息可以包括该第一组播/广播业务的配置(可称为第一配置)，该第一配置可用于传输第一组播/广播业务的数据，例如，该第一配置可以包括点到多点配置(PTM configuration)，该第一配置还可以包括点到多点控制信息(PTM control information)，该第一配置还可以 包括组播/广播业务配置(MBS configuration)，该第一配置还可以包括点到多点控制信息(PTM control information)。第六消息还可以包括所述UE的上下文信息，该UE的上下文信息可以包括UE的相关信息，例如，可以包括UE的标识信息，标识信息可以是I-RNTI，例如这个I-RNTI可以是第二基站新生成的I-RNTI；UE的上下文信息还可以包括UE的PDU会话的信息，例如，PDU会话的信息可以包括PDU会话所包含的QoS flow的参数信息；UE的上下文信息还可以包括周期性接入网通知区域计时器(periodic RNAU timer)。第六消息还可以包括所述第一组播/广播业务的信息，第一组播/广播业务的信息可以包括所述第一组播/广播业务的标识，第一组播/广播业务的组播/广播QoS信息，组播/广播QoS信息可以包括组播/广播QoS参数，等。
第一基站收到第六消息后，可以向所述UE发送第七消息，所述第七消息包括所述第一配置或第一能力信息。所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一能力信息用于指示第一基站是否支持RRC-inactive态接收(或称，第一能力信息用于指示第一基站是否支持UE在RRC-inactive态接收组播/广播业务(或第一组播/广播业务)的数据)，所述第一能力信息可以是在第一基站支持该能力时发送。
所述第一能力信息可以是比特位的方式，例如，当取值为1时，表示支持RRC-inactive态接收，当取值为0时，表示不支持RRC-inactive态接收；或者，当取值为0时，表示支持RRC-inactive态接收，当取值为1时，表示不支持RRC-inactive态接收。
作为另外一个示例，第一能力信息可以是枚举类型(enumeration)，当取值为某个整数时，表示支持RRC-inactive态接收，当取值为另一个整数时，表示不支持RRC-inactive态接收。
作为另外一个示例，第一能力信息可以为一个或多个信元(information element，IE)，当一个或多个信元出现时，表示支持RRC-inactive态接收，当一个或多个信元不出现时，表示不支持RRC-inactive态接收；或者，当一个或多个信元出现时，表示不支持RRC-inactive态接收，当一个或多个信元不出现时，表示支持RRC-inactive态接收。
所述指示是否支持无线资源控制去激活态接收可以理解为：
支持在无线资源控制去激活态接收(support the RRC-inactive MBS data reception)；
不支持在无线资源控制去激活态接收(does not support the RRC-inactive MBS data reception)；
支持在无线资源控制去激活态发送(support the RRC-inactive MBS data transmission)；
不支持在无线资源控制去激活态发送(does not support the RRC-inactive MBS data transmission)；
支持在无线资源控制去激活态接收的能力(has the capability to support reception in RRC-inactive state)；
不支持在无线资源控制去激活态接收的能力(does not have the capability to support reception in RRC-inactive state)；
支持在RRC-inactive态发送的能力(has the capability to support the RRC-inactive MBS data transmission)；
不支持在RRC-inactive态发送的能力(does not have the capability to support the RRC-inactive MBS data transmission)；
可选地，若第七消息携带的第一能力信息指示第一基站支持在无线资源控制去激活态 接收，若UE还未收到第一组播/广播业务，基于第一能力信息的指示，UE可以获知第一组播/广播业务即将发送(is going to be transferred)并且可以不需要发起服务请求(not need perform Service Request)消息，服务请求消息可以理解为第九消息的一种，该服务请求消息。若第七消息未携带第一能力信息，并且UE还未收到第一组播/广播业务，则UE发起(invoke)服务请求消息，携带第一协议数据单元PDU会话标识，用于请求激活所述第一PDU会话，进而触发第一组播/广播会话建立。所述第一PDU会话与所述第一组播/广播业务关联。应理解，所述第一PDU会话与第一组播/广播业务关联可以理解为，UE可以通过第一PDU会话的控制面信令请求加入或退出第一组播/广播业务，加入成功之后，第一PDU会话还可以用于传输第一组播/广播业务的数据。
示例性的，如图7所示，本申请提供的一种基于上述方式2.1的通信方法可包括以下步骤：
S201：UE确定基站变更为第一基站或者小区变更为第一基站的小区，和/或，UE确定/发现未接收到第一组播/广播业务的数据。
S202：UE向第一基站发送第一消息，其中，第一消息可指示第一基站发送第一组播/广播业务的数据，或者，第一消息可指示第一基站发送第一组播/广播业务的接收配置，或者第一消息可以用于指示对所述第一组播/广播业务感兴趣(indicate interest on the related MBS session)。
相应的，第一基站接收第一消息。
S203：第一基站确定是否已建立第一组播/广播会话，和/或，第一基站确定是否存储有第一组播/广播会话的上下文。
其中，对应于方式2.1.2，如果第一基站确定未建立第一组播/广播会话，和/或，第一基站确定未存储有第一组播/广播会话的上下文，则执行S205和S206。
对应于方式2.1.1，如果第一基站确定已建立第一组播/广播会话，和/或，第一基站确定存储有第一组播/广播会话的上下文，则执行S204和S206。
S204：第一基站触发第一组播/广播会话的建立，并在第一组播/广播会话的建立过程中获得第一组播/广播会话的上下文。
应理解，本申请对于第一组播/广播会话的建立方式不做要求。
S205：第一基站更新第一组播/广播会话的上下文。
其中，第一基站更新第一组播/广播会话的上下文的方式可参见方式2.1.2中的说明。
S206：第一基站向UE发送第一组播/广播业务的数据和/或接收配置。
其中，如果执行S204，则该接收配置可以是在通过S204建立第一组播/广播会话的过程中获得的。如果执行S205，则该接收配置可以是第一基站在此前建立第一组播/广播会话的过程中获得的。
可选的，如果S201中，UE确定基站由第二基站变更为第一基站，则S202中的第一消息中可包括第二基站的标识或UE的标识。
当第一基站获取第一消息中的第二基站的标识，或者，获取第一消息中的UE的标识并根据UE的标识识别UE的源基站(last serving NG-RAN/last serving gNB/source NG-RAN)为第二基站(即UE的基站由第二基站变更为第一基站)，则在图7所示的S202之后，还可执行以下步骤：
S207：第一基站可向第二基站发送第四消息、第五消息或第八消息中的至少一个消息。
其中，第四消息可用于通知第二基站更新第一组播/广播会话的上下文。
该第五消息可用于提取该UE的上下文。
第八消息可用于鉴权UE是否已经加入所述第一组播/广播业务，第八消息可以携带UE标识和第一组播/广播业务标识。
第四消息、第五消息和第八消息都可以为Xn消息或X2消息，也即，都可以为用于基站之间进行通信的消息。
可选的，第四消息、第五消息或第八消息中的至少一个消息可包括第一组播/广播会话的标识和/或UE的标识。
相应的，第二基站接收第四消息、第五消息或第八消息中的至少一个消息。
S208：第二基站可响应于第四消息、第五消息或第八消息中的至少一个消息，更新第二基站中的第一组播/广播会话的上下文。
例如，第二基站可根据第四消息、第五消息或第八消息中的至少一个消息中携带的UE的标识和/或第一组播/广播业务的标识，对第一组播/广播会话的上下文进行更新，具体可参见本申请中的说明，这里不再赘述。
再例如，第二基站可根据第八消息中携带的UE的标识和第一组播/广播业务的标识，对UE进行鉴权或检查(check)，也即，鉴权UE是否已经加入了第一组播/广播业务，例如，若第二基站发现存储的第一组播/广播业务上下文中没有UE的标识或者UE的上下文中没有第一组播/广播业务的信息，则鉴权失败；若第二基站发现存储的第一组播/广播业务上下文中有UE的标识或者UE的上下文中有第一组播/广播业务的信息，则鉴权成功。
S209：第二基站向第一基站发送第四消息、第五消息或第八消息中的至少一个消息的响应消息。
可选的，该响应消息可以是第六消息，第六消息可以是Xn消息或者X2消息或者可以是用于基站之间通信的消息。
第六消息可以包括UE的上下文信息，该UE的上下文信息可以包括UE的相关信息，例如，可以包括UE的标识信息，标识信息可以是I-RNTI。例如，这个I-RNTI可以是第二基站新生成的I-RNTI。UE的上下文信息还可以包括终端设备的PDU会话的信息。例如，PDU会话的信息可以包括PDU会话所包含的QoS flow的参数信息。UE的上下文信息还可以包括周期性接入网通知区域计时器(periodic RNAU timer)。第六消息还可以包括所述第一组播/广播业务的信息，第一组播/广播业务的信息可以包括所述第一组播/广播业务的标识，第一组播/广播业务的组播/广播QoS信息，组播/广播QoS信息可以包括组播/广播QoS参数，等。
基于图7所示流程，当UE确定基站变更为第一基站或小区变更为第一基站的小区，和/或，UE确定未接收到第一组播/广播业务的数据，可由UE向第一基站发送第一消息，使得第一基站根据第二消息及时更新第一组播/广播业务的上下文、触发第一基站建立第一组播/广播会话，并根据第二消息触发第二基站更新第一组播/广播业务的上下文。
应理解，在图7所示流程中，S201对应于图6所示的S101，也就是说，S201是S101的一种实现方式。此外，图7中的S202对应于图6中的S102，也就是说，S202是S102的一种实现方式。
示例性的，如图8所示，本申请提供的一种基于上述方式2.2的通信方法可包括以下 步骤：
S301：UE确定基站变更为第一基站或者小区变更为第一基站的小区，和/或UE确定接收到第一组播/广播业务的数据。
S302：UE向第一基站发送第二消息，其中，第二消息可用于指示第一基站更新第一组播/广播业务的上下文。
相应的，第一基站接收第二消息。
S303：第一基站更新第一组播/广播会话的上下文。
其中，第一基站更新第一组播/广播会话的上下文的方式可参见方式2.2中的说明。
第一基站还可向UE发送第二消息的响应消息。
可选的，如果S301中，UE确定基站由第二基站变更为第一基站，则S302中的第二消息中可包括第二基站的标识或UE的标识。
当第一基站获取第二消息中的第二基站的标识，或者，获取第二消息中的UE的标识并根据UE的标识识别UE的服务基站为第二基站，则在图8所示的S302之后，还可执行以下步骤：
S304：第一基站向第二基站发送第四消息、第五消息或第八消息中的至少一个消息。
其中，第四消息可用于通知第二基站更新第一组播/广播会话的上下文。
该第五消息可用于提取该UE的上下文。
第八消息可用于鉴权UE是否已经加入所述第一组播/广播业务，第八消息可以携带UE标识和第一组播/广播业务标识。
第四消息、第五消息和第八消息都可以为Xn消息或X2消息，也即，都可以为用于基站之间进行通信的消息。
可选的，第四消息、第五消息或第八消息中的至少一个消息可包括第一组播/广播会话的标识和/或UE的标识。
相应的，第二基站接收第四消息、第五消息或第八消息中的至少一个消息。
S305：第二基站可响应于第四消息、第五消息或第八消息中的至少一个消息，更新第二基站中的第一组播/广播会话的上下文。
例如，第二基站可根据第四消息、第五消息或第八消息中的至少一个消息中携带的UE的标识和/或第一组播/广播业务的标识，对第一组播/广播会话的上下文进行更新，具体可参见本申请中的说明，这里不再赘述。
如果第二基站更新第一组播/广播业务的上下文后，该上下文中的加入第一组播/广播业务的UE数量为0，或者，加入第一组播/广播业务的UE标识为空，也即，不存在UE的标识，则第二基站可释放该第一组播/广播会话或者释放该第一组播/广播会话的共享组播/广播业务流量传输。
可选地，第二基站确定第一计时器过期(expired)，所述第二基站可释放该第一组播/广播会话或者释放该第一组播/广播会话的共享组播/广播业务流量传输。此外，第一计时器可以是周期性接入网通知区域更新计时器(periodic RNAU Timer)。
S306：第二基站向第一基站发送第四消息、第五消息或第八消息中的至少一个消息的响应消息。
可选的，该响应消息可以是第六消息，第六消息可以是Xn消息或者X2消息或者可以是用于基站之间通信的消息。
例如，该响应消息可以是第六消息。第六消息中可以包括UE的上下文信息，该UE的上下文信息可以包括UE的相关信息。例如，可以包括UE的标识信息，标识信息可以是I-RNTI。例如，这个I-RNTI可以是第二基站新生成的I-RNTI。UE的上下文信息还可以包括终端设备的PDU会话的信息。例如，PDU会话的信息可以包括PDU会话所包含的QoS flow的参数信息。UE的上下文信息还可以包括周期性接入网通知区域计时器(periodic RNAU timer)。
此外，第六消息还可以包括所述第一组播/广播业务的信息，第一组播/广播业务的信息可以包括所述第一组播/广播业务的标识，第一组播/广播业务的组播/广播QoS信息，组播/广播QoS信息可以包括组播/广播QoS参数，等。
如果第二基站更新第一组播/广播业务的上下文后，该上下文中的加入第一组播/广播业务的UE数量为0，或者，加入第一组播/广播业务的UE标识为空，也即，不存在UE的标识，则第二基站可释放该第一组播/广播会话或者释放该第一组播/广播会话的共享组播/广播业务流量传输。
基于图8所示流程，当UE确定基站变更为第一基站或小区变更为第一基站的小区，和/或，UE确定接收到第一组播/广播业务的数据，则可由UE向第一基站发送第二消息，使得第一基站根据第二消息及时更新第一组播/广播业务的上下文，并根据第二消息触发第二基站更新第一组播/广播业务的上下文。
应理解，在图8所示流程中，S301对应于图6所示的S101，也就是说，S301是S101的一种实现方式。此外，图8中的S302对应于图6中的S102，也就是说，S302是S102的一种实现方式。
示例性的，如图9所示，本申请提供的一种基于上述方式2.3的通信方法可通过以下步骤实现：
S401：UE确定/发现移出RNA区域，和/或，UE确定/发现未收到(或没有收到)第一组播/广播业务的数据。其中，UE确定/发现移出RNA区域例如，基站变更为第一基站或者小区变更为第一基站的小区并且变更的第一基站或者变更的第一基站的小区在RNA区域之外，并且UE确定接收到第一组播/广播业务的数据。
或者S401可以替换为，UE确定/发现移出RNA区域，例如，基站变更为第一基站或者小区变更为第一基站的小区并且变更的第一基站或者变更的第一基站的小区在RNA区域之外。
或者S401可以替换为，UE收到了第一组播/广播业务的数据，但是发现移出RNA区域。
或者S401可以替换为，UE确定/发现没有收到第一组播/广播业务的数据，还发现移出RNA区域。
S402：UE向第一基站发送第三消息，其中，第三消息可用于恢复UE的RRC连接。
相应的，第一基站接收第三消息。
S403：第一基站更新第一组播/广播会话的上下文。
其中，第一基站更新第一组播/广播会话的上下文的方式可参见方式2.2中的说明。
可选的，如果S401中，UE确定基站由第二基站变更为第一基站，则S402中的第二消息中可包括第二基站的标识或UE的标识。
当第一基站获取第二消息中的第二基站的标识，或者，获取第二消息中的UE的标识并根据UE的标识识别UE的服务基站为第二基站，则在图8所示的S402之后，还可执行以下步骤：
S404：第一基站向第二基站发送第四消息、第五消息或第八消息中的至少一个消息。
其中，第四消息可用于通知第二基站更新第一组播/广播会话的上下文。
该第五消息可用于提取该UE的上下文。
第八消息可用于鉴权UE是否已经加入所述第一组播/广播业务，第八消息可以携带UE标识和第一组播/广播业务标识。
第四消息、第五消息和第八消息都可以为Xn消息或X2消息，也即，都可以为用于基站之间进行通信的消息。
可选的，第四消息、第五消息或第八消息中的至少一个消息可包括第一组播/广播会话的标识和/或UE的标识。
相应的，第二基站接收第四消息、第五消息或第八消息中的至少一个消息。
S405：第二基站可响应于第四消息、第五消息或第八消息中的至少一个消息，更新第二基站中的第一组播/广播会话的上下文。
例如，第二基站可根据第四消息、第五消息或第八消息中的至少一个消息中携带的UE的标识和/或第一组播/广播业务的标识，对第一组播/广播会话的上下文进行更新，具体可参见本申请中的说明，这里不再赘述。
如果第二基站更新第一组播/广播业务的上下文后，该上下文中的加入第一组播/广播业务的UE数量为0，或者，加入第一组播/广播业务的UE标识为空，也即，不存在UE的标识，则第二基站可释放该第一组播/广播会话或者释放该第一组播/广播会话的共享组播/广播业务流量传输。
可选地，第二基站确定第一计时器过期(expired)，所述第二基站可释放该第一组播/广播会话或者释放该第一组播/广播会话的共享组播/广播业务流量传输。此外，第一计时器可以是周期性接入网通知区域更新计时器(periodic RNAU Timer)。
S406：第二基站向第一基站发送第四消息、第五消息或第八消息中的至少一个消息的响应消息。
该响应消息可以是第六消息，第六消息可以是Xn消息或者X2消息或者可以是用于基站之间通信的消息。
可选的，该响应消息可以是第六消息，第六消息还可以包括UE的上下文信息，该UE的上下文信息可以包括UE的相关信息，例如，可以包括UE的标识信息，标识信息可以是I-RNTI，例如，这个I-RNTI可以是第二基站新生成的I-RNTI；UE的上下文信息还可以包括终端设备的PDU会话的信息，例如，PDU会话的信息可以包括PDU会话所包含的QoS flow的参数信息；UE的上下文信息还可以包括周期性接入网通知区域计时器(periodic RNAU timer)。第六消息还可以包括所述第一组播/广播业务的信息，第一组播/广播业务的信息可以包括所述第一组播/广播业务的标识，第一组播/广播业务的组播/广播QoS信息，组播/广播QoS信息可以包括组播/广播QoS参数，等。
S407：第一基站向UE发送第七消息。
若第七消息携带的第一能力信息指示第一基站支持在无线资源控制去激活态接收，若UE还未收到第一组播/广播业务，基于第一能力信息的指示，UE可以获知第一组播/广播 业务即将发送(is going to be transferred)并且可以不需要发起服务请求消息，服务请求消息可以理解为第九消息的一种。若第七消息未携带第一能力信息，并且UE还未收到第一组播/广播业务，则UE发起服务请求消息，携带关联的PDU会话标识，用于请求激活所述关联的PDU会话，进而触发第一组播/广播会话建立。所述关联的PDU会话与所述第一组播/广播业务关联。应理解，所述关联的PDU会话与第一组播/广播业务关联可以理解为，UE可以通过关联的PDU会话的控制面信令请求加入或退出第一组播/广播业务，加入成功之后，关联的PDU会话还可以用于传输第一组播/广播业务的数据。
基于图9所示流程，当UE移出RNA区域，和/或，UE确定未接收到第一组播/广播业务的数据，则可由UE向第一基站发送第三消息，使得第一基站根据第三消息及时更新第一组播/广播业务的上下文，并根据第二消息触发第二基站更新第一组播/广播业务的上下文。
应理解，在图9所示流程中，S401对应于图6所示的S101，也就是说，S401是S101的一种实现方式。此外，图9中的S402对应于图6中的S102，也就是说，S402是S102的一种实现方式。
基于与图6所示方案的相同的构思，本申请实施例还提供另一种通信方法，用以在UE移出注册区域或者移出RNA区域后，例如，UE的变更的基站或者变更的小区在注册区域或RNA区域之外时，使得基站能够及时建立第一组播/广播会话或更新第一组播/广播会话的上下文，以提高网络资源利用率。
该方法可由终端设备(如UE)、移动管理网元(如AMF)、会话管理网元(如SMF)和接入网设备(如基站)实施。下面以执行主体是UE、AMF、SMF和基站为例进行说明。如图10所示，该通信方法可包括以下步骤：
S501：UE确定移出注册区域或者移出RNA区域，和/或，UE确定未接收到(或没有收到)第一组播/广播业务的数据。
其中，UE确定移出注册区域或者移出RNA区域例如，基站变更为第一基站并且第一基站在注册区域之外，或者基站变更为第一基站并且第一基站在RNA之外，或者，小区变更为第一基站的小区并且该小区在注册区域之外，或者小区变更为第一基站的小区并且该小区在RNA之外，或者UE确定未接收到第一组播/广播业务的数据。
或者，UE确定/发现移出注册区域或RNA区域，例如，基站变更为第一基站或者小区变更为第一基站的小区并且变更的第一基站或者变更的第一基站的小区在注册区域或RNA区域之外。
或者，UE收到了第一组播/广播业务的数据，但是发现移出注册区域或者RNA区域。
或者，UE确定/发现没有收到第一组播/广播业务的数据，还发现移出注册区域或者RNA区域。
S501的实现方式可参见S101，这里不再赘述。
可选的，S501中的UE已加入第一组播/广播业务，且处于去激活态。
S502：UE向第一基站发送第九消息或第十消息。
相应的，第一基站接收第九消息或第十消息。
其中，该第九消息可包括服务请求(sevice request)或上行非接入层数据传输(UL NAS transport)；第十消息包括注册请求(registration request)。
可选的，该第就消息还可以包括：UE用于加入第一组播/广播业务的PDU会话的标识，所述用于UE加入所述组播业务的PDU会话可以叫做关联的PDU会话标识(associated PDU session ID)。
S503：第一基站向AMF发送第九消息或第十消息，携带所述关联的PDU会话标识。
S504：根据关联的PDU会话所对应的控制面连接，AMF向SMF发送PDU会话上下文更新请求(Nsmf_PDUSession_UpdateSMContext request)。
其中，该PDU会话上下文更新请求与关联的PDU会话对应。
相应的，SMF接收PDU会话上下文更新请求。
S505：SMF确定N2会话管理信息(N2 session management info，N2 SM Info)。其中，N2会话管理信息中可携带该第一组播/广播业务的信息，例如，第一组播/广播业务的标识和/或第一组播/广播业务的QoS参数信息等。
其中，这里的基站是UE当前所在的基站，也即，第一基站。
可选的，如果SMF根据PDU会话对应的上下文(例如，SM context)，发现UE已经加入了第一组播/广播业务，则SMF执行S505。
S506：SMF向AMF发送N2 SM Info。该N2 SM Info可包括在PDU会话上下文更新响应消息中。
相应的，AMF接收该N2 SM Info。
S507：AMF向基站发送N2消息，其中携带该N2 SM Info。
相应的，基站接收该N2消息。
S508：第一基站根据第一组播/广播业务的信息确定是否已建立该第一组播/广播会话。
若还未建立该第一组播/广播会话，则执行S509：第一基站触发建立该第一组播/广播会话，并在建立该第一组播/广播会话的过程中获得第一组播/广播会话的上下文，根据该上下文中的QoS信息进行第一组播/广播数据的接收配置。可选的，第一基站还可向UE发送该第一组播/广播业务的数据和/或接收配置。
若已建立该第一组播/广播会话，第一基站可发送第一组播/广播数据的数据和/或接收配置。例如，第一基站可通过非UE的信道发送该接收配置。例如，第一基站可通过MCCH或MCH等发送该接收配置。或者，第一基站可通过RRC消息向UE发送该接收配置。
基于图10所示流程，当UE已加入第一组播/广播业务，且处于RRC-inactive态，如果UE确定移出注册区域或RNA区域，和/或，确定未接收到第一组播/广播业务的数据，则UE可向AMF发送第九消息或第十消息，使得网络侧通知基站建立第一组播/广播业务的会话或者发送用于接收第一组播/广播业务的数据的接收配置，使得UE能够恢复/接收第一组播/广播业务的数据。
本申请实施例还提供另一种通信方法，用以在UE在RNA区域内移动时，使得基站能够及时建立第一组播/广播会话和/或更新第一组播/广播会话的上下文，以提高网络资源利用率。
该方法可由第三接入网设备(如第三基站)和第四接入网设备(如第四基站)实施。下面以执行主体是UE、AMF、SMF和基站为例进行说明。如图11所示，该通信方法可包括以下步骤：
S601：第三基站建立第一组播/广播会话，第一组播/广播会话用于传输第一组播/广播业务的数据。
可选的，第三基站可基于UE的用于请求加入第一组播/广播业务的请求建立第一组播/广播会话。第一组播/广播会话包括5G核心网共享组播/广播业务流量传输(5GC shared MBS traffic delivery)。
例如，第三基站可接收来自于核心网，例如，SMF发送的请求加入第一组播/广播业务的消息，该请求消息中可携带第一组播/广播业务的标识。第三基站可响应于该请求消息建立第一组播/广播会话。
S602：第三基站向至少一个第四基站发送第一指示，所述第一指示用于指示或触发所述第四基站建立所述第一组播/广播业务的组播/广播会话(即第一组播/广播会话)或第一组播/广播会话的享组播/广播业务流量传输。
其中，第四基站与所述第三基站位于或处于同一RNA区域。
相应的，至少一个第四基站可以响应于第一指示，建立第一组播/广播会话。
基于S601和S602，当RNA区域内的第三基站建立第一组播/广播会话，则该第三基站可通过第一指示触发RNA区域内的其他基站(即第四基站)建立该第一组播/广播会话，因此，即便UE从第三基站的覆盖范围移动到其他第四基站的覆盖范围，由于第四基站已建立第一组播/广播会话，因此，UE可从第四基站接收第一组播/广播业务的数据，而不需要第四基站建立第一组播/广播会话，能够降低组播/广播业务的传输时延，可提高业务质量。
可选的，当UE确定从第三基站移动到第四基站后，可按照本申请实施例提供的图6至图10所示方法，通知第三基站和/或第四基站更新第一组播/广播会话。
进一步可选的，图11所示流程还可包括以下步骤：
S603：第三基站确定或发现不存在UE接收第一组播/广播业务/会话。
其中，这里的不存在UE接收第一组播/广播会话可以是因为UE退出了该业务，或者，UE移出了第三基站的覆盖范围等，不作具体要求。示例性的，当第一组播/广播业务的会话上下文中不存在任何终端设备的标识，或该会话上下文中的终端设备的数量为0时，基站确定或发现不存在UE接收第一组播/广播业务/会话。
S604：如果第三基站确定第四基站的不存在UE接收第一组播/广播会话，则第三基站释放第一组播/广播会话。
也就是说，只有在RNA中的全部基站都不存在UE接收第一组播/广播会话，RNA中的基站(包括第三基站和第四基站)才释放第一组播/广播会话或释放第一组播/广播会话的享组播/广播业务流量传输。否则，即便第三基站的不存在UE接收第一组播/广播业务，只要有同一RNA中的任意基站仍存在UE接收第一组播/广播业务，则第三基站都不释放第一组播/广播会话或不释放第一组播/广播会话的享组播/广播业务流量传输。以避免RNA中的其他基站下的UE在移动到第三基站的覆盖范围内之后，需要第三基站重新建立第一组播/广播会话，因此可以提高组播/广播业务的服务质量，避免业务中断。
示例性的，在S603的一种可能的实现方式中，第三基站可接收来自于至少一个第四基站的第二指示，该第二指示用于指示第四接入网设备不存在UE接收第一组播/广播业务，或者，第二指示可用于指示还存在UE接收第一组播/广播业务的数据。因此，第三基站可根据第二指示确定RNA中其它基站是否还存在UE接收第一组播/广播业务，进一步可根 据判断决定是否触发第一组播/广播会话或第一组播/广播会话的享组播/广播业务流量传输的释放。
其中，可由第三基站在第三基站的最后一个UE退出第一组播/广播业务后，向至少一个第四基站发送第三指示，该第三指示可用于指示第三基站的最后一个UE退出第一组播/广播业务，或者，第三指示可用于确认是否第四接入网设备中的全部终端设备退出第一组播/广播业务，或者，第三指示可用于指示已无第三基站的UE接收第一组播/广播业务的数据。
例如，如图12所示，当第三基站不存在UE接收第一组播/广播业务，第三基站可向第四基站发送第三指示。任一第四基站在接收到第三指示后，可判断是否还存在UE接收第一组播/广播业务，如果第四基站不存在UE接收第一组播/广播业务，则向第三基站发送第二指示；否则，如果至少存在一个UE接收第一组播/广播业务，则该第四基站不发送第二指示，该第四基站可发送第四指示以表示还存在UE接收第一组播/广播业务。如果第三基站接收到第四基站发送的第二指示，则可确定在RNA中的全部基站都不存在UE接收第一组播/广播业务。
此外，另一种示例中，如图13所示，第二指示也可以是第三基站发送第三指示之前，第三基站从其他第四基站获取的。其中，第二指示可以是第四基站确定不存在UE接收第一组播/广播业务后发送的。例如，第三基站在发现不存在UE接收第一组播/广播业务之前，接收到来自于至少一个第四基站的第二指示，来自于第四基站的第二指示可表示不存在UE接收第一组播/广播业务，则第三基站可以在接收到第四基站的第二指示后，在第三基站不存在UE接收第一组播/广播业务后，确定在RNA中的全部基站的都不存在UE接收第一组播/广播业务，因此可进行/触发第一组播/广播会话的释放或者释放第一组播/广播会话的享组播/广播业务流量传输。可选的，该示例中，还可由第三基站向其他第四基站发送第五指示，该第五指示可用于触发第四基站释放第四基站的第一组播/广播会话或释放第一组播/广播会话的享组播/广播业务流量传输。
应理解，以上第一指示、第二指示、第三指示、第四指示或第五指示中的任意一个中，可包括所述第一组播/广播业务的标识。
还应理解，以上第一指示、第二指示、第三指示、第四指示或第五指示的功能也可由消息、指示信息或标识等方式实现，本申请不具体限定。
基于以上方法实施例，本申请实施例还提供了一种通信装置，该装置的结构如图14所示，包括收发模块(或通信模块)1401和处理模块1402，其中，收发模块1401可包括接收模块和发送模块中的至少一项，用于实现信息的接收和发送中的至少一项，处理模块1402可用于生成由收发模块1401发送的信息，或用于对收发模块1401接收到的信息进行处理。处理模块1402也可用于执行以上方法实施例部分涉及的接收和发送以外的动作。所述装置1400可以应用于终端设备、第一接入网设备、第二接入网设备、移动管理网元、会话管理网元、接入网设备、第三接入网设备和第四接入网设备中的至少一个中，以实现图6至图13所示通信方法。
在用于实现本申请实施例提供的终端设备时，该通信装置可包括终端设备。其中，在实现终端设备的功能时，处理模块1402可用于确定接入网设备变更为第一接入网设备，或者，确定小区变更为第一接入网设备的小区，所述终端设备已加入所述第一组播/广播业务且处于RRC去激活态。和/或，处理模块1402可用于确定未接收到第一组播/广播业务 的数据，所述终端设备已加入所述第一组播/广播业务且处于无线资源控制去激活态。收发模块1401可用于向所述第一接入网设备发送第一消息、第二消息、第三消息第九消息或第十消息中的至少一个；其中，所述第一消息用于指示所述第一接入网设备发送所述第一组播/广播业务的数据；所述第二消息用于指示所述第一接入网设备更新所述第一组播/广播业务的上下文；所述第三消息用于恢复所述终端设备的RRC连接；第九消息用于激活用户面连接；第十消息用于请求注册。
在一种可能的实现方式中，所述终端设备允许在无线资源控制去激活态接收组播/广播。
在一种可能的实现方式中，收发模块1401还可用于接收第一信息，所述第一信息包括所述第一接入网设备的标识和/或所述第一接入网设备的小区的标识。处理模块1402还可用于根据第一信息确定接入网设备变更为所述第一接入网设备，或者，确定小区变更为所述第一接入网设备的小区。
在一种可能的实现方式中，收发模块1401还可用于接收第二信息，所述第二信息用于指示以下中的至少一项：所述接入网设备的标识占用的所述第一信息的位数；或者，第二信息用于指示所述第一信息中接入网设备的标识的编码方式；或者，第二信息用于指示所述第一信息中小区的标识的编码方式。
在一种可能的实现方式中，收发模块1401还可用于接收(或收到或确定收到)第一组播/广播业务的数据，并向所述第一接入网设备发送所述第二消息和/或所述第三消息，或发送所述第二消息和/或所述第九消息，或发送所述第二消息和/或所述第十消息。
在一种可能的实现方式中，处理模块1402还可用于确定(或发现)没有(或未收到)第一组播/广播业务的传输，收发模块1401还可用于向所述第一接入网设备发送所述第一消息和/或所述第三消息，或发送所述第一消息和/或所述第九消息，或发送所述第一消息和/或所述第十消息。
在一种可能的实现方式中，所述第一消息、所述第二消息或所述第三消息中的至少一个消息中，包括所述终端设备的标识、所述第一组播/广播业务的标识，第一协议数据单元PDU会话标识，或所述消息的发送原因(或称为，发送所述消息的原因)中的至少一项，所述第一PDU会话与所述第一组播/广播业务关联。
在一种可能的实现方式中，收发模块1401还可用于接收第一区域的信息，所述第一区域为第二接入网设备的服务区域。所述处理模块1402还可用于确定移出所述第一区域，收发模块1401还可用于发送所述第三消息。
在一种可能的实现方式中，如果处理模块1402确定接入网设备从第二接入网设备变更为所述第一接入网设备，则第一消息、第二消息或第三消息中的至少一个中包括第二接入网设备的标识和/或地址。
在一种可能的实现方式中，处理模块1402还可用于确定移出接入网通知区域，收发模块1401还可用于发送第九消息。
在一种可能的实现方式中，处理模块1402还可用于确定移出注册区域，收发模块1401还可用于发送第十消息。因此，终端设备可在确定未接收到第一组播/广播业务的数据并确定移出注册区域的情况下，发送第十消息。
在一种可能的实现方式中，收发模块1401还可用于接收来自于第一接入网设备的第七消息，所述第七消息包括所述第一配置或第一能力信息；所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一能力信息用于指示第一接入网设备是否支持无线资 源控制RRC去激活态接收，或者，第一能力信息用于指示第一接入网设备是否支持在RRC去激活态接收所述第一组播/广播业务，或者，第一能力信息用于指示第一接入网设备是否支持UE在RRC去激活态的接收所述第一组播/广播业务的数据。
在用于实现本申请实施例提供的第一接入网设备(如第一基站)时，该通信装置可包括第一接入网设备。在实现第一接入网设备的功能时，收发模块1401可用于接收来自于终端设备的第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个，其中，所述第一消息用于通知/指示发送所述第一组播/广播数据，所述终端设备已加入所述第一组播/广播业务且处于无线资源控制去激活态；所述二消息用于通知/指示所述第一接入网设备更新所述第一组播/广播业务的上下文；所述第三消息用于恢复所述终端设备的RRC连接；所述第九消息用于激活用户面连接；所述第十消息用于请求注册；所述第一消息、所述第二消息或所述第三消息中的至少一个包括第二接入网设备的标识和/或地址。收发模块1401还可用于根据所述第二接入网设备的标识和/或地址，向所述第二接入网设备发送第四消息或第五消息或第八消息，所述第四消息用于更新所述第一组播/广播业务的上下文，所述第五消息用于提取所述终端设备的上下文，所述第八消息用于鉴权所述终端设备是否已经加入所述第一组播/广播业务。
在一种可能的实现方式中，收发模块1401还可用于向接入管理网元发送所述第九消息或所述第十消息，所述第九消息或所述第十消息携带第一协议数据单元PDU会话标识，所述第九消息或所述第十消息携带所述第一协议数据单元PDU会话标识用于激活所述第一PDU会话或用于激活所述第一PDU会话的连接，所述第一PDU会话与所述第一组播/广播业务关联。
在一种可能的实现方式中，所述第一消息、所述第二消息或所述第三消息中的至少一个可包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
在一种可能的实现方式中，所述第四消息或第五消息或第八消息包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
在一种可能的实现方式中，收发模块1401还可用于接收来自于所述第二接入网设备的第六消息，所述第六消息包括以下至少一项信息：第一配置，所述终端设备的上下文信息、所述第一组播/广播业务的信息、第一能力信息；所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一接入网设备发送第七消息，所述第七消息包括所述第一配置或第一能力信息；所述第一能力信息用于指示第一接入网设备是否支持UE在RRC去激活态的接收所述第一组播/广播业务的数据。
在用于实现本申请实施例提供的第二接入网设备(如第二基站)时，该通信装置可包括第一接入网设备。在实现第一接入网设备的功能时，收发模块1401可用于第二接入网设备接收来自于第一接入网设备的第四消息或第五消息或第八消息中的至少一个，其中，所述第四消息用于更新所述第一组播/广播业务的上下文，所述第五消息用于提取所述终端设备的上下文，所述第八消息用于鉴权所述终端设备是否已经加入所述第一组播/广播业务，所述终端设备已加入所述第一组播/广播业务且处于无线资源控制去激活态。处理模块1402可用于更新所述第一组播/广播业务的上下文。
在一种可能的实现方式中，所述第四消息或第五消息或第八消息包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
在一种可能的实现方式中，处理模块1402还可用于根据所述终端设备的数量更新所 述第一组播/广播业务上下文中的终端设备数量。
在一种可能的实现方式中，所述第四消息或所述第五消息或第八消息中的至少一个包括所述终端设备的标识，所述第二接入网设备还可删除(或移除)所述第一组播/广播业务的上下文中的所述终端设备的标识。
在一种可能的实现方式中，所述收发模块1401还可用于向所述第一接入网设备发送第六消息，所述第六消息包括第一配置，所述第一配置包括用于接收所述第一组播/广播业务的配置。
在一种可能的实现方式中，所述收发模块1401还可用于向所述终端设备发送第一区域的信息，所述第一区域包括以下至少一项：所述第二接入网设备的标识、所述第二接入网设备包括的小区、第二接入网设备的追踪区码、第二接入网设备的接入网区域码、第二接入网设备的服务区域。
在一种可能的实现方式中，处理模块1402还可用于确定第一计时器过期，所述第二接入网设备释放第一传输资源，所述第一传输资源用于传输所述第一组播/广播业务。可选的，第一传输资源包括第一组播/广播会话。
基于以上实施例，本申请实施例还提供了一种通信装置，所述设备用于实现以上各图中的通信方法。参阅图15所示，所述通信装置1500可包括：收发器1501、处理器1502以及存储器1503中的至少一项。其中，所述收发器1501、所述处理器1502以及所述存储器1503之间相互连接。
可选的，所述收发器1501、所述处理器1502以及所述存储器1503之间通过总线1504相互连接。所述总线1504可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述收发器1501，用于接收和发送数据，实现与其他设备之间的通信。例如，收发器1501可用于执行以上收发模块1401的功能。
可选的，收发器可以包括通信接口。通信接口可用于通信装置1500的通信。例如，通信接口可用于通过有线的方式实现以上收发模块1401所示功能。
所述处理器1502，用于实现如以上各图中的通信方法，具体可以参照以上实施例中的描述。例如，处理器1502可用于执行以上处理模块1402的功能。
所述存储器1503，用于存放程序指令等。具体地，程序指令可以包括程序代码，该程序代码包括计算机操作指令。存储器1503可能包含随机存取存储器(random access memory，RAM)，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。处理器1502执行存储器1503所存放的程序指令，实现上述功能，从而实现上述实施例提供的通信方法。
应理解，以上所示的收发模块1401和收发器1501中的至少一个可用于执行终端设备、第一接入网设备、第二接入网设备等通信设备或装置所执行的发送信息、通知或消息的动作，和/或，执行终端设备、第一接入网设备、第二接入网设备等通信设备或装置所执行的接收信息、通知或消息的动作。
处理模块1402和处理器1502中的至少一个可用于执行第一设备或第二设备的处理动作，例如，包括终端设备确定接入网设备变更或小区变更、生成由收发模块1401和收发 器1501中的至少一个发送的信息、通知或消息，或对收发模块1401和收发器1501中的至少一个接收的信息、通知或消息进行处理，等等。
还应理解，由以上收发模块1401、收发器1501、处理模块1402和处理器1502中的至少一个执行的个步骤中，相关技术术语、名词以及动作实现方式等可参见本申请方法实施例在图6至图13中对于相应技术术语、名词以及动作实现方式的说明。
基于以上实施例，本申请实施例还提供了一种通信方法，如图6所示该方法由终端设备和第一接入网设备实施。可选的，如图7至图9所示，该方法还可由终端设备、第一接入网设备和第二接入网设备实施。或者，如图10所示，该通信方法还可由终端设备、移动管理网元、会话管理网元和接入网设备实施。或者，如图11至图13所示，该通信方法还可由第三接入网设备和第四接入网设备实施。该方法可参见本申请对于图6至图13所示方法的说明。
基于以上实施例，本申请实施例还提供了一种系统，该系统可包括以上终端设备和第一接入网设备，或者，可包括终端设备、第一接入网设备和第二接入网设备实施，或者，可包括终端设备、移动管理网元、会话管理网元和接入网设备，或者，可包括第三接入网设备和第四接入网设备。
基于以上实施例，本申请实施例还提供了一种计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行以上实施例提供的通信方法。
基于以上实施例，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，所述计算机程序被计算机执行时，使得计算机执行以上实施例提供的通信方法。
基于以上实施例，本申请实施例还提供了一种芯片，所述芯片用于读取存储器中存储的计算机程序，实现以上实施例提供的通信方法。芯片可包括处理器。
基于以上实施例，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持计算机装置实现以上实施例中终端设备、第一接入网设备、第二接入网设备、移动管理网元、会话管理网元、接入网设备、第三接入网设备和第四接入网设备中至少一个所涉及的功能。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器用于保存该计算机装置必要的程序和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
本申请中，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。“包括A，B或C中的至少一个”可以表示：包括A；包括B；包括C；包括A和B；包括A和C；包括B和C；包括A、B和C。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (30)

  1. 一种通信方法，其特征在于，包括：
    终端设备确定接入网设备变更为第一接入网设备，或者，确定小区变更为第一接入网设备的小区，所述终端设备已加入所述第一组播/广播业务且处于无线资源控制RRC去激活态；
    所述终端设备向所述第一接入网设备发送第一消息、第二消息、第三消息、第九消息、或第十消息中的至少一个；
    其中，所述第一消息用于指示所述第一接入网设备发送所述第一组播/广播业务的数据；
    所述第二消息用于指示所述第一接入网设备更新所述第一组播/广播业务的上下文；
    所述第三消息用于恢复所述终端设备的RRC连接；
    所述第九消息用于激活用户面连接；
    所述第十消息用于请求注册。
  2. 一种通信方法，其特征在于，包括：
    终端设备确定未接收到第一组播/广播业务的数据，所述终端设备已加入所述第一组播/广播业务且处于RRC去激活态；
    所述终端设备向第一接入网设备发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个；
    其中，所述第一消息用于指示所述第一接入网设备发送所述第一组播/广播业务的数据；
    所述第二消息用于指示所述第一接入网设备更新所述第一组播/广播业务的上下文；
    所述第三消息用于恢复所述终端设备的RRC连接；
    所述第九消息用于激活用户面连接；
    所述第十消息用于请求注册。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    所述终端设备确定接入网设备变更为第一接入网设备，或者，确定小区变更为第一接入网设备的小区。
  4. 如权利要求1-3中任一项所述的方法，其特征在于，所述终端设备允许在RRC去激活态接收组播/广播。
  5. 如权利要求1-4中任一项所述的方法，其特征在于，所述终端设备确定接入网设备变更为第一接入网设备，或者，确定小区变更为所述第一接入网设备的小区，包括：
    所述终端设备接收第一信息，所述第一信息包括所述第一接入网设备的标识和/或所述第一接入网设备的小区的标识；
    所述终端设备根据第一信息确定接入网设备变更为所述第一接入网设备，或者，确定小区变更为所述第一接入网设备的小区。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收第二信息，所述第二信息用于指示以下中的至少一项：
    所述接入网设备的标识占用的所述第一信息的位数；
    所述第一信息中所述接入网设备的标识的编码方式；
    所述第一信息中所述小区的标识的编码方式。
  7. 如权利要求1-6中任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收第一组播/广播业务的数据；
    所述终端设备向所述第一接入网设备发送第一消息、第二消息、第三消息、第九消息、或第十消息中的至少一个，包括：
    所述终端设备向所述第一接入网设备发送所述第二消息和/或所述第三消息；
    或者，
    所述终端设备向所述第一接入网设备发送所述第二消息和/或所述第九消息；
    或者，
    所述第一接入网设备发送所述第二消息和/或所述第十消息。
  8. 如权利要求1-7中任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备确定未收到第一组播/广播业务的传输；
    所述终端设备向所述第一接入网设备发送第一消息、第二消息、第三消息、第九消息、或第十消息中的至少一个，包括：
    所述终端设备向所述第一接入网设备发送所述第一消息和/或所述第三消息；
    或者，
    所述终端设备向所述第一接入网设备发送所述第一消息和/或所述第九消息；
    或者，
    所述第一接入网设备发送所述第一消息和/或所述第十消息。
  9. 如权利要求1-8中任一所述的方法，其特征在于，所述第一消息、所述第二消息、所述第三消息、所述第九消息、或所述第十消息中的至少一个消息中，包括所述终端设备的标识、所述第一组播/广播业务的标识，第一协议数据单元PDU会话标识，或所述消息的发送原因中的至少一项，所述第一PDU会话与所述第一组播/广播业务关联。
  10. 如权利要求1-9中任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收第一区域的信息，所述第一区域为第二接入网设备的服务区域；
    终端设备确定接入网设备变更为第一接入网设备，包括：
    所述终端设备确定移出所述第一区域；
    所述终端设备向所述第一接入网设备发送第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个，包括：
    所述终端设备发送所述第三消息。
  11. 如权利要求1-10中任一所述的方法，其特征在于，所述终端设备确定接入网设备变更为第一接入网设备，包括：
    所述终端设备确定接入网设备从第二接入网设备变更为所述第一接入网设备，所述第一消息、所述第二消息、所述第三消息、所述第九消息或所述第十消息中的至少一个中包括所述第二接入网设备的标识和/或地址。
  12. 如权利要求2、4-10中任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备确定移出接入网通知区域RNA；
    所述终端设备向所述第一接入网设备发送第一消息、第二消息、第三消息、第九消息、或第十消息中的至少一个，包括：
    所述终端设备发送所述第九消息。
  13. 如权利要求2、4-10中任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备移出注册区域RA；
    所述终端设备向所述第一接入网设备发送第一消息、第二消息、第三消息、第九消息、或第十消息中的至少一个，包括：
    所述终端设备发送所述第十消息。
  14. 如权利要求1-13中任一所述的方法，其特征在于，包括：
    所述终端设备接收来自于第一接入网设备的第七消息，所述第七消息包括第一配置或第一能力信息；所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一能力信息用于指示第一接入网设备是否支持终端设备在RRC去激活态接收组播/广播业务。
  15. 如权利要求14所述方法，其特征在于，所述终端设备发送第九消息，包括：
    所述终端设备根据所述第一能力信息，发送第九消息。
  16. 一种通信方法，其特征在于，包括：
    第一接入网设备接收来自于终端设备的第一消息、第二消息、第三消息、第九消息或第十消息中的至少一个，其中，所述第一消息用于指示所述第一接入网设备发送所述第一组播/广播数据，所述终端设备已加入所述第一组播/广播业务且处于RRC去激活态；所述二消息用于指示所述第一接入网设备更新所述第一组播/广播业务的上下文；所述第三消息用于恢复所述终端设备的RRC连接；所述第九消息用于激活用户面连接；所述第十消息用于请求注册；
    所述第一消息、所述第二消息或所述第三消息中的至少一个包括第二接入网设备的标识和/或地址；
    所述第一接入网设备根据所述第二接入网设备的标识和/或地址，向所述第二接入网设备发送第四消息或第五消息或第八消息，所述第四消息用于更新所述第一组播/广播业务的上下文，所述第五消息用于提取所述终端设备的上下文，所述第八消息用于鉴权所述终端设备是否已经加入所述第一组播/广播业务。
  17. 根据权利要求16所述的方法，其特征在于，包括：
    所述第一接入网设备向接入管理网元发送所述第九消息或所述第十消息，所述第九消 息或所述第十消息携带第一协议数据单元PDU会话标识，所述第九消息或所述第十消息携带所述第一协议数据单元PDU会话标识用于激活所述第一PDU会话或用于激活所述第一PDU会话的连接，所述第一PDU会话与所述第一组播/广播业务关联。
  18. 如权利要求16所述的方法，其特征在于，
    所述第一消息、所述第二消息或所述第三消息中的至少一个包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
  19. 如权利要求16所述的方法，其特征在于，所述第四消息或第五消息或第八消息包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
  20. 如权利要求16、18-19中任一所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备接收来自于所述第二接入网设备的第六消息，所述第六消息包括以下至少一项信息：
    第一配置、所述终端设备的上下文信息、所述第一组播/广播业务的信息、第一能力信息；
    其中，所述第一配置包括用于接收所述第一组播/广播业务的配置；所述第一接入网设备发送第七消息，所述第七消息包括所述第一配置或第一能力信息；所述第一能力信息用于指示第一接入网设备是否支持终端设备在RRC去激活态接收组播/广播业务。
  21. 一种通信方法，其特征在于，包括：
    第二接入网设备接收来自于第一接入网设备的第四消息或第五消息或第八消息中的至少一个，其中，所述第四消息用于更新所述第一组播/广播业务的上下文，所述第五消息用于提取所述终端设备的上下文，所述第八消息用于鉴权所述终端设备是否已经加入所述第一组播/广播业务，所述终端设备已加入所述第一组播/广播业务且处于RRC去激活态；
    所述第一接入网设备更新所述第一组播/广播业务的上下文。
  22. 如权利要求21所述的方法，其特征在于，所述第四消息或第五消息或第八消息包括所述终端设备的标识和/或所述第一组播/广播业务的标识。
  23. 如权利要求21或22所述的方法，其特征在于，所述第二接入网设备更新所述第一组播/广播业务的上下文，包括：
    所述第二接入网根据所述终端设备的数量更新所述第一组播/广播业务上下文中的终端设备数量。
  24. 如权利要求21-23中任一所述的方法，其特征在于，所述第四消息或所述第五消息或第八消息中的至少一个包括所述终端设备的标识，所述第一接入网设备更新所述第一组播/广播业务的上下文，包括：
    所述第二接入网设备删除所述第一组播/广播业务的上下文中的所述终端设备的标识。
  25. 如权利要求21-24中任一所述的方法，其特征在于，所述方法还包括：
    所述第二接入网设备向所述第一接入网设备发送第六消息，所述第六消息包括第一配置，所述第一配置包括用于接收所述第一组播/广播业务的配置。
  26. 如权利要求21-25中任一所述的方法，其特征在于，所述方法还包括：
    所述第二接入网设备向所述终端设备发送第一区域的信息，所述第一区域包括以下至少一项：
    所述第二接入网设备的标识、所述第二接入网设备包括的小区、第二接入网设备的追踪区码、第二接入网设备的接入网区域码、第二接入网设备的服务区域。
  27. 如权利要求21-26中任一所述的方法，其特征在于，所述方法还包括：
    第二接入网设备确定第一计时器过期，所述第二接入网设备释放第一传输资源，所述第一传输资源用于传输所述第一组播/广播业务。
  28. 一种通信装置，其特征在于，包括处理器以及收发器；
    所述收发器用于支持所述通信装置进行通信；
    所述处理器用于执行指令，实现如权利要求1-15中任一所述的方法。
  29. 一种通信装置，其特征在于，包括处理器以及收发器；
    所述收发器用于支持所述通信装置进行通信；
    所述处理器用于执行指令，实现如权利要求16-20中任一所述的方法。
  30. 一种通信装置，其特征在于，包括处理器以及收发器；
    所述收发器用于支持所述通信装置进行通信；
    所述处理器用于执行指令，实现如权利要求21-27中任一所述的方法。
PCT/CN2023/077490 2022-03-29 2023-02-21 一种通信方法及装置 WO2023185328A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210326256.6 2022-03-29
CN202210326256.6A CN116939505A (zh) 2022-03-29 2022-03-29 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2023185328A1 true WO2023185328A1 (zh) 2023-10-05

Family

ID=88199159

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/077490 WO2023185328A1 (zh) 2022-03-29 2023-02-21 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN116939505A (zh)
WO (1) WO2023185328A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110149728A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 无线资源控制rrc状态转换的方法与装置
US20200045767A1 (en) * 2018-08-03 2020-02-06 Lenovo (Singapore) Pte. Ltd. Indicating radio capability changes in an inactive state
CN111182539A (zh) * 2017-03-24 2020-05-19 华为技术有限公司 通信方法与设备
WO2021190278A1 (zh) * 2020-03-25 2021-09-30 展讯通信（上海）有限公司 业务的请求方法及装置
CN114145073A (zh) * 2019-09-29 2022-03-04 华为技术有限公司 通信方法和通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111182539A (zh) * 2017-03-24 2020-05-19 华为技术有限公司 通信方法与设备
CN110149728A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 无线资源控制rrc状态转换的方法与装置
US20200045767A1 (en) * 2018-08-03 2020-02-06 Lenovo (Singapore) Pte. Ltd. Indicating radio capability changes in an inactive state
CN114145073A (zh) * 2019-09-29 2022-03-04 华为技术有限公司 通信方法和通信装置
WO2021190278A1 (zh) * 2020-03-25 2021-09-30 展讯通信（上海）有限公司 业务的请求方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Single-registration mode without N26 for EPS NAS message container IE", 3GPP TSG CT WG1 MEETING #125E, C1-205432, no. Electronic meeting; 20200820 - 20200828, 27 August 2020 (2020-08-27), XP051922419 *

Also Published As

Publication number Publication date
CN116939505A (zh) 2023-10-24

Similar Documents

Publication Publication Date Title
US11425537B2 (en) Communications system, communication method, and apparatus thereof
US20220174119A1 (en) Session establishment method and device
TWI681687B (zh) 處理尋呼的方法和裝置
US20220248184A1 (en) Communication Method And Apparatus
WO2020063362A1 (zh) 多播/广播业务传输的方法、核心网网元和终端设备
CN114503776A (zh) 使用共享下行链路数据支持群组通信
WO2021164564A1 (zh) 传输组播业务的方法和装置
CN104284299A (zh) 集群多播决策方法、集群终端及集群服务器
US20230164640A1 (en) Communication method and communication apparatus
US20230018974A1 (en) Multicast communication method and communication apparatus
WO2021097858A1 (zh) 一种通信方法及装置
CN104283602A (zh) 集群中继方法、装置及系统
KR20230004776A (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
US20220408317A1 (en) Handover method and communication apparatus
WO2015117375A1 (zh) Lte集群通信的方法、用户设备及第一网元设备
US20230388756A1 (en) Communication method and apparatus for multicast/broadcast service
KR102362973B1 (ko) 그룹 통신 서비스 데이터를 송신하기 위한 방법, 시스템 및 장치
WO2022242409A1 (zh) 一种传输业务数据的方法和通信装置
WO2023185328A1 (zh) 一种通信方法及装置
JP7399263B2 (ja) Ｉｏｐｓでのｍｂｍｓサポート
CN116391408A (zh) 动态切换多播和广播服务（mbs）数据包传送模式的方法和装置
US20240080931A1 (en) Communication method and apparatus
WO2022179434A1 (zh) 组播/广播业务的通信方法、装置及系统
WO2022165919A1 (zh) 一种通信方法及装置
US20240057194A1 (en) Pdu session status ie handling for mbs

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

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)