Communication method and apparatus

Abstract

Embodiments of the present application provide a communication method and device. The method comprises: a multicast session management network element receiving first information of a first multicast service from an application server, the first information being used to indicate at least one of the following: a first service area of the first multicast service, a type of the first multicast service, or the first multicast service; and the multicast session management network element sending a second service area identifier of the first multicast service to the application server according to the first information. Thus, the application server can obtain the second service area identifier of the first multicast service, i.e., the SAI of the first multicast service, without knowing network topology information.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communications, and more particularly, to a communication method and apparatus. BACKGROUND

[0002] In wireless communications, a base station broadcasts the correspondence between multicast broadcast services and frequencies that can be transmitted in a cell in a system information block (SIB) before the start of a broadcast service. Then, a terminal device selects a frequency for multicast broadcast to receive broadcast data. At this time, the multicast broadcast service sent in the SIB can be a multicast broadcast service that has been allocated resources in a core network, or can be a multicast broadcast service that has only been allocated a multicast broadcast service identifier such as a temporary mobile group identifier (TMGI).

[0003] In multicast broadcast of a 4th generation (4G) system, a service area identifier (SAI) is defined. A base station broadcasts the correspondence between the SAI and the frequency in a SIB, and a terminal device is configured with the correspondence between the TMGI and the SAI. In this way, the terminal device can obtain the correspondence between the TMGI and the frequency by reading the SIB message. In addition, for multicast broadcast of the 4G system, the application scenarios mainly focus on public safety scenarios, so it can be assumed that an application server (AS) has high authority and can know network topology information, that is, the AS can know the correspondence between the TMGI and the SAI.

[0004] However, in multicast broadcast of a 5th generation (5G) system, only the TMGI is defined. If the network side does not make any optimization, it will cause too many TMGIs to be sent in the SIB message, resulting in waste of system broadcast resources. In addition, for multicast broadcast of the 5G system, even if the SAI is defined, because the application scenarios are relatively extensive, it cannot be assumed that the AS has high authority and cannot know network topology information, that is, the AS cannot know the correspondence between the TMGI and the SAI. Therefore, for multicast broadcast of the 5G system, how to obtain the SAI corresponding to the multicast broadcast service when the AS does not know the network topology information is a problem to be solved. SUMMARY

[0005] Embodiments of the present application provide a communication method and apparatus, which can obtain the SAI corresponding to the multicast broadcast service when the AS does not know the network topology information, thereby reducing the waste of system broadcast resources.

[0006] In a first aspect, a communication method is provided, which can be performed by a multicast session management network element or a component (such as a circuit, a chip or a chip system, etc.) configured in the multicast session management network element. The present application does not limit this.

[0007] The communication method comprises: receiving first information of a first multicast service from an application server, the first information being used to indicate at least one of a first service area of the first multicast service, a type of the first multicast service, or the first multicast service; and sending, to the application server, a second service area identifier of the first multicast service according to the first information.

[0008] In the above technical solution, the multicast session management network element sends the second service area identifier of the first multicast service to the application server according to the first information sent by the application server, and thus the second service area identifier of the first multicast service (i.e., the SAI of the first multicast service) can be obtained without the application server knowing the network topology information.

[0009] In combination with the first aspect, in some implementations of the first aspect, the multicast session management network element sends, to the application server, the second service area identifier of the first multicast service according to the first information, comprising: the multicast session management network element determines the second service area identifier of the first multicast service corresponding to the first information; and the multicast session management network element sends, to the application server, the second service area identifier of the first multicast service.

[0010] In combination with the first aspect, in some implementations of the first aspect, the communication method further comprises: the multicast session management network element sends, to the application server, second information of the first multicast service, the second information comprising at least one of a frequency of the first multicast service or a temporary multicast group identifier of the first multicast service.

[0011] When the second information contains the temporary multicast group identifier of the first multicast service, the scenario of the application server requesting multiple temporary multicast group identifiers can be supported.

[0012] When the second information contains the frequency of the first multicast service, the frequency corresponding to the second service area identifier of the first multicast service on the network side can be further obtained, and thus the frequency corresponding to the service area identifier of the first multicast service can be further provided to the terminal device, so that the terminal device can directly obtain the corresponding parameters (such as scheduling information, etc.) of the multicast through the frequency corresponding to the service area identifier of the first multicast service, thereby saving the step of the terminal device first reading the frequency corresponding to the service area identifier of the first multicast service, i.e., saving the power consumption and signaling overhead of the terminal device.

[0013] In an implementable manner, the multicast session management network element sending the second information of the first multicast service to the application server comprises: the multicast session management network element determining the second information of the first multicast service corresponding to the first information of the first multicast service; and the multicast session management network element sending the second information of the first multicast service to the application server.

[0014] In another implementable manner, the multicast session management network element sending the second information of the first multicast service to the application server comprises: the multicast session management network element determining the second information of the first multicast service corresponding to the second service area identifier of the first multicast service; and the multicast session management network element sending the second information of the first multicast service to the application server.

[0015] With reference to the first aspect, in some implementations of the first aspect, the first information is carried in a temporary multicast group identifier allocation request message.

[0016] The first information is carried in an existing temporary multicast group identifier allocation request message, that is, in the process of the application server requesting allocation of a temporary multicast group identifier, the second service area identifier of the first multicast service is requested to be allocated, and thus the existing flow of requesting allocation of a temporary multicast group identifier can be reused, the modification to the existing protocol is reduced, and the processing speed is accelerated, and it is not necessary to perform the interaction between network elements again.

[0017] With reference to the first aspect, in some implementations of the first aspect, the second service area identifier of the first multicast service is carried in a response message of the temporary multicast group identifier allocation request message.

[0018] The second service area identifier of the first multicast service is carried in an existing response message of a temporary multicast group identifier allocation request message, that is, in the process of the multicast session management network element requesting allocation of a temporary multicast group identifier, the second service area identifier of the first multicast service is carried in a response message of a temporary multicast group identifier allocation request message and sent to the application server, and thus the existing flow of requesting allocation of a temporary multicast group identifier can be reused, the modification to the existing protocol is reduced, and the processing speed is accelerated, and it is not necessary to perform the interaction between network elements again.

[0019] With reference to the first aspect, in some implementations of the first aspect, the second information of the first multicast service is carried in a response message of the temporary multicast group identifier allocation request message.

[0020] The second information of the first multicast service is carried in a response message of an existing temporary multicast group identifier allocation request message, that is, the second information of the first multicast service is sent to the application server in the response message of the temporary multicast group identifier allocation request message in a process in which the multicast session management network element requests allocation of a temporary multicast group identifier, thereby reusing an existing flow of requesting allocation of a temporary multicast group identifier, reducing modification of an existing protocol, and speeding up processing without performing interaction between network elements again.

[0021] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: receiving, by the multicast session management network element, the session creation request message from the application server; and informing, by the multicast session management network element, the first network device of the second service area identifier of the first multicast service according to the session creation request message.

[0022] Optionally, the session creation request message can carry the second service area identifier of the first multicast service and / or the second information of the first multicast service. In this way, the second service area identifier of the first multicast service and / or the second information of the first multicast service can be obtained in a case where the multicast session management network element does not store the second service area identifier of the first multicast service and / or the second information of the first multicast service. The second service area identifier of the first multicast service and / or the second information of the first multicast service can be provided to the corresponding network device, and the corresponding network device, that is, the first network device, can be dynamically controlled to broadcast the second service area identifier of the first multicast service. In addition, the first network device will not broadcast too many TMGIs, thereby avoiding waste of system broadcast resources.

[0023] With reference to the first aspect, in some implementations of the first aspect, informing, by the multicast session management network element, the first network device of the second service area identifier of the first multicast service according to the session creation request message includes: determining, by the multicast session management network element, the first network device according to the session creation request message; and informing the first network device of the second service area identifier of the first multicast service.

[0024] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: informing, by the multicast session management network element, the first network device of the second information of the first multicast service.

[0025] The second aspect provides a communication method, which can be executed by an application server or a component (such as a circuit, a chip or a chip system, etc.) configured in the application server. The present application does not limit this.

[0026] The communication method comprises: sending, by an application server, first information of a first multicast service to a multicast session management network element, the first information comprising at least one of the following: a first service area of the first multicast service, a type of the first multicast service, or the first multicast service; receiving, by the application server, a second service area identifier of the first multicast service from the multicast session management network element; and informing, by the application server, a terminal device of the second service area identifier of the first multicast service.

[0027] In the technical solution, the application server sends first information to the multicast session management network element, requests a second service area identifier of the first multicast service, and obtains the second service area identifier of the first multicast service from the multicast session management network element, so that the second service area identifier of the first multicast service, i.e., the SAI of the first multicast service, can be obtained without the application server knowing the network topology information.

[0028] With reference to the second aspect, in some implementations of the second aspect, the communication method further comprises: receiving, by the application server, second information of the first multicast service from the multicast session management network element, the second information comprising at least one of the following: a frequency of the first multicast service, or a temporary multicast group identifier of the first multicast service.

[0029] With reference to the second aspect, in some implementations of the second aspect, the first information is carried in a temporary multicast group identifier temporary multicast group identifier allocation request message.

[0030] With reference to the second aspect, in some implementations of the second aspect, the second service area identifier of the first multicast service is carried in a response message of the temporary multicast group identifier allocation request message.

[0031] With reference to the second aspect, in some implementations of the second aspect, the informing, by the application server, of the terminal device of the second service area identifier of the first multicast service comprises: carrying, by the application server, the second service area identifier of the first multicast service in a service announcement message and informing the terminal device of the second service area identifier of the first multicast service.

[0032] Carrying the second service area identifier of the first multicast service in an existing service announcement message can reuse an existing process of requesting allocation of a temporary multicast group identifier, reduce changes to an existing protocol, and speed up processing without performing an interaction between network elements again.

[0033] With reference to the second aspect, in some implementations of the second aspect, the communication method further comprises: informing, by the application server, the terminal device of the second information of the first multicast service.

[0034] With reference to the second aspect, in some implementations of the second aspect, the application server notifying the terminal device of the second information of the first multicast service comprises: the application server notifying the terminal device of the second information of the first multicast service carried in a service announcement message.

[0035] Carrying the second information of the first multicast service in the existing service announcement message can reuse the existing process of requesting allocation of a temporary multicast group identifier, reduce changes to the existing protocol, and speed up processing without performing the interaction between network elements again.

[0036] In a third aspect, a communication method is provided, which can be executed by a network device or a component (such as a circuit, a chip or a chip system, etc.) configured in the network device. The present application does not limit this.

[0037] The communication method comprises: receiving a second service area identifier of a first multicast service; and broadcasting the second service area identifier of the first multicast service.

[0038] The network device can dynamically broadcast the second service area identifier of the first multicast service according to the received second service area identifier of the first multicast service. This prevents the network device from broadcasting too many TMGIs, thereby avoiding waste of system broadcast resources.

[0039] With reference to the third aspect, in some implementations of the third aspect, the communication method further comprises: the network device receiving second information of the first multicast service and / or a first service area of the first multicast service; and the network device broadcasting the second information of the first multicast service and / or the first service area of the first multicast service; wherein the second information comprises at least one of a frequency of the first multicast service or a temporary multicast group identifier of the first multicast service.

[0040] In a fourth aspect, a communication apparatus is provided, which is configured to execute the communication method in any possible implementation manner of the first aspect. Specifically, the apparatus can comprise units and / or modules for executing the communication method provided in the first aspect or any possible implementation manner of the first aspect, such as a processing unit and / or a communication unit.

[0041] In an implementation manner, the apparatus is a multicast session management network element. When the apparatus is a multicast session management network element, the communication unit can be a transceiver or an input / output interface; and 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.

[0042] In another implementation, the apparatus is a chip, chip system, or circuit configured in the application server. When the apparatus is a chip, chip system, or circuit configured in the application server, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit can be at least one processor, processing circuit, or logic circuit.

[0043] In a fifth aspect, a communication apparatus is provided, which is configured to perform the communication method in any possible implementation of the second aspect. Specifically, the apparatus can include a communication unit and / or a processing unit, which are configured to perform the communication method in the second aspect or any possible implementation of the second aspect.

[0044] In an implementation, the apparatus is a network device. When the apparatus is a network device, the communication unit can be a transceiver, or an input / output interface; and the processing unit can be at least one processor. Optionally, the transceiver can be a transceiving circuit. Optionally, the input / output interface can be an input / output circuit.

[0045] In another implementation, the apparatus is a chip, chip system, or circuit configured in the network device. When the apparatus is a chip, chip system, or circuit configured in the network device, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit can be at least one processor, processing circuit, or logic circuit.

[0046] In a sixth aspect, a communication apparatus is provided, which is configured to perform the communication method in any possible implementation of the third aspect. Specifically, the apparatus can include a communication unit and / or a processing unit, which are configured to perform the communication method in the third aspect or any possible implementation of the third aspect.

[0047] In an implementation, the apparatus is a network device. When the apparatus is a network device, the communication unit can be a transceiver, or an input / output interface; and the processing unit can be at least one processor. Optionally, the transceiver can be a transceiving circuit. Optionally, the input / output interface can be an input / output circuit.

[0048] In another implementation, the apparatus is a chip, chip system or circuit configured in the network device. When the apparatus is a chip, chip system or circuit configured in the network device, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit, etc. on the chip, chip system or circuit; the processing unit can be at least one processor, processing circuit or logic circuit, etc.

[0049] In a seventh aspect, a communication apparatus is provided, which comprises: a memory for storing programs; at least one processor for executing the computer programs or instructions stored in the memory to perform the communication method in the first aspect or any possible implementation manner of the first aspect.

[0050] In an implementation manner, the apparatus is a multicast session management network element.

[0051] In another implementation manner, the apparatus is a chip, chip system or circuit configured in the multicast session management network element.

[0052] In an eighth aspect, a communication apparatus is provided, which comprises: a memory for storing programs; at least one processor for executing the computer programs or instructions stored in the memory to perform the communication method in the second aspect or any possible implementation manner of the second aspect.

[0053] In an implementation manner, the apparatus is an application server.

[0054] In another implementation manner, the apparatus is a chip, chip system or circuit configured in the application server.

[0055] In a ninth aspect, a communication apparatus is provided, which comprises: a memory for storing programs; at least one processor for executing the computer programs or instructions stored in the memory to perform the communication method in the third aspect or any possible implementation manner of the third aspect.

[0056] In an implementation manner, the apparatus is a network device.

[0057] In another implementation manner, the apparatus is a chip, chip system or circuit configured in the network device.

[0058] In a tenth aspect, a processor is provided for performing the communication method in any possible implementation manner of the first aspect to the third aspect.

[0059] For the sending and obtaining / receiving operations involved by the processor, if no special description is made, or if it is not contrary to the actual role or internal logic in the related description, it can be understood as the processor output and receiving, input operations, and also can be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, and the present application does not limit this.

[0060] In a eleventh aspect, a computer program product is provided, which includes a computer program (also can be called code or instruction), when the computer program is run, causes a computer to execute the communication method in any possible implementation manner of the first aspect to the third aspect.

[0061] In a twelfth aspect, a computer readable storage medium is provided, which stores a computer program (also can be called code or instruction), when it is run on a computer, causes the computer to execute the communication method in any possible implementation manner of the first aspect to the third aspect.

[0062] In a thirteenth aspect, a chip is provided, which includes a processor and a communication interface, the processor reads instructions stored on a memory through the communication interface, and executes the communication method in any possible implementation manner of the first aspect to the third aspect.

[0063] Optionally, as an implementation manner, the chip further includes a memory, the memory stores a computer program or instruction, and the processor is configured to execute the computer program or instruction stored on the memory, when the computer program or instruction is executed, the processor is configured to execute the communication method in any possible implementation manner of the first aspect to the third aspect.

[0064] In a fourteenth aspect, a communication system is provided, which includes the multicast session management network element, the application server, and / or the first network device, wherein the multicast session management network element is configured to execute the communication method in any possible implementation manner of the first aspect; or the application server is configured to execute the communication method in any possible implementation manner of the second aspect; or the first network device is configured to execute the communication method in any possible implementation manner of the third aspect. BRIEF DESCRIPTION OF DRAWINGS

[0065] Figure 1 It is an architecture diagram of a communication system.

[0066] Figure 2 It is a schematic flow chart of a communication method provided by an embodiment of the present application.

[0067] Figure 3 It is a schematic flow chart of another communication method provided by an embodiment of the present application.

[0068] Figure 4 A schematic block diagram of a communication device provided in an embodiment of the present application.

[0069] Figure 5 A schematic block diagram of another communication device provided in an embodiment of the present application.

[0070] Figure 6 A schematic diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0072] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, future 5G system or New Radio (NR), etc.

[0073] The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, etc. This application does not limit this.

[0074] The technical solutions provided in the application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device-to-device (D2D) network, machine to machine (M2M) network, internet of things (IoT) network or other network. The IoT network may, for example, include a vehicle network. In the vehicle network, the communication modes are collectively referred to as vehicle to X (V2X, X may represent any object), for example, the 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.

[0075] Figure 1 is a schematic diagram of an architecture of a communication system suitable for embodiments of the application. As Figure 1 shown, as Figure 1 shown, the architecture is, for example, a 5G system (5GS) defined in the 3rd Generation Partnership Project (3GPP) protocol TS23.501. The architecture can be divided into an access network (AN) and a core network (CN). The access network can be used to implement wireless access related functions, and the core network mainly includes the following several key logical network elements: access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF) and unified data management (UDM), etc.

[0076] The network elements shown in Figure 1 will be briefly introduced below:

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

[0078] The terminal device can be a device that provides voice / data connectivity to a user, such as a handheld device with wireless connectivity, a vehicle-mounted device, and the like. Currently, some examples of terminals are: a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN), and the like. The embodiments of the present application are not limited thereto.

[0079] By way of example and not limitation, in embodiments of the present application, the terminal device can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. The wearable device is a portable device that is directly worn on the body or integrated into the clothes or accessories of the user. The wearable device is not only a hardware device, but also a powerful function achieved through software support and data interaction, cloud interaction. The general wearable smart device includes a full function, large size, and can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and focuses on a certain application function and needs to cooperate with other devices such as a smart phone, such as various smart wristbands, smart jewelry, and the like.

[0080] In addition, in embodiments of the present application, the terminal device can also be a terminal device in an internet of things (IoT) system. The IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network to realize the intelligent network of man-machine interconnection and object-object interconnection.

[0081] 2, Access network: provides network access function for user equipment, and can use different quality transmission tunnels according to the level of users, business needs, and the like. The access network can be an access network using different access technologies. There are two types of current wireless access technologies: 3GPP access technology (such as wireless access technology used in 3G, 4G or 5G systems) and non-3GPP (non-3GPP) access technology. The 3GPP access technology refers to the access technology conforming to the 3GPP standard specification, for example, the access network device in the 5G system is called the next generation Node Base station (gNB). The non-3GPP access technology refers to the access technology that does not conform to the 3GPP standard specification, for example, the access point (AP) in the wireless fidelity (WiFi) is represented by the air interface technology.

[0082] The access network that realizes the access network function based on the wireless communication technology can be referred to as a radio access network (RAN). In the 5G communication system, the RAN can also be referred to as a next generation radio access network (NG-RAN). The radio access network can manage radio resources, provide access services for terminal devices, and then complete the forwarding of control signals and user data between the terminal and the core network.

[0083] The radio access network can include, but is not limited to, a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), and the like, and can also be a gNB or a transmission point (TRP or TP) in a 5G (for example, NR) system, one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), or a base station in a next-generation communication 6G system, and the like. The embodiments of the present application do not limit the specific technology and specific device form of the radio access network device.

[0084] The access network can provide services for a cell. The terminal device can communicate with the cell through the transmission resource (for example, frequency domain resource, or spectrum resource) allocated by the access network device.

[0085] In addition, in the embodiments of the present application, the access network device can also be used to receive MBS service data (MBS data) through a shared N3 interface, and transmit the MBS data to the terminal device using a point to point (PTP) or point to multi-point (PTM) transmission mode; or manage the QoS flow of the MBS session through the N2 interface.

[0086] 3. AMF: mainly used for mobility management and access management, such as user location update, user registration network, user handover, and the like. The AMF can also be used to implement other functions in the mobility management entity (MME) except for session management. For example, lawful interception, or access authorization (or authentication) functions.

[0087] In the embodiments of the present application, the AMF can also perform the following functions: signaling interaction with the access network device and the multicast session management function (multicast broadcast SMF, MB-SMF) for MBS session management; selecting an access network device for broadcast, etc.

[0088] 4. SMF: mainly used for session management, IP address allocation and management of the UE, selection of a manageable user plane function, termination of a policy control or charging function interface, and downlink data notification, etc.

[0089] 5. MB-SMF: a session management function network element with MBS function. The MB-SMF can be used for MBS session management (including QoS control), and control of MBS transmission, including configuring data plane gateway MB-UPF and RAN nodes (through AMF) for MBS flow transmission based on policy rules from PCF or local MBS service. The MB-SMF can also be connected with a server or multicast broadcast service function network element (multicast broadcast service function, MBSF) or network exposure function (network exposure function, NEF) of the MBS service, in order to receive relevant information (such as target information) of the MBS service. In addition, the MB-SMF can also be connected with the PCF to create resources for the MBS service. The MB-SMF can be integrated into the PCF or SMF as a functional module, or can be deployed separately, which is not limited in the present application.

[0090] In the embodiments of the present application, the MB-SMF can also perform the following functions: selecting an AMF.

[0091] 6. UPF: that is, a data plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc. User data can access the data network (data network, DN) through the network element.

[0092] 7. Multicast broadcast UPF (multicast broadcast UPF, MB-UPF): used for transmitting MBS services of QoS flow to RAN. The functions of MB-UPF supporting MBS services are: filtering downlink packets of MBS flow; distributing MBS data packets to RAN nodes (or UPF); QoS enhancement and counting / reporting based on existing methods. The MB-UPF can be integrated into the UPF as a functional module, or can be deployed separately, which is not limited in the present application.

[0093] 8、Multicast and broadcast service function (MBSF): It contains the management function related to the service layer of multicast and broadcast service. The MBS-related functions supported by MBSF include: interacting with NEF, MB-SMF, multicast and broadcast service transport function (MBSTF) to obtain service layer related information; performing management function related to encoding of downlink multicast and broadcast service data; filtering and modifying the parameters provided by application function (AF) for the control plane; determining the transmission mode of data (for example, using unicast transmission, or using broadcast transmission, etc.).

[0094] 9、MBSTF: It contains the data transmission function related to the service layer of multicast and broadcast service. The MBS-related functions supported by MBSTF include: interacting with MBSF to obtain control information for multicast and broadcast data transmission; encoding the downlink multicast and broadcast service data according to the configuration of MBSF; distributing the multicast and broadcast data received from AF to MB-SMF or UPF, etc.

[0095] 10、NEF: It is used to safely open the services and capabilities provided by 3GPP network functions to the outside.

[0096] 11、AF: It is responsible for providing services to 3GPP network, such as affecting service routing, interacting with PCF to perform policy control, etc.

[0097] In the embodiments of the present application, the AF can also be referred to as AS.

[0098] 12、Policy control function (PCF): It is a unified policy framework for guiding network behavior, and provides policy rule information for control plane function network elements (such as AMF, SMF, etc.).

[0099] 13、Network function (NF) repository function (NRF): It is used to save the description information of network function entities and the services provided by them, and support service discovery, network element entity discovery, etc.

[0100] 14、Unified data management (UDM): It is used to store user data, such as subscription information, authentication / authorization information, etc.

[0101] In the architecture shown in FIG. Figure 1 , the network elements can communicate with each other through the interfaces shown in the figure. For example, Figure 1As shown, the N1 interface is the reference point between the terminal device and the AMF; the N2 interface is the reference point between the NG-RAN and the AMF, which is used for sending non-access stratum (NAS) messages, etc.; the N3 interface is the reference point between the NG-RAN and the UPF, which is used for transmitting user plane data, etc.; the N3 interface is also the reference point between the NG-RAN and the MB-UPF, which is used for transmitting user plane data, etc.; the N4 interface is the reference point between the SMF and the UPF, which is used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages; the N6 interface is the reference point between the MB-UPF and the DN, which is used for transmitting user plane data, etc.

[0102] In addition, the N11mb interface ( Figure 1 (not shown) is a reference point between AMF and MB-SMF, used for AMF and MB-SMF to exchange multicast-related session parameters, such as information on updating QoS, area, etc., activation / deactivation of multicast session instructions, etc. After receiving the parameters from MB-SMF, AMF can transmit them to the corresponding base station side; N33 interface is a reference point between AF / AS and NEF, used for AF / AS to provide NEF with multicast-related parameters, such as service area, multicast business requirements, etc.; Nmb10 interface ( Figure 1 (not shown) is a reference point between AF / AS and MBSF, used by AF / AS to provide MBSF with multicast-related parameters, such as service area, multicast service requirements, coding information, etc.; Nmb13 interface ( Figure 1 Not shown) is a reference point between AF / AS and MB-SMF, used by AF / AS to provide MB-SMF with multicast-related parameters, such as service area and multicast-related business requirements; N29mb interface ( Figure 1 Nmb1 interface (not shown) is a reference point between NEF and MB-SMF, which is used by NEF to provide MB-SMF with parameters sent by the AF side. Optionally, NEF may process the AF parameters appropriately (for example, translate the geographic location information into a cell or tracking area identifier) ​​and send it to MB-SMF. Figure 1 (not shown) is a reference point between MBSF and MB-SMF, used for MBSF and MB-SMF to exchange service-level information, such as the start / end indication of multicast broadcast session transmission;

[0103] The relationship between other interfaces and network elements is as follows: Figure 1 For the sake of brevity, they are not described in detail here.

[0104] Figure 1Npcf, Nnrf, Nudm, Namf, Nsmf, Nmbsmf, Nnef, Naf, xmb-C / MB2-C, xmb-U / MB2-U, N1, N2, N3, N4, N6, MB-N9, Uu, and Figure 1 The N11mb, Nmb10, Nmb13, N29mb, Nmb1, etc. not shown in the figure are interface serial numbers. The meanings of these interface serial numbers can be found in the meanings defined in the 3rd generation partnership project (3GPP) standard protocol, and are not limited herein.

[0105] It should be noted that Figure 1 The names of the various network elements and the communication interfaces between the network elements involved in the figure are simply explained based on the current protocol, but the application embodiments are not limited to only being applicable to the currently known communication system. Therefore, the standard names appearing when described based on the current protocol are all functional descriptions, and the specific names of the network elements, interfaces, or signaling, etc. are not limited by the application, and only indicate the functions of the network elements, interfaces, or signaling, which can be extended to other systems, such as 2G, 3G, 4G, or future communication systems.

[0106] The architecture to which the application embodiments shown in the above Figure 1 The architecture to which the application embodiments shown in the figure can be applied is only an example, and the architecture to which the application embodiments are applicable is not limited thereto, and any architecture that can realize the functions of the above-mentioned various network elements is applicable to the application embodiments.

[0107] It should also be understood that Figure 1 The AMF, SMF, UPF, MB-UPF, MB-SMF, MBSF, MBSTF, NEF, PCF, NRF, UDM shown in the figure can be understood as network elements in the core network for realizing different functions, which can be combined into network slices as needed, for example. These core network network elements can be independent devices, or can be integrated into the same device to realize different functions, and the specific form of the above-mentioned network elements is not limited by the application.

[0108] It should also be understood that the above-mentioned naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation on the application. The application does not exclude the possibility of using other names in 5G networks and other future networks. For example, in a 6G network, part or all of the above-mentioned network elements can continue to use the terms in 5G, or other names, etc. Figure 2 The interface names between the various network elements in the figure are only an example, and the names of the interfaces in the specific implementation can be other names, which are not limited by the application. In addition, the names of the messages (or signaling) transmitted between the above-mentioned various network elements are also only an example, and the functions of the messages themselves are not limited.

[0109] To facilitate understanding of the embodiments of the present application, first, the terms involved in the present application are simply explained.

[0110] 1. Multicast: the same service and the same specific content data are provided to a group of dedicated UEs at the same time (i.e., not all UEs in the multicast coverage are authorized to receive data).

[0111] 2. Broadcast: the same specific content data is provided to all UEs in a geographical area at the same time (i.e., all UEs in the broadcast coverage area are authorized to receive data). Multicast can also be referred to as groupcast.

[0112] 3. Multicast / broadcast session (MBS session): a multicast / broadcast session can provide services for a multicast / broadcast service, and a multicast / broadcast session includes a unicast or groupcast tunnel from a data network to a core network device, to an access network device, and unicast or multicast / broadcast air interface resources allocated by the access network device for transmitting the multicast / broadcast service.

[0113] It should be noted that the embodiments of the present application can be applicable to multicast and also applicable to broadcast. For the convenience of description, the following are described by taking multicast as an example.

[0114] The technical solutions provided by the present application are described below.

[0115] In the embodiments of the present application, "indicates" can include direct indication and indirect indication, and can also include explicit indication and implicit indication. The information indicated by a certain information (the first information described below) is referred to as the to-be-indicated information, and in the implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index / identifier of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be indicated only by a part of the to-be-indicated information, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be realized by means of the arrangement order of each information agreed in advance (for example, a protocol), thereby reducing the indication overhead to a certain extent.

[0116] It can be understood that the term "and / or" in this paper is only a description of the association relationship between the associated objects, which means that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents an "or" relationship between the associated objects before and after it.

[0117] In the embodiments of the present application, the descriptions such as "when", "in the case of", "if" and "whether" all refer to the device (such as the multicast session management network element or the first access and mobility management function network element) will make corresponding processing under certain objective condition, not the time limit, and also does not require the device (such as the multicast session management network element or the first access and mobility management function network element) to have a judgment action when implementing, nor means that there is other limitation.

[0118] In the embodiments of the present application, the first, second and various numbers are only for the convenience of differentiation in description, and are not used to limit the scope of the embodiments of the present application. For example, different service areas are distinguished.

[0119] In the embodiments of the present application, the application server includes two function modules of AS and application function (application function, AF).

[0120] Among them, the AS can be understood as a data plane entity, which sends the multicast / broadcast data corresponding to the target service (for example, the first multicast service described below) to the operator network (PLMN network).

[0121] The AF can be understood as a control plane entity, which can specifically include the following functions:

[0122] (1) Send the configuration parameters corresponding to the target service to the operator network.

[0123] For example, the service requirement parameters corresponding to the target service are sent to the operator network, such as priority information, bandwidth information, delay information, standardized QoS identifier, etc.

[0124] (2) Send the control parameters corresponding to the target service to the operator network.

[0125] For example, the request for activation / deactivation corresponding to the target service is sent to the operator network, etc.

[0126] (3) Obtain the parameters corresponding to the target service from the operator network, such as TMGI, SAI, frequency, etc.

[0127] In general, the application server is used to configure or obtain the parameters of the target service in the operator network, send the control information of the target service to the operator network, and send the data of the target service to the operator network.

[0128] The above briefly describes the terms involved in the present application, which will not be repeated in the following embodiments. The communication method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments provided by the present application can be applied to the architecture shown above, without limitation. Figure 3 ​

[0129] Figure 2 and Figure 3 They are respectively schematic flow charts of the communication method 200 provided in an embodiment of the present application.

[0130] like Figure 3 As shown, the communication method 200 includes S210 to S230. The following describes the various steps included in the communication method 200 in detail.

[0131] S210: The application server sends first information of a first multicast service to a multicast session management network element.

[0132] Correspondingly, the multicast session management network element receives first information of the first multicast service from the application server.

[0133] Exemplarily, the first multicast service may be a map update service, a public safety service, an emergency communication service, a video transmission service (eg, mission critical video, mission critical push-to-talk), an IoT software upgrade service, and the like.

[0134] The first information is used to request a second service area identifier of the first multicast service.

[0135] It should be noted that the first information can be a message or an information element in a message, without limitation. In addition, the number of second service area identifiers that can be requested by the first information is not limited. That is, the second service area identifier can be one or more.

[0136] For the convenience of description, the following description is made by taking the case where the second service area identifier of the first multicast service requested by the first information is one as an example.

[0137] In one example, the second service area identifier of the first multicast service is used to identify an area consisting of one or more cells. For example, SAI 1 is used to identify an area consisting of cell a and cell b. In this case, SAI 1 = {cell a, cell b}. SAI 2 is used to identify an area consisting of cell a. In this case, SAI 2 = {cell a}. SAI 3 is used to identify an area consisting of cell a, cell b, and cell c. In this case, SAI 3 = {cell a, cell b, cell c}.

[0138] In addition, the second service area identifier may be used to identify the second service area, and specifically may also be used to indicate the location of the UE to the CN.

[0139] In another example, the second service area identity of the first multicast service can include one or more service area identities, each of which can be any number from 0 to 65535, wherein a service area identity of 0 can represent a set of cells of the entire network. The service area identity is configured by the operator and corresponds to one or more cells. For example, the second service area identity of the first multicast service can be {0}, or {123}, or {65534}, or {65531, 65532}, and the like.

[0140] In yet another example, the second service area identity of the first multicast service can be analogous to the structure and usage of the existing multimedia broadcast / multicast service service area identity (MBMS SAI).

[0141] Exemplarily, the first information is used to represent at least one of the following: a first service area (SA) of the first multicast service, a type of the first multicast service, or the first multicast service.

[0142] Embodiments of the present application do not limit the manner in which the first information represents the first service area of the first multicast service. For example, the first information includes the first service area of the first multicast service or an index / identity of the first service area, wherein the index / identity of the first service area is used to identify the first service area.

[0143] In one example, the first service area of the first multicast service can be composed of one or more MBMS SAIs, and in any case, each MBMS SA can contain no more than 256 MBMS SAIs. The MBMS SAI should identify a set of cells within the PLMN, which is independent of the relevant location / routing / service area and the physical location of the cell. One cell should be able to belong to one or more MBMS SA, and thus can be addressed by one or more MBMS SA. The MBMS SA is configuration information within the PLMN, which can be obtained by the application server through configuration, or through other means, such as reporting by the UE.

[0144] In another example, the first service area of the first multicast service can be composed of one or more cell identities (cell ids) or one or more tracking areas (TAs). Wherein the cell identity and the tracking area can be obtained by the application server through configuration, or through other means, such as reporting by the UE.

[0145] In yet another example, the first service area of the first multicast service can be constituted by information of a geographical area, such as a range of latitude and longitude coordinates, a street name, etc. Thereafter, other network elements (such as the NEF network element) in the PLMN network can convert the information of the geographical area into an identifier corresponding to the PLMN network, such as a cell list, which can include the identifier of one or more cells; or a tracking area list (TAI), which includes the identifier of one or more tracking areas; or a base station identifier list (RAN id list), which can include the identifier of one or more base stations.

[0146] The embodiments of the present application do not limit the manner in which the first information indicates the type of the first multicast service. For example, the first information includes the type of the first multicast service or an index / identifier of the type of the first multicast service, where the index / identifier of the type of the first multicast service is used to identify the type of the first multicast service.

[0147] The type of the first multicast service is used to identify the service type of the first multicast service. The service type can be used to identify a type of service. For example, the type of the first multicast service includes a public safety service type, a V2X service type, a Video service type, a broadcast television service type, a public safety service type, an IoT type of service type, or a general service type, etc. Specifically, the public safety service type can be used to identify a service whose service type is public safety.

[0148] For example, if the first multicast service is a map update service, the type of the first multicast service can be a public safety service type or a general service type.

[0149] For another example, if the first multicast service is a video transmission service, the type of the first multicast service can be a Video service type.

[0150] For yet another example, if the first multicast service is an IoT software upgrade service, the type of the first multicast service can be an IoT type of service type.

[0151] The embodiments of the present application do not limit the manner in which the first information indicates the first multicast service. For example, the first information includes the first multicast service or an identifier of the first multicast service, where the identifier of the first multicast service is used to identify the first multicast service.

[0152] For example, the identifier of the first multicast service can be the name of the first multicast service.

[0153] In some embodiments, the identifier of the first multicast service can also be implemented by other identifiers.

[0154] In one example, the other identifier includes an application identifier.

[0155] Further, the first multicast service can be determined according to the application identifier.

[0156] For example, the identifier of the first multicast service can be com.example.applicationid1, and the multicast session management network element determines that the first multicast service is a broadcast television type service according to all or part of the fields in com.example.applicationid1.

[0157] For another example, the identifier of the first multicast service can be com.facebook.xyz, and the multicast session management network element determines that the first multicast service is a video type service according to all or part of the fields in com.facebook.xyz, for example, according to the facebook identifier.

[0158] For still another example, the identifier of the first multicast service can be com.whatsapp, and the multicast session management network element determines that the first multicast service is a general type service according to all or part of the fields in com.whatsapp, for example, according to the whatsapp identifier.

[0159] In another example, the other identifier includes an identifier of a characteristic of the first multicast service. For example, an IP multicast address and / or a port number.

[0160] Further, the first multicast service can be determined according to the correspondence between the identifier of the characteristic of the first multicast service and the first multicast service.

[0161] S220, the multicast session management network element sends, to the application server, a second service area identifier of the first multicast service according to the first information.

[0162] Correspondingly, the application server receives the second service area identifier of the first multicast service sent by the multicast session management network element.

[0163] It should be noted that the number of the second service area identifiers sent by the multicast session management network element to the application server is not limited by the embodiments of the present application. That is, the number of the second service area identifiers sent by the multicast session management network element to the application server can be one or more.

[0164] For the convenience of description, the number of the second service area identifiers sent by the multicast session management network element to the application server is taken as one in the following description.

[0165] In some embodiments, S220 specifically comprises: determining, by the multicast session management network element, the second service area identifier of the first multicast service corresponding to the first information; and sending, by the multicast session management network element, the second service area identifier of the first multicast service to the application server.

[0166] It should be noted that the number of the second service area identifiers of the first multicast service determined by the multicast session management network element is not limited in the embodiments of the present application. That is, the number of the second service area identifiers of the first multicast service determined by the multicast session management network element can be one or more.

[0167] For the convenience of description, the number of the second service area identifiers of the first multicast service determined by the multicast session management network element is one in the following description.

[0168] When the first information is used to indicate the first service area of the first multicast service, the following modes A and B are taken as examples to introduce how the multicast session management network element determines the second service area identifier of the first multicast service corresponding to the first information.

[0169] Mode A: the multicast session management network element can first obtain the first cell list, or the first tracking area list, or the first base station list corresponding to the first multicast service according to the first information; and then the multicast session management network element obtains the second service area identifier of the first multicast service according to the first cell list, or the first tracking area list, or the first base station list.

[0170] For example, the multicast session management network element can obtain the service area identifier corresponding to the first cell list, or the first tracking area list, or the first base station list according to the correspondence between the cell list / tracking area list / base station list and the service area identifier, and take the service area identifier as the second service area identifier. In this example, the first service area of the first multicast service can be identified by the cell list, or the tracking area list, or the base station list.

[0171] The storage location of the correspondence between the cell list / tracking area list / base station list and the service area identifier is not limited in the embodiments of the present application.

[0172] In one example, the correspondence between the cell list / tracking area list / base station list and the service area identifier can be stored in the multicast session management network element.

[0173] For example, the multicast session management network element stores the correspondence between {SAI, cell id / TA id / RAN id}, finds the SAI corresponding to the first cell list, or the first tracking area list, or the first base station list according to the cell id / TA id / RAN id, and takes the SAI as the second service area identifier of the first multicast service.

[0174] In another example, the correspondence between the cell list / tracking area list / base station list and the service area identity can be stored in other network elements, such as the NEF, UDM, NRF, etc. At this time, the multicast session management network element sends a query request message to the network element (such as the UDM, NEF, NRF) for storing the correspondence between the cell list / tracking area list / base station list and the service area identity, and the query request message includes the first cell list or the first tracking area list or the first base station list. Thereafter, the network element for storing the correspondence between the cell list / tracking area list / base station list and the service area identity returns the service area identity corresponding to the first cell list or the first tracking area list or the first base station list to the multicast session management network element, and the multicast session management network element takes the service area identity as the second service area identity of the first multicast service.

[0175] In mode B, the multicast session management network element or other network elements (such as the NEF or the UDM, etc.) in the network can authenticate the service area of the first multicast service, for example, whether the application server is authorized to transmit multicast broadcast service data in the service area of the first multicast service. If the authentication is passed, the multicast session management network element takes the service area of the first multicast service as the second service area identity of the first multicast service. Alternatively, if the authentication is partially passed (for example, the application server is only authorized to transmit multicast broadcast service data in part of the area), the multicast session management network element takes the authorized part of the service area of the first multicast service as the second service area identity of the first multicast service.

[0176] When the first information includes the type of the first multicast service, the following mode C is taken as an example to introduce how the multicast session management network element determines the second service area identity of the first multicast service corresponding to the first information.

[0177] In mode C, the multicast session management network element can obtain the service area identity corresponding to the type of the first multicast service through the locally configured correspondence between the type of the multicast service and the service area identity, and take the service area identity as the second service area identity of the first multicast service.

[0178] In one example, the PLMN network uses different service areas for different services, and the PLMN network configures the correspondence between the type of the service and the service area at the multicast session management network element. For example, the correspondence such as {service type 1, SA a}, {service type 2, SA b} is configured at the multicast session management network element. The multicast session management network element finds the service area (such as SA a) corresponding to the type of the first multicast service (such as service type 1) according to the type of the first multicast service and the above-mentioned correspondence (such as {service type 1, SA a}), which is the second service area identity of the first multicast service.

[0179] In another example, the PLMN network stores the correspondence between the type of service and the service area (e.g., {service type 1, SA a}, {service type 2, SA b}) in a certain specific network element (e.g., NEF, UDM, NRF, etc.), and the multicast session management network element sends the type of the first multicast service (e.g., service type 1) to the network element storing the correspondence between the type of service and the service area, and the network element storing the correspondence between the type of service and the service area finds the service area corresponding to the type of the first multicast service (e.g., SA a) according to the type of the first multicast service and the above correspondence (e.g., {service type 1, SA a}), which is the second service area identifier of the first multicast service, and returns to the multicast session management network element.

[0180] When the first information includes the identifier of the first multicast service, the multicast session management network element can first obtain the first multicast service according to the identifier of the first multicast service, and then determine the second service area identifier of the first multicast service according to the type of the first multicast service.

[0181] It should be noted that when the first information is used to indicate the first service area of the first multicast service, the first information includes the type of the first multicast service, or the first information includes the identifier of the first multicast service, the multicast session management network element can determine the second service area identifier according to at least one of the above schemes of determining the second service area identifier according to the service area of the first multicast service indicated by the first information, determining the second service area identifier according to the type of the first multicast service included in the first information, or determining the second service area identifier according to the identifier of the first multicast service included in the first information.

[0182] It should be noted that when the first information is used to indicate the first service area of the first multicast service, the first information includes the type of the first multicast service, or the first information includes the identifier of the first multicast service, the multicast session management network element can determine the second service area identifier according to at least one of the above schemes of determining the second service area identifier according to the service area of the first multicast service indicated by the first information, determining the second service area identifier according to the type of the first multicast service included in the first information, or determining the second service area identifier according to the identifier of the first multicast service included in the first information.

[0183] S230, the application server informs the terminal device of the second service area identifier of the first multicast service. That is, the application server sends the second service area identifier of the first multicast service to the terminal device.

[0184] Correspondingly, the terminal device receives the second service area identifier of the first multicast service from the application server.

[0185] The communication method 200 provided in the above embodiments is used, the application server sends first information to the multicast session management network element, and requests the second service area identifier of the first multicast service. Further, the multicast session management network element sends the second service area identifier of the first multicast service to the application server according to the first information, and thus the second service area identifier of the first multicast service can be acquired without the application server knowing the network topology information.

[0186] In some embodiments, S210 to S230 can be implemented in the process in which the application server requests to allocate the temporary multicast group identifier.

[0187] For example, the first information in S210 can be carried in the existing temporary multicast group identifier allocation request (nnef_tmgi_allocate request) message. The second service area identifier of the first multicast service in S220 can be carried in the response message of the existing temporary multicast group identifier allocation request message. The second service area identifier of the first multicast service in S230 can be carried in the existing service announcement (service announcement) message, service announcement message, or service / service notification message.

[0188] For example, S210 and S220 are implemented by using the existing message in the process in which the application server requests to allocate the temporary multicast group identifier. S230 is implemented by using the existing message in the process in which the application server requests to allocate the temporary multicast group identifier. For example, S210 and S220 are executed after the existing application server receives the response message of the temporary multicast group identifier allocation request message, and before the existing service announcement (service announcement) message of the application server. The second service area identifier of the first multicast service in S230 can be carried in the existing service announcement (service announcement) message.

[0189] Optionally, in some embodiments, as shown in the communication method 200, S240 is further included. Figure 3

[0190] S240, the multicast session management network element sends second information of the first multicast service to the application server.

[0191] Correspondingly, the application server receives the second information of the first multicast service from the multicast session management network element.

[0192] It should be noted that the second information can be a message or a signal element in the message, and is not limited. ​

[0193] The second information includes at least one of the following: a frequency of the first multicast service, or a temporary multicast group identifier of the first multicast service.

[0194] It should be noted that in this embodiment, S240 only needs to be executed after S210. The embodiment of the present application does not limit the sequence between S240 and S220 and S230.

[0195] It should be noted that the embodiment of the present application does not limit the number of the frequency of the first multicast service and / or the number of the temporary multicast group identifier of the first multicast service sent by the multicast session management network element to the application server. That is, the number of the frequency of the first multicast service and / or the number of the temporary multicast group identifier of the first multicast service sent by the multicast session management network element to the application server can be one or more.

[0196] For the convenience of description, the following will be described by taking one as an example for the number of the frequency of the first multicast service and / or the number of the temporary multicast group identifier of the first multicast service determined by the multicast session management network element.

[0197] In some embodiments, S240 specifically includes: the multicast session management network element determines the second information of the first multicast service corresponding to the first information according to the first information, and the multicast session management network element sends the second information of the first multicast service to the application server.

[0198] It should be noted that the embodiment of the present application does not limit the number of the frequency of the first multicast service and / or the number of the temporary multicast group identifier of the first multicast service determined by the multicast session management network element. That is, the number of the frequency of the first multicast service and / or the number of the temporary multicast group identifier of the first multicast service determined by the multicast session management network element can be one or more.

[0199] For the convenience of description, the following will be described by taking one as an example for the number of the frequency of the first multicast service and / or the number of the temporary multicast group identifier of the first multicast service determined by the multicast session management network element.

[0200] Exemplarily, the multicast session management network element determines the frequency / temporary multicast group identifier of the multicast service corresponding to the first service area / type of the first multicast service / the first multicast service according to the frequency / temporary multicast group identifier of the multicast service and the service area / type of the multicast service / corresponding relationship of the multicast service, and takes it as the frequency / temporary multicast group identifier of the first multicast service.

[0201] The storage location of the correspondence between the frequency of the multicast service and the service area or the type of the multicast service or the multicast service is not limited in the embodiments of the present application. For example, it can be stored in the multicast session management network element; or it can be stored in other network elements, such as NEF, UDM, NRF, etc. When the correspondence between the frequency of the multicast service and the service area is stored in other network elements, the multicast session management network element can obtain the frequency / temporary multicast group identifier of the first multicast service by interacting with other network elements.

[0202] In some embodiments, the correspondence between the frequency of the multicast service and the service area or the type of the multicast service or the multicast service can also be replaced by the correspondence between the frequency of the multicast service and the temporary multicast group identifier, the cell identifier, the tracking area identifier or the base station identifier. At this time, the multicast session management network element can first determine the first cell identifier, the first tracking area identifier or the first base station identifier corresponding to the first service area according to the first service area of the first multicast service; then, determine the frequency / temporary multicast group identifier of the multicast service corresponding to the first cell identifier, the first tracking area identifier or the first base station identifier corresponding to the first service area according to the correspondence between the frequency of the multicast service and the temporary multicast group identifier, the cell identifier, the tracking area identifier or the base station identifier, and take it as the frequency / temporary multicast group identifier of the first multicast service.

[0203] Exemplarily, the multicast session management network element can also determine that the temporary multicast group identifier of the first multicast service needs to be allocated according to the first information, wherein the first information does not contain the temporary multicast group identifier of the first multicast service. For example, the multicast session management network element selects an available temporary multicast group identifier from the resource pool of the network preconfigured temporary multicast group identifier as the temporary multicast group identifier of the first multicast service.

[0204] The storage location of the resource pool of the network preconfigured temporary multicast group identifier is not limited in the embodiments of the present application. For example, it can be stored in the multicast session management network element; or it can be stored in other network elements, such as NEF, UDM, NRF, etc. When the resource pool of the temporary multicast group identifier is stored in other network elements, the multicast session management network element can obtain the temporary multicast group identifier of the first multicast service by interacting with other network elements.

[0205] It should be noted that in some embodiments, the multicast session management network element can perform both the scheme of determining the frequency of the first multicast service corresponding to the first information according to the first information and the scheme of determining the temporary multicast group identifier of the first multicast service corresponding to the first information according to the first information.

[0206] In some embodiments, S240 specifically comprises: determining, by the multicast session management network element, the second information of the first multicast service corresponding to the second service area identifier of the first multicast service according to the second service area identifier of the first multicast service; and sending, by the multicast session management network element, the second information of the first multicast service to the application server.

[0207] For example, the multicast session management network element can determine the second information of the first multicast service corresponding to the second service area identifier of the first multicast service according to the correspondence between the frequency / temporary multicast group identifier of the multicast service and the service area. The specific process can refer to the description in the foregoing, which will not be described here.

[0208] The storage location of the correspondence between the frequency / temporary multicast group identifier of the multicast service and the service area is not limited in the embodiments of the present application. For example, it can be stored in the multicast session management network element; or it can be stored in other network elements, such as UDM, user data repository (UDR), PCF, NRF, NEF, MBSF NEF, UDM, NRF, or a network element dedicated to multicast broadcast, which can be deployed separately or realized by enhancing the function of an existing network element, etc. When the correspondence between the network device and its corresponding service area is stored in other network elements, the multicast session management network element can obtain the second information of the first multicast service corresponding to the second service area identifier of the first multicast service by interacting with other network elements.

[0209] Optionally, in some embodiments, as shown in Figure 3 The communication method 200 further comprises S250.

[0210] S250, the application server informs the terminal device of the second information of the first multicast service. That is, the application server sends the second information of the first multicast service to the terminal device.

[0211] Correspondingly, the terminal device receives the second information of the first multicast service from the application server.

[0212] In some embodiments, S240 and S250 can also be implemented in the process of requesting the application server to allocate the temporary multicast group identifier.

[0213] For example, S240 can be implemented by the existing message in the process of requesting the application server to allocate the temporary multicast group identifier. For example, the second information in S240 can be carried in the response message of the existing temporary multicast group identifier allocation request message. The second information of the first multicast service in S250 can be carried in the existing service announcement message.

[0214] Exemplarily, S240 is implemented by a message existing in a procedure of requesting the application server to allocate the temporary multicast group identifier. S250 is implemented by a message existing in a procedure of requesting the application server to allocate the temporary multicast group identifier. For example, S240 is executed after the existing application server receives a response message of the temporary multicast group identifier allocation request message, and before a service announcement message of the existing application server. The second information of the first multicast service in S250 can be carried in the existing service announcement message.

[0215] Optionally, in some embodiments, as shown in the communication method 200 further comprises S260 and S270. Figure 3

[0216] S260, the application server sends a session creation request message to the multicast session management network element.

[0217] Correspondingly, the multicast session management network element receives the session creation request message from the application server.

[0218] In some embodiments, the session creation request message can be understood as the multicast session creation request message described above.

[0219] It should be noted that the session creation request message can be executed in a procedure of the application server requesting the first service area identifier of the first multicast service, or can be understood as being executed in a procedure of the multicast session management network element allocating / configuring the first service area identifier.

[0220] Optionally, the session creation request message can or can not carry the first service area of the first multicast service, the second service area identifier of the first multicast service, and / or the second information of the first multicast service.

[0221] S270, the multicast session management network element informs the first network device of the second service area identifier of the first multicast service according to the session creation request message.

[0222] Optionally, the multicast session management network element can also inform the first network device of the frequency of the first multicast service, the first service area of the first multicast service, and / or the temporary multicast group identifier of the first multicast service.

[0223] Optionally, in some embodiments, S270 specifically comprises: the multicast session management network element determines the first network device; and informs the first network device of the second service area identifier of the first multicast service.

[0224] ​In one example, the multicast session management network element can determine the first network device according to a local configuration or a first service area of the first multicast service.

[0225] Illustratively, the multicast session management network element can determine the network device corresponding to the first service area of the first multicast service according to the correspondence between the network device and the service area corresponding thereto (e.g., cell id / list, TA id / list, RAN id / list, etc.), and take it as the first network device.

[0226] Embodiments of the present application do not limit the storage location of the correspondence between the network device and the service area corresponding thereto. For example, it can be stored in the multicast session management network element; or it can be stored in other network elements, such as NEF, UDM, NRF, etc. When the correspondence between the network device and the service area corresponding thereto is stored in other network elements, the multicast session management network element can obtain the first network device by interacting with other network elements.

[0227] In another example, the multicast session management network element can forward the content carried by the session creation request message to the first access and mobility management function. In turn, the first access and mobility management function determines the first network device according to a local configuration or a first service area of the first multicast service. The first access and mobility management function also informs the first network device of the second service area of the first multicast service.

[0228] Illustratively, the multicast session management network element can determine the access and mobility management function corresponding to the first service area of the first multicast service according to the correspondence between the access and mobility management function and the service area corresponding thereto (e.g., cell id / list, TA id / list, RAN id / list, etc.), and take it as the first access and mobility management function.

[0229] Embodiments of the present application do not limit the storage location of the correspondence between the access and mobility management function and the service area corresponding thereto. For example, it can be stored in the multicast session management network element; or it can be stored in other network elements, such as NEF, UDM, NRF, etc. When the correspondence between the access and mobility management function and the service area corresponding thereto is stored in other network elements, the multicast session management network element can obtain the first access and mobility management function by interacting with other network elements.

[0230] Further, in one example, the first access and mobility management function can determine the network device corresponding to the first service area of the first multicast service according to the correspondence between the network device and the service area corresponding thereto (e.g., cell id / list, TA id / list, RAN id / list, etc.), and take it as the first network device.

[0231] The storage location of the correspondence between the network device and the corresponding service area is not limited in the embodiments of the present application. For example, it can be stored in the first access and mobility management function network element; or it can be stored in other network elements, such as NEF, UDM, NRF, etc. When the correspondence between the network device and the corresponding service area is stored in other network elements, the first access and mobility management function network element can obtain the first network device by interacting with other network elements.

[0232] In another example, the first access and mobility management function can send the first service area of the first multicast service and / or the second service area identifier of the first multicast service to all network devices establishing a next generation application protocol (NGAP) connection. After receiving the first service area of the first multicast service and the second service area identifier of the first multicast service, the network device determines whether it is located in the first service area and / or the second service area of the first multicast service. Wherein, when the cell or tracking area corresponding to the network device has an intersection with the first service area and / or the second service area of the first multicast service, or when the cell or tracking area corresponding to the network device includes the first service area and / or the second service area of the first multicast service, it can be considered that the network device is located in the first service area and / or the second service area of the first multicast service. Thereafter, the network device can feed back the judgment result to the first access and mobility management function. In the case where the judgment result indicates that the network device is located in the first service area and / or the second service area of the first multicast service, the network device can be the first network device.

[0233] The specific form of the judgment result is not limited in the embodiments of the present application. For example, the judgment result can be success or failure, when the judgment result is success, that is, the network device is located in the first service area and / or the second service area of the first multicast service. When the judgment result is failure, that is, the network device is not located in the first service area and / or the second service area of the first multicast service.

[0234] Optionally, the network device can also feed back success information to the first access and mobility management function only in the case where the network device is located in the first service area and / or the second service area of the first multicast service. At this time, the network device corresponding to the success information received by the first access and mobility management function can be the first network device.

[0235] Through S270, when the multicast session management network element allocates the second service area identifier of the first multicast service, the multicast session management network element also notifies the corresponding network device of the second service area identifier of the first multicast service, so that the corresponding network device, i.e., the first network device, can broadcast the second service area identifier of the first multicast service in a dynamic manner.

[0236] Optionally, in some embodiments, as shown in FIG. 2, the communication method 200 further includes S280. Figure 4

[0237] S280, the first network device sends a response message to the multicast session management network element. The response message is used to indicate that the first network device has received the second service area identifier of the first multicast service.

[0238] Correspondingly, the multicast session management network element receives the response message from the first network device.

[0239] Optionally, in some embodiments, as shown in FIG. 2, the communication method 200 further includes S290. Figure 2

[0240] S290, the first network device broadcasts the second service area identifier of the first multicast service.

[0241] Optionally, the first network device can also broadcast the frequency of the first multicast service, the first service area of the first multicast service, and / or the temporary multicast group identifier of the first multicast service.

[0242] Optionally, the first network device can carry the second service area identifier of the first multicast service in a system broadcast message, broadcast the frequency of the first multicast service, the first service area of the first multicast service, and / or the temporary multicast group identifier of the first multicast service.

[0243] In some embodiments, the application server can transmit information between the network presentation function or the multicast broadcast service function and the multicast session management network element through the network.

[0244] For example, the application server first sends the first information to the network presentation function or the multicast broadcast service function, and then the network presentation function or the multicast broadcast service function sends the first information to the multicast session management network element.

[0245] For another example, the multicast session management network element first sends the second information or the second service area identifier of the first multicast service to the network presentation function or the multicast broadcast service function, and then the network presentation function or the multicast broadcast service function sends the second information or the second service area identifier of the first multicast service to the application server.

[0246] ​​In the embodiment that the application server transmits information between the network presentation function or the multicast broadcast service function and the multicast session management network element through the network, after the network presentation function or the multicast broadcast service function receives the first information described above in S210, the network presentation function or the multicast broadcast service function can perform authentication for the request of the application server. The authentication can be mainly achieved by querying the subscription information of the application server.

[0247] For example, the network presentation function or the multicast broadcast service function can perform authentication on whether the application server itself can send the first information, on the parameters sent by the application server (for example, the content specifically represented by the first information), on whether the application server can request the second service area identifier of the first multicast service, and the like.

[0248] If the authentication of the application server is passed, the network presentation function or the multicast broadcast service function can obtain the identifier information of the multicast broadcast service function by querying the NRF network storage function. For example, the application server can indicate the data network name, slice, and the like in the first information in S210, and the network presentation function or the multicast broadcast service function can take these information as the input of the NRF query, and then obtain the identifier of the multicast broadcast service function, and then send the first information to the multicast broadcast service function. For another example, the network presentation function or the multicast broadcast service function can obtain the identifier information of the multicast broadcast service function by local configuration, and then send the first information to the multicast broadcast service function.

[0249] In other embodiments, if the application server has the ability to provide information to the core network or to call the services exposed by the core network element, the application server can directly communicate with the multicast session management network element.

[0250] It can be understood that some optional features in the embodiments of the present application can not depend on other features in some scenarios, or can be combined with other features in some scenarios, and are not limited.

[0251] It can also be understood that the solutions in the embodiments of the present application can be reasonably combined, and the explanations or descriptions of various terms appearing in the embodiments can be mutually referenced or explained in various embodiments, and this is not limited.

[0252] It can also be understood that the size of various serial numbers in the embodiments of the present application does not mean the order of execution, but is only a distinction for convenience of description, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0253] It can also be understood that some message names are involved in the embodiments of the present application, such as the temporary multicast group identifier allocation request message, and the like, and it should be understood that the naming does not limit the protection scope of the embodiments of the present application.

[0254] It can also be understood that, in each of the above communication method embodiments, the communication method and operation implemented by the multicast session management network element can also be implemented by a component (such as a chip or circuit) of the multicast session management network element; the communication method and operation implemented by the application server can also be implemented by a component (such as a chip or circuit) of the application server; and in addition, the communication method and operation implemented by the first network device can also be implemented by a component (such as a chip or circuit) of the first network device, without limitation.

[0255] Corresponding to the communication method given in each of the above communication method embodiments, the embodiments of the present application also provide a corresponding device, which includes a module for performing the corresponding modules of each of the above communication method embodiments. The module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in each of the above communication method embodiments are also applicable to the following device embodiments.

[0256] Figure 3 is a schematic block diagram of a device provided by the embodiments of the present application. The device 400 includes a transceiver unit 410, which can be used to implement the corresponding communication function. The transceiver unit 410 can also be referred to as a communication interface or a communication unit.

[0257] Optionally, the device 400 can also include a processing unit 420, which can be used for data processing.

[0258] Optionally, the device 400 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 420 can read the instructions and / or data in the storage unit, so that the device implements the actions of different devices in each of the above communication method embodiments, such as the actions of the multicast session management network element, the application server, and the first network device.

[0259] The device 400 can be used to perform the actions of the multicast session management network element in each of the above communication method embodiments. At this time, the device 400 can be the multicast session management network element or a component of the multicast session management network element. The transceiver unit 410 is used to perform the transceiver-related operations on the multicast session management network element side in the above communication method embodiments, and the processing unit 420 is used to perform the processing-related operations on the multicast session management network element side in the above communication method embodiments.

[0260] As a design, the device 400 is used to perform the actions of the multicast session management network element in each of the above communication method embodiments.

[0261] In a possible implementation, the transceiver 410 is configured to receive first information of a first multicast service from an application server, the first information being used to indicate at least one of a first service area of the first multicast service, a type of the first multicast service, or the first multicast service; and the processing unit 420 is configured to send, to the application server, a second service area identification of the first multicast service according to the first information.

[0262] Optionally, the processing unit 420 is further configured to determine the second service area identification of the first multicast service corresponding to the first information; and send, to the application server, the second service area identification of the first multicast service.

[0263] Optionally, the transceiver 410 is further configured to send, to the application server, second information of the first multicast service, the second information including at least one of a frequency of the first multicast service or a temporary multicast group identification of the first multicast service.

[0264] Optionally, the first information is carried in a temporary multicast group identification allocation request message.

[0265] Optionally, the second service area identification of the first multicast service is carried in a response message of the temporary multicast group identification allocation request message.

[0266] Optionally, the transceiver 410 is further configured to receive, by the multicast session management network element, a session creation request message from the application server; and the processing unit 420 is further configured to inform, by the multicast session management network element, a first network device of the second service area identification of the first multicast service according to the session creation request message.

[0267] The apparatus 400 can implement steps or procedures performed by the multicast session management network element in the communication method embodiments according to the embodiments of the present application. The apparatus 400 can include units for performing the communication method performed by the multicast session management network element in the embodiments shown in the figures, or include units for performing the communication method performed by the multicast session management network element in the embodiments shown in the figures. Figure 2 The apparatus 400 can implement steps or procedures performed by the multicast session management network element in the communication method embodiments according to the embodiments of the present application. The apparatus 400 can include units for performing the communication method performed by the multicast session management network element in the embodiments shown in the figures, or include units for performing the communication method performed by the multicast session management network element in the embodiments shown in the figures. Figure 3 The apparatus 400 can implement steps or procedures performed by the multicast session management network element in the communication method embodiments according to the embodiments of the present application. The apparatus 400 can include units for performing the communication method performed by the multicast session management network element in the embodiments shown in the figures, or include units for performing the communication method performed by the multicast session management network element in the embodiments shown in the figures.

[0268] It should be understood that the specific process of each unit performing the corresponding steps is described in detail in the above communication method embodiments, and is not described here for brevity.

[0269] As another design, the apparatus 400 is configured to perform the actions performed by the application server in the above communication method embodiments.

[0270] In a possible implementation, the transceiver 410 is configured to send, to a multicast session management network element, first information of a first multicast service, the first information comprising at least one of: a first service area of the first multicast service, a type of the first multicast service, or the first multicast service; the transceiver 410 is further configured to receive, from the multicast session management network element, a second service area identifier of the first multicast service; and the transceiver 410 is further configured to inform a terminal device of the second service area identifier of the first multicast service.

[0271] Optionally, the transceiver 410 is further configured to receive, from the multicast session management network element, second information of the first multicast service, the second information comprising at least one of: a frequency of the first multicast service, or a TMGI of the first multicast service.

[0272] Optionally, the first information is carried in a temporary multicast group identifier (TMGI) allocation request message.

[0273] Optionally, the second service area identifier of the first multicast service is carried in a response message of the TMGI allocation request message.

[0274] Optionally, the transceiver 410 is further configured to inform the terminal device of the second service area identifier of the first multicast service by carrying the second service area identifier of the first multicast service in a service announcement message.

[0275] The apparatus 400 can implement the steps performed by the application server in the method embodiments of the communication method according to the embodiments of the present application. The apparatus 400 can include units configured to perform the steps of the method embodiments of the communication method performed by the application server in the embodiments shown, or include units configured to perform the steps of the method embodiments of the communication method performed by the application server in the embodiments shown. Figure 3 The apparatus 400 can implement the steps performed by the application server in the method embodiments of the communication method according to the embodiments of the present application. The apparatus 400 can include units configured to perform the steps of the method embodiments of the communication method performed by the application server in the embodiments shown, or include units configured to perform the steps of the method embodiments of the communication method performed by the application server in the embodiments shown. Figure 4 The apparatus 400 can implement the steps performed by the application server in the method embodiments of the communication method according to the embodiments of the present application. The apparatus 400 can include units configured to perform the steps of the method embodiments of the communication method performed by the application server in the embodiments shown, or include units configured to perform the steps of the method embodiments of the communication method performed by the application server in the embodiments shown.

[0276] It should be understood that the specific process in which each unit performs the corresponding steps described above has been described in detail in each of the method embodiments of the communication method, and for the sake of brevity, will not be described here.

[0277] As yet another design, the apparatus 400 is configured to perform the actions performed by the first network device in each of the method embodiments of the communication method.

[0278] In a possible implementation, the transceiver 410 is configured to receive a second service area identifier of a first multicast service; and the transceiver 410 is further configured to broadcast the second service area identifier of the first multicast service.

[0279] Optionally, the transceiver 410 is further configured to: receive second information of the first multicast service and / or a first service area of the first multicast service; and broadcast the second information of the first multicast service and / or the first service area of the first multicast service; wherein the second information comprises at least one of a frequency of the first multicast service or a temporary multicast group identity of the first multicast service.

[0280] The apparatus 400 can implement the steps or procedures corresponding to those performed by the application server in the embodiments of the communication method according to the embodiments of the present application. The apparatus 400 can include a processor 401, a memory 402 and a transceiver 410. Figure 5 The apparatus 400 can implement the steps or procedures corresponding to those performed by the application server in the embodiments of the communication method according to the embodiments of the present application. The apparatus 400 can include a processor 401, a memory 402 and a transceiver 410.

[0281] It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above embodiments of the communication method, and for the sake of brevity, it will not be repeated here.

[0282] It should also be understood that the apparatus 400 herein is embodied in the form of functional units. The term "unit" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combination of logical circuits and / or other suitable components supporting the described functions. In one optional example, those skilled in the art can understand that the apparatus 400 can be specifically a multicast session management network element in the above embodiments, and can be used to perform the respective procedures and / or steps corresponding to the multicast session management network element in the above embodiments of the communication method. Alternatively, the apparatus 400 can be specifically an application server in the above embodiments, and can be used to perform the respective procedures and / or steps corresponding to the application server in the above embodiments of the communication method. Alternatively, the apparatus 400 can be specifically a first network device in the above embodiments, and can be used to perform the respective procedures and / or steps corresponding to the first network device in the above embodiments of the communication method. To avoid repetition, it will not be repeated here.

[0283] The apparatus 400 of each of the above-mentioned schemes has a function of implementing the corresponding steps performed by the multicast session management network element in the above-mentioned communication method, or the apparatus 700 of each of the above-mentioned schemes has a function of implementing the corresponding steps performed by the application server in the above-mentioned communication method, or the apparatus 700 of each of the above-mentioned schemes has a function of implementing the corresponding steps performed by the first network device in the above-mentioned communication method. The function can be implemented by hardware, or implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, 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 the processing unit can be replaced by a processor, which respectively performs the transceiving operation and the related processing operation in each of the communication method embodiments.

[0284] In addition, the transceiver unit 410 can also be a transceiver circuit (for example, can include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0285] It should be noted that, Figure 5 The apparatus in the above-mentioned embodiments can be a network element or a device, or a chip or a chip system, for example, a system on chip (SoC). The transceiver unit can be an input / output circuit or a communication interface, and the processing unit can be a processor or a microprocessor integrated on the chip or an integrated circuit. In this regard, no limitation is made.

[0286] As shown in FIG. 5, Figure 2 The embodiment of the present application provides another apparatus 500. The apparatus 500 includes a processor 510, the processor 510 is coupled with a memory 520, the memory 520 is used to store computer programs or instructions and / or data, and the processor 510 is used to execute the computer programs or instructions stored in the memory 520, or read the data stored in the memory 520, so as to perform the communication method in each of the above-mentioned communication method embodiments.

[0287] Optionally, the processor 510 is one or more.

[0288] Optionally, the memory 520 is one or more.

[0289] Optionally, the memory 520 is integrated with the processor 510, or is separately arranged.

[0290] Optionally, as shown in FIG. 5, Figure 3 The apparatus 500 further includes a transceiver 530, which is used for receiving and / or sending signals. For example, the processor 510 is used to control the transceiver 530 to receive and / or send signals.

[0291] As an option, the apparatus 500 is configured to implement the operations performed by the multicast session management network element in the various embodiments of the communication method described above.

[0292] For example, the processor 510 is configured to execute the computer programs or instructions stored in the memory 520 to implement the operations of the application server in the various embodiments of the communication method described above. For example, Figure 2 the communication method performed by the application server in the embodiments described above, or Figure 3 the communication method performed by the application server in the embodiments described above.

[0293] For another example, the processor 510 is configured to execute the computer programs or instructions stored in the memory 520 to implement the operations of the first network device in the various embodiments of the communication method described above. For example, Figure 3 the communication method performed by the first network device in the embodiments described above. Figure 6 the communication method performed by the first network device in the embodiments described above.

[0294] For another example, the processor 510 is configured to execute the computer programs or instructions stored in the memory 520 to implement the operations of the first network device in the various embodiments of the communication method described above. For example, Figure 2 the communication method performed by the first network device in the embodiments described above.

[0295] It should be understood that the processor mentioned in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0296] It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. As an example but not limitation, the RAM includes the following various forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM).

[0297] It should be noted that when the processor is a general processor, a DSP, an ASIC, a FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, the memory (storage module) can be integrated in the processor.

[0298] It should also be noted that the memory described herein is intended to include, but not limited to, these and any other suitable type of memory.

[0299] As Figure 3 , the embodiments of the present application provide a chip system 600. The chip system 600 (or also can be called a processing system) includes a logic circuit 610 and an input / output interface 620.

[0300] The logic circuit 610 can be a processing circuit in the chip system 600. The logic circuit 610 can be coupled with the storage unit, invoke instructions in the storage unit, so that the chip system 600 can implement the communication method and functions of the embodiments of the present application. The input / output interface 620 can be an input / output circuit in the chip system 600, output information processed by the chip system 600, or input data or signaling information to be processed by the chip system 600 for processing.

[0301] Specifically, for example, if the multicast session management network element is installed with the chip system 600, the logic circuit 610 is coupled with the input / output interface 620, the logic circuit 610 can receive first information of a first multicast service from an application server through the input / output interface 620; or the input / output interface 620 can input the first information from the application server to the logic circuit 610 for processing. For another example, if the application server is installed with the chip system 600, the logic circuit 610 is coupled with the input / output interface 620, the logic circuit 610 can send first information of a first multicast service to a multicast session management network element through the input / output interface 620; or receive a second service area identifier of the first multicast service from the multicast session management network element through the input / output interface 620; or inform a terminal device of the second service area identifier of the first multicast service through the input / output interface 620. For another example, if the first network device is installed with the chip system 600, the logic circuit 610 is coupled with the input / output interface 620, the logic circuit 610 can receive a second service area identifier of a first multicast service through the input / output interface 620; or broadcast the second service area identifier of the first multicast service through the input / output interface 620.

[0302] As a solution, the chip system 600 is used to implement operations performed by a multicast session management network element in the above various embodiments of the communication method.

[0303] For example, the logic circuit 610 is used to implement operations related to processing performed by a multicast session management network element in the above embodiments of the communication method, such as, Figure 2 operations related to processing performed by a multicast session management network element in the embodiments shown in the above table, or Figure 3 operations related to processing performed by a multicast session management network element in the embodiments shown in the above table; the input / output interface 620 is used to implement operations related to sending and / or receiving performed by a multicast session management network element in the above embodiments of the communication method, such as, Figure 2 operations related to sending and / or receiving performed by a multicast session management network element in the embodiments shown in the above table, or Figure 3 operations related to sending and / or receiving performed by a multicast session management network element in the embodiments shown in the above table.

[0304] For another example, the logic circuit 610 is configured to implement the processing-related operations performed by the application server in the above-mentioned embodiments of the communication method, such as, Figure 2 the processing-related operations performed by the application server in the embodiments of Figs. 1-3, or Figure 3 the processing-related operations performed by the application server in the embodiments of Figs. 1-3. Figure 3 the sending and / or receiving-related operations performed by the application server in the above-mentioned embodiments of the communication method, such as, Figure 3 the sending and / or receiving-related operations performed by the application server in the embodiments of Figs. 1-3, or the sending and / or receiving-related operations performed by the application server in the embodiments of Figs. 1-3.

[0305] For another example, the logic circuit 610 is configured to implement the processing-related operations performed by the first network device in the above-mentioned embodiments of the communication method, such as, Figure 3 the processing-related operations performed by the first network device in the embodiments of Figs. 1-3, or ​ the sending and / or receiving-related operations performed by the first network device in the above-mentioned embodiments of the communication method, such as,

[0306] The embodiments of the present application also provide a computer readable storage medium, having stored thereon computer instructions for implementing the communication method performed by the multicast session management network element, the application server, or the first network device in the above-mentioned embodiments of the communication method.

[0307] For example, the computer program, when executed by a computer, enables the computer to implement the communication method performed by the multicast session management network element in the above-mentioned embodiments of the communication method.

[0308] The embodiments of the present application also provide a computer program product, containing instructions, which, when executed by a computer, implement the communication method performed by the multicast session management network element, the application server, or the first network device in the above-mentioned embodiments of the communication method.

[0309] The embodiments of the present application also provide a communication system, which includes the multicast session management network element, the application server, and the first network device in the above-mentioned embodiments. For example, the system contains ​ the multicast session management network element, the application server, and the first network device in the embodiments of Figs. 1-3.

[0310] The explanations and advantages of the related contents in any of the above-mentioned apparatuses can refer to the corresponding embodiments of the communication method provided above, which will not be repeated here.

[0311] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and communication method can be implemented by other manners. For example, the apparatus embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, apparatuses or units, and can be electrical, mechanical or other forms.

[0312] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. For example, the computer can be a personal computer, a server or a network device. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (such as floppy disk, hard disk, magnetic tape), optical media (such as DVD), or semiconductor media (such as solid state disk (SSD) and the like. For example, the foregoing available media includes but is not limited to: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and various media that can store program codes.

[0313] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: The multicast session management network element receives first information of a first multicast service from an application server, where the first information is used to indicate a first service area or an application identifier of the first multicast service; The multicast session management network element sends a second service area identifier of the first multicast service to the application server according to the first information; The multicast session management network element receives a session creation request message from the application server; The multicast session management network element notifies the first network device of the second service area identifier of the first multicast service according to the session creation request message.

2. The communication method according to claim 1, wherein: The multicast session management network element sending, according to the first information, a second service area identifier of the first multicast service to the application server, comprising: determining, by the multicast session management network element, a second service area identifier of the first multicast service corresponding to the first information; The multicast session management network element sends a second service area identifier of the first multicast service to the application server.

3. The communication method according to claim 1 or 2, characterized in that: The method further comprises: The multicast session management network element sends second information of the first multicast service to the application server, where the second information includes at least one of the following: the frequency of the first multicast service, or a temporary multicast group identifier of the first multicast service.

4. The communication method according to claim 1 or 2, characterized in that: The first information is carried in a temporary multicast group identifier allocation request message.

5. The communication method according to claim 4, wherein: The second service area identifier of the first multicast service is carried in a response message to the temporary multicast group identifier allocation request message.

6. A communication method, characterized in that: include: The application server sends first information of a first multicast service to the multicast session management network element, where the first information includes a first service area or an application identifier of the first multicast service; The application server receives a second service area identifier and second information of the first multicast service from the multicast session management network element, wherein the second information includes at least one of the following: a frequency of the first multicast service, or a temporary multicast group identifier of the first multicast service; The application server carries the second service area identifier of the first multicast service and the second information in a service announcement message to inform the terminal device.

7. The communication method according to claim 6, wherein: The first information is carried in a temporary multicast group identifier allocation request message.

8. The communication method according to claim 7, wherein: The second service area identifier of the first multicast service is carried in a response message to the temporary multicast group identifier allocation request message.

9. A communication device, characterized in that: include: A processor, configured to execute computer instructions stored in the memory, so that the apparatus performs: the communication method according to any one of claims 1 to 5; or The communication method according to any one of claims 6 to 8.

10. A computer storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the communication method according to any one of claims 1 to 5 is implemented; or So as to realize the communication method as claimed in any one of claims 6 to 8.

11. A communication system, characterized in that: include: A multicast session management network element, an application server, and / or a first network device, wherein: The multicast session management network element is configured to execute the communication method according to any one of claims 1 to 5; or The application server is configured to execute the communication method according to any one of claims 6 to 8.

12. A communication device, characterized in that: The communication device includes: a processing module and a transceiver module; The transceiver module is used for: receiving first information of a first multicast service from an application server, where the first information is used to indicate a first service area or an application identifier of the first multicast service; sending, according to the first information, a second service area identifier of the first multicast service to the application server; receiving a session creation request message from the application server; The second service area identifier of the first multicast service is notified to the first network device according to the session creation request message.

13. The communication device according to claim 12, wherein: The transceiver module sends the second service area identifier of the first multicast service to the application server according to the first information, including: The processing module determines a second service area identifier of the first multicast service corresponding to the first information; The transceiver module sends a second service area identifier of the first multicast service to the application server.

14. The communication device according to claim 12 or 13, characterized in that: The transceiver module is also used for: The multicast session management network element sends second information of the first multicast service to the application server, where the second information includes at least one of the following: the frequency of the first multicast service, or a temporary multicast group identifier of the first multicast service.

15. The communication device according to claim 12 or 13, characterized in that: The first information is carried in a temporary multicast group identifier allocation request message. The communication device according to claim 15 , wherein: The second service area identifier of the first multicast service is carried in a response message to the temporary multicast group identifier allocation request message.

17. A communication device, characterized in that: The communication device includes a transceiver module; The transceiver module is used for: Sending first information of a first multicast service to a multicast session management network element, where the first information includes a first service area or an application identifier of the first multicast service; receiving a second service area identifier and second information of the first multicast service from the multicast session management network element, where the second information includes at least one of the following: a frequency of the first multicast service, or a temporary multicast group identifier of the first multicast service; The second service area identifier of the first multicast service and the second information are carried in a service announcement message to inform the terminal device.

18. The communication device according to claim 17, wherein: The first information is carried in a temporary multicast group identifier allocation request message.

19. The communication device according to claim 18, wherein: The second service area identifier of the first multicast service is carried in a response message to the temporary multicast group identifier allocation request message.

Images