WO2021109134A1

WO2021109134A1 - Mbms informaiton acquisition and transmission method, terminal device and network element device

Info

Publication number: WO2021109134A1
Application number: PCT/CN2019/123730
Authority: WO
Inventors: 杨皓睿
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-12-06
Filing date: 2019-12-06
Publication date: 2021-06-10
Also published as: CN114402659A

Abstract

Some embodiments of the present application provide a multimedia broadcast multicast service information acquisition method, the method comprises: receiving a first message, wherein the first message comprises a single network slice selection assistance information (S-NSSAI) corresponding to a multimedia broadcast multicast service (MBMS), and the S-NSSAI is used for the MBMS. Some embodiments of the present application further provide a multimedia broadcast multicast service information transmission method, the method comprises:transmitting a first message to a terminal device, wherein the first message comprises an S-NSSAI corresponding to the MBMS, and the S-NSSAI is used for the MBMS. By enabling the terminal device to obtain the S-NSSAI corresponding to the MBMS, it is ensured that the terminal device can smoothly join the MBMS service.

Description

Method for obtaining and sending MBMS information, terminal equipment and network element equipment

Technical field

This application relates to the field of communication technology, and in particular to a method for acquiring and sending multimedia broadcast multicast service information, terminal equipment, and network element equipment.

Background technique

In the Long Term Evolution (Long Term Evolution, "LTE") system, the Application Server can transmit information to terminal equipment (User Equipment, "UE") in the form of broadcast or multicast. The difference between broadcast and multicast is that the broadcast service only limits the receiving area, while the multicast service limits the receiving area and requires UEs in a specific group to be able to receive it.

The LTE system structure is shown in Figure 1. When an application service transmits broadcast information to the UE, the broadcast information goes from the application service to the Broadcast Multicast-Service Centre (“BM-SC”) to the multimedia broadcast and multicast Service Gateway (Multimedia Broadcast/Multicast Service Gateway, referred to as "MBMS-GW)", and then to E-UTRAN (Evolved Global Terrestrial Radio Access Network) base station. The E-UTRAN base station then uses the broadcast channel to broadcast the received information. At the same time, the UE obtains the service ID (server ID) and the corresponding temporary mobile group identity (Temporary Mobile Group Identity) from the multimedia broadcast/multicast service (Multimedia Broadcast/Multicast Service, referred to as "MBMS") information configured by the application service or the core network. , Referred to as "TMGI"). The UE then obtains the radio resources of the broadcast channel corresponding to the TMGI from the system broadcast information of the base station, so as to receive the multicast information. If the UE needs to receive data of a certain multicast service, it needs to join the multicast group first.

The inventor found that related technologies have at least the following problems: In the current 3G or 4G network system architecture, the Gateway GPRS Support Node (Gateway GPRS Support Node, “GGSN”) needs to select one based on the MBMS service that the UE requests to join. The access point name (Access Point Name, "APN") of the MBMS service, the APN is sent to the Serving GPRS Support Node (Serving GPRS Support Node, "SGSN"), and the SGSN sends the APN to the UE. The UE then sends the APN to the SGSN, and the SGSN selects a GGSN that can support the multicast service required by the UE based on the APN. However, the process of obtaining the APN corresponding to the MBMS service by this solution is cumbersome and wastes signaling. Moreover, due to the introduction of the concept of network slicing in the 5G network, there may be multiple network slices in the same APN, which makes it impossible to obtain the APN according to the APN. If the correct GGSN is determined, there is no guarantee that the UE can join the MBMS service. That is to say, the current way the UE obtains the MBMS service information is suitable for the 3G or 4G network system architecture, but it is not suitable for the 5G network system architecture.

Summary of the invention

A technical problem to be solved by some embodiments of this application is to provide a method suitable for obtaining MBMS service information under the framework of a 5G network system, so that UEs with MBMS capabilities can successfully join MBMS through a simple signaling process. business.

An embodiment of the present application provides a method for acquiring multimedia broadcast and multicast service information. The method is applied to a terminal device and includes: sending a first message to the terminal device, where the first message contains the MBMS corresponding to the multimedia broadcast and multicast service. The single network slice selects the auxiliary information S-NSSAI of the S-NSSAI, and the S-NSSAI is used to use the MBMS.

An embodiment of the present application also provides a method for sending multimedia broadcast multicast service information. The method is applied to a network element device and includes: sending a first message to a terminal device, where the first message includes a multimedia broadcast multicast service The single network slice corresponding to the MBMS selects the auxiliary information S-NSSAI, and the S-NSSAI is used to use the MBMS.

An embodiment of the present application also provides a terminal device, including: an acquisition module, configured to receive a first message, the first message containing the single network slice selection auxiliary information S-NSSAI corresponding to the multimedia broadcast multicast service MBMS, The S-NSSAI is used to use the MBMS.

An embodiment of the present application also provides a network element device, including: a sending module, configured to send a first message to the terminal device, the first message containing the single network slice selection auxiliary information corresponding to the multimedia broadcast multicast service MBMS S-NSSAI, the S-NSSAI is used to use the MBMS.

An embodiment of the present application also provides a communication system, including the terminal device described above, and the network element device described above.

An embodiment of the present application further provides an electronic device, including: at least one processor; and a memory communicatively connected with the at least one processor; wherein the memory stores one or more programs that can be executed by the at least one processor One or more programs contain instructions, which when executed by at least one processor, cause at least one processor to execute the method for acquiring multimedia broadcast multicast service information applied to terminal devices as described above.

An embodiment of the present application further provides an electronic device, including: at least one processor; and a memory communicatively connected with the at least one processor; wherein the memory stores one or more programs that can be executed by the at least one processor One or more programs contain instructions, which when executed by at least one processor, cause at least one processor to execute the method for sending multimedia broadcast multicast service information applied to network element devices as described above.

An embodiment of the present application also provides a non-volatile computer storage medium that stores a program that can be executed by a processor. When the program is executed by the processor, the above-mentioned multimedia broadcast applied to terminal equipment is realized. The method for obtaining multicast service information, or the method for transmitting multimedia broadcast multicast service information applied to the network element device as described above.

For the prior art, the embodiment of this application receives the first message from the network element device, and uses the first message to obtain the Single-Network Slice Selection Assistance Information (Single-Network Slice Selection Assistance Information) of the MBMS requested to join. -NSSAI"). Since the S-NSSAI can uniquely indicate the MBMS service, the S-NSSAI can accurately locate the SMF supporting the MBMS service that the UE requests to join, thereby ensuring that the UE can successfully join the MBMS service. Moreover, the process is simple, and the waste of signaling is avoided, thereby saving system resources.

In an example, before receiving the first message, the method further includes: sending a request message for acquiring the MBMS to the network element device; the request message carries the service identifier of the MBMS for the network element device to determine according to the service identifier S-NSSAI, and the determined S-NSSAI is carried in the first message and fed back to the terminal device. The implementation is simple, and the UE can quickly obtain the S-NSSAI corresponding to the MBMS requesting to join.

In one example, before sending the request message for obtaining MBMS to the network element device, the session management function network element (Session Management function, referred to as "SMF") is first initiated to establish a session; the established session is used to communicate to the user plane function The network element UPF sends an MBMS service request, the MBMS service request carries the service identifier of the MBMS that the UE requests to join, and the S-NSSAI is obtained from the response message of the MBMS service request. The MBMS service request and its response message are transmitted using data packets; or, Send an MBMS service request to SMF. The MBMS service request carries the service identifier of the MBMS that the UE requests to join, and the S-NSSAI is obtained from the response message of the MBMS service request. The MBMS service request and its response message are transmitted by signaling; or The service identifier of the MBMS that the UE requests to join is carried in the session establishment request and sent to the SMF, and the S-NSSAI is obtained from the response message of the successful session establishment. S-NSSAI can be obtained by initiating a session and interacting with UPF or SMF through the session; or directly carrying the MBMS service identifier in the existing session establishment request, and using the response of the existing session establishment request The S-NSSAI is acquired by the message, so that the implementation of this application can be implemented flexibly.

In an example, before receiving the first message, it further includes: sending a registration request to an access and mobility management function network element (Access and Mobility Management function, "AMF" for short). Receiving the first message includes: receiving a registration acceptance message fed back by the access and mobility management function network element, where the registration acceptance message carries configuration and/or allowed S-NSSAIs. The UE can not only obtain S-NSSAI through interaction with SMF network elements, but also obtain accurate S-NSSAI through interaction with AMF network elements, so that the implementation of this application has a wide range of application scenarios.

In an example, the registration request is also used to trigger the AMF network element to send the identity of the UE to the policy control network element. After sending the registration request to the AMF, the second message carrying configuration information sent by the PCF is received; the configuration information includes : Used to match the service identifier of the MBMS service with the S-NSSAI corresponding to each service identifier; wherein the registration acceptance message also includes an indication of whether each S-NSSAI supports MBMS, or the second message also includes whether each S-NSSAI supports MBMS Instructions.

In an example, the registration request carries an indication that the UE supports MBMS. The registration request sent by the UE to the AMF carries the indication that the UE supports MBMS, so that the network element device can feed back the indication of whether each S-NSSAI supports MBMS for UEs that support MBMS, avoiding the feedback of each S to UEs that do not support MBMS. -Whether the NSSAI supports the MBMS instruction and the waste of resources.

In an example, after receiving the first message, it is also possible to join the MBMS according to the S-NSSAI.

Description of the drawings

One or more embodiments are exemplified by the pictures in the corresponding drawings, and these exemplified descriptions do not constitute a limitation on the embodiments.

Figure 1 is a schematic diagram of the LTE system structure in related technologies;

Figure 2 is a schematic diagram of a 5G network system architecture in related technologies;

Fig. 3 is a flow chart of transmitting MBMS information according to the first embodiment of the present application;

Fig. 4 is a flow chart of MBMS information transmission interaction according to the second embodiment of the present application;

Fig. 5 is a flow chart of MBMS information transmission interaction according to the third embodiment of the present application;

Fig. 6 is a flow chart of MBMS information transmission interaction according to the fourth embodiment of the present application;

Fig. 7 is a schematic diagram of S-NSSAI information elements in the fourth embodiment of the present application;

FIG. 8 is a schematic diagram of the structure of a communication system according to a fifth embodiment of the present application;

FIG. 9 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application;

Fig. 10 is a schematic structural diagram of an electronic device according to a seventh embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, some embodiments of the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, and are not used to limit the present application.

The embodiment of the application relates to a method for transmitting MBMS information, including a method for acquiring multimedia broadcast and multicast service information applied in a terminal device UE, and a method for sending multimedia broadcast and multicast service information applied in a network element device . Among them, the UE may be a user's mobile phone, a tablet computer, etc., which are not listed here. The network element equipment may be SMF or UPF, or it may be AMF or other network element equipment that can send messages to the UE, which are not listed here. The embodiments of the present application are intended to solve how the UE can successfully obtain information for joining the multimedia broadcast multicast service through a simple signaling process under the framework of the 5G network system. Among them, the 5G network system architecture is shown in Figure 2. The UE accesses the 5G core network through E-UTRAN or NR (radio access), and joins the MBMS service through E-UTRAN or NR. The following briefly introduces the main components involved in the 5G network architecture:

The terminal equipment UE mainly accesses the 5G network and obtains services through the wireless air interface. The terminal equipment exchanges information with the base station through the air interface, and accesses the core network through non-access stratum (Non-Access Stratum, referred to as "NAS") Exchange information with the mobile management function network element AMF.

The radio access network (Radio Access Network, "RAN") is responsible for air interface resource scheduling and air interface connection management for terminal equipment to access the network.

Access and mobility management function AMF, the core network control plane entity, is mainly responsible for user mobility management, including registration and temporary identification allocation; maintenance of IDLE and CONNECT states and state transitions; handover in CONNECT state; Trigger paging and other functions in the user IDLE state.

User plane function (User plane function, "UPF" for short), a core network user plane function entity, is responsible for forwarding user data messages, and also performs statistics on user data messages for charging and other functions.

The session management function SMF, the core network control plane entity, is mainly responsible for maintaining the PDU Session of the packet data unit, and is responsible for allocating user IP addresses. It has service quality control and charging functions; the user receives downlink data packets in the IDLE state for buffering and notifies AMF to search Call users and other functions.

Policy Control Functionality (Policy Control Functionality, referred to as "PCF"), core network control plane entity, is responsible for access and mobility management policies, UE policies, session management policies, and charging rules. This functional entity mainly generates access and mobility management strategies, UE routing strategies, service quality rules and charging rules for user data transfer, etc., based on service information, user subscription information, and operator configuration information.

The first embodiment of the present application will be described in detail below. In this embodiment, the network element device sends a first message to the UE, and the UE receives the first message. The first message contains the S-NSSAI corresponding to the MBMS. NSSAI is used to use this MBMS. Since the S-NSSAI can uniquely indicate the MBMS service, the S-NSSAI can be provided to ensure that the AMF selects the appropriate SMF, that is, accurately locate the SMF that supports the MBMS service that the UE requests to join, thereby realizing the joining of the MBMS service. The implementation details of this embodiment will be described in detail below. The following content is only provided for ease of understanding and is not necessary for the implementation of this solution.

The specific process of this embodiment is shown in FIG. 3. In step 310, the UE sends a request message for obtaining the MBMS service to the network element device, and the request message carries the MBMS service identifier. The network element equipment in this embodiment may be SMF or UPF.

In step 320, the network element device receives the request message for obtaining the MBMS service sent by the UE, and sends a response message of the request message to the UE. Specifically, after receiving the request message, the network element device obtains the service ID of the MBMS that the UE requests to join by analyzing the request message, and determines the S-NSSAI corresponding to the MBMS that the UE requests to join according to the service ID. , And carry the S-NSSAI in the response message of the request message and feed it back to the UE.

In step 330, the UE receives the response message of the request message, that is, receives the first message, and obtains the S-NSSAI of the MBMS requested to join according to the response message. Since the S-NSSAI can uniquely indicate the MBMS service, the corresponding MBMS service can be used through the S-NSSAI. In an implementation manner, after step 330, it may further include step 340, in which the UE joins the MBMS service according to the S-NSSAI. For example, the UE sends the S-NSSAI to the AMF, and the AMF determines the SMF corresponding to the MBMS service that the UE requests to join according to the S-NSSAI, that is, the SMF that supports the MBMS service, and initiates the SMF corresponding to the MBMS service that the UE requests to join Create a request for MBMS context content for the SMF to complete the establishment of MBMS context content through information interaction with BM-SC, and feedback the successful response of the MBMS context content creation request to AMF, for AMF to feed back to the UE to complete the MBMS service Join.

In a specific example, in step 320, the response message sent by the network element device to the UE may also carry one or any combination of the following information: Data Network Name (DNN) corresponding to MBMS ), support MBMS indication, multicast address, S-NSSAI of the local public land mobile network HPLMN mapped in the roaming scenario, QoS parameters, service area, MBMS service identification. If the response message sent by the network element device to the UE also includes the DNN corresponding to the MBMS, in step 340, the UE joins the MBMS service according to the DNN and S-NSSAI. Among them, if the multicast address is included in the response message, the multicast address is bound to a certain MBMS service for a period of time or all the time. If the multicast address is not included in the response message, after receiving the response message, the UE needs to obtain the multicast address corresponding to a certain MBMS service from the network.

In this embodiment, by sending a request message for obtaining MBMS to the network element device, the response message of the request message is used to obtain the S-NSSAI of the MBMS requesting to join. Since the S-NSSAI can uniquely indicate the MBMS service, the UE passes By sending the S-NSSAI to the AMF, the AMF can select the correct session management function (Session Management function, "SMF" for short), thereby ensuring that the UE can smoothly join the MBMS service. Moreover, the process of signaling interaction is simple, which avoids the waste of signaling, thereby saving system resources.

The second embodiment of the present application relates to a method for transmitting multimedia broadcast multicast service information, including a method for obtaining MBMS information applied in a UE and a method for sending MBMS information applied in a network element device. In this embodiment, the first message not only carries S-NSSAI, but can also carry DNN. On the basis of the first embodiment, this embodiment provides a specific S-NSSAI acquisition process, and the interaction flowchart of this embodiment is shown in FIG. 4.

In step 410, the UE initiates session establishment. Specifically, the UE can select an SMF and establish an arbitrary PDU session with the SMF.

In step 420, the UE uses the established session to send an MBMS service request to the SMF. The MBMS service request carries the service identifier of the MBMS that the UE requests to join, and the service identifier is used to uniquely identify the MBMS service. In a specific example, the service identifier of the MBMS may be obtained from the application layer of the UE, or the service identifier of the MBMS may also be preset in the UE. In this step, the UE carries the preset service identifier or the service identifier obtained from the application layer in the MBMS service request and sends it to the SMF of the established PDU session. The SMF that receives the MBMS service request needs to authenticate the UE. Specifically, the SMF detects whether the UE's authorization information for the MBMS service identifier is stored, and if the authorization information is not detected, step 430 is executed. In an embodiment, after the session is established, the UE may also use the established session to send an MBMS service request to the UPF. The MBMS service request carries the service identifier of the MBMS that the UE requests to join, and S is obtained from the response message of the MBMS service request. -NSSAI. In this embodiment, the MBMS service request and its response message are transmitted using data packets.

In step 430, the SMF or UPF that receives the MBMS service request initiates the authentication verification of the UE for the MBMS service identity to the BM-SC, and enters step 440 after the verification is passed. In an implementation manner, it is also possible to initiate an authentication verification of the UE for the MBMS service identity to a unified data management function (Unified Data Management, "UDM" for short). That is, if there is already authorization information of the UE based on the service identity, skip step 430 and go directly to step 440; if there is no authorization information of the UE based on the service identity, the SMF asks the BM-SC or UDM for the UE Whether to authorize the use of the MBMS indicated by the service identifier.

In step 440, the SMF determines the DNN and S-NSSAI of the MBMS service that the UE requests to join according to the service identifier carried in the MBMS service request by the UE, and carries the determined DNN and S-NSSAI in the response message of the MBMS service request , Sent to the UE.

In a specific example, the response message can also carry one or any combination of the following information: support MBMS indication, multicast address, S-NSSAI of the local public land mobile network HPLMN mapped in roaming scenarios, QoS parameters, service Area, MBMS service identification. For example, if the UE is authorized and the SMF is not an SMF that supports the MBMS service that the UE requests to join, the SMF sends an MBMS service request response message (Request MBMS service activation) to the UE, and the response message contains the MBMS service that the UE requests to join. If the UE is in a roaming scenario, the response message may also include the mapped S-NSSAI (mapped S-NSSA) of the HPLMN.

In step 450, the UE receives the response message of the MBMS service request carrying DNN and S-NSSAI fed back by the SMF, and joins the MBMS service according to the DNN and S-NSSAI in the response message. Specifically, after the UE receives the response message of the MBMS service request, it can obtain the DNN and S-NSSAI corresponding to the MBMS service requested to join from the response message. When the MBMS service is activated, the UE can send DNN and S-NSSAI to AMF, so that AMF can select the correct SMF, so that the UE can join the MBMS service smoothly.

In this embodiment, the UE initiates the establishment of a session to the SMF. Through the signaling interaction in the session, the service identifier of the MBMS requested to join is sent to the SMF or UPF, and the MBMS requested to join is obtained from the SMF or UPF. The DNN and S-NSSAI enable the UE to obtain the correct DNN and S-NSSAI corresponding to the MBMS service, so as to realize the smooth joining of the MBMS service under the framework of the 5G network system. Moreover, compared with the process of UE joining the MBMS service under the existing 3G or 4G network system architecture, the signaling interaction is simple, and the waste of signaling is avoided, thereby saving system resources.

The third embodiment of the present application relates to a method for transmitting multimedia broadcast multicast service information, including a method for obtaining MBMS information applied in a UE, and a method for sending MBMS information applied in a network element device. This embodiment is a variation of the second embodiment. In the second embodiment, the UE initiates the establishment of a session to the SMF, and uses the signaling interaction in the session to send the service identifier of the MBMS that requests to join to the SMF. However, in this embodiment, the UE directly carries the MBMS service identifier in the session establishment request and sends it to the SMF. The specific process is shown in Figure 5.

In step 510, the UE sends a session establishment request to the SMF, which carries the service identifier of the MBMS requesting to join, that is, the MBMS service identifier is carried in the session establishment request and sent to the SMF. The service identifier is used to uniquely identify the MBMS service. Similarly, the MBMS service identifier can be obtained from the application layer of the UE, or can be preset in the UE.

The SMF receiving the session establishment request detects whether the UE’s authorization information for the MBMS service identifier is stored. If the authorization information is not detected, step 520 is executed to initiate the UE’s MBMS service for the UE to the BM-SC or UDM The authentication of the identity is verified, and step 530 is entered after the verification is passed. That is to say, if there is already authorization information of the UE based on the service identity on the SMF, skip step 520 and go directly to step 530; if there is no authorization information based on the service identity of the UE on the SMF, the SMF sends the BM-SC or UDM asks whether the UE is authorized to use the MBMS indicated by the service identifier.

In step 530, the SMF determines the DNN and S-NSSAI of the MBMS service that the UE requests to join according to the service identifier carried in the session establishment request, and carries the determined DNN and S-NSSAI in the response message of the session establishment request. , Sent to the UE.

In a specific example, if the UE is authorized and the SMF is not the SMF corresponding to the MBMS service that the UE requests to join, the SMF sends a successful session establishment response to the UE. The response message contains the MBMS service that the UE requests to join. The service ID, DNN, S-NSSAI support MBMS service indication and multicast address, and if the UE is in a roaming scenario, the response message can also include the mapped HPLMN S-NSSAI.

In step 540, the UE joins the MBMS service according to the response message of successful session establishment. Specifically, the UE receives the response message of the successful session establishment of the DNN and S-NSSAI fed back by the SMF, and learns the DNN and S-NSSAI corresponding to the MBMS service requested to join through the response message, and then can directly request the AMF Activate the multicast service and provide DNN and S-NSSAI to ensure that the AMF selects the appropriate SMF. This step is similar to step 450, and will not be repeated here.

In this embodiment, the service identifier of the MBMS is directly carried in the existing session establishment request, and the response message of the existing session establishment request is used to obtain the DNN and S-NSSAI, that is, the existing message is used to realize the DNN and S-NSSAI. The accurate acquisition of, further simplifies the signaling interaction process, saves system resources, and also enables the implementation of the present application to be implemented flexibly.

The fourth embodiment of the present application relates to a method for transmitting multimedia broadcast multicast service information, including a method for obtaining MBMS information applied in a UE and a method for sending MBMS information applied in a network element device. This embodiment provides another specific S-NSSAI acquisition process, and the specific process is shown in FIG. 6.

In step 610, the UE sends a registration request (Registration Request) to the AMF.

In step 620, the AMF sends the identity of the UE to the PCF. Specifically, the UE sends the Npcf_AMassociation message or the Npcf_UEassociation message to the PCF, and the message carries the identity of the UE.

In step 630, the PCF sends a response message to the AMF to reply to the AMF.

In step 640, the AMF sends a Registration Accept message to the UE, and the PCF sends a second message carrying configuration information to the UE, such as a policy command carrying a user equipment routing policy (UE Route Selection Policy, "URSP" for short) (Policy command). Among them, each S-NSSAI configured and/or allowed is carried in the registration acceptance message. In addition, if the UE is in a roaming scenario, the registration acceptance message also carries the S-NSSAI of the HPLMN mapped in the roaming scenario; the configuration information in the second message can be the UE Route Selection Policy (UE Route Selection Policy, abbreviated as " URSP"), specifically includes: a service identifier used to match the MBMS service and an S-NSSAI corresponding to each service identifier. In this embodiment, the configuration information may also carry DNN. In an embodiment, the second message may be sent before the registration acceptance message, or after the registration acceptance message, that is, there is no clear sequence relationship between the transmission of the second message and the registration acceptance message.

In a specific example, the indication of whether MBMS is supported is carried in the registration acceptance message sent by the AMF to the UE. For example, after the AMF receives the registration request sent by the UE, when it feeds back the registration acceptance message to the UE, the registration acceptance message can be In the Configured NSSAI (Configured NSSAI) of the message, the UE will be notified of whether the configured S-NSSAI supports MBMS or not, or, in the Allowed NSSAI (allowed NSSAI) of the registration acceptance message, the allowed S-NSSAIs The indication of whether to support MBMS is notified to the UE. Configured NSSAI means the NSSAI configured for the UE. Upon receiving this configuration parameter, the UE knows which S-NSSAI is available under the network; Allowed NSSAI means which S-NSSAI is allowed by the network among the NSSAI requested by the UE. Configured NSSAI and Allowed NSSAI is one of the information elements of the registration acceptance message.

In another specific example, the indication of whether to support MBMS is carried in the second message sent by the PCF to the UE. That is, the registration acceptance message sent by the AMF to the UE is the same as the existing registration acceptance message. The configuration information carried in the second message sent by the PCF to the UE includes not only the Traffic Descripor (service identifier used to match the MBMS service) and its The corresponding DNN and S-NSSAI also include an indication of whether each MBMS service supports MBMS.

In a specific example, the indication of whether to support MBMS (MBMS indication) can be specified through the S-NSSAI information element in addition to the slice/service type ("SST") and the slice differentiator (Slice Differentiator). , Abbreviated as "SD") other bit representation, as shown in Figure 7. In other examples, SST or SD in the S-NSSAI can also be set to a specific value to indicate whether the S-NSSAI supports MBMS. Among them, SST refers to the expected network slicing behavior in terms of functions and services, and SD is optional information, supplementing slices/service types to distinguish multiple network slices of the same slice/service type.

It is worth mentioning that the registration request sent by the UE to the AMF can carry an indication that the UE supports MBMS. When the AMF sends the UE's identity to the PCF, it can also send the indication that the UE supports MBMS to the PCF, that is, in Npcf_AMassociation The message or Npcf_UEassociation message may also carry an indication that the UE supports MBMS. This enables the network element equipment to feed back the indication of whether each S-NSSAI supports MBMS for UEs that support MBMS, avoiding the waste of resources caused by also feeding back the indication of whether each S-NSSAI supports MBMS to UEs that do not support MBMS.

In step 650, the UE joins the MBMS service according to DNN and S-NSSAI. Specifically, through the registration acceptance message fed back by the AMF and the configuration information in the second message sent by the PCF, the UE obtains each S-NSSAI configured and/or allowed, the DNN and S-NSSAI corresponding to each MBMS service, and The indication of whether each S-NSSAI supports MBMS, if the UE is in a roaming scenario, the registration acceptance message also carries the S-NSSAI of the HPLMN mapped in the roaming scenario. Then, according to the MBMS service requested to join, determine the DNN and S-NSSAI corresponding to the MBMS service, request the AMF to activate the multicast service, and provide the DNN and S-NSSAI to ensure that the AMF selects the appropriate SMF.

In this embodiment, the UE does not need to interact with SMF, but directly obtains the correct DNN and S-NSSAI through the registration and interaction signaling process with AMF, which saves signaling and makes the implementation of this application possible. A wide range of application scenarios.

The fifth embodiment of the present application relates to a communication system, as shown in FIG. 8, including a terminal device 800 and a network element device 900. Wherein, the network element device 900 includes a sending module 910 for sending the first message. The terminal device 800 includes: an obtaining module 810, configured to receive the first message. Wherein, the first message includes the S-NSSAI corresponding to the MBMS, and the S-NSSAI is used to use the MBMS.

In a specific example, the terminal device 800 may also include a first sending module 820 for sending a request message for acquiring MBMS to the network element device; the network element device 900 may also include a first receiving module 920 for receiving A request message sent by the terminal device for obtaining MBMS, the request message carrying the service identifier of the MBMS, for the sending module 910 in the network element device to determine the S-NSSAI according to the service identifier, and carry the determined S-NSSAI in the first message Feedback to the terminal equipment.

In a specific example, the network element equipment 900 is SMF or UPF; the network element equipment 900 may further include: a detection module 930, configured to detect whether the UE authorization information for the service identifier is stored according to the received request message; The authentication module 940 is configured to initiate an authentication verification of the UE for the service identity to the BM-SC or UDM after the detection module does not detect the authorization information, and trigger the sending module 910 after the verification is passed.

In a specific example, the first sending module 820 included in the terminal device 800 specifically includes: a session establishment sub-module for initiating the establishment of a session to the SMF; a message sending sub-module for sending the established session to the SMF or The UPF sends an MBMS service request, and the MBMS service request carries the service identifier of the MBMS requested to join. The obtaining module 810 is specifically configured to receive the response message of the MBMS service request fed back by the SMF or UPF, and the response message of the MBMS service request carries the S-NSSAI of the MBMS requested to join. Among them, the response message can also carry one or any combination of the following information: the corresponding DNN of the MBMS, the indication of supporting MBMS, the multicast address, the S-NSSAI of the local public land mobile network HPLMN mapped in the roaming scenario, the quality of service QoS Parameters, service area, MBMS service identification.

In another specific example, the network element device 900 is an SMF, and the first sending module 820 included in the terminal device 800 is specifically configured to carry the service identifier of the MBMS requested to join in the session establishment request and send it to the SMF; the acquisition module 810 is specifically configured to receive a successful session establishment response message fed back by the SMF, and the successful session establishment response message carries the S-NSSAI of the MBMS requested to join.

In another specific example, the network element device 900 is an AMF, and the terminal device 800 further includes a second sending module 820' specifically configured to send a registration request to the AMF; the network element device 900 further includes a second receiving module 920' configured to Receive a registration request sent by the UE; the sending module 910 is specifically configured to send a registration acceptance message to the terminal device 800, where the registration acceptance message carries configuration and/or allowed S-NSSAIs. The acquiring module 810 included in the terminal device 800 is specifically configured to receive the registration acceptance message fed back by the AMF.

In a specific example, the sending module 910 of the network element device 900 is further configured to send the identification of the terminal device to the PCF after the second receiving module 920' receives the registration request sent by the UE, and trigger the PCF to send to the terminal device The second message carrying configuration information; the acquisition module 810 is also used to receive the second message carrying configuration information sent by the PCF; the configuration information may specifically be URSP, including: the service identifier used to match the MBMS service and the corresponding service identifier S-NSSAI. The registration acceptance message may also include an indication of whether each S-NSSAI supports MBMS, or the second message may also include an indication of whether each S-NSSAI supports MBMS.

In a specific example, the indication of whether to support MBMS can be indicated by other bits in the S-NSSAI information element except for the slice/service type SST and the slice differentiator SD, or the SST or SD in the S-NSSAI information element Value representation.

In a specific example, the registration request may also carry an indication that the UE supports MBMS; the sending module 910 may send an indication that the UE supports MBMS to the PCF while sending the identification of the terminal device to the PCF.

In a specific example, the terminal device 800 may further include: a joining module 830, configured to join the MBMS according to the S-NSSAI.

It is not difficult to find that this embodiment is an apparatus embodiment corresponding to the foregoing method embodiment, and this embodiment can be implemented in cooperation with any one of the first to fourth embodiments. The related technical details mentioned in the above method embodiments are still valid in this embodiment, and in order to reduce repetition, they will not be repeated here. Correspondingly, the related technical details mentioned in this embodiment can also be applied to the above method embodiment.

In addition, the modules involved in this embodiment are all logical modules. In one implementation, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Combined realization. In addition, in order to highlight the innovative part of the present invention, this embodiment does not introduce a unit that is not closely related to solving the technical problem proposed by the present invention, but this does not indicate that there are no other units in this embodiment.

The sixth embodiment of the present application relates to an electronic device, which corresponds to the UE in any one of the foregoing first to fourth embodiments. As shown in FIG. 9, the electronic device includes: at least one processor 1001; and, At least one memory 1002 communicatively connected to the processor 1001; and a communication component 1003 communicatively connected to the processor 1001 and the memory 1002, the communication component 1003 receives and sends data under the control of the processor 1001; wherein the memory 1002 stores data that can be Instructions executed by at least one processor 1001 are executed by at least one processor 1001 to implement the method for acquiring multimedia broadcast multicast service information executed by the UE in any of the foregoing method embodiments of the present application.

The seventh embodiment of the present application relates to an electronic device, which corresponds to the network element device in any one of the foregoing first to fourth embodiments. As shown in FIG. 10, the electronic device includes: at least one processor 1101; and , A memory 1102 communicatively connected with at least one processor 1101; and a communication component 1103 communicatively connected with the processor 1101 and the memory 1102, the communication component 1103 receives and sends data under the control of the processor 1101; wherein the memory 1102 stores Instructions that can be executed by at least one processor 1101 are executed by at least one processor 1101 to implement the method for sending multimedia broadcast multicast service information executed by the network element device in any of the foregoing method embodiments of the present application.

The above-mentioned products can execute the methods provided in the embodiments of the present application, and have the corresponding functional modules and beneficial effects of the execution methods. For technical details that are not described in detail in this embodiment, please refer to the methods provided in the embodiments of this application.

The eighth embodiment of the present invention relates to a non-volatile storage medium for storing computer-readable programs. The computer readable program implements the above method embodiments when executed by the processor.

That is, those skilled in the art can understand that all or part of the steps in the method of the foregoing embodiments can be implemented by instructing relevant hardware through a program. The program is stored in a storage medium and includes several instructions to enable a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

A person of ordinary skill in the art can understand that the foregoing embodiments are specific embodiments for realizing the present application, and various changes can be made to them in form and details without departing from the spirit and scope of the present application.

Claims

A method for acquiring multimedia broadcast and multicast service information, which is applied to terminal equipment, includes:

A first message is received, where the first message includes the single network slice selection auxiliary information S-NSSAI corresponding to the multimedia broadcast multicast service MBMS, and the S-NSSAI is used to use the MBMS.
The method according to claim 1, wherein before said receiving the first message, further comprising:

A request message for acquiring the MBMS is sent to the network element device; the request message carries the service identifier of the MBMS, and the service identifier of the MBMS is used by the network element device to determine the S- according to the service identifier. NSSAI;

The received first message includes the S-NSSAI determined by the network element device according to the service identifier of the MBMS.
The method according to claim 2, wherein the network element device is a session management function network element SMF or a user plane function network element UPF; and the request message for acquiring the MBMS information is sent to the network element device Before, it also included:

Initiate session establishment to the session management function network element SMF;

The sending a request message for obtaining a multimedia broadcast multicast service MBMS to a network element device includes:

Using the established session to send an MBMS service request to the session management function network element SMF or the user plane function network element UPF, where the MBMS service request carries the service identifier of the MBMS;

The receiving the first message includes:

Receiving the response message of the MBMS service request fed back by the session management function network element SMF or the user plane function network element UPF, where the response message of the MBMS service request carries the S-NSSAI.
The method according to claim 2, wherein the network element device is a session management function network element SMF; and the sending a request message for acquiring the MBMS to the network element device includes:

Carrying the service identifier of the MBMS in the session establishment request and sending it to the session management function network element SMF;

The receiving the first message includes:

Receive a successful session establishment response message fed back by the session management function network element SMF, where the successful session establishment response message carries the S-NSSAI.
The method according to any one of claims 1 to 4, wherein the first message further carries one of the following information or any combination thereof:

The data network name DNN corresponding to the MBMS, the indication of supporting MBMS, the multicast address, the S-NSSAI of the local public land mobile network HPLMN mapped in the roaming scenario, the quality of service QoS parameters, the service area, and the service identifier of the MBMS.
The method according to claim 1, wherein the network element device is an access and mobility management function network element AMF; before the receiving the first message, the method further comprises:

Sending a registration request to the access and mobility management function network element AMF;

The receiving the first message includes: receiving a registration acceptance message fed back by the access and mobility management function network element AMF, where the registration acceptance message carries the configured and/or allowed S-NSSAIs.
The method according to claim 6, wherein the registration request is also used to trigger the access and mobility management function network element AMF to send the identification of the terminal device to the policy control network element PCF;

The method also includes:

After the registration request is sent to the access and mobility management function network element AMF, the second message carrying configuration information sent by the policy control network element PCF is received; the configuration information includes: a service identifier for matching MBMS services S-NSSAI corresponding to each service ID;

Wherein, the registration acceptance message also includes an indication whether each S-NSSAI supports MBMS, or the second message also includes an indication whether each S-NSSAI supports MBMS.
The method according to claim 7, wherein the indication of whether to support MBMS is indicated by other bits in the S-NSSAI information element except for the slice/service type SST and the slice differentiator SD, or in the S-NSSAI information element The value of SST or SD is indicated.
8. The method according to any one of claims 6 to 8, wherein the registration request carries an indication that the terminal device supports MBMS.
The method according to any one of claims 1 to 9, further comprising:

After receiving the first message, join the MBMS according to the S-NSSAI.
A method for sending multimedia broadcast multicast service information, applied to network element equipment, includes:

A first message is sent to the terminal device, the first message includes the single network slice selection auxiliary information S-NSSAI corresponding to the multimedia broadcast multicast service MBMS, and the S-NSSAI is used to use the MBMS.
The method according to claim 11, wherein before the sending the first message to the terminal device, the method further comprises: receiving a request message sent by the terminal device for acquiring the MBMS; the request message carries the Business logo of MBMS;

The sending the first message to the terminal device includes:

Determine the S-NSSAI corresponding to the MBMS according to the service identifier;

The determined S-NSSAI is carried in the first message and fed back to the terminal device.
The method according to claim 12, wherein the network element device is a session management function network element SMF or a user plane function network element UPF, and after receiving the request message sent by the terminal device for acquiring the MBMS, Before the determining the S-NSSAI corresponding to the MBMS according to the service identifier, the method further includes:

Detecting whether authorization information of the terminal device for the service identifier of the MBMS is stored;

If the authorization information is not detected, it initiates an authentication verification of the terminal device's service identity for the MBMS to the broadcast multicast service center BM-SC or the unified data management function network element UDM, and the verification is passed Then, the S-NSSAI corresponding to the MBMS is determined according to the service identifier.
The method according to any one of claims 11 to 13, wherein the first message further carries one of the following information or any combination thereof:

The data network name DNN corresponding to the MBMS, the indication of supporting MBMS, the multicast address, the S-NSSAI of the local public land mobile network HPLMN mapped in the roaming scenario, the quality of service QoS parameters, the service area, and the service identifier of the MBMS.
The method according to claim 11, wherein the network element device is an access and mobility management function network element AMF; before the sending the first message to the terminal device, the method further comprises:

Receiving a registration request sent by the terminal device;

The sending the first message to the terminal device includes:

Send a registration acceptance message to the terminal device, where the registration acceptance message carries the configured and/or allowed S-NSSAIs.
The method of claim 15, further comprising:

After receiving the registration request sent by the terminal device, sending the identification of the terminal device to the policy control network element PCF, triggering the policy control network element PCF to send a second message carrying configuration information to the terminal device; The configuration information includes: the service ID used to match the MBMS service and the S-NSSAI corresponding to each service ID;

Wherein, the registration acceptance message also includes an indication whether each S-NSSAI supports MBMS, or the second message also includes an indication whether each S-NSSAI supports MBMS.
The method of claim 15 or 16, wherein:

Wherein, the registration request carries an indication that the terminal device supports MBMS.
A terminal device, including:

The acquiring module is configured to receive a first message, the first message containing the single network slice selection auxiliary information S-NSSAI corresponding to the multimedia broadcast multicast service MBMS, and the S-NSSAI is used to use the MBMS.
The terminal device according to claim 18, further comprising:

The first sending module is configured to send a request message for acquiring the MBMS to a network element device; the request message carries the service identifier of the MBMS, and the service identifier of the MBMS is used by the network element device according to the The service identifier determines the S-NSSAI;

The first message received by the acquiring module includes the S-NSSAI determined by the network element device according to the service identifier of the MBMS.
The terminal device according to claim 19, wherein the network element device is a session management function network element SMF or a user plane function network element UPF, and the first sending module comprises:

Session establishment sub-module, used to initiate session establishment to said session management function network element SMF;

A message sending submodule, configured to use the established session to send an MBMS service request to the session management function network element SMF or the user plane function network element UPF, where the MBMS service request carries the service identifier of the MBMS;

The acquiring module is specifically configured to receive the response message of the MBMS service request fed back by the session management function network element SMF or the user plane function network element UPF, where the response message of the MBMS service request carries the S- NSSAI.
The terminal device according to claim 19, the network element device is a session management function network element SMF, wherein the first sending module is specifically configured to carry the service identifier of the MBMS in the session establishment request and send it to Said session management function network element SMF;

The acquisition module is specifically configured to receive a successful session establishment response message fed back by the session management function network element SMF, and the successful session establishment response message carries the S-NSSAI.
The terminal device according to any one of claims 18 to 21, wherein the first message further carries one of the following information or any combination thereof:

The data network name DNN corresponding to the MBMS, the indication of supporting MBMS, the multicast address, the S-NSSAI of the local public land mobile network HPLMN mapped in the roaming scenario, the quality of service QoS parameters, the service area, and the service identifier of the MBMS.
The terminal device according to claim 18, further comprising:

The second sending module is used to send a registration request to the access and mobility management function network element AMF;

The acquiring module is specifically configured to receive a registration acceptance message fed back by the access and mobility management function network element AMF, and the registration acceptance message carries the configured and/or allowed S-NSSAIs.
The terminal device according to claim 23, wherein the registration request is also used to trigger the access and mobility management function network element AMF to send the identification of the terminal device to the policy control network element PCF; the acquisition module It is also used to receive a second message carrying configuration information sent by the policy control network element PCF; the configuration information includes: a service identifier used to match the MBMS service and an S-NSSAI corresponding to each service identifier;

Wherein, the registration acceptance message also includes an indication whether each S-NSSAI supports MBMS, or the second message also includes an indication whether each S-NSSAI supports MBMS.
The terminal device according to claim 24, wherein the indication of whether to support MBMS is indicated by other bits in the S-NSSAI information element except for the slice/service type SST and the slice differentiator SD, or the S-NSSAI information element The value of SST or SD in.
The terminal device according to claim 23 or 24, wherein:

The registration request carries an indication that the terminal device supports MBMS.
The terminal device according to any one of claims 18 to 26, further comprising:

The joining module is used to join the MBMS according to the S-NSSAI.
A network element equipment, including:

The sending module is configured to send a first message to the terminal device, the first message containing the single network slice selection auxiliary information S-NSSAI corresponding to the multimedia broadcast multicast service MBMS, and the S-NSSAI is used to use the MBMS.
The network element device according to claim 28, further comprising:

The first receiving module is configured to receive a request message for acquiring the MBMS sent by the terminal device; the request message carries the service identifier of the MBMS;

The sending module is specifically configured to determine the S-NSSAI corresponding to the MBMS according to the service identifier, and carry the determined S-NSSAI in the first message and feed back to the terminal device.
The network element device according to claim 29, wherein the network element device is a session management function network element SMF or a user plane function network element UPF, and the network element device further comprises:

A detection module, configured to detect whether authorization information of the terminal device for the service identifier of the MBMS is stored according to the request message received by the first receiving module;

The authentication module is used to initiate the MBMS service for the terminal device to the broadcast multicast service center BM-SC or the unified data management function network element UDM after the detection module does not detect the authorization information The authentication of the identity is verified, and the sending module is triggered after the verification is passed.
The method according to any one of claims 28 to 30, wherein the first message further carries one of the following information or any combination thereof:

The data network name DNN corresponding to the MBMS, the indication of supporting MBMS, the multicast address, the S-NSSAI of the local public land mobile network HPLMN mapped in the roaming scenario, the quality of service QoS parameters, the service area, and the service identifier of the MBMS.
The network element equipment according to claim 28, wherein the network element equipment is an access and mobility management function network element AMF; the network element equipment further comprises:

The second receiving module is configured to receive a registration request sent by the terminal device;

The sending module is specifically configured to send a registration acceptance message to the terminal device, and the registration acceptance message carries the configured and/or allowed S-NSSAIs.
The network element device according to claim 32, wherein:

The sending module is further configured to send the identification of the terminal device to the policy control network element PCF, and trigger the policy control network element PCF to send a second message carrying configuration information to the terminal device; the configuration information includes: Used to match the service ID of the MBMS service and the S-NSSAI corresponding to each service ID;

Wherein, the registration acceptance message also includes an indication whether each S-NSSAI supports MBMS, or the second message also includes an indication whether each S-NSSAI supports MBMS.
The network element device according to claim 32 or 33, wherein the registration request carries an indication that the terminal device supports MBMS.
A communication system, comprising the terminal device according to any one of claims 18 to 27, and the network element device according to any one of claims 28 to 34.
An electronic device including:

At least one processor;

A memory, which is in communication connection with the at least one processor; wherein,

The memory stores one or more programs that can be executed by the at least one processor;

The one or more programs include instructions that, when executed by at least one processor, cause the at least one processor to execute the multimedia broadcast multicast service information according to any one of claims 1 to 10 Obtaining method.
An electronic device including:

At least one processor;

A memory, which is in communication connection with the at least one processor; wherein,

The memory stores one or more programs that can be executed by the at least one processor;

The one or more programs include instructions that, when executed by at least one processor, cause the at least one processor to execute the multimedia broadcast multicast service information according to any one of claims 11 to 17. Delivery method.
A computer-readable storage medium storing a program that can be executed by a processor, and when the program is executed by the processor, it realizes the acquisition of multimedia broadcast multicast service information according to any one of claims 1 to 10 Method, or implement the method for sending multimedia broadcast multicast service information according to any one of claims 11 to 17.