Multimedia broadcast multicast service authentication method, device, equipment and storage medium

Through NAS message interaction between the terminal device and the first network element control plane, the user plane and the control plane are separated, and the compatibility problem of MBMS service operation in 5G is solved, and the normal operation of MBMS services in 5G network is achieved.

CN115336377BActive Publication Date: 2024-11-29GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202080099194.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-04-24
Publication Date
2024-11-29
Estimated Expiration
2040-04-24

AI Technical Summary

Technical Problem

In the fifth generation of mobile communications and communication system (5G), how to achieve the normal operation of multimedia broadcast multicast service (MBMS) services is considered that the 5G architecture no longer supports traditional broadcast multicast service center (BM-SC) network elements.

Method used

Through the NAS message interaction between the terminal device and the first network element control plane, the service registration, request authentication and key distribution process is completed, and the user plane and the control plane are separated to realize the BM-SC function without changing the communication in the 3GPP standard. Device, suitable for networks in all 5G scenarios.

Benefits of technology

It realizes seamless implementation of MBMS services in 5G networks, ensuring the normal operation and compatibility of services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115336377B_ABST
    Figure CN115336377B_ABST
Patent Text Reader

Abstract

The present application discloses a multimedia broadcast multicast service authentication method, device, equipment and storage medium, which relates to the field of wireless communications. The method comprises: the terminal device interacts with the first network element control plane through a mobile network control plane through a NAS message, and the interaction is used to complete at least one of the following processes: a service registration process, an authentication request process, and a key distribution process; at least one of the service registration process, the authentication request process, and the key distribution process is used for MBMS services.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular to a multimedia broadcast and multicast service authentication method, apparatus, device, and storage medium. Background Art

[0002] In the 4th Generation Mobile Communication Systems (4G), the Broadcast Multicast Service Center (BM-SC) network element, as the main node of the Multimedia Broadcast / Multicast Service (MBMS), will create and maintain MBMS services and generate and transmit data streams.

[0003] However, in the architecture of the fifth generation wireless communication systems (5G), BM-SC network elements will no longer be supported, and how to implement MBMS services has become a problem that needs to be solved. Summary of the Invention

[0004] The embodiments of the present application provide a multimedia broadcast multicast service authentication method, apparatus, device, and storage medium. The technical solution is as follows.

[0005] According to one aspect of the present application, a multimedia broadcast multicast service authentication method is provided, which is applied to a terminal device;

[0006] The terminal device interacts with the first network element control plane through a NAS message through the mobile network control plane, and the interaction is used to complete at least one of the following processes: a service registration process, an authentication request process, and a key distribution process;

[0007] At least one of the service registration process, the authentication request process, and the key distribution process is used for MBMS service.

[0008] According to one aspect of the present application, a multimedia broadcast multicast service authentication method is provided, which is applied to a communication system, wherein the communication system includes a mobile network control plane, a first network element control plane, and a first network element user plane;

[0009] The first network element control plane interacts with the terminal device through the mobile network control plane through NAS messages, and the interaction is used to complete at least one of the following processes: a service registration process, an authentication request process, and a key distribution process;

[0010] At least one of the service registration process, the authentication request process, and the key distribution process is used for MBMS service.

[0011] According to one aspect of the present application, a multimedia broadcast multicast service authentication device is provided, the device comprising: a transceiver module;

[0012] The transceiver module is configured to interact with the first network element control plane through NAS messages through the mobile network control plane, and the interaction is used to complete at least one of the following processes: service registration process, authentication request process, and key distribution process;

[0013] At least one of the service registration process, the authentication request process, and the key distribution process is used for MBMS service.

[0014] According to one aspect of the present application, a multimedia broadcast multicast service authentication device is provided, the device comprising a mobile network control plane module, a first network element control plane module, and a first network element user plane module;

[0015] The first network element control plane module interacts with the terminal device through the mobile network control plane module through NAS messages, and the interaction is used to complete at least one of the following processes: service registration process, authentication request process, and key distribution process;

[0016] At least one of the service registration process, the authentication request process, and the key distribution process is used for MBMS service.

[0017] According to one aspect of the present application, a terminal device is provided, comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the multimedia broadcast multicast service authentication method as described in the above aspects.

[0018] According to one aspect of the present application, a communication system is provided, comprising:

[0019] processor and memory;

[0020] The code in the memory run by the processor is provided to at least one network element in network function virtualization, and the at least one network element is used to execute the multimedia broadcast multicast service authentication method as described in the above aspects.

[0021] According to one aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores executable instructions, and the executable instructions are loaded and executed by the processor to implement the multimedia broadcast multicast service authentication method as described in the above aspect.

[0022] The technical solutions provided by the embodiments of the present application include at least the following beneficial effects:

[0023] The terminal device interacts with the first network element control plane through NAS messages through the mobile network control plane, that is, the function of BM-SC is realized by separating the user plane and the control plane. The MBMS service can be realized without changing the communication equipment in the 3GPP standard, and can be applied to networks in all 5G scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0025] Figure 1 is a block diagram of a communication system provided by an exemplary embodiment of the present application;

[0026] Figure 2 is a schematic diagram of a multimedia broadcast multicast service authentication method provided by an exemplary embodiment of the present application;

[0027] Figure 3 is a flowchart of a multimedia broadcast multicast service authentication method provided by an exemplary embodiment of the present application;

[0028] Figure 4 This is a method flow chart of a service registration process provided by an exemplary embodiment of the present application;

[0029] Figure 5 This is a method flow chart of a service registration process provided by an exemplary embodiment of the present application;

[0030] Figure 6 This is a method flow chart of a service registration process provided by an exemplary embodiment of the present application;

[0031] Figure 7 This is a flowchart of a method for requesting an authentication process provided by an exemplary embodiment of the present application;

[0032] Figure 8 This is a flowchart of a method for requesting an authentication process provided by an exemplary embodiment of the present application;

[0033] Figure 9 This is a flowchart of a method for requesting an authentication process provided by an exemplary embodiment of the present application;

[0034] Figure 10is a flowchart of a key distribution process provided by an exemplary embodiment of the present application;

[0035] Figure 11 is a flowchart of a key distribution process provided by an exemplary embodiment of the present application;

[0036] Figure 12 This is a network deployment diagram including a multicast service function provided by an exemplary embodiment of the present application;

[0037] Figure 13 This is a system architecture diagram including a multicast service function provided by an exemplary embodiment of the present application;

[0038] Figure 14 This is a structural block diagram of a multimedia broadcast multicast service authentication device provided by an exemplary embodiment of the present application;

[0039] Figure 15 This is a structural block diagram of a multimedia broadcast multicast service authentication device provided by an exemplary embodiment of the present application;

[0040] Figure 16 It is a structural diagram of a terminal device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0042] First, a brief introduction to the terms involved in this application:

[0043] GBA: (General Bootstrapping Architecture, general authentication mechanism);

[0044] MBS: (Multicast Broadcast Service, multicast broadcast service);

[0045] MRK: (MBMS Request Key, MBMS request key);

[0046] MSK: (MBMS Service Key, MBMS service key);

[0047] MTK: (MBMS Traffic Key, MBMS traffic key);

[0048] MUK: (MBMS User Key, MBMS user key);

[0049] MBSF: (Multimedia Broadcast Service Function, multimedia broadcast service function);

[0050] MBSU: (Multimedia Broadcast Service User plane, multimedia broadcast service user plane);

[0051] SUPI: (Subscriber Permanent Identifier, user real identity identifier).

[0052] Figure 1 A block diagram of a communication system provided by an exemplary embodiment of the present application is shown. The communication system includes: an access network 12, a terminal device 14, a core network 16, and a non-core network 18.

[0053] The access network 12 includes several network devices 120. These devices may be base stations, which are devices deployed in the access network to provide wireless communication capabilities for terminals. Base stations can include various forms of macro base stations, micro base stations, relay stations, access points, and so on. In systems using different wireless access technologies, the names of devices with base station functions may vary. For example, in LTE systems, they are called eNodeBs or eNBs; in 5G NR-U systems, they are called gNodeBs or gNBs.

[0054] The terminal device 14 may include various handheld devices with wireless communication capabilities, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of user equipment, mobile stations (MS), terminals, and the like. For ease of description, the aforementioned devices are collectively referred to as terminal devices. The network device 120 and the terminal device 14 communicate with each other via some air interface technology, such as the Uu interface.

[0055] The terminal device 14 accesses the core network 16 and the non-core network 18 through the access network 12 .

[0056] Optionally, the core network 16 includes at least one of a user plane function (UPF), an authentication server function (AUSF), a unified data management (UDM) function, a network exposure function (NEF), an access and mobility management function (AMF), a security anchor function (SEAF), a session management function (SMF), and a policy control function (PCF). One or more network elements in the core network 16 are used to carry the GBA mechanism.

[0057] Optionally, the non-core network 18 is divided into a control plane and a user plane for carrying MBS services. The non-core network 18 includes an MBSU and an MBSF.

[0058] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE-based access to Unlicensed spectrum (LTE-U) system, NR-U system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Network (WLAN) system. Networks, WLAN), Wireless Fidelity (WiFi), next generation communication systems or other communication systems, etc.

[0059] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) systems. The embodiments of the present application can also be applied to these communication systems.

[0060] Figure 2A schematic diagram of a multimedia broadcast multicast service authentication method provided by an exemplary embodiment of the present application is shown.

[0061] The terminal device interacts with the first network element control plane through NAS messages through the mobile network control plane, and the interaction is used to complete at least one of the following processes: service registration process, authentication request process, and key distribution process;

[0062] At least one of the service registration process, the authentication request process, and the key distribution process is used for the MBMS service.

[0063] The registration and authentication process is used to register the terminal device on the mobile network control plane so that the terminal device and the first network element control plane can subsequently perform MBMS services.

[0064] The authentication request process is used by the terminal device to request the first network element control plane to issue a key, so that the terminal device can communicate through the key in subsequent processes.

[0065] The key distribution process is used to distribute keys to terminal devices after the first network element control plane verification request is passed, so that the terminal device communicates through the received key.

[0066] MBMS (Multimedia Broadcast / Multicast Service) is a service type proposed by the 3rd Generation Partnership Project (3GPP). It provides two transmission methods: broadcast and multicast. Both broadcast and multicast transmit messages from one point to multiple points. SMS, images, audio, video, and applications can all be transmitted in this way, saving mobile bandwidth resources.

[0067] Optionally, the mobile network control plane is a network element in the core network.

[0068] Optionally, the first network element is a network element in a non-core network. The control plane of the first network element is used to process control plane signaling and carries functions such as key request, key distribution, and member management.

[0069] Optionally, the Non-Access Stratum (NAS) exists in the wireless communication protocol stack of the Universal Mobile Telecommunications System (UMTS), serving as a functional layer between the core network and the terminal device. NAS messages are messages transmitted in the Non-Access Stratum, and are used to facilitate signaling and data transmission between the terminal device and the control plane of the first network element.

[0070] In an optional embodiment, the terminal device interacts with the first network element control plane through a non-access layer NAS message via the mobile network control plane, including: the terminal device adds the content interacted with the first network element control plane to a container, and transmits the container through the mobile network control plane.

[0071] The information exchange between the terminal device and the first network element control plane can be carried out in a transparent transmission manner: that is, the relevant information is placed in a container, and the container is placed in a NAS message, which is transparently transmitted to the other end by the mobile network control plane.

[0072] Transparent transmission refers to transparent transmission. For the mobile network control plane, it only serves as a channel for information transmission and does not process the information. When the terminal device (or the first network element control plane) receives the transparent transmission message, it processes the information.

[0073] In summary, the method provided in this embodiment is that the terminal device interacts with the first network element control plane through NAS messages through the mobile network control plane, that is, the function of BM-SC is realized by separating the user plane and the control plane. The MBMS service can be realized without changing the communication equipment in the 3GPP standard, and can be applied to networks in all 5G scenarios.

[0074] Figure 3 A flowchart of a multimedia broadcast multicast service authentication method provided by an exemplary embodiment of the present application is shown. The method includes the following steps:

[0075] Step 310: The terminal device sends a service registration request to the mobile network control plane.

[0076] Among them, the service registration request is used to register the terminal device.

[0077] Step 320: The mobile network control plane sends a service registration request to the first network element control plane.

[0078] After receiving the service registration request sent by the terminal device, the mobile network control plane forwards the service registration request to the first network element control plane. When the terminal device needs to use the MBMS service, the terminal device needs to register first. Only when the registration is successful can the MBMS service be activated.

[0079] Optionally, the service registration request includes (or does not include) fifth key information. The fifth key information is a shared key formed between the terminal device and the network side based on the GBA mechanism.

[0080] Step 330: The first network element controls the feedback of a first verification success message to the terminal device.

[0081] The first verification success message is used to indicate that the service registration process corresponding to the service registration request is successful.

[0082] The terminal device can determine that the service registration process corresponding to the service registration request is successful based on the received first verification success message.

[0083] Optionally, if the terminal device does not receive the first verification success message, it can be determined that the service registration process corresponding to the service registration request has failed, and the service registration request needs to be resent for service registration.

[0084] Step 340: The terminal device sends a first verification request to the mobile network control plane.

[0085] The first verification request is used to request the acquisition of the first key. Optionally, the first key is used to encrypt the second key during the key request process of the terminal device.

[0086] Step 350: The mobile network control plane sends a first verification request to the first network element control plane.

[0087] After receiving the first verification request sent by the terminal device, the mobile network control plane forwards the first verification request to the first network element control plane.

[0088] Optionally, the first verification request includes (or does not include) eighth key information.

[0089] Optionally, the first verification request may be an MSK request, used to request acquisition of an MSK key.

[0090] Step 360: The first network element controls the feedback of a second verification success message to the terminal device.

[0091] The second verification success message is used to indicate that the first verification request has been successfully verified. The terminal device can determine that the request authentication process corresponding to the first verification request is successful based on the received second verification success message.

[0092] Optionally, if the terminal device does not receive the second verification success message, it can be determined that the request authentication process corresponding to the service registration request has failed and the request authentication needs to be performed again.

[0093] In step 370, the first network element controls the sending of the first key and the second key to the terminal device.

[0094] The first key is used to protect the second key, and the second key is used for data transmission between the terminal device and the user plane of the first network element.

[0095] Optionally, one or more second keys may correspond to one first key. After sending the first key to the terminal device, the first network element control plane may send multiple second keys.

[0096] Step 380: The first network element control plane sends the first key and the second key to the first network element user plane.

[0097] Optionally, corresponding to step 370 and step 380, after successfully sending the first key (or second key) to the terminal device, the control plane of the first network element sends the first key (or second key) to the user plane of the first network element.

[0098] Optionally, one first key corresponds to one or more second keys. After sending the first key to the first network element user plane, the first network element control plane may send multiple second keys.

[0099] Optionally, the mobile network control plane includes but is not limited to: at least one of: AMF network element, SMF network element, AUSF network element, SEAF network element; the first network element control plane includes but is not limited to: MBSF network element; the first network element user plane includes but is not limited to: MBSU network element.

[0100] It should be noted that the above steps 310 to 330 correspond to the service registration process, the above steps 340 to 360 correspond to the authentication request process, and the above steps 370 to 380 correspond to the key distribution process.

[0101] To summarize, in the method provided in the embodiment of the present application, the terminal device and the first network element control plane interact through NAS to complete at least one of the following registration authentication process, request authentication process, and key distribution process, and each of the registration authentication process, request authentication process, and key distribution process is used for MBMS services. A method for MBMS service is provided, in which the service registration process, MSK request verification process, and key issuance process are set in the first network element control plane, thereby ensuring the normal operation of the MBMS service.

[0102] The following further explains the above three processes:

[0103] Service registration process

[0104] Based on Figure 3 In an optional embodiment, Figure 4 A flowchart of a service registration process provided by an exemplary embodiment of the present application is shown, and the method includes:

[0105] Step 410: The terminal device sends a service registration request to the mobile network control plane.

[0106] The service registration request is used to register the terminal device.

[0107] Step 420: The mobile network control plane sends a service registration request to the first network element control plane.

[0108] After receiving the service registration request sent by the terminal device, the mobile network control plane forwards the service registration request to the first network element control plane.

[0109] Optionally, the service registration request forwarded by the mobile network control plane and received by the first network element control plane does not include the fifth key information, and the fifth key information is used to derive the third key information; or, the service registration request forwarded by the mobile network control plane and received by the first network element control plane includes the fifth key information.

[0110] Step 430: The first network element control plane sends the first network element identifier and the first random number to the mobile network control plane.

[0111] Optionally, the first network element identifier is used to uniquely identify the first network element. The first random number is a 16-octet random number generated at a control plane of the first network element.

[0112] Step 440: The mobile network controls the sending of the first network element identifier and the first random number to the terminal device.

[0113] After receiving the first network element identifier and the first random number sent by the first network element control plane, the mobile network control plane forwards the first network element identifier and the first random number to the terminal device.

[0114] Step 450: The terminal device determines first summary information.

[0115] The first summary information is verification information generated by the terminal device according to the received first random number.

[0116] Optionally, after receiving the first network element identifier and the first random number, the terminal device first confirms the identity information of the first network element according to the first network element identifier, and determines that the first network element is a server requiring MBS service.

[0117] Optionally, the process of the terminal determining the first summary information includes: determining third key information according to the first network element identifier and the first random number, determining fourth key information according to the third key information, and determining the first summary information according to the fourth key information and the first random number.

[0118] Step 460: The terminal device sends the first summary information and the second random number to the first network element control plane.

[0119] Optionally, the second random number is a 16-octet random number generated at the terminal device.

[0120] Step 470: The first network element control plane verifies the first summary information.

[0121] The first network element control plane verifies the first summary information according to the fourth key information.

[0122] Optionally, the process of the first network element control plane verifying the first summary information includes: the first network element control plane calculating the fourth key information according to the third key information; and the first network element control plane verifying the first summary information according to the first random number and the fourth key information.

[0123] Optionally, the above-mentioned third key information is a shared key between the terminal device and the first network element control plane, the third key information needs to be derived based on the fifth key information, and the third key information is used to derive the fourth key information.

[0124] In one implementation, if the service registration request forwarded by the mobile network control plane and received by the first network element control plane does not include the fifth key information, the mobile network control plane calculates the third key information; the mobile network control plane sends the third key information to the first network element control plane; and the first network element control plane receives the third key information. In another implementation, if the service registration request forwarded by the mobile network control plane and received by the first network element control plane includes the fifth key information, the first network element control plane calculates the third key information based on the fifth key information.

[0125] Step 480: The first network element control plane sends the second summary information and the first verification success message.

[0126] The second summary information is generated by the first network element control plane according to the second random number.

[0127] When the first network element control plane successfully verifies the first summary information, the first network element control plane sends the second summary information and the first verification success message to the terminal device.

[0128] Step 490: The terminal device verifies the second summary information.

[0129] The terminal device receives the second summary information fed back by the first network element control plane. The terminal device verifies the second summary information according to the second random number. If the verification is successful, the service registration process of the terminal device is completed.

[0130] Below, the above service registration process is exemplarily explained with the mobile network control plane including AMF and the first network element control plane including MBSF.

[0131] After the terminal device initiates a service registration request and transmits it through the network, if the service registration request received by MBSF does not contain the key Ks, MBSF first initiates a request containing MBSF_ID and random number nonce1 to the GBA server AMF, such as Figure 5As shown in Figure 1, the key parameter Ks in the Ks_xx_NAF is held by the terminal device and the AMF. Therefore, during the service registration and key request process, the terminal device and the AMF negotiate the Ks_xx_NAF. To ensure smooth service registration, the AMF sends the Ks_xx_NAF to the MBMS server. The service registration process is collaboratively completed by the terminal device, the GBA server AMF, and the MBS server MBSF. After successful authentication, the terminal device and the MBSF negotiate the MRK and MUK.

[0132] Combined with reference Figure 5 , Figure 5 A flowchart of a method for a service registration process provided by an exemplary embodiment of the present application is shown. In this embodiment, the service registration request does not include Ks (i.e., the fifth key information), and the method includes:

[0133] Step 510: The terminal device sends a service registration request to the AMF.

[0134] The service registration request includes B-TID and MBS Service ID, where B-TID represents the identity information generated by the terminal device through the GBA mechanism, and MBS Service ID is the MBS service ID.

[0135] Step 520: AMF sends a service registration request to MBSF.

[0136] After receiving the service registration request from the terminal device, the AMF first checks the validity period of the B-TID. If it is determined that the B-TID is within the validity period and the key corresponding to the B-TID is also within the validity period, it forwards the service registration request to the MBSF. The forwarded service registration request contains the B-TID and MBS Service ID. The B-TID represents the identity information of the terminal device generated by the GBA mechanism, and the MBS Service ID is the MBS service ID.

[0137] Step 530: MBSF sends MBSF_ID and nonce1 to AMF.

[0138] After receiving the service registration request forwarded by AMF, MBSF sends MBSF_ID (i.e., the first network element identifier) ​​and nonce1 (i.e., the first random number) to AMF, where MBSF_ID is the identity information of MBSF and nonce1 is a random number.

[0139] In step 540, the AMF calculates Ks_xx_NAF.

[0140] After receiving the above message, the AMF calculates the key Ks_xx_NAF (i.e., the third key information) according to the random number nonce1.

[0141] Optionally, Ks_xx_NAF=KDF(KAMF, "gba_xx_NAF", nonce1, SUPI, MBSF_ID), where KAMF is the shared key between the terminal device and AMF, "gba_xx_NAF" is a GBA process parameter, SUPI is the user's real identity, nonce1 is a random number, and MBSF_ID is the identity information of MBSF.

[0142] Optionally, the AMF also calculates the user key file, bootstrap time and key period.

[0143] In step 550, the AMF forwards the received MBSF_ID and nonce1 to the terminal device.

[0144] MBSF_ID is the identity information of MBSF, and nonce1 is a random number.

[0145] Step 560: The terminal device calculates MRK and MUK.

[0146] After receiving the message forwarded by AMF, the terminal device first checks MBSF_ID to verify whether the MBSF is the server that needs to receive the multicast message. If the verification is successful, the MRK (i.e., the fourth key information) and MUK are calculated according to Ks_xx_NAF.

[0147] In step 570, the AMF sends the calculated Ks_xx_NAF to the MBSF.

[0148] Optionally, the AMF also sends the calculated user key file, bootstrap time and key period to the MBSF.

[0149] Step 580: The terminal device calculates and sends the digest RES and the random number nonce2.

[0150] Optionally, RES=f2(MRK, nonce1, B-TID) (ie, the first summary information), and nonce2 is a second random number.

[0151] In step 590, MBSF calculates MRK, MUK and verifies the digest.

[0152] MBSF calculates MRK and MUK based on Ks_xx_NAF received from AMF, and then verifies whether the terminal device's summary RES is legal through the calculated MRK and MUK.

[0153] Step 5100: MBSF calculates and sends the summary RES*.

[0154] If the verification is successful, the MBSF sends a verification success flag to the terminal device, calculates the digest RES*=f2(MRK, nonce2, B-TID), and then sends RES* (i.e., the second digest information) to the terminal device in response to the terminal device's challenge, completing the service registration process of the terminal device.

[0155] Combined with reference Figure 6 , Figure 6 A flowchart of a method for a service registration process provided by an exemplary embodiment of the present application is shown. In this embodiment, the service registration request includes Ks (i.e., the fifth key information), and the method includes:

[0156] Step 610: The terminal device sends a service registration request to the AMF.

[0157] The service registration request includes B-TID and MBS Service ID, where B-TID represents the identity information generated by the terminal device through the GBA mechanism, and MBS Service ID is the MBS service ID.

[0158] Step 620: AMF sends a service registration request to MBSF.

[0159] After receiving a service registration request from a terminal device, the AMF first checks the validity period of the B-TID. If it determines that the B-TID is within the validity period and the key corresponding to the B-TID is also within the validity period, it forwards the service registration request to the MBSF. The forwarded service registration request contains the B-TID, MBS Service ID, and Ks. The B-TID represents the identity information of the terminal device generated through the GBA mechanism, the MBS Service ID is the MBS service ID, and Ks is the shared key formed between the terminal device and the network side based on the GBA mechanism.

[0160] Step 630: MBSF sends MBSF_ID and nonce1 to AMF.

[0161] After receiving the service registration request forwarded by AMF, MBSF sends MBSF_ID (i.e., the first network element identifier) ​​and nonce1 (i.e., the first random number) to AMF, where MBSF_ID is the identity information of MBSF and nonce1 is a random number.

[0162] In step 640, the AMF forwards the received MBSF_ID and nonce1 to the terminal device.

[0163] MBSF_ID is the identity information of MBSF, and nonce1 is a random number.

[0164] Step 650: The terminal device calculates MRK and MUK.

[0165] After the terminal device receives the message forwarded by AMF, it first checks MBSF_ID to verify whether the MBSF is the server that needs to receive the multicast message. If the verification is successful, the MRK (i.e., the fourth key information) and MUK are calculated based on Ks_xx_NAF (i.e., the third key information).

[0166] Optionally, Ks_xx_NAF includes one of Ks_ext_NAF and Ks_int_NAF. Specifically, Ks_ext_NAF = KDF(Ks, "gba-me", nonce1, SUPI, MBSF_ID), and Ks_int_NAF = KDF(Ks, "gba-u", nonce1, SUPI, MBSF_ID). Ks is a shared key formed between the terminal device and the network side based on the GBA mechanism, "gba-me" and "gba-u" are GBA process parameters, nonce1 is a random number, SUPI is the user's real identity, and MBSF_ID is the identity information of the MBSF.

[0167] Step 660: The terminal device calculates and sends the digest RES and the random number nonce2.

[0168] Optionally, RES=f2(MRK, nonce1, B-TID) (ie, the first summary information), and nonce2 is a second random number.

[0169] In step 670, MBSF calculates MRK, MUK and verifies the digest.

[0170] MBSF first calculates Ks_xx_NAF, then calculates MRK and MUK based on Ks_xx_NAF, and then verifies whether the terminal device's summary RES is legal through the calculated MRK and MUK.

[0171] Step 680: MBSF calculates and sends the summary RES*.

[0172] If the verification is successful, the MBSF sends a verification success flag to the terminal device, calculates the digest RES*=f2(MRK, nonce2, B-TID), and then sends RES* (i.e., the second digest information) to the terminal device in response to the terminal device's challenge, completing the service registration process of the terminal device.

[0173] Request certification process

[0174] Figure 7 A flowchart of a method for requesting authentication provided by an exemplary embodiment of the present application is shown, and the method includes:

[0175] Step 710: The terminal device sends a first verification request to the mobile network control plane.

[0176] The first verification request is used to request to obtain the first key.

[0177] Step 720: The mobile network control plane sends a first verification request to the first network element control plane.

[0178] After receiving the first verification request sent by the terminal device, the mobile network control plane forwards the first verification request to the first network element control plane.

[0179] Optionally, the first verification request forwarded by the mobile network control plane and received by the first network element control plane does not include the eighth key information, and the eighth key information is used to derive the sixth key information; or, the first verification request forwarded by the mobile network control plane and received by the first network element control plane includes the eighth key information.

[0180] After receiving the first verification request, the first network element control plane verifies the first verification request. If the verification of the first verification request succeeds, the process jumps to step 7100 ; if the verification of the first verification request fails, the process jumps to step 730 and executes steps 730 to 790 .

[0181] Step 730: The first network element control plane sends the first network element identifier and the third random number to the mobile network control plane.

[0182] Optionally, the first network element identifier is used to uniquely identify the first network element. The third random number is a 16-octet random number generated at a control plane of the first network element.

[0183] Step 740: The mobile network controls the sending of the first network element identifier and the third random number to the terminal device.

[0184] After receiving the first network element identifier and the third random number sent by the first network element control plane, the mobile network control plane forwards the first network element identifier and the third random number to the terminal device.

[0185] Step 750: The terminal device determines third summary information.

[0186] The third summary information is verification information generated by the terminal device according to the received third random number.

[0187] Optionally, after receiving the first network element identifier and the third random number, the terminal device first confirms the identity information of the first network element according to the first network element identifier, and determines that the first network element is a server requiring MBS service.

[0188] Optionally, the process of the terminal determining the third summary information includes: determining sixth key information according to the first network element identifier and the third random number, determining seventh key information according to the sixth key information, and determining third summary information according to the seventh key information and the third random number.

[0189] Step 760: The terminal device sends the third summary information and the fourth random number to the first network element control plane.

[0190] Optionally, the fourth random number is a 16-octet random number generated at the terminal device.

[0191] Step 770: The first network element control plane verifies the third summary information.

[0192] The first network element control plane verifies the third summary information according to the seventh key information.

[0193] Optionally, the process of the first network element control plane verifying the third summary information includes: the first network element control plane calculating the seventh key information according to the sixth key information; and the first network element control plane verifying the third summary information according to the third random number and the seventh key information.

[0194] Optionally, the sixth key information is a shared key between the terminal device and the first network element control plane. The sixth key information needs to be derived based on the eighth key information, and the sixth key information is used to derive the seventh key information.

[0195] In one implementation, if the service registration request forwarded by the mobile network control plane and received by the first network element control plane does not include the eighth key information, the mobile network control plane calculates the sixth key information; the mobile network control plane sends the sixth key information to the first network element control plane; and the first network element control plane receives the sixth key information. In another implementation, if the service registration request forwarded by the mobile network control plane and received by the first network element control plane includes the eighth key information, the first network element control plane calculates the sixth key information based on the eighth key information.

[0196] Step 780: The first network element control plane sends fourth summary information.

[0197] The fourth summary information is generated by the first network element control plane according to a fourth random number.

[0198] If the first network element successfully verifies the third summary information, the first network element control plane sends the fourth summary information to the terminal device. Optionally, the first network element control plane also sends a second verification success message.

[0199] Step 790: The terminal device verifies the fourth summary information.

[0200] The terminal device receives the fourth summary information fed back by the first network element control plane. The terminal device verifies the fourth summary information according to the fourth random number. If the verification is successful, the service registration process of the terminal device is completed.

[0201] Step 7100: The control plane of the first network element sends a second verification success message.

[0202] The second verification success message is used to indicate that the first verification request is successful.

[0203] Below, the above-mentioned request authentication process is exemplarily explained with the mobile network control plane including AMF and the first network element control plane including MBSF.

[0204] After service registration is completed, if the terminal device wishes to join an MBS session, it sends an MSK request to the MBSF. Specifically, depending on whether the request message received by the MBSF contains Ks, two different situations can trigger the request authentication process for the service key MSK.

[0205] Combined with reference Figure 8 , Figure 8 A flowchart of a method for requesting authentication provided by an exemplary embodiment of the present application is shown. In this embodiment, the first verification request does not include Ks (i.e., the eighth key information), and the method includes:

[0206] Step 810: The terminal device sends a first verification request to the AMF.

[0207] The first verification request includes B-TID and MSK ID, wherein B-TID represents the identity information generated by the terminal device through the GBA mechanism, and MSK ID is the MSK key ID.

[0208] Step 820: AMF sends a first verification request to MBSF.

[0209] After receiving the first verification request from the terminal device, the AMF first checks the validity period of the B-TID. If it is determined that the B-TID is within the validity period and the key corresponding to the B-TID is also within the validity period, it forwards the first verification request to the MBSF. The forwarded first verification request contains the B-TID and the MSK ID. The B-TID represents the identity information generated by the terminal device through the GBA mechanism, and the MSK ID is the MSK key ID.

[0210] After receiving the first verification request, MBSF checks whether Ks_xx_NAF is expired. If not, the process jumps to step 8110 ; if expired, the process jumps to step 830 and executes steps 830 to 8100 .

[0211] Step 830: MBSF sends MBSF_ID and nonce1 to AMF.

[0212] After receiving the service authentication request forwarded by AMF, MBSF sends MBSF_ID (i.e., the first network element identifier) ​​and nonce1 (i.e., the third random number) to AMF, where MBSF_ID is the identity information of MBSF and nonce1 is a random number.

[0213] In step 840, the AMF calculates Ks_xx_NAF.

[0214] After receiving the above message, the AMF calculates the key Ks_xx_NAF (i.e., the sixth key information) according to the random number nonce1.

[0215] Optionally, Ks_xx_NAF=KDF(KAMF, "gba_xx_NAF", nonce1, SUPI, MBSF_ID), where KAMF is the shared key between the terminal device and AMF, "gba_xx_NAF" is a GBA process parameter, SUPI is the user's real identity, nonce1 is a random number, and MBSF_ID is the identity information of MBSF.

[0216] Optionally, the AMF also calculates the user key file, bootstrap time and key period.

[0217] In step 850, the AMF forwards the received MBSF_ID and nonce1 to the terminal device.

[0218] MBSF_ID is the identity information of MBSF, and nonce1 is a random number.

[0219] Step 860: The terminal device calculates MRK and MUK.

[0220] After the terminal device receives the message forwarded by AMF, it first checks MBSF_ID to verify whether the MBSF is the server that needs to receive the multicast message. If the verification is successful, it calculates MRK (i.e., the seventh key information) and MUK based on Ks_xx_NAF.

[0221] In step 870, the AMF sends the calculated Ks_xx_NAF to the MBSF.

[0222] Optionally, the AMF also sends the calculated user key file, bootstrap time and key period to the MBSF.

[0223] Step 880: The terminal device calculates and sends the digest RES and the random number nonce2.

[0224] Optionally, RES=f2(MRK, nonce1, B-TID) (ie, the third summary information), and nonce2 is a fourth random number.

[0225] In step 890, MBSF calculates MRK, MUK and verifies the digest.

[0226] MBSF calculates MRK and MUK based on Ks_xx_NAF received from AMF, and then verifies whether the terminal device's summary RES is legal through the calculated MRK and MUK.

[0227] Step 8100, MBSF calculates and sends the summary RES*.

[0228] If RES verification is successful, the MBSF sends a verification success flag to the terminal device, calculates the digest RES*=f2(MRK, nonce2, B-TID), and then sends RES* (i.e., the fourth digest information) to the terminal device in response to the terminal device's challenge, completing the terminal device's request authentication process.

[0229] Step 8110: MBSF sends a verification success flag to the terminal device.

[0230] Combined with reference Figure 9 , Figure 9 A flowchart of a method for requesting authentication provided by an exemplary embodiment of the present application is shown. In this embodiment, the first verification request includes Ks (i.e., the eighth key information), and the method includes:

[0231] Step 910: The terminal device sends a first verification request to the AMF.

[0232] The first verification request includes B-TID and MSK ID, wherein B-TID represents the identity information generated by the terminal device through the GBA mechanism, and MSK ID is the MSK key ID.

[0233] Step 920: AMF sends a first verification request to MBSF.

[0234] After receiving the first verification request from the terminal device, the AMF first checks the validity period of the B-TID. If it determines that the B-TID is within the validity period and the key corresponding to the B-TID is also within the validity period, it forwards the first verification request to the MBSF. The forwarded first verification request contains the B-TID, MSK ID, and Ks. The B-TID represents the identity information of the terminal device generated by the GBA mechanism, the MSK ID is the MSK key ID, and Ks is the shared key formed between the terminal device and the network side based on the GBA mechanism.

[0235] After receiving the first verification request, the MBSF checks whether Ks_xx_NAF is expired. If not, the process jumps to step 990 ; if expired, the process jumps to step 930 and executes steps 930 to 980 .

[0236] Step 930: MBSF sends MBSF_ID and nonce1 to AMF.

[0237] After receiving the first verification request forwarded by AMF, MBSF sends MBSF_ID (i.e., the first network element identifier) ​​and nonce1 (i.e., the third random number) to AMF, where MBSF_ID is the identity information of MBSF and nonce1 is a random number.

[0238] In step 940, the AMF forwards the received MBSF_ID and nonce1 to the terminal device.

[0239] MBSF_ID is the identity information of MBSF, and nonce1 is a random number;

[0240] Step 950: The terminal device calculates MRK and MUK.

[0241] After the terminal device receives the message forwarded by AMF, it first checks MBSF_ID to verify whether the MBSF is the server that needs to receive the multicast message. If the verification is successful, the MRK (i.e., the seventh key information) and MUK are calculated based on Ks_xx_NAF (i.e., the sixth key information).

[0242] Optionally, Ks_xx_NAF includes one of Ks_ext_NAF and Ks_int_NAF. Specifically, Ks_ext_NAF = KDF(Ks, "gba-ne", nonce1, SUPI, MBSF_ID), and Ks_int_NAF = KDF(Ks, "gba-u", nonce1, SUPI, MBSF_ID). Ks is a shared key formed between the terminal device and the network side based on the GBA mechanism, "gba-me" and "gba-u" are GBA process parameters, nonce1 is a random number, SUPI is the user's real identity, and MBSF_ID is the identity information of the MBSF.

[0243] Step 960: The terminal device calculates and sends the digest RES and the random number nonce2.

[0244] Optionally, RES=f2(MRK, nonce1, B-TID) (ie, the third summary information), and nonce2 is a fourth random number.

[0245] In step 970, MBSF calculates MRK, MUK and verifies the digest.

[0246] MBSF first calculates Ks_xx_NAF, then calculates MRK and MUK based on Ks_xx_NAF, and then verifies whether the terminal device's summary RES is legal through the calculated MRK and MUK.

[0247] Step 980: MBSF calculates and sends the summary RES*.

[0248] If the verification is successful, the MBSF sends a verification success flag to the terminal device, calculates the digest RES*=f2(MRK, nonce2, B-TID), and then sends RES* (i.e., the fourth digest information) to the terminal device in response to the terminal device's challenge, completing the terminal device's request authentication process.

[0249] Step 990: MBSF sends a verification success flag to the terminal device.

[0250] Key issuance process

[0251] Figure 10 A flowchart of a key distribution process provided by an exemplary embodiment of the present application is shown, and the method includes:

[0252] Step 1010: The first network element controls sending a first key to the terminal device.

[0253] Optionally, the first key is used to encrypt the second key.

[0254] Step 1020: The terminal device sends a first confirmation message to the first network element control plane.

[0255] The first confirmation message is used to indicate that the terminal device has successfully received the first key.

[0256] Step 1030: The first network element control plane sends the first key to the first network element user plane.

[0257] Step 1040: The first network element controls sending the second key to the terminal device.

[0258] Optionally, the second key is used to encrypt MBS service data transmission.

[0259] Step 1050: The terminal device sends a second confirmation message to the control plane of the first network element.

[0260] The second confirmation message is used to indicate that the terminal device has successfully received the second key.

[0261] Step 1060: The control plane of the first network element sends the second key to the user plane of the first network element.

[0262] Optionally, after receiving the second key sent down, the user plane of the first network element uses the second key to encrypt data and sends the data to the terminal device.

[0263] In the following, the key issuance process is exemplarily described with the case where the first network element control plane includes the MBSF and the first network element user plane includes the MBSU.

[0264] After MBSF successfully authenticates the terminal device, MBSF stores the terminal device information to indicate that the terminal device is successfully authenticated. Then the MSK and MTK distribution processes are executed in sequence, such as Figure 11 After the delivery is completed, the MBSU uses the traffic key MTK to encrypt the multicast data and forwards it through the multimedia multicast user plane function MB-UPF.

[0265] Combined with reference Figure 11 , Figure 11 A method flow chart of a key distribution process provided by an exemplary embodiment of the present application is shown.

[0266] Step 1110 , the MBSF generates an MSK for the MSK_ID of the successful MSK request.

[0267] After MBSF successfully authenticates the MSK request of the terminal device (ie, the first verification request), MBSF generates a service key MSK for the MSK_ID of the successful MSK request.

[0268] Step 1120: MBSF sends the MSK to the terminal device.

[0269] Among them, MSK is encrypted and protected by MUK.

[0270] Step 1130: When the terminal device successfully receives the MSK, the terminal device returns an ACK to the MBSF.

[0271] Optionally, when the terminal device fails to successfully receive the MSK, the terminal device returns a NACK to the MBSF, and the MBSF needs to resend the MSK to the terminal device.

[0272] Step 1140: MBSF sends the MSK to MBSU.

[0273] The issued MSK includes the MSK and the corresponding MSK_ID.

[0274] Step 1150: MBSF generates MTK_ID and corresponding MTK.

[0275] MTK is used to encrypt multicast data.

[0276] Step 1160: MBSF sends MTK to the terminal device.

[0277] Among them, MTK is protected by MSK.

[0278] Step 1170: When the terminal device successfully receives the MTK, the terminal device returns an ACK to the MBSF.

[0279] Optionally, when the terminal device fails to successfully receive the MTK, the terminal device returns a NACK to the MBSF, and the MBSF needs to resend the MTK to the terminal device.

[0280] Step 1180: MBSF sends MTK to MBSU.

[0281] Optionally, the MBSF instructs the MBSU to use the delivered traffic key MTK to encrypt the multicast data, thereby completing the delivery process of the MSK and MTK.

[0282] Figure 12 A network deployment diagram including a multicast service function provided by an exemplary embodiment of the present application is shown.

[0283] The terminal device is connected to 5G-RAN through the Uu interface; 5G-RAN is connected to UPF through the N3 interface; 5G-RAN is connected to AMF through the N2 interface; UPF is connected to MBSU through the N6 interface; AMF is connected to MBSF through the N6mb-c interface; MBSU is connected to MBSF through the Ny interface.

[0284] In such Figure 12 In the network deployment shown, Figure 13 A system architecture diagram including a multicast service function provided by an exemplary embodiment of the present application is shown.

[0285] As a user device, UE applies for registration of MBS services in the 5G network, requests MSK, and serves as the object of key distribution.

[0286] 5G-RAN serves as the 5G access network, connecting terminal devices with the network side.

[0287] AMF is the access and mobility management function in the 5G core network, deployed uniformly with SEAF. It is mainly responsible for the GBA server function and initiating authentication or forwarding authentication requests to the MBS server in the MBS service process.

[0288] MBSF is a multicast broadcast service function. In this architecture, it serves as an MBS server and is a new network function used to process the control plane signaling part to meet the service layer functions in transmission-only mode and full service mode. It is mainly responsible for mutual authentication with the UE in the MBS service registration process and the MSK request authentication process. In the key distribution process, it is responsible for generating the service key MSK and traffic key MTK for the UE that successfully applies for the service key MSK.

[0289] MBSU stands for Multicast Broadcast Service User Plane. It is a new entity that handles the load part to cater to the service layer functions. It is a new network function that is mainly responsible for encrypting multicast data using the traffic key MTK and forwarding it by the Multimedia Multicast User Plane Function MB-UPF.

[0290] Below, in Figure 12 Under the network deployment shown, the parameters and network elements involved in each process in the above embodiment are explained.

[0291] Service registration process

[0292] Table 1-1: Meaning of service registration process parameters

[0293]

[0294] Table 1-2: Network element functions in the service registration process

[0295]

[0296] Request certification process

[0297] Table 2-1: Meaning of parameters in the authentication request process

[0298]

[0299]

[0300] Table 2-2: Network element functions in the authentication request process

[0301]

[0302] Key distribution process

[0303] Parameter name Parameter meaning MSK Service key, mainly used to encrypt MTK. MSKID MSK key ID, used to identify the MSK. MRK Requesting a key mainly involves authenticating the UE during the UE's key request process. MUK User key, mainly used to encrypt MSK. MTK Traffic key, mainly used to encrypt MBS service data transmission. MTKID MTK key ID, used to identify MTK.

[0304] Table 3-2: Network element functions in the key distribution process

[0305]

[0306] Figure 14 A structural block diagram of a multimedia broadcast multicast service authentication device provided by an exemplary embodiment of the present application is shown, and the device includes: a transceiver module 1410;

[0307] The transceiver module 1410 is configured to interact with the first network element control plane through NAS messages via the mobile network control plane, where the interaction is used to complete at least one of the following processes: a service registration process, an authentication request process, and a key distribution process;

[0308] At least one of the service registration process, the authentication request process, and the key distribution process is used for the MBMS service.

[0309] Optionally, the transceiver module 1410 includes a sending submodule 1411 , a receiving submodule 1412 , a determining submodule 1413 and a verifying submodule 1414 .

[0310] In an optional embodiment, the sending submodule 1411 is configured to add the content exchanged with the first network element control plane into a container, and transmit the container through the mobile network control plane.

[0311] In an optional embodiment, the sending submodule 1411 is configured to send a service registration request to the mobile network control plane, and the service registration request is used to register the terminal device; the receiving submodule 1412 is configured to receive a first verification success message sent by the first network element control plane after the first network element control plane receives the service registration request forwarded by the mobile network control plane, and the first verification success message is used to indicate that the service registration process corresponding to the service registration request is successful.

[0312] In an optional embodiment, the sending submodule 1411 is configured to send a first verification request to the mobile network control plane, where the first verification request is used to request to obtain a first key; the receiving submodule 1412 is configured to receive a second verification success message sent by the first network element control plane after the first network element control plane receives the first verification request forwarded by the mobile network control plane, where the second verification success message is used to indicate that the first verification request is successfully verified.

[0313] In an optional embodiment, the receiving submodule 1412 is configured to receive a first key and a second key sent by the control plane of the first network element; the first key is used to protect the second key, and the second key is used for data transmission between the terminal device and the user plane of the first network element.

[0314] In an optional embodiment, the receiving submodule 1412 is configured to receive a first network element identifier and a first random number forwarded by the mobile network control plane from the first network element control plane; the determining submodule 1413 is configured to determine, based on the first network element identifier, that the first network element is a server requiring MBS service; the determining submodule 1413 is configured to determine, based on the first network element identifier and the first random number, the third key information, the fourth key information based on the third key information, and the first summary information based on the fourth key information and the first random number; the sending submodule 1411 is configured to send the first summary information and the second random number to the first network element control plane.

[0315] In an optional embodiment, the receiving submodule 1412 is configured to receive second summary information fed back by the first network element control plane, where the second summary information is generated by the first network element control plane based on a second random number; the verification submodule 1414 is configured to verify the second summary information to complete the service registration process of the terminal device.

[0316] In an optional embodiment, the service registration request forwarded by the mobile network control plane received by the first network element control plane does not include the fifth key information, and the fifth key information is used to derive the third key information; or, the service registration request forwarded by the mobile network control plane received by the first network element control plane includes the fifth key information.

[0317] In an optional embodiment, the receiving submodule 1412 is configured to receive a second verification success message sent by the first network element control plane when the first verification request is successfully verified.

[0318] In an optional embodiment, the receiving submodule 1412 is configured to receive the first network element identifier and the third random number forwarded by the mobile network control plane from the first network element control plane when the first verification request fails; the determining submodule 1413 is configured to determine, based on the first network element identifier, that the first network element is a server requiring MBS service; the determining submodule 1413 is configured to determine the sixth key information based on the first network element identifier and the third random number, determine the seventh key information based on the sixth key information, and determine the third summary information based on the seventh key information and the third random number; the sending submodule 1411 is configured to send the third summary information and the fourth random number to the first network element control plane.

[0319] In an optional embodiment, the receiving submodule 1412 is configured to receive the fourth summary information fed back by the first network element control plane, where the fourth summary information is generated by the first network element control plane based on a fourth random number; the verification submodule 1414 is configured to verify that the fourth summary information is successful, thereby completing the verification process of the first verification request of the terminal device.

[0320] In an optional embodiment, the first verification request forwarded by the mobile network control plane received by the first network element control plane does not include the eighth key information, and the eighth key information is used to derive the sixth key information; or, the first verification request forwarded by the mobile network control plane received by the first network element control plane includes the eighth key information.

[0321] In an optional embodiment, the sending submodule 1411 is configured to feed back a first confirmation message to the first network element control plane, where the first confirmation message is used to indicate that the terminal device has successfully received the first key; the sending submodule 1411 is configured to feed back a second confirmation message to the first network element control plane, where the second confirmation message is used to indicate that the terminal device has successfully received the second key.

[0322] In an optional embodiment, the mobile network control plane includes at least one of an AMF network element, an SMF network element, an AUSF network element, and a SEAF network element; the first network element control plane includes an MBSF network element.

[0323] Figure 15 A structural block diagram of a multimedia broadcast multicast service authentication device provided by an exemplary embodiment of the present application is shown, wherein the device includes a mobile network control plane module 1501, a first network element control plane module 1502, and a first network element user plane module 1503;

[0324] The first network element control plane module 1502 interacts with the terminal device through the mobile network control plane module 1501 through NAS messages, and the interaction is used to complete at least one of the following processes: service registration process, authentication request process, and key distribution process;

[0325] At least one of the service registration process, the authentication request process, and the key distribution process is used for the MBMS service.

[0326] In an optional embodiment, the first network element control plane module 1502 adds the content interacted with the terminal device into a container, and transmits the container through the mobile network control plane module 1501 .

[0327] In an optional embodiment, the mobile network control plane module 1501 is configured to receive a service registration request sent by a terminal device, and the service registration request is used to register the terminal device; the mobile network control plane module 1501 is configured to forward the service registration request to the first network element control plane module 1502; the first network element control plane module 1502 is configured to send a first verification success message to the terminal device, and the first verification success message is used to indicate that the registration process corresponding to the service registration request is successful.

[0328] In an optional embodiment, the mobile network control plane module 1501 is configured to receive a first verification request sent by the terminal device, where the first verification request is used to request the acquisition of a first key; the mobile network control plane module 1501 is configured to forward the first verification request to the first network element control plane module 1502; the first network element control plane module 1502 is configured to send a second verification success message to the terminal device, where the second verification success message is used to indicate that the first verification request is successfully verified.

[0329] In an optional embodiment, the first network element control plane module 1502 is configured to send a first key and a second key to the terminal device and the first network element user plane module 1503, the first key is used to protect the second key, and the second key is used for data transmission between the terminal device and the first network element user plane module 1503.

[0330] In an optional embodiment, the first network element control plane module 1502 is configured to send a first network element identifier and a first random number to the mobile network control plane module 1501; the mobile network control plane module 1501 is configured to forward the first network element identifier and the first random number to the terminal device; the first network element control plane module 1502 is configured to receive first summary information and a second random number sent by the terminal device, the first summary information being generated by the terminal device based on the first random number; the first network element control plane module 1502 is configured to verify the first summary information based on the fourth key information.

[0331] In an optional embodiment, when the first digest verification is successful, the first network element control plane module 1502 is configured to feed back a first verification success message and second digest information to the terminal device, where the second digest information is generated by the first network element control plane module 1502 based on a second random number.

[0332] In an optional embodiment, the first network element control plane module 1502 is configured to calculate the fourth key information based on the third key information; the first network element control plane module 1502 is configured to verify the first summary information based on the first random number and the fourth key information.

[0333] In an optional embodiment, the service registration request forwarded by the mobile network control plane module 1501 and received by the first network element control plane module 1502 does not include the fifth key information, and the fifth key information is used to derive the third key information; the mobile network control plane module 1501 is configured to calculate the third key information; the mobile network control plane module 1501 is configured to send the third key information to the first network element control plane module 1502; the first network element control plane module 1502 is configured to receive the third key information.

[0334] In an optional embodiment, the service registration request forwarded by the mobile network control plane module 1501 and received by the first network element control plane module 1502 includes fifth key information; the first network element control plane module 1502 is configured to calculate third key information based on the fifth key information.

[0335] In an optional embodiment, the first network element control plane module 1502 is configured to verify the first verification request, and if the first verification request is successfully verified, feed back a second verification success message to the terminal device.

[0336] In an optional embodiment, the first network element control plane module 1502 is configured to verify the first verification request, and if the first verification request fails, send the first network element identifier and the third random number to the mobile network control plane module 1501; the mobile network control plane module 1501 is configured to forward the first network element identifier and the third random number to the terminal device; the first network element control plane module 1502 is configured to receive the third summary information and the fourth random number sent by the terminal device, and the third summary information is generated by the terminal device based on the third random number; the first network element control plane module 1502 is configured to verify the third summary information based on the seventh key information; if the third summary information is successfully verified, the first network element control plane module 1502 is configured to feedback the fourth summary information to the terminal device, and the fourth summary information is generated based on the fourth random number.

[0337] In an optional embodiment, the first network element control plane module 1502 is configured to calculate the seventh key information based on the sixth key information; the first network element control plane module 1502 is configured to verify the third summary information based on the third random number and the seventh key information.

[0338] In an optional embodiment, the first verification request forwarded by the mobile network control plane received by the first network element control plane does not include the eighth key information, and the eighth key information is used to derive the sixth key information; the mobile network control plane module 1501 is configured to calculate the sixth key information; the mobile network control plane module 1501 is configured to send the sixth key information to the first network element control plane; the first network element control plane module 1502 is configured to receive the sixth key information.

[0339] In an optional embodiment, the first verification request forwarded by the mobile network control plane received by the first network element control plane includes eighth key information, and the eighth key information is used to derive sixth key information; the first network element control plane module 1502 is configured to calculate the sixth key information based on the eighth key information.

[0340] In an optional embodiment, the first network element control plane module 1502 is configured to generate a first key and send the first key to the terminal device; the first network element control plane module 1502 is configured to receive a first confirmation message fed back by the terminal device, and the first confirmation message is used to indicate that the terminal device has successfully received the first key; the first network element control plane module 1502 is configured to send the first key to the first network element user plane module 1503; the first network element control plane generates a second key; the first network element control plane module 1502 is configured to send the second key to the terminal device; the first network element control plane module 1502 is configured to receive a second confirmation message fed back by the terminal device, and the second confirmation message is used to indicate that the terminal device has successfully received the second key; the first network element control plane module 1502 is configured to send the second key to the first network element user plane module 1503.

[0341] In an optional embodiment, the first network element user plane module 1503 is configured to encrypt data using the second key and send the data to the terminal device.

[0342] In an optional embodiment, the mobile network control plane module 1501 includes at least one of an AMF network element module, an SMF network element module, an AUSF network element module, and a SEAF network element module; the first network element control plane module 1502 includes an MBSF network element module; and the first network element user plane module 1503 includes an MBSU network element module.

[0343] Figure 16 A schematic structural diagram of a terminal device provided by an exemplary embodiment of the present application is shown. The terminal device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104 and a bus 105.

[0344] The processor 101 includes one or more processing cores. The processor 101 executes various functional applications and information processing by running software programs and modules.

[0345] The receiver 102 and the transmitter 103 may be implemented as a communication component, which may be a communication chip.

[0346] The memory 104 is connected to the processor 101 via a bus 105 .

[0347] The memory 104 may be used to store at least one instruction, and the processor 101 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[0348] In addition, the memory 104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).

[0349] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction, at least one program, code set or instruction set is stored. The at least one instruction, the at least one program, the code set or instruction set is loaded and executed by a processor to implement the multimedia broadcast multicast service authentication method provided by the above-mentioned various method embodiments and executed by the terminal device.

[0350] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

[0351] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A multimedia broadcast multicast service authentication method, characterized in that: Applied in a terminal device, the method comprises: The terminal device interacts with the first network element control plane through a non-access layer NAS message through the mobile network control plane, and the interaction is used to complete the following processes: service registration process, authentication request process and key distribution process; The service registration process, the authentication request process and the key distribution process are used for the multimedia broadcast multicast service MBMS service; The service registration process includes: Sending a service registration request to the mobile network control plane, where the service registration request is used to register the terminal device; After the first network element control plane receives the service registration request forwarded by the mobile network control plane, receiving a first verification success message sent by the first network element control plane, where the first verification success message is used to indicate that a service registration process corresponding to the service registration request is successful; The method further comprises: receiving a first network element identifier and a first random number forwarded by the mobile network control plane from the first network element control plane; determining, according to the first network element identifier, that the first network element is a server requiring a multicast broadcast service MBS service; Determine third key information according to the first network element identifier and the first random number, determine fourth key information according to the third key information, and determine first summary information according to the fourth key information and the first random number; Send the first summary information and the second random number to the first network element control plane.

2. The method according to claim 1, characterized in that The terminal device interacts with the first network element control plane through a non-access layer NAS message through the mobile network control plane, including: The terminal device adds the content interacted with the first network element control plane into a container, and transmits the container through the mobile network control plane.

3. The method according to claim 1, characterized in that: The authentication request process includes: Sending a first verification request to the mobile network control plane, where the first verification request is used to request to obtain a first key; After the first network element control plane receives the first verification request forwarded by the mobile network control plane, a second verification success message sent by the first network element control plane is received, where the second verification success message is used to indicate that the first verification request is successfully verified.

4. The method according to claim 1, characterized in that: The key distribution process includes: Receiving a first key and a second key sent by the control plane of the first network element; The first key is used to protect the second key, and the second key is used for data transmission between the terminal device and the user plane of the first network element.

5. The method according to claim 1, characterized in that The method further comprises: receiving second summary information fed back by the first network element control plane, where the second summary information is generated by the first network element control plane according to the second random number; The second summary information is verified to complete the service registration process of the terminal device.

6. The method according to claim 1, characterized in that The service registration request does not include fifth key information, and the fifth key information is used to derive the third key information; Or, the service registration request includes the fifth key information.

7. The method according to claim 3, characterized in that The receiving a second verification success message sent by the first network element control plane includes: When the first verification request is successfully verified, the second verification success message sent by the first network element control plane is received.

8. The method according to claim 3, characterized in that The method further comprises: In case that the first verification request fails to be verified, receiving a first network element identifier and a third random number forwarded by the mobile network control plane from the first network element control plane; Determining, according to the first network element identifier, that the first network element is a server requiring MBS service; Determine sixth key information according to the first network element identifier and the third random number, determine seventh key information according to the sixth key information, and determine third summary information according to the seventh key information and the third random number; Send the third summary information and the fourth random number to the first network element control plane.

9. The method according to claim 8, characterized in that The method further comprises: receiving fourth summary information fed back by the first network element control plane, where the fourth summary information is generated by the first network element control plane according to the fourth random number; The fourth summary information is verified successfully, completing the verification process of the first verification request of the terminal device.

10. The method according to claim 8, characterized in that The first verification request does not include eighth key information, and the eighth key information is used to derive the sixth key information; Or, the first verification request includes the eighth key information.

11. The method according to claim 4, characterized in that The method further comprises: Feedback a first confirmation message to the first network element control plane, where the first confirmation message is used to indicate that the terminal device has successfully received the first key; A second confirmation message is fed back to the first network element control plane, where the second confirmation message is used to indicate that the terminal device has successfully received the second key.

12. The method according to any one of claims 1 to 11, characterized in that: The mobile network control plane includes an access and mobility management function AMF network element; The first network element control plane includes a multimedia broadcast service function MBSF network element.

13. A multimedia broadcast multicast service authentication method, characterized in that: Applied in a communication system, the communication system includes a mobile network control plane, a first network element control plane, and a first network element user plane, the method includes: The first network element control plane interacts with the terminal device through the mobile network control plane through a non-access layer NAS message, and the interaction is used to complete the following processes: service registration process, authentication request process and key distribution process; The service registration process, the authentication request process and the key distribution process are used for the multimedia broadcast multicast service MBMS service; The service registration process includes: The mobile network control plane receives the service registration request sent by the terminal device, where the service registration request is used to register the terminal device; The mobile network control plane forwards the service registration request to the first network element control plane; The first network element controls the sending of a first verification success message to the terminal device, where the first verification success message is used to indicate that a service registration process corresponding to the service registration request is successful; Wherein, the method further comprises: The first network element control plane sends a first network element identifier and a first random number to the mobile network control plane; The mobile network controls forwarding the first network element identifier and the first random number to the terminal device, wherein the first network element identifier is used to determine that the first network element is a server requiring a multicast broadcast service MBS service; The first network element control plane receives first summary information and a second random number sent by the terminal device, where the first summary information is generated by the terminal device according to the first random number and fourth key information, the fourth key information is determined by the terminal device according to third key information, and the third key information is determined by the terminal device according to the first network element identifier and the first random number; The first network element control plane verifies the first summary information according to the fourth key information.

14. The method according to claim 13, characterized in that The first network element control plane interacts with the terminal device through a non-access layer NAS message through the mobile network control plane, including: The first network element control plane adds the content interacted with the terminal device into a container, and transmits the container through the mobile network control plane.

15. The method according to claim 13, characterized in that The authentication request process includes: The mobile network control plane receives a first verification request sent by the terminal device, where the first verification request is used to request to obtain a first key; The mobile network control plane forwards the first verification request to the first network element control plane; The first network element controls the sending of a second verification success message to the terminal device, where the second verification success message is used to indicate that the first verification request is successfully verified.

16. The method according to claim 13, characterized in that The key distribution process includes: The first network element control plane sends a first key and a second key to the terminal device and the first network element user plane respectively, the first key is used to protect the second key, and the second key is used for data transmission between the terminal device and the first network element user plane.

17. The method according to claim 13, characterized in that The first network element controls the sending of a first verification success message to the terminal device, including: When the first summary information is successfully verified, the first network element control plane feeds back the first verification success message and second summary information to the terminal device, where the second summary information is generated by the first network element control plane according to the second random number.

18. The method according to claim 13, characterized in that The first network element control plane verifies the first summary information according to the fourth key, including: The first network element control plane calculates the fourth key information according to the third key information; The first network element control plane verifies the first summary information according to the first random number and the fourth key information.

19. The method according to claim 18, characterized in that The service registration request does not include fifth key information, and the fifth key information is used to derive the third key information. The method further includes: The mobile network control plane calculates the third key information; The mobile network control plane sends the third key information to the first network element control plane; The first network element control plane receives the third key information.

20. The method according to claim 18, characterized in that The service registration request includes fifth key information, where the fifth key information is used to derive the third key information. The method further includes: The first network element control plane calculates the third key information according to the fifth key information.

21. The method according to claim 15, characterized in that The first network element controls the sending of a second verification success message to the terminal device, including: The first network element control surface verifies the first verification request, and if the first verification request is successfully verified, feeds back the second verification success message to the terminal device.

22. The method according to claim 15, characterized in that The method further comprises: The first network element control plane verifies the first verification request, and when the verification of the first verification request fails, sends the first network element identifier and the third random number to the mobile network control plane; The mobile network controls forwarding of the first network element identifier and the third random number to the terminal device; The first network element control plane receives third summary information and a fourth random number sent by the terminal device, where the third summary information is generated by the terminal device according to the third random number; The first network element control plane verifies the third summary information according to the seventh key information; When the third summary information is successfully verified, the first network element controls the terminal device to feedback fourth summary information, where the fourth summary information is generated according to the fourth random number.

23. The method according to claim 22, characterized in that The first network element control plane verifies the third summary information according to the seventh key information, including: The first network element control plane calculates the seventh key information according to the sixth key information; The first network element control plane verifies the third summary information according to the third random number and the seventh key information.

24. The method according to claim 23, characterized in that The first verification request does not include eighth key information, and the eighth key information is used to derive the sixth key information. The method further includes: The mobile network control plane calculates the sixth key information; The mobile network control plane sends the sixth key information to the first network element control plane; The first network element control plane receives the sixth key information.

25. The method according to claim 23, characterized in that The first verification request includes eighth key information, and the eighth key information is used to derive the sixth key information. The method further includes: The first network element control plane calculates the sixth key information according to the eighth key information.

26. The method according to claim 16, characterized in that The first network element control plane sends a first key and a second key to the terminal device and the first network element user plane respectively, including: The first network element control plane generates the first key, and sends the first key to the terminal device; The first network element control plane receives a first confirmation message fed back by the terminal device, where the first confirmation message is used to indicate that the terminal device successfully receives the first key; The first network element control plane sends the first key to the first network element user plane; The first network element control plane generates the second key, and sends the second key to the terminal device; The first network element control plane receives a second confirmation message fed back by the terminal device, where the second confirmation message is used to indicate that the terminal device successfully receives the second key; The first network element control plane sends the second key to the first network element user plane.

27. The method according to claim 26, characterized in that The method further comprises: The first network element user plane encrypts data using the second key and sends the data to the terminal device.

28. The method according to any one of claims 13 to 27, characterized in that: The mobile network control plane includes an access and mobility management function AMF network element; The first network element control plane includes a multimedia broadcast service function MBSF network element; The first network element user plane includes a multimedia broadcast service user plane MBSU network element.

29. A multimedia broadcast multicast service authentication device, characterized in that: The device comprises: a transceiver module; The transceiver module is configured to interact with the first network element control plane through a non-access layer NAS message through the mobile network control plane, and the interaction is used to complete the following processes: service registration process, authentication request process and key distribution process; The service registration process, the authentication request process and the key distribution process are used for the multimedia broadcast multicast service MBMS service; Wherein, the transceiver module includes a sending submodule and a receiving submodule; The sending submodule is configured to send a service registration request to the mobile network control plane, where the service registration request is used to register the terminal device; The receiving submodule is configured to receive a first verification success message sent by the first network element control plane after the first network element control plane receives the service registration request forwarded by the mobile network control plane, wherein the first verification success message is used to indicate that the service registration process corresponding to the service registration request is successful; Wherein, the transceiver module also includes a determination submodule; The receiving submodule is configured to receive a first network element identifier and a first random number forwarded by the mobile network control plane from the first network element control plane; The determining submodule is configured to determine, according to the first network element identifier, that the first network element is a server requiring a multicast broadcast service MBS service; The determination submodule is configured to determine third key information according to the first network element identifier and the first random number, determine fourth key information according to the third key information, and determine first summary information according to the fourth key information and the first random number; The sending submodule is configured to send the first summary information and the second random number to the first network element control plane.

30. The device according to claim 29, characterized in that The transceiver module includes a sending submodule; The sending submodule is configured to add the content interacted with the first network element control plane into a container, and transmit the container through the mobile network control plane.

31. The device according to claim 29, characterized in that The transceiver module includes a sending submodule and a receiving submodule; The sending submodule is configured to send a first verification request to the mobile network control plane, where the first verification request is used to request to obtain a first key; The receiving submodule is configured to receive a second verification success message sent by the first network element control plane after the first network element control plane receives the first verification request forwarded by the mobile network control plane, wherein the second verification success message is used to indicate that the first verification request is successfully verified.

32. The device according to claim 29, characterized in that The transceiver module includes a receiving submodule; the receiving submodule is configured to receive a first key and a second key sent by the first network element control plane; The first key is used to protect the second key, and the second key is used for data transmission between the terminal device and the user plane of the first network element.

33. The device according to claim 29, characterized in that The transceiver module also includes a verification submodule; The receiving submodule is configured to receive second summary information fed back by the first network element control plane, where the second summary information is generated by the first network element control plane according to the second random number; The verification submodule is configured to verify the second summary information to complete the service registration process of the terminal device.

34. The device according to claim 29, characterized in that The service registration request does not include fifth key information, and the fifth key information is used to derive the third key information; Or, the service registration request includes the fifth key information.

35. The device according to claim 31, characterized in that The receiving submodule is configured to receive the second verification success message sent by the first network element control plane when the first verification request is successfully verified.

36. The device according to claim 31, characterized in that The transceiver module also includes a determination submodule; The receiving submodule is configured to receive, when the first verification request fails to be verified, a first network element identifier and a third random number forwarded by the mobile network control plane from the first network element control plane; The determining submodule is configured to determine, according to the first network element identifier, that the first network element is a server requiring MBS service; The determining submodule is configured to determine sixth key information according to the first network element identifier and the third random number, determine seventh key information according to the sixth key information, and determine third summary information according to the seventh key information and the third random number; The sending submodule is configured to send the third summary information and the fourth random number to the first network element control plane.

37. The device according to claim 36, characterized in that The transceiver module also includes a verification submodule; The receiving submodule is configured to receive fourth summary information fed back by the first network element control plane, where the fourth summary information is generated by the first network element control plane according to the fourth random number; The verification submodule is configured to verify that the fourth summary information is successful, thereby completing the verification process of the first verification request of the terminal device.

38. The device according to claim 36, characterized in that The first verification request does not include eighth key information, and the eighth key information is used to derive the sixth key information; Or, the first verification request includes the eighth key information.

39. The device according to claim 32, characterized in that The transceiver module includes a sending submodule; The sending submodule is configured to feed back a first confirmation message to the first network element control plane, where the first confirmation message is used to indicate that the terminal device has successfully received the first key; The sending submodule is configured to feed back a second confirmation message to the first network element control plane, where the second confirmation message is used to indicate that the terminal device has successfully received the second key.

40. The device according to any one of claims 29 to 38, characterized in that The mobile network control plane includes an access and mobility management function AMF network element; The first network element control plane includes a multimedia broadcast service function MBSF network element.

41. A multimedia broadcast multicast service authentication device, characterized in that: The device comprises a mobile network control plane module, a first network element control plane module and a first network element user plane module; The first network element control plane module interacts with the terminal device through the non-access layer NAS message through the mobile network control plane module, and the interaction is used to complete the following processes: service registration process, authentication request process and key distribution process; The service registration process, the authentication request process and the key distribution process are used for the multimedia broadcast multicast service MBMS service; The mobile network control plane module is configured to receive the service registration request sent by the terminal device, where the service registration request is used to register the terminal device; The mobile network control plane module is configured to forward the service registration request to the first network element control plane module; The first network element control plane module is configured to send a first verification success message to the terminal device, where the first verification success message is used to indicate that the service registration process corresponding to the service registration request is successful; The first network element control plane module is configured to send a first network element identifier and a first random number to the mobile network control plane module; The mobile network control plane module is configured to forward the first network element identifier and the first random number to the terminal device, wherein the first network element identifier is used to determine that the first network element is a server requiring a multicast broadcast service MBS service; The first network element control plane module is configured to receive first summary information and a second random number sent by the terminal device, where the first summary information is generated by the terminal device according to the first random number and fourth key information, the fourth key information is determined by the terminal device according to third key information, and the third key information is determined by the terminal device according to the first network element identifier and the first random number; The first network element control plane module is configured to verify the first summary information according to fourth key information.

42. The device according to claim 41, characterized in that The first network element control plane module adds the content interacted with the terminal device into a container, and transmits the container through the mobile network control plane module.

43. The device according to claim 41, characterized in that The mobile network control plane module is configured to receive a first verification request sent by the terminal device, where the first verification request is used to request to obtain a first key; The mobile network control plane module is configured to forward the first verification request to the first network element control plane module; The first network element control plane module is configured to send a second verification success message to the terminal device, where the second verification success message is used to indicate that the first verification request is successfully verified.

44. The device according to claim 41, characterized in that The first network element control plane module is configured to send a first key and a second key to the terminal device and the first network element user plane module respectively, the first key is used to protect the second key, and the second key is used for data transmission between the terminal device and the first network element user plane module.

45. The device according to claim 41, characterized in that When the first summary information is successfully verified, the first network element control plane module is configured to feed back the first verification success message and second summary information to the terminal device, where the second summary information is generated by the first network element control plane module according to the second random number.

46. ​​The device according to claim 41, characterized in that The first network element control plane module is configured to calculate the fourth key information according to the third key information; The first network element control plane module is configured to verify the first summary information according to the first random number and the fourth key information.

47. The device according to claim 46, characterized in that The service registration request does not include fifth key information, and the fifth key information is used to derive the third key information; The mobile network control plane module is configured to calculate the third key information; The mobile network control plane module is configured to send the third key information to the first network element control plane module; The first network element control plane module is configured to receive the third key information.

48. The device according to claim 46, characterized in that The service registration request includes fifth key information, where the fifth key information is used to derive the third key information; The first network element control plane module is configured to calculate the third key information according to the fifth key information.

49. The device according to claim 43, characterized in that The first network element control plane module is configured to verify the first verification request, and if the first verification request is successfully verified, feedback the second verification success message to the terminal device.

50. The device according to claim 43, characterized in that The first network element control plane module is configured to verify the first verification request, and if the verification of the first verification request fails, send a first network element identifier and a third random number to the mobile network control plane module; The mobile network control plane module is configured to forward the first network element identifier and the third random number to the terminal device; The first network element control plane module is configured to receive third summary information and a fourth random number sent by the terminal device, where the third summary information is generated by the terminal device according to the third random number; The first network element control plane module is configured to verify the third summary information according to the seventh key information; In the case where the third summary information is successfully verified, the first network element control plane module is configured to feed back fourth summary information to the terminal device, where the fourth summary information is generated according to the fourth random number.

51. The device according to claim 50, characterized in that The first network element control plane module is configured to calculate the seventh key information according to the sixth key information; The first network element control plane module is configured to verify the third summary information according to the third random number and the seventh key information.

52. The device according to claim 51, characterized in that The first verification request does not include eighth key information, and the eighth key information is used to derive the sixth key information; The mobile network control plane module is configured to calculate the sixth key information; The mobile network control plane module is configured to send the sixth key information to the first network element control plane; The first network element control plane module is configured to receive the sixth key information.

53. The device according to claim 51, characterized in that The first verification request includes eighth key information, and the eighth key information is used to derive the sixth key information; The first network element control plane module is configured to calculate the sixth key information based on the eighth key information.

54. The device according to claim 44, characterized in that The first network element control plane module is configured to generate the first key and send the first key to the terminal device; The first network element control plane module is configured to receive a first confirmation message fed back by the terminal device, where the first confirmation message is used to indicate that the terminal device successfully receives the first key; The first network element control plane module is configured to send the first key to the first network element user plane module; The first network element control plane is configured to generate the second key and send the second key to the terminal device; The first network element control plane module is configured to receive a second confirmation message fed back by the terminal device, where the second confirmation message is used to indicate that the terminal device successfully receives the second key; The first network element control plane module is configured to send the second key to the first network element user plane module.

55. The device according to claim 54, characterized in that The first network element user plane module is configured to encrypt data using the second key and send the data to the terminal device.

56. The device according to any one of claims 41 to 55, characterized in that The mobile network control plane module includes an access and mobility management function AMF network element module; The first network element control plane module includes a multimedia broadcast service function MBSF network element module; The first network element user plane module includes a multimedia broadcast service user plane MBSU network element module.

57. A terminal device, characterized in that: The terminal device comprises: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the multimedia broadcast multicast service authentication method according to any one of claims 1 to 12.

58. A communication system, characterized in that: The communication system comprises: Processor and memory; The code in the memory run by the processor is provided to at least one network element in network function virtualization, and the at least one network element is used to execute the multimedia broadcast multicast service authentication method as described in any one of claims 13 to 28.

59. A computer-readable storage medium, characterized in that The readable storage medium stores executable instructions, and the executable instructions are loaded and executed by a processor to implement the multimedia broadcast multicast service authentication method according to any one of claims 1 to 12.

Citation Information

Patent Citations

  • Method, system and device for selecting network equipment

    CN101272614A

  • Method for serving multimedia broadcast / multicastservice in mobile communication system

    KR1020040084062A

  • MBMS bearer enhancements for push to talk or push to everything via embms

    US20160087810A1