WO2023134516A1 - 一种广播通信方法和装置 - Google Patents

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

Info

Publication number
WO2023134516A1
WO2023134516A1 PCT/CN2023/070401 CN2023070401W WO2023134516A1 WO 2023134516 A1 WO2023134516 A1 WO 2023134516A1 CN 2023070401 W CN2023070401 W CN 2023070401W WO 2023134516 A1 WO2023134516 A1 WO 2023134516A1
Authority
WO
WIPO (PCT)
Prior art keywords
broadcast service
broadcast
identifier
network element
network
Prior art date
Application number
PCT/CN2023/070401
Other languages
English (en)
French (fr)
Inventor
李濛
李秉肇
王燕
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP23739860.7A priority Critical patent/EP4447577A1/en
Priority to AU2023206483A priority patent/AU2023206483A1/en
Publication of WO2023134516A1 publication Critical patent/WO2023134516A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources

Definitions

  • the present application relates to the communication field, and more particularly, to a broadcast communication method and device.
  • the broadcast message includes the information of the public land mobile network (PLMN).
  • PLMN public land mobile network
  • the base station broadcasts the information of a certain cell, and the information includes the information of the PLMN to which the cell belongs.
  • the present application provides a broadcast communication method, which can reduce the waste of transmission resources.
  • a broadcast communication method is provided, and the method may be executed by a radio access network device (for example, a base station), or may also be executed by components of the radio access network device (for example, a chip or a circuit). This is not limited.
  • a radio access network device for example, a base station
  • components of the radio access network device for example, a chip or a circuit
  • the method includes: a radio access network device receives a first message from a first access and mobility management functional network element, the first message carries an identifier of a first broadcast service, and the first message is used to trigger the The first broadcast service allocates resources, wherein the radio access network equipment is shared by at least two networks, the at least two networks include a first network and a second network, and the first access and mobility management function network element Located in the first network; the radio access network device obtains information about a first resource corresponding to the first broadcast service according to the identifier of the first broadcast service, and the first resource is used to provide information to the A terminal device in the second network sends the data of the first broadcast service; the wireless access network device sends the data of the first broadcast service to the terminal device in the first network through the first resource .
  • the wireless access network device has allocated resources for the first broadcast service in the second network and established a corresponding broadcast session context of the first broadcast service
  • the network device sends the identifier of the first broadcast service, so that the radio access network device can identify the same broadcast service in different networks.
  • the radio access network device may send the data of the broadcast service in the first network by using the resource allocated for the broadcast service in the second network.
  • the wireless access network device can share air interface resources for the same broadcast service in different networks, saving the transmission resources of the wireless access network device and avoiding the waste of air interface resources.
  • the first resource may be used to send the data of the first broadcast service to the terminal device in the second network.
  • the first resource may be: air interface resource, for example, scheduling time resource, frequency resource, scheduling priority, cache resource, data radio bearer (data radio bearer, DRB), stored context information (for example, quality of service (quality of service, QoS) description information, QoS flow (flow) identification information) and one or more of the above, are not limited.
  • the information of the first resource may be, for example, identification information of the first resource (for example, context ID), or information such as the time domain and frequency domain position of the first resource, which is not limited.
  • the identifier of the first broadcast service includes a first identifier and/or a second identifier, where the first identifier includes at least one of the following: a globally unique identifier of the first broadcast service; An identifier of the first broadcast service in each of the at least two networks, or; a temporary mobile group identifier of the first broadcast service, where the temporary mobile group identifier is shared by the at least two networks ;
  • the second identification includes: the identification of the first broadcast service in the first network.
  • the identifier of the first broadcast service may include the globally unique identifier of the first broadcast service and the identifier of the first broadcast service in the first network; for another example, the identifier of the first broadcast service may include the The identifier of the first broadcast service in each of the at least two networks and the temporary mobile group identifier of the first broadcast service; for another example, the identifier of the first broadcast service may include the ID of the first broadcast service A globally unique identifier, a temporary mobile group identifier of the first broadcast service, an identifier of the first broadcast service in the first network, and so on.
  • the globally unique identifier of the first broadcast service includes an Internet Protocol IP multicast address of the first broadcast service. It should be noted that the globally unique identifier of the first broadcast service may be the Internet Protocol IP multicast address of the first broadcast service, and may also include other content, such as the source address (source address) of the multicast/broadcast data , this application is not limited.
  • the IP multicast address for example, for Internet protocol version 4 (internet protocol version 4, IPv4) can be 224.3.0.0 to 224.4.255.255, or 225.0.0.0 to 231.255.255.255, or 232.0.0.0 to 232.255 .255.255, or one or more IP addresses in the address range from 233.0.0.0 to 233.251.255.255; for Internet protocol version 6 (IPv6), it can also be one with the prefix ff02 or ff05 or ff0x or multiple IP addresses, which is not limited in this application.
  • IPv6 Internet protocol version 6
  • the identifier of the first broadcast service is the globally unique identifier of the first broadcast service
  • the request message sent by the network element of the application function to the PLMN network is realized by adding the globally unique identifier of the first broadcast service.
  • the information element in the message sent by the existing access and mobility management network element to the access network device may be extended. That is, by expanding the original identification of the first broadcast service in the network to the identification of the first broadcast service in each of the at least two networks, new functions are realized, and the network is slightly changed and easy to upgrade.
  • the wireless access network device obtains the The information about the first resource corresponding to the first broadcast service includes: the wireless access network device searches for the broadcast session context corresponding to the first broadcast service according to the globally unique identifier of the first broadcast service; The access network device obtains the information of the first resource according to the broadcast session context; wherein the broadcast session context includes the globally unique identifier of the first broadcast service and the information of the first resource.
  • the wireless access network device when the identifier of the first broadcast service is the identifier of the first broadcast service in each of the at least two networks, the wireless access network device according to The identification of the first broadcast service, and obtaining the information of the first resource corresponding to the first broadcast service includes: the radio access network device in each of the at least two networks according to the first broadcast service An identifier in a network to search for a broadcast session context corresponding to the first broadcast service; the radio access network device obtains information about the first resource according to the broadcast session context; wherein the broadcast session context includes An identifier of the first broadcast service in each of the at least two networks and information about the first resource.
  • the wireless access network device obtains the first broadcast service corresponding to the first broadcast service according to the identifier of the first broadcast service.
  • the information of the first resource includes: the radio access network device according to the pre-configured identifier of the first broadcast service in the first network and the identifier of the first broadcast service in the second network.
  • the corresponding relationship between the identifier and the second identifier is to obtain the identifier of the first broadcast service in the second network; the radio access network device in the second network according to the first broadcast service ID of the broadcast session context corresponding to the first broadcast service; the radio access network device obtains the information of the first resource according to the broadcast session context; wherein the broadcast session context includes the first broadcast session context 2. Identification and information of the first resource.
  • the radio access network device can use the first broadcast service in the second network.
  • a resource sends data of a first broadcast service in the first network.
  • the wireless access network device can use the first resource to send the data of the first broadcast service to the terminal device in the first network without searching for the context corresponding to the first broadcast service or for information about the first resource .
  • the radio access network device may acquire information about the first resource allocated for the first broadcast service in the second network according to the identifier of the first broadcast service. Subsequently, the radio access network device may send the data of the first broadcast service for the terminal device in the first network through the first resource.
  • the method further includes: when the identifier of the first broadcast service includes the first identifier, The method further includes: the wireless access network device receiving a second message from a second access and mobility management functional network element, the second message carrying the first identifier, and the second message is used to trigger Allocating resources for the first broadcast service, the second access and mobility management function network element is located in the second network of the at least two networks; the radio access network device, according to the second message, is The first broadcast service allocates the first resource; the radio access network device establishes a broadcast session context corresponding to the first broadcast service; wherein the broadcast session context includes the first identifier and the second Information about a resource.
  • the wireless access network device can broadcast the first broadcast service on the second network.
  • the service allocates resources and establishes a session context of the first broadcast service.
  • Subsequent radio access network devices may not distinguish networks, but flexibly use (also can be understood as "sharing") the resource according to whether the resource has been allocated locally for the broadcast service.
  • a broadcast communication method which can be performed by a network element with a multicast/broadcast session management function, or can also be performed by a component (such as a chip or a circuit) of a network element with a multicast/broadcast session management function Execution without limitation.
  • the method includes: a network element with a multicast/broadcast session management function receiving an identifier of a first broadcast service; the network element with a multicast/broadcast session management function sending the identifier of the first broadcast service to an access and mobility management function network element .
  • the multicast/broadcast session management function network element can receive the identifier of the first broadcast service and send it to the access and mobility management function network element, so that the wireless access network device can obtain the first The identifier of the broadcast service, identifying the same broadcast data in different networks.
  • the identifier of the first broadcast service includes a first identifier
  • the first identifier includes at least one of the following: a globally unique identifier of the first broadcast service; An identifier in each of the two networks, or: a temporary mobile group identifier of the first broadcast service, where the temporary mobile group identifier is shared by at least two networks.
  • the globally unique identifier of the first broadcast service includes an Internet Protocol IP multicast address of the first broadcast service. It should be noted that the globally unique identifier of the first broadcast service may be the Internet Protocol IP multicast address of the first broadcast service, and may also include other content, such as the source address (source address) of the multicast/broadcast data , this application is not limited.
  • the IP multicast address for example, for Internet protocol version 4 (internet protocol version 4, IPv4) can be 224.3.0.0 to 224.4.255.255, or 225.0.0.0 to 231.255.255.255, or 232.0.0.0 to 232.255.255.255, or one or more IP addresses in the address range from 233.0.0.0 to 233.251.255.255; for Internet protocol version 6 (IPv6), it can also be prefixed with ff02 or ff05 or ff0x One or more IP addresses, which are not limited by this application.
  • IPv6 Internet protocol version 6
  • the identifier of the first broadcast service is the globally unique identifier of the first broadcast service
  • the request message sent by the network element of the application function to the PLMN network is realized by adding the globally unique identifier of the first broadcast service.
  • the information element in the message sent by the existing access and mobility management network element to the access network device may be extended. That is, by expanding the original identification of the first broadcast service in the network to the identification of the first broadcast service in each of the at least two networks, new functions are realized, and the network is slightly changed and easy to upgrade.
  • the radio access network device can flexibly identify the same broadcast service for different representation forms of the identifier of the first broadcast service.
  • the multicast/broadcast session management function network element receiving the identifier of the first broadcast service includes: the multicast/broadcast session management function network element receiving the first broadcast service from the application function network element logo.
  • the multicast/broadcast session management functional network element receiving the identifier of the first broadcast service includes: the multicast/broadcast session management functional network element receiving the multicast/broadcast user plane functional network element The identifier of the first broadcast service, wherein the identifier of the first broadcast service is a globally unique identifier of the first broadcast service.
  • the multicast/broadcast session management function network element can receive the identifier of the first broadcast service from the application function network element, and can also receive the identifier of the first broadcast service from the multicast/broadcast user plane function network element logo. That is, the identifier of the first broadcast service can be flexibly received from each network element of the core network. Therefore, subsequent radio access network devices can identify the same broadcast service in different networks based on the identifiers of broadcast services received from network elements of different core networks.
  • the method further includes: the multicast/broadcast session management function network The element receives a third message from the application function network element, the third message carries the identifier of the first broadcast service, and the third message is used to trigger the multicast/broadcast session management function network element to send
  • the application function network element sends the temporary mobile group identifier of the first broadcast service; the multicast/broadcast session management function network element obtains the temporary mobile group identifier from the first network element according to the third message, or
  • the multicast/broadcast session management function network element allocates the temporary mobile group identifier for the first broadcast service according to the third message; the multicast/broadcast session management function network element sends the application function The network element sends the temporary mobility group identifier.
  • the network element with the multicast/broadcast session management function can obtain the temporary mobile group identifier from the first network element or autonomously broadcast the identifier for the first broadcast service.
  • the temporary mobile group identifier is allocated to the service, so that it can be guaranteed that the same temporary mobile group identifier is used for the same broadcast service.
  • the first network element is: a unified data management network element, a unified data storage network element, a network storage function network element, a network discovery function network element, a policy control function network element, or a multicast/ A broadcast database, wherein the multicast/broadcast database is shared by at least two networks.
  • the first network element in this application may be a network element in the existing 5G core network architecture, or a new network element defined in the future. That is, the specific name of the first network element is not limited. As long as the temporary mobile group identity of the first broadcast service can be obtained from the network element, and the temporary mobile group identity can be shared by at least two networks, all fall within the scope of protection of this application.
  • the method further includes: the multicast/broadcast user plane function network element
  • the broadcast session management functional network element sends a fourth message to the multicast/broadcast user plane functional network element, where the fourth message is used to request session establishment or modification of the first broadcast service, and the fourth message carries the first Indication information, the first indication information is used to trigger the multicast/broadcast user plane functional network element to detect the identifier of the first broadcast service.
  • the identifier of the first broadcast service can be obtained by instructing the multicast/broadcast user plane function network element to detect the identifier of the first broadcast service, which can improve the flexibility of obtaining the identifier of the first broadcast service.
  • the technical solution can obtain the identifier of the first broadcast service without relying on the application function network element, and it can also be understood that the technical solution can also be realized without enhancing the function of the application function network element.
  • a broadcast communication method is provided, and the method may be executed by an application function network element, or may also be executed by a component (such as a chip or a circuit) of the application function network element, which is not limited thereto.
  • the method includes: the application function network element obtains the identifier of the first broadcast service; the application function network element sends the identifier of the first broadcast service to the multicast/broadcast session management function network element.
  • the identifier of the first broadcast service includes a first identifier
  • the first identifier includes at least one of the following: a globally unique identifier of the first broadcast service; An identifier in each of the two networks, or: a temporary mobile group identifier of the first broadcast service, where the temporary mobile group identifier is shared by at least two networks.
  • the globally unique identifier of the first broadcast service includes an Internet Protocol IP multicast address of the first broadcast service. It should be noted that the globally unique identifier of the first broadcast service may be the Internet Protocol IP multicast address of the first broadcast service, and may also include other content, such as the source address (source address) of the multicast/broadcast data , this application is not limited.
  • the IP multicast address for example, for Internet protocol version 4 (internet protocol version 4, IPv4) can be 224.3.0.0 to 224.4.255.255, or 225.0.0.0 to 231.255.255.255, or 232.0.0.0 to 232.255.255.255, or one or more IP addresses in the address range from 233.0.0.0 to 233.251.255.255; for Internet protocol version 6 (IPv6), it can also be prefixed with ff02 or ff05 or ff0x One or more IP addresses, which are not limited by this application.
  • IPv6 Internet protocol version 6
  • the identifier of the first broadcast service is the globally unique identifier of the first broadcast service
  • the request message sent by the network element of the application function to the PLMN network is realized by adding the globally unique identifier of the first broadcast service.
  • the information element in the message sent by the existing access and mobility management network element to the access network device may be extended. That is, by expanding the original identification of the first broadcast service in the network to the identification of the first broadcast service in each of the at least two networks, new functions are realized, and the network is slightly changed and easy to upgrade.
  • the radio access network device can flexibly identify the same broadcast service for different representation forms of the first broadcast service identifier.
  • the obtaining the identifier of the first broadcast service by the application function network element includes: generating the globally unique identifier of the first broadcast service by the application function network element.
  • the at least two networks include a first network and a second network
  • obtaining the identifier of the first broadcast service by the application function network element includes: The first multicast/broadcast session management function network element in the network element receives the identifier of the first broadcast service in the first network; the application function network element receives the identifier from the second multicast/broadcast service in the second network The session management function network element receives the identifier of the first broadcast service in the second network.
  • the obtaining the identifier of the first broadcast service by the application function network element includes: obtaining the temporary mobile group identifier from the multicast/broadcast session management function network element by the application function network element.
  • the application function network element may acquire the identifier of the first broadcast service by using different methods.
  • the present application provides a broadcast communication method.
  • the method may be executed by a first network element, or may also be executed by a component (such as a chip or a circuit) of the first network element, which is not limited thereto.
  • the method includes: a first network element receives a fifth message from a network element with a multicast/broadcast session management function, the fifth message carries an identifier of a first broadcast service, and the fifth message is used to trigger the first network element sending the temporary mobile group identifier of the first broadcast service; the first network element sends the temporary mobile group identifier of the first broadcast service to the multicast/broadcast session management function network element according to the fifth message .
  • the temporary mobility group identity is shared by at least two networks.
  • the temporary mobile group identifier can be obtained from the first network element.
  • the first network element is: a unified data management network element, a unified data storage network element, a network storage function network element, a network discovery function network element, a policy control function network element, or a multicast/ A broadcast database, wherein the multicast/broadcast database is shared by at least two networks.
  • the first network element in this application may be a network element in the existing 5G core network architecture, or a new network element defined in the future. That is, the specific name of the first network element is not limited. As long as the temporary mobile group identity of the first broadcast service can be obtained from the network element, and the temporary mobile group identity can be shared by at least two networks, all fall within the scope of protection of this application.
  • the method further includes: the first network element receives from the multicast/broadcast session management function network element the information between the identifier of the first broadcast service and the identifier of the temporary mobile group Correspondence.
  • the first network element has not assigned a temporary mobile group identifier to it.
  • the multicast/broadcast session management function can The network element allocates a temporary mobile group identifier for the first broadcast service in the network, and stores it on the first network element.
  • a broadcast communication device is provided, and the device is configured to execute the method in any possible implementation manner of the foregoing first aspect to the fourth aspect.
  • the apparatus may include a unit and/or module for executing the method in any possible implementation manner of the first aspect to the fourth aspect, such as a transceiver unit and/or a processing unit.
  • the apparatus is a communication device (such as a radio access network device, a network element with a multicast/broadcast session management function, a network element with an application function, or a first network element).
  • the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the apparatus is a chip, a chip system or circuit.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • a broadcast communication device in a sixth aspect, includes: at least one processor, configured to execute a computer program or an instruction stored in a memory, so as to execute the method in any possible implementation manner of the foregoing first aspect.
  • the apparatus also includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the apparatus is a radio access network device.
  • the apparatus is a chip, a chip system or a circuit for a radio access network device.
  • a broadcast communication device includes: at least one processor, configured to execute a computer program or an instruction stored in a memory, so as to execute the method in any possible implementation manner of the second aspect above.
  • the apparatus further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a network element with a multicast/broadcast session management function.
  • the device is a chip, a chip system or a circuit for a multicast/broadcast session management function network element.
  • a broadcast communication device includes: at least one processor, configured to execute a computer program or an instruction stored in a memory, so as to execute the method in any possible implementation manner of the third aspect above.
  • the apparatus further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is an application function network element.
  • the device is a chip, a chip system or a circuit for an application function network element.
  • a broadcast communication device includes: at least one processor, configured to execute a computer program or an instruction stored in a memory, so as to execute the method in any possible implementation manner of the foregoing fourth aspect.
  • the apparatus further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a first network element.
  • the device is a chip, a chip system or a circuit for the first network element.
  • the present application provides a processor, including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation manner of any one of the first aspect to the fourth aspect .
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc.
  • the input signal received by the input circuit may be received and input by, for example but not limited to, a transceiver
  • the output signal of the output circuit may be, for example but not limited to, output to the transmitter and transmitted by the transmitter
  • the circuit may be the same circuit, which is used as an input circuit and an output circuit respectively at different times.
  • the embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.
  • the processor's output and reception, input and other operations can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through the transceiver and transmit signals through the transmitter, so as to execute the method in any possible implementation manner of any one of the first aspect to the fourth aspect.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory may be set separately from the processor.
  • the memory can be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the configuration of the memory and the processor.
  • a non-transitory memory such as a read-only memory (read only memory, ROM)
  • ROM read only memory
  • a related data interaction process such as sending indication information may be a process of outputting indication information from a processor
  • receiving capability information may be a process of receiving input capability information from a processor.
  • the data output by the processor may be output to the transmitter, and the input data received by the processor may be from the transceiver.
  • the transmitter and the transceiver may be collectively referred to as a transceiver.
  • the processing device in the eleventh aspect above may be one or more chips.
  • the processor in the processing device may be implemented by hardware or by software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, which is implemented by reading software codes stored in a memory, which can Integrated in a processor, it can exist independently of that processor.
  • a computer-readable storage medium stores program code for execution by a device, and the program code includes any one of the possible implementation manners for performing the above-mentioned first aspect to the fourth aspect Methods.
  • a computer program product including instructions is provided, and when the computer program product is run on a computer, the computer is made to execute the method in any possible implementation manner of the first aspect to the fourth aspect above.
  • a chip system including a processor, configured to call and run a computer program from a memory, so that a device installed with the chip system executes each implementation in any one of the above first to fourth aspects methods in methods.
  • a fifteenth aspect provides a broadcast communication system, where the communication system includes radio access network equipment and a network element with a first access and mobility management function; the radio access network equipment is configured to implement the first aspect above The method in any one of the implementation manners; the first access and mobility management functional network element is configured to send a first message to the radio access network device, where the first message carries the identifier of the first broadcast service , the first message is used to trigger allocation of resources for the first broadcast service; wherein, the radio access network device is shared by at least two networks, and the at least two networks include a first network and a second network, The first access and mobility management functional network element is located in the first network.
  • the communication system further includes: a network element with a multicast/broadcast session management function, and the network element with a multicast/broadcast session management function is configured to implement any one of the implementation manners in the second aspect above method.
  • the communication system further includes: an application function network element, configured to execute the method in any one implementation manner of the third aspect above.
  • the communication system further includes: a first network element, configured to execute the method in any one implementation manner of the foregoing fourth aspect.
  • FIG. 1 is a schematic diagram of a network architecture applicable to this application.
  • FIG. 2 is a schematic diagram of a scenario applicable to this application.
  • Fig. 3 is a schematic diagram of another scene applicable to this application.
  • FIG. 4 is a schematic flowchart of a broadcast communication method 100 provided by the present application.
  • FIG. 5 is a schematic flowchart of a broadcast communication method 200 provided by the present application.
  • FIG. 6 is a schematic flowchart of a broadcast communication method 300 provided by the present application.
  • FIG. 7 is a schematic flowchart of a broadcast communication method 400 provided by the present application.
  • FIG. 8 is a schematic flowchart of a broadcast communication method 500 provided by the present application.
  • FIG. 9 is a schematic flowchart of a broadcast communication method 600 provided by the present application.
  • FIG. 10 is a schematic flowchart of a broadcast communication method 700 provided by the present application.
  • FIG. 11 is a schematic flow chart of a broadcast communication method 800 provided by the present application.
  • FIG. 12 is a schematic block diagram of a broadcast communication device 100 provided by the present application.
  • FIG. 13 is a schematic block diagram of a broadcast communication device 200 provided by the present application.
  • the wireless communication systems mentioned in this application include but are not limited to: global system of mobile communication (GSM) system, long term evolution (long term evolution, LTE) frequency division duplex (frequency division duplex, FDD) system, LTE Time division duplex (time division duplex, TDD), LTE system, advanced long-term evolution (LTE-Advanced, LTE-A) system, next-generation communication system (for example, 6G communication system), fusion system of multiple access systems, or evolutionary system.
  • GSM global system of mobile communication
  • LTE long term evolution
  • FDD frequency division duplex
  • FDD frequency division duplex
  • LTE Time division duplex time division duplex
  • LTE-A advanced long-term evolution
  • next-generation communication system for example, 6G communication system
  • fusion system of multiple access systems or evolutionary system.
  • the technical solution provided by this application can also be applied to machine type communication (machine type communication, MTC), inter-machine communication long term evolution technology (long term evolution-machine, LTE-M), device to device (device to device, D2D) network , machine to machine (machine to machine, M2M) network, Internet of things (internet of things, IoT) network or other networks.
  • MTC machine type communication
  • LTE-M long term evolution technology
  • D2D device to device
  • machine to machine machine to machine
  • M2M machine to machine
  • IoT Internet of things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and Infrastructure (vehicle to infrastructure, V2I) communication, vehicle to pedestrian (vehicle to pedestrian, V2P) or vehicle to network (vehicle to network, V2N) communication, etc.
  • vehicle to vehicle vehicle to vehicle
  • V2V vehicle to vehicle
  • V2I vehicle to infrastructure
  • V2P vehicle to pedestrian
  • V2N vehicle to network
  • FIG. 1 shows a schematic diagram of a network architecture applicable to this application.
  • the network architecture takes the 5G system (the 5th generation system, 5GS) as an example.
  • the 5G system architecture is divided into two parts: the access network and the core network.
  • the network architecture may include but not limited to: unified data management (unified data management, UDM), network discovery function (network exposure function, NEF), network storage function (NF repository function, NRF), policy control function (policy control function, PCF), application function (application function, AF), access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), user equipment (user equipment, UE), wireless Access network equipment, user plane function (UPF), data network (data network, DN).
  • unified data management unified data management
  • UDM unified data management
  • NEF network exposure function
  • NRF network storage function
  • policy control function policy control function
  • PCF policy control function
  • application function application function, AF
  • access and mobility management function access and mobility management function
  • AMF session management function
  • SMF session management function
  • user equipment user
  • DN can be the Internet
  • UDM, NEF, NRF, PCF, AF, AMF, SMF, and UPF belong to network elements in the core network.
  • the core network can be called a 5G core network ( 5G core network, 5GC or 5GCN).
  • Each network element shown in FIG. 1 is briefly introduced below.
  • User equipment (user equipment, UE) (101): may be called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, A wireless communication device, user agent, or user device.
  • a terminal device may be a device that provides voice/data to a user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones , wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing equipment connected to a wireless modem, terminal in 5G network
  • PLMN public land mobile network
  • PLMN public land mobile network
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the terminal device can also be the terminal device in the IoT system.
  • IoT is an important part of the development of information technology in the future. Its main technical feature is to connect items to the network through communication technology, so as to realize Interconnection, an intelligent network of interconnection of things.
  • a certain air interface technology such as NR or LTE technology
  • a certain air interface technology may also be used to communicate with each other between terminal devices.
  • the device for realizing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to realize the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • (wireless) access network ((radio) access network, (R) AN) equipment (102) it can provide authorized users in a specific area with the function of accessing the communication network, specifically, it can include the third generation partnership project ( Wireless network devices in a 3rd generation partnership project (3GPP) network may also include access points in a non-3GPP (non-3GPP) network.
  • 3GPP 3rd generation partnership project
  • non-3GPP non-3GPP
  • RAN equipment may adopt different radio access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3rd generation, 3G), fourth generation (4th generation, 4G) or 5G systems
  • non- 3GPP (non-3GPP) access technology refers to the access technology that complies with the 3GPP standard specifications.
  • the access network equipment in the 5G system is called the next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies may include air interface technology represented by access point (AP) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code Multiple access (code division multiple access, CDMA), etc.
  • the AN device may allow non-3GPP technology interconnection and intercommunication between the terminal device and the 3GPP core network.
  • the RAN device can be responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the AN equipment provides access services for the terminal equipment, and then completes the forwarding of control signals and user data between the terminal equipment and the core network.
  • RAN equipment may include but not limited to: macro base station, micro base station (also called small station), radio network controller (radio network controller, RNC), node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be gNB or transmission point (TRP or TP) in the 5G (eg, NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or a transmission point, such as a distributed unit (DU), or a next-generation communication Base stations
  • User plane function (UPF) (103) can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc.
  • User data can be accessed to a data network (data network, DN) through this network element. In the embodiment of the present application, it can be used to realize the functions of the user plane network element.
  • the multicast/broadcast (MB) UPF involved in this application can be used to send the detected Internet protocol (internet protocol, IP) address of the multicast/broadcast service to the MB-SMF.
  • IP Internet protocol
  • Data network (digital network, DN) (104): a network for providing data transmission.
  • DN digital network
  • a network of an operator's business an Internet (Internet) network, a business network of a third party, and the like.
  • Access and mobility management function network element (access and mobility management function, AMF) (105): mainly used for mobility management and access management, etc., and can be used to implement a mobility management entity (mobility management entity, MME) Functions other than session management, for example, functions such as lawful interception, or access authorization (or authentication). In the embodiment of the present application, it can be used to implement functions of network elements with access and mobility management functions.
  • AMF access and mobility management function
  • MME mobility management entity
  • Session management function network element (session management function, SMF) (106): mainly used for session management, IP address allocation and management of terminal equipment, selection and management of user plane functions, policy control, or endpoints of charging function interfaces And downlink data notification, etc. In the embodiment of the present application, it can be used to realize the function of the session management network element.
  • SMF session management function
  • the MB-SMF involved in this application can be used to manage multicast/broadcast services, and MB-UPF can also be configured for multicast/broadcast services.
  • MB-SMF can interact with MB-UPF through signaling to instruct MB-UPF to identify the IP address of MBS data.
  • MB-SMF may need to enhance the message sent to RAN for RAN to identify the same multicast/broadcast service .
  • the SMF for managing multicast/broadcast in this application may be different from the SMF for managing unicast, and there may be an N16 interface between the unicast SMF and the multicast SMF.
  • Policy control network element Policy control function, PCF (107): a unified policy framework for guiding network behavior, providing policy rule information, etc. for control plane functional network elements (such as AMF, SMF network elements, etc.).
  • Unified data management network element (unified data management, UDM) (108): used for unified data management, 5G user data management, processing user identification, access authentication, registration, or mobility management, etc.
  • Application function network element (Application function, AF): It is used to route the data affected by the application, access the open network element of the network, or interact with the policy framework for policy control, etc.
  • AF can also be understood as an application server.
  • network elements can communicate through the interfaces shown in the figure.
  • the N1 interface is the reference point between the terminal equipment and the AMF
  • the N2 interface is the reference point between the RAN and the AMF, and is used for sending non-access stratum (non-access stratum, NAS) messages
  • the N3 interface is The reference point between RAN and UPF, used to transmit user plane data, etc.
  • N4 interface is the reference point between SMF and UPF, used to transmit tunnel identification information such as N3 connection, data cache indication information, and downlink data notification Information such as messages
  • N5 interface is the reference point between PCF and AF
  • N6 interface is the reference point between UPF and DN, used to transmit user plane data, etc.
  • N7 interface is the reference point between SMF and PCF
  • N8 The interface is the reference point between AMF and UDM
  • the N11 interface is the reference point between AMF and AMF.
  • the relationship between other interfaces and each network element is shown in FIG. 1 , and for
  • the functions or network elements such as AMF, SMF, UPF, PCF, and UDM shown in FIG. 1 may be understood as network elements for implementing different functions.
  • network slices can be combined on demand.
  • These network elements can be independent devices, or can be integrated in the same device to achieve different functions, or can be network elements in hardware devices, or software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • Multicast The same service and the same content-specific data are simultaneously provided to a dedicated group of UEs (i.e. not all UEs in the multicast coverage are authorized to receive the data). "Multicast” in this application can also be understood as “multicast”.
  • Broadcast The same content-specific data is simultaneously provided to all UEs in the geographical area (ie, all UEs in the broadcast coverage area are authorized to receive the data).
  • Multicast/broadcast service session (multicast/broadcast service-session, MBS session): A multicast/broadcast session can provide services for a multicast/broadcast service.
  • a multicast/broadcast session includes a unicast or multicast tunnel from the data network to the core network device and then to the access network device, and the unicast or multicast tunnel allocated by the access network device for sending the multicast/broadcast service /Broadcast air interface resources.
  • Fig. 2 shows a schematic diagram of a scene applicable to this application.
  • operators in order to reduce the cost of deploying radio access networks, operators generally choose to share radio access network equipment while retaining their respective core networks (in the following description, base stations are used as radio access network equipment is described).
  • MOCN multi-operator core network
  • the broadcast message includes the information of the public land mobile network (PLMN).
  • PLMN public land mobile network
  • the cell information sent by the base station includes information about the PLMN to which the cell belongs.
  • Fig. 3 shows a schematic diagram of another scenario applicable to this application.
  • the content transmitted by certain broadcast services such as weather forecast, high-precision map update, etc.
  • data of the same broadcast service needs to be transmitted multiple times on core networks of different operators and base stations shared by operators.
  • the content provider (MBS content provider) of the multicast/broadcast service sends to PLMN#a and PLMN#b respectively broadcast data.
  • the broadcast communication method provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings.
  • the embodiments provided in this application can be applied to the network architecture shown in FIG. 1 above, and can also be applied to the scenarios shown in FIG. 2 and FIG. 3 , without limitation.
  • FIG. 4 is a schematic diagram of a broadcast communication method 100 provided by the present application.
  • the method may be executed by, for example, a radio access network device.
  • the method 100 includes the following steps.
  • Step 101 a radio access network device receives a first message from a first access and mobility management functional network element.
  • the radio access network device may be shared by at least two networks, and the at least two networks may be at a PLMN granularity, or at an independent non-public network (standalone non-public network, SNPN) granularity.
  • the at least two networks may include a first network and a second network, the first network may be PLMN#1, and the second network may be PLMN#2; for another example, the at least two networks may include the first network and the second network Two networks, the first network may be SNPN#1, and the second network may be SPNN#2.
  • the first access and mobility management functional network element is located in the first network.
  • the first message may be used to trigger the wireless access network device to allocate resources for the first broadcast service, where the resources may be air interface resources, and the air interface resources may be scheduling time resources, frequency resources, scheduling priorities, cache resources, data A radio bearer (data radio bearer, DRB); or, the resource may also be stored context information (for example, QoS description information, identification information of a QoS flow (flow)), etc.
  • the first message may be used to request the radio access network device to allocate resources for the first broadcast service, or the first message may be used to request the radio access network device to establish a context corresponding to the first broadcast service.
  • the first message may be an existing message, for example, an N2 request (N2 request) message; it may also be a multicast/broadcast session-related message, for example, an MBS session resource setup request (MBSsession resource setup request), or MBS session start request (MBS session start request), or broadcast session resource setup request (broadcast session resource setup request).
  • N2 request N2 request
  • MBS session resource setup request MBS session resource setup request
  • MBS session start request MBS session start request
  • broadcast session resource setup request broadcast session resource setup request
  • the first message may be sent by the first access and mobility management functional network element according to the message received from the first multicast/broadcast session management functional network element.
  • the first message may carry an identifier of the first broadcast service, and the identifier may be used to indicate the first broadcast service.
  • the first broadcast service may be a service initiated by an application function network element and requested to establish a resource on the PLMN network and transmitted.
  • the first broadcast service may be a weather forecast service, an emergency warning service, a high-precision map service, and the like.
  • the identifier of the first broadcast service includes a first identifier and/or a second identifier.
  • the first identifier may include at least one of the following: a globally unique identifier of the first broadcast service, an identifier of the first broadcast service in each of the at least two networks, or a temporary mobile group identifier corresponding to the first broadcast service (temporary mobile group identifier, TMGI), the temporary mobile group identifier is shared by the at least two networks.
  • a globally unique identifier of the first broadcast service an identifier of the first broadcast service in each of the at least two networks
  • TMGI temporary mobile group identifier
  • the globally unique identifier of the first broadcast service may be used to globally uniquely identify the first broadcast service.
  • the globally unique identifier may be the Internet IP multicast address of the first broadcast service.
  • the globally unique identifier may also include other content, such as a source address (source address) of multicast/broadcast data, which is not limited.
  • IPv4 Internet protocol version 4
  • IPv6 Internet protocol version 6
  • IPv6 Internet protocol version 6
  • IPv6 Internet protocol version 6
  • the identifier of the first broadcast service in each of the at least two networks may also be understood as an identifier of a broadcast session of the first broadcast service in each of the at least two networks.
  • the identification includes identification information of the network.
  • the identification information of the network is PLMN ID (for example, 33E451), or PLMN ID+network identifier (network identifier, NID).
  • the identification of the first broadcast service in each of the at least two networks may be embodied in the form of a list (list), and the list includes broadcast sessions of the first broadcast service in each of the at least two networks logo.
  • the broadcast session identifier of the first broadcast service in network #1 may be TMGI#1, and TMGI#1 may specifically be 70A886 32F461; the broadcast session identifier of the first broadcast service in network #2
  • the identifier can be TMGI#2, and TMGI#2 can specifically be 81B74933E451;
  • the broadcast session identifier of the first broadcast service on network #3 can be TMGI#3, and TMGI#3 can specifically be 64973942F352.
  • the identifier of the first broadcast service in each of the at least two networks can be represented by the above list, or by an array (for example ⁇ 70A886 32F461, 81B749 33E451, 649739 42F352 ⁇ ), it can also be represented by other means for identifying a set of data (for example: structure, linked list, etc.), which is not limited in this application.
  • the identifier of the broadcast session is used to identify the broadcast session, for example, may be an identifier of a group corresponding to the broadcast session, for example, an identifier of a temporary mobile group.
  • the temporary mobile group identifier (TMGI) corresponding to the first broadcast service may be shared by at least two networks.
  • a general TMGI is configured for the first broadcast service, and the general TMGI can uniquely identify a broadcast service in both the first network and the second network.
  • the AF can provide the common TMGI.
  • universal TMGI means that one or some TMGIs can be shared by several (ie, at least two) networks.
  • the TMGI in the first network is the same as the TMGI in the second network, both being TMGI #v.
  • the second identifier may include: an identifier of the first broadcast service in the first network, and the identifier of the first broadcast service in the first network may be an identifier of a broadcast session of the first broadcast service in the first network;
  • the second identifier further includes identification information of the first broadcast service on the first network, such as PLMN ID or PLMN ID+NID.
  • the radio access network device may preconfigure or acquire or receive the identifier of the first broadcast service in each of the at least two networks. For example, when establishing a session of the first broadcast service for the first time, the radio access network device receives and stores a list of identifiers of the first broadcast service in each of the at least two networks (see Table 1). Further, when the session of the first broadcast service is not established for the first time (for example, for the second time), the core network element (for example, the first access and mobility management function network element) in the first network may carry the first broadcast service The identification of the service in the first network can avoid sending the entire list repeatedly, saving transmission resources.
  • the session of the first broadcast service may refer to a session for transmitting the first broadcast service.
  • the identifier of the first broadcast service is the globally unique identifier of the first broadcast service
  • the request message sent by the network element of the application function to the PLMN network is realized by adding the globally unique identifier of the first broadcast service.
  • the information element in the message sent by the existing access and mobility management network element to the access network device may be extended. That is, by extending the original identification of the first broadcast service in the network to the identification of the first broadcast service in each of at least two networks, new functions are realized, and the network is slightly changed and easy to upgrade.
  • Step 102 the radio access network device obtains information about the first resource corresponding to the first broadcast service according to the identifier of the first broadcast service.
  • the first resource may be used to send data of the first broadcast service to terminal devices in the second network.
  • the first resource may be: an air interface resource.
  • the air interface resources are scheduling time resources, frequency resources, scheduling priorities, cache resources, and data radio bearers (data radio bearer, DRB);
  • the first resource can also be: stored context information, for example, QoS description information, QoS Flow (flow) identification information), etc., are not limited.
  • the information of the first resource may be identification information (for example, context ID) of the first resource, or information such as time domain and frequency domain position of the first resource, which is not limited.
  • step 102 can be divided into the following scenarios:
  • Scenario 1 For the scenario where the wireless access network device has established a session of the first broadcast service in a certain network (take the second network as an example) (it can also be understood as that the first broadcast service has been allocated in the second network resource scenarios).
  • the session context corresponding to the session of the first broadcast service may include the identifier of the first broadcast service and the first broadcast service allocated to the first broadcast service. resource information.
  • the wireless access network device obtains the information of the first resource corresponding to the first broadcast service according to the identifier of the first broadcast service, and the following implementation methods may be adopted:
  • Method 1 When the identifier of the first broadcast service is the globally unique identifier of the first broadcast service, the wireless access network device searches for the broadcast session context corresponding to the first broadcast service according to the globally unique identifier of the first broadcast service, and wirelessly The access network device obtains the information of the first resource corresponding to the first broadcast service according to the broadcast session context.
  • the broadcast session context may include the globally unique identifier of the first broadcast service and information of the first resource.
  • the base station shared by the first network and the second network receives the first network
  • the first resource can be reused, thereby avoiding waste of resources.
  • Method 2 In the case where the identifier of the first broadcast service is the identifier of the first broadcast service in each of the at least two networks, the wireless access network device The identifier in each network searches for the broadcast session context corresponding to the first broadcast service, and the wireless access network device obtains the information of the first resource corresponding to the first broadcast service according to the broadcast session context.
  • the broadcast session context may include an identifier of the first broadcast service in each of the at least two networks and information about the first resource.
  • the base station shared by the second network and other networks may reuse the first resource when receiving a request from other networks to establish the first broadcast service session context (or request to allocate resources for the first broadcast service session). That is, the radio access network device does not need to reallocate resources for the first broadcast service in other networks, thereby avoiding waste of resources.
  • Method 3 In the case where the identifier of the first broadcast service is the second identifier (for example, the identifier of the first broadcast service in the first network), the wireless access network device broadcasts the first broadcast service on the first network according to the preconfigured The corresponding relationship between the identifier in the first broadcast service and the identifier of the first broadcast service in the second network, and the second identifier, obtain the identifier of the first broadcast service in the second network, and the wireless access network device uses the first broadcast service in the second network The identifier in the network searches for the broadcast session context corresponding to the first broadcast service, and the wireless access network device obtains the information of the first resource corresponding to the first broadcast service according to the broadcast session context.
  • the identifier of the first broadcast service is the second identifier (for example, the identifier of the first broadcast service in the first network)
  • the wireless access network device broadcasts the first broadcast service on the first network according to the preconfigured
  • the broadcast session context may include the second identifier and information of the first resource.
  • the base station shared by the second network and other networks may reuse the first resource when receiving a request from other networks to establish the first broadcast service session context (or request to allocate resources for the first broadcast service session). That is, the radio access network device does not need to reallocate resources for the first broadcast service in other networks, thereby avoiding waste of resources.
  • resources for example, first resources
  • the resources can be used by multiple networks (for example, the first network) to transmit the first broadcast service.
  • the service that is, the radio access network device does not need to reallocate resources for the first broadcast service in the first network, thereby avoiding waste of resources.
  • the radio access network The device may obtain information about the first resource allocated for the first broadcast service in the second network through the identifier of the first broadcast service, and then the wireless access network device may use the first resource to send the first resource for the terminal device in the first network. Data of a broadcasting service.
  • Scenario 2 is a scenario in which the wireless access network device has not yet established a session of the first broadcast service in each network.
  • the method 100 may further include: the radio access network device receiving a second message from a second access and mobility management functional network element, where the second message carries an identifier of the first broadcast service.
  • the second message is used to trigger resource allocation for the first broadcast service
  • the second access and mobility management function network element is located in the second network.
  • the identifier of the first broadcast service may include the first identifier.
  • the radio access network device allocates the first resource for the first broadcast service according to the second message, and the radio access network device establishes a broadcast session context corresponding to the first broadcast service, where the broadcast session context includes an identifier of the first broadcast service and Information about the first resource.
  • the second message in this scenario refers to the description of the first message for details.
  • the second message is transmitted between network elements of the core network in the second network
  • the first message is transmitted between network elements of the core network in the first network.
  • the second message may be an existing message, such as an N2 request message; it may also be a multicast/broadcast session-related message, such as an MBS session resource establishment request, or an MBS session start request, or a broadcast session resource establishment ask.
  • an existing message such as an N2 request message
  • it may also be a multicast/broadcast session-related message, such as an MBS session resource establishment request, or an MBS session start request, or a broadcast session resource establishment ask.
  • the radio access network device may allocate resources for the first broadcast service on the second network and establish The session context of the first broadcast service. Because the broadcast session context corresponding to the first broadcast service established in the second network includes the identifier of the first broadcast service and the information of the first resource. Therefore, the wireless access network device does not need to repeatedly allocate resources for the same broadcast service in different networks. It can also be understood that the subsequent wireless access network device does not need to distinguish between networks, but according to whether resources have been allocated for the broadcast service locally , so as to flexibly use (also can be understood as "sharing") the resource.
  • Step 103 the radio access network device sends the data of the first broadcast service to the terminal device in the first network through the first resource.
  • the radio access network device after receiving the service data from the multicast/broadcast user management network element, the radio access network device, according to the identification information contained in the service data (for example, target IP address, general packet radio The Service Tunneling Protocol (general packet radio service (GPRS) tunneling protocol, GTP) header tunnel node identifier, QoS flow identifier) recognizes that the service data belongs to the first broadcast service, and the wireless access network device according to the locally stored context information (for example, scheduling queues, reserved resources), etc., send (or broadcast) the service data through the air interface resources (for example, time-frequency resources) corresponding to the first broadcast service, and correspondingly, the terminal equipment in the first network will monitor the air interface resource to receive the business data.
  • the identification information contained in the service data for example, target IP address, general packet radio The Service Tunneling Protocol (general packet radio service (GPRS) tunneling protocol, GTP) header tunnel node identifier, QoS flow identifier)
  • GPRS general packet radio service
  • GTP general packet radio
  • the wireless access network device receives the temporary mobile When the group identifier is set, the first resource can be used to send the data of the first broadcast service to the terminal device in the first network.
  • the radio access network device since the radio access network device receives the same temporary mobile group identifier in each network, for the radio access network device, there is no need to search for the first broadcast session context After obtaining the information of the first resource, the first resource may be directly used to send the data of the first broadcast service to the terminal device in the first network.
  • the radio access network device may acquire information about the first resource allocated for the first broadcast service in the second network according to the identifier of the first broadcast service.
  • the radio access network device may send the data of the first broadcast service for the terminal device in the first network through the first resource. That is, the radio access network device can reuse the first resource without reallocating resources for the first broadcast service in other networks, thereby avoiding waste of resources.
  • the present application also provides a broadcast communication method 200, which can be executed by, for example, a network element with a multicast/broadcast session management function.
  • the method 200 includes the following steps.
  • a network element with a multicast/broadcast session management function receives an identifier of a first broadcast service.
  • the multicast/broadcast session management functional network element may be a multicast/broadcast session management functional network element located in the first network, or may be a multicast/broadcast session management functional network element located in the second network. Do limited.
  • the identifier of the first broadcast service includes a first identifier.
  • first identifier for the description of the first identifier, reference may be made to the description of step 101 in the method 100, which will not be repeated here.
  • the multicast/broadcast session management function network element receiving the identifier of the first broadcast service includes: the multicast/broadcast session management function network element receives the identification of the first broadcast service from the application function network element logo.
  • the method 200 may also include:
  • the multicast/broadcast session management function network element receives a third message from the application function network element, the third message carries the identifier of the first broadcast service, and the third message is used to trigger the multicast/broadcast session management function network
  • the element sends the temporary mobile group identifier of the first broadcast service to the application function network element.
  • the multicast/broadcast session management function network element obtains the temporary mobile group identifier of the first broadcast service from the first network element according to the third message, or; the multicast/broadcast session management function network element according to the third message, for the first network element A broadcast service is assigned a temporary mobile group identity.
  • the third message may be a TMGI allocation request (TMGIallocation request) message.
  • TMGIallocation request TMGIallocation request
  • the first network element may be a unified data management network element, a unified data storage network element, a network storage function network element, a network discovery function network element, a policy control function network element, or a multicast/broadcast database.
  • the multicast/broadcast database can be shared by at least two networks.
  • the multicast/broadcast session management functional network element receiving the identifier of the first broadcast service includes: the multicast/broadcast session management functional network element receives the multicast/broadcast user plane functional network element The identifier of the first broadcast service, wherein the identifier of the first broadcast service is a globally unique identifier of the first broadcast service.
  • the method 200 may also include:
  • the multicast/broadcast session management function network element sends a fourth message to the multicast/broadcast user plane function network element, the fourth message is used to request the session establishment or modification of the first broadcast service, the fourth message carries the first indication information, and the fourth message
  • the indication information is used to trigger the multicast/broadcast user plane functional network element to detect the identifier of the first broadcast service.
  • the globally unique identifier of the first broadcast service can be successfully obtained, that is, the identifier of the first broadcast service can be obtained without relying on the application functional network element.
  • the multicast/broadcast user plane functional network element may be a multicast/broadcast user plane functional network element located in the first network, or may be a multicast/broadcast user plane functional network element located in the second network. Do limited.
  • the fourth message may be an N4 session establishment or modification request (N4mbsession establishment/modification request) message.
  • Step 202 the multicast/broadcast session management function network element sends the identifier of the first broadcast service to the access and mobility management function network element.
  • the access and mobility management functional network element may be an access and mobility management functional network element located in the first network, or may be an access and mobility management functional network element located in the second network, which is not limited.
  • the multicast/broadcast session management functional network element can receive the identifier of the first broadcast service and send it to the access and mobility management functional network element, so that the radio access network equipment can obtain the identifier of the first broadcast service , identifying the same broadcast data in different networks.
  • the present application also provides a broadcast communication method 300 , which can be executed, for example, by an application function network element.
  • the method 300 includes the following steps.
  • Step 301 the application function network element obtains the identifier of the first broadcast service.
  • the identifier of the first broadcast service includes a first identifier.
  • first identifier for the description of the first identifier, reference may be made to the description of step 101 in the method 100, which will not be repeated here.
  • obtaining the identifier of the first broadcast service by the application function network element includes: generating the globally unique identifier of the first broadcast service by the application function network element.
  • the application function network element obtaining the identifier of the first broadcast service includes: the application function network element receiving the first broadcast from the first multicast/broadcast session management function network element in the first network The identification of the service in the first network; the application function network element receives the identification of the first broadcast service in the second network from the second multicast/broadcast session management function network element in the second network.
  • the application function network element can acquire the identifier of the first broadcast service in each network through interaction with the network elements of the core network of each network.
  • the application function network element obtaining the identifier of the first broadcast service includes: the application function network element obtaining the temporary mobile group identifier of the first broadcast service from the multicast/broadcast session management function network element.
  • Step 302 the application function network element sends the identifier of the first broadcast service to the multicast/broadcast session management function network element.
  • the application function network element can flexibly acquire the identifier of the first broadcast service through the above implementation manners.
  • the application function network element can send the obtained identifier of the first broadcast service to the multicast/broadcast session management function network element, so that the wireless access network device can obtain the identifier of the first broadcast service, and the Identify the same broadcast data in the network.
  • the present application also provides a broadcast communication method 400, which can be executed by a first network element, and the method 400 includes the following steps.
  • Step 401 the first network element receives the fifth message from the multicast/broadcast session management function network element.
  • the fifth message may carry the identifier of the first broadcast service, and the fifth message may be used to trigger the first network element to send the temporary mobile group identifier of the first broadcast service.
  • the fifth message may be a message for requesting creation of broadcast sessions, or the fifth message may be a multicast/broadcast session creation request message (for example, Nmbsmf_MBS sessioncreate request) for requesting the first A temporary mobile group identifier for a broadcast service.
  • a multicast/broadcast session creation request message for example, Nmbsmf_MBS sessioncreate request
  • Step 402 the first network element sends the temporary mobile group identifier of the first broadcast service to the multicast/broadcast session management functional network element according to the fifth message.
  • the method 400 further includes: the first network element receives the correspondence between the first broadcast service identifier and the temporary mobile group identifier from the multicast/broadcast session management functional network element. It can also be understood that the temporary mobile group identifier of the first broadcast service pre-stored on the first network element does not completely include the temporary mobile group identifier of the first broadcast service in each network. At this time, the multicast/broadcast session management The functional network element may assign a temporary mobile group identifier to the first broadcast service in the network, and send it to the first network element for storage.
  • the temporary mobility group identifier is shared by at least two networks.
  • its temporary mobile group identifier is the same in all networks.
  • its temporary mobile group identifier is different in each network, but through the temporary mobile group identifier in each network, the network elements of the core network and the radio access network equipment of each network can identify its indication All of them are the first broadcasting business.
  • the identifier of the first broadcast service in different networks can be identified by the network elements of the core network or radio access network equipment of each network as indicating the first broadcast service.
  • One broadcast service so that the wireless access network equipment does not need to re-allocate resources for the first broadcast service in different networks, avoiding the waste of air interface resources.
  • the first network uses PLMN#a as an example
  • the second network uses PLMN#b as an example for illustration
  • the terminal device uses UE as an example for illustration.
  • the suffix of the network element of the core network is "#b", which means that the network element of the core network is in PLMN#b
  • the suffix of the network element of the core network is "#a”, which means that the network element of the core network is in PLMN#a.
  • the RAN in the following specific embodiments can be understood as the RAN shared by PLMN #a and PLMN #b.
  • FIG. 8 is a schematic flowchart of a broadcast communication method 500 provided by the present application. Assuming that there are two PLMNs (denoted as PLMN#a and PLMN#b) in this embodiment, the broadcast service #1 is taken as an example for illustration in this embodiment, and the method includes:
  • step 501 the AF requests the identification of the broadcast service #1 in different PLMNs from different PLMN networks.
  • the identifier of the broadcast service #1 in different PLMNs may be an MBS Session ID, for example, a temporary mobile group identifier (TMGI), which will not be described in detail below.
  • MBS Session ID for example, a temporary mobile group identifier (TMGI), which will not be described in detail below.
  • TMGI temporary mobile group identifier
  • AF requests the identifier of broadcast service #1 from MB-SMF#a in PLMN#a, assuming that AF obtains the identifier of broadcast service #1 in PLMN#a as TMGI#x; MB-SMF#b in requesting the identifier of the broadcast service #1, it is assumed that the AF obtains the identifier of the broadcast service #1 in the PLMN#b as TMGI#y.
  • step 502 the AF generates a globally unique identifier of the broadcast service #1.
  • the AF generates the globally unique identifier of the broadcast service #1 based on the identifier of the broadcast service #1 in the PLMN #a and the identifier of the broadcast service #1 in the PLMN #b.
  • the globally unique identifier of the broadcast service #1 can be used to identify the data of the broadcast service #1; for another example, the globally unique identifier can be a number; for another example, it can be used to identify the broadcast service Address information of #1 and so on.
  • the globally unique identifier of broadcast service #1 may be the data used to identify broadcast service #1, for example, Indication#z; as an example, for broadcast service #2, its globally unique identifier may be the data used to identify broadcast service #2. Data of service #2, for example, Indication#w.
  • the globally unique identifier of the broadcast service #1 may also be the IP multicast address of the broadcast service #1. It should be noted that, in this implementation, if the globally unique identifier of the broadcast service #1 is the IP multicast address of the broadcast service #1, optionally, step 501 is not performed. It can also be understood that, at this time, the AF does not need to first request the TMGI of the broadcast service #1 in each PLMN from each PLMN.
  • MB-SMF #b when the subsequent AF sends a session creation request message to MB-SMF#b, if it only carries the IP multicast address of broadcast service #1, but does not carry the TMGI in PLMN#b, then MB-SMF #b will provide AF with the TMGI of broadcast service #1 in PLMN #b.
  • the TMGIs for example, TMGI #x, TMGI #y
  • the broadcast service #1 have the same indication #z (an example of the global unique identifier of the broadcast service #1)
  • the subsequent The base station can recognize that in different PLMNs, these different broadcast service identifiers actually correspond to the same broadcast service (ie, broadcast service #1).
  • the TMGIs are different (for example, the broadcast service #1 has different TMGIs in different PLMNs)
  • the RAN can determine that what it requests to transmit is the same broadcast service, that is, what it requests to transmit is the same broadcast data.
  • the TMGIs for example, TMGI#x, TMGI#y
  • the subsequent base station can recognize that in different PLMNs, these different TMGIs actually correspond to the same broadcast service (ie, broadcast service #1).
  • the identifiers of the broadcast service #1 are different (for example, the broadcast service #1 has different TMGIs in different PLMNs)
  • the requests for transmission are all broadcast service #1, or , it can also be understood that what is requested for transmission is the broadcast data of the broadcast service #1.
  • Step 503 AF sends a session create request (session create request) message to MB-SMF#b in PLMN#b.
  • MB-SMF#b in PLMN#b receives the broadcast session creation request.
  • the session establishment request message carries the globally unique identifier of the broadcast service #1, for example, the session establishment request message carries the Indication#z of the broadcast service #1.
  • the broadcast session creation request message carries the IP multicast address of the broadcast service #1.
  • the AF may send a session creation request to MB-SMF#b.
  • the AF sends a broadcast session creation request to MB-SMF#b by calling the Nmbsmf_MBSSession_Create Request service. It can also be understood that the AF is in the trusted domain (trusted domain) at this time.
  • the AF may first send a session creation request to the NEF, and then the NEF forwards the session creation request to MB-SMF#b.
  • the AF first sends the session creation request to the NEF by calling the Nnef_MBSSession_Create request service, and then the NEF calls the Nmbsmf_MBSSession_Create Request service to forward the session creation request to MB-SMF#b.
  • the AF is in an untrusted domain (untrusted domain), and the NEF may adjust some information in the broadcast session creation request.
  • AF since AF is in an untrusted domain and does not know the planning of a specific cell, AF may provide geographic area information, and NEF will "translate" the geographic area information into cell or tracking area information and send it to MB-SMF#b .
  • the session creation request message sent by AF to MB-SMF#b may also carry one or more of the following information: for example, the identifier TMGI#y of broadcast service #1 in PLMN#b, broadcast service #1 demand information, broadcast area information.
  • the requirement information of the broadcast service #1 may include, for example, the delay requirement of the broadcast service #1, the priority requirement of the broadcast service #1, the bandwidth requirement of the broadcast service #1, and the like. Or, alternatively, it can also be broadcast policy information. For example: 5G service quality (quality of service, QoS) identifier (identifier) (ie, 5QI), allocation and preemption priority (allocation and retention priority, ARP) information etc.
  • 5G service quality quality of service, QoS
  • identifier ie, 5QI
  • allocation and preemption priority allocation and retention priority, ARP
  • Step 504 MB-SMF#b in PLMN#b obtains the QoS information of the session of broadcast service #1.
  • MB-SMF#b can send the obtained demand information of broadcast service #1 to the network element of PCF#b, and obtain the session information of broadcast service #1 from the network element of PCF#b Policy information, based on which the QoS information of the broadcast session is generated.
  • the AF can send the demand information of the broadcast service #1 to PCF #b, and the PCF #b generates the policy information of the broadcast session according to the service demand information, and the PCF #b can send the broadcast service #
  • the policy information of the session of 1 is pushed to MB-SMF#b, and MB-SMF#b generates the QoS information of the broadcast session according to the policy information.
  • MB-SMF#b can generate the QoS information of the broadcast session according to the obtained demand information of the broadcast service #1 and according to a locally configured policy.
  • Step 505 MB-SMB#b selects AMF#b, and sends a session start request (session start request) message to AMF#b.
  • AMF#b receives the session start request message.
  • MB-SMF#b can select which AMF to send to in combination with the broadcast area information and the coverage area of the AMF.
  • MB-SMF#b may also select according to other methods, for example, MB-SMF#b sends a session start request message to all AMFs. At this time, AMF#b can accept the request sent by MB-SMF#b according to its own coverage area and broadcast area information.
  • the session start request message carries the globally unique identifier of the broadcast service #1. For example, Indication#z; and for example, the IP multicast address of the broadcast service #1.
  • the session start request message may also carry one or more of the following information: for example, the identifier TMGI#y of broadcast service #1 in PLMN#b, broadcast area information (for example, cell list ), the tracking area list ((tracking area, TA) list), and the QoS information of the broadcast session.
  • broadcast area information for example, cell list
  • tracking area list (tracking area, TA) list
  • QoS information of the broadcast session may also carry one or more of the following information: for example, the identifier TMGI#y of broadcast service #1 in PLMN#b, broadcast area information (for example, cell list ), the tracking area list ((tracking area, TA) list), and the QoS information of the broadcast session.
  • Step 506 AMF#b selects RAN#x (for example, a base station), and sends an N2 request (N2 request) message (an example of a second message) to RAN#x.
  • RAN#x for example, a base station
  • N2 request an example of a second message
  • RAN#x receives the N2 request message.
  • AMF#b may select RAN#x in combination with the broadcasted area information and the coverage area of the RAN.
  • AMF#b may also select according to other methods, for example, AMF#b sends a message to all RANs, and so on. At this time, RAN#x can judge and accept the request sent by AMF#b according to its own coverage area and broadcast area information.
  • the N2 request message carries the globally unique identifier of the broadcast service #1. For example, Indication#z; and for example, the IP multicast address of the broadcast service #1.
  • the N2 request message may also carry one or more of the following information: for example, the identifier TMGI#y of the broadcast service #1 in the PLMN#b, the broadcast area information (for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#y of the broadcast service #1 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#y of the broadcast service #1 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • the N2 request message is used to trigger RAN#x to allocate resources for broadcast service #1, in other words, the N2 request message is used to request RAN#x to allocate resources for broadcast service #1. It can also be understood that the N2 request message is used to request the RAN#x to establish a session context corresponding to the broadcast service #1.
  • the information in the N2 request message sent by AMF#b to RAN#x may not be exactly the same as the information in the session start message sent by MB-SMF#b to AMF#b.
  • the N2 request message sent by AMF#b to RAN#x may also include other information generated by AMF#b.
  • tunnel identification information Next generation application protocol (next generation application protocol, NGAP) identification information for example: AMF NGAP ID, RAN NGAP ID, etc., which will not be described in detail below.
  • Step 507 RAN#x allocates the first resource for the broadcast service #1 based on the N2 request message, and establishes a broadcast session context corresponding to the broadcast service #1.
  • the broadcast session context may include the globally unique identifier of the broadcast service #1 and the information of the first resource.
  • the context of the broadcast session may also be understood as “the context information of the broadcast session”, which will not be described in detail below.
  • the first resource can also be understood as being used to send the data of the broadcast service #1 to the UE in the PLMN #b.
  • RAN#x may allocate corresponding first resources according to the QoS information of the broadcast session. For example, resource reservation is performed for a QoS flow (flow) with a guaranteed bit rate (guaranteed bit rate, GBR).
  • the information of the first resource of the broadcast service #1 determined by RAN#x may include: (1) Multicast received group-radio network temporary identity (G-RNTI) information. (2) Information about the bandwidth part (BWP) corresponding to the broadcast service #1. For example, the service is received at the BWP, and the BWP corresponding to the sub-carrier space (sub-carrier space, SCS), frequency domain position and the length of the cyclic prefix (cyclic prefix, CP) are determined according to the BWP configuration.
  • G-RNTI Multicast received group-radio network temporary identity
  • BWP bandwidth part
  • the BWP configuration information also includes physical downlink control channel (physical downlink control channel, PDCCH) detection control resource set (control resource set, COREST) configuration information, the COREST configuration information indicates the time and frequency of the PDCCH for G-RNTI resource.
  • PDCCH physical downlink control channel
  • COREST control resource set
  • the parameters of discontinuous reception (DRX) of G-RNTI can also be understood as that the UE uses the DRX parameters to perform G-RNTI detection.
  • the configuration of the demodulation reference signal can also be understood as that the UE uses the reference signal to demodulate the PDSCH scheduled by the G-RNTI.
  • Information of the rate matching reference signal is also be understood as that the UE uses the reference signal to demodulate the PDSCH scheduled by the G
  • the broadcast session context corresponding to the broadcast service #1 established by RAN#x may also include: the identifier TMGI#y of the broadcast service #1 in PLMN#b, the broadcast area information (for example, the information of the cell list (for example, the cell list (cell list) information, tracking area list ((tracking area, TA) list), broadcast session QoS context (for example, including one or more contexts corresponding to MBS QoS flows. For example, QoS flow Identifier, QoS flow level QoS parameters and identification information of the MBS session).
  • the broadcast area information for example, the information of the cell list (for example, the cell list (cell list) information, tracking area list ((tracking area, TA) list
  • broadcast session QoS context for example, including one or more contexts corresponding to MBS QoS flows. For example, QoS flow Identifier, QoS flow level QoS parameters and identification information of the MBS session).
  • the broadcast session context may also include radio bearer (radio bearer) information of the MBS session, which will not be described in detail below.
  • radio bearer radio bearer
  • RAN#x may determine whether to store the broadcast session context according to whether it is located in the area corresponding to the broadcast area information. For example, if RAN#x judges that it is located in the area corresponding to the broadcast area information, it will store the broadcast session context; for another example, if RAN#x judges that it is not in the area corresponding to the broadcast area information, it will not store the broadcast session context. Let me repeat.
  • Step 507 can also be understood as, RAN#x searches for the broadcast session context corresponding to the broadcast service #1 based on the N2 request message and the globally unique identifier (for example, Indication#z) of the broadcast service #1. If RAN#x does not find the context of the broadcast session containing Indication#z, RAN#x determines that resources have not been allocated for broadcast service #1, and further, RAN#x allocates resources for broadcast service #1 in PLMN#b resource, and establish a broadcast session context corresponding to broadcast service #1.
  • RAN#x searches for the broadcast session context corresponding to the broadcast service #1 based on the N2 request message and the globally unique identifier (for example, Indication#z) of the broadcast service #1. If RAN#x does not find the context of the broadcast session containing Indication#z, RAN#x determines that resources have not been allocated for broadcast service #1, and further, RAN#x allocates resources for broadcast service #1 in PLMN#b resource, and establish a broadcast session context corresponding to broadcast service #1.
  • Step 508 RAN#x sends an N2 response message to AMF#b.
  • RAN#x sends an N2 response message to AMF#b to respond to the N2 request message sent by AMF#b.
  • Step 509 AMF#b sends a session start response message to MB-SMF#b.
  • AMF#b sends a session start response message to MB-SMF#b to respond to the session start request message sent by MB-SMF#b.
  • each network may also include MB-SMF#b configuring MB-UPF#b (for example, configuring MB-UPF#b to identify multicast data, forwarding rules, etc. ), and MB-SMF#b sends the response message of the session creation request to the AF, etc.
  • the specific content can refer to the protocol 3GPPTS 23.247, and will not be repeated here.
  • the above steps 503 to 509 are the process of establishing a broadcast session corresponding to the broadcast service #1 in PLMN#b and allocating the first resource for the data of the broadcast service #1.
  • the following steps 510-516 are to establish a broadcast session corresponding to broadcast service #1 in PLMN#a and use the first resource allocated for broadcast service #1 in PLMN#b to send broadcast service #1 to UE in PLMN#a data flow.
  • Step 510 AF sends a broadcast session create request (session create request) message to MB-SMF#a in PLMN#a.
  • MB-SMF#a in PLMN#a receives the broadcast session creation request.
  • the broadcast session creation request message carries the globally unique identifier of the broadcast service #1, for example, the broadcast session creation request message carries the Indication#z of the broadcast service #1; for another example, the broadcast session creation request message carries the IP address of the broadcast service #1 multicast address.
  • the AF may send a broadcast session creation request to MB-SMF#a.
  • the AF sends a broadcast session creation request to MB-SMF#a by calling the Nmbsmf_MBSSession_Create Request service. It can also be understood that the AF is in the trusted domain (trusted domain) at this time.
  • the AF may first send a session creation request to the NEF, and then the NEF forwards the session creation request to MB-SMF#a.
  • the AF first sends the session creation request to the NEF by calling the Nnef_MBSSession_Create request service, and then the NEF calls the Nmbsmf_MBSSession_Create Request service to forward the session creation request to MB-SMF#a.
  • the AF is in an untrusted domain (untrusted domain), and the NEF may adjust some information in the broadcast session creation request.
  • the AF may provide geographical area information, and the NEF will "translate" the geographical area information into cell or tracking area information and send it to MB-SMF#a.
  • the session establishment request message sent by the AF to the MB-SMF#a carries the globally unique identifier of the broadcast service #1.
  • the session creation request message may also carry one or more of the following information: for example, the identifier TMGI#x of the broadcast service #1 in the PLMN#a, the demand information of the broadcast service #1, and the broadcast area information.
  • the requirement information of the broadcast service #1 may include, for example, the delay requirement of the broadcast service #1, the priority requirement of the broadcast service #1, the bandwidth requirement of the broadcast service #1, and the like. Or, alternatively, it can also be broadcast policy information. For example: 5G service quality (quality of service, QoS) identifier (identifier) (ie, 5QI), allocation and preemption priority (allocation and retention priority, ARP) information etc.
  • 5G service quality quality of service, QoS
  • identifier ie, 5QI
  • allocation and preemption priority allocation and retention priority, ARP
  • Step 511 MB-SMF#a in PLMN#a acquires the QoS information of the session of broadcast service #1.
  • MB-SMF#a can send the obtained demand information of broadcast service #1 to PCF#a network element, and obtain the session policy information of broadcast service #1 from the PCF network element , generating the QoS information of the broadcast session according to the policy information.
  • MB-SMF#a may directly obtain policy information of the session of broadcast service #1 from PCF#a, and generate QoS information of the broadcast session according to the policy information.
  • MB-SMF#a may generate the QoS information of the broadcast session according to the obtained demand information of the broadcast service #1 and according to a locally configured policy.
  • Step 512 MB-SMB#a selects AMF#a network element, and sends a session start request (session start request) message to AMF#a.
  • AMF#a receives the session start request message.
  • MB-SMF#a may select which AMF to send to in combination with the broadcast area information and the coverage area of the AMF.
  • MB-SMF#a may also select according to other methods, for example, MB-SMF#a sends a session start request message to all AMFs. At this time, AMF#a can accept the request sent by MB-SMF#a according to its own coverage area and broadcast area information.
  • the session start request message carries the globally unique identifier of the broadcast service #1. For example, Indication#z; and for example, the IP multicast address of the broadcast service #1.
  • the session start request message may also carry one or more of the following information: for example, the identifier TMGI#x of the broadcast service #1 in the PLMN#a, the broadcast area information (for example, the cell list (cell list) Information, tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • the broadcast area information for example, the cell list (cell list) Information, tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • Step 513 AMF#a selects RAN#x (for example, a base station), and sends an N2 request (N2 request) message (an example of the first message) to RAN#x.
  • RAN#x for example, a base station
  • N2 request an example of the first message
  • RAN#x receives the N2 request message.
  • AMF#a may select RAN#x in combination with the broadcasted area information and the coverage area of the RAN.
  • AMF#a may also select according to other methods, for example, AMF#a sends a message to all RANs, and so on. At this time, RAN#x can accept the request sent by the AMF according to its own coverage area and broadcast area information.
  • RAN the same RAN is selected in PLMN#b and PLMN#a, for example, RAN#x.
  • RANs may be shared (for example, the same RAN) in different networks, which will not be described in detail below.
  • the N2 request message carries the globally unique identifier of the broadcast service #1, for example, Indication#z; and for example, the IP multicast address of the broadcast service #1.
  • the N2 request message may also carry one or more of the following information: for example, the identifier TMGI#x of the broadcast service #1 in the PLMN#b, the broadcast area information (for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#x of the broadcast service #1 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#x of the broadcast service #1 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • the N2 request message is used to trigger RAN#x to allocate resources for broadcast service #1, in other words, the N2 request message is used to request RAN#x to allocate resources for broadcast service #1. It can also be understood that the N2 request message is used to request the RAN#x to establish a session context corresponding to the broadcast service #1.
  • the information in the N2 request message sent by AMF#a to RAN#x may not be exactly the same as the information in the session start message sent by MB-SMF#a to AMF #a.
  • the N2 request message sent by AMF#a to RAN#x may also include other information generated by AMF#a. For example, tunnel identification information, next generation application protocol (next generation application protocol, NGAP) identification information (for example: AMF NGAP ID, RAN NGAP ID) and so on.
  • NGAP next generation application protocol
  • Step 514 RAN#x judges whether resources have been allocated for broadcast service #1 based on the N2 request message and the globally unique identifier of broadcast service #1. If resources have been allocated for broadcast service #1, RAN#x sends the data of broadcast service #1 in PLMN#a through the resources; and/or, if RAN#x has not allocated resources for broadcast service #1, RAN #x allocates resources for broadcasting service #1.
  • the RAN#x searches for the broadcast session context corresponding to the broadcast service #1 based on the N2 request message and the globally unique identifier of the broadcast service #1, for example, Indication#z.
  • RAN#x determines that Indication#z has been included in the context of the broadcast session in PLMN#b, then RAN#x determines that resources have been allocated for broadcast service #1, and searches in the context of the broadcast session in PLMN#b to the first resource for information.
  • the RAN#x determines not to establish the air interface resource corresponding to the broadcast service #1 in the PLMN#a, and does not establish the context corresponding to the broadcast service #1 in the PLMN#a. That is, the RAN#x determines that the data of the broadcast service #1 in the PLMN#a can be sent through the first resource in the PLMN#b.
  • RAN#x searches for the globally unique identifier of broadcast service #1, the second resource has been allocated for broadcast service #1 in PLMN#a, and the second resource is allocated in PLMN#a A context is established for Broadcast Service #1 in .
  • RAN#x After the search by RAN#x, it is determined that resources have been allocated for the broadcast service #1 in PLMN#b before, and the information of the first resource is found in the context of the broadcast session in PLMN#b. Then RAN#x can delete ("delete” can also be understood as "release”) the second resource allocated for broadcast service #1 in PLMN #a, and delete the context established for broadcast service #1 in PLMN #a.
  • the RAN#x determines that the data of the broadcast service #1 in the PLMN#a can be sent through the first resource in the PLMN#b.
  • RAN#x may not send the data of broadcast service #1 in PLMN#a on the second resource, but still use the first resource allocated for broadcast service #1 in PLMN#b to send broadcast service #1 in PLMN#b The data.
  • the "searching for the broadcast session context corresponding to the broadcast service #1" of RAN#x may be, for example, the following implementation manners.
  • RAN#x after receiving the globally unique identifier, RAN#x will check whether the globally unique identifier exists in the locally stored broadcast session context. If there is a broadcast session context, its corresponding globally unique identifier and If the globally unique identifiers of the broadcast service #1 are the same, then the search can be considered successful; otherwise, RAN#x can consider that the broadcast service #1 has not yet established a context in the base station. In other words, this is the first time that RAN#x receives the N2 message. The following will not repeat them.
  • RAN #x transmits the data of broadcast service #1 in PLMN #a through this resource
  • RAN#x recognizes that the data belongs to the broadcast service# 1. After that, RAN#x can send the data of the broadcast service #1 on the air interface (for example, time-frequency resource) resources according to the locally stored context information (for example, scheduling queue, reserved resources), etc. Terminal devices located on different networks but receiving the broadcast service #1 will monitor the corresponding air interface resources, and then can receive the data of the broadcast service #1. The following will not repeat them.
  • Step 515 RAN#x sends an N2 response message to AMF#a.
  • RAN#x sends an N2 response message to AMF#a in response to the N2 request message sent by AMF#a.
  • Step 516 AMF#a sends a session start response message to MB-SMF#a.
  • AMF#a sends a session start response message to MB-SMF#a to respond to the session start request message sent by MB-SMF#a.
  • the RAN can identify the same broadcast service in the scenario where different operators share the base station, so that the RAN can identify the same broadcast service in PLMN#b
  • the allocated resources are used to send the data of the broadcast service in PLMN#a.
  • the RAN can share air interface resources with users of different operators, which can save transmission resources of the RAN and avoid waste of air interface resources.
  • FIG. 9 is a schematic flowchart of a broadcast communication method 600 provided by the present application. Assuming that there are two PLMNs (denoted as PLMN#a and PLMN#b) in this embodiment, the broadcasting service #2 is taken as an example for illustration in this embodiment, and the method includes:
  • Step 601 AF sends a session create request (session create request) message to MB-SMF#b in PLMN#b.
  • MB-SMF#b in PLMN#b receives the session establishment request.
  • the MB-SMF#b can provide the AF with the TMGI of the broadcast service #2 in the PLMN#b, for example, TMGI#p.
  • step 503 in the method 500 For the manner in which the AF sends the session creation request to MB-SMF#b, reference may be made to step 503 in the method 500 .
  • the session creation request message sent by AF to MB-SMF#b carries one or more of the following information: for example, the MBS session identifier of broadcast service #2, such as TMGI#p, broadcast service #2 Demand information, broadcast area information.
  • the requirement information of the broadcast service #2 may include, for example, the delay requirement of the broadcast service #2, the priority requirement of the broadcast service #2, the bandwidth requirement of the broadcast service #2, and the like. Or, alternatively, it can also be broadcast policy information. For example: 5G service quality (quality of service, QoS) identifier (identifier) (ie, 5QI), allocation and preemption priority (allocation and retention priority, ARP) information etc.
  • 5G service quality quality of service, QoS
  • identifier ie, 5QI
  • allocation and preemption priority allocation and retention priority, ARP
  • Step 602 MB-SMF#b in PLMN#b acquires the QoS information of the session of broadcast service #2.
  • step 504 in the method 500 For the manner in which MB-SMF#b acquires the session QoS information of the broadcast service #2, reference may be made to step 504 in the method 500, which will not be repeated here.
  • Step 603 MB-SMB#b selects AMF#b, and sends a session start request (session start request) message to AMF#b.
  • AMF#b receives the session start request message.
  • step 505 in method 500 for the manner in which MB-SMB#b selects AMF#b, reference may be made to step 505 in method 500, which will not be repeated here.
  • the session start request message may also carry one or more of the following information: for example, the identifier TMGI#p of broadcast service #2 in PLMN#b, broadcast area information (for example, cell list (cell list) information, tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • broadcast area information for example, cell list (cell list) information, tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#p of broadcast service #2 in PLMN#b
  • broadcast area information for example, cell list (cell list) information, tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#p of broadcast service #2 in PLMN#b
  • broadcast area information for example, cell list (cell list) information, tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#p of broadcast service #2
  • Step 604 AMF#b selects RAN#x (for example, a base station), and sends an N2 request (N2 request) message (an example of a second message) to RAN#x.
  • RAN#x for example, a base station
  • N2 request an example of a second message
  • RAN#x receives the N2 request message.
  • step 506 in method 500 for the manner in which AMF#b selects RAN#x, reference may be made to step 506 in method 500, which will not be repeated here.
  • the N2 request message may also carry one or more of the following information: for example, the identifier TMGI#p of broadcast service #2 in PLMN#b, broadcast area information (for example, cell list (cell list), the tracking area list ((tracking area, TA) list), and the QoS information of the broadcast session.
  • broadcast area information for example, cell list (cell list), the tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#p of broadcast service #2 in PLMN#b
  • broadcast area information for example, cell list (cell list), the tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#p of broadcast service #2 in PLMN#b
  • broadcast area information for example, cell list (cell list), the tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#p of broadcast service #2 in P
  • the N2 request message is used to trigger RAN#x to allocate resources for broadcast service #2.
  • the N2 request message is used to request RAN#x to allocate resources for broadcast service #2. It can also be understood that the N2 request message is used to request the RAN#x to establish a session context corresponding to the broadcast service #2.
  • Step 605 RAN#x allocates the first resource for the broadcast service #2 based on the N2 request message, and establishes a broadcast session context corresponding to the broadcast service #2.
  • the first resource can also be understood as being used to send the data of the broadcast service #2 to the UE in the PLMN #b.
  • RAN#x may allocate corresponding first resources according to the QoS information of the broadcast session. For example, resource reservation is performed for a QoS flow (flow) with a guaranteed bit rate (guaranteed bit rate, GBR).
  • the information of the first resource of the broadcast service #2 determined by RAN#x may include: (1) Group-radio network temporary identity (G-RNTI) for multicast reception. (2) Information about the bandwidth part (BWP) corresponding to the broadcast service #2. For example, the service is received at the BWP, and the BWP corresponding to the sub-carrier space (sub-carrier space, SCS), frequency domain position and the length of the cyclic prefix (cyclic prefix, CP) are determined according to the BWP configuration.
  • G-RNTI Group-radio network temporary identity
  • BWP bandwidth part
  • the BWP configuration information also includes physical downlink control channel (physical downlink control channel, PDCCH) detection control resource set (control resource set, COREST) configuration information, the COREST configuration information indicates the time and frequency of the PDCCH for G-RNTI resource.
  • PDCCH physical downlink control channel
  • COREST control resource set
  • the parameters of discontinuous reception (DRX) of G-RNTI can also be understood as that the UE uses the DRX parameters to perform G-RNTI detection.
  • the configuration of the demodulation reference signal can also be understood as that the UE uses the reference signal to demodulate the PDSCH scheduled by the G-RNTI.
  • Information of the rate matching reference signal is included in the rate matching reference signal.
  • the broadcast session context corresponding to the broadcast service #2 established by the RAN#x may also include: the identifier TMGI#p of the broadcast service #2 in the PLMN#b, the broadcast area information (for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list), QoS context of the broadcast session.
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS context of the broadcast session for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS context of the broadcast session for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list.
  • Step 606 RAN#x sends an N2 response message to AMF#b.
  • RAN#x sends an N2 response message to AMF#b to respond to the N2 request message sent by AMF#b.
  • Step 607 AMF#b sends a session start response message to MB-SMF#b.
  • AMF#b sends a session start response message to MB-SMF#b to respond to the session start request message sent by MB-SMF#b.
  • Step 608 MB-SMF #b configures MB-UPF #b.
  • MB-SMF#b sends an N4 session establishment or modification (N4mb Session establishment/modification) message (an example of the fourth message) to MB-UPF#b, and the message may contain one or more of the following contents: broadcast Identification information of service #2, instruction information #1 (an example of first instruction information).
  • the indication information #1 is used to instruct MB-UPF #b to detect the IP multicast address of the broadcast service #2 (an example of the globally unique identifier of the broadcast service #2).
  • MB-UPF #b detects the IP multicast address (eg, target IP address, source IP address, etc.) of the downlink data packet of broadcast service #2. Thereafter, the data of broadcast service #2 can be transmitted between the core network and RAN#x.
  • Step 609 MB-UPF #b sends a notification message (for example, a Notification message) to MB-SMF #b, and the notification message carries the IP multicast address of the broadcast service #2.
  • MB-SMF#b receives the notification message.
  • Step 610 MB-SMF #b sends the IP multicast address of broadcast service #2 to RAN.
  • MB-SMF#b first sends the IP multicast address to AMF#b by calling the Namf_MBSBroadcast_ContextUpdate service of AMF, and then AMF#b sends it to RAN#x through an N2 message.
  • Step 611 RAN#x saves the IP multicast address of broadcast service #2 in the broadcast session context established in PLMN#b.
  • RAN#x stores the IP multicast address of the downlink data packet of the broadcast service #2 as part of the broadcast session context.
  • the above steps 601 to 611 are to establish a broadcast session corresponding to the broadcast service #2 in PLMN#b, allocate the first resource for the data of the broadcast service #2, and store the globally unique identifier of the broadcast service #2 in the context of the broadcast session process.
  • the following steps 612-622 are to establish a broadcast session corresponding to broadcast service #2 in PLMN#a and use the first resource allocated for broadcast service #2 in PLMN#b to send broadcast service #2 to UE in PLMN#a data flow.
  • steps 612 to 615 you can refer to the description of steps 601 to 604 above. The difference is that steps 612 to 615 are all in PLMH#a, and the related core network elements involved are also the cores in PLMH#a network element.
  • the RAN#x allocates the first resource for the broadcast service #2 based on the N2 request message, and establishes a broadcast session context corresponding to the broadcast service #2.
  • step 605 the difference is that at this time, RAN#x allocates the second resource for the broadcast service #2 in PLMN#a, which will not be repeated here.
  • steps 617 to 618 you can refer to the above steps 606 to 607. The difference is that steps 617 to 618 are all in PLMH#a, and the relevant core network elements involved are also the core network in PLMH#a Yuan.
  • Step 619 MB-SMF#a configures MB-UPF#a.
  • MB-SMF#a sends an N4 session establishment or modification (N4mb session establishment/modification) message (an example of the fourth message) to MB-UPF#a, and the message may contain one or more of the following contents: broadcast Identification information of service #2, instruction information #2 (an example of first instruction information).
  • the indication information #2 is used to instruct MB-UPF #a to detect the IP multicast address of the broadcast service #2 (an example of the globally unique identifier of the broadcast service #3).
  • MB-UPF#a detects the IP multicast address (eg, target IP address, source IP address, etc.) of the downlink data packet of broadcast service #2. Thereafter, the data of broadcast service #2 can be transmitted between the core network and RAN#x.
  • Step 620 MB-UPF #a sends a notification message (for example, a Notification message) to MB-SMF #a, and the notification message carries the IP multicast address of the broadcast service #2.
  • a notification message for example, a Notification message
  • MB-SMF#a receives the notification message.
  • Step 621 MB-SMF#a sends the IP multicast address of broadcast service #2 to RAN#x.
  • MB-SMF#a first sends the IP multicast address to AMF#a by invoking the Namf_MBSBroadcast_ContextUpdate service of AMF, and then AMF#a sends the IP multicast address to RAN#x through an N2 message.
  • Step 622 RAN#x determines whether resources have been allocated for broadcast service #2 based on the IP multicast address of broadcast service #2. If resources have been allocated for broadcast service #2, the data of broadcast service #2 in PLMN#a is sent through the resources; and/or, if RAN has not allocated resources for broadcast service #2, RAN#x is broadcast service #2 Allocate resources.
  • RAN#x searches for the broadcast session context corresponding to broadcast service #2 based on the N2 request message and the globally unique identifier of broadcast service #2, for example, the IP multicast address of broadcast service #2. RAN#x determines that the IP multicast address of broadcast service #2 has been included in the context of the broadcast session in PLMN#b, then RAN#x determines that resources have been allocated for broadcast service #2, and the IP multicast address in PLMN#b Information about the first resource is found in the context of the broadcast session.
  • RAN#x can delete ("delete” can also be understood as “release”) the second resource allocated for broadcast service #2 in PLMN#a, and delete the context established for broadcast service #2 in PLMN#a,
  • the data of the broadcast service #2 in the PLMN #a is sent by using the first resource allocated for the broadcast service #1 in the PLMN #b.
  • RAN#x may not send the data of broadcast service #2 in PLMN#a on the second resource, but still use the first resource allocated for broadcast service #1 in PLMN#b to send broadcast service #2 in PLMN#a The data.
  • RAN#x does not perform step 616. At this time, RAN#x does not allocate the second resource for the broadcast service #2 in PLMN#a, and directly performs steps 617 to 622. At this time, RAN#x searches for the broadcast session context corresponding to the broadcast service #2 based on the N2 request message and the globally unique identifier of the broadcast service #2, for example, the IP multicast address of the broadcast service #2. RAN #x determines that the IP multicast address of broadcast service #2 is already included in the context of the broadcast session in PLMN #b.
  • RAN#x determines that resources have been allocated for broadcast service #1, and finds the information of the first resource in the context of the broadcast session in PLMN#b, then RAN#x determines not to establish broadcast service #2 in PLMN#a The corresponding air interface resource, and the context corresponding to the broadcast service #2 is not established in PLMN#a. That is, the RAN#x determines that the data of the broadcast service #2 in the PLMN#a can be sent through the first resource in the PLMN#b.
  • the RAN can identify the same broadcast service in the scenario where different operators share the base station, so that the RAN can identify the same broadcast service in PLMN#b
  • the allocated resources are used to send the data of the broadcast service in PLMN#a.
  • the RAN can share air interface resources with users of different operators, which can save transmission resources of the RAN and avoid waste of air interface resources.
  • FIG. 10 is a schematic flowchart of a broadcast communication method 700 provided by the present application. Assuming that there are two PLMNs (denoted as PLMN#a and PLMN#b) in this embodiment, the broadcasting service #3 is taken as an example for illustration in this embodiment, and the method includes:
  • step 701 the AF requests the identification of broadcast service #3 in different PLMNs from different PLMN networks.
  • AF requests the identifier of broadcast service #3 from MB-SMF#a in PLMN#a, assuming that AF obtains the identifier of broadcast service #3 in PLMN#a as TMGI#m; MB-SMF#b in requesting the identifier of the broadcast service #3, it is assumed that the AF obtains the identifier of the broadcast service #3 in the PLMN#b as TMGI#n.
  • Step 702 AF sends a session create request (session create request) message to MB-SMF#b in PLMN#b.
  • MB-SMF#b in PLMN#b receives the broadcast session creation request.
  • the session creation request message carries a list (list) of broadcast service identifiers of the broadcast service #3 in each PLMN network.
  • list For example, the identifier in PLMN#a is TMGI#m, and the identifier in PLMN#b is TMGI#n.
  • the list of broadcast service identifiers of the broadcast service #3 in each PLMN network may also be pre-configured on the RAN (the RAN may be, for example, RAN#x), where Then the AF does not need to provide this list in the session creation request message.
  • Pre-configuration can be understood as: the RAN is originally configured with a list of broadcast service IDs for broadcast service #3 in each PLMN network.
  • the identification in does not need to carry the entire list; it can also be understood as: the RAN receives the pre-configured list of identifications of the broadcast service #3 in each network when the first broadcast service session is established for the first time, and the RAN can store at this time the list. Therefore, when requesting to establish the session of the broadcast service #3 for a non-first time (for example, the second time), only the identifier of the broadcast service #3 in the network may be carried instead of the entire list. The following will not repeat them.
  • step 503 in the method 500 for the manner in which the AF sends the session establishment request message to the MB-SMF#b in the PLMN#b, reference may be made to step 503 in the method 500, which will not be repeated here.
  • Step 703, MB-SMF#b in PLMN#b acquires the QoS information of the session of broadcast service #3.
  • step 504 in method 500 For the manner in which MB-SMF#b in PLMN#b acquires the session QoS information of broadcast service #3, reference may be made to step 504 in method 500, which will not be repeated here.
  • Step 704 MB-SMB#b selects AMF#b, and sends a session start request (session start request) message to AMF#b.
  • AMF#b receives the session start request message.
  • step 505 in method 500 for the manner in which MB-SMF#b in PLMN#b selects an AMF, reference may be made to step 505 in method 500, which will not be repeated here.
  • the session start request message may carry a list of broadcast service identifiers of the broadcast service #3 in each PLMN network.
  • the identifier in PLMN#a is TMGI#m
  • the identifier in PLMN#b is TMGI#n.
  • the session start request message may also carry one or more of the following information: for example, the identifier TMGI#n of the broadcast service #3 in the PLMN#b, the broadcast area information (for example, the cell list (cell list) Information, tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • the broadcast area information for example, the cell list (cell list) Information, tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • Step 705 AMF#b selects RAN#x (for example, a base station), and sends an N2 request (N2 request) message (an example of a second message) to RAN#x.
  • RAN#x for example, a base station
  • N2 request an example of a second message
  • RAN#x receives the N2 request message.
  • step 506 in method 500 for the manner in which AMF#b selects RAN#x, reference may be made to step 506 in method 500, which will not be repeated here.
  • the N2 request message carries a list of broadcast service identifiers of the broadcast service #3 in each PLMN network.
  • the identifier in PLMN#a is TMGI#m
  • the identifier in PLMN#b is TMGI#n.
  • the N2 request message may also carry one or more of the following information: for example, the identifier TMGI#n of the broadcast service #3 in the PLMN#b, the broadcast area information (for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#n of the broadcast service #3 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#n of the broadcast service #3 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • the N2 request message is used to trigger the RAN to allocate resources for the broadcast service #3.
  • the N2 request message is used to request the RAN#x to allocate resources for the broadcast service #3. It can also be understood that the N2 request message is used to request the RAN #x to establish a session context corresponding to the broadcast service #3.
  • Step 706 RAN#x allocates the first resource for the broadcast service #3 based on the N2 request message, and establishes a broadcast session context corresponding to the broadcast service #3.
  • the broadcast session context includes a list of broadcast service identifiers of the broadcast service #3 in each PLMN network.
  • the identifier in PLMN#a is TMGI#m
  • the identifier in PLMN#b is TMGI#n.
  • the first resource can also be understood as being used to send the data of the broadcast service #3 to the UE in the PLMN #b.
  • RAN#x may allocate corresponding first resources according to the QoS information of the broadcast session. For example, resource reservation is performed for a QoS flow (flow) with a guaranteed bit rate (guaranteed bit rate, GBR).
  • the information of the first resource of the broadcast service #3 determined by RAN#x may include: (1) Multicast received group-radio network temporary identity (G-RNTI) information. (2) Information about the bandwidth part (BWP) corresponding to the broadcast service #3. For example, the service is received at the BWP, and the BWP corresponding to the sub-carrier space (sub-carrier space, SCS), frequency domain position and the length of the cyclic prefix (cyclic prefix, CP) are determined according to the BWP configuration.
  • G-RNTI Multicast received group-radio network temporary identity
  • BWP bandwidth part
  • the BWP configuration information also includes physical downlink control channel (physical downlink control channel, PDCCH) detection control resource set (control resource set, COREST) configuration information, the COREST configuration information indicates the time and frequency of the PDCCH for G-RNTI resource.
  • PDCCH physical downlink control channel
  • COREST control resource set
  • the parameters of discontinuous reception (DRX) of G-RNTI can also be understood as that the UE uses the DRX parameters to perform G-RNTI detection.
  • the configuration of the demodulation reference signal can also be understood as that the UE uses the reference signal to demodulate the PDSCH scheduled by the G-RNTI.
  • Information of the rate matching reference signal is also be understood as that the UE uses the reference signal to demodulate the PDSCH scheduled by the G
  • the broadcast session context corresponding to the broadcast service #3 established by the RAN#x may also include: the identifier TMGI#n of the broadcast service #3 in the PLMN#b, the broadcast area information (for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list), QoS context of the broadcast session.
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS context of the broadcast session for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS context of the broadcast session for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list.
  • Step 706 can also be understood as: RAN#x searches for the broadcast session context corresponding to broadcast service #3 based on the N2 request message and the list of broadcast service identifiers of broadcast service #3 in each PLMN network. RAN#x does not find the context of the broadcast session that contains the list of broadcast service identifiers of broadcast service #3 in each PLMN network, then RAN#x determines that resources have not been allocated for broadcast service #3, and needs to be allocated in PLMN#b Broadcast service #3 allocates resources, and establishes a broadcast session context corresponding to broadcast service #3.
  • Step 707 RAN#x sends an N2 response message to AMF#b.
  • RAN#x sends an N2 response message to AMF#b to respond to the N2 request message sent by AMF#b.
  • Step 708, AMF#b sends a session start response message to MB-SMF#b.
  • AMF#b sends a session start response message to MB-SMF#b to respond to the session start request message sent by MB-SMF#b.
  • the above steps 702 to 708 are the process of establishing a broadcast session corresponding to the broadcast service #3 in PLMN#b and allocating the first resource for the data of the broadcast service #3.
  • the following steps 709-715 are to establish a broadcast session corresponding to broadcast service #3 in PLMN#a and use the first resource allocated for broadcast service #3 in PLMN#b to send broadcast service #3 to UE in PLMN#a data flow.
  • Step 709 AF sends a session create request (session create request) message (an example of the fourth message) to MB-SMF#a in PLMN#a.
  • MB-SMF#a in PLMN#a receives the broadcast session creation request.
  • the broadcast session creation request message carries a list of broadcast service identifiers of the broadcast service #3 in each PLMN network.
  • the identifier in PLMN#a is TMGI#m
  • the identifier in PLMN#b is TMGI#n, and so on.
  • the broadcast session creation request message can only carry the identifier of broadcast service #3 in PLMN#a, such as TMGI#m, and there is no need to provide the complete list to RAN.
  • step 510 in the method 500 for the manner in which the AF sends the session creation request message to the MB-SMF#a in the PLMN#a, reference may be made to step 510 in the method 500, which will not be repeated here.
  • Step 710 MB-SMF#a in PLMN#a acquires the session QoS information of broadcast service #3.
  • step 511 in method 500 for MB-SMF#a in PLMN#a to acquire the QoS information of the session of broadcast service #3, reference may be made to step 511 in method 500, which will not be repeated here.
  • Step 711 MB-SMB#a selects an AMF network element, and sends a session start request (session start request) message (an example of the third message) to AMF#a.
  • AMF#a receives the session start request message.
  • step 512 in method 500 for the manner in which MB-SMF#a in PLMN#a selects AMF#a, reference may be made to step 512 in method 500, which will not be repeated here.
  • the broadcast session start request message carries a list of broadcast service identifiers of the broadcast service #3 in each PLMN network.
  • the identifier in PLMN#a is TMGI#m
  • the identifier in PLMN#b is TMGI#n.
  • the broadcast session start request message can only carry the identifier of broadcast service #3 in PLMN#a, such as TMGI#m, and there is no need to provide the complete list to RAN.
  • Step 712 AMF#a selects RAN#x (for example, a base station), and sends an N2 request (N2 request) message (an example of a second message) to RAN#x.
  • RAN#x for example, a base station
  • N2 request an example of a second message
  • RAN#x receives the N2 request message.
  • the N2 request includes a list of broadcast service identifiers of the broadcast service #3 in each PLMN network.
  • the identifier in PLMN#a is TMGI#m
  • the identifier in PLMN#b is TMGI#n.
  • the N2 request carries the broadcast service identifier of the broadcast service #3 in the PLMN#a network.
  • the identifier in PLMN#a is TMGI#m.
  • the N2 request message may also carry one or more of the following information: for example, the identifier TMGI#n of the broadcast service #3 in the PLMN#b, the broadcast area information (for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list), QoS information of the broadcast session.
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#n of the broadcast service #3 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • QoS information of the broadcast session for example, the identifier TMGI#n of the broadcast service #3 in the PLMN#b
  • the broadcast area information for example, the information of the cell list (cell list), Tracking area list ((tracking area, TA) list
  • Step 713 RAN#x determines whether resources have been allocated for broadcast service #3 based on the N2 request message and the list of broadcast service identifiers broadcast by broadcast service #3 in each PLMN network or broadcast service identifiers in PLMN#a network. If resources have been allocated for broadcast service #3, the data of broadcast service #3 in PLMN#a is sent through the resources; and/or, if RAN#x has not allocated resources for broadcast service #3, then RAN#x is Broadcast service #3 allocates resources.
  • RAN#x broadcasts a list of service identifiers in each PLMN network based on the N2 request message and the broadcast service #3.
  • the identifier in PLMN#a is TMGI#m
  • the identifier in PLMN#a is TMGI#m
  • the identifier in b is TMGI#n
  • the broadcast session context corresponding to the broadcast service #3 is searched. If RAN#x determines that the context of the broadcast session in PLMN#b already contains a list of broadcast service identifiers corresponding to broadcast service #3 in each PLMN network, then RAN#x determines that resources have been allocated for broadcast service #3 , and find the information of the first resource in the context of the broadcast session in PLMN#b.
  • the RAN#x determines not to establish the air interface resource corresponding to the broadcast service #3 in the PLMN#a, and does not establish the context corresponding to the broadcast service #3 in the PLMN#a. That is, the RAN#x determines that the data of the broadcast service #3 in the PLMN#a can be sent through the first resource in the PLMN#b.
  • the RAN#x searches for the broadcast session context corresponding to the broadcast service #3 based on the N2 request message and the broadcast service identifier TMGI#m of the broadcast service #3 in the PLMN#a network. If the RAN #x determines that the context of the broadcast session in the PLMN #b already includes the broadcast service #3, the broadcast service identifier TMGI #m in the PLMN #a network. Then RAN#x determines that resources have been allocated for broadcast service #3, and finds information about the first resource in the context of the broadcast session in PLMN#b.
  • the RAN#x determines not to establish the air interface resource corresponding to the broadcast service #3 in the PLMN#a, and does not establish the context corresponding to the broadcast service #3 in the PLMN#a. That is, the RAN#x determines that the data of the broadcast service #3 in the PLMN#a can be sent through the first resource in the PLMN#b.
  • RAN#x when RAN#x searches for the broadcast session context corresponding to broadcast service #3, if it finds that the corresponding broadcast service identifier of broadcast service #3 stored in the context in each network and the broadcast service ID carried in the N2 request message If the identifiers of service #3 have an intersection, RAN#x determines that resources have been allocated for broadcast service #3 and finds information about the first resource in the context of the broadcast session in PLMN#b. Then the RAN#x determines not to establish the air interface resource corresponding to the broadcast service #3 in the PLMN#a, and does not establish the context corresponding to the broadcast service #3 in the PLMN#a. That is, the RAN#x determines that the data of the broadcast service #3 in the PLMN#a can be sent through the first resource in the PLMN#b.
  • RAN#x is already in PLMN#a before searching for the list of broadcast service identifiers broadcast by broadcast service #3 in each PLMN network or by broadcasting service identifiers in PLMN#a network
  • a second resource is allocated for broadcast service #3, and a context is established for broadcast service #3 in PLMN #a. After the RAN#x searches, it is determined that resources have been allocated for the broadcast service #3 in the PLMN#b before, and the information of the first resource is found in the context of the broadcast session in the PLMN#b.
  • RAN#x can delete ("delete” can also be understood as “release”) the second resource allocated for broadcast service #1 in PLMN#a, and delete the context established for broadcast service #1 in PLMN#a, Alternatively, RAN#x may not send the data of broadcast service #3 in PLMN#a on the second resource, and still use the first resource allocated for broadcast service #1 in PLMN#b to send broadcast service #3 in PLMN#a The data.
  • Step 714 RAN#x sends an N2 response message to AMF#a.
  • RAN#x sends an N2 response message to AMF#a in response to the N2 request message sent by AMF#a.
  • Step 715 AMF#a sends a session start response message to MB-SMF#a.
  • AMF#a sends a session start response message to MB-SMF#a to respond to the session start request message sent by MB-SMF#a.
  • the RAN can identify the same broadcast service in the scenario where different operators share the base station, so that the RAN can pass
  • the resource allocated for the broadcast service in PLMN#b is used to transmit the data of the broadcast service in PLMN#a.
  • the RAN can share air interface resources with users of different operators, which can save transmission resources of the RAN and avoid waste of air interface resources.
  • FIG. 11 is a schematic flowchart of a broadcast communication method 800 provided by the present application. Assuming that there are two PLMNs (denoted as PLMN#a and PLMN#b) in this embodiment, the broadcasting service #4 is taken as an example for illustration in this embodiment, and the method includes:
  • PLMN #a and PLMN #b are configured with a common TMGI, which enables the MB-SMFs of PLMN #a and PLMN #b to provide a common TMGI when the AF requests the TMGI.
  • Universal TMGI in this application means that one or some TMGIs can be shared by several (ie, at least two) PLMN networks.
  • TMGI includes PLMN ID information and information inside the PLMN. It can also be understood that TMGI is specific in each PLMN (that is, PLMN-specific).
  • each PLMN can share the TMGI (TMGI can be PLMN-specific or non-PLMN specific, but can be shared among each PLMN).
  • TMGI can be PLMN-specific or non-PLMN specific, but can be shared among each PLMN.
  • the TMGI in PLMN #a is the same as the TMGI in PLMN #b, both are TMGI #q.
  • the central database stores the correspondence between each broadcast service identifier and the general TMGI.
  • the MB-SMF of each network can store the corresponding relationship between TMGI and broadcast service identifier in UDM, UDR, NRF, NEF, PCF or in a database dedicated to multicast/broadcast (this multicast/broadcast database can be used by multiple PLMNs shared). So that the general TMGI for a certain broadcast service identifier can be directly requested from the central database subsequently.
  • Step 801 AF sends a request message #1 (an example of a third message) to MB-SMF#b in PLMN#b, and the request message #1 carries the identifier of the broadcast service #4 (for example, the IP address of the broadcast service #4 broadcast address), the request message #1 is used to request the TMGI of the broadcast service #4.
  • MB-SMF#b receives the request message.
  • the request message #1 can be used to trigger the MB-SMF #b to send the TMGI of the broadcast service #4 to the AF.
  • AF sends a TMGI allocation request (TMGI allocation request) message to MB-SMF #b, requesting to broadcast TMGI of service #4.
  • TMGI allocation request TMGI allocation request
  • Step 802 MB-SMF#b sends a request message #2 (an example of the fifth message) to the central database, the request message #2 carries the identifier of the broadcast service #4, and acquires the TMGI of the broadcast service #4.
  • the request message #2 can be used to trigger the central database to send the TMGI of the broadcast service #4.
  • the request message #2 may be: a session create request (session create request) message, requesting to find the TMGI of the broadcast service #4.
  • the request message #2 may also be a TMGI allocation request (TMGI allocation request) message, or a TMGI search request (TMGI query request) message, which is not limited here.
  • MB-SMF#b when MB-SMF#b allocates TMGI, MB-SMF#b can search the central database for the TMGI of broadcast service #4, and obtain the general TMGI corresponding to broadcast service #4 as TMGI#q .
  • MB-SMF#b when MB-SMF#b allocates TMGI, MB-SMF#b can search the central database for the TMGI of broadcast service #4, if MB-SMF#b does not find the broadcast service# 4, MB-SMF #b allocates a TMGI for the broadcast service #4 (for example, the allocated TMGI is TMGI #q), and stores it in the central database.
  • Step 803 the central database sends a response message #2 of the request message #2 to MB-SMF #b, and the response message #2 carries the general TMGI and TMGI #q of the broadcast service #4.
  • Step 804 MB-SMF #b sends a response message #1 of the request message #1 to the AF, the response message #1 carries the general TMGI of the broadcast service #4, for example, TMGI #q.
  • the response message #1 is a TMGI allocation response (allocation request) message.
  • Step 805 AF sends a session create request (session create request) message to MB-SMF#b in PLMN#b.
  • MB-SMF#b in PLMN#b receives the broadcast session creation request.
  • the session creation request message carries the general TMGI corresponding to the broadcast service #4, for example, TMGI #q.
  • the session creation request message sent by the AF to MB-SMF#b may also carry one or more of the following information: for example, the requirement information of the broadcast service #4, and the broadcast area information.
  • the requirement information of the broadcast service #4 may include, for example, the delay requirement of the broadcast service #4, the priority requirement of the broadcast service #4, the bandwidth requirement of the broadcast service #4, and the like. Or, alternatively, it can also be broadcast policy information. For example: 5G service quality (quality of service, QoS) identifier (identifier) (ie, 5QI), allocation and preemption priority (allocation and retention priority, ARP) information etc.
  • 5G service quality quality of service, QoS
  • identifier ie, 5QI
  • allocation and preemption priority allocation and retention priority, ARP
  • the implementation manner for the AF to send the session creation request message to the MB-SMF#b in the PLMN#b may refer to step 503 in the method 500, and details are not repeated here.
  • Step 806, MB-SMF#b in PLMN#b obtains the QoS information of the session of broadcast service #4.
  • step 504 in method 500 For the manner in which MB-SMF#b in PLMN#b acquires the session QoS information of broadcast service #4, reference may be made to step 504 in method 500, which will not be repeated here.
  • Step 807 MB-SMB#b selects AMF#b, and sends a session start request (session start request) message to AMF#b.
  • AMF#b receives the session start request message.
  • step 505 in method 500 for the manner in which MB-SMF#b in PLMN#b selects an AMF, reference may be made to step 505 in method 500, which will not be repeated here.
  • the session start request message carries the general TMGI corresponding to the broadcast service #4, for example, TMGI #q.
  • the session start request message may also carry one or more of the following information: broadcast area information (for example, cell list (cell list) information, tracking area list ((tracking area, TA) list), broadcast session QoS information.
  • broadcast area information for example, cell list (cell list) information, tracking area list ((tracking area, TA) list
  • TA tracking area list
  • Step 808 AMF#b selects RAN#x (for example, a base station), and sends an N2 request (N2 request) message (an example of a second message) to RAN.
  • N2 request an example of a second message
  • RAN#x receives the N2 request message.
  • step 506 in method 500 for the manner in which AMF#b selects RAN#x, reference may be made to step 506 in method 500, which will not be repeated here.
  • the N2 request message carries the general TMGI corresponding to the broadcast service #4, for example, TMGI #q.
  • the N2 request message can also carry one or more of the following information: broadcast area information (for example, cell list (cell list) information, tracking area list (tracking area, TA) list), broadcast session QoS information.
  • broadcast area information for example, cell list (cell list) information, tracking area list (tracking area, TA) list
  • TA tracking area list
  • broadcast session QoS information for example, broadcast session QoS information.
  • the N2 request message is used to trigger RAN#x to allocate resources for broadcast service #4, in other words, the N2 request message is used to request RAN#x to allocate resources for broadcast service #4. It can also be understood that the N2 request message is used to request the RAN#x to establish a session context corresponding to the broadcast service #4.
  • Step 809 RAN#x allocates the first resource for the broadcast service #4 based on the N2 request message, and establishes a broadcast session context corresponding to the broadcast service #4.
  • the broadcast session context includes a general TMGI corresponding to the broadcast service #4, for example, TMGI#q.
  • the first resource can also be understood as being used to send the data of the broadcast service #4 to the UE in the PLMN #b.
  • RAN#x may allocate corresponding first resources according to the QoS information of the broadcast session. For example, resource reservation is performed for a guaranteed bit rate (guaranteed bit rate, GBR) QoS flow (flow), and the like.
  • the information of the first resource of the broadcast service #1 determined by the RAN#x may include: (1) Information of the group-radio network temporary identity (G-RNTI) received by the multicast. (2) Information about the bandwidth part (BWP) corresponding to the broadcast service #4.
  • G-RNTI group-radio network temporary identity
  • BWP bandwidth part
  • the service is received at the BWP, and the BWP corresponding to the sub-carrier space (sub-carrier space, SCS), frequency domain position and the length of the cyclic prefix (cyclic prefix, CP) are determined according to the BWP configuration.
  • the BWP configuration information also includes physical downlink control channel (physical downlink control channel, PDCCH) detection control resource set (control resource set, COREST) configuration information, the COREST configuration information indicates the time and frequency of the PDCCH for G-RNTI resource. (3) A scrambling sequence of a physical downlink data channel (physical downlink data channel, PDSCH) of the broadcast service #4.
  • the UE uses this sequence to descramble when decoding the PDSCH of the service;
  • the parameters of discontinuous reception (DRX) of G-RNTI can also be understood as that the UE uses the DRX parameters to perform G-RNTI detection.
  • the configuration of the demodulation reference signal can also be understood as that the UE uses the reference signal to demodulate the PDSCH scheduled by the G-RNTI.
  • Information of the rate matching reference signal is also be understood that the UE uses the reference signal to demodulate the PDSCH scheduled by the G-RNTI.
  • the broadcast session context corresponding to the broadcast service #4 established by RAN#x may also include: broadcast area information (for example, cell list (cell list) information, tracking area list ((tracking area, TA) list), broadcast session QoS context.
  • broadcast area information for example, cell list (cell list) information, tracking area list ((tracking area, TA) list), broadcast session QoS context.
  • Step 809 can also be understood as, RAN#x searches for the broadcast session context corresponding to the broadcast service #4 based on the N2 request message and the general TMGI: TMGI#q corresponding to the broadcast service #4. RAN#x does not find the context of the broadcast session including TMGI#q, then RAN#x determines that resources have not been allocated for broadcast service #4, and needs to allocate resources for broadcast service #4 in PLMN#b, and establish a broadcast service The broadcast session context corresponding to #1.
  • Step 810 RAN#x sends an N2 response message to AMF#b.
  • RAN#x sends an N2 response message to AMF#b to respond to the N2 request message sent by AMF#b.
  • Step 811 AMF#b sends a session start response message to MB-SMF#b.
  • AMF#b sends a session start response message to MB-SMF#b to respond to the session start request message sent by MB-SMF#b.
  • the above steps 801 to 811 are the process of establishing a broadcast session corresponding to the broadcast service #4 in PLMN#b and allocating the first resource for the data of the broadcast service #4.
  • the following steps 812-822 are to establish a broadcast session corresponding to broadcast service #4 in PLMN#a and use the first resource allocated for broadcast service #4 in PLMN#b to send broadcast service #4 to UE in PLMN#a data flow.
  • Step 812 AF sends a request message #3 (an example of a fifth message) to MB-SMF #a in PLMN #a, requesting to broadcast TMGI of service #4.
  • MB-SMF#a receives the request message.
  • the request message #3 can be used to trigger the MB-SMF #a to send the general TMGI corresponding to the broadcast service #4 to the AF.
  • AF sends a TMGI allocation request (TMGI allocation request) message to MB-SMF #a, requesting to broadcast TMGI of service #4.
  • TMGI allocation request TMGI allocation request
  • Step 813 MB-SMF#a sends a request message #4 (an example of the seventh message) to the central database to obtain the TMGI of the broadcast service #4.
  • step 802 For the manner in which MB-SMF#a obtains the TMGI of broadcast service #4, reference may be made to step 802, which will not be repeated here.
  • Step 814 the central database sends a response message #4 of the request message #4 to the MB-SMF #a, and the response message #4 carries the general TMGI and TMGI #q of the broadcast service #4.
  • Step 815 MB-SMF #a sends a response message #3 of the request message #3 to the AF, the response message #3 carries the general TMGI of the broadcast service #4, for example, TMGI #q.
  • the response message #1 is a TMGI allocation response (allocation request) message.
  • Step 816 AF sends a session create request (session create request) message to MB-SMF#a in PLMN#a.
  • MB-SMF#a in PLMN#a receives the broadcast session creation request.
  • the session creation request message carries the general TMGI corresponding to the broadcast service #4, for example, TMGI #q.
  • the session creation request message sent by AF to MB-SMF#a may also carry one or more of the following information: for example, demand information of broadcast service #4 and broadcast area information.
  • the requirement information of the broadcast service #4 may include, for example, the delay requirement of the broadcast service #4, the priority requirement of the broadcast service #4, the bandwidth requirement of the broadcast service #4, and the like. Or, alternatively, it can also be broadcast policy information. For example: 5G service quality (quality of service, QoS) identifier (identifier) (ie, 5QI), allocation and preemption priority (allocation and retention priority, ARP) information etc.
  • 5G service quality quality of service, QoS
  • identifier ie, 5QI
  • allocation and preemption priority allocation and retention priority, ARP
  • the implementation manner for the AF to send the session creation request message to the MB-SMF#a in the PLMN#a may refer to step 510 in the method 500, which will not be repeated here.
  • Step 817 MB-SMF#a in PLMN#a acquires the QoS information of the session of broadcast service #4.
  • step 511 in the method 500 for the manner in which MB-SMF#a acquires the session QoS information of the broadcast service #4, reference may be made to step 511 in the method 500, which will not be repeated here.
  • Step 818 MB-SMB#a selects AMF#a network element, and sends a session start request (session start request) message (an example of the third message) to AMF#a.
  • AMF#a receives the session start request message.
  • step 512 in method 500 For the manner in which MB-SMB#a selects AMF#a, reference may be made to step 512 in method 500 .
  • the session start request message carries the general TMGI of the broadcast service #4, for example, TMGI #q.
  • the session start request message may also carry one or more of the following information: broadcast area information (for example, cell list (cell list) information, tracking area list ((tracking area, TA) list), broadcast session QoS information.
  • broadcast area information for example, cell list (cell list) information, tracking area list ((tracking area, TA) list
  • TA tracking area list
  • Step 819 AMF#a selects RAN#x (for example, base station), and sends an N2 request (N2 request) message (an example of the first message) to RAN.
  • RAN#x for example, base station
  • N2 request an example of the first message
  • the RAN receives the N2 request message.
  • AMF#a may refer to step 513 in method 500 for selecting the RAN#x manner.
  • the session start request message carries the general TMGI of the broadcast service #4, for example, TMGI #q.
  • the session establishment request message sent by the AF to MB-SMF#a may also carry one or more of the following information: for example, the demand information of the broadcast service #4, and the broadcast area information.
  • the requirement information of the broadcast service #4 may include, for example, the delay requirement of the broadcast service #4, the priority requirement of the broadcast service #4, the bandwidth requirement of the broadcast service #4, and the like. Or, alternatively, it can also be broadcast policy information. For example: 5G service quality (quality of service, QoS) identifier (identifier) (ie, 5QI), allocation and preemption priority (allocation and retention priority, ARP) information etc.
  • 5G service quality quality of service, QoS
  • identifier ie, 5QI
  • allocation and preemption priority allocation and retention priority, ARP
  • Step 820 RAN#x determines whether resources have been allocated for broadcast service #4 based on the N2 request message and the general TMGI of broadcast service #4. If resources have been allocated for broadcast service #4, the data of broadcast service #4 in PLMN#a is sent through the resources; and/or, if RAN#x has not allocated resources for broadcast service #4, then RAN#x is Broadcast service #4 allocates resources.
  • the first resource has been allocated for the first broadcast service (that is, the broadcast service identified by TMGI #q) in PLMN#b
  • RAN#x based on the N2 request message and
  • the general TMGI of the broadcast service #4 for example, TMGI #q, determines that the data of the broadcast service #4 in the PLMN #a can be sent through the first resource in the PLMN #b.
  • RAN#x since RAN#x receives both TMGI#q in PLMN#b and PLMN#a, RAN#x does not need to search for the broadcast session context corresponding to the first broadcast service, and The data of broadcast service #4 in PLMN #a can be sent directly by using the first resource in PLMN #b.
  • Step 821 RAN#x sends an N2 response message to AMF#a.
  • RAN#x sends an N2 response message to AMF#a in response to the N2 request message sent by AMF#a.
  • Step 822 AMF#a sends a session start response message to MB-SMF#a.
  • AMF#a sends a session start response message to MB-SMF#a to respond to the session start request message sent by MB-SMF#a.
  • the RAN can identify the same broadcast service in the scenario where different operators share the base station, so that the RAN can identify the same broadcast service through the PLMN #b.
  • the resources allocated by the broadcast service are used to transmit the data of the broadcast service in PLMN#a.
  • the RAN can share air interface resources with users of different operators, which can save transmission resources of the RAN and avoid waste of air interface resources.
  • step 503 and step 510 can be performed at the same time, that is, the AF can simultaneously receive MB-SMF#b in PLMN#b and MB-SMF#a in PLMN#a to send broadcast service session creation requests.
  • the “broadcast service” and “broadcast session” in this application can also be understood as “multicast service” and “multicast session”. Not limited.
  • pre-definition in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, curing, or pre-firing.
  • each node such as a wireless access network device, a multicast/broadcast session management function network element, an application management function network element or a first network element, in order to realize the above functions, it includes hardware corresponding to each function structure and/or software modules.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiment of the present application can divide the functional modules of the wireless access network equipment and the involved core network elements according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more than two
  • the functions are integrated in one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.
  • Fig. 12 is a schematic block diagram of a communication device 100 provided by an embodiment of the present application.
  • the apparatus 100 may include: a transceiver unit 110 and a processing unit 120 .
  • the apparatus 100 may be the wireless access network device in the above method embodiment, or may be a chip for realizing the functions of the wireless access network device in the above method embodiment. It should be understood that the apparatus 100 may correspond to the radio access network device in the method 100, method 500, method 600, method 700, and method 800 according to the embodiment of the present application, and the apparatus 100 may execute the method 100, Steps corresponding to the wireless access network equipment in the method 500, the method 600, the method 700, and the method 800.
  • the transceiver unit 110 is configured to receive a first message from a network element with a first access and mobility management function, the first message carries an identifier of a first broadcast service, and the first message is used to trigger Allocating resources for the first broadcast service; the processing unit 120 is configured to obtain information about a first resource corresponding to the first broadcast service according to the identifier of the first broadcast service, and the first resource is used to provide information to the The terminal device in the second network sends the data of the first broadcast service; the transceiver unit 110 is further configured to send the data of the first broadcast service to the terminal device in the first network through the first resource.
  • the device is shared by at least two networks, the at least two networks include a first network and a second network, and the first access and mobility management function network element is located in the first network.
  • the identifier of the first broadcast service includes a first identifier and/or a second identifier, where the first identifier includes at least one of the following: a globally unique identifier of the first broadcast service; An identifier of a broadcast service in each of the at least two networks, or; a temporary mobile group identifier of the first broadcast service, where the temporary mobile group identifier is shared by the at least two networks; the The second identifier includes: an identifier of the first broadcast service in the first network.
  • the globally unique identifier of the first broadcast service includes an Internet Protocol IP multicast address of the first broadcast service.
  • the processing unit 120 is configured to obtain the first broadcast service identifier according to the identifier of the first broadcast service.
  • the information of the first resource corresponding to the broadcast service includes: the processing unit 120 is configured to search for the broadcast session context corresponding to the first broadcast service according to the globally unique identifier of the first broadcast service; the processing unit 120 uses Obtaining the information of the first resource according to the broadcast session context; wherein the broadcast session context includes the globally unique identifier of the first broadcast service and the information of the first resource.
  • the processing unit 120 is configured to An identification of a broadcast service, obtaining information about a first resource corresponding to the first broadcast service, including: the processing unit 120 is configured to perform an operation in each of the at least two networks according to the first broadcast service ID of the broadcast session context corresponding to the first broadcast service; the processing unit 120 is configured to obtain information about the first resource according to the broadcast session context; wherein the broadcast session context includes the first broadcast session context An identifier of a broadcast service in each of the at least two networks and information about the first resource.
  • the processing unit 110 is configured to obtain the first broadcast service corresponding to the first broadcast service according to the identifier of the first broadcast service.
  • Resource information including: the processing unit 120 uses the pre-configured correspondence between the identifier of the first broadcast service in the first network and the identifier of the first broadcast service in the second network relationship, and the second identifier, obtaining the identifier of the first broadcast service in the second network; the processing unit 120 is configured to, according to the identifier of the first broadcast service in the second network, Searching for a broadcast session context corresponding to the first broadcast service; the processing unit 120 is configured to obtain information about the first resource according to the broadcast session context;
  • the transceiver unit 110 is further configured to receive a second message from a network element with a second access and mobility management function, the The second message carries the first identifier, the second message is used to trigger allocation of resources for the first broadcast service, and the second access and mobility management function network element is located at the first of the at least two networks Two networks; the processing unit 120 is configured to allocate the first resource for the first broadcast service according to the second message; the processing unit 120 is configured to establish a broadcast session context corresponding to the first broadcast service ; Wherein, the broadcast session context includes the first identifier and information of the first resource.
  • the device 100 may be the multicast/broadcast session management function network element in the above method embodiment, or may be a network element for implementing the multicast/broadcast session management function in the above method embodiment meta-function chip. It should be understood that the device 100 may correspond to the multicast/broadcast session management function network element in the method 200, method 500, method 600, method 700, and method 800 according to the embodiment of the present application, and the device 100 may execute the embodiment of the present application Steps corresponding to the multicast/broadcast session management function network element in method 200, method 500, method 600, method 700, method 800.
  • the transceiver unit 110 is configured to receive the identifier of the first broadcast service; the transceiver unit 110 is also configured to send the identifier of the first broadcast service.
  • the identifier of the first broadcast service includes a first identifier
  • the first identifier includes at least one of the following: a globally unique identifier of the first broadcast service; An identifier in each of the networks, or; a temporary mobile group identifier of the first broadcast service, where the temporary mobile group identifier is shared by at least two networks.
  • the globally unique identifier of the first broadcast service includes an Internet Protocol IP multicast address of the first broadcast service.
  • the transceiving unit 110 is configured to receive the identifier of the first broadcast service, including: the transceiving unit 110 is configured to receive the identifier of the first broadcast service from an application function network element.
  • the transceiver unit 110 before the transceiver unit 110 receives the identifier of the first broadcast service from the application function network element, the transceiver unit 110 is further configured to receive a third message, the third message carrying the first broadcast service The third message is used to trigger the device to send the temporary mobile group identifier of the first broadcast service; the processing unit 120 is configured to obtain the temporary mobile group identifier from the first network element according to the third message A mobile group identifier, or; the processing unit 120 is configured to allocate the temporary mobile group identifier for the first broadcast service according to the third message; the transceiving unit 110 is configured to send the temporary mobile group identifier.
  • the first network element is: a unified data management network element, a unified data storage network element, a network storage function network element, a network discovery function network element, a policy control function network element, or a multicast/broadcast database , wherein the multicast/broadcast database is shared by at least two networks.
  • the transceiver unit 110 is configured to receive the identifier of the first broadcast service, including: the transceiver unit 110 is configured to receive the identifier of the first broadcast service, where the identifier of the first broadcast service is the first A globally unique identifier for a broadcasting service.
  • the transceiver unit 110 before the transceiver unit 110 receives the identifier of the first broadcast service, the transceiver unit 110 is further configured to send a fourth message, where the fourth message is used to request session establishment of the first broadcast service or Modification, the fourth message carries first indication information, and the first indication information is used to trigger the processing unit 120 to detect the identifier of the first broadcast service.
  • the apparatus 100 may be the application function network element in the above method embodiment, or may be a chip for realizing the function of the application function network element in the above method embodiment. It should be understood that the device 100 may correspond to the application function network element in the method 300, the method 500, the method 600, the method 700, and the method 800 according to the embodiment of the present application, and the device 100 may execute the method 300 and the method 800 of the embodiment of the present application. Steps corresponding to the application function network element in 500, method 600, method 700, and method 800.
  • the processing unit 120 is configured to obtain the identifier of the first broadcast service; the transceiver unit 110 is configured to send the identifier of the first broadcast service.
  • the identifier of the first broadcast service includes a first identifier
  • the first identifier includes at least one of the following: a globally unique identifier of the first broadcast service; An identifier in each of the networks, or; a temporary mobile group identifier of the first broadcast service, where the temporary mobile group identifier is shared by at least two networks.
  • the globally unique identifier of the first broadcast service includes an Internet Protocol IP multicast address of the first broadcast service.
  • the processing unit 120 is configured to obtain the identifier of the first broadcast service, including: the processing unit 120 is configured to generate a globally unique identifier of the first broadcast service.
  • the at least two networks include a first network and a second network
  • the processing unit 120 is configured to obtain an identifier of the first broadcast service, including: the processing unit 120 is configured to instruct the transceiver unit 110 to obtain the identifier of the first broadcast service
  • the first multicast/broadcast session management function network element in the first network receives the identifier of the first broadcast service in the first network; the processing unit 120 is configured to instruct the transceiver unit 110
  • the second multicast/broadcast session management functional network element in the second network receives the identifier of the first broadcast service in the second network.
  • the processing unit 120 is configured to obtain the identifier of the first broadcast service, including: the processing unit 120 is configured to obtain the temporary mobile group identifier from the multicast/broadcast session management function network element.
  • the apparatus 100 may be the first network element in the above method embodiment, or may be a chip configured to realize the function of the first network element in the above method embodiment.
  • the device 100 may correspond to the first network element (for example, a central database) in the method 400 according to the embodiment of the present application, and the central database in the method 800, and the device 100 may execute the method 400 in the embodiment of the present application
  • the steps corresponding to the functional network element of the first network element may also execute the steps corresponding to the central database in method 800.
  • the transceiver unit 110 is configured to receive a fifth message, the fifth message carries the identifier of the first broadcast service, and the fifth message is used to trigger the device to send a temporary message of the first broadcast service.
  • a mobile group identifier the processing unit 120 is configured to instruct the transceiving unit 110 to send the temporary mobile group identifier of the first broadcast service according to the fifth message.
  • the transceiving unit 110 is further configured to receive the correspondence between the identifier of the first broadcast service and the identifier of the temporary mobile group from a network element with a multicast/broadcast session management function.
  • the temporary mobility group identifier is shared by at least two networks.
  • the first network element is: a unified data management network element, a unified data storage network element, a network storage function network element, a network discovery function network element, a policy control function network element, or a multicast/broadcast database , wherein the multicast/broadcast database is shared by at least two networks.
  • unit here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • the apparatus 100 may specifically be the first terminal device in the above-mentioned embodiments, and may be used to execute various procedures corresponding to the first terminal device in the above-mentioned method embodiments and/or or steps, or, the apparatus 100 may specifically be the second terminal device in the above-mentioned embodiments, and may be used to execute various processes and/or steps corresponding to the second terminal device in the above-mentioned method embodiments. To avoid repetition, here No longer.
  • the apparatus 100 in each of the above solutions has the function of implementing the corresponding steps performed by the radio access network equipment in the above method, or, the apparatus 100 in the above various solutions has a network element or application function that implements the multicast/broadcast session management function in the above method
  • the network element, or the function of the corresponding steps performed by the first network element may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver computer), and other units, such as a processing unit, may be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • a transceiver for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver computer
  • other units such as a processing unit, may be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • transceiver unit 110 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.
  • the apparatus in FIG. 12 may be the network element or device in the foregoing embodiments, or may be a chip or a chip system, for example, a system on chip (system on chip, SoC).
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. It is not limited here.
  • Fig. 13 is a schematic block diagram of a communication device 200 provided by an embodiment of the present application.
  • the apparatus 200 includes: at least one processor 220 .
  • the processor 220 is coupled with the memory for executing instructions stored in the memory to send signals and/or receive signals.
  • the device 200 further includes a memory 230 for storing instructions.
  • the device 200 further includes a transceiver 210, and the processor 220 controls the transceiver 210 to send signals and/or receive signals.
  • processor 220 and the memory 230 may be combined into one processing device, and the processor 220 is configured to execute the program codes stored in the memory 230 to implement the above functions.
  • the memory 230 may also be integrated in the processor 220 , or be independent of the processor 220 .
  • the transceiver 210 may include a transceiver (or a receiver) and a transmitter (or a transmitter).
  • the transceiver may further include antennas, and the number of antennas may be one or more.
  • the transceiver 210 may be a communication interface or an interface circuit.
  • the transceiver 210 in the device 200 may correspond to the transceiver unit 110 in the device 100
  • the processor 220 in the device 200 may correspond to the processing unit 120 in the device 200 .
  • the apparatus 200 is configured to implement the operations performed by the radio access network device in each method embodiment above.
  • the processor 220 is configured to execute the computer programs or instructions stored in the memory 230, so as to implement related operations of the radio access network device in the various method embodiments above.
  • the method 100 executed by the radio access network device in the embodiment shown in FIG. 4 or the method executed by the radio access network device in any one of the embodiments shown in FIG. 8 to FIG. 11 .
  • the apparatus 200 is used to implement the operations performed by each network element of the core network in each method embodiment above.
  • the processor 220 is configured to execute computer programs or instructions stored in the memory 230 to implement related operations of the multicast/broadcast session management function network element, the application function network element, and the first network element in each method embodiment above. For example, the method performed by the multicast/broadcast session management function network element, the application function network element, and the first network element in any one of the embodiments shown in FIG. 5 to FIG. 11 .
  • each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, no detailed description is given here.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field-programmable gate array (field-programmable gate array, FPGA) or Other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • Other programmable logic devices discrete gate or transistor logic devices, discrete hardware components.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which acts as external cache memory.
  • RAM random access memory
  • static RAM static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory direct ram-bus RAM, DR RAM
  • direct ram-bus RAM direct ram-bus RAM
  • the present application also provides a computer program product, on which computer program code is stored, and when the computer program code is run on the computer, the computer is made to execute method 100 and method 500 ⁇ The method performed by the radio access network device or the RAN in any one of the embodiments of the method 800.
  • the computer when the computer program code is executed by a computer, the computer can implement the methods performed by the multicast/broadcast session management function network element in the foregoing method 200, method 500-method 800 embodiments.
  • the computer when the computer program code is executed by a computer, the computer can implement the methods executed by the application function network element in the foregoing method 300, method 500-method 800 embodiments.
  • the computer when the computer program code is executed by a computer, the computer can implement the methods performed by the first network element in the foregoing method 400, method 500-method 800 embodiments.
  • the present application also provides a computer-readable medium, the computer-readable medium stores program codes, and when the program codes run on the computer, the computer executes the above-mentioned embodiment by wireless A method performed by an access network device, a multicast/broadcast session management function network element, an application function network element or a first network element.
  • the present application also provides a communication system, which includes a radio access network device and a first access and mobility management function network element, and the radio access network device is configured to execute the method 100 .
  • the method performed by the wireless access network device or the RAN in any one of the embodiments in the method 500 to the method 800; the first access and mobility management function network element is used to send the wireless access network
  • the device sends a first message, where the first message carries an identifier of a first broadcast service, and the first message is used to trigger allocation of resources for the first broadcast service; wherein, the wireless access network device consists of at least two Network sharing, the at least two networks include a first network and a second network, and the network element with the first access and mobility management function is located in the first network.
  • system further includes: a network element with a multicast/broadcast session management function, and the network element with a multicast/broadcast session management function is used to execute method 200, method 500-method 800 The method performed by the multicast/broadcast session management functional network element in any one of the embodiments.
  • system further includes: an application function network element; the application function network element is used to execute the application function in any one of the embodiments in the method 300, method 500-method 800 The method performed by the network element.
  • the system further includes a first network element (for example, a central database), and the first network element is used for the first network element in any one of the method 400 and execution method 800 embodiments.
  • a network element eg, a central database
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disc, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disk (solid state disc, SSD)
  • the corresponding steps are executed by corresponding modules or units, for example, the transceiver unit (transceiver) executes the steps of receiving or sending in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processing unit) device) executes.
  • the processing unit processing unit
  • the functions of the specific units reference may be made to the corresponding method embodiments.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device can be components.
  • One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more packets of data (e.g., data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet via a signal interacting with other systems). Communicate through local and/or remote processes.
  • packets of data e.g., data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet via a signal interacting with other systems.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Landscapes

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

Abstract

本申请实施例提供一种广播通信方法和装置，通过给无线接入网设备发送第一广播业务的标识，使得无线接入网设备可以识别出在不同网络中的相同的第一广播业务。无线接入网设备可以通过已经在第二网络中为该第一广播业务分配的资源，发送第一网络中的该广播业务的数据。换句话说，本申请中，无线接入网设备可以对在不同网络的相同的广播业务共享空口资源，从而，节约无线接入网设备的传输资源，避免空口资源浪费。

Description

一种广播通信方法和装置
本申请要求于2022年1月12日提交中国专利局、申请号为202210030311.7、申请名称为“一种广播通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种广播通信方法和装置。
背景技术
目前，运营商在部署网络时，为了降低成本，不同运营商之间共享基站，但会保留各自的核心网，例如，多运营商核心网(multi-operator core network，MOCN)场景。在MOCN场景中，广播消息包含公共陆地移动网络(public land mobile network，PLMN)的信息，例如，基站广播某个小区的信息，该信息包括该小区所属PLMN的信息。
然而，在上述不同运营商之间共享基站的场景中，存在不同运营商的核心网及其所共享的基站重复传输某些广播业务(例如，天气预报、高精地图更新)的情况，造成了传输资源的浪费。如何减少这种传输资源的浪费，成为亟待解决的问题。
发明内容
本申请提供了一种广播通信方法，可以减少传输资源的浪费。
第一方面，提供了一种广播通信方法，该方法可以由无线接入网设备(例如，基站)执行，或者，也可以由无线接入网设备的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：无线接入网设备接收来自第一接入和移动管理功能网元的第一消息，所述第一消息携带第一广播业务的标识，所述第一消息用于触发为所述第一广播业务分配资源，其中，所述无线接入网设备由至少两个网络共享，所述至少两个网络包括第一网络和第二网络，所述第一接入和移动管理功能网元位于所述第一网络中；所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，所述第一资源用于向所述第二网络中的终端设备发送所述第一广播业务的数据；所述无线接入网设备通过所述第一资源，向所述第一网络中的终端设备发送所述第一广播业务的数据。
基于上述技术方案，针对无线接入网设备已经在第二网络中为第一广播业务分配过资源且建立过第一广播业务的对应的广播会话上下文的场景，本申请中，通过给无线接入网设备发送第一广播业务的标识，使得无线接入网设备可以识别出不同网络中相同的广播业务。无线接入网设备可以通过已经在第二网络中为该广播业务分配的资源，发送第一网络中的该广播业务的数据。换句话说，本申请中，无线接入网设备可以对在不同网络中相同 的广播业务共享空口资源，节约无线接入网设备的传输资源，避免空口资源浪费。
本申请中，第一资源可以用于向第二网络中的终端设备发送第一广播业务的数据。例如，第一资源可以是：空口资源，例如，调度时间资源、频率资源、调度优先级、缓存资源、数据无线承载(data radio bearer，DRB)、存储的上下文信息(例如，服务质量(quality of service，QoS)描述信息、QoS流(flow)的标识信息)等上述的一个或多个，不予限定。
本申请中，第一资源的信息例如可以是，第一资源的标识信息(例如，上下文标识(context ID)，或者第一资源的时域频域位置等信息，不做限定。
在一种实现方式中，所述第一广播业务的标识包括第一标识和/或第二标识，其中，所述第一标识包括以下至少一项：所述第一广播业务的全球唯一标识；所述第一广播业务在所述至少两个网络中的每个网络中的标识，或者；所述第一广播业务的临时移动组标识，所述临时移动组标识由所述至少两个网络共享；所述第二标识包括：所述第一广播业务在所述第一网络中的标识。
例如，第一广播业务的标识可以包括所述第一广播业务的全球唯一标识和所述第一广播业务在所述第一网络中的标识；又例如，第一广播业务的标识可以包括所述第一广播业务在所述至少两个网络中的每个网络中的标识和所述第一广播业务的临时移动组标识；再例如，第一广播业务的标识可以包括所述第一广播业务的全球唯一标识、所述第一广播业务的临时移动组标识以及所述第一广播业务在所述第一网络中的标识，等等。
在一种实现方式中，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。需要说明的是，所述第一广播业务的全球唯一标识可以是所述第一广播业务的互联网协议IP多播地址，也可以包括其他内容，例如多播/广播数据的源地址(source address)，本申请不予限定。
其中，所述IP多播地址，例如，对于互联网通信协议第四版(internet protocal version 4，IPv4)可以224.3.0.0到224.4.255.255，或者225.0.0.0到231.255.255.255，或者232.0.0.0到232.255.255.255，或者233.0.0.0到233.251.255.255这些地址段中的一个或多个IP地址；对于互联网通信协议第六版(internet protocal version 6，IPv6)也可以是前缀为ff02或者ff05或者ff0x的一个或多个IP地址，本申请不予限定。
需要指出的是，在本申请中，在第一广播业务的标识是第一广播业务的全球唯一标识的情况下，例如，可以通过在应用功能网元向PLMN网络发送的请求消息中，增加一个新信元。即，应用功能网元向PLMN网络发送的请求消息中增加第一广播业务的全球唯一标识来实现，该方式对应用服务器改动较小，易于应用服务器实现，便于推广；在第一广播业务的标识是第一广播业务在至少两个网络中的每个网络中的标识的情况下，可以通过扩展现有接入和移动性管理网元向接入网设备发送的消息中的信元。即，通过将原来第一广播业务在网络中的标识，扩展成为第一广播业务在至少两个网络中每个网络中的标识，实现新的功能，对网络改动较小，易于升级。
在一种实现方式中，在所述第一广播业务的标识为所述第一广播业务的全球唯一标识的情况下，所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对 应的第一资源的信息，包括：所述无线接入网设备根据所述第一广播业务的全球唯一标识，查找所述第一广播业务对应的广播会话上下文；所述无线接入网设备根据所述广播会话上下文，获得所述第一资源的信息；其中，所述广播会话上下文包括所述第一广播业务的全球唯一标识以及所述第一资源的信息。
在一种实现方式中，在所述第一广播业务的标识为所述第一广播业务在所述至少两个网络中的每个网络中的标识的情况下，所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：所述无线接入网设备根据所述第一广播业务在所述至少两个网络中的每个网络中的标识，查找所述第一广播业务对应的广播会话上下文；所述无线接入网设备根据所述广播会话上下文，获得所述第一资源的信息；其中，所述广播会话上下文包括所述第一广播业务在所述至少两个网络中的每个网络中的标识以及所述第一资源的信息。
在一种实现方式中，在所述第一广播业务的标识包括所述第二标识情况下，所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：所述无线接入网设备根据预配置的所述第一广播业务在所述第一网络中的标识与所述第一广播业务在所述第二网络中的标识的对应关系，以及所述第二标识，获得所述第一广播业务在所述第二网络中的标识；所述无线接入网设备根据所述第一广播业务在所述第二网络中的标识，查找所述第一广播业务对应的广播会话上下文；所述无线接入网设备根据所述广播会话上下文，获得所述第一资源的信息；其中，所述广播会话上下文包括所述第二标识以及所述第一资源的信息。
在一种实现方式中，在所述第一广播业务的标识为所述第一广播业务的临时移动组标识的情况下，由于无线接入网设备在第二网络中接收的第一广播业务的临时移动组标识与在第一网络中接收的第一广播业务的临时移动组标识是共享的(例如，该临时移动组标识时相同的)，无线接入网设备可以利用第二网络中的第一资源发送第一网络中的第一广播业务的数据。换句话说，此时，无线接入网设备无须查找第一广播业务对应的上下文，查找第一资源的信息，便可以使用第一资源向第一网络中的终端设备发送第一广播业务的数据。
基于上述技术方案，本申请中，由于在第二网络中已经建立过第一广播业务对应的广播会话上下文，且该广播会话上下文中包括第一广播业务的标识和第一资源的信息。因此，无线接入网设备可以根据第一广播业务的标识，获取在第二网络中已经为第一广播业务分配的第一资源的信息。无线接入网设备后续可以通过第一资源为第一网络中的终端设备发送第一广播业务的数据。
针对无线接入网设备还未在某个网络中建立第一广播业务对应的广播会话上下文的场景，该方法还包括：在所述第一广播业务的标识包括所述第一标识的情况下，所述方法还包括：所述无线接入网设备接收来自第二接入和移动管理功能网元的第二消息，所述第二消息携带所述第一标识，所述第二消息用于触发为所述第一广播业务分配资源，所述第二接入和移动管理功能网元位于所述至少两个网络中的第二网络；所述无线接入网设备根据所述第二消息，为所述第一广播业务分配所述第一资源；所述无线接入网设备建立所述 第一广播业务对应的广播会话上下文；其中，所述广播会话上下文包括所述第一标识以及所述第一资源的信息。
基于上述技术方案，本申请中，如果还未在某个网络中为第一广播业务分配资源以及建立第一广播业务对应的广播会话，则无线接入网设备可以在第二网络为第一广播业务分配资源并且建立第一广播业务的会话上下文。后续无线接入网设备可以不区分网络，而是根据本地是否已经为该广播业务分配过资源，从而灵活使用(也可以理解为“共享”)该资源。
第二方面，提供了一种广播通信方法，该方法可以由多播/广播会话管理功能网元执行，或者，也可以由多播/广播会话管理功能网元的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：多播/广播会话管理功能网元接收第一广播业务的标识；所述多播/广播会话管理功能网元向接入和移动管理功能网元发送所述第一广播业务的标识。
基于上述技术方案，本申请中，多播/广播会话管理功能网元可以接收第一广播业务的标识，并发送给接入和移动管理功能网元，从而使得无线接入网设备可以获得第一广播业务的标识，在不同网络中识别相同的广播数据。
在一种实现方式中，所述第一广播业务的标识包括第一标识，所述第一标识包括以下至少一项：所述第一广播业务的全球唯一标识；所述第一广播业务在至少两个网络中的每个网络中的标识，或者；所述第一广播业务的临时移动组标识，所述临时移动组标识由至少两个网络共享。
在一种实现方式中，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。需要说明的是，所述第一广播业务的全球唯一标识可以是所述第一广播业务的互联网协议IP多播地址，也可以包括其他内容，例如多播/广播数据的源地址(source address)，本申请不予限定。
其中，所述IP多播地址，例如，对于互联网通信协议第四版(internet protocal version 4，IPv4)可以是224.3.0.0到224.4.255.255，或者225.0.0.0到231.255.255.255，或者232.0.0.0到232.255.255.255，或者233.0.0.0到233.251.255.255这些地址段中的一个或多个IP地址；对于互联网通信协议第六版(internet protocal version 6，IPv6)也可以是前缀为ff02或者ff05或者ff0x的一个或多个IP地址，本申请不予限定。
需要指出的是，在本申请中，在第一广播业务的标识是第一广播业务的全球唯一标识的情况下，例如，可以通过在应用功能网元向PLMN网络发送的请求消息中，增加一个新信元。即，应用功能网元向PLMN网络发送的请求消息中增加第一广播业务的全球唯一标识来实现，该方式对应用服务器改动较小，易于应用服务器实现，便于推广；在第一广播业务的标识是第一广播业务在至少两个网络中的每个网络中的标识的情况下，可以通过扩展现有接入和移动性管理网元向接入网设备发送的消息中的信元。即，通过将原来第一广播业务在网络中的标识，扩展成为第一广播业务在至少两个网络中每个网络中的标识，实现新的功能，对网络改动较小，易于升级。
另外，本申请中，针对第一广播业务的标识的不同表现形式，无线接入网设备均可以 灵活识别出其为相同的广播业务。
在一种实现方式中，所述多播/广播会话管理功能网元接收第一广播业务的标识，包括：所述多播/广播会话管理功能网元接收来自应用功能网元的第一广播业务的标识。
在一种实现方式中，所述多播/广播会话管理功能网元接收第一广播业务的标识，包括：所述多播/广播会话管理功能网元接收来自多播/广播用户面功能网元的第一广播业务的标识，其中，所述第一广播业务的标识为所述第一广播业务的全球唯一标识。
基于上述技术方案，本申请中，多播/广播会话管理功能网元可以从应用功能网元接收第一广播业务的标识，也可以从多播/广播用户面功能网元接收第一广播业务的标识。即，可以灵活的从各个核心网网元接收第一广播业务的标识。从而，使得后续无线接入网设备可以基于从不同核心网网元接收的广播业务的标识，在不同的网络中识别出相同的广播业务。
在一种实现方式中，在所述多播/广播会话管理功能网元接收来自应用功能网元的第一广播业务的标识之前，所述方法还包括：所述多播/广播会话管理功能网元接收来自所述应用功能网元的第三消息，所述第三消息携带所述第一广播业务的标识，所述第三消息用于触发所述多播/广播会话管理功能网元向所述应用功能网元发送所述第一广播业务的临时移动组标识；所述多播/广播会话管理功能网元根据所述第三消息，从第一网元获取所述临时移动组标识，或者；所述多播/广播会话管理功能网元根据所述第三消息，为所述第一广播业务分配所述临时移动组标识；所述多播/广播会话管理功能网元向所述应用功能网元发送所述临时移动组标识。
基于上述技术方案，本申请中，如果第一广播业务的标识为临时移动组标识时，多播/广播会话管理功能网元可以从第一网元获取该临时移动组标识或者自主为第一广播业务分配临时移动组标识，从而，可以保障针对同一广播业务使用相同的临时移动组标识。
在一种实现方式中，所述第一网元为：统一数据管理网元、统一数据存储网元、网络存储功能网元、网络发现功能网元、策略控制功能网元、或者，多播/广播的数据库，其中，所述多播/广播的数据库由至少两个网络共享。
本申请中的第一网元可以是现有的5G核心网架构中的网元，也可以是未来定义的新的网元。即，对第一网元的具体名称不做限定。只要可以从该网元中获取第一广播业务的临时移动组标识，且该临时移动组标识可以由至少两个网络共享，均落入本申请的保护范围。
在一种实现方式中，在所述多播/广播会话管理功能网元接收来自多播/广播用户面功能网元的第一广播业务的标识之前，所述方法还包括：所述多播/广播会话管理功能网元向所述多播/广播用户面功能网元发送第四消息，所述第四消息用于请求所述第一广播业务的会话建立或者修改，所述第四消息携带第一指示信息，所述第一指示信息用于触发所述多播/广播用户面功能网元检测所述第一广播业务的标识。
基于上述技术方案，可以通过指示多播/广播用户面功能网元检测第一广播业务的标识的方法获取第一广播业务的标识，可以提高获取第一广播业务的标识的灵活性。并且，该技术方案可以不依赖应用功能网元便可以获得第一广播业务的标识，也可以理解为，该 技术方案在应用功能网元的功能未增强的情况下也可以实现。
第三方面，提供了一种广播通信方法，该方法可以由应用功能网元执行，或者，也可以由应用功能网元的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：应用功能网元获得第一广播业务的标识；所述应用功能网元向多播/广播会话管理功能网元发送所述第一广播业务的标识。
在一种实现方式中，所述第一广播业务的标识包括第一标识，所述第一标识包括以下至少一项：所述第一广播业务的全球唯一标识；所述第一广播业务在至少两个网络中的每个网络中的标识，或者；所述第一广播业务的临时移动组标识，所述临时移动组标识由至少两个网络共享。
在一种实现方式中，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。需要说明的是，所述第一广播业务的全球唯一标识可以是所述第一广播业务的互联网协议IP多播地址，也可以包括其他内容，例如多播/广播数据的源地址(source address)，本申请不予限定。
其中，所述IP多播地址，例如，对于互联网通信协议第四版(internet protocal version 4，IPv4)可以是224.3.0.0到224.4.255.255，或者225.0.0.0到231.255.255.255，或者232.0.0.0到232.255.255.255，或者233.0.0.0到233.251.255.255这些地址段中的一个或多个IP地址；对于互联网通信协议第六版(internet protocal version 6，IPv6)也可以是前缀为ff02或者ff05或者ff0x的一个或多个IP地址，本申请不予限定。
需要指出的是，在本申请中，在第一广播业务的标识是第一广播业务的全球唯一标识的情况下，例如，可以通过在应用功能网元向PLMN网络发送的请求消息中，增加一个新信元。即，应用功能网元向PLMN网络发送的请求消息中增加第一广播业务的全球唯一标识来实现，该方式对应用服务器改动较小，易于应用服务器实现，便于推广；在第一广播业务的标识是第一广播业务在至少两个网络中的每个网络中的标识的情况下，可以通过扩展现有接入和移动性管理网元向接入网设备发送的消息中的信元。即，通过将原来第一广播业务在网络中的标识，扩展成为第一广播业务在至少两个网络中每个网络中的标识，实现新的功能，对网络改动较小，易于升级。
另外，本申请中，针对第一广播业务的标识的不同表现形式，无线接入网设备均可以灵活识别出其为相同的广播业务。
在一种实现方式中，所述应用功能网元获得第一广播业务的标识，包括：所述应用功能网元生成所述第一广播业务的全球唯一标识。
在一种实现方式中，所述至少两个网络包括第一网络和第二网络，所述应用功能网元获得第一广播业务的标识，包括：所述应用功能网元从所述第一网络中的第一多播/广播会话管理功能网元接收所述第一广播业务在所述第一网络中的标识；所述应用功能网元从所述第二网络中的第二多播/广播会话管理功能网元接收所述第一广播业务在所述第二网络中的标识。
在一种实现方式中，所述应用功能网元获得第一广播业务的标识，包括：所述应用功能网元从所述多播/广播会话管理功能网元获得所述临时移动组标识。
基于上述技术方案，本申请中，在第一广播业务的标识为不同的表现形式时，应用功能网元可以采用不同的方法获取该第一广播业务的标识。
第四方面，本申请提供了一种广播通信方法，该方法可以由第一网元执行，或者，也可以由第一网元的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：第一网元从多播/广播会话管理功能网元接收第五消息，所述第五消息携带第一广播业务的标识，所述第五消息用于触发所述第一网元发送所述第一广播业务的临时移动组标识；所述第一网元根据所述第五消息，向所述多播/广播会话管理功能网元发送所述第一广播业务的临时移动组标识。
在一种实现方式中，所述临时移动组标识由至少两个网络共享。
基于上述技术方案，本申请中，在第一广播业务的标识为临时移动组标识的情况下，可以从第一网元获取该临时移动组标识。
在一种实现方式中，所述第一网元为：统一数据管理网元、统一数据存储网元、网络存储功能网元、网络发现功能网元、策略控制功能网元、或者，多播/广播的数据库，其中，所述多播/广播的数据库由至少两个网络共享。
本申请中的第一网元可以是现有的5G核心网架构中的网元，也可以是未来定义的新的网元。即，对第一网元的具体名称不做限定。只要可以从该网元中获取第一广播业务的临时移动组标识，且该临时移动组标识可以由至少两个网络共享，均落入本申请的保护范围。
在一种实现方式中，所述方法还包括：所述第一网元从所述多播/广播会话管理功能网元接收所述第一广播业务的标识与所述临时移动组标识之间的对应关系。
基于上述技术方案，本申请中，针对在某些网络中的第一广播业务，第一网元上还没有为其分配临时移动组标识的情况，此时，可以由多播/广播会话管理功能网元为该网络中的第一广播业务分配临时移动组标识，并存储在第一网元上。
第五方面，提供了一种广播通信装置，该装置用于执行上述第一方面至第四方面任一种可能实现方式中的方法。具体地，该装置可以包括用于执行第一方面至第四方面任一种可能实现方式中的方法的单元和/或模块，如收发单元和/或处理单元。
在一种实现方式中，该装置为通信设备(例如：无线接入网设备、多播/广播会话管理功能网元、应用功能网元或者第一网元)。当该装置为通信设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于通信设备(例如：无线接入网设备、多播/广播会话管理功能网元、应用功能网元或者第一网元)的芯片、芯片系统或电路。当该装置为用于通信设备的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第六方面，提供了一种广播通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面中任一种可能实现方式中的方法。可选 地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为无线接入网设备。
在另一种实现方式中，该装置为用于无线接入网设备的芯片、芯片系统或电路。
第七方面，提供了一种广播通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第二方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为多播/广播会话管理功能网元。
在另一种实现方式中，该装置为用于多播/广播会话管理功能网元的芯片、芯片系统或电路。
第八方面，提供了一种广播通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第三方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为应用功能网元。
在另一种实现方式中，该装置为用于应用功能网元的芯片、芯片系统或电路。
第九方面，提供了一种广播通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第四方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为第一网元。
在另一种实现方式中，该装置为用于第一网元的芯片、芯片系统或电路。
第十方面，本申请提供一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第四方面中任一方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于收发器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第十一方面，提供了一种处理设备，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过收发器接收信号，通过发射器发射信号，以执行第一方面至第四 方面中任一方面中任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自收发器。其中，发射器和收发器可以统称为收发器。
上述第十一方面中的处理设备可以是一个或多个芯片。该处理设备中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十二方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第四方面任一种可能实现方式中的方法。
第十三方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第四方面任一种可能实现方式中的方法。
第十四方面，提供一种芯片系统，包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片系统的设备执行上述第一方面至第四方面中任一方面中各实现方式中的方法。
第十五方面，提供了一种广播通信系统，所述通信系统包括无线接入网设备和第一接入和移动管理功能网元；所述无线接入网设备，用于执行上述第一方面中的任一种实现方式的方法；所述第一接入和移动管理功能网元，用于向所述无线接入网设备发送第一消息，所述第一消息携带第一广播业务的标识，所述第一消息用于触发为所述第一广播业务分配资源；其中，所述无线接入网设备由至少两个网络共享，所述至少两个网络包括第一网络和第二网络，所述第一接入和移动管理功能网元位于所述第一网络中。
在一种实现方式中，所述通信系统还包括：多播/广播会话管理功能网元，所述多播/广播会话管理功能网元，用于执行上述第二方面中任一种实现方式的方法。
在一种实现方式中，所述通信系统还包括：应用功能网元，所述应用功能网元，用于执行上述第三方面中任一种实现方式的方法。
在一种实现方式中，所述通信系统还包括：第一网元，所述第一网元，用于执行上述第四方面中任一种实现方式的方法。
附图说明
图1是本申请适用的一种网络架构的示意图。
图2是本申请适用的一种场景示意图。
图3是本申请适用的另一场景示意图。
图4是本申请提供的广播通信方法100的示意性流程图。
图5是本申请提供的广播通信方法200的示意性流程图。
图6是本申请提供的广播通信方法300的示意性流程图。
图7是本申请提供的广播通信方法400的示意性流程图。
图8是本申请提供的广播通信方法500的示意性流程图。
图9是本申请提供的广播通信方法600的示意性流程图。
图10是本申请提供的广播通信方法700的示意性流程图。
图11是本申请提供的广播通信方法800的示意性流程图。
图12是本申请提供的广播通信装置100的示意性框图。
图13是本申请提供的广播通信装置200的示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请提及的无线通信系统包括但不限于：全球移动通信(global system of mobile communication，GSM)系统、长期演进(long term evolution，LTE)频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、LTE系统、先进的长期演进(LTE-Advanced，LTE-A)系统、下一代通信系统(例如，6G通信系统)、多种接入系统的融合系统，或演进系统。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(long term evolution-machine，LTE-M)、设备到设备(device to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
首先简单介绍适用于本申请的网络架构，作为示例，图1示出了本申请适用的一种网络架构的示意图。
如图1所示，该网络架构以5G系统(the 5th generation system，5GS)为例。5G系统架构分为接入网和核心网两部分。该网络架构可以包括但不限于：统一数据管理(unified data management，UDM)，网络发现功能(network exposure function，NEF)，网络存储功能(NF repository function，NRF)，策略控制功能(policy control function，PCF)，应用功能(application function，AF)，接入和移动性管理功能(access and mobility management function，AMF)，会话管理功能(session management function，SMF)，用户设备(user  equipment，UE)，无线接入网设备，用户面功能(user plane function，UPF)，数据网络(data network，DN)。其中，DN可以是互联网；UDM、NEF、NRF、PCF、AF、AMF、SMF、UPF属于核心网中的网元，由于图1以5G系统为例，那么该核心网可以称为5G核心网(5G core network，5GC或5GCN)。
下面对图1中示出的各网元做简单介绍。
1、用户设备(user equipment，UE)(101)：可以称为终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是IoT系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物互连的智能化网络。
需要指出的是，终端设备与接入网设备之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备与终端设备之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
2、(无线)接入网((radio)access network，(R)AN)设备(102)：可以为特定区域的授权用户提供接入通信网络的功能，具体可以包括第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中无线网络设备也可以包括非3GPP(non-3GPP)网络中的接入点。下文为方便描述采用AN设备表示。
RAN设备可以为采用不同的无线接入技术。目前的无线接入技术有两种类型：3GPP接入技术(例如，第三代(3rd generation，3G)、第四代(4th generation，4G)或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)或者RAN设备。非3GPP接入技术可以包括以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)等。AN设备可以允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
RAN设备能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。AN设备为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发。
RAN设备例如可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对AN设备所采用的具体技术和具体设备形态不做限定。
3、用户面功能网元(user plane function，UPF)(103)：可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网元的功能。
本申请中涉及的多播/广播(multicast/broadcast，MB)UPF可以用于将检测的多播/广播业务的互联网协议(internet protocol，IP)地址，并发送给MB-SMF。
4、数据网络(digital network，DN)(104)：用于提供传输数据的网络。例如，运营商业务的网络、因特(Internet)网、第三方的业务网络等。
5、接入和移动管理功能网元(access and mobility management function，AMF)(105)：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。在本申请实施例中，可用于实现接入和移动管理功能网元的功能。
6、会话管理功能网元(session management function，SMF)(106)：主要用于会话管理、终端设备的IP地址分配和管理、选择和管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，可用于实现会话管理网元的功能。
本申请中涉及的MB-SMF可以用于管理多播/广播业务，也可以为多播/广播业务配置MB-UPF。例如，MB-SMF可以与MB-UPF通过信令交互来指示MB-UPF识别MBS数据的IP地址，此外MB-SMF可能需要增强向RAN发送的消息，用于RAN识别同一多播/广播业务。本申请中的管理多播/广播的SMF与管理单播的SMF可能不同，单播SMF和多播SMF之间可以是N16接口。
7、策略控制网元(policy control function，PCF)(107)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
8、统一数据管理网元(unified data management，UDM)(108)：用于统一数据管理、5G用户数据管理、处理用户标识、接入鉴权、注册、或移动性管理等。
9、应用功能网元(application function，AF)：用于进行应用影响的数据路由，接入网络开放功能网元，或，与策略框架交互进行策略控制等。本申请中AF也可以理解为应用服务器。
在图1所示的网络架构中，各网元之间可以通过图中所示的接口通信。如图所示，N1接口为终端设备与AMF之间的参考点；N2接口为RAN和AMF的参考点，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为RAN和UPF之间的参考点，用于传输用户面的数据等；N4接口为SMF和UPF之间的参考点，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N5接口为PCF与AF之间的参考点；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等；N7接口为SMF和PCF之间的参考点；N8接口为AMF和UDM之间的参考点；N11接口为AMF与AMF之间的参考点。其他接口与各网元之间的关系如图1中所示，为了简洁，这里不一一详述。
应理解，上述图1所示的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF、SMF、UPF、PCF、UDM等功能或者网元，可以理解为用于实现不同功能的网元。例如，可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。
为了便于理解本申请的技术方案，下面对本申请中涉及到的术语做简单说明。
1、多播：相同的服务和相同的特定内容数据同时提供给一组专用的UE(即，并非多 播覆盖中的所有UE都被授权接收数据)。本申请中的“多播”也可以理解为“组播”。
2、广播：相同的特定内容的数据同时提供给地理区域中的所有UE(即，广播覆盖区域中的所有UE都被授权接收数据)。
3、多播/广播业务会话(multicast/broadcast service-session，MBS session)：一个多播/广播会话可以为一个多播/广播业务提供服务。一个多播/广播会话包括从数据网络到核心网设备再到接入网设备的单播或组播隧道、以及接入网设备分配的用于发送该多播/广播业务的单播或多播/广播空口资源。
图2示出了本申请适用的一种场景示意图。通常情况下，运营商在部署网络时，为了减少部署无线接入网的成本，一般选择会在保留各自核心网的同时共享无线接入网设备(下述描述中，以基站作为无线接入网设备进行说明)。例如，TS23.501中所定义的多运营商核心网(multi-operator core network，MOCN)场景。如图2所示，假设有三个运营商，其中，运营商#A、运营商#B和运营商#C分别拥有自己的核心网，但是为了节约成本(例如，部署基站的成本)，三个运营商可能会共享基站。与普通场景相比，MOCN场景的部署方式中，广播消息中包含公共陆地移动网络(public land mobile network，PLMN)的信息。例如，基站发送的小区信息中包括小区所属的PLMN的信息。
图3示出了本申请适用的另一种场景示意图，如图3所示，目前，某些广播业务(例如，天气预报，高精地图更新等)在不同运营商上传输的内容是相同的。针对这类广播业务，相同的广播业务的数据在不同运营商的核心网以及运营商所共享的基站上需要多次传输。例如，如图3所示，假设有两个运营商(记为PLMN#a和PLMN#b)，多播/广播业务的内容提供商(MBS content provider)分别向PLMN#a和PLMN#b发送广播数据。由于PLMN#a和PLMN#b共享基站，相同的广播业务的数据会在基站中发送两次(也可以理解为，基站为传输不同运营商网络中的相同广播业务需要分配两次空口资源)，从而造成传输资源的浪费。
下文将结合附图详细说明本申请实施例提供的广播通信方法。本申请提供的实施例可以应用于上述图1所示的网络架构中，也可以应用于如图2、图3所示的场景中，不作限定。
图4是本申请提供的一种广播通信方法100的示意图，该方法例如可以由无线接入网设备执行，方法100包括如下步骤。
步骤101，无线接入网设备接收来自第一接入和移动管理功能网元的第一消息。
其中，无线接入网设备可以由至少两个网络共享，该至少两个网络可以是PLMN粒度的，也可以是独立非公共网络(standalone non-public network，SNPN)粒度的。例如，该至少两个网络可以包括第一网络和第二网络，第一网络可以是PLMN#1，第二网络可以是PLMN#2；再例如，该至少两个网络可以包括第一网络和第二网络，第一网络可以是SNPN#1，第二网络可以是SNPN#2。
其中，第一接入和移动管理功能网元位于第一网络中。
需要指出的是，本申请各个实施例以无线接入网设备由两个网络共享为例进行说明，不予限制。
其中，第一消息可以用于触发无线接入网设备为第一广播业务分配资源，其中，资源 可以是空口资源，该空口资源可以是调度时间资源、频率资源、调度优先级、缓存资源、数据无线承载(data radio bearer，DRB)；或者，该资源也可以是存储的上下文信息(例如，QoS描述信息、QoS流(flow)的标识信息)等。也可以理解为，第一消息可以用于请求无线接入网设备为第一广播业务分配资源，或者，第一消息可以用于请求无线接入网设备建立第一广播业务对应的上下文。
具体地，第一消息可以为现有消息，例如，N2请求(N2 request)消息；也可以为多播/广播会话相关的消息，例如，MBS会话资源建立请求(MBSsession resource setup request)，或者是MBS会话开始请求(MBS session start request)，或者是广播会话资源建立请求(broadcast session resource setup request)。
需要说明的是，第一消息可以是由第一接入和移动管理功能网元根据从第一多播/广播会话管理功能网元接收的消息来发送的。
其中，第一消息可以携带第一广播业务的标识，该标识可以用于指示第一广播业务。第一广播业务可以是由应用功能网元发起、请求在PLMN网络建立资源并且传输的业务。例如，第一广播业务可以是天气预报业务，紧急事件告警业务、高精地图业务等。
可选的，第一广播业务的标识包括第一标识和/或第二标识。
其中，第一标识可以包括以下至少一项：第一广播业务的全球唯一标识、第一广播业务在至少两个网络中的每个网络中的标识、或第一广播业务对应的临时移动组标识(temporary mobile group identifier，TMGI)，该临时移动组标识由该至少两个网络共享。
其中，第一广播业务的全球唯一标识可以用于全球唯一标识第一广播业务。例如，该全球唯一标识可以是第一广播业务的互联网IP多播地址。又例如，该全球唯一标识除了包括第一广播业务的互联网协议IP多播地址，还可以包括其他内容，例如多播/广播数据的源地址(source address)，不予限定。
例如，对于互联网通信协议第四版(internet protocal version 4，IPv4)，该IP多播地址可以是224.3.0.0到224.4.255.255，或者225.0.0.0到231.255.255.255，或者232.0.0.0到232.255.255.255，或者233.0.0.0到233.251.255.255这些地址段中的一个或多个IP地址；对于互联网通信协议第六版(internet protocal version 6，IPv6)该IP多播地址可以是前缀为ff02或者ff05或者ff0x的一个或多个IP地址，不予限定。
其中，第一广播业务在至少两个网络中的每个网络中的标识，也可以理解为，第一广播业务在该至少两个网络中的每个网络中的广播会话的标识。
可选地，该标识包括网络的标识信息。例如，该网络的标识信息为PLMN ID(例如，33E451)，或PLMN ID+网络标识(network identifier，NID)。
例如，第一广播业务在至少两个网络中的每个网络中的标识可以采用列表(list)的形式体现，该列表包含第一广播业务在至少两个网络中的每个网络中的广播会话的标识。下面以表1为例进行说明，例如，第一广播业务在网络#1中的广播会话标识可以是TMGI#1，TMGI#1具体可以是70A886 32F461；第一广播业务在网络#2的广播会话标识可以是TMGI#2，TMGI#2具体可以是81B749 33E451；第一广播业务在网络#3的广播会话标识可以是TMGI#3，TMGI#3具体可以是649739 42F352。
表1.第一广播业务在每个网络中的广播会话的标识
Figure PCTCN2023070401-appb-000001
需要说明的是，在实际实现中，第一广播业务在至少两个网络中的每个网络中的标识，可以通过上述列表的方式表示，也可以通过数组(例如{70A886 32F461，81B749 33E451，649739 42F352})表示，也可以通过其他用于标识一组数据的方式(例如：结构体、链表等)表示，本申请不予限定。
其中，该广播会话的标识用于标识广播会话，例如，可以是该广播会话对应的群组的标识，例如，临时移动组标识。
其中，第一广播业务对应的临时移动组标识(temporary mobile group identifier，TMGI)，可以由至少两个网络共享。可以理解为，为第一广播业务配置了通用TMGI，该通用TMGI可以在第一网络和第二网络中均唯一标识一个广播业务。具体地，第一网络和第二网络的MB-SMF在向AF请求TMGI时，AF可以提供该通用TMGI。
其中，“通用TMGI”是指某个或某些TMGI可以被若干个(即，至少两个)网络共享。例如，针对第一广播业务，在第一网络中的TMGI与在第二网络中的TMGI相同，均为TMGI#v。
其中，第二标识可以包括：第一广播业务在第一网络中的标识，该第一广播业务在第一网络中的标识可以为第一广播业务在第一网络中的广播会话的标识；可选地，第二标识还包括第一广播业务在第一网络的标识信息，例如PLMN ID或PLMN ID+NID。
需要指出的是，在第一广播业务的标识包括第二标识的情况下，无线接入网设备可以预配置或者获取或接收第一广播业务在至少两个网络中的每个网络中的标识。例如，无线接入网设备在第一次建立第一广播业务的会话时接收到第一广播业务在至少两个网络中的每个网络中的标识的列表(参见表1)，并进行存储。进一步地，在非首次(例如，第二次)建立第一广播业务的会话时，第一网络中的核心网网元(例如，第一接入和移动管理功能网元)可以携带第一广播业务在第一网络中的标识，可以避免重复发送整个list，节省传输资源。
其中，第一广播业务的会话可以指的是用于传输第一广播业务的会话。
需要指出的是，在本申请中，在第一广播业务的标识是第一广播业务的全球唯一标识的情况下，例如，可以通过在应用功能网元向PLMN网络发送的请求消息中，增加一个新信元。即，应用功能网元向PLMN网络发送的请求消息中增加第一广播业务的全球唯一标识来实现，该方式对应用服务器改动较小，易于应用服务器实现，便于推广；在第一广播业务的标识是第一广播业务在至少两个网络中的每个网络中的标识的情况下，可以通过扩展现有接入和移动性管理网元向接入网设备发送的消息中的信元。即，通过将原来第一广 播业务在网络中的标识，扩展成为第一广播业务在至少两个网络中每个网络中的标识，实现新的功能，对网络改动较小，易于升级。
步骤102，无线接入网设备根据第一广播业务的标识，获得第一广播业务对应的第一资源的信息。
其中，第一资源可以用于向第二网络中的终端设备发送第一广播业务的数据。例如，第一资源可以是：空口资源。例如，该空口资源是调度时间资源、频率资源、调度优先级、缓存资源、数据无线承载(data radio bearer，DRB)；第一资源还可以是：存储的上下文信息，例如，QoS描述信息、QoS流(flow)的标识信息)等，不予限定。
其中，第一资源的信息可以是第一资源的标识信息(例如，上下文标识(context ID)，或者第一资源的时域频域位置等信息，不做限定。
其中，步骤102的实现可以分为以下场景：
场景1、对于无线接入网络设备已经在某个网络(以第二网络为例)中建立第一广播业务的会话的场景(也可以理解为，已经在第二网络中为第一广播业务分配资源的场景)。
在场景1中，该第一广播业务的会话所对应的会话上下文(后续可以简称为第一广播业务对应的会话上下文)中可以包括第一广播业务的标识以及为第一广播业务分配的第一资源的信息。步骤102中无线接入网设备根据第一广播业务的标识，获得第一广播业务对应的第一资源的信息，可以采用如下实现方式：
方式一，在第一广播业务的标识为第一广播业务的全球唯一标识的情况下，无线接入网设备根据第一广播业务的全球唯一标识，查找第一广播业务对应的广播会话上下文，无线接入网设备根据广播会话上下文获得第一广播业务对应的第一资源的信息。
其中，广播会话上下文可以包括第一广播业务的全球唯一标识以及第一资源的信息。
由于在第二网络中建立的第一广播业务会话上下文中包括第一广播业务的全球唯一标识以及第一资源的信息，因此，由第一网络和第二网络共享的基站在接收到第一网络请求建立第一广播业务会话上下文(或请求为第一广播业务会话分配资源)时，可以重用第一资源，从而可以避免资源浪费。
方式二，在第一广播业务的标识为第一广播业务在至少两个网络中的每个网络中的标识的情况下，无线接入网设备根据该第一广播业务在至少两个网络中的每个网络中的标识，查找第一广播业务对应的广播会话上下文，无线接入网设备根据广播会话上下文，获得第一广播业务对应的第一资源的信息。
其中，广播会话上下文可以包括第一广播业务在至少两个网络中的每个网络中的标识以及第一资源的信息。
由于在第二网络中建立的第一广播业务对应的广播会话上下文中包括第一广播业务在至少两个网络中的每个网络中的标识以及第一资源的信息。因此，由第二网络和其他网络共享的基站在接收到其他网络请求建立第一广播业务会话上下文(或请求为第一广播业务会话分配资源)时，可以重用第一资源。即，无线接入网设备无须为其他网络中的第一广播业务重新分配资源，从而可以避免资源浪费。
方式三，在第一广播业务的标识为第二标识(例如，第一广播业务在第一网络中的标 识)的情况下，无线接入网设备根据预配置的第一广播业务在第一网络中的标识与第一广播业务在第二网络中的标识的对应关系，以及第二标识，获得第一广播业务在第二网络中的标识，无线接入网设备根据第一广播业务在第二网络中的标识，查找第一广播业务对应的广播会话上下文，无线接入网设备根据广播会话上下文，获得第一广播业务对应的第一资源的信息。
其中，广播会话上下文可以包括第二标识以及第一资源的信息。
并且，由于在第二网络中建立的第一广播业务对应的广播会话上下文中包括第二标识以及第一资源的信息。因此，由第二网络和其他网络共享的基站在接收到其他网络请求建立第一广播业务会话上下文(或请求为第一广播业务会话分配资源)时，可以重用第一资源。即，无线接入网设备无须为其他网络中的第一广播业务重新分配资源，从而可以避免资源浪费。
需要说明的是，上述场景1中，在第二网络中已经为第一广播业务分配资源(例如，第一资源)，该资源可以供多个网络(例如，第一网络)来传输第一广播业务，即无线接入网设备无须为第一网络中的第一广播业务重新分配资源，从而可以避免资源浪费。
在上述各实施方式中，由于第二网络中已经建立过第一广播业务对应的广播会话上下文，且该广播会话上下文中包括第一广播业务的标识和第一资源的信息，因此无线接入网设备可以通过第一广播业务的标识获取在第二网络中已经为第一广播业务分配的第一资源的信息，进而无线接入网设备可以通过第一资源为第一网络中的终端设备发送第一广播业务的数据。
场景2、对于无线接入网络设备还未在各个网络中建立过第一广播业务的会话的场景。
在场景2下，方法100还可以包括：无线接入网设备接收来自第二接入和移动管理功能网元的第二消息，第二消息携带第一广播业务的标识。
其中，第二消息用于触发为第一广播业务分配资源，第二接入和移动管理功能网元位于第二网络。其中，第一广播业务的标识可以包括第一标识。
进一步地，在第一广播业务的标识包括第一标识的情况下(例如，第一广播业务的标识为第一标识；又例如，第一广播业务的标识包括第一标识和第二标识)，无线接入网设备根据第二消息，为第一广播业务分配第一资源，无线接入网设备建立第一广播业务对应的广播会话上下文，其中，该广播会话上下文包括第一广播业务的标识以及所述第一资源的信息。
其中，该场景下的第二消息具体可以参照第一消息的描述。有所区别的是，第二消息是在第二网络中的核心网网元之间传输的，第一消息是在第一网络中的核心网网元之间传输的。
其中，第二消息可以为现有消息，例如，N2请求消息；也可以为多播/广播会话相关的消息，例如，MBS会话资源建立请求，或者是MBS会话开始请求，或者是广播会话资源建立请求。
上述场景2中，如果还未在各个网络中为第一广播业务分配资源以及建立第一广播业务对应的广播会话，则无线接入网设备可以在第二网络为第一广播业务分配资源并且建立 第一广播业务的会话上下文。由于在第二网络中建立的第一广播业务对应的广播会话上下文中包括第一广播业务的标识以及第一资源的信息。因此，无线接入网设备可以不用为不同网络中的相同广播业务重复分配资源，也可以理解为，后续无线接入网设备可以不区分网络，而是根据本地是否已经为该广播业务分配过资源，从而灵活使用(也可以理解为“共享”)该资源。
步骤103，无线接入网设备通过第一资源，向第一网络中的终端设备发送第一广播业务的数据。
在一种可选的实现方式中，无线接入网设备在接收到来自多播/广播用户管理网元的业务数据后，根据该业务数据包含的标识信息(例如，目标IP地址、通用分组无线服务隧道协议(general packet radio service(GPRS)tunnelling protocol，GTP)头的隧道结点标识、QoS流标识)识别出该业务数据属于第一广播业务，无线接入网设备根据本地存储的上下文信息(例如调度队列，预留资源)等，将该业务数据通过第一广播业务对应的空口资源(例如，时频资源)发送(或广播)，相应地，第一网络中的终端设备会监听该空口资源，接收该业务数据。
在又一种可选的实现方式中，在第一广播业务的标识为临时移动组标识的情况下，由于该临时移动组标识由各个网络共享，因此，无线接入网设备接收到该临时移动组标识时，便可以用第一资源向第一网络中的终端设备发送第一广播业务的数据。换句话说，在该实现方式中，由于无线接入网设备在各个网络中接收到的都是相同的临时移动组标识，因此，对于无线接入网设备而言，无须查找第一广播会话上下文获得第一资源的信息，可以直接利用第一资源向第一网络中的终端设备发送第一广播业务的数据。
基于上述技术方案，由于在第二网络中已经建立过第一广播业务对应的广播会话上下文，且该广播会话上下文中包括第一广播业务的标识和第一资源的信息。因此，无线接入网设备可以根据第一广播业务的标识，获取在第二网络中已经为第一广播业务分配的第一资源的信息。无线接入网设备可以通过第一资源为第一网络中的终端设备发送第一广播业务的数据。即，无线接入网设备可以重用第一资源，无须为其他网络中的第一广播业务重新分配资源，从而可以避免资源浪费。
如图5所示，本申请还提供了一种广播通信方法200，该方法例如可以由多播/广播会话管理功能网元执行，方法200包括如下步骤。
步骤201，多播/广播会话管理功能网元接收第一广播业务的标识。
其中，该多播/广播会话管理功能网元可以是位于第一网络中的多播/广播会话管理功能网元，也可以是位于第二网络中的多播/广播会话管理功能网元，不做限定。
可选的，第一广播业务的标识包括第一标识。具体地，第一标识的描述可以参照方法100中的步骤101的描述，此处不再赘述。
在一种可选的实现方式中，多播/广播会话管理功能网元接收第一广播业务的标识，包括：多播/广播会话管理功能网元接收来自应用功能网元的第一广播业务的标识。
进一步的，在多播/广播会话管理功能网元接收来自应用功能网元的第一广播业务的标识之前，方法200还可以包括：
多播/广播会话管理功能网元接收来自所述应用功能网元的第三消息，该第三消息携带所述第一广播业务的标识，第三消息用于触发多播/广播会话管理功能网元向应用功能网元发送第一广播业务的临时移动组标识。多播/广播会话管理功能网元根据第三消息，从第一网元获取第一广播业务的临时移动组标识，或者；多播/广播会话管理功能网元根据所述第三消息，为第一广播业务分配临时移动组标识。
具体地，该第三消息可以是TMGI分配请求(TMGIallocation request)消息。
具体地，第一网元可以是统一数据管理网元、统一数据存储网元、网络存储功能网元、网络发现功能网元、策略控制功能网元、或者，多播/广播的数据库。其中，多播/广播的数据库可以由至少两个网络共享。
在另一种可选的实现方式中，多播/广播会话管理功能网元接收第一广播业务的标识，包括：多播/广播会话管理功能网元接收来自多播/广播用户面功能网元的第一广播业务的标识，其中，第一广播业务的标识为第一广播业务的全球唯一标识。
进一步的，多播/广播会话管理功能网元接收来自多播/广播用户面功能网元的第一广播业务的标识之前，方法200还可以包括：
多播/广播会话管理功能网元向多播/广播用户面功能网元发送第四消息，第四消息用于请求第一广播业务的会话建立或者修改，第四消息携带第一指示信息，第一指示信息用于触发多播/广播用户面功能网元检测第一广播业务的标识。
上述通过指示多播/广播用户面功能网元检测第一广播业务的标识，能够成功获得第一广播业务的全球唯一标识，即可以不依赖应用功能网元便可以获得第一广播业务的标识。
其中，该多播/广播用户面功能网元可以是位于第一网络中的多播/广播用户面功能网元，也可以是位于第二网络中的多播/广播用户面功能网元，不做限定。
具体地，该第四消息可以是N4会话建立或修改请求(N4mbsession establishment/modification request)消息。
步骤202，多播/广播会话管理功能网元向接入和移动管理功能网元发送第一广播业务的标识。
其中，该接入和移动管理功能网元可以是位于第一网络中的接入和移动管理功能网元，也可以是位于第二网络中的接入和移动管理功能网元，不做限定。
基于上述技术方案，多播/广播会话管理功能网元可以接收第一广播业务的标识，并发送给接入和移动管理功能网元，从而使得无线接入网设备可以获得第一广播业务的标识，在不同网络中识别相同的广播数据。
如图6所示，本申请还提供了一种广播通信方法300，该方法例如可以由应用功能网元执行，方法300包括如下步骤。
步骤301，应用功能网元获得第一广播业务的标识。
可选的，第一广播业务的标识包括第一标识。具体地，第一标识的描述可以参照方法100中的步骤101的描述，此处不再赘述。
在一种可选的实现方式中，应用功能网元获得第一广播业务的标识，包括：应用功能网元生成第一广播业务的全球唯一标识。
在另一种可选的实现方式中，应用功能网元获得第一广播业务的标识，包括：应用功能网元从第一网络中的第一多播/广播会话管理功能网元接收第一广播业务在第一网络中的标识；应用功能网元从第二网络中的第二多播/广播会话管理功能网元接收第一广播业务在第二网络中的标识。
也可以理解为，应用功能网元可以通过与各个网络的核心网的网元之间的交互，获取第一广播业务在各个网络中的标识。
在又一种可选的实现方式中，应用功能网元获得第一广播业务的标识，包括：应用功能网元从多播/广播会话管理功能网元获得第一广播业务的临时移动组标识。
步骤302，应用功能网元向多播/广播会话管理功能网元发送第一广播业务的标识。
根据本实施提供的方法，应用功能网元可以通过上述各个实现方式灵活获取第一广播业务的标识。
基于上述技术方案，应用功能网元可以将获取的第一广播业务的标识发送给多播/广播会话管理功能网元，从而可以使得无线接入网设备可以获得第一广播业务的标识，在不同网络中识别相同的广播数据。
如图7所示，本申请还提供了一种广播通信方法400，该方法可以由第一网元执行，方法400包括如下步骤。
步骤401，第一网元从多播/广播会话管理功能网元接收第五消息。
其中，第五消息可以携带第一广播业务的标识，第五消息可以用于触发第一网元发送第一广播业务的临时移动组标识。
其中，关于第一网元的说明可以参照方法200中的步骤201中的描述，此处不再赘述。
具体地，第五消息可以是用于请求广播会话创建(creation of broadcast sessions)的消息，或者，第五消息可以是多播/广播会话创建请求消息(例如，Nmbsmf_MBS sessioncreate request)，用于请求第一广播业务的临时移动组标识。
步骤402，第一网元根据第五消息，向多播/广播会话管理功能网元发送第一广播业务的临时移动组标识。
可选的，该方法400还包括：第一网元从多播/广播会话管理功能网元接收第一广播业务的标识与临时移动组标识之间的对应关系。也可以理解为，第一网元上预先存储的第一广播业务的临时移动组标识中没有完全包括在各个网络中的第一广播业务的临时移动组标识，此时，多播/广播会话管理功能网元可以为该网络中中的第一广播业务分配临时移动组标识，并且发送给第一网元进行存储。
可选的，该临时移动组标识由至少两个网络共享。例如，针对第一广播业务，其临时移动组标识在各个网络中是相同的。又例如，针对第一广播业务，其临时移动组标识在各个网络中不相同，但是在各个网络中通过该临时移动组标识，各个网络的核心网网元以及无线接入网设备可以识别其指示的都为第一广播业务。
基于上述技术方案，通过设计第一广播业务的临时移动组标识，使得第一广播业务在不同网络中标识，都可以被各个网络的核心网网元或者无线接入网设备识别出指示的为第一广播业务，从而无须无线接入网设备在不同网络中为第一广播业务均重新分配资源，避 免空口资源的浪费。
本申请中，在下述具体实施例中，第一网络以PLMN#a为例，第二网络以PLMN#b为例进行说明，终端设备以UE为例进行说明。下述实施例中核心网的网元的后缀为“#b”代表该核心网的网元在PLMN#b中，核心网的网元的后缀为“#a”代表该核心网的网元在PLMN#a中。下述具体实施例中的RAN可以理解为PLMN#a与PLMN#b共享的RAN。
需要说明的是，本申请的下述实施例中仅仅是以两个PLMN网络为例进行说明，本申请中，并不限定网络的数量。即，本申请的技术方案可以适用于n(n≥1)个网络共享RAN的场景。
图8是本申请提供的一种广播通信方法500的示意性流程图。假设本实施例中有两个PLMN(记为，PLMN#a和PLMN#b)，本实施例中以广播业务#1为例进行说明，该方法包括：
步骤501，AF向不同的PLMN网络请求广播业务#1在不同PLMN中的标识。
本申请中，广播业务#1在不同PLMN中的标识，可以是MBS Session ID，例如，临时移动组标识(temporary mobile group identifier，TMGI)，以下不再赘述。
例如，AF向PLMN#a中的MB-SMF#a请求广播业务#1的标识，假设，AF获得广播业务#1在PLMN#a中的标识为TMGI#x；同样的，AF向PLMN#b中的MB-SMF#b请求广播业务#1的标识，假设，AF获得广播业务#1在PLMN#b中的标识为TMGI#y。
步骤502，AF生成广播业务#1的全球唯一标识。
在一种可选的实现方式中，AF基于广播业务#1在PLMN#a中的标识以及广播业务#1在PLMN#b中的标识，生成广播业务#1的全球唯一标识。
本实施例中，该广播业务#1的全球唯一标识，例如，可以用于标识广播业务#1的数据；又例如，该全球唯一标识可以是一个数字；又例如，可以是用于标识广播业务#1的地址信息等等。
作为一个示例，广播业务#1的全球唯一标识可以是用于标识广播业务#1的数据，例如，Indication#z；作为一个示例，对于广播业务#2，其全球唯一标识可以是用于标识广播业务#2的数据，例如，Indication#w。
作为另一个示例，广播业务#1的全球唯一标识还可以是广播业务#1的IP多播地址。需要说明的是，本实施中如果广播业务#1的全球唯一标识为广播业务#1的IP多播地址时，可选地，不用执行步骤501。也可以理解为，此时AF不用先向各个PLMN请求广播业务#1的在各自PLMN中的TMGI。例如，后续AF在向MB-SMF#b发送会话创建请求消息的同时，如果只携带了广播业务#1的IP多播地址，而没有携带在PLMN#b中的TMGI时，此时MB-SMF#b会向AF提供广播业务#1在PLMN#b中的TMGI。
例如，本实施例中，在不同的PLMN中，广播业务#1的TMGI(例如，TMGI#x、TMGI#y)有相同的indication#z(广播业务#1全球唯一标识的一例)，则后续基站便可以识别出在不同的PLMN中，这些不同的广播业务标识其实对应的是同一个广播业务(即，广播业务#1)。换句话说，在不同的PLMN中，虽然TMGI不同(例如，不同的PLMN中广播业务#1有不同的TMGI)，但是，都携带了广播业务#1的全球唯一标识，例如，indication#z。则RAN可 以确定其请求传输的是同一个广播业务，即，请求传输的是相同的广播数据。
又例如，本实施例中，在不同的PLMN中，广播业务#1的TMGI(例如，TMGI#x、TMGI#y)有相同的IP多播地址(广播业务#1全球唯一标识的另一例)，则后续基站便可以识别出在不同的PLMN中，这些不同的TMGI其实对应的是同一个广播业务(即，广播业务#1)。换句话说，在不同的PLMN中，虽然广播业务#1的标识不同(例如，不同的PLMN中广播业务#1有不同的TMGI)，但是，其请求传输的是均是广播业务#1，或者，也可以理解为其请求传输的是广播业务#1的广播数据。
步骤503，AF向PLMN#b中的MB-SMF#b发送会话创建请求(session create request)消息。
对应的，PLMN#b中的MB-SMF#b接收广播会话创建请求。
该会话创建请求消息携带广播业务#1的全球唯一标识，例如，该会话创建建立请求消息携带广播业务#1的Indication#z。又例如，该广播会话创建请求消息携带广播业务#1的IP多播地址。
在一种可选的实现方式中，AF可以向MB-SMF#b发送会话创建请求。例如，AF通过调用Nmbsmf_MBSSession_Create Request服务向MB-SMF#b发送广播会话创建请求。也可以理解为，此时AF处于信任域(trusted domain)。
在另一种可选的实现方式中，AF可以先向NEF发送会话创建请求，然后NEF向MB-SMF#b转发该会话创建请求。例如，AF通过调用Nnef_MBSSession_Create request服务先向NEF发送该会话创建请求，NEF之后再调用Nmbsmf_MBSSession_Create Request服务向MB-SMF#b转发该会话创建请求。也可以理解为，此时AF处于非信任域(untrusted domain)，NEF可能会调整广播会话创建请求中的某些信息。例如，由于AF处于非信任域，不知道具体小区的规划，这样AF可能提供的是地理区域信息，NEF会将该地理区域信息“翻译”成小区或者追踪区域信息，发送给MB-SMF#b。
本实施例中，AF向MB-SMF#b发送的会话创建请求消息中还可以携带以下信息中一项或者多项：例如，广播业务#1在PLMN#b中的标识TMGI#y、广播业务#1的需求信息、广播的区域信息。
其中，广播业务#1的需求信息，例如，可以包括：广播业务#1的时延需求、广播业务#1的优先级需求、广播业务#1的带宽需求等等。或者，替代地，也可以是广播的策略信息.例如：5G服务质量(quality of service，QoS)标识符(identifier)(即，5QI)、分配和抢占优先级(allocation and retention priority，ARP)信息等等。
步骤504，PLMN#b中的MB-SMF#b获取广播业务#1的会话的QoS信息。
在一种可选的实现方式中，MB-SMF#b可以将获取的广播业务#1的需求信息，发送给PCF#b网元，并从PCF#b网元获取广播业务#1的会话的策略信息，根据该策略信息生成广播会话的QoS信息。
在另一种可选的实现方式中，AF可以将广播业务#1的需求信息发送给PCF#b，PCF#b根据该业务需求信息生成广播会话的策略信息，PCF#b可以将广播业务#1的会话的策略信息推送给MB-SMF#b，MB-SMF#b根据该策略信息生成广播会话的QoS信息。
在又一种可选的实现方式中，MB-SMF#b可以根据获取的广播业务#1的需求信息，依据本地配置的策略，生成广播会话的QoS信息。
步骤505，MB-SMB#b选择AMF#b，并向AMF#b发送会话开始请求(session start request)消息。
对应的，AMF#b接收会话开始请求消息。
在一种可选的实现方式中，MB-SMF#b可以结合广播的区域信息，以及AMF的覆盖区域选择向哪个AMF发送。
在另一种可选的实现方式中，MB-SMF#b也可以根据其他方式进行选择，例如，MB-SMF#b向所有AMF发送会话开始请求消息等。此时，AMF#b可以根据自己的覆盖范围，以及广播的区域信息接受MB-SMF#b发送的请求。
本实施例中，该会话开始请求消息中携带广播业务#1的全球唯一标识。例如，Indication#z；又例如，广播业务#1的IP多播地址。
此外，该会话开始请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#1在PLMN#b中的标识TMGI#y、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
步骤506，AMF#b选择RAN#x(例如，基站)，并向RAN#x发送N2请求(N2 request)消息(第二消息的一例)。
对应的，RAN#x接收N2请求消息。
在一种可选的实现方式中，AMF#b可以结合广播的区域信息以及RAN的覆盖区域选择RAN#x。
在另一种可选的实现方式中，AMF#b也可以根据其他方式进行选择，例如，AMF#b向所有的RAN发送消息等。此时，RAN#x可以根据自己的覆盖范围，以及广播的区域信息判断接受AMF#b发送的请求。
本实施例中，N2请求消息中携带广播业务#1的全球唯一标识。例如，Indication#z；又例如，广播业务#1的IP多播地址。
N2请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#1在PLMN#b中的标识TMGI#y、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
本实施例中，N2请求消息用于触发RAN#x为广播业务#1分配资源，换句话说，N2请求消息用于请求RAN#x为广播业务#1分配资源。也可以理解为，N2请求消息用于请求RAN#x建立广播业务#1对应的会话上下文。
本申请中，AMF#b向RAN#x发送的N2请求消息中的信息和MB-SMF#b发送给AMF#b的会话开始消息中的信息可以不完全相同。例如，AMF#b向RAN#x发送的N2请求消息还可以包括AMF#b生成的其他信息。例如，隧道标识信息下一代应用协议(next generation application protocol，NGAP)的标识信息(例如：AMF NGAP ID、RAN NGAP ID)等等，以下不再赘述。
步骤507，RAN#x基于N2请求消息为广播业务#1分配第一资源，并且建立广播业务#1 对应的广播会话上下文。
其中，该广播会话上下文中可以包括广播业务#1的全球唯一标识以及第一资源的信息。
本申请中，“广播会话的上下文”也可以理解为“广播会话的上下文信息”，以下不再赘述。
本实施例中，第一资源也可以理解为，用于向PLMN#b中UE发送广播业务#1的数据。
作为一个示例，RAN#x可以根据广播会话的QoS信息，分配对应的第一资源。例如，针对保证比特速率(guaranteed bit rate，GBR)的QoS流(flow)进行资源预留等等，具体地，RAN#x确定的广播业务#1的第一资源的信息可以包括：(1)多播接收的群组无线网络临时标识符(group-radio network tempory identity，G-RNTI)的信息。(2)广播业务#1对应的部分带宽(bandwidth part，BWP)的信息。例如，在所述BWP进行该业务的接收，根据BWP配置确定该BWP对应子载波间隔(sub-carrier space，SCS)，频域位置和循环前缀(cyclic prefix，CP)的长度。该BWP配置信息还包括物理下行控制信道(physical downlink control channel，PDCCH)检测的控制资源集(control resource set，COREST)配置信息，所述COREST配置信息指示了进行G-RNTI的PDCCH所在的时频资源。(3)广播业务#1的物理下行数据信道(physical downlink data channel，PDSCH)的加扰序列。也可以理解为，UE在解码该业务的PDSCH时采用该序列进行解扰；(4)G-RNTI的非连续接收(discontinuous reception，DRX)的参数，也可以理解为，UE使用该DRX参数进行G-RNTI检测。(5)解调参考信号的配置，也可以理解为，UE用该参考信号进行G-RNTI调度的PDSCH解调。(6)速率匹配参考信号的信息。
RAN#x建立的广播业务#1对应的广播会话上下文中还可以包括：广播业务#1在PLMN#b中的标识TMGI#y、广播的区域信息(例如，小区列表的信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS上下文(例如，包括一个或者多个MBS QoS flows对应的上下文。例如，QoS flow Identifier、QoS flow level QoS parameters以及MBS会话的标识信息)。
可选的，本申请中，该广播会话上下文中还可以包括MBS会话的无线承载(radio bearer)的信息，以下不再赘述。
本申请中，RAN#x可以根据其是否位于广播区域信息对应的区域之内，判断是否需要存储广播会话上下文。例如，RAN#x判断其位于广播区域信息对应的区域之内，则存储广播会话上下文；又例如，RAN#x判断其不在广播区域信息对应的区域之内，则不存储广播会话上下文，以下不再赘述。
步骤507也可以理解为，RAN#x基于N2请求消息以及广播业务#1的全球唯一标识(例如，Indication#z)，查找广播业务#1对应的广播会话上下文。若RAN#x没有查到包含Indication#z的广播会话的上下文，则RAN#x确定还没有为广播业务#1分配过资源，进一步地，RAN#x在PLMN#b中为广播业务#1分配资源，并且建立广播业务#1对应的广播会话上下文。
步骤508，RAN#x向AMF#b发送N2响应消息。
例如，RAN#x向AMF#b发送N2 response消息用于响应AMF#b发送的N2 request消息。
步骤509，AMF#b向MB-SMF#b发送会话开始响应消息。
例如，AMF#b向MB-SMF#b发送session start response消息用于响应MB-SMF#b发送的session start request消息。
本申请中，在各个网络中建立广播会话的后续步骤中，例如还可以包括MB-SMF#b配置MB-UPF#b(例如，配置MB-UPF#b对多播数据的识别、转发规则等)，以及MB-SMF#b向AF发送会话创建请求的响应消息等等，具体的内容可以参照协议3GPPTS 23.247，此处不再赘述。
上述步骤503～步骤509为在PLMN#b中建立广播业务#1对应的广播会话以及为广播业务#1的数据分配第一资源的流程。下述步骤510～516为在PLMN#a中建立广播业务#1对应的广播会话以及使用在PLMN#b中为广播业务#1分配的第一资源向PLMN#a中的UE发送广播业务#1的数据的流程。
步骤510，AF向PLMN#a中的MB-SMF#a发送广播会话创建请求(session create request)消息。
对应的，PLMN#a中的MB-SMF#a接收广播会话创建请求。
该广播会话创建请求消息携带广播业务#1的全球唯一标识，例如，该广播会话创建请求消息携带广播业务#1的Indication#z；又例如，该广播会话创建请求消息携带广播业务#1的IP多播地址。
在一种可选的实现方式中，AF可以向MB-SMF#a发送广播会话创建请求。例如，AF通过调用Nmbsmf_MBSSession_Create Request服务向MB-SMF#a发送广播会话创建请求。也可以理解为，此时AF处于信任域(trusted domain)。
在另一种可选的实现方式中，AF可以先向NEF发送会话创建请求，然后NEF向MB-SMF#a转发该会话创建请求。例如，AF通过调用Nnef_MBSSession_Create request服务先向NEF发送该会话创建请求，NEF之后再调用Nmbsmf_MBSSession_Create Request服务向MB-SMF#a转发该会话创建请求。也可以理解为，此时AF处于非信任域(untrusted domain)，NEF可能会调整广播会话创建请求中的某些信息。例如由于AF处于非信任域，不知道具体小区的规划，这样AF可能提供的是地理区域信息，NEF会将该地理区域信息“翻译”成小区或者追踪区域信息，发送给MB-SMF#a。
具体地，AF向MB-SMF#a发送的会话创建请求消息中携带广播业务#1的全球唯一标识。该会话创建请求消息中还可以携带以下信息中一项或者多项：例如，广播业务#1在PLMN#a中的标识TMGI#x、广播业务#1的需求信息、广播的区域信息。
其中，广播业务#1的需求信息，例如，可以包括：广播业务#1的时延需求、广播业务#1的优先级需求、广播业务#1的带宽需求等等。或者，替代地，也可以是广播的策略信息.例如：5G服务质量(quality of service，QoS)标识符(identifier)(即，5QI)、分配和抢占优先级(allocation and retention priority，ARP)信息等等。
步骤511，PLMN#a中的MB-SMF#a获取广播业务#1的会话的QoS信息。
在一种可选的实现方式中，MB-SMF#a可以将获取的广播业务#1的需求信息，发送给PCF#a网元，并从PCF网元获取广播业务#1的会话的策略信息，根据该策略信息生成广播 会话的QoS信息。
在另一种可选的实现方式中，MB-SMF#a可以直接从PCF#a获取的广播业务#1的会话的策略信息，并根据该策略信息生成广播会话的QoS信息。
在又一种可选的实现方式中，MB-SMF#a可以根据获取的广播业务#1的需求信息，依据本地配置的策略，生成广播会话的QoS信息。
步骤512，MB-SMB#a选择AMF#a网元，并向AMF#a发送会话开始请求(session start request)消息。对应的，AMF#a接收会话开始请求消息。
在一种可选的实现方式中，MB-SMF#a可以结合广播的区域信息，以及AMF的覆盖区域选择向哪个AMF发送。
在另一种可选的实现方式中，MB-SMF#a也可以根据其他方式进行选择，例如，MB-SMF#a向所有AMF发送会话开始请求消息等。此时，AMF#a可以根据自己的覆盖范围，以及广播的区域信息接受MB-SMF#a发送的请求。
本实施例中，该会话开始请求消息中携带广播业务#1的全球唯一标识。例如，Indication#z；又例如，广播业务#1的IP多播地址。
该会话开始请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#1在PLMN#a中的标识TMGI#x、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
步骤513，AMF#a选择RAN#x(例如，基站)，并向RAN#x发送N2请求(N2 request)消息(第一消息的一例)。
对应的，RAN#x接收N2请求消息。
在一种可选的实现方式中，AMF#a可以结合广播的区域信息，以及RAN的覆盖区域选择RAN#x。
在另一种可选的实现方式中，AMF#a也可以根据其他方式进行选择，例如，AMF#a向所有的RAN发送消息等。此时，RAN#x可以根据自己的覆盖范围，以及广播的区域信息接受AMF发送的请求。
也可以理解为，本申请中，在PLMN#b和PLMN#a中选择了同一个RAN，例如，RAN#x。换句话说，本申请中在不同网络中，RAN可以是共享的(例如，为同一个RAN)，以下不再赘述。
本实施例中，N2请求消息中携带广播业务#1的全球唯一标识，例如，Indication#z；又例如，广播业务#1的IP多播地址。
N2请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#1在PLMN#b中的标识TMGI#x、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
本实施例中，N2请求消息用于触发RAN#x为广播业务#1分配资源，换句话说，N2请求消息用于请求RAN#x为广播业务#1分配资源。也可以理解为，N2请求消息用于请求RAN#x建立广播业务#1对应的会话上下文。
本实施例中，AMF#a向RAN#x发送的N2请求消息中的信息和MB-SMF#a发送给AMF #a的会话开始消息中的信息可以不完全相同。例如，AMF#a向RAN#x发送的N2请求消息还可以包括AMF#a生成的其他信息。例如，隧道标识信息、下一代应用协议(next generation application protocol，NGAP)的标识信息(例如：AMF NGAP ID、RAN NGAP ID)等等。
步骤514，RAN#x基于N2请求消息以及广播业务#1的全球唯一标识判断是否已经为广播业务#1分配过资源。若已经为广播业务#1分配过资源，则RAN#x通过该资源发送PLMN#a中广播业务#1的数据；和/或，若RAN#x尚未为广播业务#1分配过资源，则RAN#x为广播业务#1分配资源。
其中，“资源”可以参考前述实施例中的相关描述，不再赘述。
在一种可选的实现方式中，RAN#x基于N2请求消息以及广播业务#1的全球唯一标识，例如，Indication#z，查找广播业务#1对应的广播会话上下文。RAN#x确定在PLMN#b中的广播会话的上下文中已经包含了Indication#z，则RAN#x确定已经为广播业务#1分配过资源，并在PLMN#b中的广播会话的上下文中查找到第一资源的信息。RAN#x确定不在PLMN#a中建立广播业务#1对应的空口资源，并且不在PLMN#a中建立广播业务#1对应的上下文。即，RAN#x确定可以通过该PLMN#b中的第一资源发送PLMN#a中广播业务#1的数据。
在另一种可选的实现方式中，如果在RAN#x在查找广播业务#1的全球唯一标识之前，已经在PLMN#a中为广播业务#1分配了第二资源，并且在PLMN#a中为广播业务#1建立了上下文。待RAN#x查找之后，确定之前在PLMN#b中已经为广播业务#1分配过资源，并在PLMN#b中的广播会话的上下文中查找到第一资源的信息。则RAN#x可以删除(“删除”也可以理解为“释放”)在PLMN#a中为广播业务#1分配的第二资源，并且删除在PLMN#a中为广播业务#1建立的上下文。即，RAN#x确定可以通过该PLMN#b中的第一资源发送PLMN#a中广播业务#1的数据。或者，RAN#x可以不在第二资源上发送PLMN#a中的广播业务#1的数据，仍然利用PLMN#b中为广播业务#1分配的第一资源发送PLMN#b中的广播业务#1的数据。
本申请中，关于RAN#x“查找广播业务#1对应的广播会话上下文”例如可以是下述实现方式。一种可选的实现方式中，RAN#x在接收到全球唯一标识之后，会在本地存储的广播会话上下文中查找全球唯一标识是否存在，如果存在一个广播会话上下文，其对应的全球唯一标识与广播业务#1的全球唯一标识相同，那么可以认为查找成功，否则RAN#x可以认为广播业务#1尚未在本基站建立上下文，换言之，此RAN#x是第一次接收与广播业务#1相关的N2消息。以下不再赘述。
本申请中，“RAN#x通过该资源发送PLMN#a中广播业务#1的数据”例如可以是下述实现方式。在一种可选的实现方式中，RAN#x根据接收的业务数据所包含的标识信息(例如：目标IP地址、GTP头的隧道结点标识、QoS流标识)，识别出数据属于广播业务#1，此后RAN#x可以根据本地存储的上下文信息(例如调度队列，预留资源)等，将广播业务#1的数据在空口(例如，时频资源)资源上发送。位于不同网络的、但接收广播业务#1的终端设备会监听对应空口资源，进而可以接收到广播业务#1的数据。以下不再赘述。
步骤515，RAN#x向AMF#a发送N2响应消息。
例如，RAN#x向AMF#a发送N2 response消息用于响应AMF#a发送的N2 request消息。
步骤516，AMF#a向MB-SMF#a发送会话开始响应消息。
例如，AMF#a向MB-SMF#a发送session start response消息用于响应MB-SMF#a发送的session start request消息。
基于上述技术方案，通过给RAN发送广播业务的全球唯一标识，使得在不同运营商共享基站的场景下，RAN可以识别出相同的广播业务，从而使得RAN通过已经在PLMN#b中为该广播业务分配的资源，发送PLMN#a中的该广播业务的数据。也可以理解为，RAN可以对不同运营商的用户共享空口资源，这样可以节约RAN的传输资源，避免空口资源浪费。
图9是本申请提供的一种广播通信方法600的示意性流程图。假设本实施例中有两个PLMN(记为，PLMN#a和PLMN#b)，本实施例中以广播业务#2为例进行说明，该方法包括：
步骤601，AF向PLMN#b中的MB-SMF#b发送会话创建请求(session create request)消息。
对应的，PLMN#b中的MB-SMF#b接收会话创建请求。
本实施例中，AF可以在向MB-SMF#b发送会话创建请求后，MB-SMF#b可以向AF提供广播业务#2在PLMN#b中的TMGI，例如为TMGI#p。
具体地，AF向MB-SMF#b发送会话创建请求的方式可以参照方法500中的步骤503。
本实施例中，AF向MB-SMF#b发送的会话创建请求消息中携带以下信息中一项或者多项：例如，广播业务#2的MBS会话标识，例如TMGI#p、广播业务#2的需求信息、广播的区域信息。
其中，广播业务#2的需求信息，例如，可以包括：广播业务#2的时延需求、广播业务#2的优先级需求、广播业务#2的带宽需求等等。或者，替代地，也可以是广播的策略信息.例如：5G服务质量(quality of service，QoS)标识符(identifier)(即，5QI)、分配和抢占优先级(allocation and retention priority，ARP)信息等等。
步骤602，PLMN#b中的MB-SMF#b获取广播业务#2的会话的QoS信息。
具体地，MB-SMF#b获取广播业务#2的会话的QoS信息的方式可以参照方法500中的步骤504，此处不再赘述。
步骤603，MB-SMB#b选择AMF#b，并向AMF#b发送会话开始请求(session start request)消息。
对应的，AMF#b接收会话开始请求消息。
具体地，MB-SMB#b选择AMF#b的方式可以参照方法500中的步骤505，此处不再赘述。
本实施例中，该会话开始请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#2在PLMN#b中的标识TMGI#p、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
步骤604，AMF#b选择RAN#x(例如，基站)，并向RAN#x发送N2请求(N2 request) 消息(第二消息的一例)。
对应的，RAN#x接收N2请求消息。
具体地，AMF#b选择RAN#x的方式可以参照方法500中的步骤506，此处不再赘述。
本实施例中，N2请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#2在PLMN#b中的标识TMGI#p、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
本实施例中，N2请求消息用于触发RAN#x为广播业务#2分配资源，换句话说，N2请求消息用于请求RAN#x为广播业务#2分配资源。也可以理解为，N2请求消息用于请求RAN#x建立广播业务#2对应的会话上下文。
步骤605，RAN#x基于N2请求消息为广播业务#2分配第一资源，并且建立广播业务#2对应的广播会话上下文。
本实施例中，第一资源也可以理解为，用于向PLMN#b中UE发送广播业务#2的数据。
作为一个示例，RAN#x可以根据广播会话的QoS信息，分配对应的第一资源。例如，针对保证比特速率(guaranteed bit rate，GBR)的QoS流(flow)进行资源预留等等，具体地，RAN#x确定的广播业务#2的第一资源的信息可以包括：(1)多播接收的群组无线网络临时标识符(group-radio network tempory identity，G-RNTI)。(2)广播业务#2对应的部分带宽(bandwidth part，BWP)的信息。例如，在所述BWP进行该业务的接收，根据BWP配置确定该BWP对应子载波间隔(sub-carrier space，SCS)，频域位置和循环前缀(cyclic prefix，CP)的长度。该BWP配置信息还包括物理下行控制信道(physical downlink control channel，PDCCH)检测的控制资源集(control resource set，COREST)配置信息，所述COREST配置信息指示了进行G-RNTI的PDCCH所在的时频资源。(3)广播业务#2的物理下行数据信道(physical downlink data channel，PDSCH)的加扰序列。也可以理解为，UE在解码该业务的PDSCH时采用该序列进行解扰；(4)G-RNTI的非连续接收(discontinuous reception，DRX)的参数，也可以理解为，UE使用该DRX参数进行G-RNTI检测。(4)解调参考信号的配置，也可以理解为，UE用该参考信号进行G-RNTI调度的PDSCH解调。(5)速率匹配参考信号的信息。
RAN#x建立的广播业务#2对应的广播会话上下文中还可以包括：广播业务#2在PLMN#b中的标识TMGI#p、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS上下文。
步骤606，RAN#x向AMF#b发送N2响应消息。
例如，RAN#x向AMF#b发送N2 response消息用于响应AMF#b发送的N2 request消息。
步骤607，AMF#b向MB-SMF#b发送会话开始响应消息。
例如，AMF#b向MB-SMF#b发送session start response消息用于响应MB-SMF#b发送的session start request消息。
步骤608，MB-SMF#b配置MB-UPF#b。
例如，MB-SMF#b向MB-UPF#b发送N4会话建立或修改(N4mb Session establishment/modification)消息(第四消息的一例)，该消息中可以包含以下内容的一项 或多项：广播业务#2的标识信息、指示信息#1(第一指示信息的一例)。其中，指示信息#1用于指示MB-UPF#b检测广播业务#2的IP多播地址(广播业务#2的全球唯一标识的一例)。例如，MB-UPF#b检测广播业务#2的下行数据包的IP多播地址(例如，可以是目标IP地址，源IP地址等)。此后，广播业务#2的数据便可以在核心网和RAN#x处传输。
步骤609，MB-UPF#b向MB-SMF#b发送通知消息(例如，发送Notification消息)，通知消息中携带广播业务#2的IP多播地址。对应的，MB-SMF#b接收该通知消息。
步骤610，MB-SMF#b向RAN发送广播业务#2的IP多播地址。
例如，MB-SMF#b通过调用AMF的Namf_MBSBroadcast_ContextUpdate服务先将该IP多播地址发送给AMF#b，然后AMF#b通过N2消息发送给RAN#x。
步骤611，RAN#x将广播业务#2的IP多播地址保存在PLMN#b中建立的广播会话上下文中。
例如，RAN#x将广播业务#2的下行数据包的IP多播地址，作为广播会话上下文的一部分进行存储。
上述步骤601～步骤611为在PLMN#b中建立广播业务#2对应的广播会话、为广播业务#2的数据分配第一资源以及将广播业务#2的全球唯一标识存储在广播会话上下文中的流程。下述步骤612～622为在PLMN#a中建立广播业务#2对应的广播会话以及使用在PLMN#b中为广播业务#2分配的第一资源向PLMN#a中的UE发送广播业务#2的数据的流程。
步骤612～步骤615，可以参照上述步骤601～604的描述，不同的是，步骤612～步骤615均是在PLMH#a中，所涉及的相关核心网网元也都是PLMH#a中的核心网网元。
可选的，步骤616，RAN#x基于N2请求消息为广播业务#2分配第一资源，并且建立广播业务#2对应的广播会话上下文。
具体地，可以参照步骤605的描述，不同的是，此时RAN#x在PLMN#a为广播业务#2分配第二资源，此处不再赘述。
步骤617～步骤618，可以参照上述步骤606～607，不同的是，步骤617～步骤618均是在PLMH#a中，所涉及的相关核心网网元也都是PLMH#a中的核心网网元。
步骤619，MB-SMF#a配置MB-UPF#a。
例如，MB-SMF#a向MB-UPF#a发送N4会话建立或修改(N4mb session establishment/modification)消息(第四消息的一例)，该消息中可以包含以下内容的一项或多项：广播业务#2的标识信息、指示信息#2(第一指示信息的一例)。其中，指示信息#2用于指示MB-UPF#a检测广播业务#2的IP多播地址(广播业务#3的全球唯一标识的一例)。例如，MB-UPF#a检测广播业务#2的下行数据包的IP多播地址(例如，可以是目标IP地址，源IP地址等)。此后，广播业务#2的数据便可以在核心网和RAN#x处传输。
步骤620，MB-UPF#a向MB-SMF#a发送通知消息(例如，发送Notification消息)，通知消息中携带广播业务#2的IP多播地址。
对应的，MB-SMF#a接收该通知消息。
步骤621，MB-SMF#a向RAN#x发送广播业务#2的IP多播地址。
例如，MB-SMF#a通过调用AMF的Namf_MBSBroadcast_ContextUpdate服务先将该IP 多播地址发送给AMF#a，然后AMF#a通过N2消息发送给RAN#x。
步骤622，RAN#x基于广播业务#2的IP多播地址判断是否已经为广播业务#2分配过资源。若已经为广播业务#2分配过资源，则通过该资源发送PLMN#a中广播业务#2的数据；和/或，若RAN尚未为广播业务#2分配过资源，则RAN#x为广播业务#2分配资源。
其中，“资源”可以参考前述实施例中的相关描述，不再赘述。
在一种可选的实现方式中，RAN#x基于N2请求消息以及广播业务#2的全球唯一标识，例如，广播业务#2的IP多播地址，查找广播业务#2对应的广播会话上下文。RAN#x确定在PLMN#b中的广播会话的上下文中已经包含了广播业务#2的IP多播地址，则RAN#x确定已经为广播业务#2分配过资源，并在PLMN#b中的广播会话的上下文中查找到第一资源的信息。则RAN#x可以删除(“删除”也可以理解为“释放”)在PLMN#a中为广播业务#2分配的第二资源，并且删除在PLMN#a中为广播业务#2建立的上下文，利用PLMN#b中为广播业务#1分配的第一资源发送PLMN#a中的广播业务#2的数据。或者，RAN#x可以不在第二资源上发送PLMN#a中的广播业务#2的数据，仍然利用PLMN#b中为广播业务#1分配的第一资源发送PLMN#a中的广播业务#2的数据。
在又一种可选的实现方式中，RAN#x不执行步骤616，此时RAN#x不会为广播业务#2在PLMN#a中分配第二资源，直接执行步骤617～步骤622。此时，RAN#x基于N2请求消息以及广播业务#2的全球唯一标识，例如，广播业务#2的IP多播地址，查找广播业务#2对应的广播会话上下文。RAN#x确定在PLMN#b中的广播会话的上下文中已经包含了广播业务#2的IP多播地址。则RAN#x确定已经为广播业务#1分配过资源，并在PLMN#b中的广播会话的上下文中查找到第一资源的信息，则RAN#x确定不在PLMN#a中建立广播业务#2对应的空口资源，并且不在PLMN#a中建立广播业务#2对应的上下文。即，RAN#x确定可以通过该PLMN#b中的第一资源发送PLMN#a中广播业务#2的数据。
基于上述技术方案，通过给RAN发送广播业务的全球唯一标识，使得在不同运营商共享基站的场景下，RAN可以识别出相同的广播业务，从而使得RAN通过已经在PLMN#b中为该广播业务分配的资源，发送PLMN#a中的该广播业务的数据。也可以理解为，RAN可以对不同运营商的用户共享空口资源，这样可以节约RAN的传输资源，避免空口资源浪费。
图10是本申请提供的一种广播通信方法700的示意性流程图。假设本实施例中有两个PLMN(记为，PLMN#a和PLMN#b)，本实施例中以广播业务#3为例进行说明，该方法包括：
步骤701，AF向不同的PLMN网络请求广播业务#3在不同PLMN中的标识。
例如，AF向PLMN#a中的MB-SMF#a请求广播业务#3的标识，假设，AF获得广播业务#3在PLMN#a中的标识为TMGI#m；同样的，AF向PLMN#b中的MB-SMF#b请求广播业务#3的标识，假设，AF获得广播业务#3在PLMN#b中的标识为TMGI#n。
步骤702，AF向PLMN#b中的MB-SMF#b发送会话创建请求(session create request)消息。
对应的，PLMN#b中的MB-SMF#b接收广播会话创建请求。
在一种可选的实现方式中，该会话创建请求消息携带广播业务#3在各个PLMN网络中广播业务标识的列表(list)。例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n。
在另一种可选的实现方式中，本申请中，广播业务#3在各个PLMN网络中广播业务标识的列表也可以预先配置在RAN上(该RAN，例如可以是，RAN#x)，此时AF便不用在会话创建请求消息中提供该列表。“预配置”可以理解为：RAN上本来就配置了广播业务#3在各个PLMN网络中广播业务标识的列表，因此，各个网络中请求建立广播会话时，可以只携带广播业务#3在该网络中的标识，不用携带整个列表；也可以理解为：RAN在第一次建立第一广播业务的会话时收到了预配置的广播业务#3在各个网络中的标识的列表，此时RAN可以存储该列表。因此，非首次(例如，第二次)请求建立广播业务#3的会话时，可以只携带广播业务#3在该网络中的标识，不用携带整个列表。以下不再赘述。
具体地，AF向PLMN#b中的MB-SMF#b发送会话创建立请求消息的方式可以参照方法500中的步骤503，此处不再赘述。
步骤703，PLMN#b中的MB-SMF#b获取广播业务#3的会话的QoS信息。
具体地，PLMN#b中的MB-SMF#b获取广播业务#3的会话的QoS信息的方式可以参照方法500中的步骤504，此处不再赘述。
步骤704，MB-SMB#b选择AMF#b，并向AMF#b发送会话开始请求(session start request)消息。
对应的，AMF#b接收会话开始请求消息。
具体地，PLMN#b中的MB-SMF#b选择AMF的方式可以参照方法500中的步骤505，此处不再赘述。
本实施例中，该会话开始请求消息中可以携带广播业务#3在各个PLMN网络中广播业务标识的列表。例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n。
该会话开始请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#3在PLMN#b中的标识TMGI#n、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
步骤705，AMF#b选择RAN#x(例如，基站)，并向RAN#x发送N2请求(N2 request)消息(第二消息的一例)。
对应的，RAN#x接收N2请求消息。
具体地，AMF#b选择RAN#x的方式可以参照方法500中的步骤506，此处不再赘述。
本实施例中，N2请求消息中携带广播业务#3在各个PLMN网络中广播业务标识的列表。例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n。
N2请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#3在PLMN#b中的标识TMGI#n、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
本实施例中，N2请求消息用于触发RAN为广播业务#3分配资源，换句话说，N2请求消息用于请求RAN#x为广播业务#3分配资源。也可以理解为，N2请求消息用于请求RAN #x建立广播业务#3对应的会话上下文。
步骤706，RAN#x基于N2请求消息为广播业务#3分配第一资源，并且建立广播业务#3对应的广播会话上下文。
其中，该广播会话上下文中包括广播业务#3在各个PLMN网络中广播业务标识的列表。例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n。
本实施例中，第一资源也可以理解为，用于向PLMN#b中UE发送广播业务#3的数据。
作为一个示例，RAN#x可以根据广播会话的QoS信息，分配对应的第一资源。例如，针对保证比特速率(guaranteed bit rate，GBR)的QoS流(flow)进行资源预留等等，具体地，RAN#x确定的广播业务#3的第一资源的信息可以包括：(1)多播接收的群组无线网络临时标识符(group-radio network tempory identity，G-RNTI)的信息。(2)广播业务#3对应的部分带宽(bandwidth part，BWP)的信息。例如，在所述BWP进行该业务的接收，根据BWP配置确定该BWP对应子载波间隔(sub-carrier space，SCS)，频域位置和循环前缀(cyclic prefix，CP)的长度。该BWP配置信息还包括物理下行控制信道(physical downlink control channel，PDCCH)检测的控制资源集(control resource set，COREST)配置信息，所述COREST配置信息指示了进行G-RNTI的PDCCH所在的时频资源。(3)广播业务#3的物理下行数据信道(physical downlink data channel，PDSCH)的加扰序列。也可以理解为，UE在解码该业务的PDSCH时采用该序列进行解扰；(4)G-RNTI的非连续接收(discontinuous reception，DRX)的参数，也可以理解为，UE使用该DRX参数进行G-RNTI检测。(5)解调参考信号的配置，也可以理解为，UE用该参考信号进行G-RNTI调度的PDSCH解调。(6)速率匹配参考信号的信息。
RAN#x建立的广播业务#3对应的广播会话上下文中还可以包括：广播业务#3在PLMN#b中的标识TMGI#n、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS上下文。
步骤706也可以理解为：RAN#x基于N2请求消息以及广播业务#3在各个PLMN网络中广播业务标识的列表，查找广播业务#3对应的广播会话上下文。RAN#x没有查到包含广播业务#3在各个PLMN网络中广播业务标识的列表的广播会话的上下文，则RAN#x确定还没有为广播业务#3分配过资源，需要在PLMN#b中为广播业务#3分配资源，并且建立广播业务#3对应的广播会话上下文。
步骤707，RAN#x向AMF#b发送N2响应消息。
例如，RAN#x向AMF#b发送N2 response消息用于响应AMF#b发送的N2 request消息。
步骤708，AMF#b向MB-SMF#b发送会话开始响应消息。
例如，AMF#b向MB-SMF#b发送session start response消息用于响应MB-SMF#b发送的session start request消息。
上述步骤702～步骤708为在PLMN#b中建立广播业务#3对应的广播会话以及为广播业务#3的数据分配第一资源的流程。下述步骤709～715为在PLMN#a中建立广播业务#3对应的广播会话以及使用在PLMN#b中为广播业务#3分配的第一资源向PLMN#a中的UE发送广播业务#3的数据的流程。
步骤709，AF向PLMN#a中的MB-SMF#a发送会话创建请求(session create request)消息(第四消息的一例)。
对应的，PLMN#a中的MB-SMF#a接收广播会话创建请求。
在一种可选的实现方式中，该广播会话创建请求消息携带广播业务#3在各个PLMN网络中广播业务标识的列表。例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n，等等。
在另一种可选的实现方式中，如果广播业务#3在各个PLMN网络中广播业务标识的列表预先已经配置在RAN(例如，RAN#x)上，或者；由于在PLMN#b中已经将该列表提供给RAN了，因此在PLMN#a中，该广播会话创建请求消息可以只携带广播业务#3在PLMN#a中的标识，例如TMGI#m，无须再将完整的列表提供给RAN。
具体地，AF向PLMN#a中的MB-SMF#a发送会话创建请求消息的方式可以参照方法500中的步骤510，此处不再赘述。
步骤710，PLMN#a中的MB-SMF#a获取广播业务#3的会话的QoS信息。
具体地，PLMN#a中的MB-SMF#a获取广播业务#3的会话的QoS信息可以参照方法500中的步骤511，此处不再赘述。
步骤711，MB-SMB#a选择AMF网元，并向AMF#a发送会话开始请求(session start request)消息(第三消息的一例)。
对应的，AMF#a接收会话开始请求消息。
具体地，PLMN#a中的MB-SMF#a选择AMF#a的方式可以参照方法500中的步骤512，此处不再赘述。
在一种可选的实现方式中，该广播会话开始请求消息携带广播业务#3在各个PLMN网络中广播业务标识的列表。例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n。
在另一种可选的实现方式中，如果广播业务#3在各个PLMN网络中广播业务标识的列表预先已经配置在RAN(例如，RAN#x)上，或者；由于在PLMN#b中已经将该列表提供给RAN了，因此在PLMN#a中，该广播会话开始请求消息可以只携带广播业务#3在PLMN#a中的标识，例如TMGI#m，无须再将完整的列表提供给RAN。
步骤712，AMF#a选择RAN#x(例如，基站)，并向RAN#x发送N2请求(N2 request)消息(第二消息的一例)。
对应的，RAN#x接收N2请求消息。
具体地，AMF#a选择RAN#x的方式可以参照方法500中的步骤513，此处不再赘述。
在一种可选的实现方式中，该N2请求包括广播业务#3在各个PLMN网络中广播业务标识的列表。例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n。
在另一种可选的实现方式中，该N2请求中携带广播业务#3在PLMN#a网络中广播业务标识。例如，在PLMN#a中的标识为TMGI#m。
N2请求消息中还可以携带以下信息中的一项或者多项：例如，广播业务#3在PLMN#b中的标识TMGI#n、广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表 ((tracking area，TA)list)、广播会话的QoS信息。
步骤713，RAN#x基于N2请求消息以及广播业务#3在各个PLMN网络中广播业务标识的列表或者在PLMN#a网络中广播业务标识，判断是否已经为广播业务#3分配过资源。若已经为广播业务#3分配过资源，则通过该资源发送PLMN#a中广播业务#3的数据；和/或，若RAN#x尚未为广播业务#3分配过资源，则RAN#x为广播业务#3分配资源。
其中，“资源”可以参考前述实施例中的相关描述，不再赘述。
在一种可选的实现方式中，RAN#x基于N2请求消息以及广播业务#3在各个PLMN网络中广播业务标识的列表，例如，在PLMN#a中的标识为TMGI#m，在PLMN#b中的标识为TMGI#n，查找广播业务#3对应的广播会话上下文。如果RAN#x确定在PLMN#b中的广播会话的上下文中已经包含了广播业务#3在各个PLMN网络中对应的广播业务标识的列表，则RAN#x确定已经为广播业务#3分配过资源，并在PLMN#b中的广播会话的上下文中查找到第一资源的信息。则RAN#x确定不在PLMN#a中建立广播业务#3对应的空口资源，并且不在PLMN#a中建立广播业务#3对应的上下文。即，RAN#x确定可以通过该PLMN#b中的第一资源发送PLMN#a中广播业务#3的数据。
在另一种可选的实现方式中，RAN#x基于N2请求消息以及广播业务#3在PLMN#a网络中广播业务标识TMGI#m，查找广播业务#3对应的广播会话上下文。如果RAN#x确定在PLMN#b中的广播会话的上下文中已经包含了广播业务#3在PLMN#a网络中广播业务标识TMGI#m。则RAN#x确定已经为广播业务#3分配过资源，并在PLMN#b中的广播会话的上下文中查找到第一资源的信息。则RAN#x确定不在PLMN#a中建立广播业务#3对应的空口资源，并且不在PLMN#a中建立广播业务#3对应的上下文。即，RAN#x确定可以通过该PLMN#b中的第一资源发送PLMN#a中广播业务#3的数据。
也可以理解为，RAN#x在查找广播业务#3对应的广播会话上下文时，如果发现该上下文中保存的广播业务#3在各个网络中的对应的广播业务标识与N2请求消息中携带的广播业务#3的标识有交集，则RAN#x确定已经为广播业务#3分配过资源并在PLMN#b中的广播会话的上下文中查找到第一资源的信息。则RAN#x确定不在PLMN#a中建立广播业务#3对应的空口资源，并且不在PLMN#a中建立广播业务#3对应的上下文。即，RAN#x确定可以通过该PLMN#b中的第一资源发送PLMN#a中广播业务#3的数据。
在又一种可选的实现方式中，如果在RAN#x在查找广播业务#3在各个PLMN网络中广播业务标识的列表或者在PLMN#a网络中广播业务标识之前，已经在PLMN#a中为广播业务#3分配了第二资源，并且在PLMN#a中为广播业务#3建立了上下文。待RAN#x查找之后确定之前在PLMN#b中已经为广播业务#3分配过资源，并在PLMN#b中的广播会话的上下文中查找到第一资源的信息。则RAN#x可以删除(“删除”也可以理解为“释放”)在PLMN#a中为广播业务#1分配的第二资源，并且删除在PLMN#a中为广播业务#1建立的上下文，或者，RAN#x可以不在第二资源上发送PLMN#a中的广播业务#3的数据，仍然利用PLMN#b中为广播业务#1分配的第一资源发送PLMN#a中的广播业务#3的数据。
步骤714，RAN#x向AMF#a发送N2响应消息。
例如，RAN#x向AMF#a发送N2 response消息用于响应AMF#a发送的N2 request消息。
步骤715，AMF#a向MB-SMF#a发送会话开始响应消息。
例如，AMF#a向MB-SMF#a发送session start response消息用于响应MB-SMF#a发送的session start request消息。
基于上述技术方案，通过给RAN发送广播业务在各个PLMN中的标识或者在PLMN#a中的标识，使得在不同运营商共享基站的场景下，RAN可以识别出相同的广播业务，从而使得RAN通过已经在PLMN#b中为该广播业务分配的资源，发送PLMN#a中的该广播业务的数据。也可以理解为，RAN可以对不同运营商的用户共享空口资源，这样可以节约RAN的传输资源，避免空口资源浪费。
图11是本申请提供的一种广播通信方法800的示意性流程图。假设本实施例中有两个PLMN(记为，PLMN#a和PLMN#b)，本实施例中以广播业务#4为例进行说明，该方法包括：
本实施例中假设：PLMN#a与PLMN#b配置了通用TMGI，这使得PLMN#a和PLMN#b的MB-SMF可以在AF请求TMGI时，提供通用TMGI。本申请中“通用TMGI”是指某个或某些TMGI可以被若干个(即，至少两个)PLMN网络共享。在原来的定义中，TMGI包含了PLMN ID信息以及PLMN内部的信息，也可以理解为，TMGI是在每个PLMN中是特定的(即，PLMN-specific)。然而，在本实施例中，假设各个PLMN可以共享TMGI(TMGI可以是PLMN-specific，也可以是non-PLMN specific，但是在各个PLMN中可以共享)。例如，针对广播业务#4，在PLMN#a中的TMGI与在PLMN#b中的TMGI相同，均为TMGI#q。
本实施例中还假设，存在“中央数据库”(第一网元的一例)，该中央数据库中存储了各个广播业务标识与通用TMGI之间的对应关系。例如，各个网络的MB-SMF可以将TMGI和广播业务标识的对应关系存储在UDM、UDR、NRF、NEF、PCF或者专用于多播/广播数据库中(此多播/广播数据库可以被多个PLMN共享)。以便于后续可以直接向中央数据库请求针对某个广播业务标识的通用TMGI。
步骤801，AF向PLMN#b中的MB-SMF#b发送请求消息#1(第三消息的一例)，请求消息#1中携带广播业务#4的标识(例如，广播业务#4的IP多播地址)，请求消息#1用于请求广播业务#4的TMGI。对应的，MB-SMF#b接收该请求消息。
具体地，请求消息#1可以用于触发MB-SMF#b向AF发送广播业务#4的TMGI。
例如，AF向MB-SMF#b发送TMGI分配请求(TMGI allocation request)消息，请求广播业务#4的TMGI。
步骤802，MB-SMF#b向中央数据库发送请求消息#2(第五消息的一例)，请求消息#2中携带广播业务#4的标识，获取广播业务#4的TMGI。
具体地，请求消息#2可以用于触发中央数据库发送广播业务#4的TMGI。
例如，请求消息#2可以是：会话创建请求(session create request)消息，请求查找广播业务#4的TMGI。此外，请求消息#2也可以是TMGI分配请求(TMGI allocation request)消息，或者是TMGI查找请求(TMGIquery request)消息，此处不予限定。
在一种可选的实现方式中，MB-SMF#b在分配TMGI时，MB-SMF#b可以向中央数据库查找广播业务#4的TMGI，获得广播业务#4对应的通用TMGI为TMGI#q。
在另一种可选的实现方式中，MB-SMF#b在分配TMGI时，MB-SMF#b可以向中央数据库查找广播业务#4的TMGI，如果MB-SMF#b没有查找到广播业务#4的TMGI，则MB-SMF#b为该广播业务#4分配TMGI(例如分配的TMGI为TMGI#q)，并存储在中央数据库中。
步骤803，中央数据库向MB-SMF#b发送请求消息#2的响应消息#2，该响应消息#2中携带广播业务#4的通用TMGI，TMGI#q。
步骤804，MB-SMF#b向AF发送请求消息#1的响应消息#1，该响应消息#1中携带广播业务#4的通用TMGI，例如，TMGI#q。
例如，该响应消息#1为TMGI分配响应(allocation request)消息。
步骤805，AF向PLMN#b中的MB-SMF#b发送会话创建请求(session create request)消息。对应的，PLMN#b中的MB-SMF#b接收广播会话创建请求。
其中，该会话创建请求消息携带广播业务#4对应的通用TMGI，例如，TMGI#q。
具体地，AF向MB-SMF#b发送的会话创建请求消息中还可以携带以下信息中一项或者多项：例如，广播业务#4的需求信息、广播的区域信息。
其中，广播业务#4的需求信息，例如，可以包括：广播业务#4的时延需求、广播业务#4的优先级需求、广播业务#4的带宽需求等等。或者，替代地，也可以是广播的策略信息.例如：5G服务质量(quality of service，QoS)标识符(identifier)(即，5QI)、分配和抢占优先级(allocation and retention priority，ARP)信息等等。
具体地，AF向PLMN#b中的MB-SMF#b发送会话创建请求消息的实现方式可以参照方法500中的步骤503，此处不再赘述。
步骤806，PLMN#b中的MB-SMF#b获取广播业务#4的会话的QoS信息。
具体地，PLMN#b中的MB-SMF#b获取广播业务#4的会话的QoS信息的方式可以参照方法500中的步骤504，此处不再赘述。
步骤807，MB-SMB#b选择AMF#b，并向AMF#b发送会话开始请求(session start request)消息。对应的，AMF#b接收会话开始请求消息。
具体地，PLMN#b中的MB-SMF#b选择AMF的方式可以参照方法500中的步骤505，此处不再赘述。
具体地，该会话开始请求消息中携带广播业务#4对应的通用TMGI，例如，TMGI#q。
该会话开始请求消息中还可以携带以下信息中的一项或者多项：广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
步骤808，AMF#b选择RAN#x(例如，基站)，并向RAN发送N2请求(N2 request)消息(第二消息的一例)。对应的，RAN#x接收N2请求消息。
具体地，AMF#b选择RAN#x的方式可以参照方法500中的步骤506，此处不再赘述。
本实施例中，N2请求消息中携带广播业务#4对应的通用TMGI，例如，TMGI#q。
N2请求消息中还可以携带以下信息中的一项或者多项：广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
本实施例中，N2请求消息用于触发RAN#x为广播业务#4分配资源，换句话说，N2请求消息用于请求RAN#x为广播业务#4分配资源。也可以理解为，N2请求消息用于请求RAN#x建立广播业务#4对应的会话上下文。
步骤809，RAN#x基于N2请求消息为广播业务#4分配第一资源，并且建立广播业务#4对应的广播会话上下文。
其中，该广播会话上下文中包括广播业务#4对应的通用TMGI，例如，TMGI#q。
其中，第一资源也可以理解为，用于向PLMN#b中UE发送广播业务#4的数据。
作为一个示例，RAN#x可以根据广播会话的QoS信息，分配对应的第一资源。例如，针对保证比特速率(guaranteed bit rate，GBR)的QoS流(flow)进行资源预留等等。具体地，RAN#x确定的广播业务#1的第一资源的信息可以包括：(1)多播接收的群组无线网络临时标识符(group-radio network tempory identity，G-RNTI)的信息。(2)广播业务#4对应的部分带宽(bandwidth part，BWP)的信息。例如，在所述BWP进行该业务的接收，根据BWP配置确定该BWP对应子载波间隔(sub-carrier space，SCS)，频域位置和循环前缀(cyclic prefix，CP)的长度。该BWP配置信息还包括物理下行控制信道(physical downlink control channel，PDCCH)检测的控制资源集(control resource set，COREST)配置信息，所述COREST配置信息指示了进行G-RNTI的PDCCH所在的时频资源。(3)广播业务#4的物理下行数据信道(physical downlink data channel，PDSCH)的加扰序列。也可以理解为，UE在解码该业务的PDSCH时采用该序列进行解扰；(4)G-RNTI的非连续接收(discontinuous reception，DRX)的参数，也可以理解为，UE使用该DRX参数进行G-RNTI检测。(5)解调参考信号的配置，也可以理解为，UE用该参考信号进行G-RNTI调度的PDSCH解调。(6)速率匹配参考信号的信息。
RAN#x建立的广播业务#4对应的广播会话上下文中还可以包括：广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS上下文。
步骤809，也可以理解为，RAN#x基于N2请求消息以及广播业务#4广播业务#4对应的通用TMGI：TMGI#q，查找广播业务#4对应的广播会话上下文。RAN#x没有查到包含TMGI#q的广播会话的上下文，则RAN#x确定还没有为广播业务#4分配过资源，需要在PLMN#b中为广播业务#4分配资源，并且建立广播业务#1对应的广播会话上下文。
步骤810，RAN#x向AMF#b发送N2响应消息。
例如，RAN#x向AMF#b发送N2 response消息用于响应AMF#b发送的N2 request消息。
步骤811，AMF#b向MB-SMF#b发送会话开始响应消息。
例如，AMF#b向MB-SMF#b发送session start response消息用于响应MB-SMF#b发送的session start request消息。
上述步骤801～步骤811为在PLMN#b中建立广播业务#4对应的广播会话以及为广播业务#4的数据分配第一资源的流程。下述步骤812～822为在PLMN#a中建立广播业务#4对应的广播会话以及使用在PLMN#b中为广播业务#4分配的第一资源向PLMN#a中的UE发送广播业务#4的数据的流程。
步骤812，AF向PLMN#a中的MB-SMF#a发送请求消息#3(第五消息的一例)，请求广播业务#4的TMGI。对应的，MB-SMF#a接收该请求消息。
具体地，请求消息#3可以用于触发MB-SMF#a向AF发送广播业务#4对应的通用TMGI。
例如，AF向MB-SMF#a发送TMGI分配请求(TMGI allocation request)消息，请求广播业务#4的TMGI。
步骤813，MB-SMF#a向中央数据库发送请求消息#4(第七消息的一例)，获取广播业务#4的TMGI。
具体地，MB-SMF#a获取广播业务#4的TMGI的方式可以参照步骤802，此处不再赘述。
步骤814，中央数据库向MB-SMF#a发送请求消息#4的响应消息#4，该响应消息#4中携带广播业务#4的通用TMGI，TMGI#q。
步骤815，MB-SMF#a向AF发送请求消息#3的响应消息#3，该响应消息#3中携带广播业务#4的通用TMGI，例如，TMGI#q。
例如，该响应消息#1为TMGI分配响应(allocation request)消息。
步骤816，AF向PLMN#a中的MB-SMF#a发送会话创建请求(session create request)消息。对应的，PLMN#a中的MB-SMF#a接收广播会话创建请求。
具体地，该会话创建请求消息携带广播业务#4对应的通用TMGI，例如，TMGI#q。
具体地，AF向MB-SMF#a发送的会话创建请求消息中还可以携带以下信息中一项或者多项：例如，广播业务#4的需求信息、广播的区域信息。
其中，广播业务#4的需求信息，例如，可以包括：广播业务#4的时延需求、广播业务#4的优先级需求、广播业务#4的带宽需求等等。或者，替代地，也可以是广播的策略信息.例如：5G服务质量(quality of service，QoS)标识符(identifier)(即，5QI)、分配和抢占优先级(allocation and retention priority，ARP)信息等等。
具体地，AF向PLMN#a中的MB-SMF#a发送会话创建请求消息的实现方式可以参照方法500中的步骤510，此处不再赘述。
步骤817，PLMN#a中的MB-SMF#a获取广播业务#4的会话的QoS信息。
具体地，MB-SMF#a获取广播业务#4的会话的QoS信息的方式可以参照方法500中的步骤511，此处不再赘述。
步骤818，MB-SMB#a选择AMF#a网元，并向AMF#a发送会话开始请求(session start request)消息(第三消息的一例)。对应的，AMF#a接收会话开始请求消息。
具体地，MB-SMB#a选择AMF#a的方式可以参照方法500中步骤512。
具体地，该会话开始请求消息中携带广播业务#4的通用TMGI，例如，TMGI#q。
该会话开始请求消息中还可以携带以下信息中的一项或者多项：广播的区域信息(例如，小区列表(cell list)的信息、跟踪区列表((tracking area，TA)list)、广播会话的QoS信息。
步骤819，AMF#a选择RAN#x(例如，基站)，并向RAN发送N2请求(N2 request)消息(第一消息的一例)。
对应的，RAN接收N2请求消息。
具体地，AMF#a选择RAN#x方式可以参照方法500中的步骤513。
其中，该会话开始请求消息中携带广播业务#4的通用TMGI，例如，TMGI#q。
其中，AF向MB-SMF#a发送的会话创建请求消息中还可以携带以下信息中一项或者多项：例如，广播业务#4的需求信息、广播的区域信息。
其中，广播业务#4的需求信息，例如，可以包括：广播业务#4的时延需求、广播业务#4的优先级需求、广播业务#4的带宽需求等等。或者，替代地，也可以是广播的策略信息.例如：5G服务质量(quality of service，QoS)标识符(identifier)(即，5QI)、分配和抢占优先级(allocation and retention priority，ARP)信息等等。
步骤820，RAN#x基于N2请求消息以及广播业务#4的通用TMGI判断是否已经为广播业务#4分配过资源。若已经为广播业务#4分配过资源，则通过该资源发送PLMN#a中广播业务#4的数据；和/或，若RAN#x尚未为广播业务#4分配过资源，则RAN#x为广播业务#4分配资源。
在一种可选的实现方式中，由于在PLMN#b中已经为第一广播业务(即，TMGI#q标识的广播业务)分配了第一资源，此时，RAN#x基于N2请求消息以及广播业务#4的通用TMGI，例如，TMGI#q，确定可以通过该PLMN#b中的第一资源发送PLMN#a中广播业务#4的数据。换句话说，本实施例中，由于RAN#x在PLMN#b中与在PLMN#a接收到的均为TMGI#q，因此，RAN#x无须查找第一广播业务对应的广播会话上下文，便可以直接利用在PLMN#b中的第一资源发送PLMN#a中广播业务#4的数据。
步骤821，RAN#x向AMF#a发送N2响应消息。
例如，RAN#x向AMF#a发送N2 response消息用于响应AMF#a发送的N2 request消息。
步骤822，AMF#a向MB-SMF#a发送会话开始响应消息。
例如，AMF#a向MB-SMF#a发送session start response消息用于响应MB-SMF#a发送的session start request消息。
基于上述技术方案，通过给RAN发送广播业务在各个网络中的通用TMGI，使得在不同运营商共享基站的场景下，RAN可以识别出相同的广播业务，从而使得RAN通过已经在PLMN#b中为该广播业务分配的资源，发送PLMN#a中的该广播业务的数据。也可以理解为，RAN可以对不同运营商的用户共享空口资源，这样可以节约RAN的传输资源，避免空口资源浪费。
可以理解，本申请实施例中的图4至图8中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图4至图8的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，本申请中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还可以理解，在本申请的各实施例中的各种数字序号的大小并不意味着执行顺序的先后，仅为描述方便进行的区分，不应对本申请实施例的实施过程构成任何限定。例如，方法500中，步骤503可以与步骤510可以同时进行，即AF可以同时接收PLMN#b中的MB-SMF#b以及PLMN#a中的MB-SMF#a发送广播业务的会话创建请求。
本申请中的“广播业务”、“广播会话”，也可以理解为“多播业务”以及“多播会话”，上述技术方案仅仅是以“广播业务”、“广播会话”为例进行说明，不予限定。
还可以理解，在本申请的各实施例中涉及到一些消息名称，其命名不对本申请实施例的保护范围造成限定。
应该理解，本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
可以理解，在本申请中，“在…情况下”、“若”以及“如果”均指在某种客观情况下装置会做出相应的处理，并非是限定时间，且也不要求装置实现时一定要有判断的动作，也不意味着存在其它限定。
可以理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
上述主要从各个节点之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个节点，例如无线接入网设备、多播/广播会话管理功能网元、应用管理功能网元或第一网元，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对无线接入网设备以及涉及的各个核心网网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图12是本申请实施例提供的通信装置100的示意性框图。如图所示，该装置100可以包括：收发单元110和处理单元120。
在一种可能的设计中，该装置100可以是上文方法实施例中的无线接入网设备，也可以是用于实现上文方法实施例中无线接入网设备的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法100、方法500、方法600、方法700、方法800中的无线接入网设备，该装置100可以执行本申请实施例的方法100、方法500、方法600、方法700、方法800中的无线接入网设备所对应的步骤。
在一种实现方式中，收发单元110用于接收来自第一接入和移动管理功能网元的第一消息，所述第一消息携带第一广播业务的标识，所述第一消息用于触发为所述第一广播业务分配资源；处理单元120用于根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，所述第一资源用于向所述第二网络中的终端设备发送所述第一广播业务的数据；收发单元110还用于通过所述第一资源，向所述第一网络中的终端设备发送所述第一广播业务的数据。其中，所述装置由至少两个网络共享，所述至少两个网络包括第一网络和第二网络，所述第一接入和移动管理功能网元位于所述第一网络中。
可选的，所述第一广播业务的标识包括第一标识和/或第二标识，其中，所述第一标识包括以下至少一项：所述第一广播业务的全球唯一标识；所述第一广播业务在所述至少两个网络中的每个网络中的标识，或者；所述第一广播业务的临时移动组标识，所述临时移动组标识由所述至少两个网络共享；所述第二标识包括：所述第一广播业务在所述第一网络中的标识。
可选的，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。
可选的，在所述第一广播业务的标识为所述第一广播业务的全球唯一标识的情况下，所述处理单元120用于根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：所述处理单元120用于根据所述第一广播业务的全球唯一标识，查找所述第一广播业务对应的广播会话上下文；所述处理单元120用于根据所述广播会话上下文，获得所述第一资源的信息；其中，所述广播会话上下文包括所述第一广播业务的全球唯一标识以及所述第一资源的信息。
可选的，在所述第一广播业务的标识为所述第一广播业务在所述至少两个网络中的每个网络中的标识的情况下，所述处理单元120用于根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：所述处理单元120用于根据所述第一广播业务在所述至少两个网络中的每个网络中的标识，查找所述第一广播业务对应的广播会话上下文；所述处理单元120用于根据所述广播会话上下文，获得所述第一资源的信息；其中，所述广播会话上下文包括所述第一广播业务在所述至少两个网络中的每个网络中的标识以及所述第一资源的信息。
可选的，在所述第一广播业务的标识包括所述第二标识情况下，所述处理单元110用于根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：所述处理单元120用于根据预配置的所述第一广播业务在所述第一网络中的标识与所述第一广播业务在所述第二网络中的标识的对应关系，以及所述第二标识，获得所述第一广播业务在所述第二网络中的标识；所述处理单元120用于根据所述第一广播业务在所述第二网络中的标识，查找所述第一广播业务对应的广播会话上下文；所述处理单元120用于根据所述广播会话上下文，获得所述第一资源的信息；
可选的，在所述第一广播业务的标识包括所述第一标识的情况下，所述收发单元110还用于接收来自第二接入和移动管理功能网元的第二消息，所述第二消息携带所述第一标识，所述第二消息用于触发为所述第一广播业务分配资源，所述第二接入和移动管理功能 网元位于所述至少两个网络中的第二网络；所述处理单元120用于根据所述第二消息，为所述第一广播业务分配所述第一资源；所述处理单元120用于建立所述第一广播业务对应的广播会话上下文；其中，所述广播会话上下文包括所述第一标识以及所述第一资源的信息。
在一种可能的设计中，该装置100可以是上文方法实施例中的多播/广播会话管理功能网元，也可以是用于实现上文方法实施例中多播/广播会话管理功能网元的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法200、方法500、方法600、方法700、方法800中的多播/广播会话管理功能网元，该装置100可以执行本申请实施例的方法200、方法500、方法600、方法700、方法800中的多播/广播会话管理功能网元所对应的步骤。
在一种实现方式中，收发单元110用于接收第一广播业务的标识；所述收发单元110还用于发送所述第一广播业务的标识。
可选的，所述第一广播业务的标识包括第一标识，所述第一标识包括以下至少一项：所述第一广播业务的全球唯一标识；所述第一广播业务在至少两个网络中的每个网络中的标识，或者；所述第一广播业务的临时移动组标识，所述临时移动组标识由至少两个网络共享。
可选的，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。
可选的，所述收发单元110用于接收第一广播业务的标识，包括：所述收发单元110用于接收来自应用功能网元的第一广播业务的标识。
可选的，在所述收发单元110接收来自应用功能网元的第一广播业务的标识之前，所述收发单元110还用于接收第三消息，所述第三消息携带所述第一广播业务的标识，所述第三消息用于触发所述装置发送所述第一广播业务的临时移动组标识；所述处理单元120用于根据所述第三消息，从第一网元获取所述临时移动组标识，或者；所述处理单元120用于根据所述第三消息，为所述第一广播业务分配所述临时移动组标识；所述收发单元110用于发送所述临时移动组标识。
可选的，所述第一网元为：统一数据管理网元、统一数据存储网元、网络存储功能网元、网络发现功能网元、策略控制功能网元、或者，多播/广播的数据库，其中，所述多播/广播的数据库由至少两个网络共享。
可选的，所述收发单元110用于接收第一广播业务的标识，包括：所述收发单元110用于接收第一广播业务的标识，其中，所述第一广播业务的标识为所述第一广播业务的全球唯一标识。
可选的，在所述收发单元110接收第一广播业务的标识之前，所述收发单元110还用于发送第四消息，所述第四消息用于请求所述第一广播业务的会话建立或者修改，所述第四消息携带第一指示信息，所述第一指示信息用于触发所述处理单元120检测所述第一广播业务的标识。
在一种可能的设计中，该装置100可以是上文方法实施例中的应用功能网元，也可以是用于实现上文方法实施例中应用功能网元的功能的芯片。应理解，该装置100可对应于 根据本申请实施例的方法300、方法500、方法600、方法700、方法800中的应用功能网元，该装置100可以执行本申请实施例的方法300、方法500、方法600、方法700、方法800中的应用功能网元所对应的步骤。
在一种实现方式中，处理单元120用于获得第一广播业务的标识；收发单元110用于发送所述第一广播业务的标识。
可选的，所述第一广播业务的标识包括第一标识，所述第一标识包括以下至少一项：所述第一广播业务的全球唯一标识；所述第一广播业务在至少两个网络中的每个网络中的标识，或者；所述第一广播业务的临时移动组标识，所述临时移动组标识由至少两个网络共享。
可选的，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。
可选的，所述处理单元120用于获得第一广播业务的标识，包括：所述处理单元120用于生成所述第一广播业务的全球唯一标识。
可选的，所述至少两个网络包括第一网络和第二网络，所述处理单元120用于获得第一广播业务的标识，包括：所述处理单元120用于指示所述收发单元110从所述第一网络中的第一多播/广播会话管理功能网元接收所述第一广播业务在所述第一网络中的标识；所述处理单元120用于指示所述收发单元110从所述第二网络中的第二多播/广播会话管理功能网元接收所述第一广播业务在所述第二网络中的标识。
所述处理单元120用于获得第一广播业务的标识，包括：所述处理单元120用于从所述多播/广播会话管理功能网元获得所述临时移动组标识。
在一种可能的设计中，该装置100可以是上文方法实施例中的第一网元，也可以是用于实现上文方法实施例中第一网元的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法400中的第一网元(例如，中央数据库)、方法800中的中央数据库，该装置100可以执行本申请实施例的方法400中的第一网元的功能网元所对应的步骤，也可以执行方法800中的中央数据库所对应的步骤。
在一种实现方式中，收发单元110用于接收第五消息，所述第五消息携带第一广播业务的标识，所述第五消息用于触发所述装置发送所述第一广播业务的临时移动组标识；所述处理单元120用于根据所述第五消息，指示所述收发单元110发送所述第一广播业务的临时移动组标识。
可选的，所述收发单元110还用于从多播/广播会话管理功能网元接收所述第一广播业务的标识与所述临时移动组标识之间的对应关系。
可选的，所述临时移动组标识由至少两个网络共享。
可选的，所述第一网元为：统一数据管理网元、统一数据存储网元、网络存储功能网元、网络发现功能网元、策略控制功能网元、或者，多播/广播的数据库，其中，所述多播/广播的数据库由至少两个网络共享。
还应理解，这里的装置100以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或 多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置100可以具体为上述实施例中的第一终端设备，可以用于执行上述各方法实施例中与第一终端设备对应的各个流程和/或步骤，或者，装置100可以具体为上述实施例中的第二终端设备，可以用于执行上述各方法实施例中与第二终端设备对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述各个方案的装置100具有实现上述方法中无线接入网设备所执行的相应步骤的功能，或者，上述各个方案的装置100具有实现上述方法中多播/广播会话管理功能网元、或者应用功能网元、或者第一网元所执行的相应步骤的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元110还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
需要指出的是，图12中的装置可以是前述实施例中的网元或设备，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
图13是本申请实施例提供的通信装置200的示意性框图。如图所示，该装置200包括：至少一个处理器220。该处理器220与存储器耦合，用于执行存储器中存储的指令，以发送信号和/或接收信号。可选地，该设备200还包括存储器230，用于存储指令。可选的，该设备200还包括收发器210，处理器220控制收发器210发送信号和/或接收信号。
应理解，上述处理器220和存储器230可以合成一个处理设备，处理器220用于执行存储器230中存储的程序代码来实现上述功能。具体实现时，该存储器230也可以集成在处理器220中，或者独立于处理器220。
还应理解，收发器210可以包括收发器(或者称，接收机)和发射器(或者称，发射机)。收发器还可以进一步包括天线，天线的数量可以为一个或多个。收发器210有可以是通信接口或者接口电路。
具体地，该设备200中的收发器210可以对应于设备100中的收发单元110，该设备200中的处理器220可对应于设备200中的处理单元120。
作为一种方案，该装置200用于实现上文各个方法实施例中由无线接入网设备执行的操作。
例如，处理器220用于执行存储器230存储的计算机程序或指令，以实现上文各个方法实施例中无线接入网设备的相关操作。例如，图4所示实施例中的无线接入网设备执行的方法100，或图8至图11中任意一个所示实施例中的无线接入网设备执行的方法。
作为另一种方案，该装置200用于实现上文各个方法实施例中由各个核心网网元执行 的操作。
例如，处理器220用于执行存储器230存储的计算机程序或指令，以实现上文各个方法实施例中多播/广播会话管理功能网元、应用功能网元、第一网元的相关操作。例如，图5至图11中任意一个所示实施例中的多播/广播会话管理功能网元、应用功能网元、第一网元执行的方法。
应理解，各收发器、处理器执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application-specific integrated circuit，ASIC)、现场可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch-link DRAM，SLDRAM)和直接内存总线随机存取存储器(direct ram-bus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品上存储有计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行方法100、方法500～方法800实施例中任意一个实施例中由无线接入网设备或RAN执行的方法。
例如，该计算机程序代码被计算机执行时，使得该计算机可以实现上述方法200、方法500～方法800实施例中由多播/广播会话管理功能网元执行的方法。
又例如，该计算机程序代码被计算机执行时，使得该计算机可以实现上述方法300、方法500～方法800实施例中由应用功能网元执行的方法。
再例如，该计算机程序代码被计算机执行时，使得该计算机可以实现上述方法400、方法500～方法800实施例中由第一网元执行的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述实施例中由无线接入网设备、多播/广播会话管理功能网元、应用功能网元或者第一网元执行的方法。
根据本申请实施例提供的方法，本申请还提供一种通信系统，其包括无线接入网设备和第一接入和移动管理功能网元，所述无线接入网设备，用于执行方法100、方法500～方法800中实施例中的任意一个实施例中无线接入网设备或RAN所执行的方法；所述第一接入和移动管理功能网元，用于向所述无线接入网设备发送第一消息，所述第一消息携带第一广播业务的标识，所述第一消息用于触发为所述第一广播业务分配资源；其中，所述无线接入网设备由至少两个网络共享，所述至少两个网络包括第一网络和第二网络，所述第一接入和移动管理功能网元位于所述第一网络中。
在一种可选的实现方式中，所述系统还包括：多播/广播会话管理功能网元，所述多播/广播会话管理功能网元，用于执行方法200、方法500～方法800中实施例中任意一个实施例中多播/广播会话管理功能网元所执行的方法。
在一种可选的实现方式中，所述系统还包括：应用功能网元；所述应用功能网元，用于执行方法300、方法500～方法800中实施例中任意一个实施例中应用功能网元所执行的方法。
在一种可选的实现方式中，所述系统还包括第一网元(例如，中央数据库)，所述第一网元，用于方法400、执行方法800实施例中任意一个实施例中第一网元(例如，中央数据库)所执行的方法。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程设备。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指 令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中，由相应的模块或单元执行相应的步骤，例如收发单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所述领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、设备和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各 个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种广播通信方法，其特征在于，包括：
    无线接入网设备接收来自第一接入和移动管理功能网元的第一消息，所述第一消息携带第一广播业务的标识，所述第一消息用于触发为所述第一广播业务分配资源，其中，所述无线接入网设备由至少两个网络共享，所述至少两个网络包括第一网络和第二网络，所述第一接入和移动管理功能网元位于所述第一网络中；
    所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，所述第一资源用于向所述第二网络中的终端设备发送所述第一广播业务的数据；
    所述无线接入网设备通过所述第一资源，向所述第一网络中的终端设备发送所述第一广播业务的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一广播业务的标识包括第一标识和/或第二标识，其中，所述第一标识包括以下至少一项：
    所述第一广播业务的全球唯一标识；
    所述第一广播业务在所述至少两个网络中的每个网络中的标识，或者；
    所述第一广播业务的临时移动组标识，所述临时移动组标识由所述至少两个网络共享；
    所述第二标识包括：所述第一广播业务在所述第一网络中的标识。
  3. 根据权利要求2所述的方法，其特征在于，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。
  4. 根据权利要求2或3所述的方法，其特征在于，在所述第一广播业务的标识为所述第一广播业务的全球唯一标识的情况下，所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：
    所述无线接入网设备根据所述第一广播业务的全球唯一标识，查找所述第一广播业务对应的广播会话上下文；
    所述无线接入网设备根据所述广播会话上下文，获得所述第一资源的信息；
    其中，所述广播会话上下文包括所述第一广播业务的全球唯一标识以及所述第一资源的信息。
  5. 根据权利要求2所述的方法，其特征在于，在所述第一广播业务的标识为所述第一广播业务在所述至少两个网络中的每个网络中的标识的情况下，所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：
    所述无线接入网设备根据所述第一广播业务在所述至少两个网络中的每个网络中的标识，查找所述第一广播业务对应的广播会话上下文；
    所述无线接入网设备根据所述广播会话上下文，获得所述第一资源的信息；
    其中，所述广播会话上下文包括所述第一广播业务在所述至少两个网络中的每个网络中的标识以及所述第一资源的信息。
  6. 根据权利要求2所述的方法，其特征在于，在所述第一广播业务的标识包括所述第 二标识情况下，所述无线接入网设备根据所述第一广播业务的标识，获得所述第一广播业务对应的第一资源的信息，包括：
    所述无线接入网设备根据预配置的所述第一广播业务在所述第一网络中的标识与所述第一广播业务在所述第二网络中的标识的对应关系，以及所述第二标识，获得所述第一广播业务在所述第二网络中的标识；
    所述无线接入网设备根据所述第一广播业务在所述第二网络中的标识，查找所述第一广播业务对应的广播会话上下文；
    所述无线接入网设备根据所述广播会话上下文，获得所述第一资源的信息；
    其中，所述广播会话上下文包括所述第二标识以及所述第一资源的信息。
  7. 根据权利要求2至6中任一项所述的方法，其特征在于，在所述第一广播业务的标识包括所述第一标识的情况下，所述方法还包括：
    所述无线接入网设备接收来自第二接入和移动管理功能网元的第二消息，所述第二消息携带所述第一标识，所述第二消息用于触发为所述第一广播业务分配资源，所述第二接入和移动管理功能网元位于所述至少两个网络中的第二网络；
    所述无线接入网设备根据所述第二消息，为所述第一广播业务分配所述第一资源；
    所述无线接入网设备建立所述第一广播业务对应的广播会话上下文；
    其中，所述广播会话上下文包括所述第一标识以及所述第一资源的信息。
  8. 一种广播通信方法，其特征在于，包括：
    多播/广播会话管理功能网元接收第一广播业务的标识；
    所述多播/广播会话管理功能网元向接入和移动管理功能网元发送所述第一广播业务的标识。
  9. 根据权利要求8所述的方法，其特征在于，所述第一广播业务的标识包括第一标识，所述第一标识包括以下至少一项：
    所述第一广播业务的全球唯一标识；
    所述第一广播业务在至少两个网络中的每个网络中的标识，或者；
    所述第一广播业务的临时移动组标识，所述临时移动组标识由至少两个网络共享。
  10. 根据权利要求9所述的方法，其特征在于，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。
  11. 根据权利要求8至10中任一项所述的方法，其特征在于，所述多播/广播会话管理功能网元接收第一广播业务的标识，包括：
    所述多播/广播会话管理功能网元接收来自应用功能网元的第一广播业务的标识。
  12. 根据权利要求11所述的方法，其特征在于，在所述多播/广播会话管理功能网元接收来自应用功能网元的第一广播业务的标识之前，所述方法还包括：
    所述多播/广播会话管理功能网元接收来自所述应用功能网元的第三消息，所述第三消息携带所述第一广播业务的标识，所述第三消息用于触发所述多播/广播会话管理功能网元向所述应用功能网元发送所述第一广播业务的临时移动组标识；
    所述多播/广播会话管理功能网元根据所述第三消息，从第一网元获取所述临时移动组 标识，或者；所述多播/广播会话管理功能网元根据所述第三消息，为所述第一广播业务分配所述临时移动组标识；
    所述多播/广播会话管理功能网元向所述应用功能网元发送所述临时移动组标识。
  13. 根据权利要求12所述的方法，其特征在于，所述第一网元为：统一数据管理网元、统一数据存储网元、网络存储功能网元、网络发现功能网元、策略控制功能网元、或者，多播/广播的数据库，其中，所述多播/广播的数据库由至少两个网络共享。
  14. 根据权利要求8至10中任一项所述的方法，其特征在于，所述多播/广播会话管理功能网元接收第一广播业务的标识，包括：
    所述多播/广播会话管理功能网元接收来自多播/广播用户面功能网元的第一广播业务的标识，其中，所述第一广播业务的标识为所述第一广播业务的全球唯一标识。
  15. 根据权利要求14所述的方法，其特征在于，在所述多播/广播会话管理功能网元接收来自多播/广播用户面功能网元的第一广播业务的标识之前，所述方法还包括：
    所述多播/广播会话管理功能网元向所述多播/广播用户面功能网元发送第四消息，所述第四消息用于请求所述第一广播业务的会话建立或者修改，所述第四消息携带第一指示信息，所述第一指示信息用于触发所述多播/广播用户面功能网元检测所述第一广播业务的标识。
  16. 一种广播通信方法，其特征在于，包括：
    应用功能网元获得第一广播业务的标识；
    所述应用功能网元向多播/广播会话管理功能网元发送所述第一广播业务的标识。
  17. 根据权利要求16所述的方法，其特征在于，所述第一广播业务的标识包括第一标识，所述第一标识包括以下至少一项：
    所述第一广播业务的全球唯一标识；
    所述第一广播业务在至少两个网络中的每个网络中的标识，或者；
    所述第一广播业务的临时移动组标识，所述临时移动组标识由至少两个网络共享。
  18. 根据权利要求17所述的方法，其特征在于，所述第一广播业务的全球唯一标识包括所述第一广播业务的互联网协议IP多播地址。
  19. 根据权利要求17或18所述的方法，其特征在于，所述应用功能网元获得第一广播业务的标识，包括：
    所述应用功能网元生成所述第一广播业务的全球唯一标识。
  20. 根据权利要求17所述的方法，其特征在于，所述至少两个网络包括第一网络和第二网络，所述应用功能网元获得第一广播业务的标识，包括：
    所述应用功能网元从所述第一网络中的第一多播/广播会话管理功能网元接收所述第一广播业务在所述第一网络中的标识；
    所述应用功能网元从所述第二网络中的第二多播/广播会话管理功能网元接收所述第一广播业务在所述第二网络中的标识。
  21. 根据权利要求17所述的方法，其特征在于，所述应用功能网元获得第一广播业务的标识，包括：
    所述应用功能网元从所述多播/广播会话管理功能网元获得所述临时移动组标识。
  22. 一种广播通信方法，其特征在于，包括：
    第一网元从多播/广播会话管理功能网元接收第五消息，所述第五消息携带第一广播业务的标识，所述第五消息用于触发所述第一网元发送所述第一广播业务的临时移动组标识；
    所述第一网元根据所述第五消息，向所述多播/广播会话管理功能网元发送所述第一广播业务的临时移动组标识。
  23. 根据权利要求22所述的方法，其特征在于，所述方法还包括：
    所述第一网元从所述多播/广播会话管理功能网元接收所述第一广播业务的标识与所述临时移动组标识之间的对应关系。
  24. 根据权利要求22或23所述的方法，其特征在于，所述临时移动组标识由至少两个网络共享。
  25. 根据权利要求22至24任一项所述的方法，其特征在于，所述第一网元为：统一数据管理网元、统一数据存储网元、网络存储功能网元、网络发现功能网元、策略控制功能网元、或者，多播/广播的数据库，其中，所述多播/广播的数据库由至少两个网络共享。
  26. 一种广播通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至25中任一项所述的方法。
  27. 根据权利要求27所述的装置，其特征在于，所述装置还包括所述存储器。
  28. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至25中任意一项所述的方法。
  29. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至25中任一项所述的方法的指令。
  30. 一种广播通信系统，其特征在于，包括：无线接入网设备和第一接入和移动管理功能网元；
    所述无线接入网设备，用于执行如权利要求1至7中任一项所述的方法；
    所述第一接入和移动管理功能网元，用于向所述无线接入网设备发送第一消息，所述第一消息携带第一广播业务的标识，所述第一消息用于触发为所述第一广播业务分配资源；
    其中，所述无线接入网设备由至少两个网络共享，所述至少两个网络包括第一网络和第二网络，所述第一接入和移动管理功能网元位于所述第一网络中。
  31. 根据权利要求30所述的通信系统，其特征在于，所述系统还包括：多播/广播会话管理功能网元；
    所述多播/广播会话管理功能网元，用于执行如权利要求8至15中任一项所述的方法。
  32. 根据权利要求30或31所述的通信系统，其特征在于，所述系统还包括：应用功能网元；
    所述应用功能网元，用于执行如权利要求16至21中任一项所述的方法。
  33. 根据权利要求30至32中任一项所述的通信系统，其特征在于，所述系统还包括： 第一网元；
    所述第一网元，用于执行如权利要求22至25中任一项所述的方法。
PCT/CN2023/070401 2022-01-12 2023-01-04 一种广播通信方法和装置 WO2023134516A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23739860.7A EP4447577A1 (en) 2022-01-12 2023-01-04 Broadcast communication method and apparatus
AU2023206483A AU2023206483A1 (en) 2022-01-12 2023-01-04 Broadcast communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210030311.7 2022-01-12
CN202210030311.7A CN116489799A (zh) 2022-01-12 2022-01-12 一种广播通信方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/762,686 Continuation US20240357623A1 (en) 2022-01-12 2024-07-03 Broadcast communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2023134516A1 true WO2023134516A1 (zh) 2023-07-20

Family

ID=87218218

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/070401 WO2023134516A1 (zh) 2022-01-12 2023-01-04 一种广播通信方法和装置

Country Status (4)

Country Link
EP (1) EP4447577A1 (zh)
CN (1) CN116489799A (zh)
AU (1) AU2023206483A1 (zh)
WO (1) WO2023134516A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112449311A (zh) * 2019-08-31 2021-03-05 华为技术有限公司 通信方法、设备及系统
WO2021163859A1 (zh) * 2020-02-17 2021-08-26 华为技术有限公司 通信方法及通信装置
CN113660616A (zh) * 2020-04-10 2021-11-16 华为技术有限公司 一种组播/广播业务的通信方法和装置
CN113873443A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 通信方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112449311A (zh) * 2019-08-31 2021-03-05 华为技术有限公司 通信方法、设备及系统
WO2021163859A1 (zh) * 2020-02-17 2021-08-26 华为技术有限公司 通信方法及通信装置
CN113660616A (zh) * 2020-04-10 2021-11-16 华为技术有限公司 一种组播/广播业务的通信方法和装置
CN113873443A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 通信方法及装置

Also Published As

Publication number Publication date
EP4447577A1 (en) 2024-10-16
AU2023206483A1 (en) 2024-08-01
CN116489799A (zh) 2023-07-25

Similar Documents

Publication Publication Date Title
US8983475B2 (en) System and method for partner network sharing architecture
JP2019520765A (ja) 無線通信システムにおけるネットワークスライスベースのｎｒのためのセル特定手順を実行する方法及び装置
CN106572516A (zh) 一种网络切片选择方法、终端设备及网络设备
EP4181588A1 (en) Method for terminal to access public and private networks and communication apparatus
CN111918279B (zh) 一种寻址方法、通信装置及系统
CN113508639B (zh) 一种用于中继通信的方法和装置
WO2022170798A1 (zh) 确定策略的方法和通信装置
CN116508392A (zh) 接入方式选择方法、终端设备和网络设备
WO2023051430A1 (zh) 通信的方法和装置
WO2023080057A1 (en) Method of access and mobility management function (amf) apparatus, method of next generation-radio access network (ng-ran) node, method of user equipment (ue), method of master node (mn), amf apparatus, ng-ran node, ue, and mn
US10057871B2 (en) Data transmission method and base station
WO2022170558A1 (zh) 选择网络的方法、终端设备和网络设备
WO2023134516A1 (zh) 一种广播通信方法和装置
CN115567991A (zh) 传输方式切换的方法和相关装置
US20240357623A1 (en) Broadcast communication method and apparatus
JP2022502979A (ja) パラメータ設定方法、端末装置及び記憶媒体
WO2023061167A1 (zh) 通信方法及装置
WO2023051428A1 (zh) 信息传输的方法和装置
WO2023103575A1 (zh) 组播/广播通信的方法与相关装置
US20240340709A1 (en) Communication method and apparatus
WO2022183317A1 (zh) 一种获取切片信息的方法和终端设备
WO2024168599A1 (en) Techniques for multicast reception by user equipment in an inactive state during mobility
CN115915091A (zh) 通信的方法和装置
CN116233957A (zh) 一种数据传输的方法和通信装置
CN115884152A (zh) 通信的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23739860

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023739860

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 202427053325

Country of ref document: IN

Ref document number: AU2023206483

Country of ref document: AU

ENP Entry into the national phase

Ref document number: 2023739860

Country of ref document: EP

Effective date: 20240710

ENP Entry into the national phase

Ref document number: 2023206483

Country of ref document: AU

Date of ref document: 20230104

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE