A broadcast communication method and apparatus

Abstract

The embodiment of the present application provides a broadcast communication method and device, wherein the wireless access network device can identify the same first broadcast service in different networks by sending the identification of the first broadcast service to the wireless access network device. The wireless access network device can send the data of the broadcast service in the first network through the resource allocated for the first broadcast service in the second network. In other words, in the present application, the wireless access network device can share the air interface resource for the same broadcast service in different networks, so that the transmission resource of the wireless access network device is saved, and the waste of the air interface resource is avoided.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a broadcast communication method and apparatus. Background Technology

[0002] Currently, to reduce costs when deploying networks, different operators share base stations but retain their own core networks, such as in a multi-operator core network (MOCN) scenario. In an MOCN scenario, broadcast messages contain information about the public land mobile network (PLMN). For example, a base station broadcasts information about a cell, which includes information about the PLMN to which that cell belongs.

[0003] However, in the scenarios where different operators share base stations, there are instances where the core networks of different operators and the shared base stations repeatedly transmit certain broadcast services (e.g., weather forecasts, high-precision map updates), resulting in a waste of transmission resources. How to reduce this waste of transmission resources has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a broadcast communication method that can reduce the waste of transmission resources.

[0005] In a first aspect, a broadcast communication method is provided, which can be performed by a wireless access network device (e.g., a base station) or by a component of the wireless access network device (e.g., a chip or circuit), without limitation.

[0006] The method includes: a radio access network device receiving a first message from a first access and mobility management function (MLM) network element, the first message carrying an identifier of a first broadcast service, the first message being used to trigger resource allocation for the first broadcast service, wherein the radio access network device is shared by at least two networks, the at least two networks including a first network and a second network, and the first MLM network element being located in the first network; the radio access network device obtaining information about a first resource corresponding to the first broadcast service based on the identifier of the first broadcast service, the first resource being used to send data of the first broadcast service to a terminal device in the second network; and the radio access network device sending the data of the first broadcast service to a terminal device in the first network through the first resource.

[0007] Based on the above technical solution, for scenarios where the wireless access network device has already allocated resources and established a corresponding broadcast session context for the first broadcast service in the second network, this application enables the wireless access network device to identify the same broadcast service in different networks by sending an identifier of the first broadcast service to the wireless access network device. The wireless access network device can then use the resources already allocated for the broadcast service in the second network to transmit the data of the broadcast service in the first network. In other words, this application allows the wireless access network device to share air interface resources for the same broadcast service in different networks, saving transmission resources and avoiding waste of air interface resources.

[0008] In this application, the first resource can be used to send data of the first broadcast service to terminal devices in the second network. For example, the first resource can be: air interface resources, such as scheduling time resources, frequency resources, scheduling priority, buffer resources, data radio bearer (DRB), stored context information (e.g., quality of service (QoS) description information, QoS flow identification information), etc., one or more of the above, without limitation.

[0009] In this application, the information of the first resource may be, for example, the identification information of the first resource (e.g., context ID, or the time-domain and frequency-domain location of the first resource, etc., without limitation).

[0010] In one implementation, the identifier of the first broadcast service includes a first identifier and / or a second identifier, wherein 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, the temporary mobile group identifier being shared by the at least two networks; the second identifier includes: an identifier of the first broadcast service in the first network.

[0011] For example, the identifier of the first broadcast service may include a globally unique identifier of the first broadcast service and an identifier of the first broadcast service in the first network; as another example, the identifier of the first broadcast service may include an identifier of the first broadcast service in each of the at least two networks and a temporary mobile group identifier of the first broadcast service; as yet another example, the identifier of the first broadcast service may include a globally unique identifier of the first broadcast service, a temporary mobile group identifier of the first broadcast service, and an identifier of the first broadcast service in the first network, and so on.

[0012] In one implementation, the globally unique identifier of the first broadcast service includes the Internet Protocol (IP) multicast address of the first broadcast service. It should be noted that the globally unique identifier of the first broadcast service can be the Internet Protocol (IP) multicast address of the first broadcast service, or it can include other content, such as the source address of the multicast / broadcast data; this application does not limit this.

[0013] The IP multicast address, for example, for Internet Protocol version 4 (IPv4), can be one or more IP addresses in the address ranges of 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 233.0.0.0 to 233.251.255.255; for Internet Protocol version 6 (IPv6), it can also be one or more IP addresses with the prefix ff02, ff05, or ff0x, and this application does not limit it.

[0014] It should be noted that, in this application, when the identifier of the first broadcast service is a globally unique identifier for the first broadcast service, for example, this can be achieved by adding a new information element to the request message sent by the application function network element to the PLMN network. That is, by adding the globally unique identifier of the first broadcast service to the request message sent by the application function network element to the PLMN network. This method requires minimal modification to the application server, is easy to implement, and is easy to promote. When the identifier of the first broadcast service is the identifier of the first broadcast service in each of at least two networks, this can be achieved by extending the information elements in the messages sent by the existing access and mobility management network element to the access network equipment. That is, by extending the original identifier of the first broadcast service in the network to the identifier of the first broadcast service in each of at least two networks, the new function is implemented, requiring minimal network modification and being easy to upgrade.

[0015] In one implementation, when the identifier of the first broadcast service is a globally unique identifier of the first broadcast service, the radio access network device obtains information about the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service, including: the radio access network device searching for the broadcast session context corresponding to the first broadcast service based on the globally unique identifier of the first broadcast service; the radio access network device obtaining information about the first resource based on the broadcast session context; wherein, the broadcast session context includes the globally unique identifier of the first broadcast service and the information about the first resource.

[0016] In one implementation, 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 radio access network device obtains information about the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service, including: the radio access network device searching for a broadcast session context corresponding to the first broadcast service based on the identifier of the first broadcast service in each of the at least two networks; the radio access network device obtaining information about the first resource based on the broadcast session context; wherein the broadcast session context includes the identifier of the first broadcast service in each of the at least two networks and the information about the first resource.

[0017] In one implementation, when the identifier of the first broadcast service includes the second identifier, the radio access network device obtains information about the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service. This includes: the radio access network device obtaining the identifier of the first broadcast service in the second network based on a 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, and the second identifier; the radio access network device searching for the broadcast session context corresponding to the first broadcast service based on the identifier of the first broadcast service in the second network; and the radio access network device obtaining information about the first resource based on the broadcast session context; wherein the broadcast session context includes the second identifier and information about the first resource.

[0018] In one implementation, when the identifier of the first broadcast service is a temporary mobile group identifier (TMBI) of the first broadcast service, since the TMBI of the first broadcast service received by the radio access network (RAN) device in the second network is shared with the TMBI of the first broadcast service received in the first network (e.g., the TMBI is the same), the RAN can use the first resource in the second network to transmit the data of the first broadcast service in the first network. In other words, at this time, the RAN does not need to look up the context corresponding to the first broadcast service or the information of the first resource to use the first resource to transmit the data of the first broadcast service to the terminal device in the first network.

[0019] Based on the above technical solution, in this application, since a broadcast session context corresponding to the first broadcast service has already been established in the second network, and this broadcast session context includes the identifier of the first broadcast service and information about the first resource, the wireless access network device can obtain information about the first resource allocated for the first broadcast service in the second network based on the identifier of the first broadcast service. The wireless access network device can then use the first resource to send data of the first broadcast service to terminal devices in the first network.

[0020] For a scenario where a radio access network device has not yet established a broadcast session context corresponding to a first broadcast service in a certain network, the method further includes: if the identifier of the first broadcast service includes the first identifier, the method further includes: the radio access network device receiving a second message from a second access and mobility management function (AM) element, the second message carrying the first identifier, the second message being used to trigger resource allocation for the first broadcast service, the second AM element being located in a second network among the at least two networks; the radio access network device allocating the first resource for the first broadcast service according to the second message; the radio access network device establishing a broadcast session context corresponding to the first broadcast service; wherein, the broadcast session context includes the first identifier and information about the first resource.

[0021] Based on the above technical solution, in this application, if resources have not yet been allocated for the first broadcast service and a corresponding broadcast session has not yet been established in a certain network, the wireless access network device can allocate resources for the first broadcast service and establish a session context for the first broadcast service in a second network. Subsequently, the wireless access network device can flexibly use (or "share") the resources based on whether resources have already been allocated for the broadcast service locally, without distinguishing between networks.

[0022] Secondly, a broadcast communication method is provided, which can be executed by a multicast / broadcast session management function network element, or by a component (e.g., a chip or circuit) of the multicast / broadcast session management function network element, without limitation.

[0023] The method includes: a multicast / broadcast session management function network element receiving an identifier of a first broadcast service; the multicast / broadcast session management function network element sending the identifier of the first broadcast service to an access and mobility management function network element.

[0024] Based on the above technical solution, in this application, 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, thereby enabling the radio access network device to obtain the identifier of the first broadcast service and identify the same broadcast data in different networks.

[0025] In one implementation, the identifier of the first broadcast service includes a first identifier, which 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 at least two networks; or a temporary mobile group identifier of the first broadcast service, which is shared by at least two networks.

[0026] In one implementation, the globally unique identifier of the first broadcast service includes the Internet Protocol (IP) multicast address of the first broadcast service. It should be noted that the globally unique identifier of the first broadcast service can be the Internet Protocol (IP) multicast address of the first broadcast service, or it can include other content, such as the source address of the multicast / broadcast data; this application does not limit this.

[0027] The IP multicast address, for example, for Internet Protocol version 4 (IPv4), can be one or more IP addresses in the address ranges of 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 233.0.0.0 to 233.251.255.255; for Internet Protocol version 6 (IPv6), it can also be one or more IP addresses with the prefix ff02, ff05, or ff0x, and this application does not limit the scope.

[0028] It should be noted that, in this application, when the identifier of the first broadcast service is a globally unique identifier for the first broadcast service, for example, this can be achieved by adding a new information element to the request message sent by the application function network element to the PLMN network. That is, by adding the globally unique identifier of the first broadcast service to the request message sent by the application function network element to the PLMN network. This method requires minimal modification to the application server, is easy to implement, and is easy to promote. When the identifier of the first broadcast service is the identifier of the first broadcast service in each of at least two networks, this can be achieved by extending the information elements in the messages sent by the existing access and mobility management network element to the access network equipment. That is, by extending the original identifier of the first broadcast service in the network to the identifier of the first broadcast service in each of at least two networks, the new function is implemented, requiring minimal network modification and being easy to upgrade.

[0029] Furthermore, in this application, wireless access network devices can flexibly identify different forms of the identifier of the first broadcast service as the same broadcast service.

[0030] In one implementation, 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 identifier of the first broadcast service from the application function network element.

[0031] In one implementation, the multicast / broadcast session management function network element receives the identifier of the first broadcast service, including: the multicast / broadcast session management function network element receives the identifier of the first broadcast service from the multicast / broadcast user plane function network element, wherein the identifier of the first broadcast service is a globally unique identifier of the first broadcast service.

[0032] Based on the above technical solution, in this application, the multicast / broadcast session management function network element can receive the identifier of the first broadcast service from the application function network element or from the multicast / broadcast user plane function network element. That is, it can flexibly receive the identifier of the first broadcast service from various core network elements. This allows subsequent radio access network devices to identify the same broadcast service in different networks based on the identifiers of broadcast services received from different core network elements.

[0033] In one implementation, before the multicast / broadcast session management function network element receives the identifier of the first broadcast service from the application function network element, the method further includes: the multicast / broadcast session management function network element receiving a third message from the application function network element, the third message carrying the identifier of the first broadcast service, the third message being used to trigger the multicast / broadcast session management function network element to send a temporary mobile group identifier of the first broadcast service to the application function network element; the multicast / broadcast session management function network element obtaining the temporary mobile group identifier from the first network element according to the third message, or; the multicast / broadcast session management function network element allocating the temporary mobile group identifier for the first broadcast service according to the third message; and the multicast / broadcast session management function network element sending the temporary mobile group identifier to the application function network element.

[0034] Based on the above technical solution, in this application, if the identifier of the first broadcast service is a temporary mobile group identifier, the multicast / broadcast session management function network element can obtain the temporary mobile group identifier from the first network element or independently allocate a temporary mobile group identifier for the first broadcast service, thereby ensuring that the same temporary mobile group identifier is used for the same broadcast service.

[0035] In one implementation, 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.

[0036] The first network element in this application can be a network element in the existing 5G core network architecture or a new network element defined in the future. That is, there is no limitation on the specific name of the first network element. As long as the temporary mobile group identifier of the first broadcast service can be obtained from the network element, and the temporary mobile group identifier can be shared by at least two networks, it falls within the protection scope of this application.

[0037] In one implementation, before the multicast / broadcast session management function network element receives the identifier of the first broadcast service from the multicast / broadcast user plane function network element, the method further includes: the multicast / broadcast session management function network element sending a fourth message to the multicast / broadcast user plane function network element, the fourth message being used to request the establishment or modification of a session for the first broadcast service, the fourth message carrying first indication information, the first indication information being used to trigger the multicast / broadcast user plane function network element to detect the identifier of the first broadcast service.

[0038] Based on the above technical solution, 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. Furthermore, this technical solution can obtain the identifier of the first broadcast service without relying on the application function network element; that is, it can be understood as being able to be implemented even without enhancing the functionality of the application function network element.

[0039] Thirdly, a broadcast communication method is provided, which can be executed by an application function network element, or by a component of the application function network element (such as a chip or circuit), without limitation.

[0040] The method includes: an application function network element obtaining an identifier of a first broadcast service; the application function network element sending the identifier of the first broadcast service to a multicast / broadcast session management function network element.

[0041] In one implementation, the identifier of the first broadcast service includes a first identifier, which 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 at least two networks; or a temporary mobile group identifier of the first broadcast service, which is shared by at least two networks.

[0042] In one implementation, the globally unique identifier of the first broadcast service includes the Internet Protocol (IP) multicast address of the first broadcast service. It should be noted that the globally unique identifier of the first broadcast service can be the Internet Protocol (IP) multicast address of the first broadcast service, or it can include other content, such as the source address of the multicast / broadcast data; this application does not limit this.

[0043] The IP multicast address, for example, for Internet Protocol version 4 (IPv4), can be one or more IP addresses in the address ranges of 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 233.0.0.0 to 233.251.255.255; for Internet Protocol version 6 (IPv6), it can also be one or more IP addresses with the prefix ff02, ff05, or ff0x, and this application does not limit the scope.

[0044] It should be noted that, in this application, when the identifier of the first broadcast service is a globally unique identifier for the first broadcast service, for example, this can be achieved by adding a new information element to the request message sent by the application function network element to the PLMN network. That is, by adding the globally unique identifier of the first broadcast service to the request message sent by the application function network element to the PLMN network. This method requires minimal modification to the application server, is easy to implement, and is easy to promote. When the identifier of the first broadcast service is the identifier of the first broadcast service in each of at least two networks, this can be achieved by extending the information elements in the messages sent by the existing access and mobility management network element to the access network equipment. That is, by extending the original identifier of the first broadcast service in the network to the identifier of the first broadcast service in each of at least two networks, the new function is implemented, requiring minimal network modification and being easy to upgrade.

[0045] Furthermore, in this application, wireless access network devices can flexibly identify different forms of the identifier of the first broadcast service as the same broadcast service.

[0046] In one implementation, the application function network element obtains the identifier of the first broadcast service by generating a globally unique identifier for the first broadcast service.

[0047] In one implementation, the at least two networks include a first network and a second network. The application function network element obtains the identifier of the first broadcast service by: the application function network element receiving the identifier of the first broadcast service in the first network from a first multicast / broadcast session management function network element in the first network; and the application function network element receiving the identifier of the first broadcast service in the second network from a second multicast / broadcast session management function network element in the second network.

[0048] In one implementation, the application function network element obtains the identifier of the first broadcast service by obtaining the temporary mobile group identifier from the multicast / broadcast session management function network element.

[0049] Based on the above technical solution, in this application, when the identifier of the first broadcast service is in different forms, the application function network element can use different methods to obtain the identifier of the first broadcast service.

[0050] Fourthly, this application provides a broadcast communication method, which can be executed by a first network element, or by a component of the first network element (such as a chip or circuit), without limitation.

[0051] The method includes: a first network element receiving a fifth message from a multicast / broadcast session management function network element, the fifth message carrying an identifier of a first broadcast service, the fifth message being used to trigger the first network element to send a temporary mobile group identifier of the first broadcast service; and the first network element sending the temporary mobile group identifier of the first broadcast service to the multicast / broadcast session management function network element according to the fifth message.

[0052] In one implementation, the temporary mobile group identifier is shared by at least two networks.

[0053] Based on the above technical solution, in this application, when the identifier of the first broadcast service is a temporary mobile group identifier, the temporary mobile group identifier can be obtained from the first network element.

[0054] In one implementation, 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.

[0055] The first network element in this application can be a network element in the existing 5G core network architecture or a new network element defined in the future. That is, there is no limitation on the specific name of the first network element. As long as the temporary mobile group identifier of the first broadcast service can be obtained from the network element, and the temporary mobile group identifier can be shared by at least two networks, it falls within the protection scope of this application.

[0056] In one implementation, the method further includes: the first network element receiving from the multicast / broadcast session management function network element the correspondence between the identifier of the first broadcast service and the temporary mobile group identifier.

[0057] Based on the above technical solution, in this application, for the first broadcast service in some networks, where a temporary mobile group identifier has not yet been assigned to the first network element, the multicast / broadcast session management function network element can assign a temporary mobile group identifier to the first broadcast service in the network and store it on the first network element.

[0058] Fifthly, a broadcast communication apparatus is provided, which is used to perform the method in any of the possible implementations of the first to fourth aspects described above. Specifically, the apparatus may include units and / or modules for performing the method in any of the possible implementations of the first to fourth aspects, such as transceiver units and / or processing units.

[0059] In one implementation, the device is a communication device (e.g., a wireless access network device, a multicast / broadcast session management function network element, an application function network element, or a first network element). When the device is a communication device, the communication unit can be a transceiver, or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0060] In another implementation, the device is a chip, chip system, or circuit for a communication device (e.g., a wireless access network device, a multicast / broadcast session management function network element, an application function network element, or a first network element). When the device is a chip, chip system, or circuit for a communication device, 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; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0061] A sixth aspect provides a broadcast communication apparatus, comprising: at least one processor for executing a computer program or instructions stored in a memory to perform the method in any possible implementation of the first aspect described above. Optionally, the apparatus further comprises a memory for storing the computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

[0062] In one implementation, the device is a wireless access network device.

[0063] In another implementation, the device is a chip, chip system, or circuit for wireless access network equipment.

[0064] A seventh aspect provides a broadcast communication apparatus, comprising: at least one processor for executing a computer program or instructions stored in a memory to perform the method in any possible implementation of the second aspect described above. Optionally, the apparatus further comprises a memory for storing the computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

[0065] In one implementation, the device is a multicast / broadcast session management function network element.

[0066] In another implementation, the device is a chip, chip system, or circuit for a network element used for multicast / broadcast session management functions.

[0067] Eighthly, a broadcast communication apparatus is provided, comprising: at least one processor for executing a computer program or instructions stored in a memory to perform the method in any possible implementation of the third aspect described above. Optionally, the apparatus further comprises a memory for storing the computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

[0068] In one implementation, the device is an application function network element.

[0069] In another implementation, the device is a chip, chip system, or circuit for applying functional network elements.

[0070] A ninth aspect provides a broadcast communication apparatus, comprising: at least one processor for executing a computer program or instructions stored in a memory to perform the method in any possible implementation of the fourth aspect described above. Optionally, the apparatus further comprises a memory for storing the computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

[0071] In one implementation, the device is the first network element.

[0072] In another implementation, the device is a chip, chip system, or circuit for the first network element.

[0073] In a tenth aspect, this application provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any one of the possible implementations of the first to fourth aspects.

[0074] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a transceiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0075] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0076] Eleventhly, a processing apparatus is provided, including a processor and a memory. The processor is used to read instructions stored in the memory and to receive signals via a transceiver and transmit signals via a transmitter to execute a method in any possible implementation of any of the first to fourth aspects.

[0077] Optionally, the processor may be one or more, and the memory may be one or more.

[0078] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0079] In the specific implementation process, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0080] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of the processor outputting indication information, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the data output by the processor can be sent to the transmitter, and the input data received by the processor can come from the transceiver. Here, the transmitter and the transceiver can be collectively referred to as transceivers.

[0081] The processing device mentioned in the eleventh aspect above can be one or more chips. The processor in the processing device can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.

[0082] In a twelfth aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including methods for performing any of the possible implementations of the first to fourth aspects described above.

[0083] In a thirteenth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method in any of the possible implementations of the first to fourth aspects described above.

[0084] In a fourteenth aspect, a chip system is provided, including a processor for calling and running a computer program from a memory, such that a device equipped with the chip system performs the methods in any of the implementations of the first to fourth aspects described above.

[0085] In a fifteenth aspect, a broadcast communication system is provided, the communication system comprising a radio access network device and a first access and mobility management function (AMU) network element; the radio access network device is configured to execute a method according to any implementation of the first aspect; the first AMU network element is configured to send a first message to the radio access network device, the first message carrying an identifier of a first broadcast service, the first message being configured to trigger resource allocation for the first broadcast service; wherein the radio access network device is shared by at least two networks, the at least two networks including a first network and a second network, and the first AMU network element is located in the first network.

[0086] In one implementation, the communication system further includes a multicast / broadcast session management function network element, which is used to execute the method of any of the implementations in the second aspect above.

[0087] In one implementation, the communication system further includes an application function network element, which is used to execute the method of any of the implementations in the third aspect above.

[0088] In one implementation, the communication system further includes a first network element, which is used to execute the method of any of the implementations in the fourth aspect above. Attached Figure Description

[0089] Figure 1 This is a schematic diagram of a network architecture to which this application applies.

[0090] Figure 2 This is a schematic diagram of a scenario to which this application applies.

[0091] Figure 3 This is a schematic diagram of another scenario to which this application applies.

[0092] Figure 4 This is a schematic flowchart of the broadcast communication method 100 provided in this application.

[0093] Figure 5 This is a schematic flowchart of the broadcast communication method 200 provided in this application.

[0094] Figure 6 This is a schematic flowchart of the broadcast communication method 300 provided in this application.

[0095] Figure 7 This is a schematic flowchart of the broadcast communication method 400 provided in this application.

[0096] Figure 8 This is a schematic flowchart of the broadcast communication method 500 provided in this application.

[0097] Figure 9 This is a schematic flowchart of the broadcast communication method 600 provided in this application.

[0098] Figure 10 This is a schematic flowchart of the broadcast communication method 700 provided in this application.

[0099] Figure 11 This is a schematic flowchart of the broadcast communication method 800 provided in this application.

[0100] Figure 12 This is a schematic block diagram of the broadcast communication device 100 provided in this application.

[0101] Figure 13 This is a schematic block diagram of the broadcast communication device 200 provided in this application. Detailed Implementation

[0102] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0103] The wireless communication systems mentioned in this application include, but are not limited to: Global System for Mobile Communication (GSM) system, Long Term Evolution (LTE) Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, LTE system, LTE-Advanced (LTE-A) system, next-generation communication system (e.g., 6G communication system), converged system of multiple access systems, or evolved system.

[0104] The technical solutions provided in this application can also be applied to machine-type communication (MTC), long-term evolution-machine (LTE-M) technology, device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of Things (IoT) networks, or other networks. Among these, IoT networks may include, for example, vehicle-to-everything (V2X) networks. The communication methods in V2X systems are collectively referred to as vehicle-to-X (V2X), where X can represent anything. For example, V2X may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0105] First, we will briefly introduce the network architecture applicable to this application as an example. Figure 1 A schematic diagram of a network architecture to which this application applies is shown.

[0106] like Figure 1As shown, this network architecture uses the 5G system (5GS) as an example. The 5G system architecture is divided into two parts: the access network and the core network. This network architecture may include, but is not limited to: unified data management (UDM), network exposure function (NEF), network repository function (NRF), policy control function (PCF), application function (AF), access and mobility management function (AMF), session management function (SMF), user equipment (UE), radio access network equipment, user plane function (UPF), and data network (DN). Here, DN can be the Internet; UDM, NEF, NRF, PCF, AF, AMF, SMF, and UPF are network elements in the core network. Figure 1 Taking a 5G system as an example, the core network can be called the 5G core network (5GC or 5GCN).

[0107] The following is about Figure 1 A brief introduction to each network element shown in the diagram is provided.

[0108] 1. User equipment (UE) (101): can be referred to as terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device.

[0109] Terminal devices can be devices that provide voice / data to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0110] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0111] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object interconnection.

[0112] It should be noted that terminal devices and access network devices can communicate with each other using some air interface technology (such as NR or LTE technology). Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology).

[0113] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system or a chip. This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0114] 2. (Radio) access network ((R)AN) device (102): This device provides access to a communication network for authorized users in a specific area. Specifically, it may include wireless network devices in 3GPP networks or access points in non-3GPP networks. For ease of description, it is referred to as an AN device below.

[0115] RAN equipment can support different radio access technologies. Currently, there are two types of radio access technologies: 3GPP access technologies (e.g., those used in 3rd generation (3G), 4th generation (4G), or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. For example, in 5G systems, access network equipment is called a next-generation NodeBase station (gNB) or RAN equipment. Non-3GPP access technologies can include air interface technologies such as access points (APs) in Wireless Fidelity (WiFi), Worldwide Interoperability for Microwave Access (WiMAX), and Code Division Multiple Access (CDMA). RAN equipment allows terminal equipment and the 3GPP core network to interconnect using non-3GPP technologies.

[0116] RAN equipment is responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. AN equipment provides access services to terminal devices, thereby completing the forwarding of control signals and user data between the terminal devices and the core network.

[0117] RAN equipment may include, but is not limited to: macro base stations, micro base stations (also known as small stations), radio network controllers (RNCs), Node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home-evolved Node Bs, or home Node Bs (HNBs)), baseband units (BBUs), access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TPs), or transmission and reception points (TRPs) in WiFi systems. It may also be gNBs or transmission points (TRPs or TPs) in 5G (e.g., NR) systems, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or network nodes constituting gNBs or transmission points, such as distributed units (DUs), or base stations in next-generation 6G communication systems. This application does not limit the specific technology or equipment form used in the AN equipment embodiments.

[0118] 3. User plane function (UPF) (103): This can be used for packet routing and forwarding, or for quality of service (QoS) processing of user plane data. User data can access the data network (DN) through this network element. In the embodiments of this application, it can be used to implement the functions of the user plane network element.

[0119] The multicast / broadcast (MB) UPF involved in this application can be used to send the Internet Protocol (IP) address of the detected multicast / broadcast service to the MB-SMF.

[0120] 4. Digital network (DN) (104): A network used to provide data transmission. Examples include carrier networks, the Internet, and third-party service networks.

[0121] 5. Access and Mobility Management Function (AMF) (105): Primarily used for mobility management and access management, it can be used to implement functions other than session management in the Mobility Management Entity (MME) function, such as lawful monitoring or access authorization (or authentication). In the embodiments of this application, it can be used to implement the functions of the access and mobility management function.

[0122] 6. Session Management Function (SMF) (106): Primarily used for session management, IP address allocation and management of terminal devices, selection and management of user plane functions, policy control, or endpoints of charging function interfaces, and downlink data notification, etc. In this embodiment, it can be used to implement the functions of the session management function.

[0123] The MB-SMF involved in this application can be used to manage multicast / broadcast services, and can also configure the MB-UPF for multicast / broadcast services. For example, the MB-SMF can interact with the MB-UPF via signaling to instruct the MB-UPF to identify the IP address of the MBS data. In addition, the MB-SMF may need to enhance the messages sent to the RAN for the 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; the unicast SMF and the multicast SMF may have an N16 interface.

[0124] 7. Policy control function (PCF) (107): A unified policy framework used to guide network behavior, providing policy rule information for control plane functional network elements (such as AMF, SMF, etc.).

[0125] 8. Unified data management (UDM) (108): Used for unified data management, 5G user data management, processing user identification, access authentication, registration, or mobility management, etc.

[0126] 9. Application Function (AF): Used for data routing affected by applications, accessing network open function network elements, or interacting with the policy framework for policy control, etc. In this application, AF can also be understood as an application server.

[0127] exist Figure 1In the network architecture shown, network elements can communicate with each other through the interfaces shown in the diagram. As shown, interface N1 is the reference point between the terminal device and the AMF; interface N2 is the reference point between the RAN and the AMF, used for sending non-access stratum (NAS) messages, etc.; interface N3 is the reference point between the RAN and the UPF, used for transmitting user plane data, etc.; interface N4 is the reference point between the SMF and the UPF, used for transmitting information such as tunnel identification information for the N3 connection, data buffer indication information, and downlink data notification messages, etc.; interface N5 is the reference point between the PCF and the AF; interface N6 is the reference point between the UPF and the DN, used for transmitting user plane data, etc.; interface N7 is the reference point between the SMF and the PCF; interface N8 is the reference point between the AMF and the UDM; and interface N11 is the reference point between AMFs. The relationships between other interfaces and each network element are as follows: Figure 1 As shown, for the sake of brevity, not all details are provided here.

[0128] It should be understood that the above Figure 1 The network architecture shown is merely an illustrative example. The network architecture applicable to the embodiments of this application is not limited to this. Any network architecture capable of implementing the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0129] It should also be understood that Figure 1 The AMF, SMF, UPF, PCF, UDM, and other functions or network elements shown can be understood as network elements used to implement different functions. For example, they can be combined into network slices as needed. These network elements can be independent devices or integrated into the same device to implement different functions. They can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). This application does not limit the specific form of the above network elements.

[0130] It should also be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 6G networks and other future networks. For example, in 6G networks, some or all of the above-mentioned network elements may use the terminology from 5G, or they may use other names, etc.

[0131] To facilitate understanding of the technical solution of this application, the terms involved in this application will be briefly explained below.

[0132] 1. Multicast: The same service and the same specific content 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). In this application, "multicast" can also be understood as "multicast".

[0133] 2. Broadcast: The same specific content is simultaneously provided to all UEs in the geographic area (i.e., all UEs in the broadcast coverage area are authorized to receive the data).

[0134] 3. Multicast / broadcast service session (MBSsession): 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 equipment and then to the access network equipment, as well as the unicast or multicast / broadcast air interface resources allocated by the access network equipment for sending the multicast / broadcast service.

[0135] Figure 2 This illustration shows a scenario to which this application applies. Typically, when deploying a network, operators, in order to reduce the cost of deploying a radio access network, generally choose to share radio access network equipment while retaining their own core network (in the following description, base stations are used as radio access network equipment). For example, the multi-operator core network (MOCN) scenario defined in TS23.501. Figure 2 As shown, suppose there are three operators: Operator #A, Operator #B, and Operator #C each have their own core network. However, to save costs (e.g., the cost of deploying base stations), the three operators may share base stations. Compared to the normal scenario, in the MOCN deployment scenario, the broadcast messages include information about the public land mobile network (PLMN). For example, the cell information sent by the base station includes information about the PLMN to which the cell belongs.

[0136] Figure 3 This illustration shows another scenario to which this application applies, such as... Figure 3 As shown, currently, some broadcast services (e.g., weather forecasts, high-precision map updates, etc.) transmit the same content across different operators. For these types of broadcast services, the same broadcast service data needs to be transmitted multiple times across the core networks of different operators and the base stations shared by the operators. For example, as... Figure 3As shown, suppose there are two operators (denoted as PLMN #a and PLMN #b), and the multicast / broadcast service content provider (MBS content provider) sends broadcast data to PLMN #a and PLMN #b respectively. Since PLMN #a and PLMN #b share a base station, the same broadcast service data will be transmitted twice in the base station (which can also be understood as the base station needing to allocate air interface resources twice to transmit the same broadcast service in different operator networks), thus wasting transmission resources.

[0137] The broadcast communication method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the above-described... Figure 1 The network architecture shown can also be applied to, for example... Figure 2 , Figure 3 The scenario shown is not limited.

[0138] Figure 4 This is a schematic diagram of a broadcast communication method 100 provided in this application. The method can be executed, for example, by a wireless access network device. The method 100 includes the following steps.

[0139] Step 101: The wireless access network device receives a first message from the first access and mobility management function network element.

[0140] The wireless access network equipment can be shared by at least two networks, which can be at the PLMN level or at the standalone non-public network (SNPN) level. For example, the at least two networks can include a first network and a second network, where the first network can be PLMN#1 and the second network can be PLMN#2; or, for another example, the at least two networks can include a first network and a second network, where the first network can be SNPN#1 and the second network can be SNPN#2.

[0141] The first access and mobility management function network element is located in the first network.

[0142] It should be noted that the various embodiments of this application are illustrated using the example of a wireless access network device shared by two networks, and are not intended to be limiting.

[0143] The first message can be used to trigger the radio access network device to allocate resources for the first broadcast service. These resources can be air interface resources, such as scheduling time resources, frequency resources, scheduling priorities, buffer resources, and data radio bearers (DRBs); alternatively, they can be stored context information (e.g., QoS description information, QoS flow identification information). In other words, the first message can be used to request the radio access network device to allocate resources for the first broadcast service, or it can be used to request the radio access network device to establish the context corresponding to the first broadcast service.

[0144] Specifically, the first message can be an existing message, such as an N2 request message; or it can be a message related to a multicast / broadcast session, such as an MBS session resource setup request, an MBS session start request, or a broadcast session resource setup request.

[0145] It should be noted that the first message may be sent by the first access and mobility management function network element based on the message received from the first multicast / broadcast session management function network element.

[0146] The first message may carry an identifier for the first broadcast service, which can be used to indicate the first broadcast service. The first broadcast service can be a service initiated by an application function network element, requesting the establishment of resources in the PLMN network and transmitting it. For example, the first broadcast service could be a weather forecast service, an emergency alarm service, a high-precision map service, etc.

[0147] Optionally, the identifier for the first broadcast service may include a first identifier and / or a second identifier.

[0148] The first identifier may include at least one of the following: a globally unique identifier for the first broadcast service, an identifier for the first broadcast service in each of at least two networks, or a temporary mobile group identifier (TMGI) corresponding to the first broadcast service, which is shared by the at least two networks.

[0149] The globally unique identifier for the first broadcast service can be used to globally uniquely identify the first broadcast service. For example, this globally unique identifier could be the Internet IP multicast address of the first broadcast service. Alternatively, in addition to including the Internet Protocol (IP) multicast address of the first broadcast service, this globally unique identifier could also include other content, such as the source address of the multicast / broadcast data, without limitation.

[0150] For example, for Internet Protocol version 4 (IPv4), the IP multicast address can be one or more IP addresses in the address ranges 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 233.0.0.0 to 233.251.255.255; for Internet Protocol version 6 (IPv6), the IP multicast address can be one or more IP addresses with the prefix ff02, ff05, or ff0x, without limitation.

[0151] The identifier of the first broadcast service in each of the at least two networks can also be understood as the identifier of the broadcast session of the first broadcast service in each of the at least two networks.

[0152] Optionally, the identifier includes network identification information. For example, the network identification information is the PLMN ID (e.g., 33E451), or the PLMN ID + network identifier (NID).

[0153] For example, the identifier of the first broadcast service in each of at least two networks can be represented in the form of a list, which contains the identifiers of the broadcast sessions of the first broadcast service in each of the at least two networks. Table 1 is used as an example below. For instance, the broadcast session identifier of the first broadcast service in network #1 could be TMGI#1, specifically 70A886 32F461; the broadcast session identifier of the first broadcast service in network #2 could be TMGI#2, specifically 81B749 33E451; and the broadcast session identifier of the first broadcast service in network #3 could be TMGI#3, specifically 649739 42F352.

[0154] Table 1. Identifiers of broadcast sessions for the first broadcast service in each network

[0155]

[0156] It should be noted that, in actual implementation, the identifier of the first broadcast service in each of at least two networks can be represented by the above-mentioned list, or by an array (e.g., {70A886 32F461, 81B74933E451, 649739 42F352}), or by other methods used to identify a set of data (e.g., structure, linked list, etc.), which are not limited in this application.

[0157] The identifier of the broadcast session is used to identify the broadcast session. For example, it can be the identifier of the group corresponding to the broadcast session, such as a temporary mobile group identifier.

[0158] The Temporary Mobile Group Identifier (TMGI) corresponding to the first broadcast service can be shared by at least two networks. This can be understood as configuring a universal TMGI for the first broadcast service, which can uniquely identify a broadcast service in both the first and second networks. Specifically, when the MB-SMFs of the first and second networks request the TMGI from the AF, the AF can provide this universal TMGI.

[0159] Here, "generic TMGI" means that one or more TMGIs can be shared by several (i.e., at least two) networks. For example, for the first broadcast service, the TMGI in the first network is the same as the TMGI in the second network, both being TMGI #v.

[0160] The second identifier may include: the identifier of the first broadcast service in the first network, which may be the identifier of the broadcast session of the first broadcast service in the first network; optionally, the second identifier may also include the identification information of the first broadcast service in the first network, such as PLMN ID or PLMN ID + NID.

[0161] It should be noted that when the identifier of the first broadcast service includes a second identifier, the radio access network device can pre-configure or acquire or receive the identifier of the first broadcast service in each of the at least two networks. For example, when the radio access network device first establishes a session for the first broadcast service, it receives a list of identifiers of the first broadcast service in each of the at least two networks (see Table 1) and stores it. Furthermore, when establishing a session for the first broadcast service on a subsequent occasion (e.g., the second time), the core network element in the first network (e.g., the first access and mobility management function element) can carry the identifier of the first broadcast service in the first network, which can avoid repeatedly sending the entire list and save transmission resources.

[0162] The first broadcast service session can refer to a session used to transmit the first broadcast service.

[0163] It should be noted that, in this application, when the identifier of the first broadcast service is a globally unique identifier for the first broadcast service, for example, this can be achieved by adding a new information element to the request message sent by the application function network element to the PLMN network. That is, by adding the globally unique identifier of the first broadcast service to the request message sent by the application function network element to the PLMN network. This method requires minimal modification to the application server, is easy to implement, and is easy to promote. When the identifier of the first broadcast service is the identifier of the first broadcast service in each of at least two networks, this can be achieved by extending the information elements in the messages sent by the existing access and mobility management network element to the access network equipment. That is, by extending the original identifier of the first broadcast service in the network to the identifier of the first broadcast service in each of at least two networks, the new function is implemented, requiring minimal network modification and being easy to upgrade.

[0164] Step 102: The wireless access network device obtains information about the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service.

[0165] The first resource can be used to send data for the first broadcast service to terminal devices in the second network. For example, the first resource can be: air interface resources. For example, the air interface resources are scheduling time resources, frequency resources, scheduling priorities, buffer resources, and data radio bearers (DRBs); the first resource can also be: stored context information, such as QoS description information, QoS flow identification information, etc., without limitation.

[0166] The information of the first resource can be the identification information of the first resource (e.g., context ID, or the time-domain and frequency-domain location of the first resource, etc., without limitation).

[0167] The implementation of step 102 can be divided into the following scenarios:

[0168] Scenario 1: For a scenario where a wireless access network device has already established a session for the first broadcast service in a certain network (taking the second network as an example) (which can also be understood as a scenario where resources have already been allocated for the first broadcast service in the second network).

[0169] In scenario 1, the session context corresponding to the session of the first broadcast service (hereinafter referred to as the session context corresponding to the first broadcast service) may include the identifier of the first broadcast service and information about the first resource allocated to the first broadcast service. In step 102, the radio access network device obtains the information about the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service, which can be implemented as follows:

[0170] In Method 1, if the identifier of the first broadcast service is a globally unique identifier of the first broadcast service, the radio access network device looks up the broadcast session context corresponding to the first broadcast service based on the globally unique identifier of the first broadcast service, and the radio access network device obtains the information of the first resource corresponding to the first broadcast service based on the broadcast session context.

[0171] The broadcast session context may include the globally unique identifier of the first broadcast service and information about the first resource.

[0172] Since the first broadcast service session context established in the second network includes the globally unique identifier of the first broadcast service and information about the first resource, the base station shared by the first network and the second network can reuse the first resource when it receives a request from the first network to establish the first broadcast service session context (or a request to allocate resources for the first broadcast service session), thereby avoiding resource waste.

[0173] Method 2: When the identifier of the first broadcast service is the identifier of the first broadcast service in each of at least two networks, the radio access network device looks up the broadcast session context corresponding to the first broadcast service based on the identifier of the first broadcast service in each of at least two networks, and obtains the information of the first resource corresponding to the first broadcast service based on the broadcast session context.

[0174] The broadcast session context may include the identifier of the first broadcast service in each of at least two networks and information about the first resource.

[0175] Because the broadcast session context corresponding to the first broadcast service established in the second network includes the identifier of the first broadcast service in each of at least two networks and information about the first resource, the base station shared by the second network and other networks can reuse the first resource when it receives a request from another network to establish a first broadcast service session context (or a request to allocate resources for the first broadcast service session). That is, the radio access network equipment does not need to reallocate resources for the first broadcast service in other networks, thus avoiding resource waste.

[0176] Method 3: When the identifier of the first broadcast service is the second identifier (e.g., the identifier of the first broadcast service in the first network), the radio access network device obtains the identifier of the first broadcast service in the second network based on 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, and the second identifier. The radio access network device then looks up the broadcast session context corresponding to the first broadcast service based on the identifier of the first broadcast service in the second network, and obtains the information of the first resource corresponding to the first broadcast service based on the broadcast session context.

[0177] The broadcast session context may include a second identifier and information about the first resource.

[0178] Furthermore, since the broadcast session context corresponding to the first broadcast service established in the second network includes information about the second identifier and the first resource, the base station shared by the second network and other networks can reuse the first resource when it receives a request from another network to establish a first broadcast service session context (or a request to allocate resources for the first broadcast service session). That is, the radio access network equipment does not need to reallocate resources for the first broadcast service in other networks, thereby avoiding resource waste.

[0179] It should be noted that in the above scenario 1, resources (e.g., first resources) have already been allocated for the first broadcast service in the second network. These resources can be used by multiple networks (e.g., the first network) to transmit the first broadcast service. That is, the wireless access network device does not need to reallocate resources for the first broadcast service in the first network, thereby avoiding resource waste.

[0180] In the above embodiments, since a broadcast session context corresponding to the first broadcast service has been established in the second network, and the broadcast session context includes the identifier of the first broadcast service and the information of the first resource, the wireless access network device can obtain the information of the first resource allocated for the first broadcast service in the second network through the identifier of the first broadcast service. Then, the wireless access network device can send the data of the first broadcast service to the terminal device in the first network through the first resource.

[0181] Scenario 2: For wireless access network devices that have not yet established first broadcast service sessions in various networks.

[0182] In scenario 2, method 100 may further include: a wireless access network device receiving a second message from a second access and mobility management function network element, the second message carrying an identifier of a first broadcast service.

[0183] The second message is used to trigger the allocation of resources for the first broadcast service, and 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.

[0184] Furthermore, when the identifier of the first broadcast service includes a first identifier (for example, the identifier of the first broadcast service is the first identifier; or, for example, the identifier of the first broadcast service includes both the first identifier and the second identifier), the radio access network device allocates a 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, wherein the broadcast session context includes the identifier of the first broadcast service and the information of the first resource.

[0185] The second message in this scenario can be described in the same way as the first message. The difference is that the second message is transmitted between core network elements in the second network, while the first message is transmitted between core network elements in the first network.

[0186] The second message can be an existing message, such as an N2 request message; or it can be a message related to a multicast / broadcast session, such as an MBS session resource establishment request, an MBS session start request, or a broadcast session resource establishment request.

[0187] In scenario 2 above, if resources have not yet been allocated for the first broadcast service and a corresponding broadcast session has not yet been established in each network, the radio access network device can allocate resources for the first broadcast service and establish a session context for the first broadcast service in the second network. Since the broadcast session context corresponding to the first broadcast service established in the second network includes the identifier of the first broadcast service and information about the first resource, the radio access network device does not need to repeatedly allocate resources for the same broadcast service in different networks. This can also be understood as the radio access network device being able to flexibly use (or "share") the resource based on whether resources have already been allocated locally for the broadcast service, regardless of the network.

[0188] Step 103: 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.

[0189] In one optional implementation, after receiving service data from a multicast / broadcast user management network element, the wireless access network device identifies that the service data belongs to a first broadcast service based on the identification information contained in the service data (e.g., target IP address, tunnel node identifier in the General Packet Radio Service (GPRS) tunneling protocol (GTP) header, QoS flow identifier). The wireless access network device then transmits (or broadcasts) the service data through the air interface resources (e.g., time-frequency resources) corresponding to the first broadcast service based on locally stored context information (e.g., scheduling queues, reserved resources). Accordingly, the terminal devices in the first network monitor the air interface resources and receive the service data.

[0190] In another alternative implementation, when the identifier of the first broadcast service is a Temporary Mobile Group (TMG) identifier, since this TMG identifier is shared by all networks, when the radio access network (RAN) device receives the TMG identifier, it can use the first resource to send the data of the first broadcast service to the terminal devices in the first network. In other words, in this implementation, since the RAN device receives the same TMG identifier in all networks, it does not need to look up the first broadcast session context to obtain the information of the first resource, and can directly use the first resource to send the data of the first broadcast service to the terminal devices in the first network.

[0191] Based on the above technical solution, since a broadcast session context corresponding to the first broadcast service has already been established in the second network, and this broadcast session context includes the identifier of the first broadcast service and information about the first resource, the radio access network device can obtain information about the first resource already allocated for the first broadcast service in the second network based on the identifier of the first broadcast service. The radio access network device can then use the first resource to send the data of the first broadcast service to terminal devices in the first network. That is, the radio access network device can reuse the first resource without having to reallocate resources for the first broadcast service in other networks, thereby avoiding resource waste.

[0192] like Figure 5 As shown, this application also provides a broadcast communication method 200, which can be executed, for example, by a multicast / broadcast session management function network element. The method 200 includes the following steps.

[0193] Step 201: The multicast / broadcast session management function network element receives the identifier of the first broadcast service.

[0194] The multicast / broadcast session management function network element can be located in the first network or in the second network, without limitation.

[0195] Optionally, the identifier of the first broadcast service includes a first identifier. Specifically, the description of the first identifier can be referred to the description of step 101 in method 100, and will not be repeated here.

[0196] In one optional implementation, the multicast / broadcast session management function network element receives the identifier of the first broadcast service, including: the multicast / broadcast session management function network element receives the identifier of the first broadcast service from the application function network element.

[0197] Furthermore, before the multicast / broadcast session management function network element receives the identifier of the first broadcast service from the application function network element, method 200 may further include:

[0198] The multicast / broadcast session management function network element receives a third message from the application function network element. This third message carries the identifier of the first broadcast service. The third message triggers the multicast / broadcast session management function network element to send a temporary mobile group identifier (MRI) for the first broadcast service to the application function network element. Based on the third message, the multicast / broadcast session management function network element obtains the MRI for the first broadcast service from the first network element; alternatively, the multicast / broadcast session management function network element assigns a MRI to the first broadcast service based on the third message.

[0199] Specifically, the third message can be a TMGI allocation request message.

[0200] Specifically, the first network element can 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.

[0201] In another optional implementation, the multicast / broadcast session management function network element receives the identifier of the first broadcast service, including: the multicast / broadcast session management function network element receives the identifier of the first broadcast service from the multicast / broadcast user plane function network element, wherein the identifier of the first broadcast service is a globally unique identifier of the first broadcast service.

[0202] Furthermore, before the multicast / broadcast session management function network element receives the identifier of the first broadcast service from the multicast / broadcast user plane function network element, method 200 may further include:

[0203] 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 establishment or modification of the session for the first broadcast service. The fourth message carries first indication information, which is used to trigger the multicast / broadcast user plane function network element to detect the identifier of the first broadcast service.

[0204] The above method, by instructing the multicast / broadcast user plane function network element to detect the identifier of the first broadcast service, can successfully obtain the globally unique identifier of the first broadcast service, meaning that the identifier of the first broadcast service can be obtained without relying on the application function network element.

[0205] The multicast / broadcast user plane function network element can be a multicast / broadcast user plane function network element located in the first network or a multicast / broadcast user plane function network element located in the second network, without limitation.

[0206] Specifically, the fourth message can be an N4 session establishment / modification request message.

[0207] 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.

[0208] The access and mobility management function network element can be located in the first network or in the second network, without limitation.

[0209] Based on the above technical solution, 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, thereby enabling the radio access network device to obtain the identifier of the first broadcast service and identify the same broadcast data in different networks.

[0210] like Figure 6 As shown, this application also provides a broadcast communication method 300, which can be executed by an application function network element, and the method 300 includes the following steps.

[0211] Step 301: The application function network element obtains the identifier of the first broadcast service.

[0212] Optionally, the identifier of the first broadcast service includes a first identifier. Specifically, the description of the first identifier can be referred to the description of step 101 in method 100, and will not be repeated here.

[0213] In one optional implementation, the application function network element obtains the identifier of the first broadcast service, including: the application function network element generates a globally unique identifier for the first broadcast service.

[0214] In another alternative implementation, the application function network element obtains the identifier of the first broadcast service, including: the application function network element receiving the identifier of the first broadcast service in the first network from the first multicast / broadcast session management function network element in the first network; and the application function network element receiving the identifier of the first broadcast service in the second network from the second multicast / broadcast session management function network element in the second network.

[0215] This can also be understood as the application function network element obtaining the identifier of the first broadcast service in each network through interaction with the network elements of the core network of each network.

[0216] In another alternative implementation, the application function network element obtains the identifier of the first broadcast service, including: the application function network element obtains the temporary mobile group identifier of the first broadcast service from the multicast / broadcast session management function network element.

[0217] Step 302: The application function network element sends the identifier of the first broadcast service to the multicast / broadcast session management function network element.

[0218] According to the method provided in this implementation, application function network elements can flexibly obtain the identifier of the first broadcast service through the above-mentioned implementation methods.

[0219] Based on the above technical solution, the application function network element can send the identifier of the first broadcast service to the multicast / broadcast session management function network element, thereby enabling the wireless access network device to obtain the identifier of the first broadcast service and identify the same broadcast data in different networks.

[0220] like Figure 7 As shown, this application also provides a broadcast communication method 400, which can be executed by a first network element. The method 400 includes the following steps.

[0221] Step 401: The first network element receives the fifth message from the multicast / broadcast session management function network element.

[0222] 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.

[0223] The description of the first network element can be found in step 201 of method 200, and will not be repeated here.

[0224] Specifically, the fifth message may be a message for requesting the creation of broadcast sessions, or the fifth message may be a multicast / broadcast session creation request message (e.g., Nmbsmf_MBSsession create request) for requesting the temporary mobile group identifier of the first broadcast service.

[0225] Step 402: 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.

[0226] Optionally, the method 400 further includes: the first network element receiving the correspondence between the identifier of the first broadcast service and the temporary mobile group identifier from the multicast / broadcast session management function network element. This can also be understood as follows: if the temporary mobile group identifiers of the first broadcast service pre-stored on the first network element do not fully include the temporary mobile group identifiers of the first broadcast services in each network, then the multicast / broadcast session management function network element can allocate temporary mobile group identifiers for the first broadcast services in that network and send them to the first network element for storage.

[0227] Optionally, the temporary mobile group identifier is shared by at least two networks. For example, for the first broadcast service, the temporary mobile group identifier is the same in all networks. Alternatively, for the first broadcast service, the temporary mobile group identifier may differ in all networks, but the core network elements and radio access network devices in each network can identify that the indicated service is the first broadcast service through this temporary mobile group identifier.

[0228] Based on the above technical solution, by designing a temporary mobile group identifier for the first broadcast service, the identifier of the first broadcast service in different networks can be identified by the core network elements or radio access network devices of each network as indicating the first broadcast service. This eliminates the need for radio access network devices to reallocate resources for the first broadcast service in different networks, thus avoiding the waste of air interface resources.

[0229] In this application, in the following specific embodiments, the first network is described using PLMN #a as an example, the second network using PLMN #b as an example, and the terminal device is described using UE as an example. In the following embodiments, the suffix "#b" for a core network element indicates that the core network element is in PLMN #b, and the suffix "#a" for a core network element indicates that the core network element is in PLMN #a. The RAN in the following specific embodiments can be understood as the RAN shared by PLMN #a and PLMN #b.

[0230] It should be noted that the following embodiments of this application are merely illustrative examples using two PLMN networks, and the number of networks is not limited in this application. That is, the technical solution of this application can be applied to scenarios where n (n≥1) networks share a RAN.

[0231] Figure 8 This is a schematic flowchart of a broadcast communication method 500 provided in this application. Assuming there are two PLMNs (denoted as PLMN #a and PLMN #b) in this embodiment, and taking broadcast service #1 as an example, the method includes:

[0232] Step 501: AF requests the identifier of broadcast service #1 in different PLMNs from different PLMN networks.

[0233] In this application, the identifier of broadcast service #1 in different PLMNs can be MBS Session ID, such as Temporary Mobile Group Identifier (TMGI), which will not be elaborated further below.

[0234] For example, AF requests the identifier of broadcast service #1 from MB-SMF #a in PLMN #a. Suppose that AF obtains the identifier of broadcast service #1 in PLMN #a as TMGI #x; similarly, AF requests the identifier of broadcast service #1 from MB-SMF #b in PLMN #b. Suppose that AF obtains the identifier of broadcast service #1 in PLMN #b as TMGI #y.

[0235] Step 502: AF generates a globally unique identifier for broadcast service #1.

[0236] In one alternative implementation, AF generates a globally unique identifier for broadcast service #1 based on the identifier of broadcast service #1 in PLMN #a and the identifier of broadcast service #1 in PLMN #b.

[0237] In this embodiment, the globally unique identifier of broadcast service #1 can be, for example, used to identify the data of broadcast service #1; or, for example, the globally unique identifier can be a number; or, for example, it can be address information used to identify broadcast service #1, etc.

[0238] As an example, the globally unique identifier for broadcast service #1 can be data used to identify broadcast service #1, such as Indication #z; as an example, for broadcast service #2, its globally unique identifier can be data used to identify broadcast service #2, such as Indication #w.

[0239] As another example, the globally unique identifier of broadcast service #1 can also be its IP multicast address. It should be noted that in this implementation, if the globally unique identifier of broadcast service #1 is its IP multicast address, step 501 can optionally be omitted. This can also be understood as the AF not needing to request the TMGI of broadcast service #1 from each PLMN in the first place. For example, if the AF subsequently sends a session creation request message to MB-SMF #b, and only carries the IP multicast address of broadcast service #1 without carrying the TMGI in PLMN #b, then MB-SMF #b will provide the AF with the TMGI of broadcast service #1 in PLMN #b.

[0240] For example, in this embodiment, in different PLMNs, the TMGI of broadcast service #1 (e.g., TMGI #x, TMGI #y) has the same indication #z (an example of the globally unique identifier of broadcast service #1). Then, the subsequent base station can identify that these different broadcast service identifiers actually correspond to the same broadcast service (i.e., broadcast service #1) in different PLMNs. In other words, although the TMGIs are different in different PLMNs (e.g., broadcast service #1 has different TMGIs in different PLMNs), they all carry the globally unique identifier of broadcast service #1, such as indication #z. Therefore, the RAN can determine that it is requesting the transmission of the same broadcast service, that is, requesting the transmission of the same broadcast data.

[0241] For example, in this embodiment, if the TMGI of broadcast service #1 (e.g., TMGI #x, TMGI #y) has the same IP multicast address in different PLMNs (another example of the globally unique identifier of broadcast service #1), then the subsequent base station can identify that these different TMGIs in different PLMNs actually correspond to the same broadcast service (i.e., broadcast service #1). In other words, although the identifier of broadcast service #1 is different in different PLMNs (e.g., broadcast service #1 has different TMGIs in different PLMNs), the requested transmission is broadcast service #1, or it can be understood as the requested transmission of broadcast data of broadcast service #1.

[0242] Step 503: AF sends a session createrequest message to MB-SMF #b in PLMN #b.

[0243] Correspondingly, MB-SMF #b in PLMN #b receives broadcast session creation requests.

[0244] This session creation request message carries a globally unique identifier for broadcast service #1. For example, this session creation request message carries the Indication #z for broadcast service #1. Another example is that this broadcast session creation request message carries the IP multicast address for broadcast service #1.

[0245] In one alternative implementation, the AF can send a session creation request to MB-SMF #b. For example, the AF sends a broadcast session creation request to MB-SMF #b by calling the Nmbsmf_MBSSession_Create Request service. This can also be understood as the AF being in the trusted domain at this point.

[0246] In another alternative implementation, the AF can first send a session creation request to the NEF, and then the NEF forwards the session creation request to the MB-SMF #b. For example, the AF sends the session creation request to the NEF by calling the Nnef_MBSSession_Create request service, and the NEF then calls the Nmbsmf_MBSSession_Create Request service to forward the session creation request to the MB-SMF #b. This can also be understood as the AF being in an untrusted domain, and the NEF may adjust some information in the broadcast session creation request. For example, because the AF is in an untrusted domain and does not know the specific cell's planning, the AF may provide geographic area information, which the NEF will "translate" into cell or tracking area information and send to the MB-SMF #b.

[0247] In this embodiment, 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, the demand information of broadcast service #1, and the area information of the broadcast.

[0248] The demand information for broadcast service #1 may include, for example, the latency requirements, priority requirements, and bandwidth requirements of broadcast service #1. Alternatively, it may include broadcast policy information, such as the 5G Quality of Service (QoS) identifier (i.e., 5QI), allocation and retention priority (ARP) information, etc.

[0249] Step 504: MB-SMF #b in PLMN #b obtains the QoS information of the broadcast service #1 session.

[0250] In one optional implementation, MB-SMF #b can send the acquired broadcast service #1 demand information to the PCF #b network element, obtain the session policy information of broadcast service #1 from the PCF #b network element, and generate the QoS information of the broadcast session based on the policy information.

[0251] In another alternative implementation, the AF can send the demand information of broadcast service #1 to PCF #b, PCF #b generates policy information for the broadcast session based on the service demand information, and PCF #b can push the policy information of the broadcast service #1 session to MB-SMF #b, MB-SMF #b generates QoS information for the broadcast session based on the policy information.

[0252] In another alternative implementation, MB-SMF #b can generate QoS information for a broadcast session based on the obtained broadcast service #1 requirements and the locally configured policy.

[0253] Step 505: MB-SMB #b selects AMF #b and sends a session startrequest message to AMF #b.

[0254] Correspondingly, AMF #b receives the session start request message.

[0255] In one alternative implementation, MB-SMF #b can combine the broadcast area information with the coverage area of ​​the AMF to select which AMF to send to.

[0256] In another alternative implementation, MB-SMF #b can also be configured to use other methods, such as sending a session start request message to all AMFs. In this case, AMF #b can accept the request sent by MB-SMF #b based on its own coverage area and the broadcast area information.

[0257] In this embodiment, the session start request message carries a globally unique identifier for broadcast service #1. For example, Indication #z; or, for example, the IP multicast address of broadcast service #1.

[0258] In addition, the session start request message may also carry one or more of the following information: for example, the identifier of broadcast service #1 in PLMN #b, TMGI #y, the area information of the broadcast (e.g., cell list information, tracking area (TA) list), and QoS information of the broadcast session.

[0259] Step 506, AMF #b selects RAN #x (e.g., the base station) and sends an N2 request message (an example of the second message) to RAN #x.

[0260] Correspondingly, RAN #x receives the N2 request message.

[0261] In one alternative implementation, AMF #b can combine the broadcast area information with the RAN coverage area to select RAN#x.

[0262] In another alternative implementation, AMF #b can also be selected in other ways, such as sending messages to all RANs. In this case, RAN #x can determine whether to accept the request sent by AMF #b based on its own coverage area and the broadcast area information.

[0263] In this embodiment, the N2 request message carries a globally unique identifier for broadcast service #1. For example, Indication #z; or, for example, the IP multicast address of broadcast service #1.

[0264] The N2 request message may also carry one or more of the following information: for example, the identifier of broadcast service #1 in PLMN #b, TMGI #y, the area information of the broadcast (e.g., cell list information, tracking area (TA) list), and QoS information of the broadcast session.

[0265] In this embodiment, 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 as the N2 request message being used to request RAN #x to establish a session context corresponding to broadcast service #1.

[0266] In this application, the information in the N2 request message sent by AMF #b to RAN #x and the information in the session start message sent by MB-SMF #b to AMF #b may not be exactly the same. For example, the N2 request message sent by AMF #b to RAN #x may also include other information generated by AMF #b. For example, tunnel identification information, identification information of the next generation application protocol (NGAP) (e.g., AMF NGAP ID, RAN NGAP ID), etc., will not be elaborated further below.

[0267] Step 507: RAN #x allocates the first resource for broadcast service #1 based on the N2 request message and establishes the broadcast session context corresponding to broadcast service #1.

[0268] The broadcast session context may include the globally unique identifier of broadcast service #1 and information about the first resource.

[0269] In this application, "the context of a broadcast session" can also be understood as "the context information of a broadcast session," which will not be elaborated further below.

[0270] In this embodiment, the first resource can also be understood as data used to send broadcast service #1 to the UE in PLMN #b.

[0271] As an example, RAN #x can allocate the corresponding first resource based on the QoS information of the broadcast session. For example, resource reservation for a QoS flow with guaranteed bit rate (GBR), etc. Specifically, the information of the first resource for broadcast service #1 determined by RAN #x may include: (1) the information of the group-radio network tempory identity (G-RNTI) for multicast reception. (2) the information of the bandwidth part (BWP) corresponding to broadcast service #1. For example, when the service is received on the BWP, the sub-carrier space (SCS), frequency domain position and cyclic prefix (CP) length corresponding to the BWP are determined according to the BWP configuration. The BWP configuration information also includes the control resource set (COREST) ​​configuration information for physical downlink control channel (PDCCH) detection, which indicates the time-frequency resource where the PDCCH for G-RNTI is located. (3) The scrambling sequence of the physical downlink data channel (PDSCH) of broadcast service #1. This can also be understood as the sequence used by the UE for descrambling when decoding the PDSCH of this service; (4) The parameters of discontinuous reception (DRX) for G-RNTI. This can also be understood as the parameters used by the UE for G-RNTI detection; (5) The configuration of the demodulation reference signal. This can also be understood as the reference signal used by the UE for demodulating the PDSCH of G-RNTI scheduling; (6) Information on the rate matching reference signal.

[0272] The broadcast session context corresponding to broadcast service #1 established by RAN #x may also include: the identifier of broadcast service #1 in PLMN #b (TMGI #y), the broadcast area information (e.g., cell list information, tracking area (TA) list), and the QoS context of the broadcast session (e.g., including the context corresponding to one or more MBS QoS flows, such as QoS flow Identifier, QoS flowlevel QoS parameters, and MBS session identification information).

[0273] Optionally, in this application, the broadcast session context may also include information about the radio bearer of the MBS session, which will not be elaborated further below.

[0274] In this application, RAN #x can determine whether it needs to store the broadcast session context based on whether it is located within the area corresponding to the broadcast area information. For example, if RAN #x determines that it is located within the area corresponding to the broadcast area information, then the broadcast session context is stored; if RAN #x determines that it is not located within the area corresponding to the broadcast area information, then the broadcast session context is not stored. This will not be elaborated further below.

[0275] Step 507 can also be understood as RAN #x searching for the broadcast session context corresponding to broadcast service #1 based on the N2 request message and the globally unique identifier of broadcast service #1 (e.g., Indication #z). If RAN #x does not find a broadcast session context containing Indication #z, then RAN #x determines that resources have not yet been allocated for broadcast service #1. Further, RAN #x allocates resources for broadcast service #1 in PLMN #b and establishes the broadcast session context corresponding to broadcast service #1.

[0276] Step 508, RAN #x sends an N2 response message to AMF #b.

[0277] For example, RAN #x sends an N2 response message to AMF #b in response to the N2 request message sent by AMF #b.

[0278] Step 509, AMF #b sends a session start response message to MB-SMF #b.

[0279] For example, AMF #b sends a session start response message to MB-SMF #b in response to the session start request message sent by MB-SMF #b.

[0280] In this application, the subsequent steps in establishing a broadcast session in each network may include, for example, configuring MB-UPF #b with MB-SMF #b (e.g., configuring MB-UPF #b to identify and forward multicast data, etc.), and sending a response message from MB-SMF #b to AF to request the session creation, etc. For details, please refer to protocol 3GPP TS 23.247, which will not be elaborated here.

[0281] Steps 503 to 509 above describe the process of establishing a broadcast session corresponding to broadcast service #1 in PLMN #b and allocating the first resource for the data of broadcast service #1. Steps 510 to 516 below describe the process of establishing a broadcast session corresponding to broadcast service #1 in PLMN #a and using the first resource allocated for broadcast service #1 in PLMN #b to send the data of broadcast service #1 to the UE in PLMN #a.

[0282] Step 510: AF sends a broadcast session createrequest message to MB-SMF #a in PLMN #a.

[0283] Correspondingly, in PLMN #a, MB-SMF #a receives broadcast session creation requests.

[0284] The broadcast session creation request message carries a globally unique identifier for broadcast service #1. For example, the broadcast session creation request message carries the Indication #z of broadcast service #1; or, for example, the broadcast session creation request message carries the IP multicast address of broadcast service #1.

[0285] In one alternative implementation, the AF can send a broadcast session creation request to MB-SMF #a. For example, the AF sends the broadcast session creation request to MB-SMF #a by calling the Nmbsmf_MBSSession_Create Request service. This can also be understood as the AF being in the trusted domain at this point.

[0286] In another alternative implementation, the AF can first send a session creation request to the NEF, and then the NEF forwards the session creation request to MB-SMF #a. For example, the AF sends the session creation request to the NEF by calling the Nnef_MBSSession_Create request service, and the NEF then calls the Nmbsmf_MBSSession_Create Request service to forward the session creation request to MB-SMF #a. This can also be understood as the AF being in an untrusted domain, and the NEF may adjust some information in the broadcast session creation request. For example, because the AF is in an untrusted domain and does not know the specific cell's planning, the AF may provide geographic area information, which the NEF will "translate" into cell or tracking area information and send to MB-SMF #a.

[0287] Specifically, the session creation request message sent by AF to MB-SMF #a carries the globally unique identifier of broadcast service #1. This session creation request message may also carry one or more of the following information: for example, the identifier of broadcast service #1 in PLMN #a, TMGI #x, the demand information of broadcast service #1, and the broadcast area information.

[0288] The demand information for broadcast service #1 may include, for example, the latency requirements, priority requirements, and bandwidth requirements of broadcast service #1. Alternatively, it may include broadcast policy information, such as the 5G Quality of Service (QoS) identifier (i.e., 5QI), allocation and retention priority (ARP) information, etc.

[0289] Step 511, MB-SMF #a in PLMN #a obtains the QoS information of the broadcast service #1 session.

[0290] In one optional implementation, MB-SMF #a can send the acquired broadcast service #1 demand information to PCF #a network element, obtain the session policy information of broadcast service #1 from PCF network element, and generate QoS information of broadcast session based on the policy information.

[0291] In another alternative implementation, MB-SMF #a can directly obtain the policy information of the broadcast service #1 session from PCF #a, and generate the QoS information of the broadcast session based on the policy information.

[0292] In another alternative implementation, MB-SMF #a can generate QoS information for a broadcast session based on the obtained broadcast service #1 requirements and the locally configured policy.

[0293] Step 512: MB-SMB #a selects the AMF #a network element and sends a session start request message to AMF #a. Correspondingly, AMF #a receives the session start request message.

[0294] In one alternative implementation, MB-SMF #a can combine the broadcast area information with the coverage area of ​​the AMF to select which AMF to send to.

[0295] In another alternative implementation, MB-SMF #a can also be configured to use other methods, such as sending a session start request message to all AMFs. In this case, AMF #a can accept the request sent by MB-SMF #a based on its own coverage area and the broadcast area information.

[0296] In this embodiment, the session start request message carries a globally unique identifier for broadcast service #1. For example, Indication #z; or, for example, the IP multicast address of broadcast service #1.

[0297] The session start request message may also carry one or more of the following information: for example, the identifier of broadcast service #1 in PLMN #a, TMGI #x, the area information of the broadcast (e.g., cell list information, tracking area (TA) list), and QoS information of the broadcast session.

[0298] Step 513, AMF #a selects RAN #x (e.g., the base station) and sends an N2 request message (an example of the first message) to RAN #x.

[0299] Correspondingly, RAN #x receives the N2 request message.

[0300] In one alternative implementation, AMF #a can combine the broadcast area information with the RAN coverage area to select RAN #x.

[0301] In another alternative implementation, AMF #a can also be selected in other ways, such as AMF #a sending messages to all RANs. In this case, RAN #x can accept the request sent by AMF based on its own coverage area and the area information being broadcast.

[0302] This can also be understood as the same RAN being selected in PLMN #b and PLMN #a, for example, RAN #x. In other words, the RAN can be shared in different networks in this application (e.g., the same RAN), which will not be elaborated further below.

[0303] In this embodiment, the N2 request message carries a globally unique identifier for broadcast service #1, for example, Indication #z; or, for example, the IP multicast address of broadcast service #1.

[0304] The N2 request message may also carry one or more of the following information: for example, the identifier of broadcast service #1 in PLMN #b, TMGI #x, broadcast area information (e.g., cell list information, tracking area (TA) list), and QoS information of the broadcast session.

[0305] In this embodiment, 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 as the N2 request message being used to request RAN #x to establish a session context corresponding to broadcast service #1.

[0306] In this embodiment, the information in the N2 request message sent by AMF #a to RAN #x and the information in the session start message sent by MB-SMF #a to AMF #a may not be exactly the same. For example, the N2 request message sent by AMF #a to RAN #x may also include other information generated by AMF #a, such as tunnel identification information, next generation application protocol (NGAP) identification information (e.g., AMF NGAP ID, RAN NGAP ID), etc.

[0307] Step 514: RAN #x determines 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 that resource; and / or, if RAN #x has not yet allocated resources for broadcast service #1, RAN #x allocates resources for broadcast service #1.

[0308] The term "resources" can be found in the descriptions in the preceding embodiments and will not be repeated here.

[0309] In one optional implementation, RAN #x looks up the broadcast session context corresponding to broadcast service #1 based on the N2 request message and the globally unique identifier of broadcast service #1, for example, Indication #z. If RAN #x determines that Indication #z is already included in the broadcast session context in PLMN #b, then RAN #x determines that resources have been allocated for broadcast service #1 and finds the information of the first resource in the broadcast session context in PLMN #b. RAN #x determines not to establish the air interface resource corresponding to broadcast service #1 in PLMN #a, and also not to establish the context corresponding to broadcast service #1 in PLMN #a. That is, RAN #x determines that data of broadcast service #1 in PLMN #a can be sent through the first resource in PLMN #b.

[0310] In another alternative implementation, if RAN #x has already allocated a second resource for broadcast service #1 in PLMN #a and established a context for broadcast service #1 in PLMN #a before looking up the globally unique identifier of broadcast service #1, and after RAN #x's lookup, it determines that a resource has already been allocated for broadcast service #1 in PLMN #b, and finds information about the first resource 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. That is, RAN #x determines that it can send the data of broadcast service #1 in PLMN #a through the first resource in PLMN #b. Alternatively, RAN #x can choose not to 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 the data of broadcast service #1 in PLMN #b.

[0311] In this application, the RAN #x function to "find the broadcast session context corresponding to broadcast service #1" can be implemented in the following ways: In one optional implementation, after receiving the globally unique identifier, RAN #x searches for the existence of the globally unique identifier in the locally stored broadcast session contexts. If a broadcast session context exists whose corresponding globally unique identifier is the same as the globally unique identifier of broadcast service #1, then the search is considered successful. Otherwise, RAN #x considers that broadcast service #1 has not yet established a context at this base station; in other words, this is the first time RAN #x has received an N2 message related to broadcast service #1. Further details will not be elaborated below.

[0312] In this application, "RAN #x sends data of broadcast service #1 in PLMN #a through this resource" can be implemented in the following way, for example. In one optional implementation, RAN #x identifies that the data belongs to broadcast service #1 based on the identification information contained in the received service data (e.g., target IP address, tunnel node identifier in GTP header, QoS flow identifier). Subsequently, RAN #x can send the data of broadcast service #1 on the air interface (e.g., time-frequency resource) based on locally stored context information (e.g., scheduling queue, reserved resources). Terminal devices located in different networks but receiving broadcast service #1 will monitor the corresponding air interface resources and thus be able to receive the data of broadcast service #1. Further details will not be elaborated below.

[0313] Step 515, RAN #x sends an N2 response message to AMF #a.

[0314] For example, RAN #x sends an N2 response message to AMF #a in response to the N2 request message sent by AMF #a.

[0315] Step 516, AMF #a sends a session start response message to MB-SMF #a.

[0316] For example, AMF #a sends a session start response message to MB-SMF #a in response to the session start request message sent by MB-SMF #a.

[0317] Based on the above technical solution, by sending a globally unique identifier for the broadcast service to the RAN, the RAN can identify the same broadcast service in scenarios where different operators share base stations. This allows the RAN to transmit the data for that broadcast service in PLMN #a using the resources already allocated for it in PLMN #b. In other words, the RAN can share air interface resources with users of different operators, thus saving RAN transmission resources and avoiding waste of air interface resources.

[0318] Figure 9 This is a schematic flowchart of a broadcast communication method 600 provided in this application. Assuming there are two PLMNs (denoted as PLMN #a and PLMN #b) in this embodiment, and taking broadcast service #2 as an example, the method includes:

[0319] Step 601: AF sends a session createrequest message to MB-SMF #b in PLMN #b.

[0320] Correspondingly, MB-SMF #b in PLMN #b receives session creation requests.

[0321] In this embodiment, after the AF sends a session creation request to the MB-SMF #b, the MB-SMF #b can provide the AF with the TMGI of broadcast service #2 in the PLMN #b, for example, TMGI #p.

[0322] Specifically, the method by which AF sends a session creation request to MB-SMF #b can be referred to step 503 in method 500.

[0323] In this embodiment, 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, the demand information of broadcast service #2, and the area information of the broadcast.

[0324] The demand information for broadcast service #2 may include, for example, the latency requirements, priority requirements, and bandwidth requirements of broadcast service #2. Alternatively, it may include broadcast policy information, such as the 5G Quality of Service (QoS) identifier (i.e., 5QI), allocation and retention priority (ARP) information, etc.

[0325] Step 602: MB-SMF #b in PLMN #b obtains the QoS information of the broadcast service #2 session.

[0326] Specifically, the method by which MB-SMF #b obtains the QoS information of the broadcast service #2 session can be referred to step 504 in method 500, and will not be repeated here.

[0327] Step 603: MB-SMB #b selects AMF #b and sends a session startrequest message to AMF #b.

[0328] Correspondingly, AMF #b receives the session start request message.

[0329] Specifically, the method for selecting AMF #b for MB-SMB #b can be referred to step 505 in method 500, and will not be repeated here.

[0330] In this embodiment, 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, the area information of the broadcast (e.g., cell list information, tracking area (TA) list), and the QoS information of the broadcast session.

[0331] Step 604, AMF #b selects RAN #x (e.g., the base station) and sends an N2 request message (an example of the second message) to RAN #x.

[0332] Correspondingly, RAN #x receives the N2 request message.

[0333] Specifically, the method for selecting RAN #x in AMF #b can be referred to step 506 in method 500, and will not be repeated here.

[0334] In this embodiment, 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, the area information of the broadcast (e.g., cell list information, tracking area (TA) list), and the QoS information of the broadcast session.

[0335] In this embodiment, the N2 request message is used to trigger RAN #x to allocate resources for broadcast service #2. In other words, the N2 request message is used to request RAN #x to allocate resources for broadcast service #2. It can also be understood as the N2 request message being used to request RAN #x to establish a session context corresponding to broadcast service #2.

[0336] Step 605: RAN #x allocates the first resource for broadcast service #2 based on the N2 request message and establishes the broadcast session context corresponding to broadcast service #2.

[0337] In this embodiment, the first resource can also be understood as data used to send broadcast service #2 to the UE in PLMN #b.

[0338] As an example, RAN #x can allocate the corresponding first resource based on the QoS information of the broadcast session. For example, resource reservation for a QoS flow with guaranteed bit rate (GBR), etc. Specifically, the information of the first resource for broadcast service #2 determined by RAN #x may include: (1) group-radio network tempory identity (G-RNTI) for multicast reception. (2) information of the bandwidth part (BWP) corresponding to broadcast service #2. For example, when the service is received on the BWP, the sub-carrier space (SCS), frequency domain position and cyclic prefix (CP) length corresponding to the BWP are determined according to the BWP configuration. The BWP configuration information also includes control resource set (COREST) ​​configuration information for physical downlink control channel (PDCCH) detection, which indicates the time-frequency resource where the PDCCH for G-RNTI is located. (3) The scrambling sequence of the physical downlink data channel (PDSCH) of broadcast service #2. This can also be understood as the sequence used by the UE for descrambling when decoding the PDSCH of this service; (4) The parameters of discontinuous reception (DRX) for G-RNTI. This can also be understood as the DRX parameters used by the UE for G-RNTI detection; (4) The configuration of the demodulation reference signal. This can also be understood as the reference signal used by the UE for demodulating the PDSCH of G-RNTI scheduling; (5) Information on the rate matching reference signal.

[0339] The broadcast session context corresponding to broadcast service #2 established by RAN #x may also include: the identifier TMGI #p of broadcast service #2 in PLMN #b, broadcast area information (e.g., cell list information, tracking area (TA) list), and the QoS context of the broadcast session.

[0340] Step 606: RAN #x sends an N2 response message to AMF #b.

[0341] For example, RAN #x sends an N2 response message to AMF #b in response to the N2 request message sent by AMF #b.

[0342] Step 607: AMF #b sends a session start response message to MB-SMF #b.

[0343] For example, AMF #b sends a session start response message to MB-SMF #b in response to the session start request message sent by MB-SMF #b.

[0344] Step 608, MB-SMF #b configures MB-UPF #b.

[0345] For example, MB-SMF #b sends an N4 Sessionestablishment / modification message (an example of the fourth message) to MB-UPF #b. This message may contain one or more of the following: identification information for broadcast service #2, and indication information #1 (an example of the first indication information). Indication information #1 instructs MB-UPF #b to detect the IP multicast address of broadcast service #2 (an example of the globally unique identifier of broadcast service #2). For example, MB-UPF #b detects the IP multicast address of the downlink data packets of broadcast service #2 (e.g., the destination IP address, source IP address, etc.). Afterward, the data for broadcast service #2 can be transmitted in the core network and at RAN #x.

[0346] Step 609: MB-UPF #b sends a notification message (e.g., a Notification message) to MB-SMF #b, carrying the IP multicast address of broadcast service #2. MB-SMF #b then receives this notification message.

[0347] Step 610: MB-SMF #b sends the IP multicast address of broadcast service #2 to the RAN.

[0348] For example, MB-SMF #b first sends the IP multicast address to AMF #b by calling AMF's Namf_MBSBroadcast_ContextUpdate service, and then AMF #b sends it to RAN #x via an N2 message.

[0349] Step 611, RAN #x stores the IP multicast address of broadcast service #2 in the broadcast session context established in PLMN #b.

[0350] For example, RAN #x stores the IP multicast address of the downlink data packet of broadcast service #2 as part of the broadcast session context.

[0351] Steps 601 to 611 above describe the process of establishing a broadcast session corresponding to broadcast service #2 in PLMN #b, allocating first resources for the data of broadcast service #2, and storing the globally unique identifier of broadcast service #2 in the broadcast session context. Steps 612 to 622 below describe the process of establishing a broadcast session corresponding to broadcast service #2 in PLMN #a and using the first resources allocated for broadcast service #2 in PLMN #b to send the data of broadcast service #2 to the UE in PLMN #a.

[0352] Steps 612 to 615 can be referred to the description of steps 601 to 604 above. The difference is that steps 612 to 615 are all in PLMH# a, and the relevant core network elements involved are also core network elements in PLMH# a.

[0353] Optionally, in step 616, RAN #x allocates the first resource for broadcast service #2 based on the N2 request message, and establishes a broadcast session context corresponding to broadcast service #2.

[0354] Specifically, refer to the description of step 605. The difference is that at this time, RAN #x allocates the second resource for broadcast service #2 in PLMN #a, which will not be elaborated here.

[0355] Steps 617 and 618 can be referred to as steps 606 and 607 above. The difference is that steps 617 and 618 are all in PLMH# a, and the relevant core network elements involved are also core network elements in PLMH# a.

[0356] Step 619, MB-SMF #a configures MB-UPF #a.

[0357] For example, MB-SMF #a sends an N4 session establishment / modification message (an example of the fourth message) to MB-UPF #a. This message may contain one or more of the following: identification information for broadcast service #2, and indication information #2 (an example of the first indication information). Indication information #2 instructs MB-UPF #a to detect the IP multicast address of broadcast service #2 (an example of the globally unique identifier of broadcast service #3). For example, MB-UPF #a detects the IP multicast address of the downlink data packets of broadcast service #2 (e.g., the destination IP address, source IP address, etc.). Afterward, the data for broadcast service #2 can be transmitted in the core network and at RAN #x.

[0358] Step 620: MB-UPF #a sends a notification message (e.g., a Notification message) to MB-SMF #a, carrying the IP multicast address of broadcast service #2.

[0359] Correspondingly, MB-SMF #a receives this notification message.

[0360] Step 621, MB-SMF #a sends the IP multicast address of broadcast service #2 to RAN #x.

[0361] For example, MB-SMF #a first sends the IP multicast address to AMF #a by calling the AMF's Namf_MBSBroadcast_ContextUpdate service, and then AMF #a sends it to RAN #x via an N2 message.

[0362] 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, then the data of broadcast service #2 in PLMN #a is sent through that resource; and / or, if RAN has not yet allocated resources for broadcast service #2, then RAN #x allocates resources for broadcast service #2.

[0363] The term "resources" can be found in the descriptions in the preceding embodiments and will not be repeated here.

[0364] In one alternative implementation, RAN #x looks up the broadcast session context corresponding to broadcast service #2 based on the N2 request message and the globally unique identifier of broadcast service #2, such as the IP multicast address of broadcast service #2. If RAN #x determines that the IP multicast address of broadcast service #2 is already included in the broadcast session context in PLMN #b, then RAN #x determines that resources have been allocated for broadcast service #2 and finds the information of the first resource in the broadcast session context in PLMN #b. RAN #x can then 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, and use the first resource allocated for broadcast service #1 in PLMN #b to send the data of broadcast service #2 in PLMN #a. Alternatively, 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 the data of broadcast service #2 in PLMN #a.

[0365] In another optional implementation, RAN #x does not execute step 616. In this case, RAN #x will not allocate the second resource for broadcast service #2 in PLMN #a, and will directly execute steps 617 to 622. At this point, RAN #x, based on the N2 request message and the globally unique identifier of broadcast service #2, such as the IP multicast address of broadcast service #2, looks up the broadcast session context corresponding to broadcast service #2. RAN #x determines that the IP multicast address of broadcast service #2 is already contained in the broadcast session context in PLMN #b. Therefore, RAN #x determines that resources have already been allocated for broadcast service #1, and since the information of the first resource is found in the broadcast session context in PLMN #b, RAN #x determines not to establish the air interface resource corresponding to broadcast service #2 in PLMN #a, and also not to establish the context corresponding to broadcast service #2 in PLMN #a. That is, RAN #x determines that data from broadcast service #2 in PLMN #a can be sent through the first resource in PLMN #b.

[0366] Based on the above technical solution, by sending a globally unique identifier for the broadcast service to the RAN, the RAN can identify the same broadcast service in scenarios where different operators share base stations. This allows the RAN to transmit the data for that broadcast service in PLMN #a using the resources already allocated for it in PLMN #b. In other words, the RAN can share air interface resources with users of different operators, thus saving RAN transmission resources and avoiding waste of air interface resources.

[0367] Figure 10 This is a schematic flowchart of a broadcast communication method 700 provided in this application. Assuming there are two PLMNs (denoted as PLMN #a and PLMN #b) in this embodiment, and using broadcast service #3 as an example, the method includes:

[0368] Step 701: AF requests the identifier of broadcast service #3 in different PLMNs from different PLMN networks.

[0369] For example, AF requests the identifier of broadcast service #3 from MB-SMF #a in PLMN #a. Suppose that AF obtains the identifier of broadcast service #3 in PLMN #a as TMGI #m; similarly, AF requests the identifier of broadcast service #3 from MB-SMF #b in PLMN #b. Suppose that AF obtains the identifier of broadcast service #3 in PLMN #b as TMGI #n.

[0370] Step 702: AF sends a session createrequest message to MB-SMF #b in PLMN #b.

[0371] Correspondingly, MB-SMF #b in PLMN #b receives broadcast session creation requests.

[0372] In one alternative implementation, the session creation request message carries a list of broadcast service identifiers for broadcast service #3 in each PLMN network. For example, the identifier is TMGI #m in PLMN #a and TMGI #n in PLMN #b.

[0373] In another optional implementation, the list of broadcast service identifiers for broadcast service #3 in each PLMN network can also be pre-configured on the RAN (e.g., RAN #x). In this case, the AF does not need to provide this list in the session creation request message. "Pre-configured" can be understood as follows: the RAN is already configured with the list of broadcast service identifiers for broadcast service #3 in each PLMN network. Therefore, when requesting to establish a broadcast session in each network, only the identifier of broadcast service #3 in that network needs to be carried, without carrying the entire list. Alternatively, it can be understood as follows: the RAN receives the pre-configured list of identifiers for broadcast service #3 in each network when establishing the first broadcast service session for the first time, and the RAN can store this list. Therefore, when requesting to establish a broadcast service #3 session for subsequent times (e.g., the second time), only the identifier of broadcast service #3 in that network needs to be carried, without carrying the entire list. Further details will not be elaborated below.

[0374] Specifically, the method by which AF sends a session creation request message to MB-SMF #b in PLMN #b can be referred to step 503 in method 500, and will not be repeated here.

[0375] Step 703: MB-SMF #b in PLMN #b obtains the QoS information of the broadcast service #3 session.

[0376] Specifically, the method by which MB-SMF #b in PLMN #b obtains the QoS information of the broadcast service #3 session can be referred to step 504 in method 500, and will not be repeated here.

[0377] Step 704: MB-SMB #b selects AMF #b and sends a session startrequest message to AMF #b.

[0378] Correspondingly, AMF #b receives the session start request message.

[0379] Specifically, the method for selecting AMF in MB-SMF #b of PLMN #b can be referred to step 505 in method 500, and will not be repeated here.

[0380] In this embodiment, the session start request message may carry a list of broadcast service identifiers for broadcast service #3 in various PLMN networks. For example, the identifier in PLMN #a is TMGI #m, and the identifier in PLMN #b is TMGI #n.

[0381] The session start request message may also carry one or more of the following information: for example, the identifier of broadcast service #3 in PLMN #b, TMGI #n, the area information of the broadcast (e.g., cell list information, tracking area (TA) list), and QoS information of the broadcast session.

[0382] Step 705, AMF #b selects RAN #x (e.g., the base station) and sends an N2 request message (an example of the second message) to RAN #x.

[0383] Correspondingly, RAN #x receives the N2 request message.

[0384] Specifically, the method for selecting RAN #x in AMF #b can be referred to step 506 in method 500, and will not be repeated here.

[0385] In this embodiment, the N2 request message carries a list of broadcast service identifiers for broadcast service #3 in each PLMN network. For example, the identifier in PLMN #a is TMGI #m, and the identifier in PLMN #b is TMGI #n.

[0386] The N2 request message may also carry one or more of the following information: for example, the identifier of broadcast service #3 in PLMN #b, TMGI #n, broadcast area information (e.g., cell list information, tracking area (TA) list), and QoS information of the broadcast session.

[0387] In this embodiment, the N2 request message is used to trigger the RAN to allocate resources for broadcast service #3. In other words, the N2 request message is used to request RAN #x to allocate resources for broadcast service #3. It can also be understood as the N2 request message being used to request RAN #x to establish a session context corresponding to broadcast service #3.

[0388] Step 706: RAN #x allocates the first resource for broadcast service #3 based on the N2 request message, and establishes the broadcast session context corresponding to broadcast service #3.

[0389] The broadcast session context includes a list of broadcast service identifiers for broadcast service #3 in each PLMN network. For example, the identifier is TMGI #m in PLMN #a and TMGI #n in PLMN #b.

[0390] In this embodiment, the first resource can also be understood as data used to send broadcast service #3 to the UE in PLMN #b.

[0391] As an example, RAN #x can allocate the corresponding first resource based on the QoS information of the broadcast session. For example, resource reservation for a QoS flow with guaranteed bit rate (GBR), etc. Specifically, the information of the first resource for broadcast service #3 determined by RAN #x may include: (1) the information of the group-radio network tempory identity (G-RNTI) for multicast reception. (2) the information of the bandwidth part (BWP) corresponding to broadcast service #3. For example, when the service is received on the BWP, the sub-carrier space (SCS), frequency domain position and cyclic prefix (CP) length corresponding to the BWP are determined according to the BWP configuration. The BWP configuration information also includes the control resource set (COREST) ​​configuration information for physical downlink control channel (PDCCH) detection, which indicates the time-frequency resource where the PDCCH for G-RNTI is located. (3) The scrambling sequence of the physical downlink data channel (PDSCH) of broadcast service #3. This can also be understood as the sequence used by the UE for descrambling when decoding the PDSCH of this service; (4) The parameters of discontinuous reception (DRX) for G-RNTI. This can also be understood as the DRX parameters used by the UE for G-RNTI detection; (5) The configuration of the demodulation reference signal. This can also be understood as the reference signal used by the UE for demodulating the PDSCH of G-RNTI scheduling; (6) Information on the rate matching reference signal.

[0392] The broadcast session context corresponding to broadcast service #3 established by RAN #x may also include: the identifier TMGI #n of broadcast service #3 in PLMN #b, broadcast area information (e.g., cell list information, tracking area (TA) list), and the QoS context of the broadcast session.

[0393] Step 706 can also be understood as follows: 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 for broadcast service #3 in each PLMN network. If RAN #x does not find a broadcast session context containing the list of broadcast service identifiers for broadcast service #3 in each PLMN network, then RAN #x determines that resources have not yet been allocated for broadcast service #3, and needs to allocate resources for broadcast service #3 in PLMN #b and establish the broadcast session context corresponding to broadcast service #3.

[0394] Step 707, RAN #x sends an N2 response message to AMF #b.

[0395] For example, RAN #x sends an N2 response message to AMF #b in response to the N2 request message sent by AMF #b.

[0396] Step 708: AMF #b sends a session start response message to MB-SMF #b.

[0397] For example, AMF #b sends a session start response message to MB-SMF #b in response to the session start request message sent by MB-SMF #b.

[0398] Steps 702 to 708 above describe the process of establishing a broadcast session corresponding to broadcast service #3 in PLMN #b and allocating the first resource for the data of broadcast service #3. Steps 709 to 715 below describe the process of establishing a broadcast session corresponding to broadcast service #3 in PLMN #a and using the first resource allocated for broadcast service #3 in PLMN #b to send the data of broadcast service #3 to the UE in PLMN #a.

[0399] Step 709, AF sends a session createrequest message (an example of the fourth message) to MB-SMF #a in PLMN #a.

[0400] Correspondingly, in PLMN #a, MB-SMF #a receives broadcast session creation requests.

[0401] In one alternative implementation, the broadcast session creation request message carries a list of broadcast service identifiers for broadcast service #3 in each PLMN network. For example, the identifier is TMGI #m in PLMN #a, TMGI #n in PLMN #b, and so on.

[0402] In another alternative implementation, if the list of broadcast service identifiers for broadcast service #3 in each PLMN network is pre-configured on the RAN (e.g., RAN #x), or if the list has already been provided to the RAN in PLMN #b, then in PLMN #a, the broadcast session creation request message can carry only the identifier of broadcast service #3 in PLMN #a, such as TMGI #m, without having to provide the complete list to the RAN.

[0403] Specifically, the method by which AF sends a session creation request message to MB-SMF #a in PLMN #a can be referred to step 510 in method 500, and will not be repeated here.

[0404] Step 710: MB-SMF #a in PLMN #a obtains the QoS information of the broadcast service #3 session.

[0405] Specifically, the QoS information of the broadcast service #3 session obtained by MB-SMF #a in PLMN #a can be found in step 511 of method 500, which will not be repeated here.

[0406] Step 711: MB-SMB #a selects the AMF network element and sends a session start request message (an example of a third message) to AMF #a.

[0407] Correspondingly, AMF #a receives the session start request message.

[0408] Specifically, the method for selecting AMF #a from MB-SMF #a in PLMN #a can be referred to step 512 in method 500, and will not be repeated here.

[0409] In one alternative implementation, the broadcast session begins by requesting a list of broadcast service identifiers for broadcast service #3 across various PLMN networks. For example, the identifier in PLMN #a is TMGI #m, and the identifier in PLMN #b is TMGI #n.

[0410] In another alternative implementation, if the list of broadcast service identifiers for broadcast service #3 in each PLMN network is pre-configured on the RAN (e.g., RAN #x), or if the list has already been provided to the RAN in PLMN #b, then in PLMN #a, the broadcast session start request message can carry only the identifier of broadcast service #3 in PLMN #a, such as TMGI #m, without having to provide the complete list to the RAN.

[0411] Step 712, AMF #a selects RAN #x (e.g., the base station) and sends an N2 request message (an example of the second message) to RAN #x.

[0412] Correspondingly, RAN #x receives the N2 request message.

[0413] Specifically, the method for selecting RAN #x in AMF #a can be referred to step 513 in method 500, which will not be repeated here.

[0414] In one alternative implementation, the N2 request includes a list of broadcast service identifiers for broadcast service #3 in each PLMN network. For example, the identifier is TMGI #m in PLMN #a and TMGI #n in PLMN #b.

[0415] In another alternative implementation, the N2 request carries the broadcast service identifier for broadcast service #3 in the PLMN #a network. For example, the identifier in PLMN #a is TMGI #m.

[0416] The N2 request message may also carry one or more of the following information: for example, the identifier of broadcast service #3 in PLMN #b, TMGI #n, broadcast area information (e.g., cell list information, tracking area (TA) list), and QoS information of the broadcast session.

[0417] Step 713: RAN #x determines whether resources have already been allocated for broadcast service #3 based on the N2 request message and the list of broadcast service identifiers for broadcast service #3 in each PLMN network or the broadcast service identifier in PLMN #a network. If resources have already been allocated for broadcast service #3, then the data for broadcast service #3 in PLMN #a is sent through that resource; and / or, if RAN #x has not yet allocated resources for broadcast service #3, then RAN #x allocates resources for broadcast service #3.

[0418] The term "resources" can be found in the descriptions in the preceding embodiments and will not be repeated here.

[0419] In one optional implementation, RAN #x, based on the N2 request message and a list of broadcast service identifiers for broadcast service #3 in each PLMN network (e.g., TMGI #m in PLMN #a and TMGI #n in PLMN #b), searches for the broadcast session context corresponding to broadcast service #3. If RAN #x determines that the broadcast session context in PLMN #b already contains the list of broadcast service identifiers for broadcast service #3 in each PLMN network, then RAN #x determines that resources have already been allocated for broadcast service #3 and finds the information of the first resource in the broadcast session context in PLMN #b. Therefore, RAN #x determines not to establish the air interface resource corresponding to broadcast service #3 in PLMN #a, and not to establish the context corresponding to broadcast service #3 in PLMN #a. That is, RAN #x determines that the data of broadcast service #3 in PLMN #a can be sent through the first resource in PLMN #b.

[0420] In another optional implementation, RAN #x, based on the N2 request message and the broadcast service identifier TMGI #m of broadcast service #3 in PLMN #a network, looks up the broadcast session context corresponding to broadcast service #3. If RAN #x determines that the broadcast session context in PLMN #b already contains the broadcast service identifier TMGI #m of broadcast service #3 in PLMN #a network, then RAN #x determines that resources have already been allocated for broadcast service #3 and finds the information of the first resource in the broadcast session context in PLMN #b. Therefore, RAN #x determines not to establish the air interface resource corresponding to broadcast service #3 in PLMN #a, and not to establish the context corresponding to broadcast service #3 in PLMN #a. That is, RAN #x determines that the data of broadcast service #3 in PLMN #a can be sent through the first resource in PLMN #b.

[0421] This can also be understood as follows: When RAN #x searches for the broadcast session context corresponding to broadcast service #3, if it finds that the broadcast service identifier for broadcast service #3 stored in that context overlaps with the identifier for broadcast service #3 carried in the N2 request message, then RAN #x determines that resources have already been allocated for broadcast service #3 and that the information of the first resource has been found in the broadcast session context in PLMN #b. Therefore, RAN #x determines not to establish the air interface resource corresponding to broadcast service #3 in PLMN #a, and not to establish the context corresponding to broadcast service #3 in PLMN #a. In other words, RAN #x determines that it can send the data of broadcast service #3 in PLMN #a through the first resource in PLMN #b.

[0422] In another alternative implementation, if RAN #x has already allocated a second resource for broadcast service #3 in PLMN #a and established a context for broadcast service #3 in PLMN #a before searching the list of broadcast service identifiers for broadcast service #3 in each PLMN network or in PLMN #a network, and after RAN #x determines that resources have already been allocated for broadcast service #3 in PLMN #b and finds information about the first resource 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. Alternatively, RAN #x can choose not to send the data of broadcast service #3 in PLMN #a on the second resource, but still use the first resource allocated for broadcast service #1 in PLMN #b to send the data of broadcast service #3 in PLMN #a.

[0423] Step 714, RAN #x sends an N2 response message to AMF #a.

[0424] For example, RAN #x sends an N2 response message to AMF #a in response to the N2 request message sent by AMF #a.

[0425] Step 715, AMF #a sends a session start response message to MB-SMF #a.

[0426] For example, AMF #a sends a session start response message to MB-SMF #a in response to the session start request message sent by MB-SMF #a.

[0427] Based on the above technical solution, by sending the identifier of the broadcast service in each PLMN or in PLMN #a to the RAN, the RAN can identify the same broadcast service in scenarios where different operators share base stations. This allows the RAN to transmit the data of the broadcast service in PLMN #a using the resources already allocated for that broadcast service in PLMN #b. In other words, the RAN can share air interface resources with users of different operators, thus saving RAN transmission resources and avoiding waste of air interface resources.

[0428] Figure 11 This is a schematic flowchart of a broadcast communication method 800 provided in this application. Assuming there are two PLMNs (denoted as PLMN #a and PLMN #b) in this embodiment, and using broadcast service #4 as an example, the method includes:

[0429] This embodiment assumes that PLMN #a and PLMN #b are configured with a common TMGI, which allows the MB-SMF of PLMN #a and PLMN #b to provide a common TMGI when the AF requests a TMGI. In this application, "common TMGI" means that one or more TMGIs can be shared by several (i.e., at least two) PLMN networks. In the original definition, TMGI includes PLMN ID information and information within the PLMN; it can also be understood as TMGI being specific to each PLMN (i.e., PLMN-specific). However, in this embodiment, it is assumed that each PLMN can share a TMGI (TMGI can be PLMN-specific or non-PLMN-specific, but can be shared across different PLMNs). For example, for broadcast service #4, the TMGI in PLMN #a is the same as the TMGI in PLMN #b, both being TMGI #q.

[0430] This embodiment also assumes the existence of a "central database" (an example of the first network element), which stores the correspondence between various broadcast service identifiers and general TMGIs. For example, each network's MB-SMF can store the correspondence between TMGIs and broadcast service identifiers in the UDM, UDR, NRF, NEF, PCF, or a dedicated multicast / broadcast database (which can be shared by multiple PLMNs). This allows for a direct request from the central database for a general TMGI for a specific broadcast service identifier.

[0431] Step 801: The AF sends a request message #1 (an example of a third message) to the MB-SMF #b in PLMN #b. Request message #1 carries the identifier of broadcast service #4 (e.g., the IP multicast address of broadcast service #4). Request message #1 is used to request the TMGI of broadcast service #4. Correspondingly, MB-SMF #b receives the request message.

[0432] Specifically, request message #1 can be used to trigger MB-SMF #b to send TMGI of broadcast service #4 to AF.

[0433] For example, AF sends a TMGI allocation request message to MB-SMF #b to request the TMGI for broadcast service #4.

[0434] 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 broadcast service #4 and obtains the TMGI of broadcast service #4.

[0435] Specifically, request message #2 can be used to trigger the central database to send broadcast service #4 via TMGI.

[0436] For example, request message #2 could be a session create request message, requesting to find the TMGI for broadcast service #4. Alternatively, request message #2 could also be a TMGI allocation request message or a TMGI query request message; the specifics are not limited here.

[0437] In one alternative implementation, when allocating a TMGI, MB-SMF #b can look up the TMGI of broadcast service #4 in the central database and obtain the general TMGI corresponding to broadcast service #4 as TMGI #q.

[0438] In another alternative implementation, when allocating a TMGI, MB-SMF #b can look up the TMGI of broadcast service #4 in the central database. If MB-SMF #b does not find the TMGI of broadcast service #4, then MB-SMF #b allocates a TMGI for broadcast service #4 (for example, the allocated TMGI is TMGI #q) and stores it in the central database.

[0439] Step 803: The central database sends a response message #2 to MB-SMF #b in response to request message #2. This response message #2 carries the general TMGI of broadcast service #4, TMGI #q.

[0440] Step 804, MB-SMF #b sends a response message #1 to AF for request message #1, which carries the general TMGI of broadcast service #4, for example, TMGI #q.

[0441] For example, response message #1 is a TMGI allocation request message.

[0442] In step 805, the AF sends a session create request message to the MB-SMF #b in PLMN #b. Correspondingly, the MB-SMF #b in PLMN #b receives the broadcast session create request.

[0443] The session creation request message carries the general TMGI corresponding to broadcast service #4, for example, TMGI #q.

[0444] Specifically, 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 demand information for broadcast service #4, and the area information of the broadcast.

[0445] The broadcast service #4's requirement information may include, for example, the latency requirement, priority requirement, and bandwidth requirement of broadcast service #4. Alternatively, it may include broadcast policy information, such as the 5G Quality of Service (QoS) identifier (i.e., 5QI), allocation and retention priority (ARP) information, etc.

[0446] Specifically, the implementation of AF sending a session creation request message to MB-SMF #b in PLMN #b can be referred to step 503 in method 500, and will not be repeated here.

[0447] Step 806: MB-SMF #b in PLMN #b obtains the QoS information of the broadcast service #4 session.

[0448] Specifically, the method by which MB-SMF #b in PLMN #b obtains the QoS information of the broadcast service #4 session can be referred to step 504 in method 500, and will not be repeated here.

[0449] In step 807, MB-SMB #b selects AMF #b and sends a session start request message to AMF #b. Correspondingly, AMF #b receives the session start request message.

[0450] Specifically, the method for selecting AMF in MB-SMF #b of PLMN #b can be referred to step 505 in method 500, and will not be repeated here.

[0451] Specifically, the session start request message carries the generic TMGI corresponding to broadcast service #4, for example, TMGI #q.

[0452] The session start request message may also carry one or more of the following information: broadcast area information (e.g., cell list information, tracking area (TA) list), and QoS information for the broadcast session.

[0453] In step 808, AMF #b selects RAN #x (e.g., the base station) and sends an N2 request message (an example of the second message) to the RAN. Correspondingly, RAN #x receives the N2 request message.

[0454] Specifically, the method for selecting RAN #x in AMF #b can be referred to step 506 in method 500, and will not be repeated here.

[0455] In this embodiment, the N2 request message carries the general TMGI corresponding to broadcast service #4, for example, TMGI #q.

[0456] The N2 request message may also carry one or more of the following information: broadcast area information (e.g., cell list information, tracking area (TA) list), and QoS information for the broadcast session.

[0457] In this embodiment, 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 as the N2 request message being used to request RAN #x to establish the session context corresponding to broadcast service #4.

[0458] Step 809: RAN #x allocates the first resource for broadcast service #4 based on the N2 request message and establishes the broadcast session context corresponding to broadcast service #4.

[0459] The broadcast session context includes the generic TMGI corresponding to broadcast service #4, for example, TMGI #q.

[0460] The first resource can also be understood as the data used to send broadcast service #4 to the UE in PLMN #b.

[0461] As an example, RAN #x can allocate the corresponding first resource based on the QoS information of the broadcast session. For example, resource reservation for a QoS flow with guaranteed bit rate (GBR). Specifically, the information of the first resource for broadcast service #1 determined by RAN #x may include: (1) information of the group-radio network tempory identity (G-RNTI) for multicast reception. (2) information of the bandwidth part (BWP) corresponding to broadcast service #4. For example, when the service is received on the BWP, the sub-carrier space (SCS), frequency domain position and cyclic prefix (CP) length corresponding to the BWP are determined according to the BWP configuration. The BWP configuration information also includes the control resource set (COREST) ​​configuration information for physical downlink control channel (PDCCH) detection, which indicates the time-frequency resource where the PDCCH for G-RNTI is located. (3) The scrambling sequence of the physical downlink data channel (PDSCH) of broadcast service #4. This can also be understood as the sequence used by the UE for descrambling when decoding the PDSCH of this service; (4) The parameters of discontinuous reception (DRX) for G-RNTI. This can also be understood as the DRX parameters used by the UE for G-RNTI detection; (5) The configuration of the demodulation reference signal. This can also be understood as the reference signal used by the UE for demodulating the PDSCH of G-RNTI scheduling; (6) Information on the rate matching reference signal.

[0462] The broadcast session context corresponding to the broadcast service #4 established by RAN #x may also include: broadcast area information (e.g., cell list information, tracking area (TA) list), and the QoS context of the broadcast session.

[0463] Step 809 can also be understood as RAN #x searching for the broadcast session context corresponding to broadcast service #4 based on the N2 request message and the general TMGI corresponding to broadcast service #4: TMGI #q. If RAN #x does not find a broadcast session context containing TMGI #q, then RAN #x determines that resources have not yet been allocated for broadcast service #4, and needs to allocate resources for broadcast service #4 in PLMN #b and establish the broadcast session context corresponding to broadcast service #1.

[0464] Step 810, RAN #x sends an N2 response message to AMF #b.

[0465] For example, RAN #x sends an N2 response message to AMF #b in response to the N2 request message sent by AMF #b.

[0466] Step 811, AMF #b sends a session start response message to MB-SMF #b.

[0467] For example, AMF #b sends a session start response message to MB-SMF #b in response to the session start request message sent by MB-SMF #b.

[0468] Steps 801 to 811 above describe the process of establishing a broadcast session corresponding to broadcast service #4 in PLMN #b and allocating the first resource for the data of broadcast service #4. Steps 812 to 822 below describe the process of establishing a broadcast session corresponding to broadcast service #4 in PLMN #a and using the first resource allocated for broadcast service #4 in PLMN #b to send the data of broadcast service #4 to the UE in PLMN #a.

[0469] In step 812, the AF sends a request message #3 (an example of the fifth message) to MB-SMF #a in PLMN #a, requesting TMGI for broadcast service #4. MB-SMF #a receives the request message accordingly.

[0470] Specifically, request message #3 can be used to trigger MB-SMF #a to send the general TMGI corresponding to broadcast service #4 to AF.

[0471] For example, AF sends a TMGI allocation request message to MB-SMF #a to request the TMGI for broadcast service #4.

[0472] 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 broadcast service #4.

[0473] Specifically, the method for MB-SMF #a to obtain the TMGI of broadcast service #4 can be referred to in step 802, and will not be repeated here.

[0474] Step 814: The central database sends a response message #4 to MB-SMF #a in response to request message #4. This response message #4 carries the general TMGI of broadcast service #4, TMGI #q.

[0475] Step 815, MB-SMF #a sends a response message #3 to AF for request message #3, which carries the general TMGI of broadcast service #4, for example, TMGI #q.

[0476] For example, response message #1 is a TMGI allocation request message.

[0477] Step 816: AF sends a session create request message to MB-SMF #a in PLMN #a. Correspondingly, MB-SMF #a in PLMN #a receives the broadcast session create request.

[0478] Specifically, the session creation request message carries the generic TMGI corresponding to broadcast service #4, for example, TMGI #q.

[0479] Specifically, the session creation request message sent by AF to MB-SMF #a may also carry one or more of the following information: for example, the demand information for broadcast service #4, and the area information of the broadcast.

[0480] The broadcast service #4's requirement information may include, for example, the latency requirement, priority requirement, and bandwidth requirement of broadcast service #4. Alternatively, it may include broadcast policy information, such as the 5G Quality of Service (QoS) identifier (i.e., 5QI), allocation and retention priority (ARP) information, etc.

[0481] Specifically, the implementation of AF sending a session creation request message to MB-SMF #a in PLMN #a can be referred to step 510 in method 500, and will not be repeated here.

[0482] Step 817: MB-SMF #a in PLMN #a obtains the QoS information of the broadcast service #4 session.

[0483] Specifically, the method by which MB-SMF #a obtains the QoS information of the broadcast service #4 session can be referred to step 511 in method 500, and will not be repeated here.

[0484] In step 818, MB-SMB #a selects the AMF #a network element and sends a session start request message (an example of a third message) to AMF #a. Correspondingly, AMF #a receives the session start request message.

[0485] Specifically, the method for selecting AMF #a for MB-SMB #a can be referred to step 512 in method 500.

[0486] Specifically, the session begins by requesting a generic TMGI for broadcast service #4 in the request message, for example, TMGI #q.

[0487] The session start request message may also carry one or more of the following information: broadcast area information (e.g., cell list information, tracking area (TA) list), and QoS information for the broadcast session.

[0488] Step 819, AMF #a selects RAN #x (e.g., the base station) and sends an N2 request message (an example of the first message) to the RAN.

[0489] Correspondingly, the RAN receives the N2 request message.

[0490] Specifically, the AMF #a selection of RAN #x mode can be referred to step 513 in method 500.

[0491] The session start request message carries a generic TMGI for broadcast service #4, for example, TMGI #q.

[0492] The session creation request message sent by AF to MB-SMF #a may also carry one or more of the following information: for example, the demand information for broadcast service #4, and the area information of the broadcast.

[0493] The broadcast service #4's requirement information may include, for example, the latency requirement, priority requirement, and bandwidth requirement of broadcast service #4. Alternatively, it may include broadcast policy information, such as the 5G Quality of Service (QoS) identifier (i.e., 5QI), allocation and retention priority (ARP) information, etc.

[0494] 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, then the data of broadcast service #4 in PLMN #a is sent through those resources; and / or, if RAN #x has not yet allocated resources for broadcast service #4, then RAN #x allocates resources for broadcast service #4.

[0495] In one alternative implementation, since a first resource has already been allocated in PLMN #b for the first broadcast service (i.e., the broadcast service identified by TMGI #q), RAN #x determines, based on the N2 request message and the general TMGI of broadcast service #4, such as TMGI #q, that it can send the data of broadcast service #4 in PLMN #a using the first resource in PLMN #b. In other words, in this embodiment, since RAN #x receives TMGI #q in both PLMN #b and PLMN #a, RAN #x does not need to look up the broadcast session context corresponding to the first broadcast service and can directly use the first resource in PLMN #b to send the data of broadcast service #4 in PLMN #a.

[0496] Step 821, RAN #x sends an N2 response message to AMF #a.

[0497] For example, RAN #x sends an N2 response message to AMF #a in response to the N2 request message sent by AMF #a.

[0498] Step 822, AMF #a sends a session start response message to MB-SMF #a.

[0499] For example, AMF #a sends a session start response message to MB-SMF #a in response to the session start request message sent by MB-SMF #a.

[0500] Based on the above technical solution, by sending a universal TMGI for broadcast services across various networks to the RAN, the RAN can identify the same broadcast service in scenarios where different operators share base stations. This allows the RAN to transmit the data for that broadcast service in PLMN #a using the resources already allocated for it in PLMN #b. In other words, the RAN can share air interface resources with users of different operators, thus saving RAN transmission resources and avoiding waste of air interface resources.

[0501] It is understood that in the embodiments of this application... Figures 4 to 8 The examples provided are merely to facilitate understanding of the embodiments of this application by those skilled in the art, and are not intended to limit the embodiments of this application to the specific scenarios illustrated. Figures 4 to 8 The examples are obviously subject to various equivalent modifications or changes, and such modifications or changes also fall within the scope of the embodiments of this application.

[0502] It is also understood that some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0503] It is also understood that the various embodiments described in this application can be independent solutions or combinations based on internal logic, and all such solutions fall within the protection scope of this application. Furthermore, the explanations or descriptions of the various terms appearing in the embodiments can be referenced or interpreted in conjunction with each other in the various embodiments, and are not limited thereto.

[0504] It is also understood that the various numerical sequences in the embodiments of this application do not imply the order of execution, but are merely distinctions for ease of description and should not constitute any limitation on the implementation process of the embodiments of this application. For example, in method 500, step 503 and step 510 can be performed simultaneously, that is, AF can simultaneously receive session creation requests for broadcast services sent by MB-SMF#b in PLMN#b and MB-SMF#a in PLMN#a.

[0505] In this application, "broadcast service" and "broadcast session" can also be understood as "multicast service" and "multicast session". The above technical solutions are only used as examples of "broadcast service" and "broadcast session" and are not intended to be limiting.

[0506] It is also understood that some message names are involved in the various embodiments of this application, and their naming does not limit the scope of protection of the embodiments of this application.

[0507] It should be understood that the predefined in this application can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0508] It is understood that in this application, "under certain circumstances", "if" and "if" all refer to the device making a corresponding processing under certain objective circumstances, and are not limited to a time, nor do they require the device to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0509] It is understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0510] The above mainly describes the solution provided by the embodiments of this application from the perspective of interaction between various nodes. It is understood that 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, includes corresponding hardware structures and / or software modules to perform the above functions. Those skilled in the art should recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0511] This application embodiment can divide the wireless access network device and its various core network elements into functional modules based on the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the division of functional modules according to each function as an example.

[0512] Figure 12 This is a schematic block diagram of a communication device 100 provided in an embodiment of this application. As shown, the device 100 may include a transceiver unit 110 and a processing unit 120.

[0513] In one possible design, the device 100 may be a wireless access network device as described in the above method embodiments, or it may be a chip for implementing the functions of the wireless access network device as described in the above method embodiments. It should be understood that the device 100 may correspond to the wireless access network device in methods 100, 500, 600, 700, and 800 according to embodiments of this application, and the device 100 may perform the steps corresponding to the wireless access network device in methods 100, 500, 600, 700, and 800 according to embodiments of this application.

[0514] In one implementation, transceiver unit 110 is configured to receive a first message from a first access and mobility management function (AMU) network element. The first message carries an identifier for a first broadcast service and is used to trigger resource allocation for the first broadcast service. Processing unit 120 is configured to obtain information about a first resource corresponding to the first broadcast service based on the identifier of the first broadcast service. The first resource is used to send data of the first broadcast service to a terminal device in the second network. Transceiver unit 110 is further configured to send data of the first broadcast service to a terminal device in the first network using the first resource. The device is shared by at least two networks, including a first network and a second network, with the first AMU network element located in the first network.

[0515] Optionally, the identifier of the first broadcast service includes a first identifier and / or a second identifier, wherein 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, the temporary mobile group identifier being shared by the at least two networks; the second identifier includes: an identifier of the first broadcast service in the first network.

[0516] Optionally, the globally unique identifier of the first broadcast service includes the Internet Protocol (IP) multicast address of the first broadcast service.

[0517] Optionally, when the identifier of the first broadcast service is a globally unique identifier of the first broadcast service, the processing unit 120 is configured to obtain information about the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service, including: the processing unit 120 is configured to look up the broadcast session context corresponding to the first broadcast service based on the globally unique identifier of the first broadcast service; the processing unit 120 is configured to obtain information about the first resource based on the broadcast session context; wherein, the broadcast session context includes the globally unique identifier of the first broadcast service and the information about the first resource.

[0518] Optionally, 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 processing unit 120 is configured to obtain information of the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service, including: the processing unit 120 is configured to look up the broadcast session context corresponding to the first broadcast service based on the identifier of the first broadcast service in each of the at least two networks; the processing unit 120 is configured to obtain information of the first resource based on the broadcast session context; wherein, the broadcast session context includes the identifier of the first broadcast service in each of the at least two networks and the information of the first resource.

[0519] Optionally, when the identifier of the first broadcast service includes the second identifier, the processing unit 110 is configured to obtain information about the first resource corresponding to the first broadcast service based on the identifier of the first broadcast service, including: the processing unit 120 is configured to obtain the identifier of the first broadcast service in the second network based on a 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, and the second identifier; the processing unit 120 is configured to look up the broadcast session context corresponding to the first broadcast service based on the identifier of the first broadcast service in the second network; and the processing unit 120 is configured to obtain information about the first resource based on the broadcast session context.

[0520] Optionally, if the identifier of the first broadcast service includes the first identifier, the transceiver unit 110 is further configured to receive a second message from a second access and mobility management function (AM) network element, the second message carrying the first identifier, the second message being used to trigger resource allocation for the first broadcast service, the second AM network element being located in the second network of the at least 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 about the first resource.

[0521] In one possible design, the device 100 may be a multicast / broadcast session management function network element in the above method embodiments, or it may be a chip for implementing the functions of the multicast / broadcast session management function network element in the above method embodiments. It should be understood that the device 100 may correspond to the multicast / broadcast session management function network element in methods 200, 500, 600, 700, and 800 according to embodiments of this application, and the device 100 may execute the steps corresponding to the multicast / broadcast session management function network element in methods 200, 500, 600, 700, and 800 according to embodiments of this application.

[0522] In one implementation, the transceiver unit 110 is used to receive the identifier of the first broadcast service; the transceiver unit 110 is also used to send the identifier of the first broadcast service.

[0523] Optionally, the identifier of the first broadcast service includes a first identifier, which 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 at least two networks; or a temporary mobile group identifier of the first broadcast service, which is shared by at least two networks.

[0524] Optionally, the globally unique identifier of the first broadcast service includes the Internet Protocol (IP) multicast address of the first broadcast service.

[0525] Optionally, the transceiver unit 110 is used to receive the identifier of the first broadcast service, including: the transceiver unit 110 is used to receive the identifier of the first broadcast service from the application function network element.

[0526] Optionally, 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 identifier of the first broadcast service, the third message being used to trigger the device to send a 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, or; the processing unit 120 is configured to allocate the temporary mobile group identifier to the first broadcast service according to the third message; the transceiver unit 110 is configured to send the temporary mobile group identifier.

[0527] Optionally, 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.

[0528] Optionally, the transceiver unit 110 is used to receive the identifier of the first broadcast service, including: the transceiver unit 110 is used to receive 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.

[0529] Optionally, 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, the fourth message being configured to request the establishment or modification of a session for the first broadcast service, the fourth message carrying first indication information, the first indication information being configured to trigger the processing unit 120 to detect the identifier of the first broadcast service.

[0530] In one possible design, the device 100 may be an application function network element in the above method embodiments, or it may be a chip for implementing the functions of the application function network element in the above method embodiments. It should be understood that the device 100 may correspond to the application function network element in methods 300, 500, 600, 700, and 800 according to the embodiments of this application, and the device 100 may execute the steps corresponding to the application function network element in methods 300, 500, 600, 700, and 800 of the embodiments of this application.

[0531] In one implementation, the processing unit 120 is used to obtain the identifier of the first broadcast service; the transceiver unit 110 is used to send the identifier of the first broadcast service.

[0532] Optionally, the identifier of the first broadcast service includes a first identifier, which 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 at least two networks; or a temporary mobile group identifier of the first broadcast service, which is shared by at least two networks.

[0533] Optionally, the globally unique identifier of the first broadcast service includes the Internet Protocol (IP) multicast address of the first broadcast service.

[0534] Optionally, the processing unit 120 is used to obtain the identifier of the first broadcast service, including: the processing unit 120 is used to generate a globally unique identifier for the first broadcast service.

[0535] Optionally, the at least two networks include a first network and a second network. The processing unit 120 is used to obtain the identifier of the first broadcast service, including: the processing unit 120 instructing the transceiver unit 110 to receive the identifier of the first broadcast service in the first network from a first multicast / broadcast session management function network element in the first network; and the processing unit 120 instructing the transceiver unit 110 to receive the identifier of the first broadcast service in the second network from a second multicast / broadcast session management function network element in the second network.

[0536] The processing unit 120 is used to obtain the identifier of the first broadcast service, including: the processing unit 120 is used to obtain the temporary mobile group identifier from the multicast / broadcast session management function network element.

[0537] In one possible design, the device 100 can be the first network element in the above method embodiments, or it can be a chip used to implement the function of the first network element in the above method embodiments. It should be understood that the device 100 can correspond to the first network element (e.g., central database) in method 400 according to the embodiments of this application, or the central database in method 800. The device 100 can execute the steps corresponding to the functional network element of the first network element in method 400 of the embodiments of this application, or it can execute the steps corresponding to the central database in method 800.

[0538] In one implementation, transceiver unit 110 is configured to receive a fifth message, the fifth message carrying an identifier of a first broadcast service, the fifth message being configured to trigger the device to send a temporary mobile group identifier of the first broadcast service; and processing unit 120 is configured to instruct transceiver unit 110 to send the temporary mobile group identifier of the first broadcast service according to the fifth message.

[0539] Optionally, the transceiver unit 110 is further configured to receive from the multicast / broadcast session management function network element the correspondence between the identifier of the first broadcast service and the temporary mobile group identifier.

[0540] Optionally, the temporary mobile group identifier may be shared by at least two networks.

[0541] Optionally, 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.

[0542] It should also be understood that the device 100 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 100 may specifically be a first terminal device in the above embodiments, used to execute the various processes and / or steps corresponding to the first terminal device in the above method embodiments; or, the device 100 may specifically be a second terminal device in the above embodiments, used to execute the various processes and / or steps corresponding to the second terminal device in the above method embodiments. To avoid repetition, further details are omitted here.

[0543] The apparatus 100 of each of the above-described schemes has the function of implementing the corresponding steps performed by the wireless access network device in the above-described method; or, the apparatus 100 of each of the above-described schemes has the function of implementing the corresponding steps performed by the multicast / broadcast session management function network element, or the application function network element, or the first network element in the above-described method. The functions can be implemented by hardware or by hardware executing corresponding software. 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 (e.g., the transmitting 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), and other units, such as processing units, can be replaced by processors, respectively executing the transceiver operations and related processing operations in each method embodiment.

[0544] In addition, the transceiver unit 110 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0545] It should be pointed out that, Figure 12 The device mentioned can be the network element or equipment in the foregoing embodiments, or it can be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0546] Figure 13This is a schematic block diagram of a communication device 200 provided in an embodiment of this application. As shown, the device 200 includes at least one processor 220. The processor 220 is coupled to a memory and is used to execute instructions stored in the memory to transmit and / or receive signals. Optionally, the device 200 also includes a memory 230 for storing instructions. Optionally, the device 200 also includes a transceiver 210, and the processor 220 controls the transceiver 210 to transmit and / or receive signals.

[0547] It should be understood that the processor 220 and memory 230 described above can be combined into a single processing device, with the processor 220 executing the program code stored in the memory 230 to achieve the aforementioned functions. In specific implementations, the memory 230 can be integrated into the processor 220 or independent of the processor 220.

[0548] It should also be understood that transceiver 210 may include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver may further include an antenna, and the number of antennas may be one or more. Transceiver 210 may have a communication interface or interface circuitry.

[0549] Specifically, the transceiver 210 in the device 200 can correspond to the transceiver unit 110 in the device 100, and the processor 220 in the device 200 can correspond to the processing unit 120 in the device 200.

[0550] As one option, the device 200 is used to implement the operations performed by the wireless access network device in the various method embodiments described above.

[0551] For example, processor 220 is used to execute computer programs or instructions stored in memory 230 to implement relevant operations of the wireless access network device in the various method embodiments described above. For example, Figure 4 Method 100 performed by the wireless access network device in the illustrated embodiment, or Figures 8 to 11 The method performed by the wireless access network device in any of the illustrated embodiments.

[0552] As an alternative, the device 200 is used to implement the operations performed by each core network element in the various method embodiments described above.

[0553] For example, processor 220 is used to execute computer programs or instructions stored in memory 230 to implement the relevant operations of the multicast / broadcast session management function network element, application function network element, and first network element in the various method embodiments described above. For example, Figures 5 to 11 The method executed by the multicast / broadcast session management function network element, application function network element, and first network element in any of the embodiments shown.

[0554] It should be understood that the specific process by which each transceiver and processor performs the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0555] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0556] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as execution by a hardware decoding processor, or as a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0557] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous-link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0558] According to the method provided in the embodiments of this application, this application also provides a computer program product, which stores computer program code. When the computer program code is run on a computer, the computer executes the method executed by the wireless access network device or RAN in any one of the embodiments of method 100, method 500 to method 800.

[0559] For example, when the computer program code is executed by a computer, it enables the computer to implement the methods executed by the multicast / broadcast session management function network element in the embodiments of methods 200, 500 to 800 described above.

[0560] For example, when the computer program code is executed by the computer, it enables the computer to implement the methods executed by the application function network element in the embodiments of methods 300, 500 to 800 described above.

[0561] For example, when the computer program code is executed by the computer, it enables the computer to implement the methods executed by the first network element in the embodiments of methods 400, 500 to 800 described above.

[0562] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing program code. When the program code is run on a computer, it causes the computer to perform the method executed by the wireless access network device, the multicast / broadcast session management function network element, the application function network element, or the first network element in the above embodiments.

[0563] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes a radio access network device and a first access and mobility management function (AMU) network element. The radio access network device is used to execute the method executed by the radio access network device or RAN in any one of the embodiments of method 100, method 500 to method 800. The first AMU network element is used to send a first message to the radio access network device. The first message carries an identifier of a first broadcast service and is used to trigger the allocation of resources for the first broadcast service. The radio access network device is shared by at least two networks, including a first network and a second network. The first AMU network element is located in the first network.

[0564] In one optional implementation, the system further includes a multicast / broadcast session management function network element, which is used to execute the method executed by the multicast / broadcast session management function network element in any one of the embodiments of method 200, method 500 to method 800.

[0565] In one optional implementation, the system further includes: an application function network element; the application function network element is used to execute the method executed by the application function network element in any one of the embodiments of method 300, method 500 to method 800.

[0566] In an optional implementation, the system further includes a first network element (e.g., a central database), which is used to execute the method performed by the first network element (e.g., the central database) in any one of the embodiments of method 400 and method 800.

[0567] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0568] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0569] In the above-described device embodiments, corresponding modules or units perform corresponding steps. For example, the transceiver unit (transceiver) performs the receiving or sending steps in the method embodiments, while other steps besides sending and receiving can be performed by the processing unit (processor). The specific functions of each unit can be found in the corresponding method embodiments. There can be one or more processors.

[0570] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (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 interacting with other systems via signals).

[0571] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0572] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0573] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0574] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0575] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0576] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0577] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A multicast / broadcast communication method, characterized in that, The method is performed by a wireless access network device or a chip used in a wireless access network device, the method comprising: The system receives a first message from a first access and mobility management function network element. The first message carries an identifier of a first multicast / broadcast service. The first message is used to trigger the allocation of resources for the first multicast / broadcast service. The radio access network device or the chip for the radio access network device is shared by at least two networks, including a first network and a second network. The first access and mobility management function network element is located in the first network. Based on the identifier of the first multicast / broadcast service, information about the first resource corresponding to the first multicast / broadcast service is obtained. The first resource is used to send data of the first multicast / broadcast service to the terminal device in the second network. The data of the first multicast / broadcast service is sent to the terminal devices in the first network using the first resource.

2. The method according to claim 1, characterized in that, The identifier of the first multicast / broadcast service includes a globally unique identifier for the first multicast / broadcast service.

3. The method according to claim 2, characterized in that, The globally unique identifier of the first multicast / broadcast service includes the Internet Protocol (IP) multicast address of the first multicast / broadcast service.

4. The method according to claim 2 or 3, characterized in that, The step of obtaining information about the first resource corresponding to the first multicast / broadcast service based on the identifier of the first multicast / broadcast service includes: Based on the globally unique identifier of the first multicast / broadcast service, find the multicast / broadcast session context corresponding to the first multicast / broadcast service; Information about the first resource is obtained based on the multicast / broadcast session context; The multicast / broadcast session context includes the globally unique identifier of the first multicast / broadcast service and information about the first resource.

5. The method according to claim 2, characterized in that, The method further includes: Receive a second message from a second access and mobility management function network element, the second message carrying a globally unique identifier of the first multicast / broadcast service, the second message being used to trigger the allocation of resources for the first multicast / broadcast service, the second access and mobility management function network element being located in the second network of the at least two networks; According to the second message, allocate the first resource to the first multicast / broadcast service; Establish the multicast / broadcast session context corresponding to the first multicast / broadcast service; The multicast / broadcast session context includes the globally unique identifier of the first multicast / broadcast service and information about the first resource.

6. The method according to any one of claims 1 to 3, characterized in that, The first message is a request to establish a multicast / broadcast session resource.

7. The method according to any one of claims 1 to 3, characterized in that, The first resource is the resource that has been allocated in the second network for the first multicast / broadcast service.

8. A multicast / broadcast communication method, characterized in that, The method is executed by a multicast / broadcast session management function network element or a chip used for a multicast / broadcast session management function network element, and the method includes: The identifier for receiving the first multicast / broadcast service; Send the identifier of the first multicast / broadcast service to the access and mobility management function network element; The identifier of the first multicast / broadcast service is used by the wireless access network device to obtain information about the first resource corresponding to the first multicast / broadcast service. The first resource is used to send the data of the first multicast / broadcast service to the terminal devices in the first network and the terminal devices in the second network.

9. The method according to claim 8, characterized in that, The identifier of the first multicast / broadcast service includes a globally unique identifier for the first multicast / broadcast service.

10. The method according to claim 9, characterized in that, The globally unique identifier of the first multicast / broadcast service includes the Internet Protocol (IP) multicast address of the first multicast / broadcast service.

11. The method according to any one of claims 8 to 10, characterized in that, The identifier for receiving the first multicast / broadcast service includes: Receive the identifier of the first multicast / broadcast service from the application function network element.

12. The method according to claim 11, characterized in that, Before receiving the identifier of the first multicast / broadcast service from the application function network element, the method further includes: A third message is received from the application function network element. The third message carries the identifier of the first multicast / broadcast service. The third message is used to trigger the multicast / broadcast session management function network element or the chip of the multicast / broadcast session management function network element to send the temporary mobile group identifier of the first multicast / broadcast service to the application function network element. According to the third message, obtain the temporary mobile group identifier from the first network element, or according to the third message, allocate the temporary mobile group identifier to the first multicast / broadcast service; Send the temporary mobile group identifier to the application function network element.

13. The method according to claim 12, characterized in that, 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.

14. The method according to any one of claims 8 to 10, characterized in that, The identifier for receiving the first multicast / broadcast service includes: Receive the identifier of the first multicast / broadcast service from the multicast / broadcast user plane function network element, wherein the identifier of the first multicast / broadcast service is a globally unique identifier of the first multicast / broadcast service.

15. The method according to claim 14, characterized in that, Before receiving the identifier of the first multicast / broadcast service from the multicast / broadcast user plane function network element, the method further includes: A fourth message is sent to the multicast / broadcast user plane function network element. The fourth message is used to request the establishment or modification of the session of the first multicast / broadcast service. The fourth message carries first indication information, which is used to trigger the multicast / broadcast user plane function network element to detect the identifier of the first multicast / broadcast service.

16. A multicast / broadcast communication method, characterized in that, The method is executed by an application function network element or a chip used in an application function network element, and the method includes: Obtain the identifier of the first multicast / broadcast service, wherein the identifier of the first multicast / broadcast service includes a globally unique identifier of the first multicast / broadcast service; Send the identifier to the first multicast / broadcast session management function network element in the first network; Send the identifier to the second multicast / broadcast session management function network element in the second network; The identifier of the first multicast / broadcast service is used by the wireless access network device to obtain information about the first resource corresponding to the first multicast / broadcast service. The first resource is used to send the data of the first multicast / broadcast service to the terminal devices in the first network and the terminal devices in the second network.

17. The method according to claim 16, characterized in that, Sending the identifier to the first multicast / broadcast session management function network element in the first network includes: A first session creation request is sent to the first multicast / broadcast session management function network element. The first session creation request carries the globally unique identifier and the temporary mobile group identifier (TMGI) of the first multicast / broadcast service in the first network.

18. The method according to claim 16 or 17, characterized in that, Sending the identifier to the second multicast / broadcast session management function network element in the second network includes: A second session creation request is sent to the second multicast / broadcast session management function network element. The second session creation request carries the globally unique identifier and the temporary mobile group identifier (TMGI) of the first multicast / broadcast service in the second network.

19. The method according to claim 16 or 17, characterized in that, The globally unique identifier of the first multicast / broadcast service includes the Internet Protocol (IP) multicast address of the first multicast / broadcast service.

20. The method according to claim 17, characterized in that, The identifier for obtaining the first multicast / broadcast service includes: Generate a globally unique identifier for the first multicast / broadcast service.

21. A multicast / broadcast communication device, characterized in that, include: A processor for executing a computer program stored in a memory to cause the apparatus to perform the method as claimed in any one of claims 1 to 7, or to cause the apparatus to perform the method as claimed in any one of claims 8 to 15, or to cause the apparatus to perform the method as claimed in any one of claims 16 to 20.

22. The apparatus according to claim 21, characterized in that, The device also includes the memory.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on a computer, causes the computer to perform the method as described in any one of claims 1 to 7, or causes the computer to perform the method as described in any one of claims 8 to 15, or causes the computer to perform the method as described in any one of claims 16 to 20.

24. A computer program product, characterized in that, The computer program product includes instructions for performing the method as described in any one of claims 1 to 7, or instructions for performing the method as described in any one of claims 8 to 15, or instructions for performing the method as described in any one of claims 16 to 20.

25. A multicast / broadcast communication system, characterized in that, include: Wireless access network equipment or chips and first access and mobility management function network elements used in wireless access network equipment; The wireless access network device or the chip for the wireless access network device is used to perform the method as described in any one of claims 1 to 7; The first access and mobility management function network element is used to send a first message to the radio access network device or a chip for the radio access network device. The first message carries an identifier of a first multicast / broadcast service and is used to trigger the allocation of resources for the first multicast / broadcast service. The wireless access network device is shared by at least two networks, including a first network and a second network, wherein the first access and mobility management function network element is located in the first network.

26. The communication system according to claim 25, characterized in that, The system also includes: a multicast / broadcast session management function network element or a chip for the multicast / broadcast session management function network element; The multicast / broadcast session management function network element or the chip used for the multicast / broadcast session management function network element is used to perform the method as described in any one of claims 8 to 15.

27. The communication system according to claim 25 or 26, characterized in that, The system also includes: application function network elements or chips for application function network elements; The application function network element or the chip used for the application function network element executes the method as described in any one of claims 16 to 20.

Images