WO2024120299A1 - Procédé de communication et appareil de communication - Google Patents

Procédé de communication et appareil de communication 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)
Chinese (zh)
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/fr

Links

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

  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande propose un procédé de communication et un appareil de communication. Un premier élément de réseau de gestion de session de multidiffusion/diffusion reçoit des informations d'identification d'un premier service de multidiffusion/diffusion en provenance d'un serveur d'applications ; et le premier élément de réseau de gestion de session de multidiffusion/diffusion envoie de premières informations d'instruction à un premier élément de réseau de fonction de plan d'utilisateur de multidiffusion/diffusion correspondant, les premières informations d'instruction étant utilisées pour ordonner au premier élément de réseau de fonction de plan d'utilisateur de multidiffusion/diffusion d'augmenter progressivement, lorsque des données du premier service de multidiffusion/diffusion sont reçues, un premier numéro d'ordre correspondant aux données. Dans le procédé, un élément de réseau de gestion de session de multidiffusion/diffusion dans un MOCN peut ordonner à un élément de réseau de fonction de plan d'utilisateur de multidiffusion/diffusion correspondant d'effectuer une configuration particulière, de telle sorte qu'un élément de réseau de fonction de plan d'utilisateur de multidiffusion/diffusion dans le MOCN peut mettre à jour de manière synchrone le numéro d'ordre de données du même service de multidiffusion/diffusion, ce qui facilite la synchronisation du numéro d'ordre de données du même service de multidiffusion/diffusion dans différents PLMN.
PCT/CN2023/135528 2022-12-08 2023-11-30 Procédé de communication et appareil de communication WO2024120299A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=91357162

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/135528 WO2024120299A1 (fr) 2022-12-08 2023-11-30 Procédé de communication et appareil de communication

Country Status (2)

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

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 (fr) * 2021-06-16 2022-12-22 华为技术有限公司 Procédé et appareil d'établissement de session

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 (fr) * 2021-06-16 2022-12-22 华为技术有限公司 Procédé et appareil d'établissement de session

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 (fr) Procédé de commutation de session pdu et appareil associé
WO2021164564A1 (fr) Procédé et appareil de transmission de service de multidiffusion
WO2021088660A1 (fr) Procédé, dispositif et appareil de communication
EP4027684A1 (fr) Procédé de configuration de service, dispositif de communication et système de communication
CN112954616B (zh) 用于实现多播广播业务切换的方法及相关设备
WO2022170819A1 (fr) Procédé de réalisation de transfert de service de multidiffusion et de diffusion, et dispositif associé
WO2021088661A1 (fr) Procédé, appareil et dispositif de communication
WO2015018232A1 (fr) Procédé et appareil de gestion de connexion de dispositif à dispositif et station de base
WO2022033168A1 (fr) Procédé de transmission de données mbs, appareil côté réseau et dispositif
WO2021097858A1 (fr) Procédé et appareil de communication
JP2022551395A (ja) データ伝送方法並びにその装置、コンピュータプログラム、制御装置及びアプリケーションサーバ
US20220408317A1 (en) Handover method and communication apparatus
WO2023029590A1 (fr) Procédé de gestion de session de diffusion/multidiffusion et appareil de communication
WO2023000884A1 (fr) Procédé de traitement de session de multidiffusion, entité de fonction de réseau, appareil, et support de stockage
WO2022037441A1 (fr) Procédé et appareil d'indication de mode de transmission pour un service mbms, et support de stockage
WO2024120299A1 (fr) Procédé de communication et appareil de communication
WO2022206775A1 (fr) Procédé et appareil de transfert de transmission pour service de multidiffusion et de diffusion
WO2022179434A1 (fr) Procédé, appareil et système de communication de service de diffusion/multidiffusion
KR20240019328A (ko) 세션 설정 방법 및 장치
EP4021072A1 (fr) Procédé, appareil et système de traitement de données
WO2024067475A1 (fr) Procédé de transmission de données et appareil de communication
EP4369745A1 (fr) Procédé et appareil de communication
WO2022165919A1 (fr) Procédé et appareil de communication