WO2024120299A1 - 一种通信方法和通信装置 - Google Patents

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

Info

Publication number
WO2024120299A1
WO2024120299A1 PCT/CN2023/135528 CN2023135528W WO2024120299A1 WO 2024120299 A1 WO2024120299 A1 WO 2024120299A1 CN 2023135528 W CN2023135528 W CN 2023135528W WO 2024120299 A1 WO2024120299 A1 WO 2024120299A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
plmn
broadcast
network element
broadcast service
Prior art date
Application number
PCT/CN2023/135528
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 WO2024120299A1 publication Critical patent/WO2024120299A1/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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • 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 a communication device.
  • the current standard protocol is discussing how different operators’ access network equipment can share access network equipment, mainly focusing on the network optimization solution for multi-operator core network (MOCN) sharing access network equipment.
  • This network optimization solution allows access network equipment to recognize that different operators are targeting the same service when requesting to establish a broadcast session, thereby further reusing air interface resources (i.e., sessions of different operators with the same service use the same air interface resources), thereby improving air interface transmission efficiency.
  • MOCN multi-operator core network
  • the MOCN scenario includes at least two public land mobile networks (PLMNs) and access network equipment, and the access network equipment can access two different PLMNs, for example, PLMN a and PLMN b.
  • PLMN a uses MB-UPF a as the anchor point of multicast session x
  • PLMN b uses MB-UPF b as the anchor point of multicast session y
  • both multicast sessions x and y are used to transmit the multicast service.
  • MB-UPF a and MB-UPF b may generate different sequence numbers for the same multicast service data, resulting in the same access network equipment accessing PLMN a and PLMN b receiving the same multicast service data from PLMN a and PLMN b.
  • the sequence numbers corresponding to the same multicast service data are different, which leads to confusion in the access network equipment's recognition of the sequence number of the same multicast service data, thereby affecting the continuity of the multicast service. Therefore, how to ensure the continuity of multicast services in the MOCN scenario has become an urgent problem to be solved.
  • the present application provides a communication method and a communication device, which can synchronize the sequence numbers of data of the same multicast/broadcast service in different PLMNs in an MOCN scenario, realize synchronization of data transmission, and thus ensure service continuity.
  • the present application provides a first communication method, which is executed by a multicast/broadcast session management network element, or by a component of the multicast/broadcast session management network element (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the multicast/broadcast session management network element functions. For example, it is executed by a first multicast/broadcast session management network element in a multi-operator network.
  • the first multicast/broadcast session management network element receives a first session establishment request message from an application server, and the first session establishment request message includes identification information of a first multicast/broadcast service; the first multicast/broadcast session management network element sends a first indication information to a first multicast/broadcast user plane function network element according to the first session establishment request message, and the first indication information is used to instruct the first multicast/broadcast user plane function network element to increment a first sequence number corresponding to the data when receiving the data of the first multicast/broadcast service; the first multicast/broadcast session management network element and the first multicast/broadcast user plane function network element are located in a first public land mobile network PLMN of a multi-operator core network MOCN.
  • the first multicast/broadcast session management network element in the MOCN can instruct the corresponding first multicast/broadcast user plane function network element to perform special configuration, for example, instructing the first multicast/broadcast user plane function network element to increment the first sequence number corresponding to the data when receiving the data of the first multicast/broadcast service (for example, adding 1 to the first sequence number).
  • the first multicast/broadcast user plane function network element synchronously updates the sequence number of the data of the same multicast/broadcast service according to the instruction of the first multicast/broadcast session management network element, which is conducive to synchronizing the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the first session establishment request message further includes an identifier of the first PLMN; and the first sequence number is used by the access network device in the MOCN to identify data of the first multicast/broadcast service from the first PLMN.
  • the first sequence number can be recognized by different access network devices in the MOCN (belonging to the same PLMN or different PLMNs); and for the data of the first multicast/broadcast service, the first sequence number of the data recognized by different access network devices is the same, which is conducive to achieving data synchronization.
  • the first session establishment request message further includes the type of the multicast/broadcast service.
  • the type of the first multicast/broadcast service is a multicast service
  • the first multicast/broadcast session management network element sends first indication information to the first multicast/broadcast user plane function network element.
  • the type of the multicast/broadcast service is a multicast service
  • the sequence number cannot be aligned (the broadcast service does not identify the specific access network device and the terminal device, so there is no problem of sequence number alignment).
  • the first multicast/broadcast session management network element sends a first indication to the first multicast/broadcast user plane function network element
  • the information enables the first multicast/broadcast user plane function network element to synchronously update the sequence number of the data of the same multicast/broadcast service according to the instruction of the first multicast/broadcast session management network element, which is conducive to synchronizing the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the first session establishment request message further includes network sharing identification information; the network sharing identification information is used to indicate that the first multicast/broadcast service is shared in a temporary multicast group identification TMGI list of a second PLMN of the MOCN, and the second PLMN is different from the first PLMN.
  • the first multicast/broadcast session management network element sends the first indication information to the first multicast/broadcast user plane function network element according to the network sharing identification information.
  • the first multicast/broadcast service when the first multicast/broadcast service is shared in the TMGI list of other PLMNs in the MOCN, it means that the first multicast/broadcast service can be sent to different access network devices in the MOCN (belonging to the same PLMN or different PLMNs).
  • the first multicast/broadcast session management network element sends the first indication information to the first multicast/broadcast user plane function network element, so that the first multicast/broadcast user plane function network element synchronously updates the sequence number of the data of the same multicast/broadcast service according to the indication of the first multicast/broadcast session management network element, which is conducive to realizing the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the present application provides a second communication method, which is executed by a multicast/broadcast session management network element, or by a component of the multicast/broadcast session management network element (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the multicast/broadcast session management network element functions. For example, it is executed by a second multicast/broadcast session management network element in a multi-operator network.
  • the second multicast/broadcast session management network element receives a second session establishment request message from an application server, and the second session establishment request message includes identification information of a first multicast/broadcast service; the second multicast/broadcast session management network element sends a second indication information to a second multicast/broadcast user plane function network element according to the second session establishment request message, and the second indication information is used to instruct the second multicast/broadcast user plane function network element to increment the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service; the second multicast/broadcast session management network element and the second multicast/broadcast user plane function network element are located in a second public land mobile network PLMN of a multi-operator core network MOCN.
  • the second multicast/broadcast session management network element in the MOCN can instruct the corresponding second multicast/broadcast user plane function network element to perform special configuration, for example, instructing the second multicast/broadcast user plane function network element to increment the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service (for example, adding 1 to the second sequence number).
  • the second multicast/broadcast user plane function network element synchronously updates the sequence number of the data of the same multicast/broadcast service according to the instruction of the second multicast/broadcast session management network element, thereby realizing synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the second session establishment request message further includes an identifier of the second PLMN; and the second sequence number is used by the access network device in the MOCN to identify data of the first multicast/broadcast service from the second PLMN.
  • the second serial number can be recognized by different access network devices in the MOCN (belonging to the same PLMN or different PLMNs); and for the data of the first multicast/broadcast service, the second serial number of the data recognized by different access network devices is the same, which is conducive to achieving data synchronization.
  • the first indication information includes a starting value of a first sequence number
  • the second indication information includes a starting value of a second sequence number
  • the starting value of the first sequence number is the same as the starting value of the second sequence number corresponding to the data of the first multicast/broadcast service in the second PLMN of the MOCN.
  • the second session establishment request message further includes the type of the multicast/broadcast service.
  • the type of the first multicast/broadcast service is a multicast service
  • the second multicast/broadcast session management network element sends first indication information to the second multicast/broadcast user plane function network element.
  • the second session establishment request message further includes network sharing identification information; the network sharing identification information is used to indicate that the first multicast/broadcast service is shared in the temporary multicast group identification TMGI list of the second PLMN of the MOCN, and the second PLMN is different from the first PLMN.
  • the second multicast/broadcast session management network element sends the second indication information to the second multicast/broadcast user plane function network element according to the network sharing identification information.
  • the present application provides a third communication method, which is executed by a multicast/broadcast user plane functional network element, and can also be executed by a component of the multicast/broadcast user plane functional network element (such as a processor, a chip, or a chip system, etc.), and can also be implemented by a logic module or software that can implement all or part of the functions of the multicast/broadcast user plane functional network element. For example, it is executed by the first multicast/broadcast user plane functional network element in a multi-operator network.
  • a component of the multicast/broadcast user plane functional network element such as a processor, a chip, or a chip system, etc.
  • a logic module or software that can implement all or part of the functions of the multicast/broadcast user plane functional network element. For example, it is executed by the first multicast/broadcast user plane functional network element in a multi-operator network.
  • the first multicast/broadcast user plane functional network element receives a first indication information from a multicast/broadcast session management network element, and the first indication information is used to indicate that the first multicast/broadcast user plane functional network element increments the first sequence number corresponding to the data when receiving the data of the first multicast/broadcast service; the first multicast/broadcast user plane functional network element receives the data of the first multicast/broadcast service from the application server, and according to the first indication information, increments the first sequence number corresponding to the data.
  • the first multicast/broadcast user plane function network element in the MOCN can perform special configuration on the processing of the user plane according to the instruction, for example, when receiving the data of the first multicast/broadcast service, the first sequence number corresponding to the data is incremented, regardless of whether it will be sent to the access network device.
  • the first multicast/broadcast user plane function network element can synchronously update the sequence number of the data of the same multicast/broadcast service, and realize synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the first multicast/broadcast user plane functional network element sends the data of the first multicast/broadcast service and the first serial number corresponding to the data to an access network device in a multi-operator core network MOCN, and the first multicast/broadcast user plane functional network element is located in the first PLMN of the MOCN, and the first serial number is used by the access network device to identify the data of the first multicast/broadcast service from the first PLMN.
  • the first multicast/broadcast user plane network element can send a first serial number to different access network devices in the MOCN (belonging to the same PLMN or different PLMNs), and for the data of the first multicast/broadcast service, the first serial number of the data identified by different access network devices is the same, which is conducive to achieving data synchronization.
  • the present application provides a fourth communication method, which is executed by a multicast/broadcast user plane functional network element, and can also be executed by a component of the multicast/broadcast user plane functional network element (such as a processor, a chip, or a chip system, etc.), and can also be implemented by a logic module or software that can implement all or part of the functions of the multicast/broadcast user plane functional network element. For example, it is executed by a second multicast/broadcast user plane functional network element in a multi-operator network.
  • a component of the multicast/broadcast user plane functional network element such as a processor, a chip, or a chip system, etc.
  • a logic module or software that can implement all or part of the functions of the multicast/broadcast user plane functional network element. For example, it is executed by a second multicast/broadcast user plane functional network element in a multi-operator network.
  • the second multicast/broadcast user plane functional network element receives second indication information from a second multicast/broadcast session management network element, and the second indication information is used to indicate that the second multicast/broadcast user plane functional network element increments the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service; the second multicast/broadcast user plane functional network element receives the data of the first multicast/broadcast service from the application server, and according to the second indication information, increments the second sequence number corresponding to the data.
  • the second multicast/broadcast user plane function network element in the MOCN can perform special configuration on the processing of the user plane according to the instruction, for example, when receiving the data of the first multicast/broadcast service, the second sequence number corresponding to the data is incremented, regardless of whether the data will be sent to the access network device.
  • the second multicast/broadcast user plane function network element can synchronously update the sequence number of the data of the same multicast/broadcast service, and realize the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • a second multicast/broadcast user plane functional network element sends data of a first multicast/broadcast service and a second serial number corresponding to the data to an access network device in the MOCN, and the second multicast/broadcast user plane functional network element is located in a second PLMN of the MOCN.
  • the second serial number is used by the access network device to identify data of the first multicast/broadcast service from the second PLMN.
  • the second multicast/broadcast user plane network element can send a second sequence number to different access network devices in the MOCN (belonging to the same PLMN or different PLMNs), and for the data of the first multicast/broadcast service, the second sequence number of the data identified by different access network devices is the same and aligned with the first sequence number, thereby facilitating data synchronization.
  • the present application provides a fifth communication method, which is executed by an application server, or by a component of the application server (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the application server functions.
  • a component of the application server such as a processor, a chip, or a chip system, etc.
  • a logic module or software that can implement all or part of the application server functions.
  • the application server sends a first session establishment request message to a first multicast/broadcast session management network element in a first PLMN of the MOCN, and the first session establishment request message includes identification information of the first multicast/broadcast service; the application server sends a second session establishment request message to a second multicast/broadcast session management network element in a second PLMN of the MOCN, and the second session establishment request message includes identification information of the first multicast/broadcast service; the first PLMN is different from the second PLMN.
  • the application server can send identification information of the first multicast/broadcast service to the multicast/broadcast session management network elements in different PLMNs of the MOCN, and the multicast/broadcast session management network elements in different PLMNs then send indication information to the corresponding multicast/broadcast user plane functional network elements, which is conducive to the multicast/broadcast user plane functional network elements in different PLMNs simultaneously receiving the data of the first multicast/broadcast service from the application server, and synchronously updating the sequence number of the data for the first multicast/broadcast service, thereby facilitating data synchronization.
  • the first session request message further includes an identifier of the first PLMN and/or a starting value of a first sequence number corresponding to the data of the first multicast/broadcast service in the first PLMN;
  • the second session request message further includes an identifier of the second PLMN and/or a starting value of a second sequence number corresponding to the data of the first multicast/broadcast service in the second PLMN; wherein the starting value of the first sequence number is the same as the starting value of the second sequence number.
  • the application server can also directly indicate the starting value of the first sequence number and the starting value of the second sequence number, and the starting value of the first sequence number and the starting value of the second sequence number are the same. Since the updating strategies of the first sequence number and the second sequence number are consistent (for example, the sequence number is increased by 1 as long as data is received), the sequence numbers of data for the same multicast/broadcast service of different PLMNs can be synchronized.
  • the present application provides a sixth communication method, which is executed by an application server, or by a component of the application server (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the application server functions.
  • the application server generates a session establishment request message, which includes an identifier of a primary public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service; the application server sends the session establishment request message to a multicast/broadcast session management network element.
  • the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used by the multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between an access network device in the MOCN and a multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the multicast/broadcast session management network element is located in the primary PLMN, or the multicast/broadcast session management network element is located in a PLMN other than the primary PLMN in the MOCN.
  • the application server can designate a PLMN in the MOCN as the primary PLMN (referred to as the main PLMN for short), so that the access network devices in the MOCN establish a shared transmission channel with the multicast/broadcast user plane functional network element of the main PLMN, so that the multicast/broadcast user plane functional network element of the main PLMN uses the same serial number for the data of the same multicast/broadcast service, thereby realizing the synchronization of the serial numbers of the data of the same multicast/broadcast service in different PLMNs, which is conducive to data synchronization.
  • the present application provides a seventh communication method, which is executed by a multicast/broadcast session management network element, or may be executed by a component of the multicast/broadcast session management network element (e.g., a processor, a chip, or a chip system, etc.), or may be implemented by a logic module or software that can implement all or part of the functions of the multicast/broadcast session management network element. For example, it is executed by a first multicast/broadcast session management network element in a multi-operator network.
  • a component of the multicast/broadcast session management network element e.g., a processor, a chip, or a chip system, etc.
  • a logic module or software that can implement all or part of the functions of the multicast/broadcast session management network element. For example, it is executed by a first multicast/broadcast session management network element in a multi-operator network.
  • the first multicast/broadcast session management network element receives a session establishment request message from an application server, the session establishment request message including an identifier of a primary public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service; the first multicast/broadcast session management network element sends a multicast/broadcast service session context to the first session management network element, the multicast/broadcast service session context including an identifier of a primary PLMN and identification information of a first multicast/broadcast service.
  • the identification information of the primary PLMN and the first multicast/broadcast service is used by the first multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network equipment in the MOCN and the multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first multicast/broadcast session management network element and the first session management network element are located in a primary PLMN.
  • the first multicast/broadcast session management network element can send the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service to the first session management network element, so that the first session management network element triggers the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane functional network element in the primary PLMN, so that the multicast/broadcast user plane functional network element of the primary PLMN uses the same serial number for the data of the same multicast/broadcast service, thereby realizing the synchronization of the serial numbers of the data of the same multicast/broadcast service in different PLMNs, which is conducive to data synchronization.
  • the present application provides an eighth communication method, which is executed by a multicast/broadcast session management network element, or may be executed by a component of the multicast/broadcast session management network element (e.g., a processor, a chip, or a chip system, etc.), or may be implemented by a logic module or software that can implement all or part of the functions of the multicast/broadcast session management network element. For example, it is executed by a second multicast/broadcast session management network element in a multi-operator network.
  • a component of the multicast/broadcast session management network element e.g., a processor, a chip, or a chip system, etc.
  • a logic module or software that can implement all or part of the functions of the multicast/broadcast session management network element.
  • it is executed by a second multicast/broadcast session management network element in a multi-operator network.
  • the second multicast/broadcast session management network element receives a session establishment request message from an application server, the session establishment request message including an identifier of a primary public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service; the second multicast/broadcast session management network element sends a multicast/broadcast service session context to the second session management network element, the multicast/broadcast service session context including an identifier of the primary PLMN and identification information of the first multicast/broadcast service.
  • the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service are used by the second multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network device of the MOCN and the multicast/broadcast user plane function network element corresponding to the identifier of the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second multicast/broadcast session management network element and the second session management network element are located in a PLMN other than the primary PLMN in the MOCN.
  • the second multicast/broadcast session management network element can send the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service to the second session management network element, so that the second session management network element triggers the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane functional network element in the primary PLMN, so that the multicast/broadcast user plane functional network element of the primary PLMN uses the same serial number for the data of the same multicast/broadcast service, thereby realizing the synchronization of the serial numbers of the data of the same multicast/broadcast service in different PLMNs, which is conducive to data synchronization.
  • the present application provides a ninth communication method, which is executed by a session management network element, or may be executed by a component of the session management network element (e.g., a processor, a chip, or a chip system, etc.), or may be implemented by a logic module or software that can implement all or part of the functions of the session management network element. For example, it is executed by a second session management network element in a second PLMN.
  • a ninth communication method which is executed by a session management network element, or may be executed by a component of the session management network element (e.g., a processor, a chip, or a chip system, etc.), or may be implemented by a logic module or software that can implement all or part of the functions of the session management network element. For example, it is executed by a second session management network element in a second PLMN.
  • the second session management network element receives a multicast session request message from a terminal device, and the multicast session request message includes an identifier of a multicast session; the second session management network element sends a multicast/broadcast service session context request message to a multicast/broadcast session management network element corresponding to the identifier of the multicast session according to the identifier of the multicast session; the second session management network element receives a multicast/broadcast service session context from the multicast/broadcast session management network element, and the multicast/broadcast service session context includes an identifier of a primary public land mobile network PLMN and identification information of a first multicast/broadcast service.
  • the identification information of the main PLMN and the identification information of the first multicast/broadcast service are used to trigger the establishment of a shared transmission channel between the access network device to which the terminal device is connected and the multicast/broadcast user plane functional network element corresponding to the identification of the main PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second session management network element sends the identifier of the primary PLMN to the access network device in the multi-operator core network. and identification information of the first multicast/broadcast service.
  • the present application provides a tenth communication method, which is executed by an access network device, and may also be executed by a component of the access network device (such as a processor, a chip, or a chip system, etc.), and may also be implemented by a logic module or software that can implement all or part of the functions of the access network device. For example, it is executed by a first access network device.
  • a component of the access network device such as a processor, a chip, or a chip system, etc.
  • a logic module or software that can implement all or part of the functions of the access network device. For example, it is executed by a first access network device.
  • the first access network device receives a first N2 protocol data unit session resource message from a first session management network element, and the first N2 protocol data unit session resource message includes an identifier of a primary public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service, and the first access network device is located in the MOCN; the first access network device sends a first N2 multicast session request message to the multicast/broadcast session management network element in the primary PLMN, and the first N2 multicast session request message includes identification information of the first multicast/broadcast service.
  • the access network device can request the multicast/broadcast session management network element of the primary PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the primary PLMN based on the identifier of the primary PLMN, thereby facilitating the multicast/broadcast user plane function network element of the primary PLMN to use the same serial number for data of the same multicast/broadcast service, thereby achieving synchronization of the serial numbers of data of the same multicast/broadcast service in different PLMNs, which is conducive to data synchronization.
  • the first access network device when the first access network device has not established a shared transmission channel, the first access network device sends identification information of the first multicast/broadcast service to the multicast/broadcast session management network element in the primary PLMN; the first access network device establishes a shared transmission channel with the multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first access network device can, based on the identifier of the primary PLMN, request the multicast/broadcast session management network element of the primary PLMN to establish a shared transmission channel with the multicast/broadcast user plane functional network element of the primary PLMN, thereby facilitating the multicast/broadcast user plane functional network element of the primary PLMN to use the same serial number for data of the same multicast/broadcast service, thereby facilitating data synchronization.
  • the first access network device receives a second N2 protocol data unit session resource message from a second session management network element, the second N2 protocol data unit session resource message including an identifier of a primary PLMN and identifier information of a first multicast/broadcast service; when the first access network device has established a shared transmission channel, the first access network device discards the second N2 protocol data unit session resource message; or, the first access network device sends a third indication message to the second session management network element, the third indication message is used to indicate that the shared transmission channel has been established.
  • the first session management network element is located in the primary PLMN, and the second session management network element is located in a PLMN other than the primary PLMN in the MOCN; or, the first session management network element is located in a PLMN other than the primary PLMN in the MOCN, and the second session management network element is located in the primary PLMN.
  • the first access network device may discard the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service, or send a third indication information to the second session management network element in the second PLMN, and the third indication information is used to indicate that the shared transmission channel has been established. That is, if the first access network device cannot be shared by all PLMNs of the MOCN, the first access network device may not use the identifier of the primary PLMN, but establish the shared transmission channel by itself.
  • a first access network device sends a switching request message to a second access network device, and the switching request message includes an identifier of a primary PLMN and identifier information of a first multicast/broadcast service; the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service are used to trigger establishment of a shared transmission channel between the second access network device and a multicast/broadcast user plane functional network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first access network device can send an identifier of a primary PLMN to the second access network device, which is beneficial for the second access network device to request, based on the identifier of the primary PLMN, the multicast/broadcast session management network element of the primary PLMN to establish a shared transmission channel with the multicast/broadcast user plane functional network element of the primary PLMN, thereby facilitating the multicast/broadcast user plane functional network element of the primary PLMN to use the same serial number for data of the same multicast/broadcast service, thereby facilitating data synchronization.
  • the present application provides an eleventh communication method, which is executed by an access network device, or may be executed by a component of the access network device (such as a processor, a chip, or a chip system, etc.), or may be implemented by a logic module or software that can implement all or part of the functions of the access network device. For example, it is executed by a first access network device.
  • the first access network device receives identification information of a first multicast/broadcast service; the first access network device sends an Xn interface message to a second access network device, and the Xn interface message includes identification information of the first multicast/broadcast service.
  • the first PLMN being a PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, the first shared transmission channel being used to transmit data of the first multicast/broadcast service.
  • the identifier of the first PLMN and the identifier information of the first multicast/broadcast service are used to trigger the establishment of a second shared transmission channel between the second access network device and the multicast/broadcast user plane function network element in the first PLMN, the second shared transmission channel being used to transmit data of the first multicast/broadcast service.
  • the first access network device and the second access network device are located in a multi-operator core network MOCN, and the first PLMN belongs to the MOCN.
  • the access network devices located in the MOCN and having the Xn interface can exchange the identification information of the multicast/broadcast service and the identification of the PLMN to which they belong through the Xn interface, so that the access network devices in the MOCN with the Xn interface can establish a shared transmission channel with the same multicast/broadcast user plane functional network element, which is conducive to data synchronization.
  • the present application provides a twelfth communication method, which is executed by an access network device, or may be executed by a component of the access network device (such as a processor, a chip, or a chip system, etc.), or may be implemented by a logic module or software that can realize all or part of the functions of the access network device. For example, it is executed by a second access network device.
  • a component of the access network device such as a processor, a chip, or a chip system, etc.
  • a logic module or software that can realize all or part of the functions of the access network device. For example, it is executed by a second access network device.
  • the second access network device receives an Xn interface message from the first access network device, and the Xn interface message includes identification information of a first multicast/broadcast service, and an identification of a first public land mobile network PLMN
  • the first PLMN is a PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service
  • the second access network device receives identification information of a second multicast/broadcast service, and according to the identification of the first PLMN, the identification information of the first multicast/broadcast service, and the identification information of the second multicast/broadcast service, establishes a second shared transmission channel with the multicast/broadcast user plane function network element in the first PLMN, and the second shared transmission channel is used to transmit data of the first multicast/broadcast service and data of the second multicast/broadcast service.
  • a second access network device located in the MOCN and having an Xn interface can receive identification information of multicast/broadcast services of other access network devices and an identification of the PLMN to which it belongs through the Xn interface, thereby enabling access network devices in the MOCN having an Xn interface to establish a shared transmission channel with the multicast/broadcast user plane functional network element in the PLMN, which is conducive to data synchronization.
  • the second access network device when the first multicast/broadcast service and the second multicast/broadcast service are of the same type, the second access network device sends a shared transmission channel establishment request message to the multicast/broadcast user plane functional network element in the first PLMN; or, when the multicast network address corresponding to the identification information of the first multicast/broadcast service is the same as the multicast network address corresponding to the identification information of the second multicast/broadcast service, the second access network device sends a shared transmission channel establishment request message to the multicast/broadcast user plane functional network element in the first PLMN.
  • the second access network device when the second multicast/broadcast service of the second access network device is the same as the first multicast/broadcast service of the first access network device, and the first access network device has established a shared transmission channel for the same multicast/broadcast service, the second access network device will attempt to establish a shared transmission channel to the first PLMN, which is conducive to achieving data synchronization.
  • the present application provides a thirteenth communication method, which is executed by an access network device, and may also be executed by a component of the access network device (such as a processor, a chip, or a chip system, etc.), and may also be implemented by a logic module or software that can implement all or part of the functions of the access network device. For example, it is executed by a first access network device.
  • a component of the access network device such as a processor, a chip, or a chip system, etc.
  • a logic module or software that can implement all or part of the functions of the access network device. For example, it is executed by a first access network device.
  • the first access network device sends a switching request message to the second access network device, and the switching request message includes an identifier of a first public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service, and the first PLMN is a PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the switching request message includes an identifier of a first public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service
  • the first PLMN is a PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • a first access network device receives a switching response message from a second access network device, the switching response message including an identifier of a second PLMN, where the second PLMN is the PLMN to which a multicast/broadcast user plane functional network element that establishes a second shared transmission channel with the second access network device belongs; or, the switching response message includes fourth indication information, where the fourth indication information is used to indicate that the multicast/broadcast user plane functional network element that establishes a second shared transmission channel with the second access network device belongs to the first PLMN; wherein the first access network device and the second access network device are located in MOCN, and the first PLMN and the second PLMN are different.
  • the first access network device can send an identifier of a first PLMN to which the first access network device belongs to the second access network device, which is beneficial for the second access network device to request, based on the identifier of the first PLMN, the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN, thereby allowing data of the same multicast/broadcast service to be transmitted through the same shared transmission channel, which is beneficial for achieving data synchronization.
  • the first access network device forwards the data of the first multicast/broadcast service to the second access network device according to the identifier of the second PLMN or the fourth indication information.
  • the first access network device can transmit part of the multicast/broadcast service data currently being sent by the first access network device to the second access network device within a certain period of time (for example, based on a timer, etc.), which can partially alleviate the problem of packet loss.
  • a first access network device receives a first N2 protocol data unit session resource message, which includes an identifier of a first PLMN and identifier information of a first multicast/broadcast service; the first access network device establishes a first shared transmission channel with a multicast/broadcast user plane functional network element in the first PLMN based on the identifier of the first PLMN and the identifier information of the first multicast/broadcast service.
  • the first access network device can request the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane functional network element of the first PLMN based on the identification of the first PLMN and the identification information of the first multicast/broadcast service, thereby facilitating the multicast/broadcast user plane functional network element of the first PLMN to use the same serial number for data of the same multicast/broadcast service, thereby facilitating data synchronization.
  • the switching request message is used to request switching of the terminal device from the first access network device to the second access network device, and the switching request message further includes an identifier of the PLMN to which the terminal device belongs.
  • the first access network device can also send the identifier of the PLMN to which the terminal device belongs to the second access network device, which is conducive to the second access network device using the multicast/broadcast user plane functional network element of the PLMN to which the terminal device belongs as a suboptimal choice for establishing a shared transmission channel.
  • the present application provides a fourteenth communication method, which is executed by an access network device, and may also be executed by a component of the access network device (such as a processor, a chip, or a chip system, etc.), and may also be implemented by a logic module or software that can implement all or part of the functions of the access network device. For example, it is executed by a second access network device.
  • a fourteenth communication method which is executed by an access network device, and may also be executed by a component of the access network device (such as a processor, a chip, or a chip system, etc.), and may also be implemented by a logic module or software that can implement all or part of the functions of the access network device. For example, it is executed by a second access network device.
  • the second access network device receives a switching request message from the first access network device, and the switching request message includes an identifier of a first public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service, and the first PLMN is a PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the switching request message includes an identifier of a first public land mobile network PLMN in a multi-operator core network MOCN and identification information of a first multicast/broadcast service
  • the first PLMN is a PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second access network device sends a switching response message to the first access network device, and the switching response message includes an identifier of the second PLMN, where the second PLMN is the PLMN to which the multicast/broadcast user plane functional network element that establishes a second shared transmission channel with the second access network device belongs; or, the switching response message includes fourth indication information, and the fourth indication information is used to indicate that the multicast/broadcast user plane functional network element that establishes a second shared transmission channel with the second access network device belongs to the first PLMN; wherein the first access network device and the second access network device are located in the MOCN, and the first PLMN and the second PLMN are different.
  • the second access network device can receive an identifier of a first PLMN to which the first access network device belongs, so that the second access network device, based on the identifier of the first PLMN, requests the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN, thereby allowing data of the same multicast/broadcast service to be transmitted through the same shared transmission channel, which is conducive to data synchronization.
  • the second access network device when the second access network device has not established a second shared transmission channel for transmitting data of the first multicast/broadcast service, the second access network device establishes a second shared transmission channel with a multicast/broadcast user plane functional network element in the first PLMN based on an identifier of the first PLMN and identifier information of the first multicast/broadcast service.
  • the second access network device can attempt to establish a shared transmission channel with the multicast/broadcast user plane functional network element in the first PLMN, so that data of the same multicast/broadcast service can be transmitted through the same shared transmission channel, which is conducive to achieving data synchronization.
  • the switching response message when the second access network device has established a second shared transmission channel for transmitting data of the first multicast/broadcast service, the switching response message includes an identifier of the PLMN corresponding to the second shared transmission channel, or the switching response message includes the fourth indication information.
  • the second access network device when the identifier of the PLMN corresponding to the second shared transmission channel is different from the identifier of the first PLMN, the second access network device receives data of a first multicast/broadcast service from the first access network device; the second access network device forwards the data of the first multicast/broadcast service using a unicast method.
  • the second access network device can receive part of the data of the multicast/broadcast service currently being sent by the first access network device within a certain period of time (for example, based on a timer, etc.), which can partially alleviate the problem of packet loss.
  • the switching request message is used to request switching of the terminal device from the first access network device to the second access network device, and the switching request message further includes an identifier of the PLMN to which the terminal device belongs.
  • the second access network device can also receive the identifier of the PLMN to which the terminal device belongs, so that the second access network device can use the multicast/broadcast user plane function network element of the PLMN to which the terminal device belongs as a suboptimal choice for establishing a shared transmission channel.
  • the second access network device establishes the second shared transmission channel according to the identifier of the first PLMN, or the identifier of the second PLMN, or the identifier of the PLMN to which the terminal device belongs.
  • the present application provides a fifteenth communication method, which is implemented by interaction between a multicast/broadcast session management network element, a multicast/broadcast user plane function network element, and an application server.
  • the application server sends a first public land network located in a multi-operator core network MOCN to the first public land network.
  • a first multicast/broadcast session management network element in a mobile network PLMN sends a first session establishment request message, the first session establishment request message includes identification information of a first multicast/broadcast service; an application server sends a second session establishment request message to a second multicast/broadcast session management network element in a second PLMN of the MOCN, the second session establishment request message includes identification information of the first multicast/broadcast service.
  • the first multicast/broadcast session management network element sends first indication information to a first multicast/broadcast user plane function network element according to the first session establishment request message, the first indication information is used to instruct the first multicast/broadcast user plane function network element to increment a first sequence number corresponding to the data of the first multicast/broadcast service when receiving the data; wherein the first multicast/broadcast session management network element and the first multicast/broadcast user plane function network element are located in the first PLMN.
  • the second multicast/broadcast session management network element sends second indication information to the second multicast/broadcast user plane function network element according to the second session establishment request message, and the second indication information is used to instruct the second multicast/broadcast user plane function network element to increment the second sequence number corresponding to the data of the first multicast/broadcast service when receiving the data of the first multicast/broadcast service; wherein the second multicast/broadcast session management network element and the second multicast/broadcast user plane function network element are located in the second PLMN.
  • the application server sends the data of the first multicast/broadcast service to the first multicast/broadcast user plane function network element and the second multicast/broadcast user plane function network element.
  • the first multicast/broadcast user plane function network element increments the first sequence number corresponding to the data of the first multicast/broadcast service according to the first indication information.
  • the second multicast/broadcast user plane function network element increments the second sequence number corresponding to the data of the first multicast/broadcast service according to the second indication information.
  • the application server can pre-request multiple PLMNs in the MOCN to perform special user plane configuration, so that each PLMN will synchronously update the sequence number of the data of the same multicast/broadcast service (for example, the sequence number of the data is updated upon receipt of the data), thereby enabling different multicast/broadcast user plane functional network elements to set the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the steps of interaction between the multicast/broadcast session management network element, the multicast/broadcast user plane function network element, and the application server can also refer to the description in the first to fifth aspects, and any possible implementation manner in the first to fifth aspects, and will not be repeated here.
  • the present application provides a sixteenth communication method, which is implemented by the interaction between a multicast/broadcast session management network element, a multicast/broadcast user plane function network element, a session management network element, an application server, and an access network device.
  • the application server generates a session establishment request message, and the session establishment request message includes the identifier of the primary PLMN in the multi-operator core network MOCN and the identification information of the first multicast/broadcast service.
  • the application server sends the session establishment request message to the first multicast/broadcast session management network element and the second multicast/broadcast session management network element respectively.
  • the first multicast/broadcast session management network element sends a multicast/broadcast service session context to the first session management network element, and the multicast/broadcast service session context includes the identifier of the primary PLMN and the identification information of the first multicast/broadcast service; the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used by the first multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first multicast/broadcast session management network element and the first session management network element are located in the primary PLMN.
  • the second multicast/broadcast session management network element sends a multicast/broadcast service session context to the second session management network element, and the multicast/broadcast service session context includes the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service; the identifier of the primary PLMN and the identifier information of the multicast/broadcast service are used by the second multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network device of the MOCN and the multicast/broadcast user plane function network element corresponding to the identifier of the primary PLMN, and the shared transmission channel is used to transmit the data of the first multicast/broadcast service; wherein the second multicast/broadcast session management network element and the second session management network element are located in a PLMN other than the primary PLMN in the MOCN.
  • the second session management network element receives a multicast session request message from a terminal device, and the multicast session request message includes the identifier of the multicast session; the second session management network element sends a multicast/broadcast service session context request message to the multicast/broadcast session management network element corresponding to the identifier of the multicast session according to the identifier of the multicast session.
  • the second session management network element receives the multicast/broadcast service session context from the multicast/broadcast session management network element, and the multicast/broadcast service session context includes the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service; the second session management network element sends the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service to the first access network device in the MOCN.
  • the first access network device in the MOCN receives the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service; the first access network device sends an N2 multicast session request message to the multicast/broadcast session management network element in the primary PLMN.
  • the access network equipment in the MOCN by enhancing the shared transmission channel establishment process of the access network equipment in the MOCN, the access network equipment in the MOCN establishes a shared transmission channel with the multicast/broadcast user plane functional network element of the main PLMN, thereby avoiding the situation where multiple multicast/broadcast user plane functional network elements generate different serial numbers, which is conducive to achieving data synchronization.
  • the steps of interaction between the multicast/broadcast session management network element, the multicast/broadcast user plane function network element, the application server, and the access network device can also refer to the description in the sixth to tenth aspects, and any possible implementation manner in the sixth to tenth aspects, and will not be repeated here.
  • the present application provides a seventeenth communication method, which is implemented by interaction between multiple access network devices having Xn interfaces in MOCN.
  • the first access network device receives identification information of a first multicast/broadcast service; the first access network device sends an Xn interface message to the second access network device, the Xn interface message includes the identification information of the first multicast/broadcast service and the identification of a first public land mobile network PLMN, the first PLMN is a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device.
  • the first shared transmission channel is used to transmit data of the first multicast/broadcast service; wherein the identifier of the first PLMN and the identifier information of the first multicast/broadcast service are used to trigger the establishment of a second shared transmission channel between the second access network device and the multicast/broadcast user plane function network element in the first PLMN, and the second shared transmission channel is used to transmit data of the first multicast/broadcast service; wherein the first access network device and the second access network device are located in a multi-operator core network MOCN, and the first PLMN belongs to the MOCN.
  • the second access network device receives the identifier information of the second multicast/broadcast service; the second access network device establishes a second shared transmission channel with the multicast/broadcast user plane function network element in the first PLMN according to the identifier of the first PLMN, the identifier information of the first multicast/broadcast service and the identifier information of the second multicast/broadcast service, and the second shared transmission channel is used to transmit data of the first multicast/broadcast service and data of the second multicast/broadcast service; wherein the first access network device and the second access network device are located in the MOCN.
  • a plurality of access network devices with Xn interfaces in MOCN can establish a shared transmission channel with the same multicast/broadcast user plane functional network element, which is conducive to synchronization.
  • the steps of interaction between the multicast/broadcast session management network element, the multicast/broadcast user plane function network element, and the access network device in the MOCN can also refer to the description in the eleventh and twelfth aspects, as well as any possible implementation manner in the eleventh and twelfth aspects, and will not be repeated here.
  • the present application provides an eighteenth communication method, which is implemented by interaction between multiple access network devices in MOCN.
  • the first access network device sends a switching request message to the second access network device, and the switching request message includes an identifier of a first public land mobile network PLMN in a multi-operator core network MOCN and identifier information of a first multicast/broadcast service.
  • the first PLMN is a PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second access network device sends a switching response message to the first access network device, and the switching response message includes an identifier of a second PLMN, and the second PLMN is a PLMN to which a multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs; or the switching response message includes fourth indication information, and the fourth indication information is used to indicate that the multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs to the first PLMN; wherein the first access network device and the second access network device are located in MOCN, and the first PLMN and the second PLMN are different.
  • the first access network device can send an identifier of a first PLMN to which the first access network device belongs to the second access network device, which is beneficial for the second access network device to request, based on the identifier of the first PLMN, the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN, thereby allowing data of the same multicast/broadcast service to be transmitted through the same shared transmission channel, which is beneficial for achieving data synchronization.
  • the steps of interaction between the first access network device and the second access network device may also refer to the description in the thirteenth aspect and the fourteenth aspect, and any possible implementation manner in the thirteenth aspect and the fourteenth aspect, and will not be repeated here.
  • the present application provides a first communication device, which may be a multicast/broadcast session management network element, or a device in a multicast/broadcast session management network element, or a device that can be used in combination with a multicast/broadcast session management network element.
  • the communication device may include a module that executes the method/operation/step/action described in the first aspect, the second aspect, the seventh aspect, the eighth aspect, and any possible implementation of the first aspect, the second aspect, the seventh aspect, and the eighth aspect, and the module may be a hardware circuit, or software, or a combination of a hardware circuit and software.
  • the communication device may include a processing unit and a communication unit.
  • the specific description of the method executed by the multicast/broadcast session management network element can refer to the corresponding description in the above-mentioned first aspect, second aspect, seventh aspect, eighth aspect, and any possible implementation of the first aspect, second aspect, seventh aspect, and eighth aspect, which will not be repeated here. It can be understood that the communication device can also achieve the effects that can be achieved in the first aspect, second aspect, seventh aspect, eighth aspect, and any possible implementation of the first aspect, second aspect, seventh aspect, and eighth aspect.
  • the present application provides a second communication device, which may be a multicast/broadcast user plane functional network element, or a device in a multicast/broadcast user plane functional network element, or a device that can be used in combination with a multicast/broadcast user plane functional network element.
  • the communication device may include a module that executes the methods/operations/steps/actions described in the third and fourth aspects, and any possible implementation of the third and fourth aspects, and the module may be a hardware circuit, or software, or a combination of a hardware circuit and software.
  • the communication device may include a processing unit and a communication unit.
  • the specific description of the method executed by the multicast/broadcast user plane function network element can refer to the corresponding description in the third aspect and the fourth aspect, and any possible implementation of the third aspect and the fourth aspect, which will not be repeated here. It can be understood that the communication device can also achieve the effects that can be achieved in the third aspect and the fourth aspect, and any possible implementation of the third aspect and the fourth aspect.
  • the present application provides a third communication device, which may be an application server, or a device in an application server, or a device that can be used in conjunction with an application server.
  • the communication device may include executing The module corresponding to the method/operation/step/action described in the fifth aspect and the sixth aspect, and any possible implementation of the fifth aspect and the sixth aspect, may be a hardware circuit, or software, or a combination of a hardware circuit and software.
  • the communication device may include a processing unit and a communication unit.
  • the specific description of the method executed by the application server can refer to the corresponding description in the fifth and sixth aspects above, and any possible implementation of the fifth and sixth aspects, and will not be repeated here. It can be understood that the communication device can also achieve the effects that can be achieved in the fifth and sixth aspects, and any possible implementation of the fifth and sixth aspects.
  • the present application provides a fourth communication device, which may be a session management network element, or a device in a session management network element, or a device that can be used in combination with a session management network element.
  • the communication device may include a module that executes the method/operation/step/action described in the ninth aspect and any possible implementation of the ninth aspect, and the module may be a hardware circuit, or software, or a combination of a hardware circuit and software.
  • the communication device may include a processing unit and a communication unit.
  • the specific description of the method executed by the session management network element can refer to the corresponding description in the above-mentioned ninth aspect and any possible implementation of the ninth aspect, and will not be repeated here. It can be understood that the communication device can also achieve the effects that can be achieved in the ninth aspect and any possible implementation of the ninth aspect.
  • the present application provides a fifth communication device, which may be an access network device, or a device in the access network device, or a device that can be used in combination with the access network device.
  • the communication device may include a module that executes the methods/operations/steps/actions described in the tenth to fourteenth aspects, and any possible implementation of the tenth to fourteenth aspects, and the module may be a hardware circuit, or software, or a combination of a hardware circuit and software.
  • the communication device may include a processing unit and a communication unit.
  • the communication device can also achieve the effects that can be achieved in the tenth to fourteenth aspects, and any possible implementation of the tenth to fourteenth aspects.
  • the present application provides a communication device, comprising: a processor and a memory, the memory being used to store instructions, and when the instructions are executed by the processor, the communication device implements the method in any possible implementation of the first to fourteenth aspects and the first to fourteenth aspects.
  • the processor and the memory are coupled.
  • the present application provides a computer-readable storage medium, on which instructions are stored.
  • the instructions When the instructions are executed on a computer, the computer executes the method in any possible implementation of aspects one to fourteen, and aspects one to fourteen.
  • the present application provides a chip system, which includes a processor and an interface, and may also include a memory, for implementing the method in any possible implementation of aspect 1 to aspect 14, and aspect 1 to aspect 14.
  • the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • the present application provides a computer program product, comprising instructions, which, when executed on a computer, cause the computer to execute the method in any possible implementation of aspects one to fourteen, and aspects one to fourteen.
  • the present application provides a communication system, which may include one or more communication devices described in aspects 19 to 24 above, to implement aspects 1 to 14, and the method in any possible implementation of aspects 1 to 14.
  • FIG1 is a schematic diagram of a communication system
  • FIG2 is a schematic diagram of a MOCN in which different PLMNs share access network equipment
  • FIG. 3a and FIG. 3b are schematic flow charts of a communication method provided by the present application.
  • FIG4 is a flow chart of another communication method provided by the present application.
  • FIG5 is a flow chart of another communication method provided by the present application.
  • FIG6 is a flow chart of another communication method provided by the present application.
  • FIG7 is a schematic diagram of a communication device provided by the present application.
  • FIG8 is a schematic diagram of another communication device provided in the present application.
  • A/B can indicate A or B
  • a and/or B can indicate: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • the words “first”, “second”, etc. may be used to distinguish between technical features with the same or similar functions.
  • the words “first”, “second”, etc. do not limit the quantity and execution order, and the words “first”, “second”, etc. do not necessarily limit them to be different.
  • the present application provides a variety of communication methods, which can realize the synchronization of serial numbers of different access network devices in a multi-operator core network scenario and realize the synchronization of data transmission.
  • the communication method provided in the present application can be applied in a communication system, specifically, in a multi-operator core network (MOCN) system.
  • MOCN multi-operator core network
  • it can be applied in the communication system shown in FIG1 .
  • FIG1 is a schematic diagram of a communication system, which includes a wireless access network and an MOCN.
  • the wireless access network is used to implement functions related to wireless access.
  • MOCN mainly includes the following key logical network elements: multicast/broadcast-session management function (MB-SMF), multicast/broadcast-user plane function (MB-UPF), and application server (AS).
  • the communication system also includes network elements not shown in FIG1, such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), unified data management (UDM) network element, network repository function (NRF), etc., which are not limited in this application.
  • the application server in this application can also be called an application function network element.
  • the communication systems mentioned in this application include but are not limited to: narrowband Internet of things (NB-IoT), global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division synchronous code division multiple access (TD-SCDMA), and 5G wireless communication.
  • NB-IoT narrowband Internet of things
  • GSM global system for mobile communications
  • EDGE enhanced data rate for GSM evolution
  • WCDMA wideband code division multiple access
  • CDMA2000 code division multiple access 2000
  • TD-SCDMA time division synchronous code division multiple access
  • 5G wireless communication The three major application scenarios of 5G mobile communication systems are enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC) and enhanced machine-type communications (eMTC) as well as future communication systems (such as 6G/7G, etc.).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communications
  • eMTC
  • Terminal equipment also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • terminal devices are: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MID), wearable devices, drones, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, terminal devices in 5G networks, terminal devices in future evolved public land mobile networks (PLMN) or terminal devices in future communication systems, etc.
  • PLMN public land mobile networks
  • Access network equipment refers to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network, and can also be called a base station. That is, the satellite in this application can connect a terminal device to the RAN, and can also be called a satellite base station.
  • RAN radio access network
  • RAN nodes are: a gNB, a transmission reception point (TRP), an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home evolved NodeB (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), or a wireless fidelity (Wifi) access point (AP), a satellite in a satellite communication system, a wireless controller in a cloud radio access network (CRAN) scenario, a wearable device, a drone, or a device in an Internet of Vehicles (e.g., vehicle to everything (V2X)), or a communication device in device to device (D2D) communication, etc.
  • TRP transmission reception point
  • eNB evolved Node B
  • RNC radio network controller
  • NB Node B
  • BSC base station controller
  • BTS base transceiver station
  • AP wireless
  • the access network device may include a centralized unit (CU) node, a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • the RAN device including the CU node and the DU node will In the long term evolution (LTE) system, the protocol layer of the eNB is split, and the functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU, which is centrally controlled by the CU.
  • LTE long term evolution
  • MB-SMF has similar functions to SMF and is mainly responsible for session management in mobile networks, such as session establishment, modification, and release, for example, allocating IP addresses to users, selecting UPF that provides message forwarding functions, etc.
  • MB-UPF has similar functions to UPF and is mainly responsible for processing user messages, such as forwarding and billing.
  • FIG2 is a schematic diagram of different PLMNs sharing access network equipment in a MOCN.
  • the MOCN shows terminal equipment, access network equipment and PLMN.
  • other devices or network elements not shown can refer to the specific examples of existing MOCN, which are not limited in this application.
  • PLMN a and PLMN b have a common access network equipment (such as the next generation radio access network (NG-RAN) in FIG2 ).
  • NG-RAN next generation radio access network
  • the NG-RAN when PLMN a and PLMN b send the same multicast/broadcast service data to the NG-RAN respectively, the NG-RAN needs to send two copies of data on the air interface, which will cause a waste of air interface resources.
  • the communication method provided in this application allows access network equipment to identify that different operators are targeting the same service when requesting to establish a multicast/broadcast session, thereby being able to reuse air interface resources (i.e., sessions of different operators for the same service use the same air interface resources), thereby improving air interface transmission efficiency.
  • the multicast technology based on unicast aims to solve the problem of how to further save network resources on the basis of reusing the existing unicast process as much as possible.
  • multicast technology can also be called groupcast technology.
  • the user plane function network element only sends one copy of the data stream of the same service sent to different terminal devices in the group (for example, from the UPF to the access network), thereby improving the efficiency of the use of air interface resources and core network resources.
  • a joining process based on unicast multicast technology includes the following steps:
  • Step 1 The terminal device sends a join request message to the SMF.
  • the UE sends a join request message through a non-access stratum (NAS) message (such as a protocol data unit (PDU) session modification request or a PDU session establishment request), or a user plane join request message (such as an Internet group management protocol join (IGMPJoin) message).
  • NAS non-access stratum
  • PDU protocol data unit
  • IGMPJoin Internet group management protocol join
  • the join request message contains multicast group information (also called multicast session information, which is used to send data corresponding to the multicast group).
  • Step 2 After receiving the join request message from the terminal device, SMF obtains the multicast information. For example, SMF can obtain the multicast information from MB-SMF or UDR based on the multicast group information/multicast session information, and generate the multicast context information corresponding to the multicast based on the multicast information. Optionally, SMF can also generate the quality of service flow (QoS Flow) information of the unicast corresponding to the multicast.
  • QoS Flow quality of service flow
  • Step 3 SMF sends a request message to the access network device, which contains the information generated in step 2.
  • Step 4 The access network device establishes or modifies the multicast context information corresponding to the multicast according to the request message of the SMF.
  • the access network device may further establish the unicast context information.
  • MB-UPF inserts a sequence number (SN) when sending downlink multicast data. Since there is only one MB-UPF, all access network devices in PLMN have the same understanding of the sequence number (the same sequence number corresponds to the same data). Then different access network devices will generate a packet data convergence protocol (PDCP) sequence number based on the sequence number of the multicast data and send the data through the air interface.
  • PDCP packet data convergence protocol
  • a terminal device needs to be switched from a source access network device (referred to as S-RAN) to a target access network device (referred to as T-RAN)
  • S-RAN and T-RAN will exchange information (such as SN sequence number and/or PDCP sequence number), and S-RAN will decide when to stop forwarding based on the SN sequence number provided by T-RAN. For example, when forwarding to a certain SN sequence number, S-RAN will stop forwarding data.
  • MMS multicast and broadcast service
  • FIGS. 3a and 3b are flowcharts of a communication method provided by the present application.
  • the communication method is applied to the communication system shown in Figure 1.
  • the communication method can be implemented by interaction between an application server, a multicast/broadcast session management network element, and a multicast/broadcast user plane function network element, and includes the following steps:
  • An application server sends a first session establishment request message to a first multicast/broadcast session management network element located in a first PLMN of an MOCN.
  • the first PLMN located in the MOCN may refer to the first PLMN and other PLMNs being connected to one or more access network devices.
  • the MOCN network sharing architecture in this application only the RAN is shared.
  • the 5G MOCN (including UE, RAN and AMF) for the 5G system supports the ability of operators to use multiple PLMN IDs.
  • the first session establishment request message may include identification information of the first multicast/broadcast service.
  • the identification information of the multicast/broadcast service is used to identify the multicast/broadcast service.
  • the identification information of the multicast/broadcast service is used to uniquely identify the multicast/broadcast service globally.
  • the service can be identified by the identifier in different PLMNs.
  • the identification information of the multicast/broadcast service may be an associated session identifier (associated session identifier), and the associated session identifier enables the shared NG-RAN node to determine that multiple MBS sessions are sending the same content of the same MBS service.
  • the associated session identifier may be a source specific multicast address (SSM).
  • SSM source specific multicast address
  • the identification information of the multicast/broadcast service may be a temporary multicast group identifier (TMGI) list, indicating that the multicast/broadcast service is shared in the TMGI list.
  • TMGI temporary multicast group identifier
  • MOCN ID a MOCN identifier
  • the MOCN ID may be an IP multicast address.
  • the first session establishment request message further includes, but is not limited to, one or more of the following information: the type of the first multicast/broadcast service, identification information of the multicast session, or an identification of the PLMN, etc.
  • the type of the multicast/broadcast service is used to indicate the type of the first multicast/broadcast service, for example, a multicast service or a broadcast service. Further, when the type of the first multicast/broadcast service is a multicast service, it indicates that the first multicast/broadcast service has a sharing requirement, that is, the first multicast/broadcast service can be shared in different PLMNs.
  • the identification information of the multicast session is used to identify the multicast session, for example, it can be the TMGI corresponding to the multicast session, and the multicast session is used to transmit data of the first multicast/broadcast service.
  • the TMGI can be the TMGI corresponding to the first multicast/broadcast service in the first PLMN of the MOCN.
  • the TMGI can be the TMGI corresponding to the first multicast/broadcast service in the first PLMN of the MOCN.
  • the identification of the PLMN is used to identify the PLMN, for example, the PLMN ID.
  • the first session establishment request message is sent by the application server directly to the first multicast/broadcast session management network element, or is sent by the application server to the first multicast/broadcast session management network element through a network exposure function (NEF) network element, which is not limited in this application.
  • NEF network exposure function
  • the application server sends a second session establishment request message to a second multicast/broadcast session management network element located in a second PLMN of the MOCN.
  • the second session establishment request message may include identification information of the first multicast/broadcast service.
  • the identification information may be the same as or different from the identification information of the first multicast/broadcast service in step S101, without limitation.
  • step S101 The functional description of the identification information of the multicast/broadcast service can be referred to step S101, which will not be repeated here.
  • the second session establishment request message when the second session establishment request message carries identification information of the first multicast/broadcast service, it may indicate that the first multicast/broadcast service is shared in different PLMNs.
  • the second session establishment request message also includes the type of the first multicast/broadcast service, identification information of the multicast session, network sharing identification information, PLMN identification, etc.
  • the description of the above information can refer to the corresponding description in Example 1 and will not be repeated here.
  • S101 and S102 may be executed in a certain order or simultaneously.
  • S101 may be executed first and then S102;
  • S102 may be executed first and then S101; or
  • S101 and S102 may be executed simultaneously, which is not limited in this embodiment.
  • the first multicast/broadcast session management network element sends first indication information to the first multicast/broadcast user plane function network element according to the first session establishment request message.
  • the first indication information may be used to instruct the first multicast/broadcast user plane function network element to increment a first sequence number corresponding to the data when receiving data of the first multicast/broadcast service.
  • the first multicast/broadcast session management network element and the first multicast/broadcast user plane function network element are located in the first PLMN.
  • the specific implementation of the first indication information may include but is not limited to the following situations:
  • the first indication information is used as an independent information element. For example, it is implemented by setting a specific bit value for an existing information element, or by a newly added information element, without limitation.
  • the information element is carried in an N4mb session establishment/session modification message sent by the first multicast/broadcast session management network element to the first multicast/broadcast user plane function network element.
  • the increment in the present application refers to the increment of the sequence number, and the increment may be performed on the basis of the sequence number, and the magnitude of the increment follows a preset rule or strategy, and the magnitude may be fixed, for example, incremented in a fixed step length, and the fixed step length may be 1 or greater than 1.
  • the magnitude may also be variable, for example, incremented in an arithmetic progression, such as incrementing by 1, 3, 5, etc., which is not limited in this embodiment.
  • the plane function network element may also increment the serial number corresponding to the data.
  • the first indication information is implemented by a combination of multiple information elements. For example, in a forwarding action rule (FAR), it is defined to send data to a specific destination (such as a specified IP address), or it is defined to discard data before sending (that is, not sending data).
  • FAR forwarding action rule
  • the first indication information can also make the processing of the first multicast/broadcast service data by the first multicast/broadcast user plane functional network element the same as the processing of the first multicast/broadcast service data by other multicast/broadcast user plane functional network elements, which is also conducive to data synchronization.
  • the first multicast/broadcast session management network element can trigger the remaining session establishment steps, for example, the first multicast/broadcast session management network element executes the steps of interacting with the PCF to generate multicast policy information, etc.
  • the specific implementation method can refer to the corresponding description in the existing protocol standard and will not be repeated here.
  • the first multicast/broadcast session management network element sends first indication information to the first multicast/broadcast user plane function network element according to the type of the multicast/broadcast service in the first session establishment request message and/or the identification information of the first multicast/broadcast service.
  • the first multicast/broadcast session management network element sends the first indication information to the first multicast/broadcast user plane function network element, so that the first multicast/broadcast user plane function network element can synchronously update the sequence number of the data of the first multicast/broadcast service, so as to synchronize the sequence number of the data of the first multicast/broadcast service in different PLMNs.
  • the first indication information also includes a starting value of the first sequence number.
  • the starting value of the first sequence number is 0.
  • the second multicast/broadcast session management network element sends second indication information to the second multicast/broadcast user plane function network element according to the second session establishment request message.
  • the second indication information may be used to instruct the second multicast/broadcast user plane function network element to increment a second sequence number corresponding to the data when receiving data of the first multicast/broadcast service.
  • the second multicast/broadcast session management network element and the second multicast/broadcast user plane function network element are located in the second PLMN.
  • the specific implementation method of the second indication information can refer to the specific implementation method of the first indication information.
  • the second indication information is implemented as an independent information element by setting a specific bit value for the existing information element, or by a newly added information element.
  • the information element is carried in the N4mb session establishment/session modification message sent by the second multicast/broadcast session management network element to the second multicast/broadcast user plane function network element, or is implemented by a combination of one or more existing information elements, which will not be repeated here.
  • the second multicast/broadcast session management network element can trigger the remaining session establishment steps, for example, the second multicast/broadcast session management network element executes the steps of interacting with the PCF to generate multicast policy information, etc.
  • the specific implementation method can refer to the corresponding description in the existing protocol standard and will not be repeated here.
  • the second multicast/broadcast session management network element sends second indication information to the second multicast/broadcast user plane function network element according to the type of multicast/broadcast service in the second session establishment request message and/or the identification information of the first multicast/broadcast service.
  • the specific implementation method can refer to the implementation method in S103, which will not be repeated here.
  • the second multicast/broadcast session management network element sends the second indication information to the second multicast/broadcast user plane function network element, so that the second multicast/broadcast user plane function network element can synchronously update the sequence number of the data of the first multicast/broadcast service.
  • the second indication information also includes the starting value of the second sequence number.
  • the starting value of the second sequence number is 0.
  • the starting value of the first sequence number may be the same as the starting value of the second sequence number corresponding to the data of the first multicast/broadcast service in the second PLMN of the MOCN.
  • the strategy for incrementing the sequence number is also the same (for example, when receiving the data of the first multicast/broadcast service, the sequence number is increased by 1), so that the sequence number of the data of the first multicast/broadcast service can remain the same in the first PLMN and the second PLMN.
  • S103 and S104 may be executed in a certain order or simultaneously.
  • S103 may be executed first and then S104;
  • S104 may be executed first and then S103;
  • S103 and S104 may also be executed simultaneously, which is not limited in this embodiment.
  • the application server can pre-request multiple PLMNs in the MOCN (for example, the first PLMN and the second PLMN in this embodiment) to perform special user plane configuration, so that each PLMN will synchronously update the sequence number of the data of the same multicast/broadcast service (for example, the sequence number of the data is updated upon receipt of the data), thereby enabling different multicast/broadcast user plane functional network elements to set the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • PLMNs in the MOCN for example, the first PLMN and the second PLMN in this embodiment
  • each PLMN will synchronously update the sequence number of the data of the same multicast/broadcast service (for example, the sequence number of the data is updated upon receipt of the data), thereby enabling different multicast/broadcast user plane functional network elements to set the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the method further comprises the following steps, as shown in FIG3b:
  • the application server sends data of the first multicast/broadcast service to the first multicast/broadcast user plane function network element and the second multicast/broadcast user plane function network element.
  • an MBS session for transmitting the data of the first multicast/broadcast service may have been pre-established.
  • the first multicast/broadcast user plane function network element increments the first sequence number corresponding to the data of the first multicast/broadcast service according to the first indication information.
  • the increment may refer to the related description in step S103, for example, when the first multicast/broadcast user plane function network element receives data of the first multicast/broadcast service, the first sequence number corresponding to the data of the first multicast/broadcast service is increased by 1.
  • the first multicast/broadcast user plane functional network element adds 1 to the starting value of the first sequence number according to the first indication information, and the value after adding 1 is the value of the first sequence number corresponding to the data of the first multicast/broadcast service.
  • the first multicast/broadcast user plane function network element sends the data of the first multicast/broadcast service to the designated IP address according to the first indication information.
  • the second multicast/broadcast user plane function network element increments the second sequence number corresponding to the data of the first multicast/broadcast service according to the second indication information.
  • the increment may refer to the related description in step S103, for example, when the second multicast/broadcast user plane function network element receives data of the first multicast/broadcast service, the second sequence number corresponding to the data of the first multicast/broadcast service is increased by 1.
  • the second multicast/broadcast user plane functional network element adds 1 to the starting value of the second sequence number according to the second indication information, and the value after adding 1 is the value of the second sequence number corresponding to the data of the second multicast/broadcast service.
  • the second multicast/broadcast user plane function network element sends the data of the second multicast/broadcast service to the specified IP address according to the second indication information, wherein the specified IP address is the same as the specified IP address to which the first multicast/broadcast user plane function network element sends the data of the first multicast/broadcast service in S106.
  • the first serial number and the second serial number can be kept synchronized. If there is an access network device that can be connected to the first multicast/broadcast user plane functional network element and the second multicast/broadcast user plane functional network element at the same time, then when the access network device receives data of the first multicast/broadcast service from the first multicast/broadcast user plane functional network element and data of the first multicast/broadcast service from the second multicast/broadcast user plane functional network element, the access network device can recognize that the data from the two devices is data of the same multicast/broadcast service.
  • data for the same first multicast/broadcast service can be sent to the access network device only by the first multicast/broadcast user plane functional network element, or only by the second multicast/broadcast user plane functional network element, which is conducive to reducing the consumption of air interface resources.
  • S106 and S107 may be executed in a certain order or simultaneously.
  • S106 may be executed first and then S107;
  • S107 may be executed first and then S106; or
  • S106 and S107 may be executed simultaneously, which is not limited in this embodiment.
  • the message name in this application is only an example. This application does not limit the name of the message between each network element or device.
  • the name of each message can refer to the description in the standard protocol.
  • FIG4 is a flow chart of another communication method provided by the present application.
  • the communication method is applied to the communication system shown in FIG1.
  • the communication method can be implemented by interaction between an application server, a multicast/broadcast session management network element, a multicast/broadcast user plane function network element, a session management network element, an access network device, and a terminal device, and includes the following steps:
  • the application server generates a session establishment request message.
  • the session establishment request message may include the identifier of the primary PLMN in the MOCN, and further, may include the identifier information of the first multicast/broadcast service.
  • the main PLMN may also be called a primary PLMN, and the MB-UPF in the main PLMN may be called a primary MB-UPF.
  • the session establishment request message includes the identifier of the primary PLMN, and the primary MB-UPF may be used to uniformly route data of multicast/broadcast services in the MOCN, that is, it may not be limited to specific services.
  • the session establishment request message includes identification information of the first multicast/broadcast service and an identification of the primary PLMN.
  • the main MB-UPF can be used to uniformly route data of the first multicast/broadcast service in the MOCN, that is, all access network devices in the MOCN can establish a shared transmission channel with the main MB-UPF to realize the forwarding of data of the first multicast/broadcast service.
  • the description of the PLMN identification and the identification information of the multicast/broadcast service can refer to the corresponding description in Example 1, which will not be repeated here.
  • the application server sends the session establishment request message to the first multicast/broadcast session management network element and the second multicast/broadcast session management network element respectively.
  • the application server can select a PLMN as the main PLMN from the PLMNs that need to transmit data for multicast/broadcast services in the MOCN, and the access network device establishes a shared transmission channel with the MB-UPF of the main PLMN, that is, the access network device establishes a shared transmission channel with the same MB-UPF, thereby avoiding the situation where multiple MB-UPFs generate different serial numbers and solving the problem of serial number asynchrony.
  • the three PLMNs can all transmit data of multicast/broadcast services (such as data of the first multicast/broadcast service).
  • the application server selects the first PLMN as the primary PLMN, and the access network device establishes a shared transmission channel with the MB-UPF of the first PLMN to transmit data of the first multicast/broadcast service.
  • the session establishment request message further includes but is not limited to one or more of the following information: type of multicast/broadcast service, identification information of the multicast session, or network sharing identification information, etc.
  • type of multicast/broadcast service e.g., a multicast/broadcast service
  • identification information of the multicast session e.g., a multicast session
  • network sharing identification information e.g., a network sharing identification information
  • the session establishment request message can be sent by the application server directly to the first multicast/broadcast session management network element or the second multicast/broadcast session management network element, or by the application server through NEF to the first multicast/broadcast session management network element or the second multicast/broadcast session management network element, which is not limited in this application.
  • session establishment request message sent to the first multicast/broadcast session management network element and the second multicast/broadcast session management network element in the above S202 may be slightly different and is not limited.
  • steps S201-S202 may be replaced by: the application server sends the identifier of the primary PLMN to the first multicast/broadcast session management network element and the second multicast/broadcast session management network element respectively, and further, may send the identifier information of the first multicast/broadcast service without limitation.
  • the first multicast/broadcast session management network element sends the multicast/broadcast service session context to the first session management network element.
  • the multicast/broadcast service session context may include the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service.
  • the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service can be used by the first multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network device and the multicast/broadcast user plane function network element in the primary PLMN.
  • the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first multicast/broadcast session management network element triggers the access network device in the MOCN (for example, the access network device in the second PLMN) to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN after receiving the multicast/broadcast service session context.
  • the first multicast/broadcast session management network element and the first session management network element are located in the same PLMN, for example, they may be located in the second PLMN or in the first PLMN, without limitation.
  • the first multicast/broadcast session management network element triggers the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane functional network element in the primary PLMN.
  • the "trigger" here can be understood as: the first multicast/broadcast session management network element includes the identifier of the primary PLMN in the multicast/broadcast service session context, which is finally sent to the access network device in the MOCN via the first session management network element.
  • the access network device in the MOCN When the access network device in the MOCN has not yet established a transmission channel with the multicast/broadcast user plane functional network element for this multicast/broadcast service, the access network device in the MOCN establishes a shared transmission channel with the multicast/broadcast user plane functional network element of the primary PLMN.
  • the multicast/broadcast service session context also includes identification information of other multicast/broadcast services (for example, identification information of a second multicast/broadcast service)
  • the identification of the main PLMN and the identification information of the second multicast/broadcast service are used by the first multicast/broadcast session management network element to trigger the establishment of a second shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane functional network element in the main PLMN, and the second shared transmission channel is used to transmit data of the second multicast/broadcast service.
  • the first multicast/broadcast session management network element may further perform the following steps:
  • the first multicast/broadcast session management network element After receiving the session establishment request message, the first multicast/broadcast session management network element saves the primary PLMN identifier (also called Primary PLMN ID) and the identifier information of the first multicast/broadcast service in the MBS session context.
  • Primary PLMN ID also called Primary PLMN ID
  • the first multicast/broadcast session management network element After receiving the session establishment request message, the first multicast/broadcast session management network element triggers the remaining session establishment steps, for example, the first multicast/broadcast session management network element executes the step of interacting with the PCF to generate multicast policy information, the first multicast/broadcast session management network element executes the step of configuring the first multicast/broadcast user plane function network element, etc.
  • the first multicast/broadcast session management network element executes the step of interacting with the PCF to generate multicast policy information
  • the first multicast/broadcast session management network element executes the step of configuring the first multicast/broadcast user plane function network element, etc.
  • the second multicast/broadcast session management network element sends the multicast/broadcast service session context to the second session management network element.
  • the multicast/broadcast service session context includes the identifier of the primary PLMN in the MOCN, and further, may also include identifier information of the first multicast/broadcast service.
  • the identification information of the primary PLMN and the first multicast/broadcast service can be used by the second multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network device and the multicast/broadcast user plane function network element in the primary PLMN.
  • the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second multicast/broadcast session management network element triggers the access network device in the MOCN (e.g., the access network device in the second PLMN) to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN after receiving the multicast/broadcast service session context.
  • the second multicast/broadcast session management network element and the second session management network element are located in the same PLMN, for example, they may be located in the second PLMN or in the first PLMN without limitation.
  • the second multicast/broadcast session management network element triggers the establishment of a shared transmission channel between the access network device of MOCN and the multicast/broadcast user plane functional network element corresponding to the identifier of the primary PLMN.
  • the "trigger" here can be understood as: the second multicast/broadcast session management network element includes the identifier of the primary PLMN in the multicast/broadcast service session context, which is finally sent to the access network device in MOCN via the second session management network element.
  • the access network device in MOCN When the access network device in MOCN has not yet established a transmission channel for this multicast/broadcast service with the multicast/broadcast user plane functional network element, the access network device in MOCN establishes a shared transmission channel with the multicast/broadcast user plane functional network element of the primary PLMN.
  • the multicast/broadcast service session context also includes identification information of other multicast/broadcast services (for example, identification information of a second multicast/broadcast service)
  • identification of the main PLMN and the identification information of the second multicast/broadcast service are used by the second multicast/broadcast session management network element to trigger the establishment of a second shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane function network element in the main PLMN, and the second shared transmission channel is used to transmit data of the second multicast/broadcast service.
  • the second multicast/broadcast session management network element may further perform the following steps:
  • the second multicast/broadcast session management network element After receiving the session establishment request message, the second multicast/broadcast session management network element saves the primary PLMN identifier (also called Primary PLMN ID) and the identifier information of the first multicast/broadcast service in the MBS session context (i.e., saves them as part of the MBS session context).
  • Primary PLMN ID also called Primary PLMN ID
  • the second multicast/broadcast session management network element After receiving the session establishment request message, the second multicast/broadcast session management network element triggers the remaining session establishment steps, for example, the second multicast/broadcast session management network element executes the step of interacting with the PCF to generate multicast policy information, the second multicast/broadcast session management network element executes the step of configuring the second multicast/broadcast user plane function network element, etc.
  • the second multicast/broadcast session management network element executes the step of interacting with the PCF to generate multicast policy information
  • the second multicast/broadcast session management network element executes the step of configuring the second multicast/broadcast user plane function network element, etc.
  • S203 and S204 may be executed in a certain order or simultaneously.
  • S203 may be executed first and then S204;
  • S204 may be executed first and then S203;
  • S203 and S204 may also be executed simultaneously, which is not limited in this embodiment.
  • the shared transmission channel establishment process of the access network equipment in MOCN can be enhanced, so that the access network equipment in MOCN can establish a shared transmission channel with the multicast/broadcast user plane functional network element of the main PLMN, thereby avoiding the situation where multiple multicast/broadcast user plane functional network elements generate different serial numbers, which is conducive to achieving data synchronization.
  • Example 2 may further include the following steps:
  • S205 The terminal device sends a multicast session request message to the second session management network element in the second PLMN.
  • the multicast session request message includes an identifier of the multicast/broadcast service session.
  • the second session management network element sends a multicast/broadcast service session context request message to the multicast/broadcast session management network element corresponding to the identifier of the multicast/broadcast service session according to the identifier of the multicast/broadcast service session.
  • the identifier of the multicast session may include information such as TMGI or IP multicast address. For example, if in a certain time period, the terminal device requests to join the multicast group and sends a multicast session request message to the second session management network element.
  • the multicast session request message may be a PDU session establishment request (PDUSessionEstablishmentrequest) message, or a PDU session modification request (PDUSessionModificationrequest) message.
  • PDU sessionEstablishmentrequest PDU session establishment request
  • PDUSessionModificationrequest PDU session modification request
  • the second session management network element sends a multicast/broadcast service session context request message to the multicast/broadcast session management network element corresponding to the multicast/broadcast service session identifier according to the multicast session identifier, and the multicast/broadcast service session context request message is used to request to obtain the MBS session context corresponding to the multicast/broadcast service session.
  • the multicast/broadcast service session context request message can be an interface provided by MB-SMF - Multicast Broadcast Session Context Status Subscribe Request (Nmbsmf_MBSSession_ContextStatusSubscribe request) message.
  • the multicast/broadcast session management network element corresponding to the identifier of the multicast session sends the multicast/broadcast service session context to the second session management network element.
  • the multicast/broadcast service session context includes the identifier of the primary PLMN and identifier information of the first multicast/broadcast service.
  • the second session management network element sends an N2 protocol data unit session resource message to the first access network device in the MOCN.
  • the N2 protocol data unit session resource message may include the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service, and the first access network device is the access network device accessed by the terminal device joining the first multicast/broadcast service.
  • the first access network device sends a first N2 multicast session request message to the multicast/broadcast session management network element in the primary PLMN.
  • the first N2 multicast session request message is used to request the establishment of a shared transmission channel between the first access network and a multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first N2 multicast session request message may be a multicast broadcast and service distribution setup request transmission (MBS Distribution Setup Request Transfer) message.
  • MMS Distribution Setup Request Transfer multicast broadcast and service distribution setup request transmission
  • the message may be further included in a distribution setup request (DISTRIBUTION SETUP REQUEST) message sent by the first access network device to the AMF, and sent by the AMF to the multicast/broadcast session management network element in the primary PLMN.
  • DISTRIBUTION SETUP REQUEST distribution setup request
  • the first N2 multicast session request message includes identification information of the first multicast/broadcast service.
  • the identifier of the first multicast/broadcast service is an IP multicast address
  • the first access network provides the entire content of the identification information of the first multicast/broadcast service to the MB-SMF.
  • the first access network device may first select the corresponding AMF according to the identifier of the primary PLMN, and then the AMF may find the corresponding MB-SMF through the NRF according to the IP multicast address.
  • the first access network device may find the corresponding TMGI from the TMGI list according to the identifier of the primary PLMN (for example, find the corresponding TMGI according to the PLMN ID field contained in the TMGI). In this case, the first access network device only needs to provide part of the identification information of the first multicast/broadcast service (for example, provide the TMGI corresponding to the primary PLMN in the TMGI list).
  • S209 may include the following two cases:
  • Case 1 When the first access network device has not established a shared transmission channel, the first access network device sends a first N2 multicast session request message to the multicast/broadcast session management network element in the primary PLMN, and establishes a shared transmission channel with the multicast/broadcast user plane function network element in the primary PLMN.
  • the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first access network device can, based on the identifier of the first PLMN, request the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane functional network element of the first PLMN, thereby facilitating the multicast/broadcast user plane functional network element of the first PLMN to use the same serial number for the data of the first multicast/broadcast service, thereby facilitating data synchronization.
  • Case 2 When the first access network device has established a shared transmission channel, the first access network device discards the N2 protocol data unit session resource message; or, the first access network device sends a third indication information to the second session management network element, and the third indication information is used to indicate that the shared transmission channel has been established; or, the first access network device sends a response message of the N2 protocol data unit session resource message to the second session management network element, indicating that the first access network device has successfully received the N2 protocol data unit session resource message.
  • the N2 protocol data unit session resource message can be a NGAP PDU session resource establishment message, or a NGAP PDU session resource modification message.
  • the first access network device may discard the identifier of the first PLMN and the identifier information of the first multicast/broadcast service, or send a third indication information to the second session management network element, the third indication information is used to indicate that the shared transmission channel has been established. That is, if the first access network device cannot be shared by all PLMNs of the MOCN, the first access network device may not use the identifier of the primary PLMN, but establish a shared transmission channel by itself to transmit the data of the first multicast/broadcast service.
  • the first access network device can configure a radio resource control (RRC) connection of the terminal device.
  • RRC radio resource control
  • the first access network device sends a switching request message to the second access network device.
  • the switching request message includes the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service.
  • the first access network device determines to switch the terminal device
  • the first access network device can send a switching request message to the second access network device (that is, T-RAN).
  • the identification information of the first PLMN and the identification information of the first multicast/broadcast service are used to trigger the establishment of a shared transmission channel between the second access network device and the multicast/broadcast user plane function network element in the first PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the identification of the first public land mobile network refers to the PLMN whose MB-SMF manages the multicast session received by the UE in the S-RAN, which may be different from the UE's registered PLMN ID.
  • the second access network device sends a second N2 multicast session request message to the multicast/broadcast session management network element in the primary PLMN.
  • the second N2 multicast session request message includes the identification information of the first multicast/broadcast service, which is used to request the establishment of a shared transmission channel between the second access network and the multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second N2 multicast session request message can be a multicast broadcast and service distribution setup request transmission (MBS Distribution Setup Request Transfer) message. It can be further included in a distribution setup request (DISTRIBUTION SETUP REQUEST) message sent by the second access network device to the AMF, and sent by the AMF to the multicast/broadcast session management network element in the first PLMN.
  • the second N2 multicast session request message may include all or part of the identification information of the first multicast/broadcast service.
  • reference may be made to the description of the first N2 multicast session request message, which will not be described in detail here.
  • S211 may include the following two cases:
  • Case 1 When the second access network device has not established a shared transmission channel, the second access network device sends a second N2 multicast session request message to the multicast/broadcast session management network element in the primary PLMN, and establishes a shared transmission channel with the multicast/broadcast user plane function network element in the primary PLMN.
  • the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second access network device also establishes a multicast/broadcast channel with the primary PLMN.
  • the shared transmission channel between the multicast/broadcast user plane functional network elements is conducive to enabling the multicast/broadcast user plane functional network elements of the primary PLMN to use the same sequence number for the data of the first multicast/broadcast service, which is conducive to achieving data synchronization.
  • the second access network device may not use the identity of the primary PLMN due to configuration reasons, but establish a shared transmission channel through the existing process. For example, assuming that the second access network device cannot be shared by the PLMN, the second access network device can only be connected to the second PLMN, and the second access network device establishes a shared transmission channel with the multicast/broadcast user plane function network element of the second PLMN.
  • FIG5 is a flow chart of another communication method provided by the present application.
  • the communication method is applied to the communication system shown in FIG1.
  • the communication method can be implemented by the interaction between a multicast/broadcast session management network element, a multicast/broadcast user plane function network element, a session management network element, an access network device, and a terminal device, and includes the following steps:
  • a first access network device receives identification information of a first multicast/broadcast service.
  • the description of the identification information of the first multicast/broadcast service can refer to the corresponding description in Example 1, and will not be repeated here.
  • the terminal device sends a multicast session request message to the first session management network element, where the multicast session request message includes an identifier of the multicast session.
  • the multicast session request message may be a PDU session establishment request (PDUSessionEstablishmentrequest) message, or a PDU session modification request (PDUSessionModificationrequest) message.
  • the first session management network element sends a multicast/broadcast service session context request message to the multicast/broadcast session management network element corresponding to the multicast session identifier according to the multicast session identifier.
  • the multicast/broadcast service session context request message may be an interface provided by MB-SMF - Multicast Broadcast Session Context Status Subscribe Request (Nmbsmf_MBSSession_ContextStatusSubscribereques) message.
  • the identifier of the multicast session may include information such as TMGI or IP multicast address.
  • the multicast/broadcast session management network element corresponding to the multicast session identifier sends a multicast/broadcast service session context to the first session management network element.
  • the multicast/broadcast service session context includes identifier information of the first multicast/broadcast service.
  • the first session management network element sends identification information of the first multicast/broadcast service to the first access network device.
  • the first access network device receives the identification information of the first multicast/broadcast service from the first session management network element.
  • the first access network device may trigger a process for establishing a shared transmission channel.
  • the specific implementation method may refer to the corresponding process in the existing standard protocol and will not be repeated here.
  • the first access network device sends an Xn interface message to the second access network device.
  • the Xn interface message includes identification information of the first multicast/broadcast service and an identification of the first PLMN.
  • the Xn interface message may be an NG-RAN node configuration update (NG-RAN node Configuration Update) request message, or a resource status reporting (Resource Status Reporting) message, or a newly designed message, which is not limited in this application.
  • NG-RAN node Configuration Update NG-RAN node Configuration Update
  • Resource Status Reporting Resource Status Reporting
  • the first PLMN is a PLMN to which a multicast/broadcast user plane functional network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the first access network device and the second access network device are located in the MOCN, and the first PLMN belongs to the MOCN, and the first access network device and the second access network device both have an Xn interface, then the first access network can send the identification information of the first multicast/broadcast service and the identification of the first PLMN to the second access network device through the Xn interface.
  • the identification information of the first PLMN and the identification information of the first multicast/broadcast service are used to trigger the establishment of a second shared transmission channel between the second access network device and the multicast/broadcast user plane functional network element in the first PLMN, and the second shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the second access network device After the second access network device receives the identification information of the first PLMN and the identification information of the first multicast/broadcast service, if the second access network device needs to establish a shared transmission channel later, the second access network device preferentially chooses to establish a second shared transmission channel with the multicast/broadcast user plane functional network element in the first PLMN, so that the second access network device and the first access network device both establish a shared transmission channel to the same PLMN, which is conducive to achieving synchronization of data transmission.
  • the second access network device when the second access network device receives the Xn interface message, the second access network device will not immediately establish a shared transmission channel, but will wait until a terminal device with the same identification information of the first multicast/broadcast service joins the second access network device before establishing a corresponding shared transmission channel.
  • Example 3 further includes the following steps:
  • the second access network device receives identification information of a second multicast/broadcast service.
  • the identification information of the second multicast/broadcast service is similar to the identification information of the first multicast/broadcast service.
  • the description of the identification information of the second multicast/broadcast service can refer to the description of the identification information of the first multicast/broadcast service in Example 1, which will not be repeated here.
  • Another terminal device After a period of time, another terminal device sends a multicast session request message to the second session management network element.
  • the message includes an identification of the multicast session.
  • the second session management network element sends a multicast/broadcast service session context request message to the multicast/broadcast session management network element corresponding to the multicast session identifier according to the multicast session identifier.
  • the identifier of the multicast session may include information such as TMGI or IP multicast address.
  • the multicast/broadcast session management network element corresponding to the multicast session identifier sends a multicast/broadcast service session context to the second session management network element.
  • the multicast/broadcast service session context includes identifier information of the second multicast/broadcast service.
  • the second session management network element sends identification information of the second multicast/broadcast service to the second access network device.
  • the second access network device receives the identification information of the second multicast/broadcast service from the second session management network element.
  • the second session management network element in the above steps (5) to (8) can also be replaced by the first session management network element, that is, the terminal device can request to join the multicast group in the same PLMN or in another PLMN.
  • the second access network device establishes a second shared transmission channel with a multicast/broadcast user plane function network element in the first PLMN according to the identifier of the first PLMN, the identifier information of the first multicast/broadcast service and the identifier information of the second multicast/broadcast service.
  • the second shared transmission channel is used to transmit data of the first multicast/broadcast service and data of the second multicast/broadcast service.
  • S304 includes the following situations:
  • Case 1 When the first multicast/broadcast service and the second multicast/broadcast service are of the same type, the second access network device sends a shared transmission channel establishment request message to the multicast/broadcast user plane function network element in the first PLMN.
  • the type information of the first multicast/broadcast service may be included in the identification information of the first multicast/broadcast service
  • the type information of the second multicast/broadcast service may be included in the identification information of the second multicast/broadcast service.
  • a field in the identification information carries the type information.
  • Case 2 When the multicast network address corresponding to the identification information of the first multicast/broadcast service is the same as the multicast network address corresponding to the identification information of the second multicast/broadcast service, the second access network device sends a shared transmission channel establishment request message to the multicast/broadcast user plane function network element in the first PLMN.
  • the multicast network address corresponding to the first multicast/broadcast service may be included in the identification information of the first multicast/broadcast service
  • the multicast network address corresponding to the second multicast/broadcast service may be included in the identification information of the second multicast/broadcast service.
  • a field in the identification information carries the multicast network address corresponding to the multicast/broadcast service.
  • Case three when the identification information of the first multicast/broadcast service is the same as the identification information of the second multicast/broadcast service, the second access network device sends a shared transmission channel establishment request message to the multicast/broadcast user plane function network element in the first PLMN.
  • the second access network device finds that there is already an access network device (such as the first access network device) nearby that has established a shared transmission channel, the second access network device will attempt to establish a shared transmission channel to the same PLMN, which is conducive to achieving synchronization of data transmission.
  • FIG6 is a flow chart of another communication method provided by the present application.
  • the communication method is applied to the communication system shown in FIG1.
  • the communication method can be implemented by interaction between an application server, a multicast/broadcast session management network element, a multicast/broadcast user plane function network element, a session management network element, an access network device, and a terminal device, and includes the following steps:
  • S401 A first access network device sends a switching request message to a second access network device.
  • the switching request message includes the identifier of the first PLMN in the MOCN and the identifier information of the first multicast/broadcast service.
  • the first PLMN is a PLMN to which a multicast/broadcast user plane functional network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of a first multicast/broadcast service.
  • the description of the identification information of the first PLMN and the first multicast/broadcast service can refer to the corresponding description in Example 1, and will not be repeated here.
  • the first access network device sends the identifier of the first PLMN and identifier information of the first multicast/broadcast service to the second access network device.
  • the switching request message also includes the identifier of the PLMN to which the terminal device belongs.
  • the first access network device may also send the identifier of the PLMN to which the terminal device belongs to the second access network device, so that the second access network device uses the multicast/broadcast user plane function network element of the PLMN to which the terminal device belongs as a suboptimal choice for establishing a shared transmission channel.
  • the application server sends a first session establishment request message to a first multicast/broadcast session management network element in a first PLMN of the MOCN, wherein the first session establishment request message includes identification information of the first multicast/broadcast service and an identification of the first PLMN.
  • the first multicast/broadcast session management network element can trigger the remaining session establishment steps, for example, the first multicast/broadcast session management network element executes the steps of interacting with the PCF to generate multicast policy information, etc.
  • the specific implementation method can refer to the corresponding description in the existing protocol standard and will not be repeated here.
  • the application server sends a second session establishment request message to a second multicast/broadcast session management network element in a second PLMN of the MOCN, wherein the second session establishment request message includes an identifier of the second PLMN and identifier information of the first multicast/broadcast service.
  • the second multicast/broadcast session management network element can trigger the remaining session establishment steps, for example, the second multicast/broadcast session management network element executes the steps of interacting with the PCF to generate multicast policy information, etc.
  • the specific implementation method can refer to the corresponding description in the existing protocol standard and will not be repeated here.
  • the terminal device sends a multicast session request message to the first session management network element in the first PLMN, where the multicast session request message includes an identifier of the multicast session.
  • the first session management network element sends a multicast/broadcast service session context request message to a multicast/broadcast session management network element corresponding to the multicast session identifier according to the multicast session identifier.
  • the multicast/broadcast session management network element corresponding to the multicast session identifier sends a multicast/broadcast service session context to the first session management network element.
  • the multicast/broadcast service session context includes identifier information of the first multicast/broadcast service.
  • the first session management network element sends identification information of the first multicast/broadcast service to the first access network device.
  • the first access network device receives the identification information of the first multicast/broadcast service from the first session management network element.
  • the first access network device may trigger a process for establishing a shared transmission channel.
  • the specific implementation method may refer to the corresponding process in the existing standard protocol and will not be repeated here.
  • the first access network device may configure the RRC connection of the terminal device.
  • the specific implementation method may refer to the corresponding description in the existing protocol standard, which will not be repeated here.
  • the second access network device sends a switching response message to the first access network device.
  • the switching response message includes the identifier of the second PLMN or the fourth indication information.
  • the second PLMN is the PLMN to which the multicast/broadcast user plane functional network element that establishes the second shared transmission channel with the second access network device belongs.
  • the second PLMN is different from the first PLMN, indicating that the second access network device uses a PLMN identifier different from that of the first access network device to establish a shared transmission channel.
  • the second PLMN may be the first PLMN, that is, the PLMN pointed to by the shared transmission channel established by the second access network device is the first PLMN, indicating that the second access network device reuses the first PLMN.
  • the fourth indication information is used to indicate that the multicast/broadcast user plane functional network element that establishes the second shared transmission channel with the second access network device belongs to the first PLMN. That is, the PLMN pointed to by the shared transmission channel established by the second access network device is the first PLMN, indicating that the second access network device reuses the first PLMN.
  • S402 may include the following situations:
  • Case 1 When the second access network device has not established a second shared transmission channel for transmitting data of the first multicast/broadcast service, the second access network device establishes a second shared transmission channel with the multicast/broadcast user plane functional network element in the first PLMN based on the identifier of the first PLMN and the identifier information of the first multicast/broadcast service.
  • the second access network device may attempt to establish a shared transmission channel with the multicast/broadcast user plane functional network element in the first PLMN, so that the data of the first multicast/broadcast service is transmitted through the same shared transmission channel, which is conducive to data synchronization.
  • the second PLMN identifier included in the switching response message sent by the second access network device to the first access network device is the first PLMN identifier; or, the switching response message includes fourth indication information, and the fourth indication information is used to indicate that the multicast/broadcast user plane functional network element that establishes the second shared transmission channel with the second access network device belongs to the first PLMN. That is, the PLMN pointed to by the shared transmission channel established by the second access network device is the first PLMN, indicating that the second access network device reuses the first PLMN.
  • Case 2 When the second access network device has established a second shared transmission channel for transmitting data of the first multicast/broadcast service, the switching response message fed back by the second access network device to the first access network device includes the identifier of the second PLMN or the fourth indication information.
  • the switching response message fed back by the second access network device to the first access network device includes fourth indication information, and the fourth indication information is used to indicate that the multicast/broadcast user plane functional network element that establishes the second shared transmission channel with the second access network device belongs to the first PLMN; or, the identifier of the second PLMN included in the switching response message is the first PLMN.
  • the switching response message that the second access network device feeds back to the first access network device includes the identifier of the second PLMN. At this time, the second PLMN is different from the first PLMN.
  • the second access network device when the second access network device has established a second shared transmission channel for transmitting data of the first multicast/broadcast service, the second access network device The network access device may not feed back information to the first access network device.
  • the first access network device forwards the data of the first multicast/broadcast service to the second access network device according to the identifier of the second PLMN or the fourth indication information.
  • the first access network device may forward the data of the first multicast/broadcast service to the second access network device within a preset time period, which may partially alleviate the problem of packet loss but will not occupy more forwarding resources.
  • the first access network device can transmit part of the multicast/broadcast service data currently being sent by the first access network device to the second access network device within a certain period of time (for example, based on a timer, etc.), which can partially alleviate the problem of packet loss.
  • the second access network device forwards the data of the first multicast/broadcast service in unicast mode.
  • the first access network device may stop forwarding data of the first multicast/broadcast service to the second access network device.
  • the device or equipment provided by the present application may include a hardware structure and/or a software module, and the above functions are realized in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a certain function in the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • the division of modules in the present application is schematic, which is only a logical function division, and there may be other division methods in actual implementation.
  • each functional module in each embodiment of the present application can be integrated in a processor, or it can be physically present separately, or two or more modules can be integrated in one module.
  • the above integrated module can be implemented in the form of hardware or in the form of software functional modules.
  • FIG 7 is a schematic diagram of a communication device provided by the present application.
  • the device may include a module corresponding to the method/operation/step/action described in any of the embodiments shown in Figures 3a to 6, and the module may be a hardware circuit, or software, or a combination of a hardware circuit and software.
  • the apparatus 700 includes a communication unit 701 and a processing unit 702, and is used to implement the methods executed by each network element or device in the above embodiments.
  • the device is a multicast/broadcast session management network element, or is located in a multicast/broadcast session management network element.
  • the communication unit 701 is used to receive a first session establishment request message from an application server, and the first session establishment request message includes identification information of a first multicast/broadcast service and an identification of a first PLMN in the MOCN.
  • the processing unit 702 is used to send a first indication information to a first multicast/broadcast user plane function network element through the communication unit 701 according to the first session establishment request message, and the first indication information is used to instruct the first multicast/broadcast user plane function network element to increment a first sequence number corresponding to the data when receiving data of the first multicast/broadcast service; wherein the first multicast/broadcast session management network element and the first multicast/broadcast user plane function network element are located in the first PLMN.
  • the first sequence number is used by an access network device in the MOCN to identify data of a first multicast/broadcast service from a first PLMN.
  • the first session establishment request message further includes the type of the multicast/broadcast service.
  • the communication unit 701 is further configured to send first indication information to the first multicast/broadcast user plane function network element.
  • the first session establishment request message also includes network sharing identification information; the network sharing identification information is used to indicate that the first multicast/broadcast service is shared in the temporary multicast group identification TMGI list of the second PLMN of the MOCN, and the second PLMN is different from the first PLMN.
  • the communication unit 701 is also used to send the first indication information to the first multicast/broadcast user plane function network element according to the network sharing identification information.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation manner can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can instruct the corresponding first multicast/broadcast user plane function network element to perform special configuration, for example, instruct the first multicast/broadcast user plane function network element to increment the first sequence number corresponding to the data when receiving the data of the first multicast/broadcast service (for example, add 1 to the first sequence number).
  • the first multicast/broadcast user plane function network element synchronously updates the sequence number of the data of the same multicast/broadcast service according to the instruction of the first multicast/broadcast session management network element, which is conducive to realizing the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device is a multicast/broadcast session management network element, or is located in a multicast/broadcast session management network element.
  • the communication unit 701 is used to receive a second session establishment request message from an application server, and the second session establishment request message includes identification information of the first multicast/broadcast service and an identification of the second PLMN in the MOCN.
  • the processing unit 702 is used to send second indication information to the second multicast/broadcast user plane function network element through the communication unit 701 according to the second session establishment request message, and the second indication information is used to instruct the second multicast/broadcast user plane function network element to increment the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service; wherein the second multicast/broadcast session management network element and the second multicast/broadcast user plane function network element are located in the second PLMN.
  • the second serial number is used by an access network device in the MOCN to identify data of the first multicast/broadcast service from the second PLMN.
  • the first indication information includes a starting value of a first sequence number
  • the second indication information includes a starting value of a second sequence number
  • the starting value of the first sequence number is the same as the starting value of the second sequence number corresponding to the data of the first multicast/broadcast service in the second PLMN of the MOCN.
  • the second session establishment request message further includes the type of the multicast/broadcast service.
  • the communication unit 701 is further configured to send first indication information to the second multicast/broadcast user plane function network element.
  • the second session establishment request message further includes network sharing identification information; the network sharing identification information is used to indicate that the first multicast/broadcast service is shared in the temporary multicast group identification TMGI list of the second PLMN of the MOCN, and the second PLMN is different from the first PLMN.
  • the communication unit 701 is also used to send second indication information to the second multicast/broadcast user plane function network element according to the network sharing identification information.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation manner can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can instruct the corresponding second multicast/broadcast user plane function network element to perform special configuration, for example, instruct the second multicast/broadcast user plane function network element to increment the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service (for example, add 1 to the second sequence number).
  • the second multicast/broadcast user plane function network element synchronously updates the sequence number of the data of the same multicast/broadcast service according to the instruction of the second multicast/broadcast session management network element, thereby realizing the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device is a multicast/broadcast user plane functional network element, or is located in a multicast/broadcast user plane functional network element.
  • the communication unit 701 is used to receive first indication information from a multicast/broadcast session management network element, and the first indication information is used to instruct the first multicast/broadcast user plane functional network element to increment the first sequence number corresponding to the data when receiving the data of the first multicast/broadcast service.
  • the communication unit 701 is also used to receive the data of the first multicast/broadcast service from the application server; the processing unit 702 is used to increment the first sequence number corresponding to the data according to the first indication information.
  • the communication unit 701 is also used to send the data of the first multicast/broadcast service and the first serial number corresponding to the data to an access network device in the MOCN.
  • the first multicast/broadcast user plane function network element is located in the first PLMN of the MOCN.
  • the first serial number is used by the access network device to identify the data of the first multicast/broadcast service from the first PLMN.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation manner can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can perform special configuration on the processing of the user plane according to the instruction, for example, when the data of the first multicast/broadcast service is received, the first sequence number corresponding to the data is incremented, regardless of whether the data will be sent to the access network device.
  • the first multicast/broadcast user plane functional network element can synchronously update the sequence number of the data of the same multicast/broadcast service, and realize the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device is a multicast/broadcast user plane functional network element, or is located in a multicast/broadcast user plane functional network element.
  • the communication unit 701 receives second indication information from a second multicast/broadcast session management network element, and the second indication information is used to instruct the second multicast/broadcast user plane functional network element to increment the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service.
  • the communication unit 701 is also used to receive the data of the first multicast/broadcast service from the application server; the processing unit 702 is used to increment the second sequence number corresponding to the data according to the second indication information.
  • the communication unit 701 is also used to send data of the first multicast/broadcast service and a second serial number corresponding to the data to an access network device in the MOCN, the second multicast/broadcast user plane functional network element is located in the second PLMN of the MOCN, and the second serial number is used by the access network device to identify data of the first multicast/broadcast service from the second PLMN.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation manner can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can perform special configuration on the processing of the user plane according to the instruction, for example, when the data of the first multicast/broadcast service is received, the second sequence number corresponding to the data is incremented, regardless of whether the data will be sent to the access network device.
  • the second multicast/broadcast user plane functional network element can synchronously update the sequence number of the data of the same multicast/broadcast service, and realize the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device is an application server, or is located in an application server.
  • the communication unit 701 is used to send a first session establishment request message to a first multicast/broadcast session management network element located in a first PLMN of the MOCN, and the first session establishment request message includes an identifier of the first PLMN and identification information of the first multicast/broadcast service.
  • the communication unit 701 is also used to send a second session establishment request message to a second multicast/broadcast session management network element located in a second PLMN of the MOCN, and the second session establishment request message includes an identifier of the second PLMN and identification information of the first multicast/broadcast service; wherein the first PLMN is different from the second PLMN.
  • the processing unit 702 is optional and is not limited.
  • the first session request message also includes a starting value of a first sequence number corresponding to the data of the first multicast/broadcast service in the first PLMN;
  • the second session request message also includes a starting value of a second sequence number corresponding to the data of the first multicast/broadcast service in the second PLMN; wherein the starting value of the first sequence number is the same as the starting value of the second sequence number.
  • the specific execution process of the communication unit 701 in this implementation manner can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can send identification information of the first multicast/broadcast service to the multicast/broadcast session management network elements in different PLMNs of the MOCN, and the multicast/broadcast session management network elements in different PLMNs can then send indication information to the corresponding multicast/broadcast user plane functional network elements, which is conducive to enabling the multicast/broadcast user plane functional network elements in different PLMNs to simultaneously receive data of the first multicast/broadcast service from the application server and synchronously update the sequence number of the data for the first multicast/broadcast service, thereby facilitating data synchronization.
  • the device is an application server, or is located in an application server.
  • the processing unit 702 is used to generate a session establishment request message, which includes an identifier of a primary PLMN in the MOCN and identification information of a first multicast/broadcast service.
  • the communication unit 701 is used to send the session establishment request message to a multicast/broadcast session management network element.
  • the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used by the multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between an access network device in the MOCN and a multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the multicast/broadcast session management network element is located in the primary PLMN, or the multicast/broadcast session management network element is located in a PLMN other than the primary PLMN in the MOCN.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation mode can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can specify a PLMN in the MOCN as the main PLMN (referred to as the main PLMN), so that the access network devices in the MOCN establish a shared transmission channel with the multicast/broadcast user plane functional network element of the main PLMN, so that the multicast/broadcast user plane functional network element of the main PLMN uses the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device is a multicast/broadcast session management network element, or is located in a multicast/broadcast session management network element.
  • the communication unit 701 is used to receive a session establishment request message from an application server, and the session establishment request message includes an identifier of a primary PLMN in the MOCN and identification information of a first multicast/broadcast service.
  • the communication unit 701 is also used to send a multicast/broadcast service session context to a first session management network element, and the multicast/broadcast service session context includes an identifier of the primary PLMN and identification information of the first multicast/broadcast service.
  • the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used by the first multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between an access network device in the MOCN and a multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the processing unit 702 is optional and is not limited.
  • the first multicast/broadcast session management network element and the first session management network element are located in the primary PLMN.
  • the specific execution process of the communication unit 701 in this implementation mode can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can send the identification information of the primary PLMN and the first multicast/broadcast service to the first session management network element, so that the first session management network element triggers the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane function network element in the primary PLMN, so that the multicast/broadcast user plane function network element of the primary PLMN uses the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device is a multicast/broadcast session management network element, or is located in a multicast/broadcast session management network element.
  • the communication unit 701 is used to receive a session establishment request message from an application server, and the session establishment request message includes an identifier of a primary PLMN in the MOCN and identification information of a first multicast/broadcast service.
  • the communication unit 701 is also used to send a multicast/broadcast service session context to a second session management network element, and the multicast/broadcast service session context includes an identifier of the primary PLMN and identification information of the first multicast/broadcast service.
  • the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used by the second multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network device of the MOCN and the multicast/broadcast user plane function network element corresponding to the identifier of the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the processing unit 702 is optional and is not limited.
  • the second multicast/broadcast session management network element and the second session management network element are located in a PLMN other than the primary PLMN in the MOCN.
  • the specific execution process of the communication unit 701 in this implementation mode can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can send the identification information of the primary PLMN and the identification information of the first multicast/broadcast service to the second session management network element, so that the second session management network element triggers the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane functional network element in the primary PLMN, so that the multicast/broadcast user plane functional network element of the primary PLMN uses the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device is a session management network element, or is located in a session management network element.
  • the communication unit 701 is used to receive a multicast session request message from a terminal device, and the multicast session request message includes an identifier of a multicast session.
  • the processing unit 702 is used to send a multicast/broadcast service session context request message to a multicast/broadcast session management network element corresponding to the identifier of the multicast session through the communication unit 701 according to the identifier of the multicast session.
  • the communication unit 701 is also used to receive a multicast/broadcast service session context from the multicast/broadcast session management network element, and the multicast/broadcast service session context includes an identifier of a primary PLMN and identification information of a first multicast/broadcast service.
  • the primary PLMN The PLMN identifier and the identifier information of the first multicast/broadcast service are used to trigger the establishment of a shared transmission channel between the access network device to which the terminal device accesses and the multicast/broadcast user plane functional network element corresponding to the identifier of the primary PLMN.
  • the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the communication unit 701 is further configured to send the identifier of the primary PLMN and identifier information of the first multicast/broadcast service to an access network device in a core network of multiple operators.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation manner can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can request the multicast/broadcast session management network element corresponding to the identifier of the multicast session to obtain the multicast/broadcast service session context, thereby obtaining the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service, thereby triggering the establishment of a shared transmission channel between the access network device accessed by the terminal device and the multicast/broadcast user plane functional network element corresponding to the identifier of the primary PLMN, which is conducive to making the multicast/broadcast user plane functional network element of the primary PLMN use the same sequence number for the data of the same multicast/broadcast service, which is conducive to achieving data synchronization.
  • the device is an access network device, or is located in an access network device.
  • the communication unit 701 is used to receive a first N2 protocol data unit session resource message from a first session management network element, the first N2 protocol data unit session resource message including an identifier of a primary PLMN in the MOCN and identification information of a first multicast/broadcast service, and the first access network device is located in the MOCN.
  • the communication unit 701 is also used to send a first N2 multicast session request message to a multicast/broadcast session management network element in the primary PLMN, the first N2 multicast session request message including identification information of the first multicast/broadcast service.
  • the processing unit 702 is optional and is not limited.
  • the communication unit 701 is further configured to send identification information of the first multicast/broadcast service to the multicast/broadcast session management network element in the primary PLMN.
  • the processing unit 702 is configured to establish a shared transmission channel with a multicast/broadcast user plane function network element in the primary PLMN, where the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the communication unit 701 is further used to receive a second N2 protocol data unit session resource message from a second session management network element, the second N2 protocol data unit session resource message including an identifier of the primary PLMN and identifier information of the first multicast/broadcast service.
  • the processing unit 702 is used to discard the second N2 protocol data unit session resource message; or, the communication unit 701 is further used to send a third indication information to the second session management network element, the third indication information being used to indicate that the shared transmission channel has been established.
  • the first session management network element is located in the primary PLMN, and the second session management network element is located in a PLMN other than the primary PLMN in the MOCN; or, the first session management network element is located in a PLMN other than the primary PLMN in the MOCN, and the second session management network element is located in the primary PLMN.
  • the communication unit 701 is further used to send a switching request message to the second access network device, where the switching request message includes an identifier of the primary PLMN and identifier information of the first multicast/broadcast service.
  • the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service are used to trigger the establishment of a shared transmission channel between the second access network device and the multicast/broadcast user plane function network element in the primary PLMN, where the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation manner can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can request the multicast/broadcast session management network element of the primary PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the primary PLMN based on the identifier of the primary PLMN, thereby facilitating the multicast/broadcast user plane function network element of the primary PLMN to use the same sequence number for data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device is an access network device, or is located in an access network device.
  • the communication unit 701 is used to receive identification information of a first multicast/broadcast service.
  • the communication unit 701 is also used to send an Xn interface message to a second access network device, the Xn interface message including identification information of the first multicast/broadcast service and an identification of a first public land mobile network PLMN, the first PLMN being the PLMN to which a multicast/broadcast user plane functional network element that establishes a first shared transmission channel with the first access network device belongs, the first shared transmission channel being used to transmit data of the first multicast/broadcast service.
  • the identification of the first PLMN and the identification information of the first multicast/broadcast service are used to trigger the establishment of a second shared transmission channel between the second access network device and the multicast/broadcast user plane functional network element in the first PLMN, the second shared transmission channel being used to transmit data of the first multicast/broadcast service.
  • the processing unit 702 is optional and is not limited.
  • the first access network device and the second access network device are located in a multi-operator core network MOCN, and the first PLMN belongs to the MOCN.
  • the communication method implemented by the device enables access network devices located in the MOCN and having an Xn interface to exchange identification information of multicast/broadcast services and the identification of the PLMN to which they belong through the Xn interface, so that the access network devices in the MOCN with the Xn interface can establish a shared transmission channel with the same multicast/broadcast user plane function network element, which is conducive to data synchronization.
  • the device is an access network device, or is located in an access network device.
  • the communication unit 701 is used to receive an Xn interface message from a first access network device, the Xn interface message including identification information of a first multicast/broadcast service and an identification of a first PLMN, the first PLMN being the PLMN to which a multicast/broadcast user plane functional network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the communication unit 701 is also used to receive identification information of a second multicast/broadcast service.
  • the processing unit 702 is used to establish a second shared transmission channel with a multicast/broadcast user plane functional network element in the first PLMN according to the identification of the first PLMN, the identification information of the first multicast/broadcast service, and the identification information of the second multicast/broadcast service, and the second shared transmission channel is used to transmit data of the first multicast/broadcast service and data of the second multicast/broadcast service.
  • the first access network device and the second access network device are located in an MOCN, and the first PLMN belongs to the MOCN.
  • the communication unit 701 is used to send a shared transmission channel establishment request message to the multicast/broadcast user plane functional network element in the first PLMN; or, when the multicast network address corresponding to the identification information of the first multicast/broadcast service is the same as the multicast network address corresponding to the identification information of the second multicast/broadcast service, the communication unit 701 is used to send a shared transmission channel establishment request message to the multicast/broadcast user plane functional network element in the first PLMN.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation mode can also refer to the corresponding description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device enables the second access network device located in the MOCN and having an Xn interface to receive the identification information of the multicast/broadcast service of other access network devices and the identification of the PLMN to which it belongs through the Xn interface, so that the access network devices in the MOCN with the Xn interface can establish a shared transmission channel with the multicast/broadcast user plane function network element in the PLMN, which is conducive to data synchronization.
  • the device is an access network device, or is located in an access network device.
  • the communication unit 701 is used to send a handover request message to the second access network device, the handover request message including an identifier of a first PLMN in MOCN and identifier information of a first multicast/broadcast service, the first PLMN being the PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the communication unit 701 is also used to receive a handover response message from the second access network device, the handover response message including an identifier of a second PLMN, the second PLMN being the PLMN to which a multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs; or the handover response message includes fourth indication information, the fourth indication information being used to indicate that the multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs to the first PLMN.
  • the first access network device and the second access network device are located in MOCN, and the first PLMN and the second PLMN are different. It should be noted that in this implementation manner, the processing unit 702 is optional and is not limited.
  • the communication unit 701 is further configured to forward the data of the first multicast/broadcast service to the second access network device according to an identifier of the second PLMN or fourth indication information.
  • the communication unit 701 is further configured to receive a first N2 protocol data unit session resource message, where the first N2 protocol data unit session resource message includes an identifier of the first PLMN and identifier information of the first multicast/broadcast service.
  • the processing unit 702 is configured to establish a first shared transmission channel with a multicast/broadcast user plane function network element in the first PLMN according to the identifier of the first PLMN and the identifier information of the first multicast/broadcast service.
  • the switching request message is used to request to switch the terminal device from the first access network device to the second access network device, and the switching request message also includes an identifier of the PLMN to which the terminal device belongs.
  • the communication method implemented by the device can send the identifier of the first PLMN to which the first access network device belongs to the second access network device, which is conducive to the second access network device to request the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN based on the identifier of the first PLMN, so that the data of the same multicast/broadcast service is transmitted through the same shared transmission channel, which is conducive to data synchronization.
  • the device is an access network device, or is located in an access network device.
  • the communication unit 701 is used to receive a handover request message from the first access network device, the handover request message including an identifier of a first PLMN in the MOCN and identifier information of a first multicast/broadcast service, the first PLMN being the PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the communication unit 701 is also used to send a handover response message to the first access network device, the handover response message including an identifier of a second PLMN, the second PLMN being the PLMN to which a multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs; or the handover response message includes fourth indication information, the fourth indication information being used to indicate that the multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs to the first PLMN.
  • the first access network device and the second access network device are located in the MOCN, and the first PLMN and the second PLMN are different. It should be noted that in this implementation manner, the processing unit 702 is optional and is not limited.
  • processing the single Element 702 is used to establish a second shared transmission channel with a multicast/broadcast user plane function network element in the first PLMN according to the identifier of the first PLMN and the identifier information of the first multicast/broadcast service.
  • the switching response message includes an identifier of the PLMN corresponding to the second shared transmission channel, or the switching response message includes the fourth indication information.
  • the communication unit 701 is used to receive data of a first multicast/broadcast service from the first access network device.
  • the processing unit 702 is used to forward the data of the first multicast/broadcast service in a unicast manner.
  • the switching request message is used to request to switch the terminal device from the first access network device to the second access network device, and the switching request message also includes an identifier of the PLMN to which the terminal device belongs.
  • the processing unit 702 is configured to establish a second shared transmission channel according to an identifier of the first PLMN, or an identifier of the second PLMN, or an identifier of the PLMN to which the terminal device belongs.
  • the specific execution process of the communication unit 701 and the processing unit 702 in this implementation mode can also refer to the corresponding description in the above method embodiment, which will not be repeated here.
  • the communication method implemented by the device can receive the identifier of the first PLMN to which the first access network device belongs, so that the second access network device requests the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN based on the identifier of the first PLMN, so that the data of the same multicast/broadcast service is transmitted through the same shared transmission channel, which is conducive to data synchronization.
  • Fig. 8 is a schematic diagram of another communication device provided by the present application, which is used to implement the communication methods in the above method embodiments.
  • the device 800 may also be a chip system, or a network element or device described in the above method embodiments.
  • the apparatus 800 includes a communication interface 801 and a processor 802.
  • the communication interface 801 may be, for example, a transceiver, an interface, a bus, a circuit, or a device capable of implementing transceiver functions.
  • the communication interface 801 is used to communicate with other devices through a transmission medium, so that the apparatus 800 can communicate with other devices.
  • the processor 802 is used to perform processing-related operations.
  • the device 800 may be a multicast/broadcast session management network element, or may be located in a multicast/broadcast session management network element.
  • the communication interface 801 is used to receive a first session establishment request message from an application server, and the first session establishment request message includes identification information of a first multicast/broadcast service and an identification of a first PLMN in the MOCN.
  • the processor 802 is used to send first indication information to a first multicast/broadcast user plane function network element through the communication interface 801 according to the first session establishment request message, and the first indication information is used to instruct the first multicast/broadcast user plane function network element to increment a first sequence number corresponding to the data when receiving data of the first multicast/broadcast service; wherein the first multicast/broadcast session management network element and the first multicast/broadcast user plane function network element are located in the first PLMN.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can instruct the corresponding first multicast/broadcast user plane function network element to perform special configuration, for example, instruct the first multicast/broadcast user plane function network element to increment the first sequence number corresponding to the data when receiving the data of the first multicast/broadcast service (for example, add 1 to the first sequence number).
  • the first multicast/broadcast user plane function network element synchronously updates the sequence number of the data of the same multicast/broadcast service according to the instruction of the first multicast/broadcast session management network element, which is conducive to synchronizing the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device 800 may be a multicast/broadcast session management network element, or may be located in a multicast/broadcast session management network element.
  • the communication interface 801 is used to receive a second session establishment request message from an application server, and the second session establishment request message includes identification information of the first multicast/broadcast service and an identification of the second PLMN in the MOCN.
  • the processor 802 is used to send second indication information to the second multicast/broadcast user plane function network element through the communication interface 801 according to the second session establishment request message, and the second indication information is used to instruct the second multicast/broadcast user plane function network element to increment the second sequence number corresponding to the data of the first multicast/broadcast service when receiving the data; wherein the second multicast/broadcast session management network element and the second multicast/broadcast user plane function network element are located in the second PLMN.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can instruct the corresponding second multicast/broadcast user plane function network element to perform special configuration, for example, instruct the second multicast/broadcast user plane function network element to increment the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service (for example, add 1 to the second sequence number).
  • the second multicast/broadcast user plane function network element synchronously updates the sequence number of the data of the same multicast/broadcast service according to the instruction of the second multicast/broadcast session management network element, thereby realizing the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device 800 may be a multicast/broadcast user plane function network element, or may be located in a multicast/broadcast user plane function network element.
  • the communication interface 801 is used to receive first indication information from a multicast/broadcast session management network element, and the first indication information is used to instruct the first multicast/broadcast user plane function network element to increment the first sequence number corresponding to the data when receiving data of the first multicast/broadcast service.
  • the communication interface 801 is further configured to receive data of a first multicast/broadcast service from an application server; and the processor 802 is configured to increment a first sequence number corresponding to the data according to the first indication information.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can perform special configuration on the processing of the user plane according to the indication, for example, when the data of the first multicast/broadcast service is received, the first sequence number corresponding to the data is incremented, regardless of whether the data will be sent to the access network device.
  • the first multicast/broadcast user plane functional network element can synchronously update the sequence number of the data of the same multicast/broadcast service, and synchronize the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device 800 may be a multicast/broadcast user plane functional network element, or may be located in a multicast/broadcast user plane functional network element.
  • the communication interface 801 is used to receive second indication information from a second multicast/broadcast session management network element, and the second indication information is used to instruct the second multicast/broadcast user plane functional network element to increment the second sequence number corresponding to the data when receiving the data of the first multicast/broadcast service.
  • the communication interface 801 is also used to receive the data of the first multicast/broadcast service from the application server; the processor 802 is used to increment the second sequence number corresponding to the data according to the second indication information.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can indicate special configuration of the user plane processing, for example, when the data of the first multicast/broadcast service is received, the second sequence number corresponding to the data is incremented, regardless of whether the data will be sent to the access network device.
  • the second multicast/broadcast user plane functional network element can synchronously update the sequence number of the data of the same multicast/broadcast service, and realize the synchronization of the sequence number of the data of the same multicast/broadcast service in different PLMNs.
  • the device 800 may be an application server, or may be located in an application server.
  • the processor 802 is used to send a first session establishment request message to a first multicast/broadcast session management network element in a first PLMN of the MOCN through a communication interface 801, wherein the first session establishment request message includes an identifier of the first PLMN and identification information of the first multicast/broadcast service.
  • the processor 802 is also used to send a second session establishment request message to a second multicast/broadcast session management network element in a second PLMN of the MOCN through a communication interface 801, wherein the second session establishment request message includes an identifier of the second PLMN and identification information of the first multicast/broadcast service; wherein the first PLMN is different from the second PLMN.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can send identification information of the first multicast/broadcast service to the multicast/broadcast session management network elements in different PLMNs of the MOCN, and the multicast/broadcast session management network elements in different PLMNs then send indication information to the corresponding multicast/broadcast user plane function network elements, which is conducive to enabling the multicast/broadcast user plane function network elements in different PLMNs to simultaneously receive the data of the first multicast/broadcast service from the application server, and synchronously update the sequence number of the data for the first multicast/broadcast service, thereby facilitating data synchronization.
  • the device 800 may be an application server, or may be located in an application server.
  • the processor 802 is used to generate a session establishment request message, which includes an identifier of a primary PLMN in the MOCN and identifier information of a first multicast/broadcast service.
  • the communication interface 801 is used to send the session establishment request message to a multicast/broadcast session management network element.
  • the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service are used by the multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between an access network device in the MOCN and a multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can specify a PLMN in the MOCN as the main PLMN, so that the access network devices in the MOCN establish a shared transmission channel with the multicast/broadcast user plane functional network element of the main PLMN, so that the multicast/broadcast user plane functional network element of the main PLMN uses the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device 800 may be a multicast/broadcast session management network element, or may be located in the multicast/broadcast session management network element.
  • the communication interface 801 is used to receive a session establishment request message from an application server, and the session establishment request message includes an identifier of a primary PLMN in the MOCN and identification information of a first multicast/broadcast service.
  • the processor 802 is used to send a multicast/broadcast service session context to a first session management network element through the communication interface 801, and the multicast/broadcast service session context includes an identifier of the primary PLMN and identification information of the first multicast/broadcast service.
  • the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used by the first multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between an access network device in the MOCN and a multicast/broadcast user plane function network element in the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the specific execution process of the communication interface 801 and the processor 802 in this embodiment can also refer to the method executed by the communication unit in the embodiment of Figure 7, and the description in the above method embodiment, which will not be repeated here.
  • the identification information of the primary PLMN and the identification information of the first multicast/broadcast service are sent so that the first session management network element triggers the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane functional network element in the primary PLMN, thereby enabling the multicast/broadcast user plane functional network element of the primary PLMN to use the same serial number for data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device 800 may be a multicast/broadcast session management network element, or may be located in the multicast/broadcast session management network element.
  • the communication interface 801 is used to receive a session establishment request message from an application server, and the session establishment request message includes an identifier of a primary PLMN in the MOCN and identification information of a first multicast/broadcast service.
  • the processor 802 is used to send a multicast/broadcast service session context to a second session management network element through the communication interface 801, and the multicast/broadcast service session context includes an identifier of the primary PLMN and identification information of the first multicast/broadcast service.
  • the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used by the second multicast/broadcast session management network element to trigger the establishment of a shared transmission channel between the access network device of the MOCN and the multicast/broadcast user plane function network element corresponding to the identifier of the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can send the identification information of the primary PLMN and the identification information of the first multicast/broadcast service to the second session management network element, so that the second session management network element triggers the establishment of a shared transmission channel between the access network device in the MOCN and the multicast/broadcast user plane function network element in the primary PLMN, so that the multicast/broadcast user plane function network element of the primary PLMN uses the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device 800 may be a session management network element, or may be located in the session management network element.
  • the communication interface 801 is used to receive a multicast session request message from a terminal device, and the multicast session request message includes an identifier of a multicast session.
  • the processor 802 is used to send a multicast/broadcast service session context request message to a multicast/broadcast session management network element corresponding to the identifier of the multicast session through the communication interface 801 according to the identifier of the multicast session.
  • the communication interface 801 is also used to receive a multicast/broadcast service session context from the multicast/broadcast session management network element, and the multicast/broadcast service session context includes an identifier of a primary PLMN and identification information of a first multicast/broadcast service.
  • the identifier of the primary PLMN and the identification information of the first multicast/broadcast service are used to trigger the establishment of a shared transmission channel between the access network device to which the terminal device is connected and the multicast/broadcast user plane function network element corresponding to the identifier of the primary PLMN, and the shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can request the multicast/broadcast session management network element corresponding to the identifier of the multicast session to obtain the multicast/broadcast service session context, thereby obtaining the identifier of the primary PLMN and the identifier information of the first multicast/broadcast service, thereby triggering the establishment of a shared transmission channel between the access network device accessed by the terminal device and the multicast/broadcast user plane function network element corresponding to the identifier of the primary PLMN, which is conducive to making the multicast/broadcast user plane function network element of the primary PLMN use the same sequence number for the data of the same multicast/broadcast service, which is conducive to achieving data synchronization.
  • the apparatus 800 may be an access network device, or may be located in the access network device, specifically, the communication interface 801 is used to receive a first N2 protocol data unit session resource message from a first session management network element, the first N2 protocol data unit session resource message including an identifier of a primary PLMN in the MOCN and identification information of a first multicast/broadcast service, and the first access network device is located in the MOCN.
  • the processor 802 is used to send a first N2 multicast session request message to a multicast/broadcast session management network element in the primary PLMN through the communication interface 801, the first N2 multicast session request message including identification information of the first multicast/broadcast service.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can request the multicast/broadcast session management network element of the primary PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the primary PLMN based on the identifier of the primary PLMN, thereby facilitating the multicast/broadcast user plane function network element of the primary PLMN to use the same sequence number for the data of the same multicast/broadcast service, which is conducive to data synchronization.
  • the device 800 may be an access network device, or may be located in the access network device.
  • the communication interface 801 is used to receive identification information of the first multicast/broadcast service.
  • the processor 802 is used to send an Xn interface message to the second access network device through the communication interface 801, and the Xn interface message includes the identification information of the first multicast/broadcast service and the identification of the first public land mobile network PLMN.
  • the first PLMN is the PLMN to which the multicast/broadcast user plane functional network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the identification of the first PLMN and the identification information of the first multicast/broadcast service are used to trigger the establishment of a second shared transmission channel between the second access network device and the multicast/broadcast user plane functional network element in the first PLMN, and the second shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the specific execution process of the communication interface 801 and the processor 802 in this embodiment can also refer to the method executed by the communication unit in the embodiment of FIG. 7 and the description in the method embodiment above, which will not be repeated here.
  • the communication method implemented by the device enables access network devices located in the MOCN and having an Xn interface to exchange identification information of multicast/broadcast services and the identification of the PLMN to which they belong through the Xn interface. As a result, all access network devices in the MOCN with an Xn interface establish a shared transmission channel with the same multicast/broadcast user plane functional network element, which is conducive to data synchronization.
  • the device 800 may be an access network device, or may be located in the access network device.
  • the communication interface 801 is used to receive an Xn interface message from a first access network device, the Xn interface message including identification information of a first multicast/broadcast service and an identification of a first PLMN, the first PLMN being the PLMN to which a multicast/broadcast user plane functional network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the communication interface 801 is also used to receive identification information of a second multicast/broadcast service.
  • the processor 802 is used to establish a second shared transmission channel with a multicast/broadcast user plane functional network element in the first PLMN according to the identification of the first PLMN, the identification information of the first multicast/broadcast service, and the identification information of the second multicast/broadcast service, and the second shared transmission channel is used to transmit data of the first multicast/broadcast service and data of the second multicast/broadcast service.
  • the first access network device and the second access network device are located in an MOCN, and the first PLMN belongs to the MOCN.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device enables the second access network device located in the MOCN and having an Xn interface to receive the identification information of the multicast/broadcast service of other access network devices and the identification of the PLMN to which it belongs through the Xn interface, so that the access network devices in the MOCN with the Xn interface can establish a shared transmission channel with the multicast/broadcast user plane function network element in the PLMN, which is conducive to data synchronization.
  • the device 800 may be an access network device, or may be located in the access network device.
  • the processor 802 is used to send a switching request message to the second access network device through the communication interface 801, the switching request message including the identifier of the first PLMN in the MOCN and the identifier information of the first multicast/broadcast service, the first PLMN is the PLMN to which the multicast/broadcast user plane function network element that establishes the first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the communication interface 801 is also used to receive a switching response message from the second access network device, the switching response message including the identifier of the second PLMN, the second PLMN is the PLMN to which the multicast/broadcast user plane function network element that establishes the second shared transmission channel with the second access network device belongs; or the switching response message includes fourth indication information, the fourth indication information is used to indicate that the multicast/broadcast user plane function network element that establishes the second shared transmission channel with the second access network device belongs to the first PLMN.
  • the first access network device and the second access network device are located in the MOCN, and the first PLMN and the second PLMN are different.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can send the identifier of the first PLMN to which the first access network device belongs to the second access network device, which is conducive to the second access network device requesting the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN based on the identifier of the first PLMN, so that the data of the same multicast/broadcast service is transmitted through the same shared transmission channel, which is conducive to data synchronization.
  • the device 800 may be an access network device, or may be located in the access network device.
  • the communication interface 801 is used to receive a handover request message from the first access network device, the handover request message including an identifier of a first PLMN in the MOCN and identifier information of a first multicast/broadcast service, the first PLMN being the PLMN to which a multicast/broadcast user plane function network element that establishes a first shared transmission channel with the first access network device belongs, and the first shared transmission channel is used to transmit data of the first multicast/broadcast service.
  • the processor 802 is used to send a handover response message to the first access network device through the communication interface 801, the handover response message including an identifier of a second PLMN, the second PLMN being the PLMN to which a multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs; or the handover response message includes fourth indication information, the fourth indication information being used to indicate that the multicast/broadcast user plane function network element that establishes a second shared transmission channel with the second access network device belongs to the first PLMN.
  • the first access network device and the second access network device are located in the MOCN, and the first PLMN and the second PLMN are different.
  • the specific execution process of the communication interface 801 and the processor 802 in this implementation manner can also refer to the method executed by the communication unit and the processing unit in the embodiment of Figure 7, as well as the description in the previous method embodiment, which will not be repeated here.
  • the communication method implemented by the device can receive the identifier of the first PLMN to which the first access network device belongs, so that the second access network device requests the multicast/broadcast session management network element of the first PLMN to establish a shared transmission channel with the multicast/broadcast user plane function network element of the first PLMN based on the identifier of the first PLMN, so that the data of the same multicast/broadcast service is transmitted through the same shared transmission channel, which is conducive to data synchronization.
  • the device 800 may also include at least one memory 803 for storing program instructions and/or data.
  • the memory and the processor are coupled.
  • the coupling in this application is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other forms, for information exchange between devices, units or modules.
  • the processor may operate in conjunction with the memory.
  • the processor may execute program instructions stored in the memory.
  • the at least one memory and the processor are integrated together.
  • connection medium between the communication interface, processor and memory is not limited in this application.
  • the memory, processor and communication interface are connected via a bus, and the bus 804 is represented by a thick line in FIG8 .
  • the connection between other components is only for illustration.
  • the bus can be divided into an address bus, a data bus, a control bus, etc.
  • only one thick line is used in FIG8 , but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in this application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM).
  • the memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
  • the memory in the present application may also be a circuit or any other device that can realize a storage function, used to store program instructions and/or data.
  • the present application provides a communication device, which includes a processor, the processor is coupled to a memory, and the processor is used to read and execute computer instructions stored in the memory to implement the communication method in any one of the embodiments shown in Figures 3a to 6.
  • the present application provides a communication system, which includes one or more of the network elements or devices in any one of the embodiments shown in FIG. 3a to FIG. 6.
  • the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores a program or instruction.
  • the program or instruction is executed on a computer, the computer executes the communication method in any one of the embodiments shown in FIG. 3a to FIG. 6.
  • the present application provides a computer program product, which includes instructions.
  • the instructions When the instructions are executed on a computer, the computer executes the communication method in any one of the embodiments shown in FIG. 3a to FIG. 6 .
  • the present application provides a chip or a chip system, which includes at least one processor and an interface, the interface and the at least one processor are interconnected through lines, and the at least one processor is used to run a computer program or instruction to execute the communication method in any one of the embodiments shown in Figures 3a to 6.
  • the interface in the chip may be an input/output interface, a pin or a circuit, etc.
  • the above-mentioned chip system can be a system on chip (SOC) or a baseband chip, etc., wherein the baseband chip can include a processor, a channel encoder, a digital signal processor, a modem and an interface module, etc.
  • SOC system on chip
  • baseband chip can include a processor, a channel encoder, a digital signal processor, a modem and an interface module, etc.
  • the chip or chip system described above in the present application further includes at least one memory, in which instructions are stored.
  • the memory may be a storage unit inside the chip, such as a register, a cache, etc., or a storage unit of the chip (e.g., a read-only memory, a random access memory, etc.).
  • the technical solution provided in this application can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented by software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium, etc.
  • the various embodiments may reference each other, for example, the methods and/or terms between method embodiments may reference each other, for example, the functions and/or terms between device embodiments may reference each other, for example, the functions and/or terms between device embodiments and method embodiments may reference each other.

Landscapes

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

Abstract

本申请提供一种通信方法和通信装置，其中，第一多播/广播会话管理网元接收来自应用服务器的第一多播/广播业务的标识信息；第一多播/广播会话管理网元向对应的第一多播/广播用户面功能网元发送第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号。通过该方法，MOCN中的多播/广播会话管理网元可以指示对应的多播/广播用户面功能网元进行特殊的配置，从而使得MOCN中的多播/广播用户面功能网元可以同步更新相同多播/广播业务的数据的序列号，有利于实现相同多播/广播业务的数据的序列号在不同PLMN中同步。

Description

一种通信方法和通信装置
本申请要求在2022年12月8日提交中国国家知识产权局、申请号为202211572149.8的中国专利申请的优先权，发明名称为“一种通信方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法和通信装置。
背景技术
当前标准协议正在讨论不同运营商接入网设备如何共享接入网设备，主要聚焦在多运营商核心网(multi-operator core network，MOCN)共享接入网设备的网络优化方案。该网络优化方案可以让接入网设备识别不同运营商在请求建立广播会话时所针对的是同一个业务，从而进一步地，能够重用空口的资源(即，同一个业务不同运营商的会话使用同一份空口资源)，进而提高空口传输效率。
在MOCN共享接入网设备的网络优化方案中，假设该MOCN场景包括至少两个公共陆地移动网络(publiclandmobilenetwork，PLMN)和接入网设备，该接入网设备可以接入两个不同的PLMN，例如，PLMN a和PLMN b。进一步地，以多播业务为例，假设PLMN a使用MB-UPF a作为多播会话x的锚点，而PLMN b使用MB-UPF b作为多播会话y的锚点，多播会话x和y均用于传输该多播业务。MB-UPF a和MB-UPF b针对相同的多播业务数据可能生成不同的序列号，导致接入PLMN a和PLMN b的同一个接入网设备在从PLMN a和PLMN b接收到相同的多播业务数据时，该相同的多播业务数据对应的序列号却不相同，从而导致接入网设备对该相同的多播业务数据的序列号的认知产生混乱，进而影响了该多播业务的连续性。因此，如何保障MOCN场景下多播业务的连续性成为亟待解决的问题。
发明内容
本申请提供一种通信方法和通信装置，该方法可以实现MOCN场景下相同多播/广播业务的数据的序列号在不同PLMN中同步，实现数据传输的同步，进而保证了业务连续性。
第一方面，本申请提供第一种通信方法，该方法由多播/广播会话管理网元所执行，也可以由多播/广播会话管理网元的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分多播/广播会话管理网元功能的逻辑模块或软件实现。例如，由多运营商网络中的第一多播/广播会话管理网元所执行。其中，第一多播/广播会话管理网元接收来自应用服务器的第一会话建立请求消息，该第一会话建立请求消息包括第一多播/广播业务的标识信息；第一多播/广播会话管理网元根据该第一会话建立请求消息，向第一多播/广播用户面功能网元发送第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号；其中，第一多播/广播会话管理网元和第一多播/广播用户面功能网元位于多运营商核心网MOCN的第一公共陆地移动网络PLMN中。
该方法中，MOCN中的第一多播/广播会话管理网元可以指示对应的第一多播/广播用户面功能网元进行特殊的配置，例如，指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号(例如将第一序列号加1)。从而使得第一多播/广播用户面功能网元根据第一多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，有利于实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，第一会话建立请求消息还包括第一PLMN的标识；第一序列号用于MOCN中的接入网设备识别来自第一PLMN的第一多播/广播业务的数据。
该方法中，第一序列号可以被MOCN中不同的接入网设备(属于相同的PLMN或者不同的PLMN)识别；并且针对该第一多播/广播业务的数据，不同的接入网设备所识别的该数据的第一序列号是相同的，从而有利于实现数据同步。
一种可能的实施方式中，第一会话建立请求消息还包括该多播/广播业务的类型。当第一多播/广播业务的类型为多播业务时，第一多播/广播会话管理网元向第一多播/广播用户面功能网元发送第一指示信息。
该方法中，当多播/广播业务的类型为多播业务时，存在序列号无法对齐的场景(广播业务不识别具体的接入网设备和终端设备，因此不存在序列号无法对齐的问题)。若该第一会话建立请求消息包括多播/广播业务的类型为多播业务，则第一多播/广播会话管理网元向第一多播/广播用户面功能网元发送第一指示 信息，使得第一多播/广播用户面功能网元根据第一多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，有利于实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，第一会话建立请求消息还包括网络共享标识信息；该网络共享标识信息用于指示第一多播/广播业务在MOCN的第二PLMN的临时多播群组标识TMGI列表中共享，第二PLMN与第一PLMN不同。则第一多播/广播会话管理网元根据该网络共享标识信息，向第一多播/广播用户面功能网元发送第一指示信息。
该方法中，当第一多播/广播业务在MOCN的其他PLMN的TMGI列表中共享时，表示第一多播/广播业务可以发给MOCN中不同的接入网设备(属于相同的PLMN或者不同的PLMN)。则第一多播/广播会话管理网元向第一多播/广播用户面功能网元发送第一指示信息，使得第一多播/广播用户面功能网元根据第一多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，有利于实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
第二方面，本申请提供第二种通信方法，该方法由多播/广播会话管理网元所执行，也可以由多播/广播会话管理网元的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分多播/广播会话管理网元功能的逻辑模块或软件实现。例如，由多运营商网络中的第二多播/广播会话管理网元所执行。其中，第二多播/广播会话管理网元接收来自应用服务器的第二会话建立请求消息，该第二会话建立请求消息包括第一多播/广播业务的标识信息；第二多播/广播会话管理网元根据第二会话建立请求消息，向第二多播/广播用户面功能网元发送第二指示信息，该第二指示信息用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号；其中，第二多播/广播会话管理网元和第二多播/广播用户面功能网元位于多运营商核心网MOCN的第二公共陆地移动网络PLMN中。
该方法中，MOCN中的第二多播/广播会话管理网元可以指示对应的第二多播/广播用户面功能网元进行特殊的配置，例如，指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号(例如将第二序列号加1)。从而使得第二多播/广播用户面功能网元根据第二多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，从而实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，第二会话建立请求消息还包括第二PLMN的标识；第二序列号用于MOCN中的接入网设备识别来自第二PLMN的第一多播/广播业务的数据。
该方法中，第二序列号可以被MOCN中不同的接入网设备(属于相同的PLMN或者不同的PLMN)识别；并且针对该第一多播/广播业务的数据，不同的接入网设备所识别的该数据的第二序列号是相同的，从而有利于实现数据同步。
一种可能的实施方式中，第一指示信息包括第一序列号的起始值，第二指示信息包括第二序列号的起始值，第一序列号的起始值与第一多播/广播业务的数据在MOCN的第二PLMN中对应的第二序列号的起始值相同。
该方法中，假设不同PLMN针对相同多播/广播业务的数据，该数据的序列号的起始值都是相同的(例如从0开始依次递增)，从而有利于实现不同PLMN之间针对相同多播/广播业务的数据的序列号同步。
一种可能的实施方式中，第二会话建立请求消息还包括该多播/广播业务的类型。当第一多播/广播业务的类型为多播业务时，第二多播/广播会话管理网元向第二多播/广播用户面功能网元发送第一指示信息。
一种可能的实施方式中，第二会话建立请求消息还包括网络共享标识信息；该网络共享标识信息用于指示第一多播/广播业务在MOCN的第二PLMN的临时多播群组标识TMGI列表中共享，第二PLMN与第一PLMN不同。则第二多播/广播会话管理网元根据该网络共享标识信息，向第二多播/广播用户面功能网元发送第二指示信息。
第三方面，本申请提供第三种通信方法，该方法由多播/广播用户面功能网元所执行，也可以由多播/广播用户面功能网元的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分多播/广播用户面功能网元功能的逻辑模块或软件实现。例如，由多运营商网络中的第一多播/广播用户面功能网元所执行。其中，第一多播/广播用户面功能网元接收来自多播/广播会话管理网元的第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号；第一多播/广播用户面功能网元接收来自应用服务器的第一多播/广播业务的数据，并根据该第一指示信息，递增该数据对应的第一序列号。
该方法中，MOCN中的第一多播/广播用户面功能网元可以根据指示对用户面的处理进行特殊配置，例如，在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号，而不管是否会向接入网设备发 送该数据。从而使得第一多播/广播用户面功能网元可以同步更新相同多播/广播业务的数据的序列号，实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，第一多播/广播用户面功能网元向多运营商核心网MOCN中的接入网设备发送该第一多播/广播业务的数据以及该数据对应的所述第一序列号，第一多播/广播用户面功能网元位于MOCN的第一PLMN中，第一序列号用于该接入网设备识别来自第一PLMN的第一多播/广播业务的数据。
该方法中，第一多播/广播用户面网元可以向MOCN中不同的接入网设备(属于相同的PLMN或者不同的PLMN)发送第一序列号，并且针对该第一多播/广播业务的数据，不同的接入网设备所识别的该数据的第一序列号是相同的，从而有利于实现数据同步。
第四方面，本申请提供第四种通信方法，该方法由多播/广播用户面功能网元所执行，也可以由多播/广播用户面功能网元的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分多播/广播用户面功能网元功能的逻辑模块或软件实现。例如，由多运营商网络中的第二多播/广播用户面功能网元所执行。其中，第二多播/广播用户面功能网元接收来自第二多播/广播会话管理网元的第二指示信息，该第二指示信息用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时，递增该数据对应的第二序列号；第二多播/广播用户面功能网元接收来自应用服务器的第一多播/广播业务的数据，并且根据该第二指示信息，递增该数据对应的第二序列号。
该方法中，MOCN中的第二多播/广播用户面功能网元可以根据指示对用户面的处理进行特殊配置，例如，在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号，而不管是否会向接入网设备发送该数据。从而使得第二多播/广播用户面功能网元可以同步更新相同多播/广播业务的数据的序列号，实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，第二多播/广播用户面功能网元向MOCN中的接入网设备发送第一多播/广播业务的数据以及该数据对应的第二序列号，第二多播/广播用户面功能网元位于MOCN的第二PLMN中，第二序列号用于该接入网设备识别来自第二PLMN的第一多播/广播业务的数据。
该方法中，第二多播/广播用户面网元可以向MOCN中不同的接入网设备(属于相同的PLMN或者不同的PLMN)发送第二序列号，并且针对该第一多播/广播业务的数据，不同的接入网设备所识别的该数据的第二序列号是相同的，并且和第一序列号是对齐的，从而有利于实现数据同步。
第五方面，本申请提供第五种通信方法，该方法由应用服务器所执行，也可以由应用服务器的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分应用服务器功能的逻辑模块或软件实现。其中，应用服务器向位于MOCN的第一PLMN中的第一多播/广播会话管理网元发送第一会话建立请求消息，该第一会话建立请求消息包括第一多播/广播业务的标识信息；应用服务器向位于MOCN的第二PLMN中的第二多播/广播会话管理网元发送第二会话建立请求消息，该第二会话建立请求消息包括第一多播/广播业务的标识信息；其中，第一PLMN与第二PLMN不同。
该方法中，应用服务器可以向MOCN的不同PLMN中的多播/广播会话管理网元发送第一多播/广播业务的标识信息，不同PLMN中的多播/广播会话管理网元再向分别对应的多播/广播用户面功能网元发送指示信息，有利于使得不同PLMN中的多播/广播用户面功能网元同时接收来自应用服务器的第一多播/广播业务的数据，并同步更新针对该第一多播/广播业务的数据的序列号，从而有利于实现数据同步。
一种可能的实施方式中，第一会话请求消息还包括第一PLMN的标识和/或第一多播/广播业务的数据在第一PLMN中对应的第一序列号的起始值；第二会话请求消息还包括第二PLMN的标识和/或第一多播/广播业务的数据在第二PLMN中对应的第二序列号的起始值；其中，第一序列号的起始值与第二序列号的起始值相同。
该方法中，应用服务器还可以直接指示第一序列号的起始值和第二序列号的起始值，并且第一序列号的起始值和第二序列号的起始值相同，由于第一序列号和第二序列号更新的策略一致(例如只要接收数据，就将序列号加1)，则不同PLMN针对相同多播/广播业务的数据的序列号可以同步。
第六方面，本申请提供第六种通信方法，该方法由应用服务器所执行，也可以由应用服务器的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分应用服务器功能的逻辑模块或软件实现。其中，应用服务器生成会话建立请求消息，该会话建立请求消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息；应用服务器向多播/广播会话管理网元发送该会话建立请求消息。其中，该主PLMN的标识和该第一多播/广播业务的标识信息用于多播/广播会话管理网元触发建立MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输该第一多播/广播业务的数据。
一种可能的实施方式中，多播/广播会话管理网元位于主PLMN中，或者多播/广播会话管理网元位于MOCN中的除主PLMN之外的PLMN中。
上述方法中，应用服务器可以指定MOCN中的某一个PLMN作为主要PLMN(简称为主PLMN)，从而使得MOCN中的接入网设备都与该主PLMN的多播/广播用户面功能网元建立共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，从而实现了相同多播/广播业务的数据的序列号在不同PLMN中同步，有利于实现数据同步。
第七方面，本申请提供第七种通信方法，该方法由多播/广播会话管理网元所执行，也可以由多播/广播会话管理网元的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分多播/广播会话管理网元功能的逻辑模块或软件实现。例如，由多运营商网络中的第一多播/广播会话管理网元所执行。其中，第一多播/广播会话管理网元接收来自应用服务器的会话建立请求消息，该会话建立请求消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息；第一多播/广播会话管理网元向第一会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。其中，主PLMN的标识和第一多播/广播业务的标识信息用于该第一多播/广播会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
一种可能的实施方式中，第一多播/广播会话管理网元和第一会话管理网元位于主PLMN中。
上述方法中，当第一多播/广播会话管理网元对应的第一会话管理网元请求获取多播/广播业务会话上下文时，第一多播/广播会话管理网元可以向该第一会话管理网元发送主PLMN的标识和第一多播/广播业务的标识信息，以使该第一会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，从而实现了相同多播/广播业务的数据的序列号在不同PLMN中同步，有利于实现数据同步。
第八方面，本申请提供第八种通信方法，该方法由多播/广播会话管理网元所执行，也可以由多播/广播会话管理网元的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分多播/广播会话管理网元功能的逻辑模块或软件实现。例如，由多运营商网络中的第二多播/广播会话管理网元所执行。其中，第二多播/广播会话管理网元接收来自应用服务器的会话建立请求消息，该会话建立请求消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息；第二多播/广播会话管理网元向第二会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。该主PLMN的标识和第一多播/广播业务的标识信息用于该第二多播/广播会话管理网元触发建立该MOCN的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
一种可能的实施方式中，第二多播/广播会话管理网元和第二会话管理网元位于该MOCN中除主PLMN之外的PLMN中。
上述方法中，当第二多播/广播会话管理网元对应的第二会话管理网元请求获取多播/广播业务会话上下文时，第二多播/广播会话管理网元可以向该第二会话管理网元发送主PLMN的标识和第一多播/广播业务的标识信息，以使该第二会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，从而实现了相同多播/广播业务的数据的序列号在不同PLMN中同步，有利于实现数据同步。
第九方面，本申请提供第九种通信方法，该方法由会话管理网元所执行，也可以由会话管理网元的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分会话管理网元功能的逻辑模块或软件实现。例如，由第二PLMN中的第二会话管理网元所执行。其中，第二会话管理网元接收来自终端设备的多播会话请求消息，该多播会话请求消息包括多播会话的标识；第二会话管理网元根据该多播会话的标识，向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息；第二会话管理网元接收来自多播/广播会话管理网元的多播/广播业务会话上下文，该多播/广播业务会话上下文包括主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息。其中，主PLMN的标识和第一多播/广播业务的标识信息用于触发建立该终端设备所接入的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
一种可能的实施方式中，第二会话管理网元向多运营商核心网中的接入网设备发送该主PLMN的标识 和第一多播/广播业务的标识信息。
上述方法中，当第二会话管理网元收到终端设备的多播会话请求消息时，可以向多播会话的标识对应的多播/广播会话管理网元请求获取多播/广播业务会话上下文，从而获取主PLMN的标识和第一多播/广播业务的标识信息，从而触发建立该终端设备所接入的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，从而实现了相同多播/广播业务的数据的序列号在不同PLMN中同步，有利于实现数据同步。
第十方面，本申请提供第十种通信方法，该方法由接入网设备所执行，也可以由接入网设备的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分接入网设备功能的逻辑模块或软件实现。例如，由第一接入网设备所执行。其中，第一接入网设备接收来自第一会话管理网元的第一N2协议数据单元会话资源消息，该第一N2协议数据单元会话资源消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息，该第一接入网设备位于该MOCN中；第一接入网设备向主PLMN中的多播/广播会话管理网元发送第一N2多播会话请求消息，该第一N2多播会话请求消息包括第一多播/广播业务的标识信息。
该方法中，接入网设备可以基于主PLMN的标识，向主PLMN的多播/广播会话管理网元请求建立与该主PLMN的多播/广播用户面功能网元之间的共享传输通道，从而有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，从而实现了相同多播/广播业务的数据的序列号在不同PLMN中同步，有利于实现数据同步。
一种可能的实施方式中，当第一接入网设备未建立共享传输通道时，第一接入网设备向主PLMN中的多播/广播会话管理网元发送第一多播/广播业务的标识信息；第一接入网设备建立与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
该方法中，假设第一接入网设备未建立共享传输通道，则第一接入网设备可以基于主PLMN的标识，向主PLMN的多播/广播会话管理网元请求建立与该主PLMN的多播/广播用户面功能网元之间的共享传输通道，从而有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，第一接入网设备接收来自第二会话管理网元的第二N2协议数据单元会话资源消息，该第二N2协议数据单元会话资源消息包括主PLMN的标识和第一多播/广播业务的标识信息；当第一接入网设备已建立共享传输通道时，第一接入网设备丢弃该第二N2协议数据单元会话资源消息；或者，第一接入网设备向第二会话管理网元发送第三指示信息，该第三指示信息用于指示该共享传输通道已建立。其中，第一会话管理网元位于主PLMN中，第二会话管理网元位于该MOCN中的除主PLMN之外的PLMN中；或者，第一会话管理网元位于该MOCN中的除主PLMN之外的PLMN中，第二会话管理网元位于该主PLMN中。
该方法中，假设第一接入网设备已建立共享传输通道，则第一接入网设备可能丢弃主PLMN的标识和第一多播/广播业务的标识信息，或者，向第二PLMN中的第二会话管理网元发送第三指示信息，该第三指示信息用于指示该共享传输通道已建立。也即是，若第一接入网设备不能被该MOCN的所有PLMN共享时，第一接入网设备可以不使用主PLMN的标识，而是自行建立共享传输通道。
一种可能的实施方式中，第一接入网设备向第二接入网设备发送切换请求消息，该切换请求消息包括主PLMN的标识和第一多播/广播业务的标识信息；该主PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与该主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
该方法中，若属于第一接入网设备的终端设备需要切换至第二接入网设备，则第一接入网设备可以向第二接入网设备发送主PLMN的标识，有利于使第二接入网设备基于主PLMN的标识，向主PLMN的多播/广播会话管理网元请求建立与该主PLMN的多播/广播用户面功能网元之间的共享传输通道，从而有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
第十一方面，本申请提供第十一种通信方法，该方法由接入网设备所执行，也可以由接入网设备的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分接入网设备功能的逻辑模块或软件实现。例如，由第一接入网设备所执行。其中，第一接入网设备接收第一多播/广播业务的标识信息；第一接入网设备向第二接入网设备发送Xn接口消息，该Xn接口消息包括第一多播/广播业务的标识信息 以及第一公共陆地移动网络PLMN的标识，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。其中，第一PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据。
一种可能的实施方式中，第一接入网设备和第二接入网设备位于多运营商核心网MOCN中，且第一PLMN属于该MOCN。
上述方法中，位于MOCN中并且有Xn接口的接入网设备之间，可以通过Xn接***互多播/广播业务的标识信息以及所属PLMN的标识，从而使得在有Xn接口的MOCN中的接入网设备都与相同的多播/广播用户面功能网元建立共享传输通道，有利于实现数据同步。
第十二方面，本申请提供第十二种通信方法，该方法由接入网设备所执行，也可以由接入网设备的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分接入网设备功能的逻辑模块或软件实现。例如，由第二接入网设备所执行。其中，第二接入网设备接收来自第一接入网设备的Xn接口消息，该Xn接口消息包括第一多播/广播业务的标识信息，以及第一公共陆地移动网络PLMN的标识，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输所述第一多播/广播业务的数据；第二接入网设备接收第二多播/广播业务的标识信息，并根据该第一PLMN的标识、该第一多播/广播业务的标识信息和该第二多播/广播业务的标识信息，建立与该第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据和第二多播/广播业务的数据。其中，第一接入网设备和第二接入网设备位于MOCN中，且第一PLMN属于MOCN。
该方法中，位于MOCN中并且有Xn接口的第二接入网设备可以通过Xn接口接收其他接入网设备的多播/广播业务的标识信息以及所属PLMN的标识，从而使得在有Xn接口的MOCN中的接入网设备都可以与该PLMN中的多播/广播用户面功能网元建立共享传输通道，有利于实现数据同步。
一种可能的实施方式中，当第一多播/广播业务和第二多播/广播业务的类型相同时，第二接入网设备向第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息；或者，当第一多播/广播业务的标识信息对应的多播网络地址与第二多播/广播业务的标识信息对应的多播网络地址相同时，第二接入网设备向第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息。
该方法中，当第二接入网设备的第二多播/广播业务与第一接入网设备的第一多播/广播业务相同时，且针对该相同的多播/广播业务第一接入网设备已建立共享传输通道，则第二接入网设备将尝试建立到第一PLMN的共享传输通道，有利于实现数据同步。
第十三方面，本申请提供第十三种通信方法，该方法由接入网设备所执行，也可以由接入网设备的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分接入网设备功能的逻辑模块或软件实现。例如，由第一接入网设备所执行。其中，第一接入网设备向第二接入网设备发送切换请求消息，该切换请求消息包括多运营商核心网MOCN中第一公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。第一接入网设备接收来自第二接入网设备的切换响应消息，该切换响应消息包括第二PLMN的标识，该第二PLMN为与所述第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，该切换响应消息包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN；其中，第一接入网设备和第二接入网设备位于MOCN中，第一PLMN和第二PLMN不同。
该方法中，若属于第一接入网设备的终端设备需要切换至第二接入网设备，则第一接入网设备可以向第二接入网设备发送第一接入网设备所属的第一PLMN的标识，有利于使第二接入网设备基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
一种可能的实施方式中，第一接入网设备根据第二PLMN的标识或第四指示信息，向所述第二接入网设备转发所述第一多播/广播业务的数据。
该方法中，若第二接入网设备向第一接入网设备反馈其已建立与其他PLMN中的多播/广播用户面功能网元之间的共享传输通道，则第一接入网设备可以在一定时间内(例如基于定时器等)，向第二接入网设备传输部分第一接入网设备当前正在发送的该多播/广播业务的数据，这样可以部分缓解丢包的问题。
一种可能的实施方式中，第一接入网设备接收第一N2协议数据单元会话资源消息，该第一N2协议数据单元会话资源消息包括第一PLMN的标识和第一多播/广播业务的标识信息；第一接入网设备根据该第一PLMN的标识和第一多播/广播业务的标识信息，建立与第一PLMN中的多播/广播用户面功能网元之间的第一共享传输通道。
该方法中，第一接入网设备可以基于第一PLMN的标识和第一多播/广播业务的标识信息，向该第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而有利于使得该第一PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，切换请求消息用于请求将终端设备从第一接入网设备切换至第二接入网设备，该切换请求消息还包括终端设备所属的PLMN的标识。
该方法中，第一接入网设备还可以向第二接入网设备发送终端设备所属的PLMN的标识，有利于使第二接入网设备将终端设备所属的PLMN的多播/广播用户面功能网元作为建立共享传输通道的次优选择。
第十四方面，本申请提供第十四种通信方法，该方法由接入网设备所执行，也可以由接入网设备的部件(例如处理器、芯片、或芯片***等)执行，还可以由能实现全部或部分接入网设备功能的逻辑模块或软件实现。例如，由第二接入网设备所执行。其中，第二接入网设备接收来自第一接入网设备的切换请求消息，该切换请求消息包括多运营商核心网MOCN中第一公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。第二接入网设备向第一接入网设备发送切换响应消息，该切换响应消息包括第二PLMN的标识，第二PLMN为与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，该切换响应消息包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN；其中，第一接入网设备和第二接入网设备位于该MOCN中，第一PLMN和第二PLMN不同。
该方法中，若属于第一接入网设备的终端设备需要切换至第二接入网设备，则第二接入网设备可以接收第一接入网设备所属的第一PLMN的标识，使得第二接入网设备基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
一种可能的实施方式中，当第二接入网设备未建立用于传输第一多播/广播业务的数据的第二共享传输通道时，第二接入网设备根据第一PLMN的标识和第一多播/广播业务的标识信息，建立与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道。
该方法中，若第二接入网设备未建立用于传输相同多播/广播业务的数据的共享传输通道时，第二接入网设备可以尝试与第一PLMN中的多播/广播用户面功能网元建立共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
一种可能的实施方式中，当第二接入网设备已建立用于传输第一多播/广播业务的数据的第二共享传输通道时，切换响应消息包括第二共享传输通道对应的PLMN的标识，或者，切换响应消息包括所述第四指示信息。
一种可能的实施方式中，当第二共享传输通道对应的PLMN的标识与第一PLMN的标识不同时，第二接入网设备接收来自述第一接入网设备的第一多播/广播业务的数据；第二接入网设备使用单播方式转发该第一多播/广播业务的数据。
该方法中，若第二接入网设备向第一接入网设备反馈其已建立与其他PLMN中的多播/广播用户面功能网元之间的共享传输通道，则第二接入网设备可以在一定时间内(例如基于定时器等)接收部分第一接入网设备当前正在发送的该多播/广播业务的数据，这样可以部分缓解丢包的问题。
一种可能的实施方式中，切换请求消息用于请求将终端设备从第一接入网设备切换至第二接入网设备，该切换请求消息还包括终端设备所属的PLMN的标识。
该方法中，第二接入网设备还可以接收终端设备所属的PLMN的标识，使得第二接入网设备可以将终端设备所属的PLMN的多播/广播用户面功能网元作为建立共享传输通道的次优选择。
一种可能的实施方式中，第二接入网设备根据第一PLMN的标识，或所述第二PLMN的标识，或所述终端设备所属的PLMN的标识，建立第二共享传输通道。
第十五方面，本申请提供第十五种通信方法，该方法由多播/广播会话管理网元、多播/广播用户面功能网元、应用服务器之间的交互实现。其中，应用服务器向位于多运营商核心网MOCN的第一公共陆地 移动网络PLMN中的第一多播/广播会话管理网元发送第一会话建立请求消息，该第一会话建立请求消息包括第一多播/广播业务的标识信息；应用服务器向位于该MOCN的第二PLMN中的第二多播/广播会话管理网元发送第二会话建立请求消息，该第二会话建立请求消息包括第一多播/广播业务的标识信息。第一多播/广播会话管理网元根据该第一会话建立请求消息，向第一多播/广播用户面功能网元发送第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号；其中，第一多播/广播会话管理网元和第一多播/广播用户面功能网元位于第一PLMN中。第二多播/广播会话管理网元根据该第二会话建立请求消息，向第二多播/广播用户面功能网元发送第二指示信息，该第二指示信息用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号；其中，第二多播/广播会话管理网元和第二多播/广播用户面功能网元位于第二PLMN中。应用服务器向第一多播/广播用户面功能网元和第二多播/广播用户面功能网元发送第一多播/广播业务的数据。第一多播/广播用户面功能网元根据该第一指示信息，递增该第一多播/广播业务的数据对应的第一序列号。第二多播/广播用户面功能网元根据该第二指示信息，递增该第一多播/广播业务的数据对应的第二序列号。
该方法中，应用服务器可以预先请求MOCN中的多个PLMN进行特殊的用户面配置，使得每个PLMN均会同步更新相同多播/广播业务的数据的序列号(例如收到该数据就更新该数据的序列号)，从而使得不同多播/广播用户面功能网元对于相同的多播/广播业务的数据设置相同的序列号，有利于实现数据的同步。
一种可能的实施方式中，多播/广播会话管理网元、多播/广播用户面功能网元、应用服务器之间交互的步骤还可以参考第一方面至第五方面，以及第一方面至第五方面中任一种可能的实施方式中的描述，此处不再赘述。
第十六方面，本申请提供第十六种通信方法，该方法由多播/广播会话管理网元、多播/广播用户面功能网元、会话管理网元、应用服务器、接入网设备之间的交互实现。其中，应用服务器生成会话建立请求消息，该会话建立请求消息包括多运营商核心网MOCN中主PLMN的标识和第一多播/广播业务的标识信息。应用服务器向第一多播/广播会话管理网元和第二多播/广播会话管理网元分别发送该会话建立请求消息。第一多播/广播会话管理网元向第一会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息；该主PLMN的标识和第一多播/广播业务的标识信息用于第一多播/广播会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。其中，第一多播/广播会话管理网元和第一会话管理网元位于主PLMN中。第二多播/广播会话管理网元向第二会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息；该主PLMN的标识和多播/广播业务的标识信息用于第二多播/广播会话管理网元触发建立MOCN的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输该第一多播/广播业务的数据；其中，第二多播/广播会话管理网元和第二会话管理网元位于MOCN中除主PLMN之外的PLMN中。第二会话管理网元接收来自终端设备的多播会话请求消息，该多播会话请求消息包括多播会话的标识；第二会话管理网元根据该多播会话的标识，向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息。第二会话管理网元接收来自该多播/广播会话管理网元的多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息；第二会话管理网元向MOCN中的第一接入网设备发送该主PLMN的标识和第一多播/广播业务的标识信息。MOCN中的第一接入网设备接收该主PLMN的标识和所述第一多播/广播业务的标识信息；第一接入网设备向主PLMN中的多播/广播会话管理网元发送N2多播会话请求消息。
该方法中，通过增强MOCN中的接入网设备的共享传输通道建立流程，使得MOCN中的接入网设备均与主PLMN的多播/广播用户面功能网元建立共享传输通道，从而避免了多个多播/广播用户面功能网元产生不同序列号的情况，有利于实现数据的同步。
一种可能的实施方式中，多播/广播会话管理网元、多播/广播用户面功能网元、应用服务器、接入网设备之间交互的步骤还可以参考第六方面至第十方面，以及第六方面至第十方面中任一种可能的实施方式中的描述，此处不再赘述。
第十七方面，本申请提供第十七种通信方法，该方法由MOCN中存在Xn接口的多个接入网设备之间的交互实现。其中，第一接入网设备接收第一多播/广播业务的标识信息；第一接入网设备向第二接入网设备发送Xn接口消息，该Xn接口消息包括该第一多播/广播业务的标识信息以及第一公共陆地移动网络PLMN的标识，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所 属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据；其中，第一PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据；其中，第一接入网设备和第二接入网设备位于多运营商核心网MOCN中，且第一PLMN属于MOCN。第二接入网设备接收第二多播/广播业务的标识信息；第二接入网设备根据第一PLMN的标识、第一多播/广播业务的标识信息和第二多播/广播业务的标识信息，建立与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据和第二多播/广播业务的数据；其中，第一接入网设备和第二接入网设备位于MOCN中。
该方法中，MOCN中存在Xn接口的多个接入网设备之间，可以与相同的多播/广播用户面功能网元建立共享传输通道，有利于实现的同步。
一种可能的实施方式中，MOCN中的多播/广播会话管理网元、多播/广播用户面功能网元、接入网设备之间交互的步骤还可以参考第十一方面和第十二方面，以及第十一方面和第十二方面中任一种可能的实施方式中的描述，此处不再赘述。
第十八方面，本申请提供第十八种通信方法，该方法由MOCN中的多个接入网设备之间的交互实现。其中，第一接入网设备向第二接入网设备发送切换请求消息，该切换请求消息包括多运营商核心网MOCN中第一公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输所述第一多播/广播业务的数据。第二接入网设备向第一接入网设备发送切换响应消息，该切换响应消息包括第二PLMN的标识，该第二PLMN为与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，该切换响应消息包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN；其中，第一接入网设备和第二接入网设备位于MOCN中，第一PLMN和第二PLMN不同。
该方法中，若属于第一接入网设备的终端设备需要切换至第二接入网设备，则第一接入网设备可以向第二接入网设备发送第一接入网设备所属的第一PLMN的标识，有利于使第二接入网设备基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
一种可能的实施方式中，第一接入网设备和第二接入网设备之间交互的步骤还可以参考第十三方面和第十四方面，以及第十三方面和第十四方面中任一种可能的实施方式中的描述，此处不再赘述。
第十九方面，本申请提供第一种通信装置，该通信装置可以是多播/广播会话管理网元，也可以是多播/广播会话管理网元中的装置，或者是能够和多播/广播会话管理网元匹配使用的装置。一种可能的实施方式中，该通信装置可以包括执行如第一方面、第二方面、第七方面、第八方面，以及第一方面、第二方面、第七方面、第八方面中任一种可能的实施方式中描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可以是软件，也可以是硬件电路结合软件实现。一种可能的实施方式中，该通信装置可以包括处理单元和通信单元。
其中，对多播/广播会话管理网元执行的方法的具体描述可以参考上述第一方面、第二方面、第七方面、第八方面，以及第一方面、第二方面、第七方面、第八方面中任一种可能的实施方式中对应的描述，此处不再赘述。可以理解的是，该通信装置也可以实现如第一方面、第二方面、第七方面、第八方面，以及第一方面、第二方面、第七方面、第八方面中任一种可能的实施方式中可以实现的效果。
第二十方面，本申请提供第二种通信装置，该通信装置可以是多播/广播用户面功能网元，也可以是多播/广播用户面功能网元中的装置，或者是能够和多播/广播用户面功能网元匹配使用的装置。一种可能的实施方式中，该通信装置可以包括执行如第三方面和第四方面，以及第三方面和第四方面中任一种可能的实施方式中描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可以是软件，也可以是硬件电路结合软件实现。一种可能的实施方式中，该通信装置可以包括处理单元和通信单元。
其中，对多播/广播用户面功能网元执行的方法的具体描述可以参考上述第三方面和第四方面，以及第三方面和第四方面中任一种可能的实施方式中对应的描述，此处不再赘述。可以理解的是，该通信装置也可以实现如第三方面和第四方面，以及第三方面和第四方面中任一种可能的实施方式中可以实现的效果。
第二十一方面，本申请提供第三种通信装置，该通信装置可以是应用服务器，也可以是应用服务器中的装置，或者是能够和应用服务器匹配使用的装置。一种可能的实施方式中，该通信装置可以包括执行如 第五方面和第六方面，以及第五方面和第六方面中任一种可能的实施方式中描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可以是软件，也可以是硬件电路结合软件实现。一种可能的实施方式中，该通信装置可以包括处理单元和通信单元。
其中，对应用服务器执行的方法的具体描述可以参考上述第五方面和第六方面，以及第五方面和第六方面中任一种可能的实施方式中对应的描述，此处不再赘述。可以理解的是，该通信装置也可以实现如第五方面和第六方面，以及第五方面和第六方面中任一种可能的实施方式中可以实现的效果。
第二十二方面，本申请提供第四种通信装置，该通信装置可以是会话管理网元，也可以是会话管理网元中的装置，或者是能够和会话管理网元匹配使用的装置。一种可能的实施方式中，该通信装置可以包括执行如第九方面以及第九方面中任一种可能的实施方式中描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可以是软件，也可以是硬件电路结合软件实现。一种可能的实施方式中，该通信装置可以包括处理单元和通信单元。
其中，对会话管理网元执行的方法的具体描述可以参考上述第九方面以及第九方面中任一种可能的实施方式中对应的描述，此处不再赘述。可以理解的是，该通信装置也可以实现如第九方面以及第九方面中任一种可能的实施方式中可以实现的效果。
第二十三方面，本申请提供第五种通信装置，该通信装置可以是接入网设备，也可以是接入网设备中的装置，或者是能够和接入网设备匹配使用的装置。一种可能的实施方式中，该通信装置可以包括执行如第十方面至第十四方面，以及第十方面至第十四方面中任一种可能的实施方式中描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可以是软件，也可以是硬件电路结合软件实现。一种可能的实施方式中，该通信装置可以包括处理单元和通信单元。
可以理解的是，该通信装置也可以实现如第十方面至第十四方面，以及第十方面至第十四方面中任一种可能的实施方式中可以实现的效果。
第二十四方面，本申请提供一种通信装置，包括：处理器和存储器，该存储器用于存储指令，当指令被处理器执行时，使得该通信设备实现上述第一方面至第十四方面，以及第一方面至第十四方面中任一种可能的实施方式中的方法。可选的，该处理器和存储器耦合。
第二十五方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质上存储指令，当所述指令在计算机上运行时，使得计算机执行第一方面至第十四方面，以及第一方面至第十四方面中任一种可能的实施方式中的方法。
第二十六方面，本申请提供一种芯片***，该芯片***包括处理器和接口，还可以包括存储器，用于实现上述第一方面至第十四方面，以及第一方面至第十四方面中任一种可能的实施方式中的方法。该芯片***可以由芯片构成，也可以包含芯片和其他分立器件。
第二十七方面，本申请提供一种计算机程序产品，包括指令，当所述指令在计算机上运行时，使得计算机执行第一方面至第十四方面，以及第一方面至第十四方面中任一种可能的实施方式中的方法。
第二十八方面，本申请提供一种通信***，该通信***可以包括上述第十九方面至第二十四方面中描述的一个或多个通信装置，实现第一方面至第十四方面，以及第一方面至第十四方面中任一种可能的实施方式中的方法。
附图说明
图1为一种通信***的示意图；
图2为一种MOCN中不同PLMN共享接入网设备的示意图；
图3a和图3b为本申请提供的一种通信方法的流程示意图；
图4为本申请提供的另一种通信方法的流程示意图；
图5为本申请提供的另一种通信方法的流程示意图；
图6为本申请提供的另一种通信方法的流程示意图；
图7为本申请提供的一种通信装置的示意图；
图8为本申请提供的另一种通信装置的示意图。
具体实施方式
在本申请中，“/”可以表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；“和/或”可以用于描述关联对象存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。为了便于描述本申请的技术方案，在本申请中， 可以采用“第一”、“第二”等字样对功能相同或相似的技术特征进行区分。该“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。在本申请中，“示例性的”或者“例如”等词用于表示例子、例证或说明，被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
下面将结合本申请中的附图，对本申请中的技术方案进行描述。
为了解决不同多播/广播用户面功能网元针对相同的多播业务生成不同的序列号，从而导致接入网设备对数据的序列号的认知产生混乱的问题；以及当数据的序列号无法同步，如何尽量保障多运营商核心网场景下多播的业务连续性的问题，本申请提供了多种通信方法，该方法可以实现多运营商核心网场景下不同接入网设备的序列号同步，实现数据传输的同步。
其中，本申请提供的通信方法可以应用于通信***中，具体来说，可以应用于多运营商核心网(multi-operator core network，MOCN)***中。例如，应用于图1所示的通信***。
图1为一种通信***的示意图，该通信***包括无线接入网和MOCN两部分。其中，无线接入网用于实现无线接入相关的功能。MOCN主要包括以下几个关键逻辑网元：多播/广播会话管理网元(multicast/broadcast-session management function，MB-SMF)、多播/广播用户面功能网元(multicast/broadcast-user plane function，MB-UPF)、应用服务器(application server，AS)。可选的，该通信***还包括图1中未示出的网元，例如接入和移动管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、用户面功能(user plane function，UPF)、策略控制功能(policy control function，PCF)、统一数据管理(unified data management，UDM)网元、网络存储功能(network repository function，NRF)等，本申请不作限定。本申请中的应用服务器也可以称为应用功能(application function)网元。
本申请提及的通信***包括但不限于：窄带物联网***(narrow band-Internet of things，NB-IoT)、全球移动通信***(global system for mobile communications，GSM)、增强型数据速率GSM演进***(enhanced data rate for GSM evolution，EDGE)、宽带码分多址***(wideband code division multiple access，WCDMA)、码分多址2000***(code division multiple access，CDMA2000)、时分同步码分多址***(time division-synchronization code division multiple access，TD-SCDMA)，长期演进***(long term evolution，LTE)以及5G移动通信***的三大应用场景增强移动宽带(enhanced mobility broad band，eMBB)，超高可靠与低时延通信(ultra-reliable and low latency communications，URLLC)和增强型机器类通信(enhanced machine-type communication，eMTC)以及未来的通信***(例如6G/7G等)。
终端设备，又称之为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是指向用户提供语音和/或数据连通性的设备。例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端设备的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，无人机、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、5G网络中的终端设备、未来演进的公共陆地移动网络(publiclandmobilenetwork，PLMN)中的终端设备或未来的通信***中的终端设备等。
接入网设备是指将终端设备接入到无线网络的无线接入网(radio access network，RAN)节点(或设备)，又可以称为基站。也即是，本申请中的卫星可以将终端设备接入到RAN，也可以称为卫星基站。例如，一些RAN节点的举例为：继续演进的节点B(gNB)、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)、卫星通信***中的卫星、云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、可穿戴设备、无人机、或者车联网中的设备(例如车联万物设备(vehicle to everything，V2X))，或者设备间(device to device，D2D)通信中的通信设备等。另外，在一种网络结构中，接入网设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。其中包括CU节点和DU节点的RAN设备将 长期演进(long term evolution，LTE)***中eNB的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
其中，MB-SMF与SMF的功能类似，主要负责移动网络中的会话管理，如会话建立、修改、释放，例如为用户分配IP地址、选择提供报文转发功能的UPF等。MB-UPF与UPF的功能类似，主要负责对用户报文进行处理，如转发、计费等。
一、本申请涉及的相关概念：
1、MOCN的场景：
当前标准协议正在讨论不同运营商网络共享基站，主要聚焦在多运营商核心网(multi-operator core network，MOCN)网络共享的网络优化方案。例如，图2为一种MOCN中不同PLMN共享接入网设备的示意图。该MOCN中示出了终端设备、接入网设备和PLMN，可选的，其他未示出的设备或网元可以参考现有MOCN的具体示例，本申请不作限定。假设存在两个PLMN(如图2中的PLMN a和PLMN b)，PLMN a和PLMN b拥有共同的接入网设备(如图2中的下一代无线接入网(nextgenerationradioaccessnetwork，NG-RAN))。目前对于该NG-RAN而言，当PLMN a和PLMN b分别向该NG-RAN发送相同的多播/广播业务的数据时，该NG-RAN需要在空口发送两份数据，将造成空口资源的浪费。本申请提供的通信方法可以让接入网设备识别不同运营商在请求建立多播/广播会话时，针对的是同一个业务，从而能够重用空口的资源(即，同一个业务不同运营商的会话使用同一份空口资源)，进而提高空口传输效率。
2、基于单播的多播技术：
基于单播的多播技术旨在解决：如何在尽量重用现有单播流程的基础之上，进一步节约网络资源。其中，多播技术也可以称为组播技术。例如，用户面功能网元针对发给群组内不同终端设备的相同业务的数据流，只发送一份(例如从UPF发送至接入网)，从而提高空口资源和核心网资源的使用效率。例如，一种基于单播的多播技术的加入流程包括以下步骤：
步骤1：终端设备向SMF发送加入请求消息。例如，UE通过非接入层(non-access stratum，NAS)消息(如协议数据单元(protocol data unit，PDU)会话修改请求，或者PDU会话建立请求)，或用户面的加入请求消息(如因特网组管理协议加入(Internet group management protocol join，IGMPJoin)消息)。该加入请求消息包含多播的群组信息(也可以称为多播的会话信息，多播会话用于发送多播的群组对应的数据)。
步骤2：在接收到终端设备的加入请求消息后，SMF获取多播的信息。例如，SMF可以根据多播的群组信息/多播的会话信息，从MB-SMF或UDR处获取多播的信息，并且根据该多播的信息，生成多播对应的多播上下文信息。可选地，SMF还可以生成多播对应的单播的服务质量流(quality of serviceflow，QoS Flow)的信息。
步骤3：SMF向接入网设备发送请求消息，该请求消息中包含步骤2中生成的信息。
步骤4：接入网设备根据SMF的请求消息，建立或修改多播对应的多播上下文信息。可选的，接入网设备还可以进一步地建立单播上下文信息。
3、多播方案的业务连续性机制：
目前，针对PLMN的多播会话，其锚点(如MB-UPF)仅有一个。MB-UPF在发送下行多播数据时会***序列号(sequence number，SN)，由于仅有一个MB-UPF，因此PLMN内所有的接入网设备对于序列号有相同的理解(相同序列号对应的数据相同)。然后不同的接入网设备会根据多播数据的序列号产生分组数据汇聚协议(packet data convergence protocol，PDCP)序列号，并通过空口发送数据。
可选的，若存在终端设备需要从源接入网设备(简称为S-RAN)切换至目标接入网设备(简称为T-RAN)，则在切换阶段，当S-RAN和T-RAN都支持多播/广播业务(multicast and broadcast service，MBS)时，S-RAN与T-RAN会交互信息(例如交互SN序列号和/或PDCP序列号)，S-RAN会根据T-RAN提供SN序列号决定何时停止转发。例如，当转发到某个SN序列号时，S-RAN将停止转发数据。
二、本申请提供的通信方法：
示例一：图3a和图3b为本申请提供的一种通信方法的流程示意图。该通信方法应用于如图1所示的通信***中。例如，该通信方法可以由应用服务器、多播/广播会话管理网元、多播/广播用户面功能网元之间的交互实现，包括以下步骤：
S101，应用服务器向位于MOCN的第一PLMN中的第一多播/广播会话管理网元发送第一会话建立请求消息。
此处，位于MOCN的第一PLMN可以指，第一PLMN与其他PLMN均连接到某个或某些接入网设备。例如，本申请中的MOCN网络共享架构中，仅共享RAN。面向5G***的5G MOCN(包括UE、RAN和AMF)，支持运营商使用多个PLMN ID的能力。
其中，第一会话建立请求消息可以包括第一多播/广播业务的标识信息。
其中，多播/广播业务的标识信息用于标识多播/广播业务。具体地，多播/广播业务的标识信息用于用全球唯一标识该多播/广播业务，例如，在不同PLMN中均可以通过该标识识别出该业务。例如，多播/广播业务的标识信息可以是关联的会话标识(associated session identifier)，关联的会话标识使得共享的NG-RAN节点可以确定多个MBS会话正在发送相同MBS服务的相同内容。其中，关联的会话标识可以是特定源的多播地址(source specific multicast address，SSM)。又例如，多播/广播业务的标识信息可以是临时多播群组标识(temporary multicast group identifier，TMGI)列表，表示该多播/广播业务在TMGI列表中共享。
可选的，MOCN标识(简称为MOCN ID)用于标识MOCN。其中，MOCN ID可以是IP多播地址。
可选的，该第一会话建立请求消息还包括但不限于以下一项或多项信息：第一多播/广播业务的类型、多播会话的标识信息、或PLMN的标识等。
其中，多播/广播业务的类型用于指示上述第一多播/广播业务的类型，例如，多播业务或广播业务。进一步地，当第一多播/广播业务的类型为多播业务时，则表示该第一多播/广播业务有共享需求，也即是，该第一多播/广播业务可以在不同PLMN中共享。
多播会话的标识信息用于标识多播会话，例如，可以是该多播会话对应的TMGI，该多播会话用于传输第一多播/广播业务的数据。该TMGI可以为第一多播/广播业务在MOCN的第一PLMN中对应的TMGI。又例如，
PLMN的标识用于标识PLMN，例如，PLMN ID。
可选的，该第一会话建立请求消息是由应用服务器直接向第一多播/广播会话管理网元发送的，或者由应用服务器通过网络呈现功能(network exposure function，NEF)网元向第一多播/广播会话管理网元发送的，本申请不作限定。
S102，应用服务器向位于该MOCN的第二PLMN中的第二多播/广播会话管理网元发送第二会话建立请求消息。
其中，第二会话建立请求消息可以包括第一多播/广播业务的标识信息。该标识信息与步骤S101中的第一多播/广播业务的标识信息可以相同，也可以不同，不予限制。
其中，多播/广播业务的标识信息的功能性描述可以参考步骤S101，此处不再赘述。
示例性地，当第二会话建立请求消息携带有第一多播/广播业务的标识信息时，则可以表示第一多播/广播业务在不同PLMN中共享。
可选的，第二会话建立请求消息还包括第一多播/广播业务的类型、多播会话的标识信息、网络共享标识信息、PLMN的标识等，对上述信息的描述可以参考示例一中对应的描述，此处不再赘述。
可选的，S101和S102在执行时可能存在先后顺序，也可能是同时执行的。例如，可以先执行S101，后执行S102；也可以先执行S102，后执行S101；还可以同时执行S101和S102，本实施例不作限定。
S103，第一多播/广播会话管理网元根据该第一会话建立请求消息，向第一多播/广播用户面功能网元发送第一指示信息。
其中，该第一指示信息可以用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号。
其中，第一多播/广播会话管理网元和第一多播/广播用户面功能网元位于第一PLMN中。
其中，第一指示信息的具体实现方式可以包括但不限于以下几种情况：
情况一：第一指示信息作为一个独立的信元。例如，通过对现有信元设置特定的比特值来实现，或者通过一种新增的信元来实现，不予限制。例如，该信元携带于第一多播/广播会话管理网元向第一多播/广播用户面功能网元发送的N4mb会话建立/会话修改消息中。
需要说明的是，本申请中的递增是指将序列号进行递增处理，该递增处理可以是在该序列号的基础上进行增加，该增加的幅度遵循预设的规则或策略，该幅度可以是固定的，例如，以固定步长进行递增，该固定步长可以是1，也可以大于1。该幅度也可以是变化的，例如，以等差数列的方式进行递增，例如依次递增1、3、5等数值，本实施例不作限定。
需要指出的是，即使第一多播/广播用户面功能网元未向接入网设备发送该数据，第一多播/广播用户 面功能网元也可以将该数据对应的序列号进行递增处理。
情况二：第一指示信息由多个信元的组合来实现。例如，在转发行为规则(forwarding action rule，FAR)中，定义将数据发送到某个特定目的地(例如某个指定IP地址)，或者定义将数据在发送之前进行丢弃(也即是不发送数据)。在采用FAR实现方式的情况下，第一指示信息也能够使得第一多播/广播用户面功能网元对第一多播/广播业务的数据的处理，与其他多播/广播用户面功能网元对第一多播/广播业务的数据的处理是相同的，从而也有利于实现数据同步。
可选的，第一多播/广播会话管理网元在接收第一会话建立请求消息后，可以触发余下的会话建立步骤，例如，第一多播/广播会话管理网元执行与PCF交互生成多播的策略信息的步骤等，具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
可选的，步骤S103中第一多播/广播会话管理网元根据第一会话建立请求消息中的多播/广播业务的类型和/或第一多播/广播业务的标识信息，向第一多播/广播用户面功能网元发送第一指示信息。例如，当第一多播/广播业务的类型为多播业务，并且第一会话建立请求消息中携带有第一多播/广播业务的标识信息(表示该第一多播/广播业务有共享需求，也即是，该第一多播/广播业务可以在不同PLMN中共享)时，第一多播/广播会话管理网元向第一多播/广播用户面功能网元发送第一指示信息，以使第一多播/广播用户面功能网元可以同步更新第一多播/广播业务的数据的序列号，实现第一多播/广播业务的数据的序列号在不同PLMN中同步。
可选的，第一指示信息还包括第一序列号的起始值。例如，第一序列号的起始值为0。其中，本实施例中假设MOCN中不同PLMN针对同一多播/广播业务的数据的序列号的起始值相同，从而有利于不同PLMN针对同一多播/广播业务的数据的序列号实现同步。
S104，第二多播/广播会话管理网元根据第二会话建立请求消息，向第二多播/广播用户面功能网元发送第二指示信息。
其中，该第二指示信息可以用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号。
其中，第二多播/广播会话管理网元和第二多播/广播用户面功能网元位于第二PLMN中。对第二会话建立请求消息的描述可以参考S102中对应的描述，此处不再赘述。
其中，第二指示信息的具体实现方式可以参考第一指示信息的具体实现方式，例如第二指示信息作为一个独立的信元，通过对现有信元设置特定的比特值来实现，或者通过一种新增的信元来实现，例如，该信元携带于第二多播/广播会话管理网元向第二多播/广播用户面功能网元发送的N4mb会话建立/会话修改消息中，或者由一个或多个现有信元的组合来实现，此处不再赘述。
可选的，第二多播/广播会话管理网元在接收第二会话建立请求消息后，可以触发余下的会话建立步骤，例如，第二多播/广播会话管理网元执行与PCF交互生成多播的策略信息的步骤等，具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
可选的，步骤S104中第二多播/广播会话管理网元根据第二会话建立请求消息中的多播/广播业务的类型和/或第一多播/广播业务的标识信息，向第二多播/广播用户面功能网元发送第二指示信息。具体实现方式可以参考S103中的实现方式，此处不再赘述。其中，第二多播/广播会话管理网元向第二多播/广播用户面功能网元发送第二指示信息，以使第二多播/广播用户面功能网元可以同步更新第一多播/广播业务的数据的序列号。
可选的，第二指示信息还包括第二序列号的起始值。例如，第二序列号的起始值为0。其中，第一序列号的起始值与第一多播/广播业务的数据在MOCN的第二PLMN中对应的第二序列号的起始值可以相同。在第一多播/广播业务的数据在MOCN的第一PLMN中的第一序列号和第二PLMN中的第二序列号的起始值相同的情况下，对序列号进行递增处理的策略也相同(例如，当接收第一多播/广播业务的数据时，就将序列号加1)，能够实现第一多播/广播业务的数据的序列号在第一PLMN和第二PLMN中保持相同。
可选的，S103和S104在执行时可能存在先后顺序，也可能是同时执行的。例如，可以先执行S103，后执行S104；也可以先执行S104，后执行S103；还可以同时执行S103和S104，本实施例不作限定。
可见，通过执行上述S101-S104，应用服务器可以预先请求MOCN中的多个PLMN(例如本实施例中的第一PLMN和第二PLMN)进行特殊的用户面配置，使得每个PLMN均会同步更新相同多播/广播业务的数据的序列号(例如收到该数据就更新该数据的序列号)，从而使得不同多播/广播用户面功能网元对于相同的多播/广播业务的数据设置相同的序列号，有利于实现数据的同步。
可选的，上述方法还包括以下步骤，如图3b所示：
S105，应用服务器向第一多播/广播用户面功能网元和第二多播/广播用户面功能网元发送第一多播/广播业务的数据。
需要指出的是，在应用服务器向第一多播/广播用户面功能网元和第二多播/广播用户面功能网元发送第一多播/广播业务的数据之前，可以已预先建立用于传输第一多播/广播业务的数据的MBS会话。
S106，第一多播/广播用户面功能网元根据第一指示信息，递增该第一多播/广播业务的数据对应的第一序列号。
其中，递增可以参考步骤S103中的相关描述，例如，当第一多播/广播用户面功能网元接收第一多播/广播业务的数据时，将第一多播/广播业务的数据对应的第一序列号加1。
在一个示例中，当第一指示信息包括第一序列号的起始值时，第一多播/广播用户面功能网元根据第一指示信息，将第一序列号的起始值加1，加1后的数值也即是第一多播/广播业务的数据对应的第一序列号的数值。
在另一个示例中，当第一指示信息为FAR时，第一多播/广播用户面功能网元根据第一指示信息，将该第一多播/广播业务的数据发送至指定的IP地址。
S107，第二多播/广播用户面功能网元根据第二指示信息，递增该第一多播/广播业务的数据对应的第二序列号。
其中，递增可以参考步骤S103中的相关描述，例如，当第二多播/广播用户面功能网元接收第一多播/广播业务的数据时，将第一多播/广播业务的数据对应的第二序列号加1。
示例性地，当第二指示信息包括第二序列号的起始值时，第二多播/广播用户面功能网元根据第二指示信息，将第二序列号的起始值加1，加1后的数值也即是第二多播/广播业务的数据对应的第二序列号的数值。
当第二指示信息为FAR时，第二多播/广播用户面功能网元根据第二指示信息，将该第二多播/广播业务的数据发送至指定的IP地址。其中，该指定的IP地址和S106中第一多播/广播用户面功能网元将第一多播/广播业务的数据发送至指定的IP地址相同。
因此，第一序列号和第二序列号可以保持同步。若存在接入网设备可以同时与第一多播/广播用户面功能网元以及第二多播/广播用户面功能网元相连接，则当该接入网设备接收来自第一多播/广播用户面功能网元的第一多播/广播业务的数据，以及来自第二多播/广播用户面功能网元的第一多播/广播业务的数据时，该接入网设备可以识别来自两个设备的数据为同一多播/广播业务的数据。或者，针对相同的第一多播/广播业务的数据，可以仅由第一多播/广播用户面功能网元发送至该接入网设备，或者仅由第二多播/广播用户面功能网元发送至该接入网设备，有利于降低空口资源的消耗。
可选的，S106和S107在执行时可能存在先后顺序，也可能是同时执行的。例如，可以先执行S106，后执行S107；也可以先执行S107，后执行S106；还可以同时执行S106和S107，本实施例不作限定。
可选的，本申请中的消息名称仅为一种示例，本申请并不限定各个网元或设备之间的消息的名称，各个消息的名称可以参考标准协议中的描述。
示例二：图4为本申请提供的另一种通信方法的流程示意图。该通信方法应用于如图1所示的通信***中。例如，该通信方法可以由应用服务器、多播/广播会话管理网元、多播/广播用户面功能网元、会话管理网元、接入网设备、终端设备之间的交互实现，包括以下步骤：
S201，应用服务器生成会话建立请求消息。
其中，该会话建立请求消息可以包括MOCN中主PLMN的标识，进一步地，还可以包括第一多播/广播业务的标识信息。
其中，主PLMN也可以称为主要PLMN，该主PLMN中的MB-UPF，可以称为主MB-UPF。
示例性地，该会话建立请求消息包括主PLMN的标识，主MB-UPF可以用于在MOCN中的统一路由多播/广播业务的数据，即可以不限于特定的业务。
示例性地，该会话建立请求消息包括第一多播/广播业务的标识信息和主PLMN的标识，该主MB-UPF可以用于在MOCN中的统一路由第一多播/广播业务的数据，即该MOCN中的接入网设备均可以与该主MB-UPF建立共享传输通道，以实现第一多播/广播业务的数据的转发。
其中，对PLMN的标识和多播/广播业务的标识信息的描述可以参考示例一中对应的描述，此处不再赘述。
S202，应用服务器向第一多播/广播会话管理网元和第二多播/广播会话管理网元分别发送该会话建立请求消息。
具体地，应用服务器可以从MOCN中需要传输多播/广播业务的数据的PLMN中选择一个PLMN作为主PLMN，接入网设备与该主PLMN的MB-UPF建立共享传输通道，即实现了接入网设备与同一个MB-UPF建立共享传输通道，从而避免了多个MB-UPF产生不同序列号的情况，解决了序列号不同步的问题。
例如，假设MOCN中存在3个PLMN，分别为第一PLMN、第二PLMN和第三PLMN，该3个PLMN都可以传输多播/广播业务的数据(例如第一多播/广播业务的数据)。应用服务器选择第一PLMN作为主PLMN，接入网设备与第一PLMN的MB-UPF建立共享传输通道，以传输第一多播/广播业务的数据。
可选的，该会话建立请求消息还包括但不限于以下信息中的一项或多项：多播/广播业务的类型、多播会话的标识信息、或网络共享标识信息等。对上述信息的描述可以参考示例一中对应的描述，此处不再赘述。
可选的，该会话建立请求消息可以由应用服务器直接向第一多播/广播会话管理网元或第二多播/广播会话管理网元发送，也可以由应用服务器通过NEF向第一多播/广播会话管理网元或第二多播/广播会话管理网元发送，本申请不作限定。
需要指出的是，上述S202中向第一多播/广播会话管理网元和第二多播/广播会话管理网元发送的会话建立请求消息可以略有不同，不予限制。
此外，步骤S201-S202可以替换为：应用服务器向第一多播/广播会话管理网元和第二多播/广播会话管理网元分别发送主PLMN的标识，进一步地，还可以发送第一多播/广播业务的标识信息，不予限制。
S203，第一多播/广播会话管理网元向第一会话管理网元发送多播/广播业务会话上下文。
其中，该多播/广播业务会话上下文可以包括主PLMN的标识和第一多播/广播业务的标识信息。
其中，主PLMN的标识和第一多播/广播业务的标识信息可以用于第一多播/广播会话管理网元触发建立接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道。其中，该共享传输通道用于传输第一多播/广播业务的数据。例如，假设主PLMN为第一PLMN，那么第一多播/广播会话管理网元在接收到多播/广播业务会话上下文之后，触发该MOCN中的接入网设备(例如，第二PLMN中的接入网设备)建立与第一PLMN的多播/广播用户面功能网元之间的共享传输通道。
其中，第一多播/广播会话管理网元和第一会话管理网元位于同一个PLMN中，例如，可以位于第二PLMN中，也可以位于第一PLMN中，不予限制。
可选的，第一多播/广播会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，此处的“触发”可以理解为：第一多播/广播会话管理网元在多播/广播业务会话上下文中包含主PLMN的标识，经由第一会话管理网元最终发送给MOCN中的接入网设备。当MOCN中的接入网设备尚未建立与多播/广播用户面功能网元之间，针对此多播/广播业务的传输通道时，MOCN中的接入网设备与主PLMN的多播/广播用户面功能网元建立共享传输通道。
可选的，若多播/广播业务会话上下文还包括其他的多播/广播业务的标识信息(例如还包括第二多播/广播业务的标识信息)，则主PLMN的标识和第二多播/广播业务的标识信息用于第一多播/广播会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第二多播/广播业务的数据。
可选的，第一多播/广播会话管理网元在执行S203之前，还可以执行以下步骤：
(1)第一多播/广播会话管理网元在接收该会话建立请求消息后，将主PLMN的标识(也称为Primary PLMN ID)和第一多播/广播业务的标识信息保存在MBS会话上下文中。
(2)第一多播/广播会话管理网元接收该会话建立请求消息后，触发余下的会话建立步骤，例如，第一多播/广播会话管理网元执行与PCF交互生成多播的策略信息的步骤，第一多播/广播会话管理网元执行配置第一多播/广播用户面功能网元的步骤等，具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
S204，第二多播/广播会话管理网元向第二会话管理网元发送多播/广播业务会话上下文。
其中，该多播/广播业务会话上下文包括MOCN中主PLMN的标识，进一步地，还可以包括第一多播/广播业务的标识信息。
其中，主PLMN的标识和第一多播/广播业务的标识信息可以用于第二多播/广播会话管理网元触发建立接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道。其中，该共享传输通道用于传输该第一多播/广播业务的数据。例如，假设主PLMN为第一PLMN，那么第二多播/广播会话管理网元在接收到多播/广播业务会话上下文之后，触发该MOCN中的接入网设备(例如第二PLMN中的接入网设备)建立与第一PLMN的多播/广播用户面功能网元之间的共享传输通道。
其中，第二多播/广播会话管理网元和第二会话管理网元位于同一个PLMN中，例如，可以位于第二PLMN中，也可以位于第一PLMN中，不予限制。
可选的，第二多播/广播会话管理网元触发建立MOCN的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，此处的“触发”可以理解为：第二多播/广播会话管理网元在多播/广播业务会话上下文中包含主PLMN的标识，经由第二会话管理网元最终发送给MOCN中的接入网设备。当MOCN中的接入网设备尚未建立与多播/广播用户面功能网元之间，针对此多播/广播业务的传输通道时，MOCN中的接入网设备与主PLMN的多播/广播用户面功能网元建立共享传输通道。
可选的，若多播/广播业务会话上下文还包括其他的多播/广播业务的标识信息(例如还包括第二多播/广播业务的标识信息)，则主PLMN的标识和第二多播/广播业务的标识信息用于第二多播/广播会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第二多播/广播业务的数据。
可选的，第二多播/广播会话管理网元在执行S204之前，还可以执行以下步骤：
(1)第二多播/广播会话管理网元接收该会话建立请求消息后，将主PLMN的标识(也称为Primary PLMN ID)和第一多播/广播业务的标识信息保存在MBS会话上下文中(即将它们作为MBS会话上下文中的一部分加以保存)。
(2)第二多播/广播会话管理网元接收该会话建立请求消息后，触发余下的会话建立步骤，例如，第二多播/广播会话管理网元执行与PCF交互生成多播的策略信息的步骤，第二多播/广播会话管理网元执行配置第二多播/广播用户面功能网元的步骤等，具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
可选的，S203和S204在执行时可能存在先后顺序，也可能是同时执行的。例如，可以先执行S203，后执行S204；也可以先执行S204，后执行S203；还可以同时执行S203和S204，本实施例不作限定。
可见，通过执行上述S201-S204，可以增强MOCN中的接入网设备的共享传输通道建立流程，使得MOCN中的接入网设备均与主PLMN的多播/广播用户面功能网元建立共享传输通道，从而避免了多个多播/广播用户面功能网元产生不同序列号的情况，有利于实现数据的同步。
可选的，示例二还可以包括以下步骤：
S205，终端设备向第二PLMN中的第二会话管理网元发送多播会话请求消息。
其中，该多播会话请求消息包括多播/广播业务会话的标识。
S206，第二会话管理网元根据该多播/广播业务会话的标识，向该多播/广播业务会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息。
其中，多播会话的标识可以包括TMGI、或IP多播地址等信息。例如，若在某一时间段，终端设备请求加入多播群组，并向第二会话管理网元发送多播会话请求消息。
具体地，该多播会话请求消息可以是PDU会话建立请求(PDUSessionEstablishmentrequest)消息，或者是PDU会话修改请求(PDUSessionModificationrequest)消息。
第二会话管理网元根据该多播会话的标识，向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息，该多播/广播业务会话上下文请求消息用于请求获取该多播/广播业务会话对应的MBS会话上下文。具体地，该多播/广播业务会话上下文请求消息可以是MB-SMF提供的接口-多播广播会话上下文状态订阅请求(Nmbsmf_MBSSession_ContextStatusSubscribe request)消息。
S207，多播会话的标识对应的多播/广播会话管理网元向第二会话管理网元发送多播/广播业务会话上下文。
其中，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。
S208，第二会话管理网元向MOCN中的第一接入网设备发送N2协议数据单元会话资源消息。
其中，该N2协议数据单元会话资源消息可以包括主PLMN的标识和第一多播/广播业务的标识信息，该第一接入网设备为加入第一多播/广播业务的终端设备所接入的接入网设备。
S209，第一接入网设备向主PLMN中的多播/广播会话管理网元发送第一N2多播会话请求消息。
其中，该第一N2多播会话请求消息用于请求建立第一接入网与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
示例性地，第一N2多播会话请求消息可以是多播广播和业务分发建立请求传输(MBS Distribution Setup Request Transfer)消息。该消息可以进一步包含在第一接入网设备发送给AMF的分发建立请求(DISTRIBUTION SETUP REQUEST)消息中，并由AMF发送给主PLMN中的多播/广播会话管理网元。
可选的，该第一N2多播会话请求消息包括第一多播/广播业务的标识信息。例如，若第一多播/广播业务的标识是IP多播地址，则第一接入网将第一多播/广播业务的标识信息的全部内容提供给MB-SMF。具体地，第一接入网设备可以首先根据主PLMN的标识选择对应的AMF，然后AMF根据该IP多播地址，通过NRF找出对应的MB-SMF。又例如，若第一多播/广播业务的标识是TMGI列表，则第一接入网设备可以根据主PLMN的标识从该TMGI列表中找到对应的TMGI(例如根据TMGI包含的PLMN ID字段找到对应的TMGI)。在这种情况下，第一接入网设备仅需要提供第一多播/广播业务的标识信息的部分内容(例如提供TMGI列表中与主PLMN对应的TMGI)。
可选的，S209的具体实现方式可以包括以下两种情况：
情况一：当第一接入网设备未建立共享传输通道时，第一接入网设备向主PLMN中的多播/广播会话管理网元发送第一N2多播会话请求消息，并建立与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
例如，假设第一接入网设备未建立共享传输通道，假设主PLMN为第一PLMN，则第一接入网设备可以基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而有利于使得第一PLMN的多播/广播用户面功能网元针对第一多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
情况二：当第一接入网设备已建立共享传输通道时，第一接入网设备丢弃该N2协议数据单元会话资源消息；或者，第一接入网设备向第二会话管理网元发送第三指示信息，该第三指示信息用于指示该共享传输通道已建立；再或者，第一接入网设备向第二会话管理网元发送N2协议数据单元会话资源消息的响应消息，表示第一接入网设备已经成功收到N2协议数据单元会话资源消息。示例性地，N2协议数据单元会话资源消息可以是NGAP PDU会话资源建立(NGAP PDU Session resource establishment)消息，或者是NGAP PDU会话资源修改(NGAP PDU Session resource modify)消息。
例如，假设第一接入网设备已建立共享传输通道，假设主PLMN为第一PLMN，则第一接入网设备可能丢弃第一PLMN的标识和第一多播/广播业务的标识信息，或者，向第二会话管理网元发送第三指示信息，该第三指示信息用于指示该共享传输通道已建立。也即是，若第一接入网设备不能被该MOCN的所有PLMN共享时，第一接入网设备可以不使用主PLMN的标识，而是自行建立共享传输通道以传输第一多播/广播业务的数据。
可选的，当共享传输通道建立完毕后，第一接入网设备可以配置终端设备的无线资源控制(radio resource control，RRC)连接。具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
S210，第一接入网设备向第二接入网设备发送切换请求消息。
其中，该切换请求消息包括主PLMN的标识和第一多播/广播业务的标识信息。
其中，若第一接入网设备(也即是S-RAN)确定将终端设备进行切换，则第一接入网设备可以向第二接入网设备(也即是T-RAN)发送切换请求消息。第一PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与第一PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。其中，第一公共陆地移动网络的标识指的是UE在S-RAN接收的多播会话由哪个PLMN的MB-SMF管理，这可能和UE的注册的PLMN ID不相同。
S211，第二接入网设备向主PLMN中的多播/广播会话管理网元发送第二N2多播会话请求消息。
其中，该第二N2多播会话请求消息包括第一多播/广播业务的标识信息，用于请求建立第二接入网与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。示例性地，第二N2多播会话请求消息可以是多播广播和业务分发建立请求传输(MBS Distribution Setup Request Transfer)消息。其可以进一步包含在第二接入网设备发送给AMF的分发建立请求(DISTRIBUTION SETUP REQUEST)消息中，并由AMF发送给第一PLMN中的多播/广播会话管理网元。
可选的，该第二N2多播会话请求消息可以包括第一多播/广播业务的标识信息的全部或部分内容。具体实现方式可以参考对第一N2多播会话请求消息的描述，此处不再赘述。
可选的，S211的具体实现方式可以包括以下两种情况：
情况一：当第二接入网设备未建立共享传输通道时，第二接入网设备向主PLMN中的多播/广播会话管理网元发送第二N2多播会话请求消息，并建立与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
例如，假设第二接入网设备未建立共享传输通道，则第二接入网设备也建立与主PLMN中的多播/广 播用户面功能网元之间的共享传输通道，从而有利于使得该主PLMN的多播/广播用户面功能网元针对第一多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
情况二：第二接入网设备可以基于配置原因，不使用主PLMN的标识，而是通过现有的流程建立共享传输通道。例如，假设第二接入网设备不能被PLMN共享时，第二接入网设备只能连接到第二PLMN时，第二接入网设备建立与第二PLMN的多播/广播用户面功能网元之间的共享传输通道。
示例三：图5为本申请提供的另一种通信方法的流程示意图。该通信方法应用于如图1所示的通信***中。例如，该通信方法可以由多播/广播会话管理网元、多播/广播用户面功能网元、会话管理网元、接入网设备、终端设备之间的交互实现，包括以下步骤：
S301，第一接入网设备接收第一多播/广播业务的标识信息。
其中，对第一多播/广播业务的标识信息的描述可以参考示例一中对应的描述，此处不再赘述。
可选的，S301之前还包括以下步骤：
(1)终端设备向第一会话管理网元发送多播会话请求消息，该多播会话请求消息包括多播会话的标识。具体地，该多播会话请求消息可以是PDU会话建立请求(PDUSessionEstablishmentrequest)消息，或者是PDU会话修改请求(PDUSessionModificationrequest)消息。
(2)第一会话管理网元根据该多播会话的标识，向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息。具体地，多播/广播业务会话上下文请求消息可以是MB-SMF提供的接口-多播广播会话上下文状态订阅请求t(Nmbsmf_MBSSession_ContextStatusSubscribereques)消息。
其中，多播会话的标识可以包括TMGI、或IP多播地址等信息。
(3)多播会话的标识对应的多播/广播会话管理网元向第一会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括第一多播/广播业务的标识信息。
(4)第一会话管理网元向第一接入网设备发送第一多播/广播业务的标识信息。对应的，第一接入网设备接收来自第一会话管理网元的第一多播/广播业务的标识信息。
上述步骤(1)至(4)的具体实现方式可以参考示例二中对应的描述，此处不再赘述。
可选的，当第一接入网设备接收第一多播/广播业务的标识信息时，第一接入网设备可以触发建立共享传输通道的流程，具体实现方式可以参考现有标准协议中对应的流程，此处不再赘述。
S302，第一接入网设备向第二接入网设备发送Xn接口消息，该Xn接口消息包括该第一多播/广播业务的标识信息以及第一PLMN的标识。
示例性地，Xn接口消息可以是NG-RAN节点配置更新(NG-RAN node Configuration Update)请求消息，也可以是资源状态上报(Resource Status Reporting)消息，也可以是新设计消息，本申请不作限定。
其中，第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。例如，本实施例假设第一接入网设备和第二接入网设备位于MOCN中，且第一PLMN属于MOCN，且第一接入网设备和第二接入网设备都有Xn接口，则第一接入网可以通过Xn接口向第二接入网设备发送第一多播/广播业务的标识信息以及第一PLMN的标识。
其中，第一PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据。例如，当第二接入网设备接收第一PLMN的标识和第一多播/广播业务的标识信息后，若之后第二接入网设备需要建立共享传输通道，则第二接入网设备优先选择与第一PLMN中的多播/广播用户面功能网元建立第二共享传输通道，从而使得第二接入网设备与第一接入网设备都建立到同一个PLMN的共享传输通道，有利于实现数据传输的同步。
可选的，当第二接入网设备接收Xn接口消息后，第二接入网设备不会立即建立共享传输通道，而是等到后续有相同的第一多播/广播业务的标识信息的终端设备加入第二接入网设备时，第二接入网设备才会建立对应的共享传输通道。
可选的，示例三还包括以下步骤：
S303，第二接入网设备接收第二多播/广播业务的标识信息。
其中，第二多播/广播业务的标识信息和第一多播/广播业务的标识信息是类似的，对第二多播/广播业务的标识信息描述可以参考示例一中对第一多播/广播业务的标识信息的描述，此处不再赘述。
可选的，S303之前还包括以下步骤：
(5)一段时间后，另外一个终端设备向第二会话管理网元发送多播会话请求消息，该多播会话请求 消息包括多播会话的标识。
(6)第二会话管理网元根据该多播会话的标识，向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息。
其中，多播会话的标识可以包括TMGI、或IP多播地址等信息。
(7)多播会话的标识对应的多播/广播会话管理网元向第二会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括第二多播/广播业务的标识信息。
(8)第二会话管理网元向第二接入网设备发送第二多播/广播业务的标识信息。对应的，第二接入网设备接收来自第二会话管理网元的第二多播/广播业务的标识信息。
其中，上述步骤(5)至(8)的具体实现方式可以参考示例二中对应的描述，此处不再赘述。可选的，上述步骤(5)至(8)中的第二会话管理网元也可以替换为第一会话管理网元，也即是，该终端设备可以在同一PLMN请求加入多播群组，也可以在另一PLMN请求加入多播群组。
S304，第二接入网设备根据第一PLMN的标识、第一多播/广播业务的标识信息和第二多播/广播业务的标识信息，建立与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道。
其中，该第二共享传输通道用于传输第一多播/广播业务的数据和第二多播/广播业务的数据。
其中，S304的具体实现方式包括以下情况：
情况一：当第一多播/广播业务和第二多播/广播业务的类型相同时，第二接入网设备向第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息。
例如，第一多播/广播业务的类型信息可以包含于第一多播/广播业务的标识信息中，第二多播/广播业务的类型信息可以包含于第二多播/广播业务的标识信息中，具体地，标识信息中的某一字段携带类型信息。
情况二：当第一多播/广播业务的标识信息对应的多播网络地址与第二多播/广播业务的标识信息对应的多播网络地址相同时，第二接入网设备向第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息。
例如，第一多播/广播业务对应的多播网络地址可以包含于第一多播/广播业务的标识信息中，第二多播/广播业务对应的多播网络地址可以包含于第二多播/广播业务的标识信息中，具体地，标识信息中的某一字段携带多播/广播业务对应的多播网络地址。
情况三：当第一多播/广播业务的标识信息和第二多播/广播业务的标识信息相同时，第二接入网设备向第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息。
综上所述，若第二接入网设备发现附近已经有一个接入网设备(例如第一接入网设备)建立了共享传输通道，则第二接入网设备将尝试建立到同一PLMN的共享传输通道，有利于实现数据传输的同步。
示例四：图6为本申请提供的另一种通信方法的流程示意图。该通信方法应用于如图1所示的通信***中。例如，该通信方法可以由应用服务器、多播/广播会话管理网元、多播/广播用户面功能网元、会话管理网元、接入网设备、终端设备之间的交互实现，包括以下步骤：
S401，第一接入网设备向第二接入网设备发送切换请求消息。
其中，该切换请求消息包括MOCN中第一PLMN的标识和第一多播/广播业务的标识信息。
其中，第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。
其中，对第一PLMN和第一多播/广播业务的标识信息的描述可以参考示例一中对应的描述，此处不再赘述。
例如，若属于第一接入网设备的终端设备需要切换至第二接入网设备，则第一接入网设备向第二接入网设备发送第一PLMN的标识和第一多播/广播业务的标识信息。
可选的，切换请求消息还包括终端设备所属的PLMN的标识。例如，第一接入网设备还可以向第二接入网设备发送终端设备所属的PLMN的标识，从而使第二接入网设备将终端设备所属的PLMN的多播/广播用户面功能网元作为建立共享传输通道的次优选择。
可选的，S401之前还包括以下步骤：
(1)应用服务器向位于MOCN的第一PLMN中的第一多播/广播会话管理网元发送第一会话建立请求消息。其中，第一会话建立请求消息包括第一多播/广播业务的标识信息和第一PLMN的标识。
可选的，第一多播/广播会话管理网元接收第一会话建立请求消息后，可以触发余下的会话建立步骤，例如，第一多播/广播会话管理网元执行与PCF交互生成多播的策略信息的步骤等，具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
(2)应用服务器向位于该MOCN的第二PLMN中的第二多播/广播会话管理网元发送第二会话建立请求消息。其中，第二会话建立请求消息包括第二PLMN的标识和第一多播/广播业务的标识信息。
可选的，第二多播/广播会话管理网元接收第二会话建立请求消息后，可以触发余下的会话建立步骤，例如，第二多播/广播会话管理网元执行与PCF交互生成多播的策略信息的步骤等，具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
(3)终端设备向第一PLMN中的第一会话管理网元发送多播会话请求消息，该多播会话请求消息包括多播会话的标识。
(4)第一会话管理网元根据该多播会话的标识，向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息。
(5)多播会话的标识对应的多播/广播会话管理网元向第一会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括第一多播/广播业务的标识信息。
(6)第一会话管理网元向第一接入网设备发送第一多播/广播业务的标识信息。对应的，第一接入网设备接收来自第一会话管理网元的第一多播/广播业务的标识信息。
其中，上述步骤(1)和(6)的具体实现方式可以参考示例二或示例三中对应的描述，此处不再赘述。
可选的，当第一接入网设备接收第一多播/广播业务的标识信息时，第一接入网设备可以触发建立共享传输通道的流程，具体实现方式可以参考现有标准协议中对应的流程，此处不再赘述。
可选的，当共享传输通道建立完毕后，第一接入网设备可以配置终端设备的RRC连接。具体实现方式可以参考现有协议标准中对应的描述，此处不再赘述。
S402，第二接入网设备向第一接入网设备发送切换响应消息。
其中，该切换响应消息包括第二PLMN的标识或第四指示信息。
其中，第二PLMN为与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN。可选的，第二PLMN与第一PLMN不同，表示第二接入网设备使用与第一接入网设备不同的PLMN标识建立了共享传输通道。或者，第二PLMN可以就是第一PLMN，也即是，第二接入网设备已建立的共享传输通道指向的PLMN就是第一PLMN，表示第二接入网设备复用第一PLMN。
其中，第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN。也即是，第二接入网设备已建立的共享传输通道指向的PLMN就是第一PLMN，表示第二接入网设备复用第一PLMN。
其中，S402的具体实现方式可以包括以下几种情况：
情况一：当第二接入网设备未建立用于传输第一多播/广播业务的数据的第二共享传输通道时，第二接入网设备根据第一PLMN的标识和第一多播/广播业务的标识信息，建立与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道。
例如，若第二接入网设备未建立用于传输第一多播/广播业务的数据的共享传输通道，第二接入网设备可以尝试与第一PLMN中的多播/广播用户面功能网元建立共享传输通道，从而使得第一多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。在这种情况下，第二接入网设备向第一接入网设备发送的切换响应消息中包括的第二PLMN标识为第一PLMN标识；或者，切换响应消息中包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN。也即是，第二接入网设备已建立的共享传输通道指向的PLMN就是第一PLMN，表示第二接入网设备复用第一PLMN。
情况二：当第二接入网设备已建立用于传输第一多播/广播业务的数据的第二共享传输通道时，则第二接入网设备向第一接入网设备反馈的切换响应消息包括第二PLMN的标识或第四指示信息。
例如，若第二接入网设备已建立用于传输第一多播/广播业务的数据的共享传输通道，并且该共享传输通道指向与第一PLMN标识相同的PLMN，也即是，第二接入网设备已建立的共享传输通道指向的PLMN就是第一PLMN，表示第二接入网设备复用第一PLMN，则第二接入网设备向第一接入网设备反馈的切换响应消息中包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN；或者，切换响应消息包括的第二PLMN的标识为第一PLMN。
又例如，若第二接入网设备已建立用于传输第一多播/广播业务的数据的共享传输通道，并且该共享传输通道指向与第一PLMN标识不同的PLMN，则第二接入网设备向第一接入网设备反馈的切换响应消息中包括第二PLMN的标识，此时第二PLMN与第一PLMN不同。
可选的，当第二接入网设备已建立用于传输第一多播/广播业务的数据的第二共享传输通道时，第二接 入网设备还可以不向第一接入网设备反馈信息。
可选的，S402之后还包括以下步骤：
(7)第一接入网设备根据第二PLMN的标识或第四指示信息，向第二接入网设备转发第一多播/广播业务的数据。
可选的，第一接入网设备可以在预设的时间段内向第二接入网设备转发第一多播/广播业务的数据，可以部分缓解丢包的问题，但是也不会占用较多的转发资源。
例如，若第二接入网设备向第一接入网设备反馈其已建立与其他PLMN中的多播/广播用户面功能网元之间的共享传输通道，则第一接入网设备可以在一定时间内(例如基于定时器等)，向第二接入网设备传输部分第一接入网设备当前正在发送的该多播/广播业务的数据，这样可以部分缓解丢包的问题。在这种情况下，第二接入网设备使用单播方式转发该第一多播/广播业务的数据。
可选的，当第二共享传输通道对应的PLMN的标识与第一PLMN的标识不同时，第一接入网设备可以停止向第二接入网设备转发第一多播/广播业务的数据。
为了实现本申请提供的方法中的各功能，本申请提供的装置或设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
图7为本申请提供的一种通信装置的示意图。该装置可以包括执行如图3a至图6所示的任一实施例中所描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可以是软件，也可以是硬件电路结合软件实现。
该装置700包括通信单元701和处理单元702，用于实现前述实施例中各个网元或设备所执行的方法。
一种可能的实施方式中，该装置为多播/广播会话管理网元，或位于多播/广播会话管理网元中。具体地，通信单元701用于接收来自应用服务器的第一会话建立请求消息，该第一会话建立请求消息包括第一多播/广播业务的标识信息和MOCN中第一PLMN的标识。处理单元702用于根据第一会话建立请求消息，通过通信单元701向第一多播/广播用户面功能网元发送第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号；其中，第一多播/广播会话管理网元和第一多播/广播用户面功能网元位于第一PLMN中。
可选的，第一序列号用于MOCN中的接入网设备识别来自第一PLMN的第一多播/广播业务的数据。
可选的，第一会话建立请求消息还包括该多播/广播业务的类型。当第一多播/广播业务的类型为多播业务时，通信单元701还用于向第一多播/广播用户面功能网元发送第一指示信息。
可选的，第一会话建立请求消息还包括网络共享标识信息；该网络共享标识信息用于指示第一多播/广播业务在MOCN的第二PLMN的临时多播群组标识TMGI列表中共享，第二PLMN与第一PLMN不同。通信单元701还用于根据该网络共享标识信息，向第一多播/广播用户面功能网元发送第一指示信息。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以指示对应的第一多播/广播用户面功能网元进行特殊的配置，例如，指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号(例如将第一序列号加1)。从而使得第一多播/广播用户面功能网元根据第一多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，有利于实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置为多播/广播会话管理网元，或位于多播/广播会话管理网元中。具体地，通信单元701用于接收来自应用服务器的第二会话建立请求消息，该第二会话建立请求消息包括第一多播/广播业务的标识信息和MOCN中第二PLMN的标识。处理单元702用于根据第二会话建立请求消息，通过通信单元701向第二多播/广播用户面功能网元发送第二指示信息，该第二指示信息用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号；其中，第二多播/广播会话管理网元和第二多播/广播用户面功能网元位于第二PLMN中。
可选的，第二序列号用于MOCN中的接入网设备识别来自第二PLMN的第一多播/广播业务的数据。
可选的，第一指示信息包括第一序列号的起始值，第二指示信息包括第二序列号的起始值，第一序列号的起始值与第一多播/广播业务的数据在MOCN的第二PLMN中对应的第二序列号的起始值相同。
可选的，第二会话建立请求消息还包括该多播/广播业务的类型。当第一多播/广播业务的类型为多播业务时，通信单元701还用于向第二多播/广播用户面功能网元发送第一指示信息。
可选的，第二会话建立请求消息还包括网络共享标识信息；该网络共享标识信息用于指示第一多播/广播业务在MOCN的第二PLMN的临时多播群组标识TMGI列表中共享，第二PLMN与第一PLMN不同。通信单元701还用于根据该网络共享标识信息，向第二多播/广播用户面功能网元发送第二指示信息。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以指示对应的第二多播/广播用户面功能网元进行特殊的配置，例如，指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号(例如将第二序列号加1)。从而使得第二多播/广播用户面功能网元根据第二多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，从而实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置为多播/广播用户面功能网元，或位于多播/广播用户面功能网元中。具体地，通信单元701用于接收来自多播/广播会话管理网元的第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号。通信单元701还用于接收来自应用服务器的第一多播/广播业务的数据；处理单元702用于根据该第一指示信息，递增该数据对应的第一序列号。
可选的，通信单元701还用于向MOCN中的接入网设备发送该第一多播/广播业务的数据以及该数据对应的所述第一序列号，第一多播/广播用户面功能网元位于MOCN的第一PLMN中，第一序列号用于该接入网设备识别来自第一PLMN的第一多播/广播业务的数据。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以根据指示对用户面的处理进行特殊配置，例如，在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号，而不管是否会向接入网设备发送该数据。从而使得第一多播/广播用户面功能网元可以同步更新相同多播/广播业务的数据的序列号，实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置为多播/广播用户面功能网元，或位于多播/广播用户面功能网元中。具体地，通信单元701接收来自第二多播/广播会话管理网元的第二指示信息，该第二指示信息用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时，递增该数据对应的第二序列号。通信单元701还用于接收来自应用服务器的第一多播/广播业务的数据；处理单元702用于根据该第二指示信息，递增该数据对应的第二序列号。
可选的，通信单元701还用于向MOCN中的接入网设备发送第一多播/广播业务的数据以及该数据对应的第二序列号，第二多播/广播用户面功能网元位于MOCN的第二PLMN中，第二序列号用于该接入网设备识别来自第二PLMN的第一多播/广播业务的数据。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以根据指示对用户面的处理进行特殊配置，例如，在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号，而不管是否会向接入网设备发送该数据。从而使得第二多播/广播用户面功能网元可以同步更新相同多播/广播业务的数据的序列号，实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置为应用服务器，或位于应用服务器中。具体地，通信单元701用于向位于MOCN的第一PLMN中的第一多播/广播会话管理网元发送第一会话建立请求消息，该第一会话建立请求消息包括第一PLMN的标识和第一多播/广播业务的标识信息。通信单元701还用于向位于MOCN的第二PLMN中的第二多播/广播会话管理网元发送第二会话建立请求消息，该第二会话建立请求消息包括第二PLMN的标识和第一多播/广播业务的标识信息；其中，第一PLMN与第二PLMN不同。需要指出的是，在该实施方式中，处理单元702为可选的，不予限制。
可选的，第一会话请求消息还包括第一多播/广播业务的数据在第一PLMN中对应的第一序列号的起始值；第二会话请求消息还包括第一多播/广播业务的数据在第二PLMN中对应的第二序列号的起始值；其中，第一序列号的起始值与第二序列号的起始值相同。
该实施方式中通信单元701的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。 该装置所实现的通信方法可以向MOCN的不同PLMN中的多播/广播会话管理网元发送第一多播/广播业务的标识信息，不同PLMN中的多播/广播会话管理网元再向分别对应的多播/广播用户面功能网元发送指示信息，有利于使得不同PLMN中的多播/广播用户面功能网元同时接收来自应用服务器的第一多播/广播业务的数据，并同步更新针对该第一多播/广播业务的数据的序列号，从而有利于实现数据同步。
一种可能的实施方式中，该装置为应用服务器，或位于应用服务器中。具体地，处理单元702用于生成会话建立请求消息，该会话建立请求消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息。通信单元701用于向多播/广播会话管理网元发送该会话建立请求消息。其中，该主PLMN的标识和该第一多播/广播业务的标识信息用于多播/广播会话管理网元触发建立MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输该第一多播/广播业务的数据。
可选的，多播/广播会话管理网元位于主PLMN中，或者多播/广播会话管理网元位于MOCN中的除所述主PLMN之外的PLMN中。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以指定MOCN中的某一个PLMN作为主要PLMN(简称为主PLMN)，从而使得MOCN中的接入网设备都与该主PLMN的多播/广播用户面功能网元建立共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置为多播/广播会话管理网元，或位于多播/广播会话管理网元中。具体地，通信单元701用于接收来自应用服务器的会话建立请求消息，该会话建立请求消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息。通信单元701还用于向第一会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。其中，主PLMN的标识和第一多播/广播业务的标识信息用于该第一多播/广播会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。需要指出的是，在该实施方式中，处理单元702为可选的，不予限制。
可选的，第一多播/广播会话管理网元和第一会话管理网元位于主PLMN中。
该实施方式中通信单元701的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以向第一会话管理网元发送主PLMN的标识和第一多播/广播业务的标识信息，以使该第一会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置为多播/广播会话管理网元，或位于多播/广播会话管理网元中。具体地，通信单元701用于接收来自应用服务器的会话建立请求消息，该会话建立请求消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息。通信单元701还用于向第二会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。该主PLMN的标识和第一多播/广播业务的标识信息用于该第二多播/广播会话管理网元触发建立该MOCN的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。需要指出的是，在该实施方式中，处理单元702为可选的，不予限制。
可选的，第二多播/广播会话管理网元和第二会话管理网元位于该MOCN中除主PLMN之外的PLMN中。
该实施方式中通信单元701的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以向该第二会话管理网元发送主PLMN的标识和第一多播/广播业务的标识信息，以使该第二会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置为会话管理网元，或位于会话管理网元中。具体地，通信单元701用于接收来自终端设备的多播会话请求消息，该多播会话请求消息包括多播会话的标识。处理单元702用于根据该多播会话的标识，通过通信单元701向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息。通信单元701还用于接收来自多播/广播会话管理网元的多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。其中，主 PLMN的标识和第一多播/广播业务的标识信息用于触发建立该终端设备所接入的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
可选的，通信单元701还用于向多运营商核心网中的接入网设备发送该主PLMN的标识和第一多播/广播业务的标识信息。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以向多播会话的标识对应的多播/广播会话管理网元请求获取多播/广播业务会话上下文，从而获取主PLMN的标识和第一多播/广播业务的标识信息，从而触发建立该终端设备所接入的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置为接入网设备，或位于接入网设备中。具体地，通信单元701用于接收来自第一会话管理网元的第一N2协议数据单元会话资源消息，该第一N2协议数据单元会话资源消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息，该第一接入网设备位于该MOCN中。通信单元701还用于向主PLMN中的多播/广播会话管理网元发送第一N2多播会话请求消息，该第一N2多播会话请求消息包括第一多播/广播业务的标识信息。需要指出的是，在该实施方式中，处理单元702为可选的，不予限制。
可选的，当第一接入网设备未建立共享传输通道时，通信单元701还用于向主PLMN中的多播/广播会话管理网元发送第一多播/广播业务的标识信息。处理单元702用于建立与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
可选的，通信单元701还用于接收来自第二会话管理网元的第二N2协议数据单元会话资源消息，该第二N2协议数据单元会话资源消息包括主PLMN的标识和第一多播/广播业务的标识信息。当第一接入网设备已建立共享传输通道时，处理单元702用于丢弃该第二N2协议数据单元会话资源消息；或者，通信单元701还用于向第二会话管理网元发送第三指示信息，该第三指示信息用于指示该共享传输通道已建立。其中，第一会话管理网元位于主PLMN中，第二会话管理网元位于该MOCN中除主PLMN之外的PLMN中；或者，第一会话管理网元位于该MOCN中除主PLMN之外的PLMN中，第二会话管理网元位于主PLMN中。
可选的，通信单元701还用于向第二接入网设备发送切换请求消息，该切换请求消息包括主PLMN的标识和第一多播/广播业务的标识信息。该主PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与该主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以基于主PLMN的标识，向主PLMN的多播/广播会话管理网元请求建立与该主PLMN的多播/广播用户面功能网元之间的共享传输通道，从而有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置为接入网设备，或位于接入网设备中。具体地，通信单元701用于接收第一多播/广播业务的标识信息。通信单元701还用于向第二接入网设备发送Xn接口消息，该Xn接口消息包括第一多播/广播业务的标识信息以及第一公共陆地移动网络PLMN的标识，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。其中，第一PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据。需要指出的是，在该实施方式中，处理单元702为可选的，不予限制。
可选的，第一接入网设备和第二接入网设备位于多运营商核心网MOCN中，且第一PLMN属于该MOCN。
该实施方式中，通信单元701的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法使得位于MOCN中并且有Xn接口的接入网设备之间，可以通过Xn接***互多播/广播业务的标识信息以及所属PLMN的标识，从而使得在有Xn接口的MOCN中的接入网设备都与相同的多播/广播用户面功能网元建立共享传输通道，有利于实现数据同步。
一种可能的实施方式中，该装置为接入网设备，或位于接入网设备中。具体地，通信单元701用于接收来自第一接入网设备的Xn接口消息，该Xn接口消息包括第一多播/广播业务的标识信息，以及第一PLMN的标识，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输所述第一多播/广播业务的数据。通信单元701还用于接收第二多播/广播业务的标识信息。处理单元702用于根据该第一PLMN的标识、该第一多播/广播业务的标识信息和该第二多播/广播业务的标识信息，建立与该第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据和第二多播/广播业务的数据。其中，第一接入网设备和第二接入网设备位于MOCN中，且第一PLMN属于MOCN。
可选的，当第一多播/广播业务和第二多播/广播业务的类型相同时，通信单元701用于向第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息；或者，当第一多播/广播业务的标识信息对应的多播网络地址与第二多播/广播业务的标识信息对应的多播网络地址相同时，通信单元701用于向第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法使得位于MOCN中并且有Xn接口的第二接入网设备可以通过Xn接口接收其他接入网设备的多播/广播业务的标识信息以及所属PLMN的标识，从而使得在有Xn接口的MOCN中的接入网设备都可以与该PLMN中的多播/广播用户面功能网元建立共享传输通道，有利于实现数据同步。
一种可能的实施方式中，该装置为接入网设备，或位于接入网设备中。具体地，通信单元701用于向第二接入网设备发送切换请求消息，该切换请求消息包括MOCN中第一PLMN的标识和第一多播/广播业务的标识信息，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。通信单元701还用于接收来自第二接入网设备的切换响应消息，该切换响应消息包括第二PLMN的标识，该第二PLMN为与所述第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，该切换响应消息包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN。其中，第一接入网设备和第二接入网设备位于MOCN中，第一PLMN和第二PLMN不同。需要指出的是，在该实施方式中，处理单元702为可选的，不予限制。
可选的，通信单元701还用于根据第二PLMN的标识或第四指示信息，向所述第二接入网设备转发所述第一多播/广播业务的数据。
可选的，通信单元701还用于接收第一N2协议数据单元会话资源消息，该第一N2协议数据单元会话资源消息包括第一PLMN的标识和第一多播/广播业务的标识信息。处理单元702用于根据该第一PLMN的标识和第一多播/广播业务的标识信息，建立与第一PLMN中的多播/广播用户面功能网元之间的第一共享传输通道。
可选的，切换请求消息用于请求将终端设备从第一接入网设备切换至第二接入网设备，该切换请求消息还包括终端设备所属的PLMN的标识。
该实施方式中，通信单元701的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以向第二接入网设备发送第一接入网设备所属的第一PLMN的标识，有利于使第二接入网设备基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
一种可能的实施方式中，该装置为接入网设备，或位于接入网设备中。具体地，通信单元701用于接收来自第一接入网设备的切换请求消息，该切换请求消息包括MOCN中第一PLMN的标识和第一多播/广播业务的标识信息，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。通信单元701还用于向第一接入网设备发送切换响应消息，该切换响应消息包括第二PLMN的标识，第二PLMN为与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，该切换响应消息包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN。其中，第一接入网设备和第二接入网设备位于该MOCN中，第一PLMN和第二PLMN不同。需要指出的是，在该实施方式中，处理单元702为可选的，不予限制。
可选的，当第二接入网设备未建立用于传输第一多播/广播业务的数据的第二共享传输通道时，处理单 元702用于根据第一PLMN的标识和第一多播/广播业务的标识信息，建立与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道。
可选的，当第二接入网设备已建立用于传输第一多播/广播业务的数据的第二共享传输通道时，切换响应消息包括第二共享传输通道对应的PLMN的标识，或者，切换响应消息包括所述第四指示信息。
可选的，当第二共享传输通道对应的PLMN的标识与第一PLMN的标识不同时，通信单元701用于接收来自述第一接入网设备的第一多播/广播业务的数据。处理单元702用于使用单播方式转发该第一多播/广播业务的数据。
可选的，切换请求消息用于请求将终端设备从第一接入网设备切换至第二接入网设备，该切换请求消息还包括终端设备所属的PLMN的标识。
可选的，处理单元702用于根据第一PLMN的标识，或所述第二PLMN的标识，或所述终端设备所属的PLMN的标识，建立第二共享传输通道。
该实施方式中通信单元701和处理单元702的具体执行流程还可以参考前文方法实施例中对应的描述，此处不再赘述。该装置所实现的通信方法可以接收第一接入网设备所属的第一PLMN的标识，使得第二接入网设备基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
图8为本申请提供的另一种通信装置的示意图，用于实现上述各方法实施例中的通信方法。该装置800也可以是芯片***，也可以是上述方法实施例中描述的网元或设备。
其中，装置800包括通信接口801和处理器802。通信接口801例如可以是收发器、接口、总线、电路或者能够实现收发功能的装置。其中，通信接口801用于通过传输介质和其它设备进行通信，从而用于装置800可以和其它设备进行通信。处理器802用于执行处理相关的操作。
一种可能的实施方式中，该装置800可以为多播/广播会话管理网元，也可以位于多播/广播会话管理网元中，具体地，通信接口801用于接收来自应用服务器的第一会话建立请求消息，该第一会话建立请求消息包括第一多播/广播业务的标识信息和MOCN中第一PLMN的标识。处理器802用于根据第一会话建立请求消息，通过通信接口801向第一多播/广播用户面功能网元发送第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号；其中，第一多播/广播会话管理网元和第一多播/广播用户面功能网元位于第一PLMN中。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以指示对应的第一多播/广播用户面功能网元进行特殊的配置，例如，指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号(例如将第一序列号加1)。从而使得第一多播/广播用户面功能网元根据第一多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，有利于实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置800可以为多播/广播会话管理网元，也可以位于多播/广播会话管理网元中，具体地，通信接口801用于接收来自应用服务器的第二会话建立请求消息，该第二会话建立请求消息包括第一多播/广播业务的标识信息和MOCN中第二PLMN的标识。处理器802用于根据第二会话建立请求消息，通过通信接口801向第二多播/广播用户面功能网元发送第二指示信息，该第二指示信息用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号；其中，第二多播/广播会话管理网元和第二多播/广播用户面功能网元位于第二PLMN中。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以指示对应的第二多播/广播用户面功能网元进行特殊的配置，例如，指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号(例如将第二序列号加1)。从而使得第二多播/广播用户面功能网元根据第二多播/广播会话管理网元的指示，同步更新相同多播/广播业务的数据的序列号，从而实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置800可以为多播/广播用户面功能网元，也可以位于多播/广播用户面功能网元中，具体地，通信接口801用于接收来自多播/广播会话管理网元的第一指示信息，该第一指示信息用于指示第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增该数据对应的第一序 列号。通信接口801还用于接收来自应用服务器的第一多播/广播业务的数据；处理器802用于根据该第一指示信息，递增该数据对应的第一序列号。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以根据指示对用户面的处理进行特殊配置，例如，在接收到第一多播/广播业务的数据时递增该数据对应的第一序列号，而不管是否会向接入网设备发送该数据。从而使得第一多播/广播用户面功能网元可以同步更新相同多播/广播业务的数据的序列号，实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置800可以为多播/广播用户面功能网元，也可以位于多播/广播用户面功能网元中，具体地，通信接口801用于接收来自第二多播/广播会话管理网元的第二指示信息，该第二指示信息用于指示第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时，递增该数据对应的第二序列号。通信接口801还用于接收来自应用服务器的第一多播/广播业务的数据；处理器802用于根据该第二指示信息，递增该数据对应的第二序列号。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以指示对用户面的处理进行特殊配置，例如，在接收到第一多播/广播业务的数据时递增该数据对应的第二序列号，而不管是否会向接入网设备发送该数据。从而使得第二多播/广播用户面功能网元可以同步更新相同多播/广播业务的数据的序列号，实现相同多播/广播业务的数据的序列号在不同PLMN中同步。
一种可能的实施方式中，该装置800可以为应用服务器，也可以位于应用服务器中，具体地，处理器802用于通过通信接口801向位于MOCN的第一PLMN中的第一多播/广播会话管理网元发送第一会话建立请求消息，该第一会话建立请求消息包括第一PLMN的标识和第一多播/广播业务的标识信息。处理器802还用于通过通信接口801向位于MOCN的第二PLMN中的第二多播/广播会话管理网元发送第二会话建立请求消息，该第二会话建立请求消息包括第二PLMN的标识和第一多播/广播业务的标识信息；其中，第一PLMN与第二PLMN不同。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以向MOCN的不同PLMN中的多播/广播会话管理网元发送第一多播/广播业务的标识信息，不同PLMN中的多播/广播会话管理网元再向分别对应的多播/广播用户面功能网元发送指示信息，有利于使得不同PLMN中的多播/广播用户面功能网元同时接收来自应用服务器的第一多播/广播业务的数据，并同步更新针对该第一多播/广播业务的数据的序列号，从而有利于实现数据同步。
一种可能的实施方式中，该装置800可以为应用服务器，也可以位于应用服务器中，具体地，处理器802用于生成会话建立请求消息，该会话建立请求消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息。通信接口801用于向多播/广播会话管理网元发送该会话建立请求消息。其中，该主PLMN的标识和该第一多播/广播业务的标识信息用于多播/广播会话管理网元触发建立MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输该第一多播/广播业务的数据。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以指定MOCN中的某一个PLMN作为主PLMN，从而使得MOCN中的接入网设备都与该主PLMN的多播/广播用户面功能网元建立共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为多播/广播会话管理网元，也可以位于多播/广播会话管理网元中，具体地，通信接口801用于接收来自应用服务器的会话建立请求消息，该会话建立请求消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息。处理器802用于通过通信接口801向第一会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。其中，主PLMN的标识和第一多播/广播业务的标识信息用于该第一多播/广播会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以向第一会话管理网元 发送主PLMN的标识和第一多播/广播业务的标识信息，以使该第一会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为多播/广播会话管理网元，也可以位于多播/广播会话管理网元中，具体地，通信接口801用于接收来自应用服务器的会话建立请求消息，该会话建立请求消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息。处理器802用于通过通信接口801向第二会话管理网元发送多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。该主PLMN的标识和第一多播/广播业务的标识信息用于该第二多播/广播会话管理网元触发建立该MOCN的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以向该第二会话管理网元发送主PLMN的标识和第一多播/广播业务的标识信息，以使该第二会话管理网元触发建立该MOCN中的接入网设备与主PLMN中的多播/广播用户面功能网元之间的共享传输通道，从而使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为会话管理网元，也可以位于会话管理网元中，具体地，通信接口801用于接收来自终端设备的多播会话请求消息，该多播会话请求消息包括多播会话的标识。处理器802用于根据该多播会话的标识，通过通信接口801向该多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息。通信接口801还用于接收来自多播/广播会话管理网元的多播/广播业务会话上下文，该多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息。其中，主PLMN的标识和第一多播/广播业务的标识信息用于触发建立该终端设备所接入的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，该共享传输通道用于传输第一多播/广播业务的数据。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以向多播会话的标识对应的多播/广播会话管理网元请求获取多播/广播业务会话上下文，从而获取主PLMN的标识和第一多播/广播业务的标识信息，从而触发建立该终端设备所接入的接入网设备与主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为接入网设备，也可以位于接入网设备中，具体地，通信接口801用于接收来自第一会话管理网元的第一N2协议数据单元会话资源消息，该第一N2协议数据单元会话资源消息包括MOCN中主PLMN的标识和第一多播/广播业务的标识信息，该第一接入网设备位于该MOCN中。处理器802用于通过通信接口801向主PLMN中的多播/广播会话管理网元发送第一N2多播会话请求消息，该第一N2多播会话请求消息包括第一多播/广播业务的标识信息。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以基于主PLMN的标识，向主PLMN的多播/广播会话管理网元请求建立与该主PLMN的多播/广播用户面功能网元之间的共享传输通道，从而有利于使得该主PLMN的多播/广播用户面功能网元针对相同多播/广播业务的数据使用相同的序列号，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为接入网设备，也可以位于接入网设备中，具体地，通信接口801用于接收第一多播/广播业务的标识信息。处理器802用于通过通信接口801向第二接入网设备发送Xn接口消息，该Xn接口消息包括第一多播/广播业务的标识信息以及第一公共陆地移动网络PLMN的标识，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。其中，第一PLMN的标识和第一多播/广播业务的标识信息用于触发建立第二接入网设备与第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法使得位于MOCN中并且有Xn接口的接入网设备之间，可以通过Xn接***互多播/广播业务的标识信息以及所属PLMN的标识， 从而使得在有Xn接口的MOCN中的接入网设备都与相同的多播/广播用户面功能网元建立共享传输通道，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为接入网设备，也可以位于接入网设备中，具体地，通信接口801用于接收来自第一接入网设备的Xn接口消息，该Xn接口消息包括第一多播/广播业务的标识信息，以及第一PLMN的标识，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输所述第一多播/广播业务的数据。通信接口801还用于接收第二多播/广播业务的标识信息。处理器802用于根据该第一PLMN的标识、该第一多播/广播业务的标识信息和该第二多播/广播业务的标识信息，建立与该第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，该第二共享传输通道用于传输第一多播/广播业务的数据和第二多播/广播业务的数据。其中，第一接入网设备和第二接入网设备位于MOCN中，且第一PLMN属于MOCN。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法使得位于MOCN中并且有Xn接口的第二接入网设备可以通过Xn接口接收其他接入网设备的多播/广播业务的标识信息以及所属PLMN的标识，从而使得在有Xn接口的MOCN中的接入网设备都可以与该PLMN中的多播/广播用户面功能网元建立共享传输通道，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为接入网设备，也可以位于接入网设备中，具体地，处理器802用于通过通信接口801向第二接入网设备发送切换请求消息，该切换请求消息包括MOCN中第一PLMN的标识和第一多播/广播业务的标识信息，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。通信接口801还用于接收来自第二接入网设备的切换响应消息，该切换响应消息包括第二PLMN的标识，该第二PLMN为与所述第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，该切换响应消息包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN。其中，第一接入网设备和第二接入网设备位于MOCN中，第一PLMN和第二PLMN不同。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以向第二接入网设备发送第一接入网设备所属的第一PLMN的标识，有利于使第二接入网设备基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
一种可能的实施方式中，该装置800可以为接入网设备，也可以位于接入网设备中，具体地，通信接口801用于接收来自第一接入网设备的切换请求消息，该切换请求消息包括MOCN中第一PLMN的标识和第一多播/广播业务的标识信息，该第一PLMN为与第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，该第一共享传输通道用于传输第一多播/广播业务的数据。处理器802用于通过通信接口801向第一接入网设备发送切换响应消息，该切换响应消息包括第二PLMN的标识，第二PLMN为与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，该切换响应消息包括第四指示信息，该第四指示信息用于指示与第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于第一PLMN。其中，第一接入网设备和第二接入网设备位于该MOCN中，第一PLMN和第二PLMN不同。
该实施方式中通信接口801和处理器802的具体执行流程还可以参考图7实施例中通信单元和处理单元所执行的方法，以及前文方法实施例中的描述，此处不再赘述。该设备所实现的通信方法可以接收第一接入网设备所属的第一PLMN的标识，使得第二接入网设备基于第一PLMN的标识，向第一PLMN的多播/广播会话管理网元请求建立与该第一PLMN的多播/广播用户面功能网元之间的共享传输通道，从而使得相同的多播/广播业务的数据通过同一共享传输通道传输，有利于实现数据同步。
可选的，该装置800还可以包括至少一个存储器803，用于存储程序指令和/或数据。一种实施方式中，存储器和处理器耦合。本申请中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器可能和存储器协同操作。处理器可能执行存储器中存储的程序指令。所述至少一个存储器和处理器集成在一起。
本申请中不限定上述通信接口、处理器以及存储器之间的具体连接介质。例如，存储器、处理器以及通信接口之间通过总线连接，总线804在图8中以粗线表示，其它部件之间的连接方式，仅是进行示意性 说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图8中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
本申请提供一种通信装置，该装置包括处理器，处理器与存储器耦合，处理器用于读取并执行存储器中存储的计算机指令，以实现如图3a至图6所示的任一实施例中的通信方法。
本申请提供一种通信***，该通信***包括如图3a至图6所示的任一实施例中的各个网元或设备中的一种或多种。
本申请提供一种计算机可读存储介质。该计算机可读存储介质存储有程序或指令。当所述程序或指令在计算机上运行时，使得计算机执行如图3a至图6所示的任一实施例中的通信方法。
本申请中提供一种计算机程序产品。该计算机程序产品包括指令。当所述指令在计算机上运行时，使得计算机执行如图3a至图6所示的任一实施例中的通信方法。
本申请提供一种芯片或者芯片***，该芯片或者芯片***包括至少一个处理器和接口，接口和至少一个处理器通过线路互联，至少一个处理器用于运行计算机程序或指令，以执行如图3a至图6所示的任一实施例中的通信方法。
其中，芯片中的接口可以为输入/输出接口、管脚或电路等。
上述芯片***可以是片上***(system on chip，SOC)，也可以是基带芯片等，其中基带芯片可以包括处理器、信道编码器、数字信号处理器、调制解调器和接口模块等。
在一种实现方式中，本申请中上述描述的芯片或者芯片***还包括至少一个存储器，该至少一个存储器中存储有指令。该存储器可以为芯片内部的存储单元，例如，寄存器、缓存等，也可以是该芯片的存储单元(例如，只读存储器、随机存取存储器等)。
本申请提供的技术方案可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端设备或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质等。
在本申请中，在无逻辑矛盾的前提下，各实施例之间可以相互引用，例如方法实施例之间的方法和/或术语可以相互引用，例如装置实施例之间的功能和/或术语可以相互引用，例如装置实施例和方法实施例之间的功能和/或术语可以相互引用。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (38)

  1. 一种通信方法，其特征在于，包括：
    第一多播/广播会话管理网元接收来自应用服务器的第一会话建立请求消息，所述第一会话建立请求消息包括第一多播/广播业务的标识信息；
    所述第一多播/广播会话管理网元根据所述第一会话建立请求消息，向第一多播/广播用户面功能网元发送第一指示信息，所述第一指示信息用于指示所述第一多播/广播用户面功能网元在接收到所述第一多播/广播业务的数据时递增所述数据对应的第一序列号；
    其中，所述第一多播/广播会话管理网元和所述第一多播/广播用户面功能网元位于多运营商核心网MOCN的第一公共陆地移动网络PLMN中。
  2. 根据权利要求1所述的方法，其特征在于，所述第一会话建立请求消息还包括所述第一PLMN的标识；
    所述第一序列号用于所述MOCN中的接入网设备识别来自所述第一PLMN的所述第一多播/广播业务的数据。
  3. 一种通信方法，其特征在于，包括：
    第二多播/广播会话管理网元接收来自应用服务器的第二会话建立请求消息，所述第二会话建立请求消息包括第一多播/广播业务的标识信息；
    所述第二多播/广播会话管理网元根据所述第二会话建立请求消息，向第二多播/广播用户面功能网元发送第二指示信息，所述第二指示信息用于指示所述第二多播/广播用户面功能网元在接收到所述第一多播/广播业务的数据时递增所述数据对应的第二序列号；
    其中，所述第二多播/广播会话管理网元和所述第二多播/广播用户面功能网元位于多运营商核心网MOCN的第二公共陆地移动网络PLMN中。
  4. 根据权利要求3所述的方法，其特征在于，所述第二会话建立请求消息还包括所述第二PLMN的标识；
    所述第二序列号用于所述MOCN中的接入网设备识别来自所述第二PLMN的所述第一多播/广播业务的数据。
  5. 一种通信方法，其特征在于，包括：
    第一多播/广播用户面功能网元接收来自多播/广播会话管理网元的第一指示信息，所述第一指示信息用于指示所述第一多播/广播用户面功能网元在接收到第一多播/广播业务的数据时递增所述数据对应的第一序列号；
    所述第一多播/广播用户面功能网元接收来自应用服务器的所述第一多播/广播业务的数据；
    所述第一多播/广播用户面功能网元根据所述第一指示信息，递增所述数据对应的所述第一序列号。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一多播/广播用户面功能网元向多运营商核心网MOCN中的接入网设备发送所述第一多播/广播业务的数据以及所述数据对应的所述第一序列号，
    所述第一多播/广播用户面功能网元位于所述MOCN的第一PLMN中，所述第一序列号用于所述接入网设备识别来自所述第一PLMN的所述第一多播/广播业务的数据。
  7. 一种通信方法，其特征在于，包括：
    第二多播/广播用户面功能网元接收来自第二多播/广播会话管理网元的第二指示信息，所述第二指示信息用于指示所述第二多播/广播用户面功能网元在接收到第一多播/广播业务的数据时，递增所述数据对应的第二序列号；
    所述第二多播/广播用户面功能网元接收来自应用服务器的所述第一多播/广播业务的数据；
    所述第二多播/广播用户面功能网元根据所述第二指示信息，递增所述数据对应的所述第二序列号。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述第二多播/广播用户面功能网元向多运营商核心网MOCN中的接入网设备发送所述第一多播/广播业务的数据以及所述数据对应的所述第二序列号，
    所述第二多播/广播用户面功能网元位于所述MOCN的第二PLMN中，所述第二序列号用于所述接入网设备识别来自所述第二PLMN的所述第一多播/广播业务的数据。
  9. 根据权利要求1所述的方法，其特征在于，所述第一会话建立请求消息还包括所述多播/广播业务的类型；
    所述第一多播/广播会话管理网元根据所述第一会话建立请求消息，向第一多播/广播用户面功能网元发送第一指示信息，包括：
    当所述第一多播/广播业务的类型为多播业务时，所述第一多播/广播会话管理网元向所述第一多播/广播用户面功能网元发送所述第一指示信息。
  10. 根据权利要求1所述的方法，其特征在于，所述第一会话建立请求消息还包括网络共享标识信息；所述网络共享标识信息用于指示所述第一多播/广播业务在所述MOCN的第二PLMN的临时多播群组标识TMGI列表中共享，所述第二PLMN与所述第一PLMN不同；
    所述第一多播/广播会话管理网元根据所述第一会话建立请求消息，向第一多播/广播用户面功能网元发送第一指示信息，包括：
    所述第一多播/广播会话管理网元根据所述网络共享标识信息，向所述第一多播/广播用户面功能网元发送所述第一指示信息。
  11. 根据权利要求1所述的方法，其特征在于，所述第一指示信息包括所述第一序列号的起始值，所述第一序列号的起始值与所述第一多播/广播业务的数据在所述MOCN的第二PLMN中对应的第二序列号的起始值相同。
  12. 一种通信方法，其特征在于，包括：
    应用服务器向位于多运营商核心网MOCN的第一公共陆地移动网络PLMN中的第一多播/广播会话管理网元发送第一会话建立请求消息，所述第一会话建立请求消息包括第一多播/广播业务的标识信息；
    所述应用服务器向位于所述MOCN的第二PLMN中的第二多播/广播会话管理网元发送第二会话建立请求消息，所述第二会话建立请求消息包括所述第一多播/广播业务的标识信息；
    其中，所述第一PLMN与所述第二PLMN不同。
  13. 根据权利要求12所述的方法，其特征在于，所述第一会话请求消息还包括所述第一PLMN的标识和/或所述第一多播/广播业务的数据在所述第一PLMN中对应的第一序列号的起始值；
    所述第二会话请求消息还包括所述第二PLMN的标识和/或所述第一多播/广播业务的数据在所述第二PLMN中对应的第二序列号的起始值；
    其中，所述第一序列号的起始值与所述第二序列号的起始值相同。
  14. 一种通信方法，其特征在于，包括：
    应用服务器生成会话建立请求消息，所述会话建立请求消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息；
    所述应用服务器向多播/广播会话管理网元发送所述会话建立请求消息；
    其中，所述主PLMN的标识和所述第一多播/广播业务的标识信息用于所述多播/广播会话管理网元触发建立所述MOCN中的接入网设备与所述主PLMN中的多播/广播用户面功能网元之间的共享传输通道，所述共享传输通道用于传输所述第一多播/广播业务的数据；
    所述多播/广播会话管理网元位于所述主PLMN中，或者所述多播/广播会话管理网元位于所述MOCN中的除所述主PLMN之外的PLMN中。
  15. 一种通信方法，其特征在于，包括：
    第一多播/广播会话管理网元接收来自应用服务器的会话建立请求消息，所述会话建立请求消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息；
    所述第一多播/广播会话管理网元向第一会话管理网元发送多播/广播业务会话上下文，所述多播/广播业务会话上下文包括所述主PLMN的标识和所述第一多播/广播业务的标识信息；
    其中，所述主PLMN的标识和所述第一多播/广播业务的标识信息用于所述第一多播/广播会话管理网元触发建立所述MOCN中的接入网设备与所述主PLMN中的多播/广播用户面功能网元之间的共享传输通道，所述共享传输通道用于传输所述第一多播/广播业务的数据；
    其中，所述第一多播/广播会话管理网元和所述第一会话管理网元位于所述主PLMN中。
  16. 一种通信方法，其特征在于，包括：
    第二多播/广播会话管理网元接收来自应用服务器的会话建立请求消息，所述会话建立请求消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息；
    所述第二多播/广播会话管理网元向第二会话管理网元发送多播/广播业务会话上下文，所述多播/广播业务会话上下文包括所述主PLMN的标识和所述第一多播/广播业务的标识信息；
    其中，所述主PLMN的标识和所述第一多播/广播业务的标识信息用于所述第二多播/广播会话管理网 元触发建立所述MOCN的接入网设备与所述主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，所述共享传输通道用于传输所述第一多播/广播业务的数据；
    其中，所述第二多播/广播会话管理网元和所述第二会话管理网元位于所述MOCN中除所述主PLMN之外的PLMN中。
  17. 一种通信方法，其特征在于，包括：
    第二会话管理网元接收来自终端设备的多播会话请求消息，所述多播会话请求消息包括多播会话的标识；
    所述第二会话管理网元根据所述多播会话的标识，向所述多播会话的标识对应的多播/广播会话管理网元发送多播/广播业务会话上下文请求消息；
    所述第二会话管理网元接收来自所述多播/广播会话管理网元的多播/广播业务会话上下文，所述多播/广播业务会话上下文包括主PLMN的标识和第一多播/广播业务的标识信息；
    其中，所述主PLMN的标识和所述第一多播/广播业务的标识信息用于触发建立所述终端设备所接入的接入网设备与所述主PLMN的标识对应的多播/广播用户面功能网元之间的共享传输通道，所述共享传输通道用于传输所述第一多播/广播业务的数据；
    其中，所述第二会话管理网元位于所述MOCN中除所述主PLMN之外的PLMN中。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述第二会话管理网元向多运营商核心网中的接入网设备发送所述主PLMN的标识和所述第一多播/广播业务的标识信息。
  19. 一种通信方法，其特征在于，包括：
    第一接入网设备接收来自第一会话管理网元的第一N2协议数据单元会话资源消息，所述第一N2协议数据单元会话资源消息包括多运营商核心网MOCN中主公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息，所述第一接入网设备位于所述MOCN中；
    所述第一接入网设备向所述主PLMN中的多播/广播会话管理网元发送第一N2多播会话请求消息，所述第一N2多播会话请求消息包括所述第一多播/广播业务的标识信息。
  20. 根据权利要求19所述的方法，其特征在于，所述第一接入网设备向所述主PLMN中的多播/广播会话管理网元发送N2多播会话请求消息，包括：
    当所述第一接入网设备未建立共享传输通道时，所述第一接入网设备向所述主PLMN中的多播/广播会话管理网元发送所述第一多播/广播业务的标识信息；
    所述第一接入网设备建立与所述主PLMN中的所述多播/广播用户面功能网元之间的共享传输通道，所述共享传输通道用于传输所述第一多播/广播业务的数据。
  21. 根据权利要求19或20所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备接收来自第二会话管理网元的第二N2协议数据单元会话资源消息，所述第二N2协议数据单元会话资源消息包括所述主PLMN的标识和所述第一多播/广播业务的标识信息；
    当所述第一接入网设备已建立共享传输通道时，所述第一接入网设备丢弃所述第二N2协议数据单元会话资源消息；或者，所述第一接入网设备向所述第二会话管理网元发送第三指示信息，所述第三指示信息用于指示所述共享传输通道已建立；
    其中，所述第一会话管理网元位于所述主PLMN中，所述第二会话管理网元位于所述MOCN中除所述主PLMN之外的PLMN中；或者，所述第一会话管理网元位于所述MOCN中除所述主PLMN之外的PLMN中，所述第二会话管理网元位于所述主PLMN中。
  22. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备向第二接入网设备发送切换请求消息，所述切换请求消息包括所述主PLMN的标识和所述第一多播/广播业务的标识信息；
    其中，所述主PLMN的标识和所述第一多播/广播业务的标识信息用于触发建立所述第二接入网设备与所述主PLMN中的多播/广播用户面功能网元之间的共享传输通道，所述共享传输通道用于传输所述第一多播/广播业务的数据。
  23. 一种通信方法，其特征在于，包括：
    第一接入网设备接收第一多播/广播业务的标识信息；
    所述第一接入网设备向第二接入网设备发送Xn接口消息，所述Xn接口消息包括所述第一多播/广播业务的标识信息以及第一公共陆地移动网络PLMN的标识，所述第一PLMN为与所述第一接入网设备建 立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，所述第一共享传输通道用于传输所述第一多播/广播业务的数据；
    其中，所述第一PLMN的标识和所述第一多播/广播业务的标识信息用于触发建立所述第二接入网设备与所述第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，所述第二共享传输通道用于传输所述第一多播/广播业务的数据；
    其中，所述第一接入网设备和所述第二接入网设备位于多运营商核心网MOCN中，且所述第一PLMN属于所述MOCN。
  24. 一种通信方法，其特征在于，包括：
    第二接入网设备接收来自第一接入网设备的Xn接口消息，所述Xn接口消息包括第一多播/广播业务的标识信息，以及第一公共陆地移动网络PLMN的标识，所述第一PLMN为与所述第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，所述第一共享传输通道用于传输所述第一多播/广播业务的数据；
    所述第二接入网设备接收第二多播/广播业务的标识信息；
    所述第二接入网设备根据所述第一PLMN的标识、所述第一多播/广播业务的标识信息和所述第二多播/广播业务的标识信息，建立与所述第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，所述第二共享传输通道用于传输所述第一多播/广播业务的数据和所述第二多播/广播业务的数据；
    其中，所述第一接入网设备和所述第二接入网设备位于MOCN中，且所述第一PLMN属于所述MOCN。
  25. 根据权利要求24所述的方法，其特征在于，所述第二接入网设备根据所述第一PLMN的标识、所述第一多播/广播业务的标识信息和所述第二多播/广播业务的标识信息，建立与所述第一PLMN中的多播/广播用户面功能网元之间的第二共享传输通道，包括：
    当所述第一多播/广播业务和所述第二多播/广播业务的类型相同时，所述第二接入网设备向所述第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息；或者，
    当所述第一多播/广播业务的标识信息对应的多播网络地址与所述第二多播/广播业务的标识信息对应的多播网络地址相同时，所述第二接入网设备向所述第一PLMN中的多播/广播用户面功能网元发送共享传输通道建立请求消息。
  26. 一种通信方法，其特征在于，包括：
    第一接入网设备向第二接入网设备发送切换请求消息，所述切换请求消息包括多运营商核心网MOCN中第一公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息，所述第一PLMN为与所述第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，所述第一共享传输通道用于传输所述第一多播/广播业务的数据；
    所述第一接入网设备接收来自所述第二接入网设备的切换响应消息，所述切换响应消息包括第二PLMN的标识，所述第二PLMN为与所述第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，所述切换响应消息包括第四指示信息，所述第四指示信息用于指示与所述第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于所述第一PLMN；
    其中，所述第一接入网设备和所述第二接入网设备位于所述MOCN中，所述第一PLMN和所述第二PLMN不同。
  27. 根据权利要求26所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备根据所述第二PLMN的标识或所述第四指示信息，向所述第二接入网设备转发所述第一多播/广播业务的数据。
  28. 根据权利要求26所述的方法，其特征在于，所述第一接入网设备向第二接入网设备发送切换请求消息之前，所述方法还包括：
    所述第一接入网设备接收第一N2协议数据单元会话资源消息，所述第一N2协议数据单元会话资源消息包括所述第一PLMN的标识和所述第一多播/广播业务的标识信息；
    所述第一接入网设备根据所述第一PLMN的标识和所述第一多播/广播业务的标识信息，建立与所述第一PLMN中的多播/广播用户面功能网元之间的所述第一共享传输通道。
  29. 一种通信方法，其特征在于，包括：
    第二接入网设备接收来自第一接入网设备的切换请求消息，所述切换请求消息包括多运营商核心网MOCN中第一公共陆地移动网络PLMN的标识和第一多播/广播业务的标识信息，所述第一PLMN为与所述第一接入网设备建立第一共享传输通道的多播/广播用户面功能网元所属的PLMN，所述第一共享传输通 道用于传输所述第一多播/广播业务的数据；
    所述第二接入网设备向所述第一接入网设备发送切换响应消息，所述切换响应消息包括第二PLMN的标识，所述第二PLMN为与所述第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元所属的PLMN；或者，所述切换响应消息包括第四指示信息，所述第四指示信息用于指示与所述第二接入网设备建立第二共享传输通道的多播/广播用户面功能网元属于所述第一PLMN；
    其中，所述第一接入网设备和所述第二接入网设备位于所述MOCN中，所述第一PLMN和所述第二PLMN不同。
  30. 根据权利要求29所述的方法，其特征在于，所述第二接入网设备向所述第一接入网设备发送切换响应消息之前，所述方法还包括：
    当所述第二接入网设备未建立用于传输所述第一多播/广播业务的数据的第二共享传输通道时，所述第二接入网设备根据所述第一PLMN的标识和所述第一多播/广播业务的标识信息，建立与所述第一PLMN中的多播/广播用户面功能网元之间的所述第二共享传输通道。
  31. 根据权利要求29所述的方法，其特征在于，当所述第二接入网设备已建立用于传输所述第一多播/广播业务的数据的第二共享传输通道时，所述切换响应消息包括所述第二共享传输通道对应的PLMN的标识，或者，所述切换响应消息包括所述第四指示信息。
  32. 根据权利要求31所述的方法，其特征在于，所述方法还包括：
    当所述第二共享传输通道对应的PLMN的标识与所述第一PLMN的标识不同时，所述第二接入网设备接收来自所述第一接入网设备的所述第一多播/广播业务的数据；
    所述第二接入网设备使用单播方式转发所述第一多播/广播业务的数据。
  33. 一种通信装置，其特征在于，包括处理单元和通信单元，所述处理单元和通信单元用于执行如权利要求1至32中任一项所述的方法。
  34. 一种通信装置，其特征在于，包括：处理器和存储器，所述存储器用于存储指令，当所述指令被所述处理器执行时，使得该通信设备执行如权利要求1至32中任一项所述的方法。
  35. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至32中任一项所述的方法。
  36. 一种芯片***，其特征在于，所述芯片***包括处理器、存储器和接口，所述处理器和接口用于执行如权利要求1至32中任一项所述的方法。
  37. 一种通信***，其特征在于，包括通信装置，所述通信装置用于执行如权利要求1至32中任一项所述的方法。
  38. 一种计算机程序产品，其特征在于，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至32中任一项所述的方法。
PCT/CN2023/135528 2022-12-08 2023-11-30 一种通信方法和通信装置 WO2024120299A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211572149.8 2022-12-08
CN202211572149.8A CN118175510A (zh) 2022-12-08 2022-12-08 一种通信方法和通信装置

Publications (1)

Publication Number Publication Date
WO2024120299A1 true WO2024120299A1 (zh) 2024-06-13

Family

ID=91357162

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/135528 WO2024120299A1 (zh) 2022-12-08 2023-11-30 一种通信方法和通信装置

Country Status (2)

Country Link
CN (1) CN118175510A (zh)
WO (1) WO2024120299A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190124623A1 (en) * 2016-04-28 2019-04-25 Nokia Technologies Oy Method and apparatus for providing broadcast/multicast services
US20190364534A1 (en) * 2016-09-08 2019-11-28 Neil GINSBURG Network entities, a wireless communication system and a method for collecting data for multiple mobile network operators
CN115175255A (zh) * 2021-04-01 2022-10-11 华为技术有限公司 一种多播广播业务的传输切换方法及装置
WO2022262589A1 (zh) * 2021-06-16 2022-12-22 华为技术有限公司 一种会话建立方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190124623A1 (en) * 2016-04-28 2019-04-25 Nokia Technologies Oy Method and apparatus for providing broadcast/multicast services
US20190364534A1 (en) * 2016-09-08 2019-11-28 Neil GINSBURG Network entities, a wireless communication system and a method for collecting data for multiple mobile network operators
CN115175255A (zh) * 2021-04-01 2022-10-11 华为技术有限公司 一种多播广播业务的传输切换方法及装置
WO2022262589A1 (zh) * 2021-06-16 2022-12-22 华为技术有限公司 一种会话建立方法及装置

Also Published As

Publication number Publication date
CN118175510A (zh) 2024-06-11

Similar Documents

Publication Publication Date Title
US11425537B2 (en) Communications system, communication method, and apparatus thereof
JP7048745B2 (ja) 通信方法および関連製品
WO2020147761A1 (zh) 一种pdu会话切换方法及其装置
WO2021164564A1 (zh) 传输组播业务的方法和装置
WO2021088660A1 (zh) 通信方法、装置及设备
EP4027684A1 (en) Service configuration method, communication device, and communication system
WO2021088661A1 (zh) 通信方法、装置及设备
WO2015018232A1 (zh) 设备到设备连接管理方法、装置及基站
WO2022033168A1 (zh) 一种mbs业务数据传输方法和网络侧装置及设备
WO2021097858A1 (zh) 一种通信方法及装置
US20220408317A1 (en) Handover method and communication apparatus
JP2022551395A (ja) データ伝送方法並びにその装置、コンピュータプログラム、制御装置及びアプリケーションサーバ
WO2023029590A1 (zh) 一种组播/广播会话管理方法及通信装置
WO2023000884A1 (zh) 多播会话处理方法、网络功能实体、装置及存储介质
WO2022037441A1 (zh) Mbms业务的传输模式指示方法、装置及存储介质
WO2024120299A1 (zh) 一种通信方法和通信装置
WO2022206775A1 (zh) 一种多播广播业务的传输切换方法及装置
WO2022179434A1 (zh) 组播/广播业务的通信方法、装置及***
KR20240019328A (ko) 세션 설정 방법 및 장치
EP4021072A1 (en) Data processing method, apparatus, and system
WO2024067475A1 (zh) 数据传输方法和通信装置
EP4369745A1 (en) Communication method and apparatus
WO2022165919A1 (zh) 一种通信方法及装置
WO2024120268A1 (zh) 一种信息处理方法、装置及设备
WO2023103575A1 (zh) 组播/广播通信的方法与相关装置