WO2020063362A1 - 多播/广播业务传输的方法、核心网网元和终端设备 - Google Patents

多播/广播业务传输的方法、核心网网元和终端设备 Download PDF

Info

Publication number
WO2020063362A1
WO2020063362A1 PCT/CN2019/105586 CN2019105586W WO2020063362A1 WO 2020063362 A1 WO2020063362 A1 WO 2020063362A1 CN 2019105586 W CN2019105586 W CN 2019105586W WO 2020063362 A1 WO2020063362 A1 WO 2020063362A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
network element
terminal device
broadcast
core network
Prior art date
Application number
PCT/CN2019/105586
Other languages
English (en)
French (fr)
Inventor
李濛
杨艳梅
应江威
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19867972.2A priority Critical patent/EP3849219A4/en
Priority to PCT/CN2019/105586 priority patent/WO2020063362A1/zh
Publication of WO2020063362A1 publication Critical patent/WO2020063362A1/zh
Priority to US17/215,754 priority patent/US20210219106A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present application relates to the field of communications, and more specifically, to a method for transmitting a multicast / broadcast service, a core network element, and a terminal device.
  • a multi-link transmission mode can be adopted, that is, a plurality of unicast modes are used to implement the point-to-multipoint service transmission.
  • the network side establishes a plurality of transmission links; the sender sends multiple copies of the data; and a shared link transmission method can also be adopted, that is, the network side provides a link shared by multiple receivers, and the sender sends only one Data, the network side copies and transmits the data to multiple recipients.
  • BM-SC broadcast multicast service center
  • AF application function
  • a terminal device may support different or even multiple wireless access technologies (radio access technology (RAT)).
  • RAT radio access technology
  • Multicast broadcast it is not enough for the network side to determine whether to use the multi-link transmission mode or the shared link transmission mode.
  • the network side and the terminal device still do not know the specific RAT based on which to perform point-to-multipoint service transmission. Therefore, the existing transmission scheme decision process for point-to-multipoint service transmission cannot be applied to a scenario where a terminal device supports multicast broadcasting of multiple RATs.
  • the present application provides a method for transmitting multicast / broadcast services, core network elements, and terminal equipment, which can adapt to the case where a terminal device supports multiple RATs in a 5G mobile communication system, and can improve the efficiency of multicast / broadcast transmission.
  • a method for transmitting a multicast / broadcast service includes obtaining, by a first core network element, a network element located in a first service area of the multicast / broadcast service and belonging to the corresponding multicast / broadcast service.
  • the multicast / broadcast access type supported by the terminal device of the group the first core network element determines that the multicast / broadcast service is within the first service area according to the multicast / broadcast access type supported by the terminal device Multicast / broadcast transmission type; the first core network element notifies the access network element corresponding to the multicast / broadcast service to use the multicast / broadcast transmission type to transmit data of the multicast / broadcast service.
  • the first core network element obtains a multicast / broadcast access type supported by the terminal devices of the group corresponding to the multicast / broadcast service, and Broadcast / broadcast access type, determine the multicast / broadcast transmission type of the multicast / broadcast service in the first service area, and notify the access network element, so the first core network element can determine the specific This kind of RAT performs multicast / broadcast transmission, which can better adapt to the situation that the terminal device supports multiple RATs in the 5G mobile communication system, and can improve the efficiency of multicast / broadcast transmission.
  • the first service area is an area in which data of the multicast / broadcast service is transmitted.
  • the specific form of the first service area may be a list of cells or a list of tracking areas.
  • the group corresponding to the multicast / broadcast service indicates a set of terminal devices that accept the multicast / broadcast service.
  • the multicast / broadcast transmission type includes one or more of the following: multicast / broadcast of an NR system, multicast / broadcast single frequency network (MBSFN), or unicast Cell point-to-multipoint (SCPTM) multicast / broadcast.
  • MMSFN multicast / broadcast single frequency network
  • SCPTM unicast Cell point-to-multipoint
  • the access network element corresponding to the multicast / broadcast service may be replaced with the access network element corresponding to the first service area.
  • the access network element corresponding to the multicast / broadcast service is an access network element that receives the data of the multicast / broadcast service from the core network element and sends the data of the multicast / broadcast service to the terminal device.
  • the access network element corresponding to the first service area may refer to an access network element that provides services to terminal devices in the first service area.
  • the first core network element determines that the multicast / broadcast service is in the first service according to a multicast / broadcast access type supported by the terminal device.
  • the type of multicast / broadcast transmission in the area includes: when the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is greater than or equal to a preset value, the first core The network element determines a multicast / broadcast transmission type of the multicast / broadcast service in the first service area according to a multicast / broadcast access type supported by the terminal device.
  • the first core network element may be determined only when the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is greater than or equal to a preset value.
  • the multicast / broadcast transmission type of the broadcast / broadcast service in the first service area that is, when the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is small, a multi-link transmission mode may be adopted; When there are a large number of terminal devices in the group, a shared link transmission mode may be adopted, and the determined multicast / broadcast transmission type is used for multicast / broadcast transmission.
  • the method further includes: the first core network element receives the location information of the terminal device from a second core network element; the first core network And determining the second service area of the multicast / broadcast service according to the location information of the terminal device, where the second service area is located in the first service area; the first core network element sends the The second core network element sends the information of the second service area and the identifier of the multicast / broadcast service.
  • Dynamically updating the scope of the service area in this possible implementation manner can make the service area more adaptable to the number and distribution of terminal devices, and avoid low multicast / broadcasting efficiency caused by the preset service area not matching the actual terminal device distribution. Can improve the efficiency of multicast / broadcast service transmission.
  • the first core network element obtains a terminal located in a first service area of a multicast / broadcast service and belonging to a group corresponding to the multicast / broadcast service.
  • the multicast / broadcast access type supported by the device includes: the first core network element requests a unified data management UDM network element for the multicast / broadcast access type supported by the terminal device; the first core network The element receives a multicast / broadcast access type supported by the terminal device from the UDM network element.
  • the multicast / broadcast access type supported by the terminal device may come from a UDM network element, and the UDM network element may feedback the multicast / broadcast access type supported by one or more terminal devices.
  • the first core network element obtains a terminal located in a first service area of a multicast / broadcast service and belonging to a group corresponding to the multicast / broadcast service.
  • the multicast / broadcast access type supported by the device includes: the first core network element sends a subscription message to the second core network element, the subscription message is used to subscribe to a multicast supported by a terminal device that meets a preset condition / Broadcast access type; the first core network element receives a notification message from the second core network element, the notification message includes a multicast / broadcast access supported by a terminal device that meets the preset condition Types of.
  • the subscription message includes information of the first service area
  • the terminal device meeting a preset condition includes a terminal device located in the first service area.
  • the second core network element when the supported multicast / broadcast access type reported by the terminal device is received, the second core network element does not make a judgment and directly reports the supported multicast / broadcast reported by the terminal device.
  • the access type is sent to the network element of the first core network.
  • the first core network element determines whether the terminal device belongs to a group corresponding to a multicast / broadcast service.
  • the method further includes: obtaining, by the first core network element, the location in the first service area according to a multicast / broadcast access type supported by the terminal device that meets the preset condition, and A multicast / broadcast access type supported by a terminal device belonging to a group corresponding to the multicast / broadcast service.
  • the subscription message includes information of the first service area and an identifier of the multicast / broadcast service
  • the terminal device that satisfies a preset condition includes Terminal devices in the first service area that belong to the group corresponding to the multicast / broadcast service.
  • the network element of the second core network determines whether the terminal device belongs to a group corresponding to a multicast / broadcast service. When the terminal device belongs to the group corresponding to the multicast / broadcast service, the second core network element sends the supported multicast / broadcast access type reported by the terminal device to the first core network element.
  • a method for transmitting a multicast / broadcast service includes: the second core network element receives a subscription message from the first core network element, the subscription message is used to subscribe to meet pre- A multicast / broadcast access type supported by a conditional terminal device; the second core network element receiving a multicast / broadcast access type supported by the first terminal device from a first terminal device, the first The terminal device meets the preset condition; the second core network element sends a notification message to the first core network element, the notification message includes a multicast / broadcast access type supported by the first terminal device .
  • the second core network element receives the first core network element subscribes to a multicast / broadcast access type subscription message supported by a terminal device that satisfies a preset condition.
  • a terminal device receives a multicast / broadcast access type supported by the terminal device, and notifies the first core network network element of the multicast / broadcast access type supported by the first terminal device, thereby providing the first core network element with Information for determining the capabilities of the terminal equipment required for specific RATs for multicast / broadcast transmission, so that the multicast / broadcast transmission can better adapt to the situation where the terminal equipment supports multiple RATs in the 5G mobile communication system, which can improve Efficiency of multicast / broadcast transmission.
  • the subscription message includes information of a first service area of a multicast / broadcast service, and the terminal device that meets a preset condition includes a location device located in the first service area.
  • a terminal device; or the subscription message includes information of a first service area of a multicast / broadcast service and an identifier of the multicast / broadcast service, and the terminal device that satisfies a preset condition includes a location in the first service area And terminal devices belonging to the group corresponding to the multicast / broadcast service.
  • the method further includes: the second core network element receives a first request message from the first terminal device, where the first request message is used for requesting Register with the first terminal device; and the second core network element determines that the first terminal device meets the preset condition according to the first request message.
  • the first request message includes an identifier of the multicast / broadcast service, and the subscription message includes information of the first service area and the multicast / broadcast Service identifier;
  • the second core network element determining that the first terminal device meets the preset condition according to the first request message includes: the second core network element according to the multicast / The identifier of the broadcast service and the first terminal device are located in the first service area, and it is determined that the first terminal device meets the preset condition.
  • the terminal device carries the identifier of the multicast / broadcast service in the first request message, so that the second core network element can determine whether the terminal device meets the preset condition, which can save signaling and processes. .
  • the receiving, by the second core network element, a multicast / broadcast access type supported by the first terminal device from the first terminal device includes: the second The core network element receives a first request message from the first terminal device, where the first request message is used to request registration with the first terminal device, and the first request message includes the first terminal device support Multicast / broadcast access type.
  • the terminal device carries the supported multicast / broadcast access type in the registration request, which can save signaling and processes.
  • the method further includes: sending, by the second core network element, the registration area information of the first terminal device to the first terminal device;
  • the registration area is located in the first business area, or the registration area and the first business area do not intersect.
  • by combining the registration area of the terminal device with the multicast / broadcasting area it can be ensured that the terminal device can promptly notify the network side when it moves out of the multicast / broadcasting area.
  • the terminal device accesses the network, it informs the network side of the joining group information and multicast / broadcast capability through NAS messages, so that the network side can count the number of terminal devices.
  • the information of the registration area of the first terminal device is carried in a response message of the first request message. This possible implementation can save signaling.
  • the method further includes: sending, by the second core network element, the first service area information to the first terminal device.
  • the terminal device by notifying the terminal device of the multicast / broadcasting area (first service area), it can be ensured that the terminal device can promptly notify the network side when it moves out of the multicast / broadcasting area.
  • the terminal device accesses the network, it will inform the network side of the joining group information and multicast / broadcast capability through NAS messages, so that the network side can count the number of terminal devices.
  • the information of the first service area is carried in a response message of the first request message. This possible implementation can save signaling.
  • the method further includes: the second core network element sends the location information of the first terminal device to the first core network element; the first The second core network element receives information of the second service area of the multicast / broadcast service from the first core network element and the identifier of the multicast / broadcast service.
  • the second service area is located at Within the first service area; the second core network element sends information of the second service area and the identifier of the multicast / broadcast service to the first terminal device.
  • a method for transmitting a multicast / broadcast service includes: a terminal device acquiring a multicast / broadcast access type supported by the terminal device; and the terminal device sending an IP address to a second core network element.
  • This section describes the types of multicast broadcast access supported by the terminal device.
  • the terminal device reports to the core network element a multicast / broadcast access type supported by the terminal device, so that the core network element may
  • the access type determines the specific RAT for multicast / broadcast transmission, so that the multicast / broadcast transmission can better adapt to the situation that the terminal device supports multiple RATs in the 5G mobile communication system, and can improve the efficiency of the multicast / broadcast transmission .
  • the multicast broadcast access type supported by the terminal device is carried in a first request message, and the first request message is used to request registration with the terminal device.
  • the method further includes: the terminal device sends a first request message to the second core network element, and the first request message is used to request the End device registration.
  • the first request message includes an identifier of a multicast / broadcast service corresponding to a group to which the terminal device belongs.
  • the method further includes: receiving, by the terminal device, information of a first service area of the multicast / broadcast service from the second core network element; when When the terminal device moves out of the first service area, the terminal device sends a first request message to the second core network element.
  • a method for transmitting a multicast / broadcast service includes: the third core network element receives a second request message from the first core network element, the second request message is used to request the The multicast / broadcast access type supported by the terminal equipment belonging to the group corresponding to the multicast / broadcast service within the first service area of the broadcast / broadcast service; the third core network element sends the first core network element to the first The core network element sends a multicast broadcast access type supported by the terminal device.
  • the second request message includes a list of the terminal devices located in the first service area and belonging to a group corresponding to the multicast / broadcast service.
  • the method further includes: receiving, by the third core network element, a second core network element that is located in the first service area and belongs to the multicast The multicast broadcast access type supported by the terminal device of the group corresponding to the / broadcast service.
  • the present application provides a core network element for performing the method in the first aspect or any possible implementation manner thereof.
  • the core network element may include a module for executing the method in the first aspect or any possible implementation manner thereof.
  • the present application provides a core network element for implementing the method in the second aspect or any possible implementation manner thereof.
  • the core network element may include a module for executing the method in the second aspect or any possible implementation manner thereof.
  • the present application provides a terminal device for performing the method in the third aspect or any possible implementation manner thereof.
  • the core network element may include a module for performing a method in the third aspect or any possible implementation manner thereof.
  • this application provides a core network element that is used to implement the method in the fourth aspect or any possible implementation manner thereof.
  • the core network element may include a module for executing a method in the first aspect or any possible implementation manner thereof.
  • the present application provides a core network element, which includes a processor and a memory, where the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, so that the network device executes the first Method in one aspect or any of its possible implementations.
  • the present application provides a core network element, which includes a processor and a memory, where the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, so that the network device executes the first
  • the method in either aspect or any of its possible implementations.
  • the present application provides a terminal device.
  • the terminal device includes a processor and a memory, where the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, so that the terminal device executes the third aspect or Method in any of its possible implementations.
  • the present application provides a core network element, which includes a processor and a memory, where the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, so that the network device executes Method in the fourth aspect or any of its possible implementations.
  • the present application provides a computer-readable storage medium having instructions stored thereon, and when the instructions are run on a computer, the computer is caused to execute the method of the first aspect and any possible implementation thereof.
  • the present application provides a computer-readable storage medium on which instructions are stored, and when the instructions are run on a computer, the computer is caused to execute the method of the second aspect and any of its possible implementation manners.
  • the present application provides a computer-readable storage medium on which instructions are stored, and when the instructions are run on a computer, the computer is caused to execute the method of the third aspect and any of its possible implementation manners.
  • the present application provides a computer-readable storage medium on which instructions are stored, and when the instructions are run on a computer, the computer is caused to execute the method of the fourth aspect and any of its possible implementation manners.
  • the present application provides a computer program product including instructions, characterized in that when the computer runs the finger of the computer program product, the computer executes the method of the first aspect and any of its possible implementations .
  • the present application provides a computer program product including instructions, characterized in that when the computer runs the finger of the computer program product, the computer executes the method of the second aspect and any of its possible implementation manners .
  • the present application provides a computer program product including instructions, characterized in that when the computer runs the finger of the computer program product, the computer executes the method of the third aspect and any of its possible implementation manners .
  • the present application provides a computer program product including instructions, characterized in that when the computer runs the finger of the computer program product, the computer executes the method of the fourth aspect and any of its possible implementation manners .
  • the present application provides a computer chip that enables a computer to execute the method of the first aspect and any of its possible implementation manners.
  • the present application provides a computer chip that enables a computer to execute the method of the second aspect and any of its possible implementation manners.
  • the present application provides a computer chip that enables a computer to execute the method in the third aspect and any of its possible implementation manners.
  • the present application provides a computer chip that causes a computer to execute the method in the fourth aspect and any of its possible implementation manners.
  • FIG. 1 is a schematic diagram of a wireless communication system according to the present application.
  • FIG. 2 is a schematic diagram of a point-to-multipoint service transmission scenario to which the method of the embodiment of the present application is applied.
  • FIG. 3 is a schematic diagram of a point-to-multipoint service transmission scenario using a multi-link transmission mode.
  • FIG. 4 is a schematic diagram of a point-to-multipoint service transmission scenario using a shared link transmission mode.
  • FIG. 5 is a schematic diagram of a system architecture of a 5G mobile communication system.
  • Figure 6 is a schematic diagram of the MBMS system architecture.
  • FIG. 7 is a schematic diagram of a system architecture of a 5G mobile communication system incorporating MBMS according to an embodiment of the present application.
  • FIG. 8 is a flowchart of a method for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • FIG. 9 is a flowchart of another method for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of an MBMS transmission process.
  • FIG. 11 is a flowchart of another method for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • FIG. 12 is a flowchart of another method for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • FIG. 13 is a flowchart of another method for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • FIG. 14 is a flowchart of another method for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • FIG. 15 is a flowchart of another method for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of a core network element provided by an embodiment of the present application.
  • FIG. 17 is a schematic block diagram of another core network element provided by an embodiment of the present application.
  • FIG. 18 is a schematic block diagram of another core network element provided by an embodiment of the present application.
  • FIG. 19 is a schematic block diagram of another core network element provided by an embodiment of the present application.
  • FIG. 20 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 21 is a schematic block diagram of another terminal device according to an embodiment of the present application.
  • FIG. 22 is a schematic block diagram of another core network element provided by an embodiment of the present application.
  • FIG. 23 is a schematic block diagram of another core network element provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a wireless communication system 100 according to the present application.
  • the wireless communication system 100 can work in a high-frequency band, and is not limited to a long term evolution (LTE) system, but also a 5G system system, a machine to machine (M2M) system, or an evolved in the future. Communication systems, etc.
  • the wireless communication system 100 may include one or more access network devices 110, one or more terminal devices 120, and a core network (CN) 130. among them:
  • the access network device 110 belongs to a (radio) access network ((R) AN).
  • the access network device 110 may be a base station, and the base station may be used to communicate with one or more terminal devices, and may also be used to communicate with one or more base stations with partial terminal device functions (for example, macro base stations and micro base stations). Communication, communication between access points).
  • the base station may be an evolved base station (eNB) in an LTE system, or a base station in a 5G system.
  • the base station may also be an access point (AP), a transport node (TRP), a central unit (CU), or other network entities, and may include part or Full functionality without restrictions.
  • AP access point
  • TRP transport node
  • CU central unit
  • the terminal devices 120 may be distributed throughout the wireless communication system 100, and may be stationary or mobile.
  • the terminal device 120 may be a mobile device, a mobile station, a mobile unit, an M2M terminal, a wireless unit, a remote unit, a user agent, a mobile client, or a user equipment (UE).
  • UE user equipment
  • the access network device 110 may be configured to communicate with the terminal device 120 through one or more antennas.
  • the access network device 110 may transmit control information or user data to the core network 130 through a backhaul interface 150 (for example, an S1 interface).
  • the access network device 110 and the access network device 110 may also communicate with each other directly or indirectly through a backhaul interface 140 (such as an Xn interface).
  • the core network 130 is composed of a series of physical network elements. These network elements communicate with each other through standardized interfaces or service calls.
  • the core network is responsible for, for example, user access and mobility management, session management, policy control, data packet forwarding, and tunnel management. And address management.
  • the core network may include a mobility management entity (MME), a serving gateway (S-GW), a packet data gateway (packet data network gateway, PDN gateway, and P-GW) and home users. Server (home subscriber, server, HSS) and other network elements.
  • the core network may include access and mobility management (AMF) network elements, session management (SMF) network elements, and user plane function (UPF). Network element, unified data management (UDM) network element, and policy control function (PCF) network element.
  • MME mobility management entity
  • S-GW serving gateway
  • PDN gateway packet data gateway
  • P-GW packet data gateway
  • Server home subscriber, server, HSS
  • the core network may include access and mobility management (AMF) network elements,
  • the wireless communication system shown in FIG. 1 is only for more clearly illustrating the technical solution of the present application, and does not constitute a limitation on the present application.
  • Those skilled in the art may know that with the evolution of the network architecture and the emergence of new service scenarios, The technical solutions provided in the application examples are also applicable to similar technical problems.
  • FIG. 2 is a schematic diagram of a point-to-multipoint service transmission scenario 200.
  • the sender 210 sends data to multiple terminal devices.
  • FIG. 2 schematically illustrates three terminal devices: a terminal device 221, a terminal device 222, and a terminal device 223.
  • FIG. 3 is a schematic diagram of a point-to-multipoint service transmission scenario 300 using a multi-link transmission mode.
  • the sender 310 in the point-to-multipoint service transmission, the sender 310 establishes a plurality of transmission links and sends data to multiple terminal devices.
  • FIG. 3 schematically illustrates three terminal devices: a terminal device 321, a terminal device 322, and a terminal device 323; and three corresponding links: a link 331, a link 332, and a link 333.
  • FIG. 4 is a schematic diagram of a point-to-multipoint service transmission scenario 400 using a shared link transmission mode.
  • the sender 410 in the point-to-multipoint service transmission, establishes a link 430 shared by multiple terminal devices, and sends data to the multiple terminal devices.
  • three terminal devices are schematically shown in FIG. 4: a terminal device 421, a terminal device 422, and a terminal device 423.
  • the sender in FIG. 2 to FIG. 4 may be a user plane function network element in an access network device or a core network.
  • FIG. 5 is a schematic diagram of a system architecture of a 5G mobile communication system. The functions of the network elements are described in detail below.
  • Network open function (NEF) network element It is the network element of the operator's network that is used to open the data in the network to a third-party application server or receive data provided by the third-party application server for the network.
  • Network storage function (NRF) network element used to realize the storage of data in the network.
  • Unified data management (UDM) network element It is used to perform unified data management on the data in the network. Its main functions are management of various user contract data, user authentication data management, user identification management, and so on.
  • AUSF Authentication service function
  • Session management function (SMF) network element The main functions include session management, network protocol (IP) address allocation and management of terminal equipment, selection and management of user plane functions, and downlink data notification.
  • IP network protocol
  • Access and mobility management (AMF) network element The main functions include mobility management, legal monitoring, and access authorization / authentication.
  • User plane function (UPF) network element mainly provides user plane service processing functions, including service routing, packet forwarding, anchoring functions, quality of service (QoS) processing of user plane data, uplink
  • QoS quality of service
  • the identification of the path identifies and routes to the data network, the downlink packet buffer, the notification trigger of the downlink data arrival, and the connection to the external data network.
  • (R) AN Provides network resources for access of terminal equipment, which can be base stations in the LTE system or 5G system; is responsible for radio resource management, uplink and downlink data classification and QoS applications, and completes signaling processing with control plane network elements Complete data forwarding and other functions with user plane network elements. It is worth noting that, in the LTE system, this network element may be called an eNodeB or an eNB. In a 5G system, (R) AN can also be called the next generation radio access network (NG-RAN).
  • the NG-RAN may include a next generation eNodeB / eNB (ng-eNB) and / or a gNB.
  • the Ng-eNB can support the interface of the 5G core network (that is, it can be connected to the 5G core network), and its air interface technology is based on the LTE technology.
  • PCF Policy control function
  • PCF policy and charging rule function
  • DN Data network
  • a network used to transmit data such as the Internet.
  • NF network function
  • FIG. 6 is a schematic diagram of a system architecture of a multimedia broadcast multicast service (MBMS).
  • the content provider may be a network element or a device on the network side.
  • the MBMS receiver (MBMS receiver) may be a terminal device.
  • the content provider sends data to the BM-SC network element through the IP network, and then the BM-SC network element sends the data to the MBMS receiver via the MBMS gateway (MBMS gateway) of the core network and the radio access network.
  • the radio access network may be an evolved universal terrestrial radio access network (E-UTRAN) and / or a universal terrestrial radio access network (UTRAN).
  • E-UTRAN evolved universal terrestrial radio access network
  • UTRAN universal terrestrial radio access network
  • FIG. 7 is a schematic diagram of a system architecture of a 5G mobile communication system incorporating MBMS according to an embodiment of the present application.
  • the SMF network element in FIG. 7 may implement the session management function of the BM-SC network element in the MBMS system architecture in FIG. 6, that is, the SMF network element in FIG. 7 may implement a multicast broadcast transmission session Management function, that is, the SMF is enhanced as a network element that can support a group-session management function (G-SMF).
  • the SMF network element in FIG. 7 can also implement the control plane function (CPF) of the system architecture of the BM-SC and MBMS.
  • the CPF mainly includes session management functions such as establishment, release, and modification of a user plane transmission path of a multicast / broadcast service of a terminal device (for example, functions of an SMF network element).
  • the SMF network element in FIG. 7 may implement the service management functions of the BM-SC network element in the MBMS system architecture in FIG. 6, that is, the group management, security management, and service announcement functions.
  • these service management functions can be implemented in a separate MBMS service control network element.
  • the MBMS service control network element is a new network function entity defined in the 5G system, and includes a BM-SC network element. Business management functions.
  • the AMF network element in FIG. 7 can implement the function of transferring session information between the SMF network element and the RAN. It should be understood that the AMF network element herein may also be a group-access and mobility management function (G-AMF) network element.
  • G-AMF group-access and mobility management function
  • the UPF network element in FIG. 7 can implement the user plane function of multicast broadcast transmission, that is, the user plane function of the BM-SC network element and MBMS-GW in the MBMS system architecture in FIG. 6.
  • the network element of the first core network may be an SMF network element or a G-SMF network element having an MBMS function, and may also be an MBMS service control network element.
  • the second core network element may be an AMF network element or a G-AMF network element.
  • the third core network element may be a UDM network element.
  • the first core network element is an SMF network element
  • the second core network element is an AMF network element
  • the third core network element is a UDM network element. It should be understood that the present application may also be based on other architectures than the system architecture shown in FIG. 7, and each core network element may be another network element having a similar function to the foregoing network element, which is not limited in this application.
  • FIG. 8 is a flowchart of a method 800 for transmitting a multicast / broadcast service according to an embodiment of the present application, as described below.
  • the first core network element obtains a multicast / broadcast access type supported by terminal devices located in a first service area of the multicast / broadcast service and belonging to a group corresponding to the multicast / broadcast service.
  • the first service area is a service area (SA) corresponding to the multicast / broadcast service discussed in the embodiments of the present application.
  • SA service area
  • the first service area is an area in which data of the multicast / broadcast service is transmitted.
  • a multicast / broadcast service can correspond to a service area.
  • the specific form of the first service area may be a list of cells or a list of tracking areas.
  • the group corresponding to the multicast / broadcast service indicates a set of terminal devices that accept the multicast / broadcast service.
  • a multicast / broadcast service can correspond to a group, and the group can include one or more terminal devices.
  • the service area may also be referred to as a group conversation area.
  • the business area is a geographical area.
  • a group is a logical concept.
  • a terminal device belonging to a group corresponding to a multicast / broadcast service is a terminal device that receives the service of the multicast / broadcast service.
  • the multicast / broadcast transmission type includes one or more of the following: multicast / broadcast of an NR system, multicast / broadcast single frequency network (MBSFN), or unicast Cell point-to-multipoint (SCPTM) multicast / broadcast.
  • the multicast / broadcast transmission type may also include multicast / broadcast of other types of systems or other types of networks, which is not limited in this application.
  • the type of multicast / broadcast access supported by the terminal device may be considered as the capability of the terminal device, and may be referred to as the multicast / broadcast access capability of the terminal device.
  • the multicast / broadcast access type supported by the terminal device may include one or more of the following: multicast / broadcast of NR system, multicast / broadcast of MBSFN, or multicast / broadcast of SCPTM.
  • the first core network element determines a multicast / broadcast transmission type of the multicast / broadcast service in the first service area according to a multicast / broadcast access type supported by the terminal device.
  • the first core network element notifies the access network element corresponding to the multicast / broadcast service to use the multicast / broadcast transmission type to transmit data of the multicast / broadcast service.
  • the access network element corresponding to the multicast / broadcast service may be replaced with the access network element corresponding to the first service area.
  • the access network element corresponding to the multicast / broadcast service is an access network element that receives the data of the multicast / broadcast service from the core network element and sends the data of the multicast / broadcast service to the terminal device.
  • the access network element corresponding to the first service area may refer to an access network element that provides services to terminal devices in the first service area.
  • the access network element may be located in the first service area or may not be located in the first service area, which is not limited in this application.
  • the first core network element may send the multicast / broadcast transmission type and the identifier of the multicast / broadcast service to the access network element corresponding to the multicast / broadcast service to notify the access
  • the multicast / broadcast transmission type determined by the incoming network element is applicable to which multicast / broadcast service or which group.
  • step S830 may also be replaced by the first core network element sending the multicast / broadcast transmission type and the identifier of the multicast / broadcast service to the access network element corresponding to the multicast / broadcast service.
  • the identification of the multicast / broadcast service can be used to identify and distinguish between different multicast / broadcast services, and can also be used to identify the group corresponding to the multicast / broadcast service.
  • multicast / broadcast identification is used to identify and distinguish between multicast / broadcast services and groups corresponding to multicast / broadcast services; in other existing systems or networks, groups are used
  • the group identifier is used to identify and distinguish the multicast / broadcast service and the group corresponding to the multicast / broadcast service.
  • the identifier of the multicast / broadcast service may be a multicast / broadcast identifier or a group identifier.
  • the multicast / broadcast identifier indicates a transmission service of a multicast / broadcast service indicated by the multicast / broadcast identifier subscribed by the terminal device.
  • the group identifier indicates that the terminal device belongs to a group corresponding to the multicast / broadcast service.
  • the first core network element obtains a multicast / broadcast access type supported by the terminal devices of the group corresponding to the multicast / broadcast service, and Broadcast / broadcast access type, determine the multicast / broadcast transmission type of the multicast / broadcast service in the first service area, and notify the access network element, so the first core network element can determine the specific This kind of RAT performs multicast / broadcast transmission, which can better adapt to the situation that the terminal device supports multiple RATs in the 5G mobile communication system, and can improve the efficiency of multicast / broadcast transmission.
  • step S820 may include: when the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is greater than or equal to a preset value
  • the first core network element determines the multicast / broadcast transmission type of the multicast / broadcast service in the first service area according to the multicast / broadcast access type supported by the terminal device.
  • the network element of the first core network may determine a transmission mode for point-to-multipoint service transmission, for example, determine whether to use a multi-link transmission mode or a shared link transmission mode.
  • the first core network element may determine the relationship between the number of terminal devices in the group corresponding to the multicast / broadcast service and the preset value in the first service area.
  • the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is less than (or less than or equal to) a preset value, it is determined to adopt a multi-link transmission mode (that is, a plurality of unicast transmissions) Mode) to perform multicast / broadcast service transmission.
  • the first core network element When the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is greater than or equal to (or greater than) a preset value, the first core network element according to the multicast supported by the terminal device / Broadcast access type, determining the multicast / broadcast transmission type of the multicast / broadcast service in the first service area.
  • the first core network element selects a multicast / broadcast access type with a maximum number of terminal devices as the multicast / broadcast transmission type of the multicast / broadcast service in the first service area. . For example, if the terminal devices located in the first service area of the multicast / broadcast service and belonging to the group corresponding to the multicast / broadcast service support the most MBSFN multicast / broadcast terminal devices, the MBSFN multicast / Broadcast is the multicast / broadcast transmission type of the multicast / broadcast service in the first service area.
  • a certain multicast / broadcast transmission type is used for multicast / broadcast service transmission, and the part of the terminal equipment supports multicast / broadcast corresponding to the type of multicast / broadcast transmission.
  • Access type for another part of the terminal equipment, another multicast / broadcast transmission type is used for multicast / broadcast service transmission, and the other part of the terminal equipment supports multicast / broadcast corresponding to the other multicast / broadcast transmission type Broadcast access type.
  • some of the terminal devices support multicast / broadcast of the NR system.
  • the NR system uses the multicast / broadcast transmission type for multicast / broadcast service transmission; another part of the terminal equipment supports SCPTM's multicast / broadcast, then the other part of the terminal equipment uses SCPTM's multicast / broadcast transmission type for multicast / Broadcast service transmission.
  • some terminal devices may support multiple multicast / broadcast access types.
  • the first core network element may select a suitable multiple for these terminal devices based on the capabilities of the terminal devices and the total number of terminal devices.
  • the method 800 may further include: the first core network element receives the location information of the terminal device from the second core network element; the first core network element according to the The location information of the terminal device determines a second service area of the multicast / broadcast service, the second service area is located in the first service area; the first core network element sends the second core network element to the second core network element Information about the service area and the identity of the multicast / broadcast service.
  • the information of the first service area and the information of the second service area may specifically be a list of cell identifiers or a list of tracking area identifiers.
  • the process of the first core network element determining the second service area to replace the original first service area can be understood as the first core network element dynamically updating the range of the service area.
  • the network element of the first core network may be determined by the number and distribution of terminal devices subscribing to the same multicast broadcast service. In one example, the number and distribution of terminal devices can be determined by counting the location information of each terminal device.
  • the location information of the terminal device may be sent by the second core network element to the first core network element.
  • the network element of the first core network may obtain the location information of the terminal device through reporting by the terminal device.
  • the network element of the first core network may also obtain the location information of the terminal device through other methods, which is not limited in this application.
  • the location information of the terminal device may be a cell identifier of a cell where the terminal device is located. Of course, the location information of the terminal device may also be other forms of information, which is not limited in this application.
  • the scope of the dynamically updated service area may include determining a second service area of the multicast / broadcast service, where the second service area is located within the first service area. That is, the scope of the dynamically updated service area may be a reduction of the scope of an existing service area, and the reduction of the first service area to a second service area. In addition, the scope of dynamically updating the service area may also be to expand the scope of the existing service area, or select a new service area from the candidate set to apply the multicast / broadcast service, which is not limited in this application.
  • the first core network element may notify the corresponding core network element and / or the access network element, such as the UPF and RAN, so as to facilitate the core network element and / or the access network Yuan updates the scope of the business area.
  • the first core network element may send information about the second service area and the identifier of the multicast / broadcast service to the second core network element.
  • the second core network element receives the information of the second service area of the multicast / broadcast service from the first core network element and the identifier of the multicast / broadcast service.
  • the identification of the multicast / broadcast service is sent to indicate to which multicast / broadcast service or group the determined information of the second service area is applicable.
  • the second core network element may send the information of the second service area and the identification of the multicast / broadcast service to the terminal device. That is, the network element of the second core network can inform the terminal device of the latest service area information, and this process can be implemented by a service announcement process, which is not described herein again.
  • Dynamically updating the scope of the business area can make the business area more adaptable to the number and distribution of terminal devices, avoid the inefficient multicast / broadcast caused by the preset business area not matching the actual terminal device distribution, and improve multicast / broadcast Efficiency of business transmission.
  • step of dynamically updating the scope of the service area may not be based on steps S810 to S830, but may be an independent method of dynamically updating the scope of the service area.
  • step S810 may include: the first core network element requests a UDM network element (which may be the third core network element described above) for multiple supported by the terminal device Broadcast / broadcast access type; the first core network element receives a multicast / broadcast access type supported by the terminal device from the UDM network element.
  • a UDM network element which may be the third core network element described above
  • the third core network element receives the request from the first core network element.
  • the third core network element may be a second request message, and the second request message is used for requesting to be located in the first service area of the multicast / broadcast service.
  • the multicast / broadcast access type supported by the terminal device belonging to the group corresponding to the multicast / broadcast service the third core network element sends the multicast broadcast supported by the terminal device to the first core network element Access type. That is, the multicast / broadcast access type supported by the terminal device can come from a UDM network element.
  • the second request message may include a list of the terminal devices located in the first service area and belonging to the group corresponding to the multicast / broadcast service. It should be understood that the second request message may also request the multicast / broadcast access type supported by the terminal device through other content. For example, the second request message is only used to request the multicast / broadcast access type supported by the terminal device, and does not send a list of the terminal device.
  • the third core network element may send all the multicast / broadcast access type related information of all the terminal devices it finds to the first core network element. The first core network element determines which multicast / broadcast access types supported by the terminal equipment to determine the multicast / broadcast transmission type of the multicast / broadcast service in the first service area. This application does not limit the specific form of the second request message.
  • step S810 may include: the first core network element sends a subscription message to the second core network element, and the subscription message is used to subscribe to a message that meets a preset condition.
  • Multicast / broadcast access type supported by a terminal device the first core network element receives a notification message from the second core network element, the notification message includes a multicast / broadcast supported by a terminal device that meets the preset condition Access type.
  • the second core network element receives a subscription message from the first core network element, and the second core network element sends a notification message to the first core network element. That is, the multicast / broadcast access type supported by the terminal device may come from a second core network element, such as an AMF network element.
  • the subscription message includes information of the first service area and an identifier of the multicast / broadcast service
  • the terminal device that satisfies a preset condition includes the terminal device located in the first service area and belonging to the The terminal equipment of the group corresponding to the broadcast / broadcast service.
  • the first core network element sends an identification of the multicast / broadcast service to the second core network element. In this way, through identification of the multicast / broadcast service, the network element of the second core network can distinguish which multicast / broadcast service is, or determine the group corresponding to the multicast / broadcast service.
  • the second core network element When the second core network element receives the supported multicast / broadcast access type reported by the terminal device, the second core network element determines whether the terminal device belongs to a group corresponding to the multicast / broadcast service. When the terminal device belongs to the group corresponding to the multicast / broadcast service, the second core network element sends the supported multicast / broadcast access type reported by the terminal device to the first core network element.
  • the subscription message includes information of the first service area
  • the terminal device that meets a preset condition includes a terminal device located in the first service area.
  • the first core network element does not send the identification of the multicast / broadcast service to the second core network element.
  • the second core network element When receiving the supported multicast / broadcast access type reported by the terminal device, the second core network element does not make a judgment and directly sends the supported multicast / broadcast access type reported by the terminal device to the first core.
  • Network element The first core network element determines whether the terminal device belongs to a group corresponding to a multicast / broadcast service.
  • the method 800 may further include: the first core network element According to the multicast / broadcast access type supported by the terminal device that satisfies the preset condition, obtaining the multicast / broadcast supported by the terminal device located in the first service area and belonging to the group corresponding to the multicast / broadcast service Broadcast access type.
  • FIG. 9 is a flowchart of another method 900 for transmitting a multicast / broadcast service according to an embodiment of the present application, which is as follows.
  • the second core network element receives a subscription message from the first core network element, and the subscription message is used to subscribe to a multicast / broadcast access type supported by a terminal device that meets a preset condition.
  • the second core network element receives a multicast / broadcast access type supported by the first terminal device from the first terminal device, and the first terminal device meets the preset condition.
  • related information of the multicast / broadcast access type supported by the terminal device of the network element of the second core network may come from the terminal device.
  • the first terminal device acquires the multicast / broadcast access type supported by the first terminal device, and sends the multicast broadcast access type supported by the first terminal device to the second core network element.
  • the first terminal device may obtain the multicast / broadcast access type supported by the first terminal device from the memory.
  • the second core network element sends a notification message to the first core network element, where the notification message includes a multicast / broadcast access type supported by the first terminal device.
  • a second core network element receives a subscription message of a multicast / broadcast access type supported by a terminal device that meets a preset condition from the first core network element, and A terminal device receives a multicast / broadcast access type supported by the terminal device, and notifies the first core network network element of the multicast / broadcast access type supported by the first terminal device, thereby providing the first core network element with Information for determining the capabilities of the terminal equipment required for specific RATs for multicast / broadcast transmission, so that the multicast / broadcast transmission can better adapt to the situation where the terminal equipment supports multiple RATs in the 5G mobile communication system, which can improve Efficiency of multicast / broadcast transmission.
  • the subscription message includes information about a first service area of a multicast / broadcast service, and the terminal device that meets a preset condition includes a terminal located in the first service area
  • the subscription message includes information of the first service area of the multicast / broadcast service and the identifier of the multicast / broadcast service
  • the terminal device that satisfies a preset condition includes the terminal device located in the first service area and belonging to the The terminal equipment of the group corresponding to the broadcast / broadcast service.
  • the subscription message in this implementation scenario is similar to the detailed description of the subscription message in the method 800, and is not repeated here.
  • the method 900 may further include: the second core network element receiving a first request message from the first terminal device, where the first request message is used for requesting Register the first terminal device; the second core network element determines that the first terminal device meets the preset condition according to the first request message.
  • the first terminal device sends a first request message to the second core network element.
  • the first request message may include an identifier of the multicast / broadcast service, and the subscription message includes information of the first service area and an identifier of the multicast / broadcast service; the second core network element is based on
  • the first request message which determines that the first terminal device meets the preset condition, may include: the second core network element is located in the first service area according to the identifier of the multicast / broadcast service and the first terminal device To determine that the first terminal device meets the preset condition.
  • the second core network element determines that the first terminal device belongs to a group corresponding to the multicast / broadcast service according to the identifier of the multicast / broadcast service in the first request message. In other words, the network element of the second core network determines that the first terminal device is subscribed to the multicast / broadcast service according to the identifier of the multicast / broadcast service in the first request message.
  • the first terminal device may carry the position of the first terminal device in the first request message, so that the second core network element can determine that the first terminal device is located in the first service area.
  • the first terminal device may also send the first request message to the second core network element when it is determined that it is located in the first service area.
  • the access network element sends the location information of the first terminal device to the second core network element together with the first request message.
  • the second core network element receiving the multicast / broadcast access type supported by the first terminal device from the first terminal device may include: the first The second core network element receives a first request message from the first terminal device, where the first request message is used to request registration to the first terminal device, and the first request message includes a multicast / Broadcast access type.
  • the multicast / broadcast access type supported by the first terminal device may be carried in the first request message, which can save signaling and Resources. That is, the first terminal device may report the supported multicast / broadcast access type to the network side through an existing non-access stratum (NAS) process to achieve the purpose of saving signaling and resources.
  • NAS non-access stratum
  • the first terminal device may not report the supported multicast / broadcast access type through the first request message, but adopt other signaling, which is not limited in this application.
  • Existing terminal equipment can be in a connected state and an idle state.
  • a multi-link transmission mode ie, a unicast transmission mode
  • data can be received / sent only when the terminal device is in a connected state.
  • a terminal device When a terminal device is in an idle state, its related communication module is in a closed state, so the power consumption of the terminal device is in a relatively low situation.
  • the terminal device wants to send data to the network side, or the network side wants to send unicast data to the terminal device, the terminal device must first enter the connected state.
  • a terminal device For a terminal device, if it is in an idle state, it means that when the terminal device changes the residential cell, the network side cannot know the change of the terminal device position in time. In this way, when the network side needs to send data to the terminal device in the idle state, the network side cannot page the terminal device.
  • the existing system proposes the concept of a registration area (RA).
  • RA registration area
  • the network side When the network side needs to send downlink data to an idle terminal device, the network side only needs to send a paging message to the registration area.
  • the terminal device moves out of the current registration area, the terminal device needs to send a registration request message of the mobile type to the network side, and the network side will allocate a new registration area to the terminal device.
  • the first request message in the foregoing is the registration request message.
  • FIG. 10 is a flowchart of the MBMS transmission process 1000, as follows.
  • An associated transmission function (ADF) network element sends a transmission request to an MBMS delivery function (MBMS delivery function) network element.
  • ADF transmission function
  • gateway GPRS support node gateway GPRS support node (GGSN) start session 1-n).
  • S1041-S104n, the MBMS transmission function network element and the GGSN respectively end session 1-n (session stop 1-n).
  • the terminal device initiates ADP.
  • This process can be used for a terminal device to report to the MBMS service control network element that the terminal device uses a multicast / broadcast service, which is convenient for the BM-SC network element to perform statistics on whether it is necessary to switch between a multilink transmission mode and a shared link transmission mode.
  • the BM-SC network element can adjust the transmission mode based on a pre-configured preset value.
  • ADP is that after the terminal device receives the data of the multicast / broadcast service, it sends a message to the BM-SC network element (or AF network element) to inform it that it has received the data of the multicast / broadcast service.
  • the BM-SC network element or AF network element
  • the BM-SC network element can count the number of receiving terminal devices, and then determine the transmission scheme used (that is, whether the multi-link transmission mode or the shared link transmission mode is used).
  • the terminal device can still receive multicast / broadcast data when it is idle, but when the terminal device initiates ADP (that is, when sending data to the network side), it is required that the terminal device first enter the connection state, and the network side needs to be a terminal device. Establish additional transmission resources, which will waste the power of terminal equipment and resources on the network side.
  • ADP that is, when sending data to the network side
  • ADP only reports after the terminal device receives the data of the multicast / broadcast service, so that the data collected by the network side is later (the BM-SC statistics will be triggered after the data of the multicast / broadcast service is sent, and then the transmission is switched. the way).
  • the method 900 may further include: the second core network element receives a first request message from the first terminal device, where the first request message includes a multicast / An identifier of a broadcast service, the first request message is used to request registration with a first terminal device; the second core network element sends information about a registration area of the first terminal device to the first terminal device; and the registration area Located in the first business area, or the registration area and the first business area do not intersect.
  • This implementation scenario enables the network element of the second core network to obtain the first service area correspondingly according to the identifier of the multicast / broadcast service.
  • the second core network element sets a registration area for the first terminal device, it considers the first service area, that is, the range in which the multicast / broadcast service is sent.
  • the registration area is located within the first business area, or there is no intersection between the registration area and the first business area. In this way, when the first terminal device moves out of the first service area, the second core network element can be notified in time.
  • the second core network element can use the existing registration request process to simultaneously count the terminal devices in the first service area. To facilitate the network element of the second core network to determine the transmission scheme to be used.
  • the transmission scheme used is determined after the terminal device receives the data of the multicast / broadcast service.
  • the terminal device can report the change in location in time, making the first
  • the transmission scheme adopted by the two core network network elements is switched in time.
  • this process is incorporated into the registration request process, which can save the power of the terminal equipment and the resources on the network side.
  • the information of the registration area of the first terminal device may be carried in a response message of the first request message.
  • the information of the registration area can also be carried in other signaling, which is not limited in this application.
  • the method 900 may further include: the second core network element sending the first service area information to the first terminal device. Accordingly, the first terminal device receives the information of the first service area of the multicast / broadcast service from the network element of the second core network.
  • the network element of the second core network sends the information of the first service area to the first terminal device.
  • the information of the first service area includes a range sent by the multicast / broadcast service.
  • the first terminal device may send a first request message to the second core network element.
  • the first terminal device notifies the second core network element through the first request message.
  • the second core network element can use the existing registration request process to simultaneously count the number of terminal devices in the first service area, so as to facilitate the second
  • the core network element determines the transmission scheme to be used. Compared with ADP, the transmission scheme used is determined after the terminal device receives the data of the multicast / broadcast service.
  • the terminal device can report the change of location in time, making the first The transmission scheme adopted by the two core network network elements is switched in time. At the same time, this process is incorporated into the registration request process, which can save the power of the terminal equipment and the resources on the network side.
  • the information of the first service area is carried in a response message of the first request message to save signaling overhead.
  • the information of the first service area may also be carried in other signaling, or the information of the first service area may be sent separately, which is not limited in this application.
  • the method 900 may further include: the second core network element sending the location information of the first terminal device to the first core network element; the first The second core network element receives information of the second service area of the multicast / broadcast service from the first core network element and the identifier of the multicast / broadcast service.
  • the second service area is located in the first service area.
  • the second core network element sends the information of the second service area and the identifier of the multicast / broadcast service to the first terminal device.
  • operations performed by the second core network element in the process of dynamically updating the range of the service area and operations of the second core network element in the detailed description of the process of dynamically updating the range of the service area in method 800 Correspondence is not repeated here.
  • FIG. 11 is a flowchart of another method 1100 for transmitting a multicast / broadcast service according to an embodiment of the present application, which is as follows.
  • the terminal device obtains a multicast / broadcast access type supported by the terminal device.
  • the multicast / broadcast access type supported by the terminal device can be obtained from the memory.
  • S1120 The terminal device sends a multicast broadcast access type supported by the terminal device to the second core network element.
  • a terminal device reports a multicast / broadcast access type supported by the terminal device to a core network element, so that the core network element may perform multicast / broadcast support based on the terminal device.
  • the access type determines the specific RAT for multicast / broadcast transmission, so that the multicast / broadcast transmission can better adapt to the situation that the terminal device supports multiple RATs in the 5G mobile communication system, and can improve the efficiency of the multicast / broadcast transmission.
  • the multicast broadcast access type supported by the terminal device may be carried in a first request message, where the first request message is used to request registration with the terminal device.
  • the method 1100 may further include: the terminal device sends a first request message to the second core network element, where the first request message is used to request the End device registration.
  • the first request message may include an identifier of a multicast / broadcast service corresponding to a group to which the terminal device belongs.
  • the method 1100 may further include: the terminal device receiving information of the first service area of the multicast / broadcast service from the second core network element; When the terminal device moves out of the first service area, the terminal device sends a first request message to the second core network element.
  • operations performed by the terminal device correspond to operations performed by the terminal device in the method 900, and details are not described herein again.
  • FIG. 12 is a flowchart of another method 1200 for transmitting a multicast / broadcast service according to an embodiment of the present application, which is as follows.
  • the third core network element receives a second request message from the first core network element.
  • the second request message is used to request that the second request message is located in the first service area of the multicast / broadcast service and belongs to the multicast / broadcast.
  • the third core network element sends a multicast broadcast access type supported by the terminal device to the first core network element.
  • a third core network element receives a second request message of a multicast / broadcast access type supported by the first core network element from the terminal device, and sends the second request message to the first core network.
  • the network element generates a multicast / broadcast access type supported by the terminal device, thereby providing the first core network network element with information for determining the capabilities of the terminal device required for specific RATs for multicast / broadcast transmission, so that Multicast / broadcast transmission can better adapt to the situation that terminal equipment supports multiple RATs in a 5G mobile communication system, and can improve the efficiency of multicast / broadcast transmission.
  • the second request message may include a list of the terminal devices located in the first service area and belonging to a group corresponding to the multicast / broadcast service.
  • the method 1200 may further include: receiving, by the third core network element, a second core network element from the second core network element that is located in the first service area and belongs to the multi-node network.
  • the method 1200 may further include: the third core network element receiving the second core network element from the second core network element located in the first service area and belonging to the multi-node The multicast broadcast access type supported by the terminal device in the group corresponding to the broadcast / broadcast service. That is, the related information about the multicast broadcast access type supported by the terminal device in the third core network element may be from the second core network element.
  • the network element of the third core network may obtain the multicast broadcast access type supported by the terminal device through other methods or from other devices, which is not limited in this application.
  • FIG. 13 is a flowchart of another method 1300 for transmitting a multicast / broadcast service according to an embodiment of the present application.
  • the method 1300 is applicable to the following scenarios: the AF network element already knows the list of terminal equipment subscribing to the multicast / broadcast service, and it is known that it needs to provide the first service area (the first service area does not change with the location of the terminal device) send data.
  • the first core network element for example, the SMF network element
  • the method 1300 is implemented by participating in a third core network element (for example, a UDM network element).
  • the method 1300 for multicast / broadcast service transmission may include the following steps.
  • the AF network element sends a multicast / broadcast service request message to the SMF network element.
  • the multicast / broadcast service request message includes a first service area where the multicast / broadcast service functions and a list of terminal devices receiving the multicast / broadcast service.
  • S1320 The SMF network element sends a second request message to the UDM network element.
  • the UDM network element receives the second request message sent by the SMF network element.
  • the second request message may include a list of terminal devices located in the first service area and belonging to the group corresponding to the multicast / broadcast service.
  • Step S1320 may correspond to step S1210 in the method 1200 of the foregoing embodiment.
  • the UDM network element sends a list of multicast / broadcast access types supported by the terminal device to the SMF network element.
  • the SMF network element receives a list of multicast / broadcast access types supported by the terminal device sent by the UDM network element.
  • Step S1330 may correspond to step S810 in method 800 of the foregoing embodiment and step S1220 in method 1200 of the foregoing embodiment.
  • the UDM network element can search the local subscription data to find the list of multicast / broadcast access types supported by the terminal device corresponding to the list of terminal devices.
  • the SMF network element determines a multicast / broadcast transmission type of the multicast / broadcast service in the first service area according to the multicast / broadcast access type supported by the terminal device.
  • Step S1340 may correspond to step S820 in the method 800 of the foregoing embodiment.
  • the SMF network element may send the identification of the multicast / broadcast transmission type and the multicast / broadcast service to the access network element corresponding to the multicast / broadcast service, which will not be repeated here.
  • the SMF network element can also update the service area, which is not repeated here.
  • FIG. 14 is a flowchart of still another multicast / broadcast service transmission method 1400 according to an embodiment of the present application. As shown in FIG. 14, the method 1400 includes the following steps.
  • S1401 The SMF network element sends a subscription message to the AMF network element.
  • the subscription message includes information of the first service area and an identifier of the multicast / broadcast service.
  • the identifier of the multicast / broadcast service may be a group identifier or a multicast / broadcast identifier.
  • the subscription message is not directed to a certain terminal device, but is targeted to all terminal devices belonging to the group corresponding to the multicast / broadcast service (identified by the identification of the multicast / broadcast service) in the first service area.
  • the AMF network element receives the subscription message sent by the SMF network element.
  • Step S1401 may correspond to step S910 in the method 900 of the foregoing embodiment.
  • the terminal device accesses the network, the terminal device sends a registration request (a NAS message) to the AMF network element.
  • the registration request message includes a multicast / broadcast access type supported by the terminal device, and an identifier of the multicast / broadcast service to which it is subscribed.
  • the AMF network element can know which multicast / broadcast service the terminal device has joined through the identification of the multicast / broadcast service. That is, the AMF network element can find the service area corresponding to the identifier of the multicast / broadcast service through the identifier of the multicast / broadcast service provided by the terminal device, that is, the first service area.
  • the AMF network element may store the identification of the multicast / broadcast service of the terminal device and the multicast / broadcast access type supported by the terminal device, so as to facilitate the subsequent steps (for example, step S1404).
  • the AMF network element receives a registration request message sent by the terminal device.
  • the registration request message may be considered a first request message.
  • Step S1402 may correspond to step S920 in the method 900 of the foregoing embodiment and step S1120 in the method 1100 of the foregoing embodiment.
  • the AMF network element allocates a registration area to the terminal device according to the information of the first service area.
  • the specific implementation process of S1403 can be:
  • the registration area allocated by the AMF network element for the terminal device is located in the first service area, or
  • the registration area allocated by the AMF network element to the terminal device does not overlap with the first service area.
  • S1404 The AMF network element sends a notification message to the SMF network element.
  • the notification message is used to inform the SMF network element that the multicast / broadcast service is in the effective area (that is, the first service area), and the terminal device joins the multicast / broadcast service, so that the SMF network element subsequently determines the multicast / broadcast Service transmission type and trigger activation of corresponding user plane resources.
  • the notification message may include an identifier of the terminal device, an identifier of a multicast / broadcast service, and a multicast / broadcast access type supported by the terminal device.
  • the SMF network element receives the notification message sent by the AMF network element.
  • Step S1404 may correspond to step S930 in the method 900 of the foregoing embodiment.
  • S1405 A registration response message sent by the AMF network element to the terminal device.
  • the registration response message may be a response message of a registration request message, which is also called a registration acceptance message.
  • the registration response message includes information on the registration area allocated in S1403.
  • the terminal device receives a registration response message sent by the AMF network element.
  • the SMF network element After receiving the notification message sent by the AMF network element in S1404, and when the SMF network element determines to adopt the shared link transmission mode, the SMF network element determines the multicast / broadcast transmission type.
  • the foregoing determination manner may be: judging the relationship between the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area and a preset value.
  • the SMF network element When the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is greater than or equal to (or greater than) a preset value, the SMF network element according to the multicast / broadcast access supported by the terminal device Type to determine the type of multicast / broadcast transmission of the multicast / broadcast service in the first service area, for example, one or more of the following: multicast / broadcast of NR system, multicast / broadcast of MBSFN, or Multicast / broadcast.
  • Step S1406 may correspond to step S820 in the method 800 of the foregoing embodiment.
  • the SMF network element triggers the UPF network element and the RAN network element to activate the user plane resources corresponding to the multicast / broadcast transmission type determined in S1406.
  • Step S1407 may correspond to step S830 in the method 800 of the foregoing embodiment.
  • S1408 Perform multicast / broadcast service transmission after the user plane resources are established.
  • the RAN network element may send data of the multicast / broadcast service to the terminal device through the established user plane resource.
  • S1403 and S1405 can be executed in parallel with S1404 and S1406 to S1408.
  • the registration area of the terminal device is combined with the multicast / broadcasting area to ensure that the terminal device can promptly notify the network side when it moves out of the multicast / broadcasting area.
  • the terminal device accesses the network, it informs the network side of the joining group information and multicast / broadcast capability through NAS messages, so that the network side can count the number of terminal devices.
  • FIG. 15 is a schematic flowchart of another method 1500 for transmitting a multicast / broadcast service according to an embodiment of the present application. As shown in FIG. 15, the method 1500 includes the following steps.
  • S1501 The SMF network element sends a subscription message to the AMF network element.
  • the subscription message includes information of the first service area and an identifier of the multicast / broadcast service.
  • the identifier of the multicast / broadcast service may be a group identifier or a multicast / broadcast identifier.
  • the subscription message is not directed to a certain terminal device, but is targeted to all terminal devices belonging to the group corresponding to the multicast / broadcast service (identified by the identification of the multicast / broadcast service) in the first service area.
  • the AMF network element receives the subscription message sent by the SMF network element.
  • Step S1501 may correspond to step S910 in the method 900 of the foregoing embodiment.
  • the registration request message includes a multicast / broadcast access type supported by the terminal device, and an identifier of the multicast / broadcast service to which it is subscribed.
  • the AMF network element can know which multicast / broadcast service the terminal device has joined through the identification of the multicast / broadcast service. That is, the AMF network element can find the service area corresponding to the identifier of the multicast / broadcast service through the identifier of the multicast / broadcast service provided by the terminal device, that is, the first service area.
  • the AMF network element may store the identification of the multicast / broadcast service of the terminal device and the multicast / broadcast access type supported by the terminal device, so as to facilitate the use in subsequent steps (for example, step S1504).
  • the AMF network element receives a registration request message sent by the terminal device.
  • the registration request message may be considered a first request message.
  • Step S1502 may correspond to step S920 in the method 900 of the foregoing embodiment and step S1120 in the method 1100 of the foregoing embodiment.
  • S1503 A registration response message sent by the AMF network element to the terminal device.
  • the registration response message is a response message of the registration request message, which is also called a registration acceptance message.
  • the registration response message includes the information of the registration area and also the information of the first service area, that is, the information of the effective area of the multicast / broadcast service.
  • the terminal device receives a registration response message sent by the AMF network element.
  • the AMF network element sends a notification message to the SMF network element.
  • the notification message is used to inform the SMF network element that the multicast / broadcast service is in the effective area (that is, the first service area), and the terminal device joins the multicast / broadcast service, so that the SMF network element subsequently determines the multicast / broadcast Service transmission type and trigger activation of corresponding user plane resources.
  • the notification message may include an identifier of the terminal device, an identifier of a multicast / broadcast service, and a multicast / broadcast access type supported by the terminal device.
  • the SMF network element receives the notification message sent by the AMF network element.
  • Step S1504 may correspond to step S930 in the method 900 of the foregoing embodiment.
  • the SMF network element After receiving the notification message sent by the AMF network element in S1204, and when the SMF network element determines to adopt the shared link transmission mode, the SMF network element determines the multicast / broadcast transmission type.
  • the transmission is transmitted in a multi-link transmission mode or a shared link transmission mode.
  • the foregoing determination manner may be: judging the relationship between the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area and a preset value.
  • the SMF network element When the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is greater than or equal to (or greater than) a preset value, the SMF network element according to the multicast / broadcast access supported by the terminal device Type to determine the type of multicast / broadcast transmission of the multicast / broadcast service in the first service area, for example, one or more of the following: multicast / broadcast of NR system, multicast / broadcast of MBSFN, or Multicast / broadcast.
  • Step S1505 may correspond to step S820 in the method 800 of the foregoing embodiment.
  • the SMF network element triggers the UPF network element and the RAN network element to activate the user plane resources corresponding to the multicast / broadcast transmission type determined in S1505.
  • Step S1506 may correspond to step S830 in the method 800 of the foregoing embodiment.
  • S1507 Perform multicast / broadcast service transmission after the user plane resources are established.
  • the RAN network element may send data of the multicast / broadcast service to the terminal device through the established user plane resource.
  • S1503 and S1504 to S1507 can be executed in parallel.
  • the AMF network element no longer considers the first service area to set up the registration area, but directly sends the information of the first service area to the terminal device.
  • the terminal device moves out of the current first service area, Will trigger the registration request process of the mobile type (moving out of the current business area).
  • the terminal device by notifying the terminal device of the multicast / broadcasting area (first service area), it can be ensured that the terminal device can promptly notify the network side when it moves out of the multicast / broadcasting area.
  • the terminal device accesses the network, it informs the network side of the joining group information and multicast / broadcast capability through NAS messages, so that the network side can count the number of terminal devices.
  • the multicast / broadcast service transmission method of the present application has been described in detail above with reference to FIGS. 1 to 15, and the core network element and terminal device of the present application are described in detail with reference to FIGS. 16 to 23.
  • FIG. 16 is a schematic block diagram of a core network element 1600 according to an embodiment of the present application. As shown in FIG. 16, the core network element 1600 may include:
  • An obtaining module 1610 configured to obtain a multicast / broadcast access type supported by terminal devices located in a first service area of the multicast / broadcast service and belonging to a group corresponding to the multicast / broadcast service;
  • a determining module 1620 configured to determine a multicast / broadcast transmission type of the multicast / broadcast service in the first service area according to a multicast / broadcast access type supported by the terminal device;
  • a sending module 1630 is configured to notify an access network element corresponding to the multicast / broadcast service to use the multicast / broadcast transmission type to transmit data of the multicast / broadcast service.
  • the core network element in the embodiment of the present application obtains the multicast / broadcast access type supported by the terminal devices of the group corresponding to the multicast / broadcast service, and determines the multi-port based on the multicast / broadcast access type supported by the terminal device.
  • the multicast / broadcast transmission type of the broadcast / broadcast service in the first service area, and the access network element is notified, so that the core network element can determine the specific RAT for multicast / broadcast transmission based on, which can better Adapting to the situation that the terminal equipment supports multiple RATs in the 5G mobile communication system can improve the efficiency of multicast / broadcast transmission.
  • the determining module 1620 may be specifically configured to: when the number of terminal devices in the group corresponding to the multicast / broadcast service in the first service area is greater than or When it is equal to a preset value, a multicast / broadcast transmission type of the multicast / broadcast service in the first service area is determined according to a multicast / broadcast access type supported by the terminal device.
  • the obtaining module 1610 may be further configured to: receive location information of the terminal device from a second core network element; the determining module 1620 may be further configured to: The location information of the terminal device determines a second service area of the multicast / broadcast service, where the second service area is located in the first service area; the sending module 1630 may be further configured to: send to the second core network The network element sends information of the second service area and an identifier of the multicast / broadcast service.
  • the sending module 1630 may be further configured to request a unified data management UDM network element for a multicast / broadcast access type supported by the terminal device; the obtaining module 1610 may specifically Used to: receive a multicast / broadcast access type supported by the terminal device from the UDM network element.
  • the sending module 1630 may be further configured to: send a subscription message to the second core network element, where the subscription message is used to subscribe to a terminal device that meets a preset condition and supports Multicast / broadcast access type; the acquisition module 1610 may be specifically configured to: receive a notification message from the network element of the second core network, where the notification message includes a multicast / broadcast supported by a terminal device that meets the preset condition Access type.
  • the subscription message includes information of the first service area
  • the terminal device that meets a preset condition includes a terminal device located in the first service area
  • the subscription message includes information of the first service area and an identifier of the multicast / broadcast service
  • the terminal device that meets a preset condition includes the terminal device located in the first service area and belonging to the multi-service The terminal equipment of the group corresponding to the broadcast / broadcast service.
  • the terminal device that meets a preset condition includes a terminal located in the first service area
  • the obtaining module 1610 may be further configured to obtain, according to the multicast / broadcast access type supported by the terminal device that meets the preset condition, that the location is within the first service area and belongs to the multiple The multicast / broadcast access type supported by the terminal devices of the group corresponding to the broadcast / broadcast service.
  • FIG. 17 is a schematic block diagram of another core network element 1700 according to an embodiment of the present application.
  • the core network element 1700 may include a processor 1710 and a memory 1720.
  • the memory 1720 stores computer instructions.
  • the processor 1710 executes the computer instructions, the core network element 1700 causes the core network element 1700 to be stored.
  • the core network element in the embodiment of the present application obtains the multicast / broadcast access type supported by the terminal devices of the group corresponding to the multicast / broadcast service, and determines the multi-port based on the multicast / broadcast access type supported by the terminal device.
  • the multicast / broadcast transmission type of the broadcast / broadcast service in the first service area, and the access network element is notified, so that the core network element can determine the specific RAT for multicast / broadcast transmission based on, which can better Adapting to the situation that the terminal equipment supports multiple RATs in the 5G mobile communication system can improve the efficiency of multicast / broadcast transmission.
  • the processor 1710 executes the computer instructions, so that the core network element 1700 specifically performs the following steps: when the multiple When the number of terminal devices in the group corresponding to the broadcast / broadcast service is greater than or equal to a preset value, determining that the multicast / broadcast service is in the first place according to the multicast / broadcast access type supported by the terminal device. Multicast / broadcast transmission type within the service area.
  • the processor 1710 is further configured to execute the computer instructions, so that the core network element 1700 further performs the following steps: receiving from the second core network element Location information of the terminal device; determining a second service area of the multicast / broadcast service according to the location information of the terminal device, the second service area being located within the first service area; The two core network element sends the information of the second service area and the identifier of the multicast / broadcast service.
  • the processor 1710 executes the computer instructions, so that the core network element 1700 specifically performs the following steps: requesting the terminal from a unified data management UDM network element A multicast / broadcast access type supported by the device; receiving a multicast / broadcast access type supported by the terminal device from the UDM network element.
  • the processor 1710 executes the computer instructions, so that the core network element 1700 specifically performs the following steps: sending a subscription message to the second core network element, The subscription message is used to subscribe to a multicast / broadcast access type supported by a terminal device that satisfies a preset condition; receiving a notification message from the network element of the second core network, where the notification message includes a message that satisfies the preset condition Multicast / broadcast access type supported by the terminal device.
  • the subscription message includes information of the first service area
  • the terminal device that meets a preset condition includes a terminal device located in the first service area
  • the subscription message includes information of the first service area and an identifier of the multicast / broadcast service
  • the terminal device that meets a preset condition includes the terminal device located in the first service area and belonging to the multi-service The terminal equipment of the group corresponding to the broadcast / broadcast service.
  • the terminal device that meets a preset condition includes a terminal located in the first service area
  • the processor 1710 is further configured to execute the computer instructions, so that the core network element 1700 further performs the following steps: according to the multicast / broadcast access supported by the terminal device that meets the preset condition Type, to obtain a multicast / broadcast access type supported by the terminal devices located in the first service area and belonging to the group corresponding to the multicast / broadcast service.
  • the core network element 1700 may further include a transceiver for receiving (acquiring) or sending data.
  • the core network element 1600 shown in FIG. 16 or the core network element 1700 shown in FIG. 17 may be used to perform operations or processes of the first core network element in the foregoing method embodiment, and the core network element 1600
  • the operations and / or functions of the modules and devices in the core network element 1700 are respectively to implement the corresponding process of the first core network element in the above method embodiment, and for the sake of brevity, they are not repeated here.
  • FIG. 18 is a schematic block diagram of another core network element 1800 according to an embodiment of the present application. As shown in FIG. 18, the core network element 1800 may include:
  • a receiving module 1810 configured to receive a subscription message from a first core network element, where the subscription message is used to subscribe to a multicast / broadcast access type supported by a terminal device that meets a preset condition;
  • the receiving module 1810 is further configured to receive a multicast / broadcast access type supported by the first terminal device from the first terminal device, where the first terminal device meets the preset condition;
  • a sending module 1820 is configured to send a notification message to the first core network element, where the notification message includes a multicast / broadcast access type supported by the first terminal device.
  • the core network element in the embodiment of the present application receives a subscription message of the first core network element that subscribes to a multicast / broadcast access type supported by a terminal device that meets a preset condition, and receives the multicast / broadcast supported by the terminal device from the first terminal device. Broadcast access type, and notify the first core network element of the multicast / broadcast access type supported by the first terminal device, thereby providing the first core network element to determine the specific RAT based on which multicast / Information about the capabilities of the terminal equipment required for broadcast transmission enables the multicast / broadcast transmission to better adapt to the case where the terminal equipment supports multiple RATs in the 5G mobile communication system, and can improve the efficiency of the multicast / broadcast transmission.
  • the subscription message includes information about a first service area of a multicast / broadcast service
  • the terminal device that satisfies a preset condition includes a location in the first service area
  • the subscription message includes information of a first service area of a multicast / broadcast service and an identifier of the multicast / broadcast service
  • the terminal device that meets a preset condition includes the first Terminal equipment in a service area and belonging to a group corresponding to the multicast / broadcast service.
  • the receiving module 1810 may be further configured to receive a first request message from the first terminal device, where the first request message is used to request a response to the first Terminal device registration; the core network element 1800 may further include a determining module 1830, configured to determine that the first terminal device meets the preset condition according to the first request message.
  • the first request message includes an identifier of the multicast / broadcast service
  • the subscription message includes information of the first service area and the multicast Identification of the broadcast / broadcast service
  • the determining module 1830 may be specifically configured to determine, according to the identification of the multicast / broadcast service and that the first terminal device is located in the first service area, that the first terminal device meets the Preset conditions.
  • the receiving module 1810 may be specifically configured to: receive a first request message from the first terminal device, where the first request message is used to request the A terminal device is registered, and the first request message includes a multicast / broadcast access type supported by the first terminal device.
  • the sending module 1820 may be further configured to send information of a registration area of the first terminal device to the first terminal device, where the registration area is located in the The first service area, or the registration area and the first service area do not intersect.
  • information about a registration area of the first terminal device is carried in a response message of the first request message.
  • the sending module 1820 may be further configured to send information of the first service area to the first terminal device.
  • the information of the first service area is carried in a response message of the first request message.
  • the sending module 1820 may be further configured to send the location information of the first terminal device to the first core network element; the receiving module 1810 may also be configured to receive Information of the second service area of the multicast / broadcast service from the first core network element, and an identifier of the multicast / broadcast service, the second service area is located in the first service area The sending module 1820 may be further configured to send the information of the second service area and the identifier of the multicast / broadcast service to the first terminal device.
  • FIG. 19 is a schematic block diagram of still another core network element 1900 according to an embodiment of the present application.
  • the core network element 1900 may include a processor 1910 and a memory 1920.
  • the memory 1920 stores computer instructions.
  • the core network element 1900 causes the core network element 1900 to The following steps are performed: receiving a subscription message from a network element of the first core network, where the subscription message is used to subscribe to a multicast / broadcast access type supported by a terminal device that meets a preset condition; and receiving the first from the first terminal device.
  • a multicast / broadcast access type supported by a terminal device the first terminal device meets the preset condition, and sends a notification message to the first core network element, the notification message including the first terminal device Supported multicast / broadcast access types.
  • the core network element in the embodiment of the present application receives a subscription message of the first core network element that subscribes to a multicast / broadcast access type supported by a terminal device that meets a preset condition, and receives the multicast / broadcast supported by the terminal device from the first terminal device. Broadcast access type, and notify the first core network element of the multicast / broadcast access type supported by the first terminal device, thereby providing the first core network element to determine the specific RAT based on which multicast / Information about the capabilities of the terminal equipment required for broadcast transmission enables the multicast / broadcast transmission to better adapt to the case where the terminal equipment supports multiple RATs in the 5G mobile communication system, and can improve the efficiency of the multicast / broadcast transmission.
  • the subscription message includes information about a first service area of a multicast / broadcast service
  • the terminal device that satisfies a preset condition includes a location in the first service area
  • the subscription message includes information of a first service area of a multicast / broadcast service and an identifier of the multicast / broadcast service
  • the terminal device that meets a preset condition includes the first Terminal equipment in a service area and belonging to a group corresponding to the multicast / broadcast service.
  • the processor 1910 is further configured to execute the computer instructions, so that the core network element 1900 further executes the following steps: receiving from the first terminal device A first request message, the first request message is used to request registration with the first terminal device; and according to the first request message, it is determined that the first terminal device meets the preset condition.
  • the first request message includes an identifier of the multicast / broadcast service
  • the subscription message includes information of the first service area and the multicast / Broadcast service identification
  • the processor 1910 executes the computer instructions, so that the core network element 1900 specifically performs the following steps: according to the multicast / broadcast service identification and the first terminal device is located in the Within the first service area, it is determined that the first terminal device meets the preset condition.
  • the processor 1910 executes the computer instructions, so that the core network element 1900 specifically performs the following steps: receiving a first from the first terminal device A request message, where the first request message is used to request registration with the first terminal device, and the first request message includes a multicast / broadcast access type supported by the first terminal device.
  • the processor 1910 is further configured to execute the computer instructions, so that the core network element 1900 further performs the following steps: sending to the first terminal device Information of a registration area of the first terminal device; wherein the registration area is located in the first service area, or the registration area and the first service area do not intersect.
  • information about a registration area of the first terminal device is carried in a response message of the first request message.
  • the processor 1910 is further configured to execute the computer instructions, so that the core network element 1900 further performs the following steps: sending to the first terminal device Information of the first service area.
  • the information of the first service area is carried in a response message of the first request message.
  • the processor 1910 is further configured to execute the computer instructions, so that the core network element 1900 further performs the following steps: to the first core network network Sending the location information of the first terminal device; receiving information about the second service area of the multicast / broadcast service from the first core network element, and the identifier of the multicast / broadcast service, so The second service area is located in the first service area; sending the information of the second service area and the identifier of the multicast / broadcast service to the first terminal device.
  • the core network element 1900 may further include a transceiver for receiving (acquiring) or sending data.
  • the core network element 1800 shown in FIG. 18 or the core network element 1900 shown in FIG. 19 may be used to perform operations or processes of the second core network element in the foregoing method embodiment, and the core network element 1800
  • the operations and / or functions of the various modules and devices in the core network element 1900 are respectively to implement the corresponding process of the second core network element in the above method embodiment, and for the sake of brevity, they are not repeated here.
  • FIG. 20 is a schematic block diagram of a terminal device 2000 according to an embodiment of the present application. As shown in FIG. 20, the terminal device 2000 includes:
  • An acquisition module 2010, configured to acquire a multicast / broadcast access type supported by the terminal device 2000;
  • the sending module 2020 is configured to send a multicast broadcast access type supported by the terminal device 2000 to a second core network element.
  • the terminal device in the embodiment of the present application reports to the core network element the multicast / broadcast access type supported by the terminal device, so that the core network element determines the specific based on the multicast / broadcast access type supported by the terminal device.
  • the RAT performs multicast / broadcast transmission, so that the multicast / broadcast transmission can better adapt to the situation that the terminal device supports multiple RATs in the 5G mobile communication system, and can improve the efficiency of the multicast / broadcast transmission.
  • the multicast broadcast access type supported by the terminal device 2000 is carried in a first request message, where the first request message is used to request the terminal Device 2000 is registered.
  • the sending module 2020 is further configured to send a first request message to the second core network element, where the first request message is used to request the terminal device 2000 registration.
  • the first request message includes an identifier of a multicast / broadcast service corresponding to a group to which the terminal device 2000 belongs.
  • the terminal device 2000 may further include a receiving module 2030 for receiving a first service area of the multicast / broadcast service from the second core network element.
  • the sending module 2020 is further configured to send a first request message to the second core network element when the terminal device 2000 moves out of the first service area.
  • FIG. 21 is a schematic block diagram of another terminal device 2100 according to an embodiment of the present application.
  • the terminal device 2100 includes a processor 2110 and a memory 2120.
  • the memory 2120 stores computer instructions.
  • the processor 2110 executes the computer instructions
  • the terminal device 2100 executes the following steps: The multicast / broadcast access type supported by the terminal device 2100; sending the multicast broadcast access type supported by the terminal device 2100 to the second core network element.
  • the multicast broadcast access type supported by the terminal device 2100 is carried in a first request message, and the first request message is used to request the terminal Device 2100 is registered.
  • the processor 2110 is further configured to execute the computer instructions, so that the terminal device 2100 further performs the following steps: sending to the second core network element A first request message, where the first request message is used to request registration with the terminal device 2100.
  • the first request message includes an identifier of a multicast / broadcast service corresponding to a group to which the terminal device 2100 belongs.
  • the processor 2110 is further configured to execute the computer instructions, so that the terminal device 2100 further performs the following steps: receiving a network element from the second core network element Information of the first service area of the multicast / broadcast service; when the terminal device 2100 moves out of the first service area, send a first request message to the second core network element.
  • the terminal device 2100 may further include a transceiver for receiving (acquiring) or transmitting data.
  • terminal device 2000 shown in FIG. 20 or the terminal device 2100 shown in FIG. 21 may be used to perform operations or processes of the terminal device in the foregoing method embodiment, and each module and device in the terminal device 2000 or the terminal device 2100 The operations and / or functions are respectively to implement the corresponding process of the terminal device in the foregoing method embodiments, and for the sake of brevity, they will not be repeated here.
  • FIG. 22 is a schematic block diagram of another core network element 2200 according to an embodiment of the present application. As shown in FIG. 22, the core network element 2200 may include:
  • the receiving module 2210 is configured to receive a second request message from a first core network element, where the second request message is used to request that the second request message is located in a first service area of a multicast / broadcast service and belongs to the multicast / broadcast Multicast / broadcast access type supported by the terminal equipment of the service corresponding group;
  • a sending module 2220 is configured to send a multicast broadcast access type supported by the terminal device to the first core network element.
  • the core network element in the embodiment of the present application receives the second request message of the multicast / broadcast access type supported by the terminal device from the first core network element, and generates the multicast / broadcast supported by the terminal device to the first core network element.
  • Access type thereby providing the first core network element with information for determining the capabilities of the terminal device required for specific RATs for multicast / broadcast transmission, so that the multicast / broadcast transmission can better adapt to 5G
  • a terminal device supports multiple RATs in a mobile communication system, the efficiency of multicast / broadcast transmission can be improved.
  • the second request message includes a list of the terminal devices located in the first service area and belonging to a group corresponding to the multicast / broadcast service .
  • the receiving module 2210 may be further configured to receive a second core network element that is located in the first service area and belongs to the multicast / broadcast service.
  • FIG. 23 is a schematic block diagram of another core network element 2300 according to an embodiment of the present application.
  • the core network element 2300 may include a processor 2310 and a memory 2320.
  • the memory 2320 stores computer instructions.
  • the core network element 2300 causes the core network element 2300 to be stored. Perform the following steps: receive a second request message from a first core network element, the second request message is used to request that the second request message is located in the first service area of the multicast / broadcast service and belongs to the multicast / broadcast service correspondence A multicast / broadcast access type supported by the terminal devices of the group; sending the multicast broadcast access type supported by the terminal device to the first core network element.
  • the core network element in the embodiment of the present application receives the second request message of the multicast / broadcast access type supported by the terminal device from the first core network element, and generates the multicast / broadcast supported by the terminal device to the first core network element.
  • Access type thereby providing the first core network element with information for determining the capabilities of the terminal device required for specific RATs for multicast / broadcast transmission, so that the multicast / broadcast transmission can better adapt to 5G
  • a terminal device supports multiple RATs in a mobile communication system, the efficiency of multicast / broadcast transmission can be improved.
  • the second request message includes a list of the terminal devices located in the first service area and belonging to a group corresponding to the multicast / broadcast service .
  • the processor 2310 is further configured to execute the computer instructions, so that the core network element 2300 further performs the following steps: receiving a second core network element A multicast broadcast access type supported by the terminal device located in the first service area and belonging to a group corresponding to the multicast / broadcast service.
  • the core network element 2300 may further include a transceiver for receiving (acquiring) or sending data.
  • the core network element 2200 shown in FIG. 22 or the core network element 2300 shown in FIG. 23 may be used to execute the operation or process of the third core network element in the foregoing method embodiment, and the core network element 2200
  • the operations and / or functions of the modules and devices in the core network element 2200 are respectively to implement the corresponding process of the third core network element in the above method embodiment, and for the sake of brevity, they will not be repeated here.
  • processors mentioned in the embodiments of the present application may include a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory mentioned in the embodiments of the present application may be volatile memory (non-volatile memory) or non-volatile memory (non-volatile memory), or may include both volatile and non-volatile memory .
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrical memory Erase programmable read-only memory (electrically EPROM, EEPROM), flash memory (flash memory), hard disk (hard disk drive) (HDD) or solid-state hard disk (solid-state drive (SSD)).
  • the volatile memory may be a random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double SDRAM double SDRAM
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • enhanced SDRAM enhanced SDRAM
  • SLDRAM synchronous connection dynamic random access memory
  • direct RAMbus RAM direct RAMbus RAM
  • the processor is a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component
  • the memory memory module
  • memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
  • An embodiment of the present application further provides a computer-readable storage medium having instructions stored thereon, and when the instructions are run on a computer, the computer is caused to execute the steps performed by the first core network element in the foregoing method embodiment. .
  • An embodiment of the present application further provides a computer-readable storage medium having instructions stored thereon.
  • the instructions When the instructions are run on a computer, the computer is caused to execute the steps performed by the second core network element in the foregoing method embodiment. .
  • An embodiment of the present application further provides a computer-readable storage medium that stores instructions thereon, and when the instructions are run on a computer, the computer is caused to execute the steps performed by the third core network element in the foregoing method embodiment. .
  • An embodiment of the present application further provides a computer-readable storage medium having instructions stored thereon, and when the instructions are run on a computer, the computer is caused to execute the steps performed by the terminal device in the foregoing method embodiment.
  • An embodiment of the present application further provides a computer program product including instructions, which is characterized in that when a computer runs the finger of the computer program product, the computer executes the foregoing method embodiment by a first core network element. A step of.
  • An embodiment of the present application further provides a computer program product including instructions, characterized in that when a computer runs the finger of the computer program product, the computer executes the foregoing method embodiment and is executed by a second core network element. A step of.
  • An embodiment of the present application further provides a computer program product including instructions, characterized in that when a computer runs the finger of the computer program product, the computer executes the foregoing method embodiment and is executed by a third core network element. A step of.
  • An embodiment of the present application further provides a computer program product including instructions, characterized in that when a computer runs the finger of the computer program product, the computer executes the steps performed by the terminal device in the foregoing method embodiment.
  • An embodiment of the present application further provides a computer chip that causes a computer to execute the steps performed by the first core network element in the foregoing method embodiment.
  • An embodiment of the present application further provides a computer chip that enables a computer to execute the steps performed by the second core network element in the foregoing method embodiment.
  • An embodiment of the present application further provides a computer chip that causes a computer to execute the steps performed by the third core network element in the foregoing method embodiment.
  • An embodiment of the present application further provides a computer chip that enables a computer to execute the steps performed by the terminal device in the foregoing method embodiment.
  • the device or network element provided in the embodiment of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented in software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may 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 may be from a website site, computer, server, or data center Transmission by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high density digital video disc (DVD)), or a semiconductor medium (for example, an SSD).
  • the size of the sequence numbers of the above processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not deal with the implementation process of the embodiment of this application. Constitute any limitation.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.

Abstract

本申请提供了一种多播/广播业务传输的方法、核心网网元和终端设备，该方法包括：第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于该多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；该第一核心网网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型；该第一核心网网元通知该多播/广播业务对应的接入网网元采用该多播/广播传输类型传输该多播/广播业务的数据。本申请的方法，第一核心网网元可以确定具体基于何种RAT进行多播/广播传输，能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。

Description

多播/广播业务传输的方法、核心网网元和终端设备
本申请要求于2018年09月30日提交中国专利局、申请号为201811159996.5、申请名称为“多播/广播业务传输的方法、核心网网元和终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及多播/广播业务传输的方法、核心网网元和终端设备。
背景技术
在第三代合作伙伴计划(the 3rd generation partnership project，3GPP)正在推进的移动通信系统中，存在网络侧向多个终端设备发送相同数据的需求，即存在点对多点的业务传输需求。
针对点对多点的业务传输需求，可以采用多链路传输方式，即采用复数个单播的方式实现点对多点的业务传输。具体地，网络侧建立复数个传输链路；发送方发送数据的多个副本；也可以采用共享链路传输方式，即网络侧提供一个被多个接收方共享的链路，发送方仅发送一份数据，网络侧将数据复制并传输至多个接收方。现有的一种具体的关联传送流程(associated delivery procedure，ADP)中，核心网中的广播多播业务中心(broadcast multicast service center，BM-SC)网元或应用功能(application function，AF)网元可以统计终端设备的个数，进而确定采用多链路传输方式还是共享链路传输方式，来进行点对多点的业务传输。
在新空口(new radio，NR)移动通信系统，即第5代(5th generation，5G)移动通信系统中，终端设备可能支持不同的、甚至多种无线接入技术(radio access technology，RAT)的多播广播。在这种情况下，网络侧仅仅确定是采用多链路传输方式还是共享链路传输方式是不够的，网络侧和终端设备仍然不知道具体基于何种RAT来进行点对多点的业务传输。因此，现有的点对多点业务传输的传输方案决策过程不能适用于终端设备支持多种RAT的多播广播的场景。
发明内容
本申请提供一种多播/广播业务传输的方法、核心网网元和终端设备，能够适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
第一方面，提供了一种多播/广播业务传输的方法，该方法包括第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于该多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；该第一核心网网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型；该第一核心网网元通知 该多播/广播业务对应的接入网网元采用该多播/广播传输类型传输该多播/广播业务的数据。
第一方面提供的多播/广播业务传输的方法，第一核心网网元获取多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，并根据终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型，并通知接入网网元，由此第一核心网网元可以确定具体基于何种RAT进行多播/广播传输，能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
其中，第一业务区域是该多播/广播业务的数据在其中进行传输的区域。第一业务区域的具体形式可以是小区的列表，也可以是追踪区域的列表。
其中，多播/广播业务对应的群组表示接受该多播/广播业务的终端设备的集合。
其中，多播/广播传输类型包括以下一种或多种：NR系统的多播/广播、多播/组播单频网络(multicast/broadcast single frequency network，MBSFN)的多播/广播、或单小区点对多点(single cell point to multipoint，SCPTM)的多播/广播。
其中，多播/广播业务对应的接入网网元可以替换为第一业务区域对应的接入网网元。
其中，多播/广播业务对应的接入网网元为从核心网网元接收多播/广播业务的数据，并向终端设备发送此多播/广播业务的数据的接入网网元。
其中，第一业务区域对应的接入网网元可以指为第一业务区域中的终端设备提供服务的接入网网元。
在第一方面的一种可能的实现方式中，所述第一核心网网元根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型，包括：当所述第一业务区域内所述多播/广播业务对应的群组中的终端设备的数量大于或等于预设值时，所述第一核心网网元根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型。在本可能的实现方式中，第一核心网网元可以是在第一业务区域内所述多播/广播业务对应的群组中的终端设备的数量大于或等于预设值时，才确定多播/广播业务在所述第一业务区域内的多播/广播传输类型。即，第一业务区域内所述多播/广播业务对应的群组中的终端设备的数量较少时，可以采用多链路传输方式；第一业务区域内所述多播/广播业务对应的群组中的终端设备的数量较多时，可以采用共享链路传输方式，并以确定的多播/广播传输类型进行多播/广播传输。
在第一方面的一种可能的实现方式中，所述方法还包括：所述第一核心网网元从第二核心网网元接收所述终端设备的位置信息；所述第一核心网网元根据所述终端设备的位置信息，确定所述多播/广播业务的第二业务区域，所述第二业务区域位于所述第一业务区域内；所述第一核心网网元向所述第二核心网网元发送所述第二业务区域的信息以及所述多播/广播业务的标识。在本可能的实现方式动态更新业务区域的范围，可以使得业务区域更加能够适配终端设备的数量和分布，避免由于预设的业务区域不符合实际终端设备分布导致的多播/广播效率低下，能够提高多播/广播业务传输的效率。
在第一方面的一种可能的实现方式中，所述第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，包括：所述第一核心网网元向统一数据管理UDM网元请求所述终端设备支持的 多播/广播接入类型；所述第一核心网网元接收来自所述UDM网元的所述终端设备支持的多播/广播接入类型。在本可能的实现方式中，终端设备支持的多播/广播接入类型可以来自于UDM网元，UDM网元可以反馈一个或多个终端设备支持的多播/广播接入类型。
在第一方面的一种可能的实现方式中，所述第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，包括：所述第一核心网网元向第二核心网网元发送订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；所述第一核心网网元接收来自所述第二核心网网元的通知消息，所述通知消息包含满足所述预设条件的终端设备支持的多播/广播接入类型。
在第一方面的一种可能的实现方式中，所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备。在本可能的实现方式中，当接收到终端设备上报的所支持的多播/广播接入类型时，第二核心网网元不进行判断，直接将终端设备上报的所支持的多播/广播接入类型发给第一核心网网元。由第一核心网网元判断终端设备是否属于多播/广播业务对应的群组。
在第一方面的一种可能的实现方式中，当所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备时，所述方法还包括：所述第一核心网网元根据所述满足所述预设条件的终端设备支持的多播/广播接入类型，获取所述位于所述第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型。
在第一方面的一种可能的实现方式中，所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识，所述满足预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。在本可能的实现方式中，由第二核心网网元判断终端设备是否属于多播/广播业务对应的群组。当终端设备属于多播/广播业务对应的群组时，第二核心网网元再将终端设备上报的所支持的多播/广播接入类型发给第一核心网网元。
第二方面，提供了一种一种多播/广播业务传输的方法，该方法包括：第二核心网网元接收来自第一核心网网元的订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；所述第二核心网网元接收来自第一终端设备的所述第一终端设备支持的多播/广播接入类型，所述第一终端设备满足所述预设条件；所述第二核心网网元向所述第一核心网网元发送通知消息，所述通知消息包含所述第一终端设备支持的多播/广播接入类型。
第二方面提供的多播/广播业务传输的方法，第二核心网网元接收第一核心网网元订阅满足预设条件的终端设备支持的多播/广播接入类型的订阅消息，从第一终端设备接收终端设备支持的多播/广播接入类型，并通知第一核心网网元该第一终端设备支持的多播/广播接入类型，由此向第一核心网网元提供用于确定具体基于何种RAT进行多播/广播传输所需的终端设备的能力的信息，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
在第二方面的一种可能的实现方式中，所述订阅消息包含多播/广播业务的第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备；或 者，所述订阅消息包含多播/广播业务的第一业务区域的信息和所述多播/广播业务的标识，所述满足预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。
在第二方面的一种可能的实现方式中，所述方法还包括：所述第二核心网网元接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册；所述第二核心网网元根据所述第一请求消息，确定所述第一终端设备满足所述预设条件。
在第二方面的一种可能的实现方式中，所述第一请求消息包含所述多播/广播业务的标识，所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识；所述第二核心网网元根据所述第一请求消息，确定所述第一终端设备满足所述预设条件，包括：所述第二核心网网元根据所述多播/广播业务的标识和所述第一终端设备位于所述第一业务区域内，确定所述第一终端设备满足所述预设条件。在本可能的实现方式中，终端设备通过第一请求消息中携带多播/广播业务的标识，使得第二核心网网元可以确定终端设备是否满足所述预设条件，可以节省信令及流程。
在第二方面的一种可能的实现方式中，所述第二核心网网元接收来自第一终端设备的所述第一终端设备支持的多播/广播接入类型，包括：所述第二核心网网元接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册，所述第一请求消息包含所述第一终端设备支持的多播/广播接入类型。在本可能的实现方式中，终端设备将所支持的多播/广播接入类型携带在注册请求中，可以节省信令及流程。
在第二方面的一种可能的实现方式中，所述方法还包括：所述第二核心网网元向所述第一终端设备发送所述第一终端设备的注册区域的信息；其中，所述注册区域位于所述第一业务区域内，或所述注册区域与所述第一业务区域没有交集。在本可能的实现方式中，通过将终端设备的注册区域与多播/广播的作用区域结合，可以保证终端设备在移出多播/广播的作用区域时得以及时通知网络侧。终端设备在接入网络时，通过NAS消息将加入的群组信息和多播/广播的能力告知网络侧，方便网络侧对终端设备的数量进行统计。
在第二方面的一种可能的实现方式中，所述第一终端设备的注册区域的信息携带在所述第一请求消息的响应消息中。本可能的实现方式可以节省信令。
在第二方面的一种可能的实现方式中，所述方法还包括：所述第二核心网网元向所述第一终端设备发送所述第一业务区域的信息。在本可能的实现方式中，通过将多播/广播的作用区域(第一业务区域)告知给终端设备，可以保证终端设备在移出多播/广播的作用区域时得以及时通知网络侧。终端设备在接入网络时，通过NAS消息将加入的群组信息和多播/广播的能力告知网络侧，方便网络侧对终端设备的数量进行统计
在第二方面的一种可能的实现方式中，所述第一业务区域的信息携带在所述第一请求消息的响应消息中。本可能的实现方式可以节省信令。
在第二方面的一种可能的实现方式中，所述方法还包括：所述第二核心网网元向所述第一核心网网元发送所述第一终端设备的位置信息；所述第二核心网网元接收来自所述第一核心网网元的所述多播/广播业务的第二业务区域的信息，以及所述多播/广播业务的标识，所述第二业务区域位于所述第一业务区域内；所述第二核心网网元向所述第一终端设备发送所述第二业务区域的信息，以及所述多播/广播业务的标识。
第三方面，提供了一种多播/广播业务传输的方法，包括：终端设备获取所述终端设备所支持的多播/广播接入类型；所述终端设备向第二核心网网元发送所述终端设备所支持的多播广播接入类型。
第三方面提供的多播/广播业务传输的方法，终端设备向核心网网元上报终端设备所支持的多播/广播接入类型，以便于核心网网元根据终端设备支持的多播/广播接入类型确定具体基于何种RAT进行多播/广播传输，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
在第三方面的一种可能的实现方式中，所述终端设备所支持的多播广播接入类型携带在第一请求消息中，所述第一请求消息用于请求对所述终端设备注册。
在第三方面的一种可能的实现方式中，所述方法还包括：所述终端设备向所述第二核心网网元发送第一请求消息，所述第一请求消息用于请求对所述终端设备注册。
在第三方面的一种可能的实现方式中，所述第一请求消息包含所述终端设备所属群组对应的多播/广播业务的标识。
在第三方面的一种可能的实现方式中，所述方法还包括：所述终端设备接收来自所述第二核心网网元的所述多播/广播业务的第一业务区域的信息；当所述终端设备移出所述第一业务区域时，所述终端设备向所述第二核心网网元发送第一请求消息。
第四方面，提供了一种多播/广播业务传输的方法，包括：第三核心网网元接收来自第一核心网网元的第二请求消息，所述第二请求消息用于请求位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；所述第三核心网网元向所述第一核心网网元发送所述终端设备所支持的多播广播接入类型。
在第四方面的一种可能的实现方式中，所述第二请求消息包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备的列表。
在第四方面的一种可能的实现方式中，所述方法还包括：所述第三核心网网元接收来自第二核心网网元的位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备支持的多播广播接入类型。
第五方面，本申请提供了一种核心网网元，用于执行上述第一方面或其任一可能的实现方式中的方法。具体地，该核心网网元可以包括用于执行第一方面或其任一可能的实现方式中的方法的模块。
第六方面，本申请提供了一种核心网网元，用于执行上述第二方面或其任一可能的实现方式中的方法。具体地，该核心网网元可以包括用于执行第二方面或其任一可能的实现方式中的方法的模块。
第七方面，本申请提供了一种终端设备，用于执行上述第三方面或其任一可能的实现方式中的方法。具体地，该核心网网元可以包括用于执行第三方面或其任一可能的实现方式中的方法的模块。
第八方面，本申请提供了一种核心网网元，用于执行上述第四方面或其任一可能的实现方式中的方法。具体地，该核心网网元可以包括用于执行第搜方面或其任一可能的实现方式中的方法的模块。
第九方面，本申请提供了一种核心网网元，该核心网网元包括处理器和存储器，该存 储器用于存储指令，该处理器用于执行该存储器存储的指令，使得该网络设备执行第一方面或其任一可能的实现方式中的方法。
第十方面，本申请提供了一种核心网网元，该核心网网元包括处理器和存储器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，使得该网络设备执行第二方面或其任一可能的实现方式中的方法。
第十一方面，本申请提供了一种终端设备，该终端设备包括处理器和存储器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，使得该终端设备执行第三方面或其任一可能的实现方式中的方法。
第十二方面，本申请提供了一种核心网网元，该核心网网元包括处理器和存储器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，使得该网络设备执行第四方面或其任一可能的实现方式中的方法。
第十三方面，本申请提供了一种计算机可读存储介质，其上存储有指令，当该指令在计算机上运行时，使得该计算机执行第一方面及其任一可能的实现方式的方法。
第十四方面，本申请提供了一种计算机可读存储介质，其上存储有指令，当该指令在计算机上运行时，使得该计算机执行第二方面及其任一可能的实现方式的方法。
第十五方面，本申请提供了一种计算机可读存储介质，其上存储有指令，当该指令在计算机上运行时，使得该计算机执行第三方面及其任一可能的实现方式的方法。
第十六方面，本申请提供了一种计算机可读存储介质，其上存储有指令，当该指令在计算机上运行时，使得该计算机执行第四方面及其任一可能的实现方式的方法。
第十七方面，本申请提供了一种包括指令的计算机程序产品，其特征在于，当计算机运行该计算机程序产品的该指时，该计算机执行第一方面及其任一可能的实现方式的方法。
第十八方面，本申请提供了一种包括指令的计算机程序产品，其特征在于，当计算机运行该计算机程序产品的该指时，该计算机执行第二方面及其任一可能的实现方式的方法。
第十九方面，本申请提供了一种包括指令的计算机程序产品，其特征在于，当计算机运行该计算机程序产品的该指时，该计算机执行第三方面及其任一可能的实现方式的方法。
第二十方面，本申请提供了一种包括指令的计算机程序产品，其特征在于，当计算机运行该计算机程序产品的该指时，该计算机执行第四方面及其任一可能的实现方式的方法。
第二十一方面，本申请提供了一种计算机芯片，该计算机芯片使得计算机执行第一方面及其任一可能的实现方式的方法。
第二十二方面，本申请提供了一种计算机芯片，该计算机芯片使得计算机执行第二方面及其任一可能的实现方式的方法。
第二十三方面，本申请提供了一种计算机芯片，该计算机芯片使得计算机执行第三方面及其任一可能的实现方式的方法。
第二十四方面，本申请提供了一种计算机芯片，该计算机芯片使得计算机执行第四方面及其任一可能的实现方式的方法。
第五至第二十四方面及其任一可能的实现方式所能得到的效果与第一至第四方面的相应效果一致，不再赘述。
附图说明
图1是本申请涉及的无线通信系统的示意图。
图2是应用本申请实施例的方法的点对多点的业务传输场景的示意图。
图3是采用多链路传输方式的点对多点的业务传输场景的示意图。
图4是采用共享链路传输方式的点对多点的业务传输场景的示意图。
图5是5G移动通信系统的系统架构示意图。
图6是MBMS的系统架构示意图。
图7是本申请实施例提供的一种结合了MBMS的5G移动通信系统的系统架构示意图。
图8是本申请实施例提供的一种多播/广播业务传输的方法的流程图。
图9是本申请实施例提供的另一种多播/广播业务传输的方法的流程图。
图10是一种MBMS传输过程的示意性流程图。
图11是本申请实施例提供的又一种多播/广播业务传输的方法的流程图。
图12是本申请实施例提供的又一种多播/广播业务传输的方法的流程图。
图13是本申请实施例提供的又一种多播/广播业务传输的方法的流程图。
图14是本申请实施例提供的又一种多播/广播业务传输的方法的流程图。
图15是本申请实施例提供的又一种多播/广播业务传输的方法的流程图。
图16是本申请实施例提供的一种核心网网元的示意性框图。
图17是本申请实施例提供的另一种核心网网元的示意性框图。
图18是本申请实施例提供的又一种核心网网元的示意性框图。
图19是本申请实施例提供的又一种核心网网元的示意性框图。
图20是本申请实施例提供的一种终端设备的示意性框图。
图21是本申请实施例提供的另一种终端设备的示意性框图。
图22是本申请实施例提供的又一种核心网网元的示意性框图。
图23是本申请实施例提供的又一种核心网网元的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1是本申请涉及的无线通信系统100的示意图。该无线通信系统100可以工作在高频频段上，不限于长期演进(long term evolution，LTE)系统，还可以是5G系统系统，机器与机器通信(machine to machine，M2M)系统，或未来演进的通信系统等。如图1所示，无线通信系统100可包括：一个或多个接入网设备110，一个或多个终端设备120，以及核心网(core network，CN)130。其中：
接入网设备110，属于(无线)接入网((radio)access network，(R)AN)。接入网设备110可以为基站，基站可以用于与一个或多个终端设备进行通信，也可以用于与一个或多个具有部分终端设备功能的基站进行通信(比如，宏基站与微基站之间的通信，接 入点之间的通信)。基站可以是LTE系统中的演进型基站(evolved Node B，eNB)，或5G系统中的基站。另外，基站也可以为接入点(access point，AP)、传输节点(transport point，TRP)、中心单元(central unit，CU)或其他网络实体，并且可以包括以上网络实体的功能中的部分或全部功能，不予限制。
终端设备120，可以分布在整个无线通信系统100中，可以是静止的，也可以是移动的。终端设备120可以是移动设备、移动台(mobile station)、移动单元(mobile unit)、M2M终端、无线单元，远程单元、用户代理、移动客户端、或用户设备(user equipment，UE)等。
具体的，接入网设备110可用于通过一个或多个天线与终端设备120通信。接入网设备110可通过回程(backhaul)接口150(例如，S1接口)向核心网130传输控制信息或者用户数据。接入网设备110与接入网设备110之间也可以通过回程(backhaul)接口140(如Xn接口)，直接地或者间接地相互通信。
核心网130，由一系列物理网元所构成，这些网元通过标准化的接口或服务调用相互通信，核心网负责例如用户接入与移动性管理、会话管理、策略控制、数据包转发、隧道管理和地址管理等功能。在LTE系统中，核心网可以包括移动管理实体(mobility management entity，MME)，服务网关(serving gateway，S-GW)，分组数据网关(packet data network gateway，PDN gateway，P-GW)和归属用户服务器(home subscriber server，HSS)等网元。在5G系统中，核心网可以包括接入和移动管理功能(access and mobility management function，AMF)网元，会话管理功能(session management function，SMF)网元，用户平面功能(user plane function，UPF)网元，统一数据管理(unified data management，UDM)网元和策略控制功能(policy control function，PCF)网元等。
图1示出的无线通信系统仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
图2是点对多点的业务传输场景200的示意图。如图2所示，点对多点的业务传输中，发送方210向多个终端设备发送数据。其中，图2中示意性地示出了三个终端设备：终端设备221、终端设备222和终端设备223。
图3是采用多链路传输方式的点对多点的业务传输场景300的示意图。如图3所示，点对多点的业务传输中，发送方310建立复数个传输链路，向多个终端设备发送数据。其中，图3中示意性地示出了三个终端设备：终端设备321、终端设备322和终端设备323；以及对应的三个链路：链路331、链路332和链路333。
图4是采用共享链路传输方式的点对多点的业务传输场景400的示意图。如图4所示，点对多点的业务传输中，发送方410建立一个被多个终端设备共享的链路430，向多个终端设备发送数据。其中，图4中示意性地示出了三个终端设备：终端设备421、终端设备422和终端设备423。
其中，图2至图4中的发送方可以是接入网设备或核心网中的用户平面功能网元。
图5是5G移动通信系统的系统架构示意图。下面将详细介绍其中网元的功能。
网络开放功能(network exposure function，NEF)网元：是运营商网络将网络中的网元，用于将网络中的数据开放给第三方应用服务器，或接收第三方应用服务器为网络提供 的数据。
网络存储功能(network repository function，NRF)网元：用于实现对网络中数据的存储。
统一数据管理(unified data management，UDM)网元：用于对对网络中的数据进行统一地数据管理。其主要功能是对各种用户签约数据的管理、用户鉴权数据管理、用户的标识管理等。
认证服务功能(authentication server function，AUSF)网元：主要功能包括用户鉴权和认证等。
会话管理功能(session management function，SMF)网元：主要功能包括会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择和管理用户平面功能和下行数据通知等。
接入和移动管理功能(access and mobility management function，AMF)网元：主要功能包括移动性管理、合法监听、和接入授权\鉴权等。
用户平面功能(user plane function，UPF)网元：主要提供用户平面的业务处理功能，包括业务路由、包转发、锚定功能、用户面数据的服务质量(quality of service，QoS)处理、上行链路的标识识别并路由到数据网络、下行包缓存和下行链路数据到达的通知触发、与外部数据网络连接等。
(R)AN：为终端设备的接入提供网络资源，可以是LTE系统或5G系统中的基站；负责无线资源管理、上下行数据分类和QoS应用、以及与控制面网元完成信令处理、与用户面网元完成数据转发等功能。值得注意的是，在LTE系统中，此网元可称为eNodeB或eNB。在5G系统中，(R)AN也可以被称为下一代无线接入网(the next generation radio access network，NG-RAN)。NG-RAN可以包括下一代eNodeB/eNB(next generation eNodeB/eNB，ng-eNB)和/或gNB。Ng-eNB可以支持5G核心网的接口(即可以与5G核心网连接)，并且其空口技术基于LTE技术。
策略控制功能(policy control function，PCF)网元：主要功能和LTE系统中的策略与计费规则功能(policy and charging rules function，PCRF)网元功能类似。其从UDM网元获得用户签约策略并下发到AMF网元、SMF网元等网元，再由AMF网元、SMF网元进一步下发到终端设备、RAN和UPF。
数据网络(data network，DN)：用于传输数据的网络，例如Internet网络等。
其中，本文中网络功能(network function，NF)实体是一种概括的描述，例如AMF网元，SMF网元，PCF网元，UDM网元等网元均可以被称为NF网元。
图6是多媒体广播多播业务(multimedia broadcast multicast service，MBMS)的系统架构示意图。如图6所示，内容提供方(content provider)可以是网络侧的网元或设备。MBMS接收方(MBMS receiver)可以是终端设备。内容提供方通过IP网将数据发送到BM-SC网元，然后BM-SC网元经由核心网的MBMS网关(MBMS gateway，MBMS GW)和无线接入网将数据发送到MBMS接收方。其中，无线接入网可以为演进的通用陆地无线接入网络(evolved universal terrestrial radio access network，E-UTRAN)和/或通用陆地无线接入网络(universal terrestrial radio access network，UTRAN)。
图7是本申请实施例提供的一种结合MBMS的5G移动通信系统的系统架构示意图。
在一些实施例中，图7中的SMF网元可以实现图6中MBMS的系统架构中BM-SC网元的会话管理功能，即，图7中的SMF网元可以实现对多播广播传输会话的管理功能，即此SMF被增强为可以支持群组会话管理功能(group-session management function，G-SMF)的网元。此外，图7中的SMF网元还可以实现BM-SC和MBMS的系统架构的控制面功能(control plane function，CPF)。其中，CPF主要包括对终端设备的多播/广播业务的用户面传输路径的建立、释放和更改等会话管理功能(例如SMF网元的功能)。
在另一些实施例中，图7中的SMF网元可以实现图6中MBMS的系统架构中BM-SC网元的业务管理功能，即组管理、安全管理以及业务公告功能。可替换地，这些业务管理功能可以在单独的MBMS业务控制(MBMS service control)网元中实现，MBMS业务控制网元是在5G系统中定义的新的网络功能实体，包含了BM-SC网元的业务管理功能。
图7中的AMF网元可以实现在SMF网元和RAN之间传递会话信息的功能。应理解，这里的AMF网元也可以是群组接入和移动管理功能(group-access and mobility management function，G-AMF)网元。
图7中的UPF网元可以实现多播广播传输的用户面功能，即图6中MBMS的系统架构中BM-SC网元和MBMS-GW的用户面功能。
需要说明的是，在本申请的各实施例中，第一核心网网元可以为具有MBMS功能的SMF网元或G-SMF网元，还可以为MBMS业务控制网元。第二核心网网元可以为AMF网元或G-AMF网元。第三核心网网元可以为UDM网元。此外，接入网网元、AMF网元、MBMS业务控制等设备均可以参照图1至7中任一附图中所涉及的描述，本申请对此不作限定。
下文中将以第一核心网网元为SMF网元，第二核心网网元为AMF网元，第三核心网网元为UDM网元为例进行说明。应理解，本申请还可以基于图7示出的系统架构以外的其它架构，各核心网网元可以为与上述网元具有类似功能的其它网元，本申请对此不作限定。
图8是本申请实施例提供的一种多播/广播业务传输的方法800的流程图，如下所述。
S810，第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于该多播/广播业务对应的群组的终端设备支持的多播/广播接入类型。
其中，第一业务区域是本申请各实施例所讨论的多播/广播业务对应的业务区域(service area，SA)。
第一业务区域是该多播/广播业务的数据在其中进行传输的区域。通常，一个多播/广播业务可以对应一个业务区域。第一业务区域的具体形式可以是小区的列表，也可以是追踪区域的列表。
其中，多播/广播业务对应的群组表示接受该多播/广播业务的终端设备的集合。通常，一个多播/广播业务可以对应一个群组，该群组中可以包括一个或多个终端设备。
在一些实施场景中，业务区域也可以称为群组会话区域。需要说明的是，业务区域是地理上的一个区域。可能存在一个或一些终端设备，其虽然在地理上位于在该区域内，但是并不接受该多播/广播业务的服务。群组是逻辑上的概念，属于多播/广播业务对应的群组的终端设备是接受该多播/广播业务的服务的终端设备。
其中，多播/广播传输类型包括以下一种或多种：NR系统的多播/广播、多播/组播单 频网络(multicast/broadcast single frequency network，MBSFN)的多播/广播、或单小区点对多点(single cell point to multipoint，SCPTM)的多播/广播。多播/广播传输类型还可以包括其他类型系统或其他类型网络的多播/广播，本申请对此不做限定。
进一步地，终端设备支持的多播/广播接入类型可认为是终端设备的能力，可以称之为终端设备的多播/广播接入能力。终端设备支持的多播/广播接入类型可以包括以下一种或多种：NR系统的多播/广播、MBSFN的多播/广播或SCPTM的多播/广播。
S820，该第一核心网网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型。
S830，该第一核心网网元通知该多播/广播业务对应的接入网网元采用该多播/广播传输类型传输该多播/广播业务的数据。
其中，多播/广播业务对应的接入网网元可以替换为第一业务区域对应的接入网网元。
其中，多播/广播业务对应的接入网网元为从核心网网元接收多播/广播业务的数据，并向终端设备发送此多播/广播业务的数据的接入网网元。
其中，第一业务区域对应的接入网网元可以指为第一业务区域中的终端设备提供服务的接入网网元。该接入网网元可以为位于第一业务区域内，也可以不位于第一业务区域内，本申请对此不作限定。
示例性地，步骤S830中，第一核心网网元可以向该多播/广播业务对应的接入网网元发送该多播/广播传输类型以及该多播/广播业务的标识，以通知接入网网元所确定的多播/广播传输类型适用于哪个多播/广播业务或哪个群组的。显然，步骤S830也可以替换为第一核心网网元向该多播/广播业务对应的接入网网元发送该多播/广播传输类型以及该多播/广播业务的标识。
其中，多播/广播业务的标识可以用于标识并区分不同的多播/广播业务，也可以用于标识多播/广播业务对应的群组。在现有的一些系统或网络中，用多播/广播标识来标识并区分多播/广播业务以及标识多播/广播业务对应的群组；在现有的另一些系统或网络中，用群组标识来标识并区分多播/广播业务以及标识多播/广播业务对应的群组。本申请的各实施例中，多播/广播业务的标识可以是多播/广播标识，也可以是群组标识。多播/广播标识表示该终端设备订阅的该多播/广播标识所指示的多播/广播业务的传输服务。群组标识表示该终端设备属于该多播/广播业务对应的群组。在终端设备与接入网网元或核心网网元交互信令，以开展多播/广播传输时，在信令中可以携带该多播/广播业务的标识。多播/广播业务的标识可以由SMF网元进行分配并告知应用服务器。应用服务器通过应用层将分配结果发送至终端设备。
本申请实施例的多播/广播业务传输的方法，第一核心网网元获取多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，并根据终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型，并通知接入网网元，由此第一核心网网元可以确定具体基于何种RAT进行多播/广播传输，能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，步骤S820可以包括：当该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量大于或等于预设值时，第一核心网网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内 的多播/广播传输类型。
第一核心网网元可以确定点对多点业务传输的传输方式，例如确定是采用多链路传输方式或是采用共享链路传输方式。
示例性地，第一核心网网元可以判断该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量与预设值的关系。当该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量小于(或者小于或等于)预设值时，确定采用多链路传输方式(即复数个单播的传输方式)来进行多播/广播业务传输。当该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量大于或等于(或者大于)预设值时，该第一核心网网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型。
在一个例子中，该第一核心网网元选择具有最多数量的终端设备支持的多播/广播接入类型，作为该多播/广播业务在该第一业务区域内的多播/广播传输类型。例如，位于多播/广播业务的第一业务区域内，且属于该多播/广播业务对应的群组的终端设备中，支持MBSFN的多播/广播的终端设备最多，则将MBSFN的多播/广播作为该多播/广播业务在该第一业务区域内的多播/广播传输类型。
在另一个例子中，对于一部分终端设备，采用某一多播/广播传输类型进行多播/广播业务传输，该部分终端设备均支持与该种多播/广播传输类型相对应的多播/广播接入类型；对于另一部分终端设备，采用另一多播/广播传输类型进行多播/广播业务传输，该另一部分终端设备均支持与该另一多播/广播传输类型相对应的多播/广播接入类型。例如，位于多播/广播业务的第一业务区域内，且属于该多播/广播业务对应的群组的终端设备中，一部分终端设备支持NR系统的多播/广播，则该部分终端设备采用NR系统的多播/广播传输类型进行进行多播/广播业务传输；另一部分终端设备支持SCPTM的多播/广播，则该另一部分终端设备采用SCPTM的多播/广播传输类型进行进行多播/广播业务传输。
在又一个例子中，某些终端设备可能支持多种多播/广播接入类型，第一核心网网元可以根据终端设备的能力和终端设备的总数量，为这些终端设备选定合适的多种多播/广播接入类型来进行多播/广播业务传输。
可选地，上述实施例的另一种实施场景中，方法800还可以包括：第一核心网网元从第二核心网网元接收该终端设备的位置信息；第一核心网网元根据该终端设备的位置信息，确定该多播/广播业务的第二业务区域，该第二业务区域位于该第一业务区域内；第一核心网网元向该第二核心网网元发送该第二业务区域的信息以及该多播/广播业务的标识。
其中，本申请各实施例中，第一业务区域的信息以及第二业务区域的信息具体可以是小区标识的列表或追踪区域标识的列表。
第一核心网网元确定第二业务区域，以替代原有的第一业务区域的过程，可以理解为第一核心网网元动态更新业务区域的范围。更新业务区域的范围时，第一核心网网元可以通过根据订阅同一个多播广播业务的终端设备的数量和分布来确定。在一个例子中，终端设备的数量和分布可以通过统计各终端设备的位置信息来确定。终端设备的位置信息可以是第二核心网网元向第一核心网网元发送的。第一核心网网元则可以通过终端设备上报，来得到终端设备的位置信息。当然，第一核心网网元也可以通过其他方式获得终端设备的 位置信息，本申请对此不作限定。终端设备的位置信息可以是终端设备所在小区的小区标识。当然，终端设备的位置信息也可以是其他形式的信息，本申请对此不作限定。
如前文所描述的，动态更新业务区域的范围可以包括确定该多播/广播业务的第二业务区域，该第二业务区域位于该第一业务区域内。即，动态更新业务区域的范围可以是缩小现有的业务区域的范围，缩小第一业务区域为第二业务区域。此外，动态更新业务区域的范围还可以是扩大现有的业务区域的范围，或者从候选集合中选择一个新的业务区域来适用该多播/广播业务，本申请对此不作限定。
动态更新业务区域的范围后，第一核心网网元可以通知相应的核心网网元和/或接入网网元，例如通知UPF和RAN，以便于核心网网元和/或接入网网元对业务区域的范围进行更新。在一个例子中，第一核心网网元确定第二业务区域后，可以向第二核心网网元发送该第二业务区域的信息以及该多播/广播业务的标识。相对应地，第二核心网网元接收来自第一核心网网元的多播/广播业务的第二业务区域的信息，以及多播/广播业务的标识。应理解，发送多播/广播业务的标识是为了指示所确定的第二业务区域的信息是适用于哪个多播/广播业务或哪个群组的。第二核心网网元可以向终端设备发送第二业务区域的信息以及多播/广播业务的标识。即，通过第二核心网网元可以告知终端设备最新的业务区域的信息，该过程可以通过业务通知(service announcement)过程实现，此处不进行赘述。
动态更新业务区域的范围，可以使得业务区域更加能够适配终端设备的数量和分布，避免由于预设的业务区域不符合实际终端设备分布导致的多播/广播效率低下，能够提高多播/广播业务传输的效率。
应理解，该动态更新业务区域的范围的步骤，可以不基于步骤S810至S830，而是形成独立的动态更新业务区域的范围的方法。
可选地，在上述实施例的又一种实施场景中，步骤S810可以包括：该第一核心网网元向UDM网元(可以是上述第三核心网网元)请求该终端设备支持的多播/广播接入类型；该第一核心网网元接收来自该UDM网元的该终端设备支持的多播/广播接入类型。
相对应地，第三核心网网元接收来自第一核心网网元的请求，例如可以为第二请求消息，该第二请求消息用于请求位于多播/广播业务的第一业务区域内，且属于该多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；该第三核心网网元向该第一核心网网元发送该终端设备所支持的多播广播接入类型。即，终端设备支持的多播/广播接入类型可以来自于UDM网元。
其中，该第二请求消息可以包括位于该第一业务区域内且属于该多播/广播业务对应的群组的该终端设备的列表。应理解，第二请求消息还可以通过其他的内容来请求该终端设备支持的多播/广播接入类型。例如，第二请求消息仅用于请求终端设备支持的多播/广播接入类型，而不发送终端设备的列表。第三核心网网元可以将其查找到的所有的终端设备的多播/广播接入类型相关信息全部发送给第一核心网网元。由第一核心网网元确定参考哪些终端设备支持的多播/广播接入类型，来确定多播/广播业务在该第一业务区域内的多播/广播传输类型。本申请对第二请求消息的具体形式不作限定。
该实施场景对应的具体例子将在下文的图13中进行详细说明。
可选地，在上述实施例的又一种实施场景中，步骤S810可以包括：该第一核心网网元向第二核心网网元发送订阅消息，该订阅消息用于订阅满足预设条件的终端设备支持的 多播/广播接入类型；该第一核心网网元接收来自该第二核心网网元的通知消息，该通知消息包含满足该预设条件的终端设备支持的多播/广播接入类型。相对应地，第二核心网网元接收来自第一核心网网元的订阅消息，并且第二核心网网元向第一核心网网元发送通知消息。即，终端设备支持的多播/广播接入类型可以来自于第二核心网网元，例如AMF网元。
可选地，在一个例子中，该订阅消息包含该第一业务区域的信息和该多播/广播业务的标识，该满足预设条件的终端设备包括位于该第一业务区域内且属于该多播/广播业务对应的群组的终端设备。在该例子中，第一核心网网元向第二核心网网元发送多播/广播业务的标识。这样第二核心网网元通过多播/广播业务的标识，可以区分出是哪个多播/广播业务，或确定出多播/广播业务对应的群组。当第二核心网网元接收到终端设备上报的所支持的多播/广播接入类型时，第二核心网网元判断终端设备是否属于多播/广播业务对应的群组。当终端设备属于多播/广播业务对应的群组时，第二核心网网元再将终端设备上报的所支持的多播/广播接入类型发给第一核心网网元。
可选地，在另一个例子中，该订阅消息包含该第一业务区域的信息，该满足预设条件的终端设备包括位于该第一业务区域内的终端设备。在该例子中，第一核心网网元不向第二核心网网元发送多播/广播业务的标识。当接收到终端设备上报的所支持的多播/广播接入类型时，第二核心网网元不进行判断，直接将终端设备上报的所支持的多播/广播接入类型发给第一核心网网元。由第一核心网网元判断终端设备是否属于多播/广播业务对应的群组。即，当该订阅消息包含该第一业务区域的信息，该满足预设条件的终端设备包括位于该第一业务区域内的终端设备时，该方法800还可以包括：该第一核心网网元根据该满足该预设条件的终端设备支持的多播/广播接入类型，获取该位于该第一业务区域内，且属于该多播/广播业务对应的群组的终端设备支持的多播/广播接入类型。
图9是本申请实施例提供的另一种多播/广播业务传输的方法900的流程图，具体如下。
S910，第二核心网网元接收来自第一核心网网元的订阅消息，该订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型。
S920，该第二核心网网元接收来自第一终端设备的该第一终端设备支持的多播/广播接入类型，该第一终端设备满足该预设条件。
应理解，第二核心网网元的终端设备支持的多播/广播接入类型的相关信息可以来自于终端设备。相对应地，第一终端设备获取第一终端设备所支持的多播/广播接入类型，并向向第二核心网网元发送第一终端设备所支持的多播广播接入类型。其中，第一终端设备可以从内存中获取第一终端设备所支持的多播/广播接入类型。
S930，该第二核心网网元向该第一核心网网元发送通知消息，该通知消息包含该第一终端设备支持的多播/广播接入类型。
本申请实施例的多播/广播业务传输的方法，第二核心网网元接收第一核心网网元订阅满足预设条件的终端设备支持的多播/广播接入类型的订阅消息，从第一终端设备接收终端设备支持的多播/广播接入类型，并通知第一核心网网元该第一终端设备支持的多播/广播接入类型，由此向第一核心网网元提供用于确定具体基于何种RAT进行多播/广播传输所需的终端设备的能力的信息，使得多播/广播传输能够更好地适应5G移动通信系统中 终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，该订阅消息包含多播/广播业务的第一业务区域的信息，该满足预设条件的终端设备包括位于该第一业务区域内的终端设备；或者，该订阅消息包含多播/广播业务的第一业务区域的信息和该多播/广播业务的标识，该满足预设条件的终端设备包括位于该第一业务区域内且属于该多播/广播业务对应的群组的终端设备。本实施场景中的订阅消息，与方法800中对订阅消息的详细说明类似，此处不再赘述。
可选地，在上述实施例的另一种实施场景中，方法900还可以包括：该第二核心网网元接收来自该第一终端设备的第一请求消息，该第一请求消息用于请求对该第一终端设备注册；该第二核心网网元根据该第一请求消息，确定该第一终端设备满足该预设条件。相应地，第一终端设备向该第二核心网网元发送第一请求消息。
在一个例子中，该第一请求消息可以包含该多播/广播业务的标识，该订阅消息包含该第一业务区域的信息和该多播/广播业务的标识；该第二核心网网元根据该第一请求消息，确定该第一终端设备满足该预设条件，可以包括：该第二核心网网元根据该多播/广播业务的标识和该第一终端设备位于该第一业务区域内，确定该第一终端设备满足该预设条件。第二核心网网元根据第一请求消息中的该多播/广播业务的标识，确定第一终端设备属于多播/广播业务对应的群组。或者说，第二核心网网元根据第一请求消息中的该多播/广播业务的标识，确定第一终端设备订阅了多播/广播业务。
此外，第一终端设备可以在第一请求消息中携带第一终端设备的位置，使得第二核心网网元能够确定第一终端设备位于第一业务区域内。第一终端设备也可以在确定自己位于第一业务区域内时，才向第二核心网网元发送第一请求消息。或者，接入网网元将第一终端设备的位置信息与第一请求消息一并发送至第二核心网网元。
可选地，在上述实施例的又一种实施场景中，该第二核心网网元接收来自第一终端设备的该第一终端设备支持的多播/广播接入类型，可以包括：该第二核心网网元接收来自该第一终端设备的第一请求消息，该第一请求消息用于请求对该第一终端设备注册，该第一请求消息包含该第一终端设备支持的多播/广播接入类型。具体而言，第一终端设备上报所支持的多播/广播接入类型时，可以将第一终端设备支持的多播/广播接入类型携带在第一请求消息中，这样可以节省信令和资源。即，第一终端设备可以通过已有的非接入层(non-access stratum，NAS)流程，向网络侧上报其支持的多播/广播接入类型，以达到节省信令和资源的目的。当然，第一终端设备也可以不通过第一请求消息上报所支持的多播/广播接入类型，而是采用其他的信令，本申请对此不作限定。
下面详细说明上述实施例的另外两种可选的实施场景，在此之前，先说明这两种可选的实施场景所针对的现有方案中所存在的问题。
现有的终端设备可以处于连接态和空闲态。对于多链路传输方式(即单播的传输方式)而言，只有终端设备处于连接态才能接收/发送数据。当终端设备处于空闲态时，其相关的通信模块会处于关闭状态，由此终端设备的功率消耗处于相对较低的情形。当终端设备想要向网络侧发送数据，或网络侧想要向终端设备发送单播数据时，终端设备必须首先进入连接态。
对于终端设备而言，如果其处于空闲态，则意味着终端设备在更换驻留小区时，网络 侧无法及时获知终端设备位置的改变。这样当网络侧需要发送数据至空闲状态的终端设备时，网络侧会寻呼不到终端设备。现有的系统为了实现对终端设备的粗粒度的位置管理，提出了注册区域(registration area，RA)的概念。当网络侧需要向空闲态的终端设备发送下行数据时，网络侧只需要向注册区域发送寻呼消息。当终端设备移出了当前的注册区域时，终端设备需要向网络侧发送移动类型的注册请求消息，网络侧会为终端设备再分配新的注册区域。前文中的第一请求消息，即为注册请求消息。
一种现有的点对多点业务传输的传输方案决策基于关联传送流程(associated delivery procedure，ADP)。图10是MBMS传输过程1000的流程图，具体如下。
S1010，关联传送功能(associated delivery function，ADF)网元向MBMS传送功能(MBMS delivery function)网元发送传输请求(transmission request)。
S1021-S102n，MBMS传送功能网元与网关GPRS支持节点(gateway GPRS support node，GGSN)分别开始会话1-n(session start 1-n)。
S1031-S103n，向MBMS的终端设备传输MBMS数据1-n(MBMS data transfer 1-n)。
S1041-S104n，MBMS传送功能网元与GGSN分别结束会话1-n(session stop 1-n)。
S1050，执行ADP。
由图10可知，在成功发送MBMS数据(可能通过多链路传输方式发送，也可能通过共享链路传输方式发送)后，终端设备会发起ADP。此过程可用于终端设备向MBMS业务控制网元上报此终端设备使用了多播/广播业务，方便BM-SC网元进行统计是否需要进行多链路传输方式共享链路传输方式的切换。BM-SC网元可以基于预配置的预设值进行传输方式的调整。
ADP是终端设备在接收到多播/广播业务的数据后，向BM-SC网元(或AF网元)发送消息告知其接收了多播/广播业务的数据。这样BM-SC网元(或AF网元)可以统计接收终端设备的个数，进而确定采用的传输方案(即：采用多链路传输方式还是共享链路传输方式)。
然而，上述过程存在以下问题：
首先，终端设备处于空闲状态时，仍然可以接收多播/广播业务的数据，但终端设备发起ADP时(即向网络侧发送数据时)要求终端设备首先进入连接状态，并且网络侧需要为终端设备建立额外的传输资源，这会浪费终端设备的功率以及网络侧的资源。
其次，ADP是在终端设备接收到多播/广播业务的数据之后才会上报，这样网络侧统计的数据较迟(多播/广播业务的数据发送之后才会触发BM-SC统计，进而切换传输方式)。
针对上述问题，方法900对应的实施例的一种实施场景中，方法900还可以包括：第二核心网网元接收来自第一终端设备的第一请求消息，该第一请求消息包含多播/广播业务的标识，该第一请求消息用于请求对第一终端设备注册；该第二核心网网元向该第一终端设备发送该第一终端设备的注册区域的信息；其中，该注册区域位于该第一业务区域内，或该注册区域与该第一业务区域没有交集。
该实施场景使得第二核心网网元可以根据多播/广播业务的标识，对应得到第一业务区域。第二核心网网元在为第一终端设备设置注册区域时，考虑第一业务区域，即多播/广播业务发送的范围。注册区域位于该第一业务区域内，或该注册区域与该第一业务区域没有交集。这样的话，当第一终端设备移出第一业务区域时，可以及时通知第二核心网网 元，第二核心网网元利用已有的注册请求流程可以同时统计在第一业务区域内的终端设备的个数，以便于第二核心网网元确定采用的传输方案。相对于ADP是在终端设备接收到多播/广播业务的数据之后才会确定采用的传输方案，该实施场景随着终端设备移出某个业务区域，终端设备可以及时上报位置变化的情况，使得第二核心网网元及时切换采用的传输方案。同时，该过程合并在注册请求流程中，可以节省终端设备的功率以及网络侧的资源。
可选地，该第一终端设备的注册区域的信息可以携带在该第一请求消息的响应消息中。当然，注册区域的信息也可以在其他信令中携带，本申请对此不作限定。
该实施场景的具体例子将在下文的图14中进行详细说明。
针对上述问题，方法900对应的实施例的另一种实施场景中，方法900还可以包括：所述第二核心网网元向所述第一终端设备发送所述第一业务区域的信息。相应地第一终端设备接收来自所述第二核心网网元的多播/广播业务的第一业务区域的信息。
该实施场景中，第二核心网网元将第一业务区域的信息发送给第一终端设备。该第一业务区域的信息包括多播/广播业务发送的范围。这样的话，当第一终端设备移出第一业务区域时，第一终端设备可以向第二核心网网元发送第一请求消息。第一终端设备通过第一请求消息通知第二核心网网元，第二核心网网元利用已有的注册请求流程可以同时统计在第一业务区域内的终端设备的个数，以便于第二核心网网元确定采用的传输方案。相对于ADP是在终端设备接收到多播/广播业务的数据之后才会确定采用的传输方案，该实施场景随着终端设备移出第一业务区域，终端设备可以及时上报位置变化的情况，使得第二核心网网元及时切换采用的传输方案。同时，该过程合并在注册请求流程中，可以节省终端设备的功率以及网络侧的资源。
可选地，该第一业务区域的信息携带在所述第一请求消息的响应消息中，以节省信令开销。当然，第一业务区域的信息也可以在其他信令中携带，或者该第一业务区域的信息可以单独发送，本申请对此不作限定。
该实施场景的具体例子将在下文的图15中进行详细说明。
可选地，在上述实施例的又一种实施场景中，该方法900还可以包括：该第二核心网网元向该第一核心网网元发送该第一终端设备的位置信息；该第二核心网网元接收来自该第一核心网网元的该多播/广播业务的第二业务区域的信息，以及该多播/广播业务的标识，该第二业务区域位于该第一业务区域内；该第二核心网网元向该第一终端设备发送该第二业务区域的信息，以及该多播/广播业务的标识。本实施场景中，第二核心网网元在动态更新业务区域的范围的过程所执行的操作，与方法800中动态更新业务区域的范围的过程的详细描述中的第二核心网网元的操作对应，此处不再赘述。
图11是本申请实施例提供的又一种多播/广播业务传输的方法1100的流程图，具体如下。
S1110，终端设备获取该终端设备所支持的多播/广播接入类型。
其中，终端设备所支持的多播/广播接入类型可以从内存中获取。
S1120，该终端设备向第二核心网网元发送该终端设备所支持的多播广播接入类型。
本申请实施例的多播/广播业务传输的方法，终端设备向核心网网元上报终端设备所支持的多播/广播接入类型，以便于核心网网元根据终端设备支持的多播/广播接入类型确 定具体基于何种RAT进行多播/广播传输，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，该终端设备所支持的多播广播接入类型可以携带在第一请求消息中，该第一请求消息用于请求对该终端设备注册。
可选地，在上述实施例的另一种实施场景中，该方法1100还可以包括：该终端设备向该第二核心网网元发送第一请求消息，该第一请求消息用于请求对该终端设备注册。
可选地，在上述实施例的又一种实施场景中，该第一请求消息可以包含该终端设备所属群组对应的多播/广播业务的标识。
可选地，在上述实施例的又一种实施场景中，该方法1100还可以包括：该终端设备接收来自该第二核心网网元的该多播/广播业务的第一业务区域的信息；当该终端设备移出该第一业务区域时，该终端设备向该第二核心网网元发送第一请求消息。
本实施例中，终端设备所执行的操作，与方法900中终端设备所执行的操作对应，此处不再赘述。
图12是本申请实施例提供的又一种多播/广播业务传输的方法1200的流程图，具体如下。
S1210，第三核心网网元接收来自第一核心网网元的第二请求消息，该第二请求消息用于请求位于多播/广播业务的第一业务区域内，且属于该多播/广播业务对应的群组的终端设备支持的多播/广播接入类型。
S1220，该第三核心网网元向该第一核心网网元发送该终端设备所支持的多播广播接入类型。
本申请实施例的多播/广播业务传输的方法，第三核心网网元接收第一核心网网元请求终端设备支持的多播/广播接入类型的第二请求消息，向第一核心网网元发生终端设备支持的多播/广播接入类型，由此向第一核心网网元提供用于确定具体基于何种RAT进行多播/广播传输所需的终端设备的能力的信息，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，该第二请求消息可以包括位于该第一业务区域内且属于该多播/广播业务对应的群组的该终端设备的列表。
可选地，在上述实施例的另一种实施场景中，该方法1200还可以包括：该第三核心网网元接收来自第二核心网网元的位于该第一业务区域内且属于该多播/广播业务对应的群组的该终端设备支持的多播广播接入类型。
可选地，在上述实施例的又一种实施场景中，该方法1200还可以包括：该第三核心网网元接收来自第二核心网网元的位于该第一业务区域内且属于该多播/广播业务对应的群组的该终端设备支持的多播广播接入类型。即第三核心网网元中的终端设备支持的多播广播接入类型的相关信息，可以是来自第二核心网网元的。当然，第三核心网网元可以通过其他方法或从其他设备获得终端设备支持的多播广播接入类型，本申请对此不作限定。
下面以一个具体的例子说明本申请实施例提供的又一种多播/广播业务传输的方法1300。图13是本申请实施例提供的又一种多播/广播业务传输的方法1300的流程图。该方法1300适用于以下场景：AF网元已知订阅多播/广播业务的终端设备的列表，并且已知需要向第一业务区域(该第一业务区域不随着终端设备位置的变化而变化)发送数据。 此时，第一核心网网元(例如，SMF网元)仅需要确定以哪种(些)多播/广播传输类型向此第一业务区域发送多播/广播业务的数据。该方法1300通过第三核心网网元(例如，UDM网元)参与实现。
如图13所示，多播/广播业务传输的方法1300可以包括以下步骤。
S1310，AF网元向SMF网元发送多播/广播业务请求消息。
其中，该多播/广播业务请求消息中包含多播/广播业务作用的第一业务区域，以及接收该多播/广播业务的终端设备的列表。
S1320，SMF网元向UDM网元发送第二请求消息。
相应地，UDM网元接收SMF网元发送的第二请求消息。
其中，第二请求消息可以包括位于第一业务区域内且属于该多播/广播业务对应的群组的终端设备的列表。
步骤S1320可以与前文实施例的方法1200中的步骤S1210对应。
S1330，UDM网元向SMF网元发送终端设备支持的多播/广播接入类型的列表。
相应地，SMF网元接收UDM网元发送的终端设备支持的多播/广播接入类型的列表。
步骤S1330可以与前文实施例的方法800中的步骤S810以及前文实施例的方法1200中的步骤S1220对应。
其中，UDM网元可以查找本地的签约数据，找到终端设备的列表对应的终端设备支持的多播/广播接入类型的列表。
S1340，SMF网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型。
步骤S1340可以与前文实施例的方法800中的步骤S820对应。
之后，SMF网元可以向该多播/广播业务对应的接入网网元发送采用该多播/广播传输类型和该多播/广播业务的标识，此处不再赘述。此外，SMF网元还可以更新业务区域，此处也不再赘述。
图14是本申请实施例提供的又一种多播/广播业务传输的方法1400的流程图。如图14所示，方法1400包括以下步骤。
S1401，SMF网元向AMF网元发送订阅消息。
其中，该订阅消息包含第一业务区域的信息和多播/广播业务的标识。
其中，多播/广播业务的标识可以为群组标识(group ID)或多播/广播标识。该订阅消息不是针对某个终端设备的，而是针对第一业务区域内的所有属于该多播/广播业务(通过多播/广播业务的标识来标识)对应的群组的终端设备。
相应地，AMF网元接收SMF网元发送的订阅消息。
步骤S1401可以与前文实施例的方法900中的步骤S910对应。
S1402，当终端设备接入到网络时，终端设备向AMF网元发送注册请求(registration request)消息(其是一种NAS消息)。
其中，注册请求消息中包含终端设备支持的多播/广播接入类型，以及其订阅的多播/广播业务的标识。
示例性地，AMF网元通过多播/广播业务的标识可以获知终端设备加入了哪一个多播/广播业务。即，AMF网元通过终端设备提供的多播/广播业务的标识可以找到多播/广播业 务的标识所对应的业务区域，即第一业务区域。
此外，AMF网元可以存储终端设备的多播/广播业务的标识和终端设备支持的多播/广播接入类型，以方便后续步骤(例如步骤S1404)使用。
相应地，AMF网元接收终端设备发送的注册请求消息。注册请求消息可认为是第一请求消息。
步骤S1402可以与前文实施例的方法900中的步骤S920以及前文实施例的方法1100中的步骤S1120对应。
S1403，AMF网元根据第一业务区域的信息，为终端设备分配注册区域。
其中，S1403具体实现过程可以是:
a.AMF网元为终端设备分配的注册区域位于第一业务区域内，或者
b.AMF网元为终端设备分配的注册区域与所述第一业务区域没有交集。
S1404，AMF网元向SMF网元发送通知消息。
其中，该通知消息用于告知SMF网元在多播/广播业务的作用区域(即第一业务区域)内，终端设备加入该多播/广播业务，以便于SMF网元后续确定多播/广播业务传输类型并触发激活相应的用户面资源。
其中，通知消息可以包含终端设备的标识，多播/广播业务的标识，以及终端设备支持的多播/广播接入类型。
相应地，SMF网元接收AMF网元发送的通知消息。
步骤S1404可以与前文实施例的方法900中的步骤S930对应。
S1405，AMF网元向终端设备发送的注册响应消息。
其中，注册响应消息可以是注册请求消息的响应消息，也称为注册接受消息。
其中，注册响应消息包含S1403中分配的注册区域的信息。
相应地，终端设备接收AMF网元发送的注册响应消息。
S1406，当接收到AMF网元在S1404中发送的通知消息后，并且在SMF网元确定采用共享链路传输方式时，SMF网元确定多播/广播传输类型。
示例性的，上述确定的方式可以是：判断该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量与预设值的关系。
当该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量大于或等于(或者大于)预设值时，SMF网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型，例如为以下一种或多种：NR系统的多播/广播、MBSFN的多播/广播或SCPTM的多播/广播。
步骤S1406可以与前文实施例的方法800中的步骤S820对应。
S1407，SMF网元触发UPF网元和RAN网元激活S1406中确定的多播/广播传输类型对应的用户面资源。
步骤S1407可以与前文实施例的方法800中的步骤S830对应。
S1408，在用户面资源建立好后进行多播/广播业务传输。
示例性的，RAN网元可以通过建立的用户面资源将多播/广播业务的数据发送至终端设备。
其中，S1403和S1405，与S1404和S1406至S1408可以并行执行。
当终端设备移出当前的注册区域时，会触发移动类型的注册请求过程，执行S1409至S1415，与S1402至S1408类似，不再赘述。
本实施例通过将终端设备的注册区域与多播/广播的作用区域结合，可以保证终端设备在移出多播/广播的作用区域时得以及时通知网络侧。终端设备在接入网络时，通过NAS消息将加入的群组信息和多播/广播的能力告知网络侧，方便网络侧对终端设备的数量进行统计。
图15是本申请实施例提供的又一种多播/广播业务传输的方法1500的示意性流程图。如图15所示，方法1500包括以下步骤。
S1501，SMF网元向AMF网元发送订阅消息。
其中，该订阅消息包含第一业务区域的信息和多播/广播业务的标识。
其中，多播/广播业务的标识可以为群组标识(group ID)或多播/广播标识。该订阅消息不是针对某个终端设备的，而是针对第一业务区域内的所有属于该多播/广播业务(通过多播/广播业务的标识来标识)对应的群组的终端设备。
相应地，AMF网元接收SMF网元发送的订阅消息。
步骤S1501可以与前文实施例的方法900中的步骤S910对应。
S1502，当终端设备接入到网络时，终端设备向AMF网元发送注册请求消息。
其中，注册请求消息中包含终端设备支持的多播/广播接入类型，以及其订阅的多播/广播业务的标识。
示例性地，AMF网元通过多播/广播业务的标识可以获知终端设备加入了哪一个多播/广播业务。即，AMF网元通过终端设备提供的多播/广播业务的标识可以找到多播/广播业务的标识所对应的业务区域，即第一业务区域。
此外，AMF网元可以存储终端设备的多播/广播业务的标识和终端设备支持的多播/广播接入类型，以方便后续步骤(例如步骤S1504)使用。
相应地，AMF网元接收终端设备发送的注册请求消息。注册请求消息可认为是第一请求消息。
步骤S1502可以与前文实施例的方法900中的步骤S920以及前文实施例的方法1100中的步骤S1120对应。
S1503，AMF网元向终端设备发送的注册响应消息。
其中，注册响应消息为注册请求消息的响应消息，也称为注册接受消息。
此外，注册响应消息包含注册区域的信息，还包含第一业务区域的信息，即多播/广播业务的作用区域的信息。
相应地，终端设备接收AMF网元发送的注册响应消息。
S1504，AMF网元向SMF网元发送通知消息。
其中，该通知消息用于告知SMF网元在多播/广播业务的作用区域(即第一业务区域)内，终端设备加入该多播/广播业务，以便于SMF网元后续确定多播/广播业务传输类型并触发激活相应的用户面资源。
其中，通知消息可以包含终端设备的标识，多播/广播业务的标识，以及终端设备支持的多播/广播接入类型。
相应地，SMF网元接收AMF网元发送的通知消息。
步骤S1504可以与前文实施例的方法900中的步骤S930对应。
S1505，当接收到AMF网元在S1204中发送的通知消息后，并且在SMF网元确定采用共享链路传输方式时，SMF网元确定多播/广播传输类型。
例如，该传输发送为多链路传输方式或共享链路传输方式。
示例性的，上述确定的方式可以是：判断该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量与预设值的关系。
当该第一业务区域内该多播/广播业务对应的群组中的终端设备的数量大于或等于(或者大于)预设值时，SMF网元根据该终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型，例如为以下一种或多种：NR系统的多播/广播、MBSFN的多播/广播或SCPTM的多播/广播。
步骤S1505可以与前文实施例的方法800中的步骤S820对应。
S1506，SMF网元触发UPF网元和RAN网元激活S1505中确定的多播/广播传输类型对应的用户面资源。
步骤S1506可以与前文实施例的方法800中的步骤S830对应。
S1507，在用户面资源建立好后进行多播/广播业务传输。
示例性的，RAN网元可以通过建立的用户面资源将多播/广播业务的数据发送至终端设备。
其中，S1503，与S1504至S1507可以并行执行。
当终端设备移出当前的第一业务区域时，会触发移动类型(移出当前的业务区域)的注册请求过程，执行S1508至S1513，与S1502至S1507类似，不再赘述。
与方法1400相比，方法1500中，AMF网元不再考虑第一业务区域设置注册区域，而是直接将第一业务区域的信息发送给终端设备，当终端设备移出当前的第一业务区域时，会触发移动类型(移出当前的业务区域)的注册请求过程。
本实施例通过将多播/广播的作用区域(第一业务区域)告知给终端设备，可以保证终端设备在移出多播/广播的作用区域时得以及时通知网络侧。终端设备在接入网络时，通过NAS消息将加入的群组信息和多播/广播的能力告知网络侧，方便网络侧对终端设备的数量进行统计。
以上结合图1至图15详细说明了本申请的多播/广播业务传输的方法，下面结合图16至图23详细说明本申请的核心网网元和终端设备。
图16是本申请实施例提供的一种核心网网元1600的示意性框图。如图16所示，核心网网元1600可以包括：
获取模块1610，用于获取位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；
确定模块1620，用于根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型；
发送模块1630，用于通知所述多播/广播业务对应的接入网网元采用所述多播/广播传输类型传输所述多播/广播业务的数据。
本申请实施例的核心网网元，获取多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，并根据终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第 一业务区域内的多播/广播传输类型，并通知接入网网元，由此核心网网元可以确定具体基于何种RAT进行多播/广播传输，能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，确定模块1620具体可以用于：当所述第一业务区域内所述多播/广播业务对应的群组中的终端设备的数量大于或等于预设值时，根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型。
可选地，在上述实施例的一种实施场景中，获取模块1610还可以用于：从第二核心网网元接收所述终端设备的位置信息；确定模块1620还可以用于：根据所述终端设备的位置信息，确定所述多播/广播业务的第二业务区域，所述第二业务区域位于所述第一业务区域内；发送模块1630还可以用于：向所述第二核心网网元发送所述第二业务区域的信息以及所述多播/广播业务的标识。
可选地，在上述实施例的一种实施场景中，发送模块1630还可以用于：向统一数据管理UDM网元请求所述终端设备支持的多播/广播接入类型；获取模块1610具体可以用于：接收来自所述UDM网元的所述终端设备支持的多播/广播接入类型。
可选地，在上述实施例的一种实施场景中，发送模块1630还可以用于：向第二核心网网元发送订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；获取模块1610具体可以用于：接收来自所述第二核心网网元的通知消息，所述通知消息包含满足所述预设条件的终端设备支持的多播/广播接入类型。
可选地，在上述实施例的一种实施场景中，所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备；或者，所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识，所述满足预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。
可选地，在上述实施例的一种实施场景中，当所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备时，获取模块1610还可以用于：根据所述满足所述预设条件的终端设备支持的多播/广播接入类型，获取所述位于所述第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型。
图17是本申请实施例提供的另一种核心网网元1700的示意性框图。如图17所示，核心网网元1700可以包括处理器1710和存储器1720，所述存储器1720中存储有计算机指令，所述处理器1710执行所述计算机指令时，使得所述核心网网元1700执行以下步骤：获取位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型；通知所述多播/广播业务对应的接入网网元采用所述多播/广播传输类型传输所述多播/广播业务的数据。
本申请实施例的核心网网元，获取多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，并根据终端设备支持的多播/广播接入类型，确定该多播/广播业务在该第一业务区域内的多播/广播传输类型，并通知接入网网元，由此核心网网元可以确定具体 基于何种RAT进行多播/广播传输，能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，所述处理器1710执行所述计算机指令，使得所述核心网网元1700具体执行以下步骤：当所述第一业务区域内所述多播/广播业务对应的群组中的终端设备的数量大于或等于预设值时，根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型。
可选地，在上述实施例的一种实施场景中，所述处理器1710还用于执行所述计算机指令，使得所述核心网网元1700还执行以下步骤：从第二核心网网元接收所述终端设备的位置信息；根据所述终端设备的位置信息，确定所述多播/广播业务的第二业务区域，所述第二业务区域位于所述第一业务区域内；向所述第二核心网网元发送所述第二业务区域的信息以及所述多播/广播业务的标识。
可选地，在上述实施例的一种实施场景中，所述处理器1710执行所述计算机指令，使得所述核心网网元1700具体执行以下步骤：向统一数据管理UDM网元请求所述终端设备支持的多播/广播接入类型；接收来自所述UDM网元的所述终端设备支持的多播/广播接入类型。
可选地，在上述实施例的一种实施场景中，所述处理器1710执行所述计算机指令，使得所述核心网网元1700具体执行以下步骤：向第二核心网网元发送订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；接收来自所述第二核心网网元的通知消息，所述通知消息包含满足所述预设条件的终端设备支持的多播/广播接入类型。
可选地，在上述实施例的一种实施场景中，所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备；或者，所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识，所述满足预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。
可选地，在上述实施例的一种实施场景中，当所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备时，所述处理器1710还用于执行所述计算机指令，使得所述核心网网元1700还执行以下步骤：根据所述满足所述预设条件的终端设备支持的多播/广播接入类型，获取所述位于所述第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型。
可选地，核心网网元1700还可以包括收发器，用于接收(获取)或发送数据。
应理解，图16所示的核心网网元1600或图17所示的核心网网元1700，可用于执行上述方法实施例中第一核心网网元的操作或流程，并且核心网网元1600或核心网网元1700中的各个模块和器件的操作和/或功能分别为了实现上述方法实施例中第一核心网网元的相应流程，为了简洁，此处不再赘述。
图18是本申请实施例提供的又一种核心网网元1800的示意性框图。如图18所示，核心网网元1800可以包括：
接收模块1810，用于接收来自第一核心网网元的订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；
接收模块1810还用于接收来自第一终端设备的所述第一终端设备支持的多播/广播接入类型，所述第一终端设备满足所述预设条件；
发送模块1820，用于向所述第一核心网网元发送通知消息，所述通知消息包含所述第一终端设备支持的多播/广播接入类型。
本申请实施例的核心网网元接收第一核心网网元订阅满足预设条件的终端设备支持的多播/广播接入类型的订阅消息，从第一终端设备接收终端设备支持的多播/广播接入类型，并通知第一核心网网元该第一终端设备支持的多播/广播接入类型，由此向第一核心网网元提供用于确定具体基于何种RAT进行多播/广播传输所需的终端设备的能力的信息，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，所述订阅消息包含多播/广播业务的第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备；或者，所述订阅消息包含多播/广播业务的第一业务区域的信息和所述多播/广播业务的标识，所述满足预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。
可选地，在上述实施例的一种实施场景中，接收模块1810还可以用于接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册；核心网网元1800还可以包括确定模块1830，用于根据所述第一请求消息，确定所述第一终端设备满足所述预设条件。
可选地，在上述实施例的一种实施场景中，所述第一请求消息包含所述多播/广播业务的标识，所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识；确定模块1830具体可以用于：根据所述多播/广播业务的标识和所述第一终端设备位于所述第一业务区域内，确定所述第一终端设备满足所述预设条件。
可选地，在上述实施例的一种实施场景中，接收模块1810具体可以用于：接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册，所述第一请求消息包含所述第一终端设备支持的多播/广播接入类型。
可选地，在上述实施例的一种实施场景中，发送模块1820还可以用于向所述第一终端设备发送所述第一终端设备的注册区域的信息；其中，所述注册区域位于所述第一业务区域内，或所述注册区域与所述第一业务区域没有交集。
可选地，在上述实施例的一种实施场景中，所述第一终端设备的注册区域的信息携带在所述第一请求消息的响应消息中。
可选地，在上述实施例的一种实施场景中，发送模块1820还可以用于向所述第一终端设备发送所述第一业务区域的信息。
可选地，在上述实施例的一种实施场景中，所述第一业务区域的信息携带在所述第一请求消息的响应消息中。
可选地，在上述实施例的一种实施场景中，发送模块1820还可以用于向所述第一核心网网元发送所述第一终端设备的位置信息；接收模块1810还可以用于接收来自所述第一核心网网元的所述多播/广播业务的第二业务区域的信息，以及所述多播/广播业务的标识，所述第二业务区域位于所述第一业务区域内；发送模块1820还可以用于向所述第一 终端设备发送所述第二业务区域的信息，以及所述多播/广播业务的标识。
图19是本申请实施例提供的又一种核心网网元1900的示意性框图。如图19所示，核心网网元1900可以包括处理器1910和存储器1920，所述存储器1920中存储有计算机指令，所述处理器1910执行所述计算机指令时，使得所述核心网网元1900执行以下步骤：接收来自第一核心网网元的订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；接收来自第一终端设备的所述第一终端设备支持的多播/广播接入类型，所述第一终端设备满足所述预设条件；向所述第一核心网网元发送通知消息，所述通知消息包含所述第一终端设备支持的多播/广播接入类型。
本申请实施例的核心网网元接收第一核心网网元订阅满足预设条件的终端设备支持的多播/广播接入类型的订阅消息，从第一终端设备接收终端设备支持的多播/广播接入类型，并通知第一核心网网元该第一终端设备支持的多播/广播接入类型，由此向第一核心网网元提供用于确定具体基于何种RAT进行多播/广播传输所需的终端设备的能力的信息，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，所述订阅消息包含多播/广播业务的第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备；或者，所述订阅消息包含多播/广播业务的第一业务区域的信息和所述多播/广播业务的标识，所述满足预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。
可选地，在上述实施例的一种实施场景中，所述处理器1910还用于执行所述计算机指令，使得所述核心网网元1900还执行以下步骤：接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册；根据所述第一请求消息，确定所述第一终端设备满足所述预设条件。
可选地，在上述实施例的一种实施场景中，所述第一请求消息包含所述多播/广播业务的标识，所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识；所述处理器1910执行所述计算机指令，使得所述核心网网元1900具体执行以下步骤：根据所述多播/广播业务的标识和所述第一终端设备位于所述第一业务区域内，确定所述第一终端设备满足所述预设条件。
可选地，在上述实施例的一种实施场景中，所述处理器1910执行所述计算机指令，使得所述核心网网元1900具体执行以下步骤：接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册，所述第一请求消息包含所述第一终端设备支持的多播/广播接入类型。
可选地，在上述实施例的一种实施场景中，所述处理器1910还用于执行所述计算机指令，使得所述核心网网元1900还执行以下步骤：向所述第一终端设备发送所述第一终端设备的注册区域的信息；其中，所述注册区域位于所述第一业务区域内，或所述注册区域与所述第一业务区域没有交集。
可选地，在上述实施例的一种实施场景中，所述第一终端设备的注册区域的信息携带在所述第一请求消息的响应消息中。
可选地，在上述实施例的一种实施场景中，所述处理器1910还用于执行所述计算机 指令，使得所述核心网网元1900还执行以下步骤：向所述第一终端设备发送所述第一业务区域的信息。
可选地，在上述实施例的一种实施场景中，所述第一业务区域的信息携带在所述第一请求消息的响应消息中。
可选地，在上述实施例的一种实施场景中，所述处理器1910还用于执行所述计算机指令，使得所述核心网网元1900还执行以下步骤：向所述第一核心网网元发送所述第一终端设备的位置信息；接收来自所述第一核心网网元的所述多播/广播业务的第二业务区域的信息，以及所述多播/广播业务的标识，所述第二业务区域位于所述第一业务区域内；向所述第一终端设备发送所述第二业务区域的信息，以及所述多播/广播业务的标识。
可选地，核心网网元1900还可以包括收发器，用于接收(获取)或发送数据。
应理解，图18所示的核心网网元1800或图19所示的核心网网元1900，可用于执行上述方法实施例中第二核心网网元的操作或流程，并且核心网网元1800或核心网网元1900中的各个模块和器件的操作和/或功能分别为了实现上述方法实施例中第二核心网网元的相应流程，为了简洁，此处不再赘述。
图20是本申请实施例提供的一种终端设备2000的示意性框图。如图20所示，终端设备2000包括：
获取模块2010，用于获取所述终端设备2000所支持的多播/广播接入类型；
发送模块2020，用于向第二核心网网元发送所述终端设备2000所支持的多播广播接入类型。
本申请实施例的终端设备，向核心网网元上报终端设备所支持的多播/广播接入类型，以便于核心网网元根据终端设备支持的多播/广播接入类型确定具体基于何种RAT进行多播/广播传输，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，所述终端设备2000所支持的多播广播接入类型携带在第一请求消息中，所述第一请求消息用于请求对所述终端设备2000注册。
可选地，在上述实施例的一种实施场景中，发送模块2020还用于向所述第二核心网网元发送第一请求消息，所述第一请求消息用于请求对所述终端设备2000注册。
可选地，在上述实施例的一种实施场景中，所述第一请求消息包含所述终端设备2000所属群组对应的多播/广播业务的标识。
可选地，在上述实施例的一种实施场景中，终端设备2000还可以包括接收模块2030，用于接收来自所述第二核心网网元的所述多播/广播业务的第一业务区域的信息；发送模块2020还用于当所述终端设备2000移出所述第一业务区域时，向所述第二核心网网元发送第一请求消息。
图21是本申请实施例提供的另一种终端设备2100的示意性框图。如图21所示，终端设备2100包括处理器2110和存储器2120，所述存储器2120中存储有计算机指令，所述处理器2110执行所述计算机指令时，使得所述终端设备2100执行以下步骤：获取所述终端设备2100所支持的多播/广播接入类型；向第二核心网网元发送所述终端设备2100所支持的多播广播接入类型。
可选地，在上述实施例的一种实施场景中，所述终端设备2100所支持的多播广播接 入类型携带在第一请求消息中，所述第一请求消息用于请求对所述终端设备2100注册。
可选地，在上述实施例的一种实施场景中，所述处理器2110还用于执行所述计算机指令，使得所述终端设备2100还执行以下步骤：向所述第二核心网网元发送第一请求消息，所述第一请求消息用于请求对所述终端设备2100注册。
可选地，在上述实施例的一种实施场景中，所述第一请求消息包含所述终端设备2100所属群组对应的多播/广播业务的标识。
可选地，在上述实施例的一种实施场景中，所述处理器2110还用于执行所述计算机指令，使得所述终端设备2100还执行以下步骤：接收来自所述第二核心网网元的所述多播/广播业务的第一业务区域的信息；当所述终端设备2100移出所述第一业务区域时，向所述第二核心网网元发送第一请求消息。
可选地，终端设备2100还可以包括收发器，用于接收(获取)或发送数据。
应理解，图20所示的终端设备2000或图21所示的终端设备2100，可用于执行上述方法实施例中终端设备的操作或流程，并且终端设备2000或终端设备2100中的各个模块和器件的操作和/或功能分别为了实现上述方法实施例中终端设备的相应流程，为了简洁，此处不再赘述。
图22是本申请实施例提供的又一种核心网网元2200的示意性框图。如图22所示，核心网网元2200可以包括：
接收模块2210，用于接收来自第一核心网网元的第二请求消息，所述第二请求消息用于请求位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；
发送模块2220，用于向所述第一核心网网元发送所述终端设备所支持的多播广播接入类型。
本申请实施例的核心网网元接收第一核心网网元请求终端设备支持的多播/广播接入类型的第二请求消息，向第一核心网网元发生终端设备支持的多播/广播接入类型，由此向第一核心网网元提供用于确定具体基于何种RAT进行多播/广播传输所需的终端设备的能力的信息，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，所述第二请求消息包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备的列表。
可选地，在上述实施例的一种实施场景中，接收模块2210还可以用于接收来自第二核心网网元的位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备支持的多播广播接入类型。
图23是本申请实施例提供的又一种核心网网元2300的示意性框图。如图23所示，核心网网元2300可以包括处理器2310和存储器2320，所述存储器2320中存储有计算机指令，所述处理器2310执行所述计算机指令时，使得所述核心网网元2300执行以下步骤：接收来自第一核心网网元的第二请求消息，所述第二请求消息用于请求位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；向所述第一核心网网元发送所述终端设备所支持的多播广播接入类型。
本申请实施例的核心网网元接收第一核心网网元请求终端设备支持的多播/广播接入 类型的第二请求消息，向第一核心网网元发生终端设备支持的多播/广播接入类型，由此向第一核心网网元提供用于确定具体基于何种RAT进行多播/广播传输所需的终端设备的能力的信息，使得多播/广播传输能够更好地适应5G移动通信系统中终端设备支持多种RAT的情况，可以提高多播/广播传输的效率。
可选地，在上述实施例的一种实施场景中，所述第二请求消息包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备的列表。
可选地，在上述实施例的一种实施场景中，所述处理器2310还用于执行所述计算机指令，使得所述核心网网元2300还执行以下步骤：接收来自第二核心网网元的位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备支持的多播广播接入类型。
可选地，核心网网元2300还可以包括收发器，用于接收(获取)或发送数据。
应理解，图22所示的核心网网元2200或图23所示的核心网网元2300，可用于执行上述方法实施例中第三核心网网元的操作或流程，并且核心网网元2200或核心网网元2200中的各个模块和器件的操作和/或功能分别为了实现上述方法实施例中第三核心网网元的相应流程，为了简洁，此处不再赘述。
应理解，本申请实施例中提及的处理器可以包括中央处理器(central processing pnit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic Device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
还应理解，本申请实施例中提及的存储器可以是易失性存储器(volatile memory)或非易失性存储器(non-volatile memory)，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、快闪存储器(flash memory)、硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供一种计算机可读存储介质，其上存储有指令，当所述指令在计算 机上运行时，使得所述计算机执行上述方法实施例的由第一核心网网元执行的步骤。
本申请实施例还提供一种计算机可读存储介质，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行上述方法实施例的由第二核心网网元执行的步骤。
本申请实施例还提供一种计算机可读存储介质，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行上述方法实施例的由第三核心网网元执行的步骤。
本申请实施例还提供一种计算机可读存储介质，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行上述方法实施例的由终端设备执行的步骤。
本申请实施例还提供一种包括指令的计算机程序产品，其特征在于，当计算机运行所述计算机程序产品的所述指时，所述计算机执行上述方法实施例的由第一核心网网元执行的步骤。
本申请实施例还提供一种包括指令的计算机程序产品，其特征在于，当计算机运行所述计算机程序产品的所述指时，所述计算机执行上述方法实施例的由第二核心网网元执行的步骤。
本申请实施例还提供一种包括指令的计算机程序产品，其特征在于，当计算机运行所述计算机程序产品的所述指时，所述计算机执行上述方法实施例的由第三核心网网元执行的步骤。
本申请实施例还提供一种包括指令的计算机程序产品，其特征在于，当计算机运行所述计算机程序产品的所述指时，所述计算机执行上述方法实施例的由终端设备执行的步骤。
本申请实施例还提供一种计算机芯片，该计算机芯片使得计算机执行上述方法实施例的由第一核心网网元执行的步骤。
本申请实施例还提供一种计算机芯片，该计算机芯片使得计算机执行上述方法实施例的由第二核心网网元执行的步骤。
本申请实施例还提供一种计算机芯片，该计算机芯片使得计算机执行上述方法实施例的由第三核心网网元执行的步骤。
本申请实施例还提供一种计算机芯片，该计算机芯片使得计算机执行上述方法实施例的由终端设备执行的步骤。
本申请实施例提供给的设备或网元，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体 介质(例如，SSD)等。
应理解，本文中涉及的第一、第二、第三以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (30)

  1. 一种多播/广播业务传输的方法，其特征在于，包括：
    第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；
    所述第一核心网网元根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型；
    所述第一核心网网元通知所述多播/广播业务对应的接入网网元采用所述多播/广播传输类型传输所述多播/广播业务的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一核心网网元根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型，包括：
    当所述第一业务区域内所述多播/广播业务对应的群组中的终端设备的数量大于或等于预设值时，所述第一核心网网元根据所述终端设备支持的多播/广播接入类型，确定所述多播/广播业务在所述第一业务区域内的多播/广播传输类型。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一核心网网元从第二核心网网元接收所述终端设备的位置信息；
    所述第一核心网网元根据所述终端设备的位置信息，确定所述多播/广播业务的第二业务区域，所述第二业务区域位于所述第一业务区域内；
    所述第一核心网网元向所述第二核心网网元发送所述第二业务区域的信息以及所述多播/广播业务的标识。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，包括：
    所述第一核心网网元向统一数据管理UDM网元请求所述终端设备支持的多播/广播接入类型；
    所述第一核心网网元接收来自所述UDM网元的所述终端设备支持的多播/广播接入类型。
  5. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一核心网网元获取位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型，包括：
    所述第一核心网网元向第二核心网网元发送订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；
    所述第一核心网网元接收来自所述第二核心网网元的通知消息，所述通知消息包含满足所述预设条件的终端设备支持的多播/广播接入类型。
  6. 根据权利要求5所述的方法，其特征在于，所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备；或者，
    所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识，所述满足 预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。
  7. 根据权利要求6所述的方法，其特征在于，当所述订阅消息包含所述第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备时，所述方法还包括：
    所述第一核心网网元根据所述满足所述预设条件的终端设备支持的多播/广播接入类型，获取所述位于所述第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型。
  8. 一种多播/广播业务传输的方法，其特征在于，所述方法包括：
    第二核心网网元接收来自第一核心网网元的订阅消息，所述订阅消息用于订阅满足预设条件的终端设备支持的多播/广播接入类型；
    所述第二核心网网元接收来自第一终端设备的所述第一终端设备支持的多播/广播接入类型，所述第一终端设备满足所述预设条件；
    所述第二核心网网元向所述第一核心网网元发送通知消息，所述通知消息包含所述第一终端设备支持的多播/广播接入类型。
  9. 根据权利要求8所述的方法，其特征在于，所述订阅消息包含多播/广播业务的第一业务区域的信息，所述满足预设条件的终端设备包括位于所述第一业务区域内的终端设备；或者，
    所述订阅消息包含多播/广播业务的第一业务区域的信息和所述多播/广播业务的标识，所述满足预设条件的终端设备包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的终端设备。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第二核心网网元接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册；
    所述第二核心网网元根据所述第一请求消息，确定所述第一终端设备满足所述预设条件。
  11. 根据权利要求10所述的方法，其特征在于，所述第一请求消息包含所述多播/广播业务的标识，所述订阅消息包含所述第一业务区域的信息和所述多播/广播业务的标识；
    所述第二核心网网元根据所述第一请求消息，确定所述第一终端设备满足所述预设条件，包括：
    所述第二核心网网元根据所述多播/广播业务的标识和所述第一终端设备位于所述第一业务区域内，确定所述第一终端设备满足所述预设条件。
  12. 根据权利要求8或9所述的方法，其特征在于，所述第二核心网网元接收来自第一终端设备的所述第一终端设备支持的多播/广播接入类型，包括：
    所述第二核心网网元接收来自所述第一终端设备的第一请求消息，所述第一请求消息用于请求对所述第一终端设备注册，所述第一请求消息包含所述第一终端设备支持的多播/广播接入类型。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二核心网网元向所述第一终端设备发送所述第一终端设备的注册区域的信息；
    其中，所述注册区域位于所述第一业务区域内，或所述注册区域与所述第一业务区域没有交集。
  14. 根据权利要求13所述的方法，其特征在于，所述第一终端设备的注册区域的信息携带在所述第一请求消息的响应消息中。
  15. 根据权利要求9至12中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二核心网网元向所述第一终端设备发送所述第一业务区域的信息。
  16. 根据权利要求15所述的方法，其特征在于，所述第一业务区域的信息携带在所述第一请求消息的响应消息中。
  17. 根据权利要求8至16中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二核心网网元向所述第一核心网网元发送所述第一终端设备的位置信息；
    所述第二核心网网元接收来自所述第一核心网网元的所述多播/广播业务的第二业务区域的信息，以及所述多播/广播业务的标识，所述第二业务区域位于所述第一业务区域内；
    所述第二核心网网元向所述第一终端设备发送所述第二业务区域的信息，以及所述多播/广播业务的标识。
  18. 一种多播/广播业务传输的方法，其特征在于，包括：
    终端设备获取所述终端设备所支持的多播/广播接入类型；
    所述终端设备向第二核心网网元发送所述终端设备所支持的多播广播接入类型。
  19. 根据权利要求18所述的方法，其特征在于，所述终端设备所支持的多播广播接入类型携带在第一请求消息中，所述第一请求消息用于请求对所述终端设备注册。
  20. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述第二核心网网元发送第一请求消息，所述第一请求消息用于请求对所述终端设备注册。
  21. 根据权利要求19或20所述的方法，其特征在于，所述第一请求消息包含所述终端设备所属群组对应的多播/广播业务的标识。
  22. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收来自所述第二核心网网元的所述多播/广播业务的第一业务区域的信息；
    当所述终端设备移出所述第一业务区域时，所述终端设备向所述第二核心网网元发送第一请求消息。
  23. 一种多播/广播业务传输的方法，其特征在于，包括：
    第三核心网网元接收来自第一核心网网元的第二请求消息，所述第二请求消息用于请求位于多播/广播业务的第一业务区域内，且属于所述多播/广播业务对应的群组的终端设备支持的多播/广播接入类型；
    所述第三核心网网元向所述第一核心网网元发送所述终端设备所支持的多播广播接入类型。
  24. 根据权利要求23所述的方法，其特征在于，所述第二请求消息包括位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备的列表。
  25. 根据权利要求23或24所述的方法，其特征在于，所述方法还包括：
    所述第三核心网网元接收来自第二核心网网元的位于所述第一业务区域内且属于所述多播/广播业务对应的群组的所述终端设备支持的多播广播接入类型。
  26. 根据权利要求1至25中任一项所述的方法，其特征在于，所述多播/广播传输类型包括以下一种或多种：新空口NR系统的多播/广播、多播/组播单频网络MBSFN的多播/广播或单小区点对多点SCPTM的多播/广播。
  27. 一种核心网网元，其特征在于，包括处理器和存储器，所述存储器中存储有计算机指令，所述处理器执行所述计算机指令时，使得所述核心网网元执行权利要求1至7中任一项所述的方法。
  28. 一种核心网网元，其特征在于，包括处理器和存储器，所述存储器中存储有计算机指令，所述处理器执行所述计算机指令时，使得所述核心网网元执行权利要求8至17中任一项所述的方法。
  29. 一种终端设备，其特征在于，所述终端设备包括处理器和存储器，所述存储器中存储有计算机指令，所述处理器执行所述计算机指令时，使得所述终端设备执行权利要求18至22中任一项所述的方法。
  30. 一种核心网网元，其特征在于，包括处理器和存储器，所述存储器中存储有计算机指令，所述处理器执行所述计算机指令时，使得所述核心网网元执行权利要求23至25中任一项所述的方法。
PCT/CN2019/105586 2018-09-30 2019-09-12 多播/广播业务传输的方法、核心网网元和终端设备 WO2020063362A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP19867972.2A EP3849219A4 (en) 2018-09-30 2019-09-12 BROADCASTING / MULTI-BROADCASTING SERVICE TRANSMISSION PROCESS, NETWORK CORE ELEMENT AND TERMINAL DEVICE
PCT/CN2019/105586 WO2020063362A1 (zh) 2018-09-30 2019-09-12 多播/广播业务传输的方法、核心网网元和终端设备
US17/215,754 US20210219106A1 (en) 2018-09-30 2021-03-29 Multicast/broadcast service transmission method, core network element, and terminal device

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201811159996.5A CN110972078A (zh) 2018-09-30 2018-09-30 多播/广播业务传输的方法、核心网网元和终端设备
CN201811159996.5 2018-09-30
PCT/CN2019/105586 WO2020063362A1 (zh) 2018-09-30 2019-09-12 多播/广播业务传输的方法、核心网网元和终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/215,754 Continuation US20210219106A1 (en) 2018-09-30 2021-03-29 Multicast/broadcast service transmission method, core network element, and terminal device

Publications (1)

Publication Number Publication Date
WO2020063362A1 true WO2020063362A1 (zh) 2020-04-02

Family

ID=69953288

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/105586 WO2020063362A1 (zh) 2018-09-30 2019-09-12 多播/广播业务传输的方法、核心网网元和终端设备

Country Status (4)

Country Link
US (1) US20210219106A1 (zh)
EP (1) EP3849219A4 (zh)
CN (1) CN110972078A (zh)
WO (1) WO2020063362A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021197469A1 (zh) * 2020-04-03 2021-10-07 维沃移动通信有限公司 传输通道变更方法、接入网设备及核心网设备
CN113498138A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 通信方法和通信装置
WO2022001671A1 (zh) * 2020-06-30 2022-01-06 华为技术有限公司 通信方法及装置
CN115175255A (zh) * 2021-04-01 2022-10-11 华为技术有限公司 一种多播广播业务的传输切换方法及装置
WO2022241691A1 (zh) * 2021-05-19 2022-11-24 华为技术有限公司 一种组播/广播通信方法和装置
EP4156726A1 (en) * 2020-05-22 2023-03-29 LG Electronics, Inc. Multicast-related communication
EP4131850A4 (en) * 2020-04-03 2023-08-09 Vivo Mobile Communication Co., Ltd. SERVICE TRANSMISSION METHOD, SERVICE TRANSMISSION MODE CONFIGURATION METHOD AND ASSOCIATED DEVICE
EP4254993A4 (en) * 2020-12-31 2023-12-13 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND COMMUNICATION DEVICE

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020002374A1 (en) * 2018-06-26 2020-01-02 Huawei Technologies Co., Ltd. Entities and methods for providing multicast/broadcast services in 5g networks
CN113518433B (zh) * 2020-04-09 2023-08-18 成都鼎桥通信技术有限公司 资源管理方法、装置及设备
JP2023528138A (ja) * 2020-04-10 2023-07-04 オッポ広東移動通信有限公司 セッション処理方法、デバイス及び記憶媒体
WO2021208059A1 (zh) * 2020-04-17 2021-10-21 Oppo广东移动通信有限公司 连接建立方法、装置、设备及存储介质
CN113556689B (zh) * 2020-04-24 2022-09-23 大唐移动通信设备有限公司 一种传输方式上报方法、装置、设备及电子介质
CN111526552B (zh) * 2020-05-13 2024-02-02 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
WO2021232998A1 (en) * 2020-05-22 2021-11-25 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for handling multicast broadcast service
CN113709677B (zh) * 2020-05-22 2023-04-11 大唐移动通信设备有限公司 加入组播广播业务mbs会话的方法及装置
CN115776646B (zh) 2020-06-04 2023-09-01 华为技术有限公司 适用于多链路的组播业务传输方法及装置
CN113891340B (zh) * 2020-07-02 2023-10-27 中国移动通信集团安徽有限公司 自适应流控方法、装置、计算设备和存储介质
US11595988B2 (en) * 2020-08-12 2023-02-28 Samsung Electronics Co., Ltd. Method and device for providing local MBS in wireless communication system
CN114079870B (zh) * 2020-08-13 2023-06-02 华为技术有限公司 通信方法及装置
CN112073919B (zh) * 2020-09-08 2024-03-01 腾讯科技（深圳）有限公司 多播广播业务的通信方法及装置、电子设备、存储介质
CN114554624A (zh) * 2020-11-25 2022-05-27 维沃移动通信有限公司 通信指示方法、装置及网络侧设备
CN115396823A (zh) * 2021-05-19 2022-11-25 华为技术有限公司 一种传输业务数据的方法和通信装置
CN113490155B (zh) * 2021-07-01 2023-04-07 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、介质及电子设备
CN113490156B (zh) * 2021-07-01 2024-03-12 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、介质及电子设备
CN115955649A (zh) * 2021-10-08 2023-04-11 维沃移动通信有限公司 多播业务处理方法、装置及网络设备
CN113891326B (zh) * 2021-10-15 2023-06-06 中国联合网络通信集团有限公司 一种业务传输方法、装置及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104284299A (zh) * 2013-07-09 2015-01-14 中兴通讯股份有限公司 集群多播决策方法、集群终端及集群服务器
CN105376717A (zh) * 2014-08-25 2016-03-02 中兴通讯股份有限公司 建立lte集群通信承载的方法、用户设备及第一网元设备
US20170290014A1 (en) * 2016-03-30 2017-10-05 Samsung Electronics Co., Ltd Method and apparatus for transmitting signal in wireless communication

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101981953A (zh) * 2008-01-29 2011-02-23 夏普株式会社 通信设备、通信方法
CN102378148B (zh) * 2010-08-23 2016-06-01 中兴通讯股份有限公司 终端、hss、及核心网网元获知终端能力的方法和系统
US10771929B2 (en) * 2016-03-18 2020-09-08 Lg Electronics Inc. Method and apparatus for performing V2X communication on basis of cell group information
WO2018175974A1 (en) * 2017-03-24 2018-09-27 Intel Corporation Systems and methods for group based services provisioning
CN115361657B (zh) * 2018-01-03 2023-09-01 交互数字专利控股公司 用于IoT应用的5G网络中的多播和广播服务

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104284299A (zh) * 2013-07-09 2015-01-14 中兴通讯股份有限公司 集群多播决策方法、集群终端及集群服务器
CN105376717A (zh) * 2014-08-25 2016-03-02 中兴通讯股份有限公司 建立lte集群通信承载的方法、用户设备及第一网元设备
US20170290014A1 (en) * 2016-03-30 2017-10-05 Samsung Electronics Co., Ltd Method and apparatus for transmitting signal in wireless communication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"5G Broadcast Requirements Analysis for LTE", 3GPP TSG RAN WG1 MEETING #94BIS R1-1811318, 29 September 2018 (2018-09-29), XP051518721 *
See also references of EP3849219A4 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021197469A1 (zh) * 2020-04-03 2021-10-07 维沃移动通信有限公司 传输通道变更方法、接入网设备及核心网设备
EP4131850A4 (en) * 2020-04-03 2023-08-09 Vivo Mobile Communication Co., Ltd. SERVICE TRANSMISSION METHOD, SERVICE TRANSMISSION MODE CONFIGURATION METHOD AND ASSOCIATED DEVICE
CN113498138A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 通信方法和通信装置
CN113498138B (zh) * 2020-04-07 2023-07-07 华为技术有限公司 通信方法和通信装置
EP4156726A1 (en) * 2020-05-22 2023-03-29 LG Electronics, Inc. Multicast-related communication
WO2022001671A1 (zh) * 2020-06-30 2022-01-06 华为技术有限公司 通信方法及装置
EP4254993A4 (en) * 2020-12-31 2023-12-13 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND COMMUNICATION DEVICE
CN115175255A (zh) * 2021-04-01 2022-10-11 华为技术有限公司 一种多播广播业务的传输切换方法及装置
WO2022241691A1 (zh) * 2021-05-19 2022-11-24 华为技术有限公司 一种组播/广播通信方法和装置

Also Published As

Publication number Publication date
EP3849219A4 (en) 2021-10-27
US20210219106A1 (en) 2021-07-15
CN110972078A (zh) 2020-04-07
EP3849219A1 (en) 2021-07-14

Similar Documents

Publication Publication Date Title
WO2020063362A1 (zh) 多播/广播业务传输的方法、核心网网元和终端设备
US11425537B2 (en) Communications system, communication method, and apparatus thereof
US10993086B2 (en) Method, system, and apparatus for transmitting group communication service data
KR101514425B1 (ko) Mbms 서비스 송신 방식의 전환 방법, 장치 및 사용자 장비
US20190141486A1 (en) Service processing method, device, and system
WO2021164564A1 (zh) 传输组播业务的方法和装置
WO2019042059A1 (zh) 数据传输的方法及装置
US10595168B2 (en) Enhancements to eMBMS for group communication
US20230011492A1 (en) Adaptive service areas for multicast session continuity
US20230388756A1 (en) Communication method and apparatus for multicast/broadcast service
US20230413355A1 (en) Method and equipment for multicast transmission
US11140656B2 (en) Paging in a group communications system
WO2022233024A1 (en) A method of establishing multicast broadcast service session, and system and apparatus thereof
WO2022233026A1 (en) A method of handover of mbs session, and system and apparatus thereof
WO2023185328A1 (zh) 一种通信方法及装置
US20230292227A1 (en) Method for delivery method switch from unicast to multicast
US20220376937A1 (en) Selecting ingress node for a multicast distribution session
CN117596552A (zh) 经由pdu会话建立过程请求加入mbs会话的方法及用户设备
CN117356075A (zh) 一种mbs会话创建的方法及其系统和装置
CN116390173A (zh) 支持多媒体广播组播业务mbs广播业务传输的方法

Legal Events

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

Ref document number: 19867972

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019867972

Country of ref document: EP

Effective date: 20210408