Communication method, first network element, second network element, user equipment, communication system, storage medium and product

Abstract

The embodiment of the application provides a kind of communication method, first network element, second network element, user equipment, communication system, storage medium and product, it is related to communication technical field, method includes: receiving the first request sent by user equipment UE;The first request is used to request to establish first communication connection, and the first communication connection is the communication connection to be established before establishing multicast broadcast service MBS session;After the authentication result of first service providing equipment to UE about first service is authentication success, determine that the second network element will join the UE in the MBS session;The first service is the service using MBS session.Thereby UE does not need to apply to join MBS session, can be joined multicast broadcast service by first network element and second network element after authentication success, reduce the signaling interaction of network when UE joins multicast broadcast service, thereby reduce the overall signaling overhead of network.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, a first network element, a second network element, a user equipment, a communication system, a storage medium, and a product. Background Technology

[0002] With globalization and the rapid development of the maritime economy, the safety of ships at sea has become particularly important. Satellite systems for maritime distress and safety communications have the capability to provide a wide range of communication services to protect the lives of ships and crew.

[0003] Among the many communication methods in satellite systems, such as ship-to-shore advance warning, shore-to-ship distress relay warning, and shore-to-ship broadcasting of maritime safety information, Multimedia Broadcast Service (MBS) is an important service for satellite communication systems to implement these methods.

[0004] Currently, when UE (User Equipment) joins multicast services, the network suffers from significant overall signaling overhead, requiring further optimization. Summary of the Invention

[0005] This application provides a communication method, a first network element, a second network element, a user equipment, a communication system, a storage medium, and a product to address the problem of high overall signaling overhead in the network when a UE joins a multicast service.

[0006] In a first aspect, embodiments of this application provide a communication method, the method being applied to a first network element, the method comprising:

[0007] Receive a first request sent by a user equipment (UE); the first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session;

[0008] After the first service providing device successfully authenticates the UE for the first service, it determines that the second network element will add the UE to the MBS session; the first service is a service that uses the MBS session.

[0009] In some embodiments, the method further includes:

[0010] The first instruction information is obtained according to the first request; the first instruction information is used to instruct the first service providing device on the authentication result of the UE regarding the first service, wherein the authentication result is authentication success or authentication failure.

[0011] In some embodiments, obtaining the first indication information according to the first request includes:

[0012] Send a second request to the first service providing device; the second request is used to request authentication of the UE with respect to the first service.

[0013] Receive the first instruction information sent by the first service providing device.

[0014] In some embodiments, the second request includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0015] In some embodiments, the first indication information is carried in a first response, and the first response further includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0016] In some embodiments, obtaining the first indication information according to the first request includes:

[0017] According to the first request, the second network element receives a first indication information sent by the second network element. The first indication information is generated by the second network element receiving a second indication information sent by the first service providing device. The second indication information is used to indicate whether the authentication result of the first service providing device for the UE regarding the first service is successful or unsuccessful. The second indication information is received by the second network element after sending a third request to the first service providing device. The third request is used to authenticate the UE regarding the first service.

[0018] In some embodiments, determining that the second network element adds the UE to the MBS session includes:

[0019] The third indication information sent by the second network element is received; the third indication information is used to indicate that the UE has successfully joined the MBS session.

[0020] In some embodiments, determining that the second network element adds the UE to the MBS session further includes:

[0021] A fourth request is sent to the second network element; the fourth request is used to request that the UE be added to the MBS session.

[0022] In some embodiments, the first request is a registration request; the registration request is used to request registration of a communication connection; the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0023] In some embodiments, the method further includes:

[0024] Send registration acceptance information to the UE; the registration acceptance information includes fourth indication information; the fourth indication information is used to indicate that a request will be made to the first service providing device to authenticate the UE with respect to the first service;

[0025] Receive registration success information sent by the UE.

[0026] In some embodiments, the first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0027] In some embodiments, the method further includes:

[0028] Send a fifth indication message to the access network device; the fifth indication message is used to indicate the communication resources required to configure the MBS session.

[0029] Secondly, embodiments of this application provide a communication method, the method being applied to a second network element, the method comprising:

[0030] After the UE requests to establish a first communication connection and the first service providing device successfully authenticates the UE for the first service, the UE is added to the Multicast Broadcast Service (MBS) session; the first communication connection is the communication connection to be established before establishing the MBS session; the first service is the service that uses the MBS session.

[0031] In some embodiments, the method further includes:

[0032] Receive a fifth request sent by the first network element, the fifth request being used to request the establishment of a first communication connection for the UE;

[0033] A third request is sent to the first service providing device according to the fifth request; the third request is used to request authentication of the UE with respect to the first service.

[0034] The device receives a second indication message sent by the first service provider, the second indication message being used to indicate that the first service provider's authentication result for the UE regarding the first service is successful.

[0035] In some embodiments, the fifth request is a request to establish a PDU session for the UE, and the fifth request includes a first identifier; the first identifier is used to characterize the identity of the ship to which the UE is located.

[0036] In some embodiments, the third request includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0037] In some embodiments, the second indication information is carried in a second response, the second response further including a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0038] In some embodiments, the method further includes:

[0039] Send a third indication message to the first network element; the third indication message is used to indicate that the UE has successfully joined the MBS session.

[0040] In some embodiments, the method further includes:

[0041] The system receives a fourth request sent by the first network element; the fourth request is used to request that the UE be added to the MBS session.

[0042] Thirdly, embodiments of this application provide a communication method, the method being applied to a user equipment (UE), the method comprising:

[0043] Send a first request to the first network element; the first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session;

[0044] After the first service providing device successfully authenticates the UE for the first service, it receives a sixth indication message sent by the access network device; the first service is a service using an MBS session; the sixth indication message is used to indicate that the UE has joined an MBS session.

[0045] In some embodiments, the sixth indication information includes:

[0046] First type; the first type is used to characterize the service type of MBS;

[0047] First region; the first region is used to characterize the service area information of MBS.

[0048] In some embodiments, the first request is a registration request; the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0049] In some embodiments, the method further includes:

[0050] The system receives registration acceptance information sent by a first network element; the registration acceptance information includes fourth indication information; the fourth indication information is used to indicate that the system will request the first service providing device to authenticate the UE with respect to the first service.

[0051] Send a registration success message to the first network element.

[0052] In some embodiments, the first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0053] Fourthly, embodiments of this application provide a first network element, including:

[0054] The receiving module is used to receive a first request sent by the user equipment (UE); the first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session;

[0055] The processing module is configured to determine, after the first service providing device successfully authenticates the UE for the first service, that the second network element will add the UE to the MBS session; the first service is a service that uses the MBS session.

[0056] In some embodiments, the processing module is further configured to:

[0057] The first instruction information is obtained according to the first request; the first instruction information is used to instruct the first service providing device on the authentication result of the UE regarding the first service, wherein the authentication result is authentication success or authentication failure.

[0058] In some embodiments, when the processing module obtains the first indication information according to the first request, it is specifically used for:

[0059] Send a second request to the first service providing device; the second request is used to request the UE to perform authentication and authorization for the first service; receive the first instruction information sent by the first service providing device.

[0060] In some embodiments, the second request includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0061] In some embodiments, the first indication information is carried in a first response, and the first response further includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0062] In some embodiments, when the processing module obtains the first indication information according to the first request, it is specifically used for:

[0063] According to the first request, the second network element receives a first indication information sent by the second network element. The first indication information is generated by the second network element receiving a second indication information sent by the first service providing device. The second indication information is used to indicate whether the authentication result of the first service providing device for the UE regarding the first service is successful or unsuccessful. The second indication information is received by the second network element after sending a third request to the first service providing device. The third request is used to authenticate the UE regarding the first service.

[0064] In some embodiments, when determining that the second network element adds the UE to the MBS session, the processing module is specifically used for:

[0065] The third indication information sent by the second network element is received; the third indication information is used to indicate that the UE has successfully joined the MBS session.

[0066] In some embodiments, when the processing module determines that the second network element has added the UE to the MBS session, it is further configured to:

[0067] A fourth request is sent to the second network element; the fourth request is used to request that the UE be added to the MBS session.

[0068] In some embodiments, the first request is a registration request; the registration request is used to request registration of a communication connection; the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0069] In some embodiments, the first network element further includes:

[0070] The first sending module is used to send registration acceptance information to the UE; the registration acceptance information includes fourth indication information; the fourth indication information is used to indicate that a request will be made to the first service providing device to authenticate the UE with respect to the first service; and to receive registration success information sent by the UE.

[0071] In some embodiments, the first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0072] In some embodiments, the first network element further includes:

[0073] The second sending module is used to send a fifth indication message to the access network device; the fifth indication message is used to indicate the communication resources required to configure the MBS session.

[0074] Fifthly, embodiments of this application provide a second network element, including:

[0075] The processing module is used to add the UE to the Multicast Broadcast Service (MBS) session after the UE requests to establish a first communication connection and the authentication result of the first service providing device for the UE regarding the first service is successful; the first communication connection is the communication connection to be established before establishing the MBS session; the first service is the service that uses the MBS session.

[0076] In some embodiments, the processing module is further configured to:

[0077] The system receives a fifth request sent by a first network element, the fifth request being used to request the establishment of a first communication connection for the UE; sends a third request to a first service providing device according to the fifth request; the third request being used to request authentication of the UE regarding the first service; and receives a second indication information sent by the first service providing device, the second indication information being used to indicate that the authentication result of the first service providing device for the UE regarding the first service is successful.

[0078] In some embodiments, the fifth request is a request to establish a PDU session for the UE, and the fifth request includes a first identifier; the first identifier is used to characterize the identity of the ship to which the UE is located.

[0079] In some embodiments, the third request includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0080] In some embodiments, the second indication information is carried in a second response, the second response further including a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

[0081] In some embodiments, the second network element further includes:

[0082] The sending module is used to send third indication information to the first network element; the third indication information is used to indicate that the UE has successfully joined the MBS session.

[0083] In some embodiments, the second network element further includes:

[0084] The receiving module is used to receive a fourth request sent by the first network element; the fourth request is used to request that the UE be added to the MBS session.

[0085] Sixthly, embodiments of this application provide a user equipment, including:

[0086] The sending module is used to send a first request to the first network element; the first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session;

[0087] The receiving module is configured to receive a sixth indication message sent by the access network device after the authentication result of the first service providing device for the UE regarding the first service is successful; the first service is a service using an MBS session; the sixth indication message is used to indicate that the UE has joined an MBS session.

[0088] In some embodiments, the sixth indication information includes:

[0089] First type; the first type is used to characterize the service type of MBS;

[0090] First region; the first region is used to characterize the service area information of MBS.

[0091] In some embodiments, the first request is a registration request; the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0092] In some embodiments, the receiving module is further configured to:

[0093] The system receives registration acceptance information sent by a first network element; the registration acceptance information includes fourth indication information; the fourth indication information is used to indicate that the system will request the first service providing device to authenticate the UE with respect to the first service; and sends registration success information to the first network element.

[0094] In some embodiments, the first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

[0095] In a seventh aspect, embodiments of this application provide a first network element, including: a memory and a processor;

[0096] The memory stores computer-executed instructions;

[0097] The processor executes computer execution instructions stored in the memory to implement the communication method as described in any of the first aspects.

[0098] Eighthly, embodiments of this application provide a second network element, including: a memory and a processor;

[0099] The memory stores computer-executed instructions;

[0100] The processor executes computer execution instructions stored in the memory to implement the communication method as described in any of the second aspects.

[0101] Ninthly, embodiments of this application provide a user equipment, including: a memory and a processor;

[0102] The memory stores computer-executed instructions;

[0103] The processor executes computer execution instructions stored in the memory to implement the communication method as described in any of the third aspects.

[0104] In a tenth aspect, embodiments of this application provide a communication system including a first network element, a second network element, and a user equipment, wherein the first network element is configured to implement the communication method described in any one of the first aspects, the second network element is configured to implement the communication method described in any one of the second aspects, and the user equipment is configured to implement the communication method described in the third aspect.

[0105] Eleventhly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of the first, second, or third aspects.

[0106] In a twelfth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method as described in any one of the first, second, or third aspects.

[0107] In the communication method, first network element, second network element, user equipment, communication system, storage medium, and product provided in this application embodiment, the first network element receives a first request sent by the user equipment (UE). The first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session. After the first service providing device successfully authenticates the UE regarding the first service, it determines that the second network element will add the UE to the MBS session. The first service is a service that uses the MBS session. Thus, the UE does not need to apply to join the MBS session; after successful authentication, the first and second network elements can add the UE to the multicast broadcast service, reducing the network signaling interaction when the UE joins the multicast broadcast service, thereby reducing the overall network signaling overhead. Attached Figure Description

[0108] Figure 1 One of the flowcharts of the communication method provided in the embodiments of this application;

[0109] Figure 2 A second schematic flowchart illustrating the communication method provided in an embodiment of this application;

[0110] Figure 3A third schematic flowchart illustrating the communication method provided in this application embodiment;

[0111] Figure 4 A fourth schematic flowchart illustrating the communication method provided in the embodiments of this application;

[0112] Figure 5 Fifth flowchart illustrating the communication method provided in the embodiments of this application;

[0113] Figure 6 A flowchart illustrating the communication method provided in this application embodiment is shown in Figure 6.

[0114] Figure 7 Seventh schematic flowchart of the communication method provided in the embodiments of this application;

[0115] Figure 8 Eighth flowchart illustrating the communication method provided in the embodiments of this application;

[0116] Figure 9 A flowchart illustrating the communication method provided in this application embodiment is shown in Figure 9.

[0117] Figure 10 A flowchart illustrating the communication method provided in this application embodiment is shown in Figure 10.

[0118] Figure 11 Flowchart eleven of the communication method provided in the embodiments of this application;

[0119] Figure 12 Flowchart XII of the communication method provided in the embodiments of this application;

[0120] Figure 13 This is one of the structural schematic diagrams of the first network element provided in the embodiments of this application;

[0121] Figure 14 This is one of the structural schematic diagrams of the second network element provided in the embodiments of this application;

[0122] Figure 15 This is one of the structural schematic diagrams of the user equipment provided in the embodiments of this application;

[0123] Figure 16 This is the second schematic diagram of the structure of the first network element provided in the embodiments of this application;

[0124] Figure 17 This is the second schematic diagram of the structure of the second network element provided in the embodiments of this application;

[0125] Figure 18 This is a second schematic diagram of the structure of a user equipment provided in an embodiment of this application. Detailed Implementation

[0126] First, the relevant terms used in this application will be explained.

[0127] Multimedia Broadcast Service (MBS) is a service that simultaneously transmits multimedia content to multiple users via a wireless network. MBS is commonly used in mobile communication networks to improve spectrum efficiency and network resource utilization. It allows operators to provide video, audio, and other multimedia content to multiple users at the same time without needing to establish a separate connection for each user.

[0128] MSS (Maritime Ship Service) refers to a company or organization that specializes in providing a variety of services to the maritime industry. These services can cover a wide range of areas to support the operation, maintenance, and management of vessels.

[0129] TMGI (Temporary Mobile Group Identity) is an identifier used to identify a specific user group that provides multicast and broadcast services in a mobile communication network.

[0130] MMSI (Maritime Mobile Service Identity) is a unique nine-digit identifier used to identify ships, coastal radio stations and other maritime communication equipment.

[0131] GPSI (Generic Public Subscription Identifier) ​​is an identifier used to identify a user or device.

[0132] UDM (Unified Data Management) is a key functional node in the core network, responsible for managing user data and related information.

[0133] SMF (Session Management Function) is a key component in the core network, responsible for managing user sessions and data connections.

[0134] AMF (Access and Mobility Management Function) is a key component in the core network, responsible for managing the access and mobility of user equipment.

[0135] A network element (NE) is a functional entity in a communication network that performs specific network functions and tasks. A network element can be a hardware device, a software system, or a combination of both, and is responsible for handling data flow, signal transmission, and management tasks within the network.

[0136] A PDU (Protocol Data Unit Session) is used to manage the connection between user equipment and the data network.

[0137] User equipment (UAE) can be any device that includes wireless transceiver capabilities and can work with base stations or other user equipment to provide services to users. UAE can refer to terminal equipment, user terminals, etc. For example, UAE can be a cellular phone, a personal digital assistant (PDA), or a handheld device, computing device, in-vehicle device, or wearable device with wireless communication capabilities.

[0138] Other terms:

[0139] "Including" and its variations can refer to non-restrictive inclusion.

[0140] "First," "second," etc., are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0141] "At least one" means one or more. "More than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the related objects before and after it are in an "or" relationship.

[0142] The terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0143] Phrases such as “under certain circumstances” or “when” are used to indicate conditions.

[0144] Currently, satellite systems used for maritime distress and safety communications services provide at least the following maritime distress and safety communication capabilities:

[0145] Ship-to-shore distress alerts / calls, shore-to-ship distress relay alerts / calls, ship-to-shore, shore-to-ship, and ship-to-ship search and rescue coordination communications, ship-to-shore transmission of maritime safety information, shore-to-ship broadcasting of maritime safety information, and general ship-to-shore, shore-to-ship, and ship-to-ship communications. Among these, shore-to-ship maritime information safety broadcasting is an essential communication requirement for satellite communication systems.

[0146] Shore-to-ship maritime information security broadcasts typically involve a content service provider creating a Mobile Broadcast Service (MBS) session and broadcasting a service announcement to the UE. When a UE has an MBS service requirement, the UE triggers the MBS joining process. Because this process is triggered by the UE, and the UE may have other service requirements, the number of signaling interactions between communication devices during the UE joining the MBS session is relatively high, increasing network signaling overhead and potentially causing network congestion.

[0147] Therefore, when a UE joins a multicast service, the network currently suffers from significant overall signaling overhead, requiring further optimization.

[0148] In view of this, this application provides a communication method, a first network element, a second network element, a user equipment, a communication system, a storage medium, and a product, which reduces network signaling interaction and thus reduces the overall signaling overhead of the network when the UE joins multicast services.

[0149] The technical solution of this application and how it solves the above-mentioned technical problems will be described in detail below with reference to specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described here with reference to the accompanying drawings.

[0150] Figure 1 This is one of the flowcharts illustrating the communication method provided in an embodiment of this application. For example... Figure 1 As shown, the method includes:

[0151] S101, The user equipment sends a first request to the first network element.

[0152] In some embodiments, the first network element can be a network element in the core network, and the first network element can be virtual or physical.

[0153] In some embodiments, the first network element can be used for access and mobility management.

[0154] In some embodiments, the name of the first network element is not limited, and may be, for example, an access and mobility management network element, a processing network element, etc.

[0155] Optionally, the first network element is AMF.

[0156] In some embodiments, the first request is used to request the establishment of a first communication connection.

[0157] In some embodiments, the first request is used to request the establishment of a PDU session.

[0158] In some embodiments, the name of the first request is not limited, and may be, for example, a communication connection establishment request, a PDU session request, etc.

[0159] In some embodiments, the first communication connection is a communication connection to be established before establishing a Multicast Broadcast Service (MBS) session.

[0160] In some embodiments, the first communication connection may be a PDU session connection, a communication registration connection, etc.

[0161] In some embodiments, the name of the first communication connection is not limited, and may be, for example, a communication connection, a session connection, etc.

[0162] In some embodiments, an MBS session has already been created.

[0163] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0164] S102, the first network element sends a second request to the first service provider equipment.

[0165] In some embodiments, the first service-providing device is an electronic device of a network service provider.

[0166] In some embodiments, the first service providing device is a device that provides network services.

[0167] In some embodiments, the name of the first service-providing device is not limited, and may be, for example, a service provider, a network service-providing device, etc.

[0168] Optionally, the first service provider can be an MSS device.

[0169] In some embodiments, the second request is used to request the UE to authenticate the first service.

[0170] In some embodiments, the second request is used to request the first service-providing device to perform authentication processing.

[0171] In some embodiments, the name of the second request is not limited, and may be, for example, an authentication request, a verification request, etc.

[0172] In some embodiments, the first service is a service that uses an MBS session.

[0173] In some embodiments, the first service is the service provided after joining an MBS session.

[0174] In some embodiments, the name of the first service is not limited, and may be, for example, MBS-related services, shore-to-ship broadcasting services, safety information services, etc.

[0175] In some embodiments, the second request includes a first identifier and / or a second identifier; that is, the second request may include only the first identifier, only the second identifier, or both the first and second identifiers. The first identifier is used to characterize the identity of the vessel to which the UE resides. The second identifier is used to characterize the public identity of the UE.

[0176] In some embodiments, the first identifier is used to identify the vessel's identity when authenticating the first service provider's device.

[0177] In some embodiments, the name of the first identifier is not limited, and may be, for example, a ship identifier, a mobile water identifier, etc.

[0178] Optionally, the first identifier is MMSI. By using MMSI as the first identifier, the accuracy of authentication of the first service provider device can be improved based on the stability and accuracy of MMSI.

[0179] In some embodiments, the second identifier is used to identify the UE's identity when authenticating the first service-providing device.

[0180] In some embodiments, the name of the second identifier is not limited, and may be, for example, a UE identifier, a public identifier, etc.

[0181] Optionally, the second identifier is GPSI. By using GPSI as the second identifier, the accuracy of authentication of the first service provider device can be improved based on the stability and accuracy of GPSI.

[0182] S103, The first service providing equipment sends the first instruction information to the first network element.

[0183] In some embodiments, the first indication information is used to indicate the authentication result of the UE by the first service providing device regarding the first service.

[0184] In some embodiments, the authentication result is either authentication successful or authentication failed.

[0185] In some embodiments, the first indication information is used to indicate the authentication result for the second request.

[0186] In some embodiments, the name of the first indication information is not limited, and may be, for example, an authentication result indication, an authentication result indication, etc.

[0187] In some embodiments, the first indication information is generated after authentication processing based on the second request.

[0188] In some embodiments, the first indication information is carried in the first response, and the first response also includes a first identifier and / or a second identifier, that is, the first response may include only the first identifier, only the second identifier, or both the first identifier and the second identifier.

[0189] In some embodiments, the first response is used to respond to the second request.

[0190] In some embodiments, the first response is used to respond to the authentication result of the UE regarding the first service.

[0191] In some embodiments, the name of the first response is not limited, and may be, for example, authentication response, authorization response, etc.

[0192] Optionally, the first response may also include the authentication result.

[0193] S104, the first network element sends a fourth request to the second network element.

[0194] In some embodiments, the second network element can be a network element in the core network, and the second network element can be virtual or physical.

[0195] In some embodiments, the second network element can be used to manage user sessions and data connections.

[0196] In some embodiments, the name of the second network element is not limited, and may be, for example, a management user session network element and a data connection, a data connection management network element, etc.

[0197] Optionally, the second network element is an SMF.

[0198] In some embodiments, the fourth request is used to request that the UE be added to the MBS session.

[0199] In some embodiments, the name of the fourth request is not limited, and may be, for example, MBS session join request, session join request, etc.

[0200] In some embodiments, before S104, the first network element may also determine whether authentication is successful based on the first indication information, and execute the process of S104 after successful authentication.

[0201] S105, the second network element sends a third instruction message to the first network element.

[0202] In some embodiments, the third indication information is used to indicate that the UE has successfully joined the MBS session.

[0203] In some embodiments, the third indication information is used to indicate the result that the UE has joined the MBS session.

[0204] In some embodiments, the name of the third indication information is not limited; for example, it can be session addition result information, MBS session addition information, etc.

[0205] In some embodiments, the third instruction information may be carried in the response to the fourth request.

[0206] S106. The first network element sends the fifth instruction information to the access network equipment.

[0207] In some embodiments, the access network device is located between the user and core network in the network architecture, providing functions such as data transmission, signal processing, and user access management.

[0208] In some embodiments, the access network equipment can be satellite network equipment, base stations, G-NBs (gNodeBs), radio access network equipment, etc. Among them, a G-NB is a radio access network device in a 5G mobile communication network.

[0209] In some embodiments, the fifth indication information is used to indicate the communication resources required to configure an MBS session.

[0210] In some embodiments, the fifth indication information is used to indicate the MBS communication resources required by the UE.

[0211] In some embodiments, the name of the fifth instruction information is not limited, and may be, for example, MBS configuration instruction, resource configuration instruction, etc.

[0212] S107. The access network equipment sends the sixth instruction information to the user equipment.

[0213] In some embodiments, the sixth indication information is used to indicate that the user has joined an MBS session.

[0214] In some embodiments, the sixth indication information is used to indicate the status of the UE joining the MBS session.

[0215] In some embodiments, the name of the sixth indication information is not limited, and may be, for example, MBS result indication, session joining result, etc.

[0216] In some embodiments, the sixth indication information includes:

[0217] The first type is used to characterize the service type of MBS.

[0218] The first region is used to represent the service area information of MBS.

[0219] In some embodiments, the name of the first type is not limited, and may be, for example, MBS service type, MBS type, etc.

[0220] In some embodiments, the first type is a multicast service or a broadcast service.

[0221] In some embodiments, the name of the first region is not limited, and may be, for example, a service region, an MBS service area, etc.

[0222] In some embodiments, the first region includes a list of cell IDs (identifiers), a list of TAIs (Tracking Area Identity), and geographic region information.

[0223] In some embodiments, the cell ID list refers to an identifier used to uniquely identify each radio cell in a mobile communication network.

[0224] In some embodiments, TAI refers to an identifier in a mobile communication network used to uniquely identify a tracking area.

[0225] In some embodiments, geographic area information refers to data used to describe and manage a specific geographic area within the network coverage area.

[0226] Optionally, the sixth indication information may also include TMGI, source-specific multicast (SSM), and the IP multicast address of the MBS session.

[0227] In some embodiments, a source IP multicast address is a multicast communication mode that allows a receiver to specify the source address of the multicast stream it wishes to receive.

[0228] In some embodiments, an IP multicast address is a special IP address used for multicast communication, which allows data to be sent from one source to multiple receivers without having to send a separate data packet to each receiver.

[0229] In the communication method provided in this application embodiment, the user equipment sends a first request to a first network element, which then sends a second request to a first service provider to perform corresponding authentication through the first service provider. After successful authentication, the first network element sends a fourth request to a second network element to add the UE to the MBS session through the second network element. Simultaneously, upon receiving a third indication from the second network element, the first network element configures the communication resources required for the MBS session to the UE through the access network device.

[0230] When the user equipment sends the first request (i.e., communication) to the first network element, the first network element can execute the relevant procedures to add the UE to the MBS session, so that the UE can join the MBS session without the user equipment actively sending an MBS session request. This reduces the signaling interaction of the network when the UE joins the multicast service, thereby reducing the overall signaling overhead of the network.

[0231] The following section takes the first network element as an example, combined with... Figure 2 The communication method provided in this application will be described.

[0232] Figure 2 This is a second schematic flowchart illustrating the communication method provided in an embodiment of this application. Figure 2 As shown, the method includes:

[0233] S201, The user equipment sends a first request to the first network element.

[0234] In some embodiments, S201 is implemented in a similar manner to S101 described above, and will not be repeated here.

[0235] S202, the first network element sends the fifth request to the second network element.

[0236] In some embodiments, the fifth request is used to request the establishment of a first communication connection for the UE.

[0237] In some embodiments, the fifth request is generated by the first network element based on the first request.

[0238] Optionally, the content of the fifth request may be the same as that of the first request.

[0239] In some embodiments, the name of the fifth request is not limited, and may be, for example, a communication connection request, a communication establishment request, etc.

[0240] In some embodiments, the fifth request is a request to establish a PDU session for the UE. The fifth request includes a first identifier. The first identifier is used to identify the vessel to which the UE is located.

[0241] S203, the second network element sends a third request to the first service provider.

[0242] In some embodiments, the third request is used to request authentication of the UE with respect to the first service.

[0243] In some embodiments, the third request is used to request the first service-providing device to perform authentication processing.

[0244] In some embodiments, the name of the third request is not limited, and may be, for example, an authentication request, a verification request, etc.

[0245] In some embodiments, the third request includes a first identifier and / or a second identifier; that is, the third request may include only the first identifier, only the second identifier, or both the first and second identifiers. The first identifier is used to characterize the identity of the vessel to which the UE resides. The second identifier is used to characterize the public identity of the UE.

[0246] S204. The first service providing equipment sends a second instruction message to the second network element.

[0247] In some embodiments, the second indication information is used to indicate that the authentication result of the first service providing device for the UE regarding the first service is successful.

[0248] In some embodiments, the second indication information is used to indicate the authentication result for the third request.

[0249] In some embodiments, the name of the second indication information is not limited, and may be, for example, an authentication result indication, a certification result indication, etc.

[0250] Optionally, the second indication information can also be used to indicate whether the authentication result of the first service providing device for the UE regarding the first service is successful or unsuccessful.

[0251] In some embodiments, the second indication information is carried in the second response, and the second response further includes the first identifier and / or the second identifier, that is, the second response may include only the first identifier, only the second identifier, or both the first identifier and the second identifier.

[0252] In some embodiments, the second response is used to respond to a third request.

[0253] In some embodiments, the second response is used to respond to the authentication result of the UE regarding the first service.

[0254] In some embodiments, the name of the second response is not limited, and may be, for example, authentication response, authorization response, etc.

[0255] Optionally, the second response may also include the authentication result.

[0256] Optionally, the second response may contain the same content as the first response.

[0257] S205, The second network element adds the UE to the MBS session.

[0258] In some embodiments, the second network element can directly add the UE to the MBS session.

[0259] Optionally, prior to S205, the second network element may also send a first instruction message to the first network element to notify the first network element of the authentication result of the first service as either successful or unsuccessful.

[0260] The first indication information is generated by the second network element upon receiving the second indication information sent by the first service providing device. The second indication information is received by the second network element after sending a third request to the first service providing device.

[0261] Optionally, after sending the first indication information, the UE can be added to the MBS session only when a fourth request is received from the first network element.

[0262] For example, S205 can be executed after S104 to S105. This ensures that the second network element only adds the UE to the MBS session upon receiving the fourth request from the first network element. By adding a process where the first network element determines the authentication result and the request, the accuracy of the second network element in adding UEs that need to join the MBS session can be improved.

[0263] S206, The second network element sends a third instruction message to the first network element.

[0264] In some embodiments, S206 is implemented in a similar manner to S105 described above, and will not be repeated here.

[0265] S207. The first network element sends the fifth instruction information to the access network equipment.

[0266] In some embodiments, S207 is implemented in a similar manner to S106 described above, and will not be repeated here.

[0267] S208. The access network equipment sends the sixth instruction information to the user equipment.

[0268] In some embodiments, S208 is implemented in a similar manner to S107 described above, and will not be repeated here.

[0269] In the communication method provided in this application embodiment, the user equipment sends a first request to a first network element. Then, via the first network element and a second network element, the second network element sends a third request to a first service provider to perform corresponding authentication through the first service provider. After successful authentication, the second network element can either add the UE to the MBS session or send first indication information to the first network element, which then sends a fourth request to add the UE to the MBS session.

[0270] When the user equipment sends the first request (i.e., communication) to the first network element, the second network element can add the UE to the MBS session without the user equipment actively sending an MBS session request. This reduces the signaling interaction of the network when the UE joins the multicast service, thereby reducing the overall signaling overhead of the network.

[0271] Figure 3This is the third flowchart illustrating the communication method provided in this application. Figure 3 As shown, in this embodiment, the first network element can perform the relevant steps to add the UE to the MBS session, and the method includes:

[0272] S301, The first network element receives the first request sent by the user equipment.

[0273] S302. After the first service providing device confirms that the UE's authentication of the first service is successful, the second network element determines that the UE will be added to the MBS session.

[0274] In some embodiments, after obtaining the first indication information, the second network element can determine to add the UE to the MBS session, as follows:

[0275] The first instruction information is obtained according to the first request. The first instruction information is used to indicate the authentication result of the first service providing device to the UE regarding the first service, and the authentication result is either successful or unsuccessful.

[0276] In some embodiments, the steps by which the first network element determines that the second network element has added the UE to the MBS session can be as follows: Figure 1 and Figure 2 The process steps executed by the first network element.

[0277] In some embodiments, the relevant steps refer to steps related to adding the UE to the MBS session, such as sending a fourth request to the second network element, receiving third indication information sent by the second network element, etc.

[0278] For details on the execution process of S301 to S302, please refer to the execution processes of S101 to S107 and S201 to S208, which will not be repeated here.

[0279] It should be noted that, Figure 3 The communication method provided in the embodiment and Figure 1 Examples and Figure 2 The communication methods described in the embodiments have the same beneficial effects, and will not be repeated here.

[0280] Figure 4 This is the fourth flowchart illustrating the communication method provided in the embodiments of this application. Figure 4 As shown, in this embodiment, the method includes:

[0281] S401, the first network element receives the first request sent by the user equipment.

[0282] In some embodiments, the first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier. The first identifier is used to characterize the ship identity of the UE.

[0283] If the first request is a PDU session establishment request, the UE can be added to the MBS session later through the PDU session process, thus improving the efficiency of adding the UE to the MBS session.

[0284] S402, the first network element sends a second request to the first service provider equipment.

[0285] In some embodiments, S402 is implemented in a similar manner to S302 described above, and will not be repeated here.

[0286] S403, The first network element receives the first instruction information sent by the first service providing device.

[0287] S404, The first network element sends a fourth request to the second network element.

[0288] S405, the first network element receives the third instruction information sent by the second network element.

[0289] S406. The first network element sends the fifth instruction information to the access network equipment.

[0290] In some embodiments, the implementation of S401 to S406 is similar to the implementation of S101 to S107 described above, and will not be repeated here.

[0291] It should be noted that, Figure 4 The communication method provided in the embodiment and Figure 1 The communication method in the embodiments has the same beneficial effects, and will not be described again here.

[0292] The following is based on this embodiment, combined with Figure 5 The communication method provided in this application is described.

[0293] Figure 5 This is the fifth flowchart illustrating the communication method provided in the embodiments of this application. Figure 5 As shown, the method includes:

[0294] S501, the first network element receives the first request sent by the user equipment.

[0295] In some embodiments, the first request is a registration request.

[0296] In some embodiments, the registration request is used to request registration for a communication connection. The first request includes a first identifier. The first identifier is used to identify the vessel to which the UE is located.

[0297] S502, the first network element sends the fifth request to the second network element.

[0298] In some embodiments, S502 is implemented in a similar manner to S202 described above, and will not be repeated here.

[0299] S503, the first network element sends registration acceptance information to the user equipment.

[0300] In some embodiments, the registration acceptance information is used to indicate that the registration has been accepted.

[0301] In some embodiments, registration acceptance information is information generated when registering a device, user, or application on a network or system.

[0302] In some embodiments, the registration acceptance information includes fourth indication information. The fourth indication information is used to indicate that the first service providing device will request authentication of the UE with respect to the first service.

[0303] In some embodiments, the fourth indication information is used to indicate that the UE will perform MBS session-related procedures.

[0304] In some embodiments, the name of the fourth indication information is not limited, and may be, for example, authentication prompt information, session prompt information, etc.

[0305] S504, the first network element receives the registration success information sent by the user equipment.

[0306] In some embodiments, a registration success message is used to indicate that registration has been completed.

[0307] In some embodiments, the registration success message is a confirmation message after the registration process is completed.

[0308] S505, the first network element receives the first instruction information sent by the second network element.

[0309] In some embodiments, the first indication information is generated by the second network element upon receiving second indication information sent by the first service providing device. The second indication information is received by the second network element after sending a third request to the first service providing device.

[0310] S506, the first network element sends the fifth instruction information to the access network equipment.

[0311] For details on the execution process of S506, please refer to the execution processes of S106 and S207, which will not be repeated here.

[0312] The communication method in this embodiment can add the UE to the MBS session during the UE registration process, thereby adding the UE to the MBS session when the UE registers for the first time, avoiding the UE requesting to join the MBS after registration, reducing the signaling interaction of the network when the UE joins the multicast service, and thus reducing the overall signaling overhead of the network.

[0313] Another embodiment of this application provides a communication method including:

[0314] After the UE requests to establish the first communication connection and the first service providing device successfully authenticates the UE regarding the first service, the UE is added to the MBS session. The first communication connection is the communication connection to be established before establishing the multicast service MBS session. The first service is the service that uses the MBS session.

[0315] Specifically, please refer to the execution processes of S101 to S107 and S201 to S208 for the execution process of the above process, which will not be repeated here.

[0316] It should be noted that the communication method provided in this embodiment is the same as... Figure 1 Examples and Figure 2 The communication methods described in the embodiments have the same beneficial effects, and will not be repeated here.

[0317] Figure 6 This is a sixth flowchart illustrating the communication method provided in an embodiment of this application. Figure 6 As shown, the method includes:

[0318] S601, the second network element receives the fifth request sent by the first network element.

[0319] S602, the second network element sends a third request to the first service provider.

[0320] S603, the second network element receives the second instruction information sent by the first service providing device.

[0321] S604, The second network element adds the UE to the MBS session.

[0322] S605, the second network element sends a third instruction message to the first network element.

[0323] Specifically, the execution process of S601 to S605 can be found in the execution process of S201 to S208, which will not be repeated here.

[0324] It should be noted that, Figure 6 The communication method provided in the embodiment and Figure 2 The communication methods described in the embodiments have the same beneficial effects, and will not be repeated here.

[0325] Figure 7 This is the seventh flowchart illustrating the communication method provided in the embodiments of this application. Figure 7 As shown, the method in this embodiment can be further divided into:

[0326] S701, the second network element receives the fifth request sent by the first network element.

[0327] S702, the second network element sends a third request to the first service provider.

[0328] S703, the second network element receives the second instruction information sent by the first service providing device.

[0329] S704, the second network element sends the authentication result to the first network element.

[0330] S705, the second network element receives the fourth request sent by the first network element.

[0331] S706, the second network element sends a third instruction message to the first network element.

[0332] Specifically, the execution process of S701 to S706 can be found in the execution process of S201 to S208, which will not be repeated here.

[0333] It should be noted that, Figure 7 The communication method provided in the embodiment and Figure 2 The communication methods described in the embodiments have the same beneficial effects, and will not be repeated here.

[0334] Figure 8 This is the eighth flowchart illustrating the communication method provided in the embodiments of this application. Figure 8 As shown, the method in this embodiment further includes:

[0335] S801, The user equipment sends a first request to the first network element.

[0336] S802, The user equipment receives the sixth instruction information sent by the access network equipment.

[0337] Specifically, the execution process of S801 to S802 can be found in S101 to S107 and the execution process of S201 to S208, which will not be repeated here.

[0338] It should be noted that, Figure 8 The communication method provided in the embodiment and Figure 1 Examples and Figure 2 The communication methods described in the embodiments have the same beneficial effects, and will not be repeated here.

[0339] Figure 9 This is flowchart nine of the communication method provided in the embodiments of this application. Figure 9 As shown, the method includes:

[0340] S901, The user equipment sends a first request to the first network element.

[0341] S902, The user equipment receives the registration acceptance information sent by the first network element.

[0342] S903, The user equipment sends a registration success message to the first network element.

[0343] S904. The user equipment receives the sixth instruction information sent by the access network equipment.

[0344] Specifically, the execution process of S901 to S904 can also be found in the execution process of S501 to S506, which will not be repeated here.

[0345] It should be noted that, Figure 9 The communication method provided in the embodiment and Figure 5 The communication methods described in the embodiments have the same beneficial effects, and will not be repeated here.

[0346] In some embodiments, such as Figure 10 As shown, the specific application examples of the communication method provided in this embodiment are as follows:

[0347] Among them, the first network element is AMF, the second network element is SMF, the first request is a registration request, the access network equipment is g-NB or satellite, and the first service provider is an MSS device, hereinafter referred to as MSS.

[0348] S1001: The UE sends a registration request to the AMF, and the registration request carries the MMSI (MMSI: Maritime Mobile Communication Service Identifier, which uniquely identifies a vessel).

[0349] S1002: The network side (including AMF and UDM in the diagram) performs primary authentication on the UE, i.e., initial registration authentication.

[0350] S1003: When the AMF determines that the UE is a shipborne terminal and that the MSS authentication process for the UE needs to be executed, it includes an indication of the pending MSS authentication in a subsequent registration acceptance message. The AMF stores the MSS authentication in the UE context to indicate that the MSS authentication is in a pending state. The UE should wait for the MSS authentication process to complete before proceeding with subsequent services.

[0351] S1004: The network AMF sends a registration acceptance message to the UE.

[0352] S1005: The UE sends a registration completion message to the network.

[0353] S1006: From AMF to MSS, AMF initiates an authentication request message (application layer authentication) to MSS. For the UE's initial authentication, the message should carry parameters such as GPSI (General Public Subscription Identifier) ​​and MMSI.

[0354] S1007: MSS to AMF. The MSS sends an authentication response message to the AMF. The response message should carry parameters such as GPSI, MMSI, and the authentication result (success or failure) between the UE and the MSS.

[0355] S1008: The AMF determines the authentication result (success or failure) between the UE and the MSS. If the authentication result is successful, an MBS session is initiated, which can also be called an MBS PDU session, i.e., the MBS session join request in the aforementioned embodiment. Otherwise, no MBS session join request is initiated.

[0356] S1009: AMF to SMF, AMF sends MBS session join request to SMF.

[0357] S1010: From SMF to AMF, SMF sends an MBS session join response to AMF. The response message should carry parameters indicating whether the MBS session join was successful or failed.

[0358] S1011: AMF to g-NB: After the MBS session is successfully joined, the AMF sends a message request to the g-NB. The message request should carry the MBS session ID that the UE has joined.

[0359] S1012: The g-NB sends an RRC message to the UE. The access network should configure radio resources for the UE for multicast MBS sessions. The UE receives multicast or broadcast data according to the MBS session message parameters.

[0360] In some embodiments, such as Figure 11 As shown, another application example is as follows:

[0361] Based on the above application examples, the network can actively request the UE to join the MBS session during the PDU session establishment process, and the specific process is as follows:

[0362] S1101: UE->g-NB->AMF->SMF, the UE initiates a PDU session establishment with the network and completes the session creation.

[0363] S1102: SMF to MSS. The SMF sends an authentication request message to the MSS. For the UE's initial authentication, the message should carry parameters such as GPSI and MMSI.

[0364] S1103: MSS to SMF. The MSS sends an authentication response message to the SMF. The response message should carry parameters such as GPSI, MMSI, and the authentication result (success or failure) between the UE and the MSS.

[0365] S1104: SMF to AMF: The SMF sends a notification message to the AMF, informing the UE of the authentication result between the UE and the MSS, and carrying parameters such as the authentication result (success or failure).

[0366] S1105: The AMF determines the authentication result (success or failure) between the UE and the MSS. If the authentication result is successful, it initiates an MBS session join request, also known as an MBS PDU session join request; otherwise, it does not initiate an MBS session join request.

[0367] S1106: AMF to SMF, AMF sends MBS session join request to SMF.

[0368] S1107: From SMF to AMF, SMF sends an MBS session join response to AMF. The response message should carry parameters indicating whether the MBS session join was successful or failed.

[0369] S1108: AMF to g-NB: After the MBS PDU session is successfully joined, the AMF sends a message request to the g-NB. The message request should carry the MBS session ID that the UE has joined.

[0370] S1109: g-NB sends an RRC message to UE. The access network should configure radio resources for the UE for multicast MBS sessions. The UE receives multicast or broadcast data according to the MBS session message parameters.

[0371] Based on the above application examples, such as Figure 12 As shown, the network's initiative to request the UE to join the MBS session can be performed during the PDU session establishment process, and the implementation methods differ. The specific process is as follows:

[0372] S1201: UE->g-NB->AMF->SMF, the UE initiates a PDU session establishment with the network and completes the session creation.

[0373] S1202: SMF to MSS. The SMF sends an authentication request message to the MSS. For the UE's initial authentication, the message should carry parameters such as GPSI and MMSI.

[0374] S1203: MSS to SMF. The MSS sends an authentication response message to the SMF. The response message should carry parameters such as GPSI, MMSI, and the authentication result (success or failure) between the UE and the MSS.

[0375] S1204: The SMF determines whether the UE and MSS authentication is successful. If the authentication is successful, the SMF will actively add the UE to the MBS session, which can also be called the MBS PDU session.

[0376] S1205: SMF to AMF, SMF sends a notification message to notify that the UE has joined the MBS session. The message must carry parameters such as the MBS session ID that the UE has joined.

[0377] S1206: AMF to g-NB: After the MBS PDU session is successfully joined, the AMF sends a message request to the g-NB. The message request should carry the MBS session ID that the UE has joined.

[0378] S1207: g-NB sends an RRC message to UE. The access network should configure radio resources for the UE for multicast MBS sessions. The UE receives multicast or broadcast data according to the MBS session message parameters.

[0379] The communication method in this embodiment, where the MBS joining process is triggered by the network, reduces network signaling interaction. During registration, the MBS joining process is triggered by the AMF. During PDU session establishment, the MBS joining process is triggered by the SMF. This increases the ways to add the UE to the MBS session and shortens the process, thereby reducing network signaling overhead.

[0380] Figure 13 This is one of the structural schematic diagrams of the first network element provided in the embodiments of this application. The first network element 1000 can be implemented through a combination of software and / or hardware. For example... Figure 13 As shown, the first network element 1000 includes:

[0381] The receiving module 1001 is used to receive a first request sent by the user equipment (UE). The first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session.

[0382] The processing module 1002 is used to determine, after the first service providing device successfully authenticates the UE regarding the first service, that the second network element will add the UE to the MBS session. The first service is the service that uses the MBS session.

[0383] The first network element 1000 provided in this application embodiment executes the method steps executed by the first network element in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0384] In some embodiments, the processing module 1002 is further configured to:

[0385] The first instruction information is obtained according to the first request. The first instruction information is used to indicate the authentication result of the first service providing device to the UE regarding the first service, and the authentication result is either successful or unsuccessful.

[0386] In some embodiments, when the processing module 1002 obtains the first indication information according to the first request, it is specifically used for:

[0387] A second request is sent to the first service-providing device. This second request is used to request authentication of the UE regarding the first service. A first indication message is received from the first service-providing device.

[0388] In some embodiments, the second request includes a first identifier and / or a second identifier. The first identifier is used to characterize the vessel on which the UE is located. The second identifier is used to characterize the UE's public identity.

[0389] In some embodiments, the first indication information is carried in the first response, which further includes a first identifier and / or a second identifier. The first identifier is used to characterize the vessel identity of the UE. The second identifier is used to characterize the public identity of the UE.

[0390] In some embodiments, when the processing module 1002 obtains the first indication information according to the first request, it is specifically used for:

[0391] The second network element receives a first indication message from the first network element upon receiving a second indication message from the first service provider. This first indication message is generated by the second network element upon receiving a second indication message from the first service provider. The second indication message indicates whether the authentication result of the UE regarding the first service is successful or failed. The second indication message is received by the second network element after sending a third request to the first service provider. This third request is used to authenticate the UE regarding the first service.

[0392] In some embodiments, when the processing module 1002 determines that the second network element has added the UE to the MBS session, it is specifically used to:

[0393] Receive the third indication information sent by the second network element. The third indication information is used to indicate that the UE has successfully joined the MBS session.

[0394] In some embodiments, when the processing module 1002 determines that the second network element has added the UE to the MBS session, it is further configured to:

[0395] Send a fourth request to the second network element. The fourth request is used to request that the UE be added to the MBS session.

[0396] In some embodiments, the first request is a registration request. The registration request is used to request registration for a communication connection. The first request includes a first identifier. The first identifier is used to identify the vessel to which the UE is located.

[0397] In some embodiments, the first network element 1000 further includes:

[0398] The first sending module is used to send registration acceptance information to the UE. The registration acceptance information includes fourth indication information. This fourth indication information indicates that the first service providing device will request authentication of the UE regarding the first service. The module also receives registration success information from the UE.

[0399] In some embodiments, the first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier. The first identifier is used to characterize the ship identity of the UE.

[0400] In some embodiments, the first network element 1000 further includes:

[0401] The second sending module is used to send the fifth indication information to the access network equipment. The fifth indication information is used to indicate the communication resources required to configure the MBS session.

[0402] The first network element 1000 provided in this application embodiment executes the method steps executed by the first network element in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0403] Figure 14 This is one of the structural schematic diagrams of a user equipment provided in an embodiment of this application. The second network element 1100 can be implemented through a combination of software and / or hardware. For example... Figure 14 As shown, the second network element 1100 includes:

[0404] Processing module 1101 is used to add the UE to the MBS session after the UE requests to establish a first communication connection and the first service providing device successfully authenticates the UE regarding the first service. The first communication connection is the communication connection to be established before establishing a multicast service MBS session. The first service is the service that uses the MBS session.

[0405] The second network element 1100 provided in this application embodiment executes the method steps executed by the second network element in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0406] In some embodiments, the processing module 1101 is further configured to:

[0407] The system receives a fifth request from the first network element, which requests the establishment of a first communication connection for the UE. Based on the fifth request, it sends a third request to the first service-providing device. The third request requests authentication of the UE regarding the first service. The system also receives a second indication from the first service-providing device, indicating that the authentication result of the first service-providing device for the UE regarding the first service is successful.

[0408] In some embodiments, the fifth request is a request to establish a PDU session for the UE, and the fifth request includes a first identifier. The first identifier is used to characterize the ship identity of the UE.

[0409] In some embodiments, the third request includes a first identifier and / or a second identifier. The first identifier is used to characterize the vessel on which the UE resides. The second identifier is used to characterize the UE's public identity.

[0410] In some embodiments, the second indication information is carried in the second response, which further includes a first identifier and / or a second identifier. The first identifier is used to characterize the vessel identity of the UE. The second identifier is used to characterize the public identity of the UE.

[0411] In some embodiments, the second network element 1100 further includes:

[0412] The sending module is used to send third indication information to the first network element. The third indication information is used to indicate that the UE has successfully joined the MBS session.

[0413] In some embodiments, the second network element 1100 further includes:

[0414] The receiving module is used to receive the fourth request sent by the first network element. The fourth request is used to request that the UE be added to the MBS session.

[0415] The second network element 1100 provided in this application embodiment executes the method steps executed by the second network element in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0416] Figure 15 This is one of the structural schematic diagrams of a user equipment provided in an embodiment of this application. For example... Figure 15 As shown, user equipment 1200 can be implemented through a combination of software and / or hardware. For example... Figure 15 As shown, user equipment 1200 includes:

[0417] The sending module 1201 is used to send a first request to the first network element. The first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session.

[0418] The receiving module 1202 is configured to receive a sixth indication message sent by the access network device after the first service providing device has successfully authenticated the UE regarding the first service. The first service is a service using an MBS session. The sixth indication message is used to indicate that the UE has joined an MBS session.

[0419] The user equipment 1200 provided in this application embodiment executes the method steps of the user equipment in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0420] In some embodiments, the sixth indication information includes:

[0421] Type 1. Type 1 is used to characterize the service type of MBS.

[0422] First region. The first region is used to represent MBS service area information.

[0423] In some embodiments, the first request is a registration request. The first request includes a first identifier. The first identifier is used to identify the vessel to which the UE is located.

[0424] In some embodiments, the receiving module 1202 is further configured to:

[0425] Receive registration acceptance information from the first network element. The registration acceptance information includes fourth indication information. The fourth indication information is used to indicate that the first service providing device will request authentication of the UE with respect to the first service. Send registration success information to the first network element.

[0426] In some embodiments, the first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier. The first identifier is used to characterize the ship identity of the UE.

[0427] The user equipment 1200 provided in this application embodiment executes the method steps of the user equipment in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0428] Figure 16 This is a second schematic diagram of the structure of the first network element provided in an embodiment of this application. (See attached diagram.) Figure 16 As shown, the first network element 1300 may include a processor 1301, a memory 1302, and a transceiver 1303. The transceiver 1303 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter port, or transmitter interface, etc., and the receiver may also be referred to as a receiver, receiver port, or receiver interface, etc. Exemplarily, each of the processor 1301, memory 1302, and transceiver 1303 is interconnected via a bus.

[0429] The memory 1302 is used to store program instructions. The processor 1301 is used to execute the program instructions stored in the memory to cause the electronic device to perform the above-described method.

[0430] Implementing all or part of the steps of each of the above method embodiments can be accomplished by hardware associated with program instructions. The program described above can be stored in a readable memory. When executed, the program performs the steps of each of the above method embodiments. The memory (storage medium) described above includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0431] Figure 17 This is a second schematic diagram of the structure of the second network element provided in an embodiment of this application. For example... Figure 17 As shown, the second network element 1400 may include a processor 1401, a memory 1402, and a transceiver 1403. The transceiver 1403 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter port, or transmitter interface, and the receiver may also be referred to as a receiver, receiver port, or receiver interface, etc. Exemplarily, each of the processor 1401, memory 1402, and transceiver 1403 is interconnected via a bus.

[0432] The memory 1402 is used to store program instructions. The processor 1401 is used to execute the program instructions stored in the memory to cause the electronic device to perform the above-described method.

[0433] Implementing all or part of the steps of each of the above method embodiments can be accomplished by hardware associated with program instructions. The program described above can be stored in a readable memory. When executed, the program performs the steps of each of the above method embodiments. The memory (storage medium) described above includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0434] Figure 18 This is a second schematic diagram of the structure of a user equipment provided in an embodiment of this application. For example... Figure 18 As shown, user equipment 1500 may include a processor 1501, a memory 1502, and a transceiver 1503. The transceiver 1503 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter port, or transmitter interface, etc., and the receiver may also be referred to as a receiver, receiver port, or receiver interface, etc. Exemplarily, each of the processor 1501, memory 1502, and transceiver 1503 is interconnected via a bus.

[0435] The memory 1502 is used to store program instructions. The processor 1501 is used to execute the program instructions stored in the memory to cause the electronic device to perform the above-described method.

[0436] Implementing all or part of the steps of each of the above method embodiments can be accomplished by hardware associated with program instructions. The program described above can be stored in a readable memory. When executed, the program performs the steps of each of the above method embodiments. The memory (storage medium) described above includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0437] This application provides a communication system, including: a first network element, a second network element, and a user equipment, wherein the first network element is configured to execute the method steps executed by the first network element in any of the above embodiments, the second network element is configured to execute the method steps executed by the second network element in any of the above embodiments, and the user equipment is configured to execute the method steps executed by the user equipment in any of the above embodiments.

[0438] This application provides a computer-readable storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above-described method embodiments.

[0439] This application provides a computer program product, including a computer program, which, when executed by a communication device, implements any of the above-described method embodiments.

[0440] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0441] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0442] Those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A communication method, characterized in that, The method is applied to a first network element, and the method includes: Receive a first request sent by a user equipment (UE); the first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session; After the first service providing device successfully authenticates the UE for the first service, it determines that the second network element will add the UE to the MBS session; the first service is a service that uses the MBS session.

2. The method according to claim 1, characterized in that, The method further includes: The first instruction information is obtained according to the first request; the first instruction information is used to instruct the first service providing device on the authentication result of the UE regarding the first service, wherein the authentication result is authentication success or authentication failure.

3. The method according to claim 2, characterized in that, The step of obtaining the first indication information according to the first request includes: Send a second request to the first service providing device; the second request is used to request authentication of the UE with respect to the first service. Receive the first instruction information sent by the first service providing device.

4. The method according to claim 3, characterized in that, The second request includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

5. The method according to claim 3, characterized in that, The first indication information is carried in the first response, which further includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

6. The method according to claim 2, characterized in that, The step of obtaining the first indication information according to the first request includes: According to the first request, the second network element receives a first indication information sent by the second network element. The first indication information is generated by the second network element receiving a second indication information sent by the first service providing device. The second indication information is used to indicate whether the authentication result of the first service providing device for the UE regarding the first service is successful or unsuccessful. The second indication information is received by the second network element after sending a third request to the first service providing device. The third request is used to authenticate the UE regarding the first service.

7. The method according to claim 1, characterized in that, The step of determining that the second network element adds the UE to the MBS session includes: The third indication information sent by the second network element is received; the third indication information is used to indicate that the UE has successfully joined the MBS session.

8. The method according to claim 7, characterized in that, The step of determining that the second network element adds the UE to the MBS session further includes: A fourth request is sent to the second network element; the fourth request is used to request that the UE be added to the MBS session.

9. The method according to claim 3, characterized in that, The first request is a registration request; the registration request is used to request the registration of a communication connection; the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

10. The method according to claim 9, characterized in that, The method further includes: Send registration acceptance information to the UE; the registration acceptance information includes fourth indication information; the fourth indication information is used to indicate that a request will be made to the first service providing device to authenticate the UE with respect to the first service; Receive registration success information sent by the UE.

11. The method according to claim 6, characterized in that, The first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

12. The method according to claim 3 or 6, characterized in that, The method further includes: Send a fifth indication message to the access network device; the fifth indication message is used to indicate the communication resources required to configure the MBS session.

13. A communication method, characterized in that, The method is applied to a second network element, and the method includes: After the UE requests to establish a first communication connection and the first service providing device successfully authenticates the UE for the first service, the UE is added to the Multicast Broadcast Service (MBS) session; the first communication connection is the communication connection to be established before establishing the MBS session; the first service is the service that uses the MBS session.

14. The method according to claim 13, characterized in that, The method further includes: Receive a fifth request sent by the first network element, the fifth request being used to request the establishment of a first communication connection for the UE; A third request is sent to the first service providing device according to the fifth request; the third request is used to request authentication of the UE with respect to the first service. The device receives a second indication message sent by the first service provider, the second indication message being used to indicate that the first service provider's authentication result for the UE regarding the first service is successful.

15. The method according to claim 14, characterized in that, The fifth request is a request to establish a PDU session for the UE, and the fifth request includes a first identifier; the first identifier is used to characterize the identity of the ship to which the UE is located.

16. The method according to claim 14, characterized in that, The third request includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

17. The method according to claim 14, characterized in that, The second indication information is carried in the second response, which also includes a first identifier and / or a second identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located; the second identifier is used to characterize the public identity of the UE.

18. The method according to claim 13, characterized in that, The method further includes: Send a third indication message to the first network element; the third indication message is used to indicate that the UE has successfully joined the MBS session.

19. The method according to claim 13, characterized in that, The method further includes: The system receives a fourth request sent by the first network element; the fourth request is used to request that the UE be added to the MBS session.

20. A communication method, characterized in that, The method is applied to a user equipment (UE), and the method includes: Send a first request to the first network element; the first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a multicast broadcast service (MBS) session; After the first service providing device successfully authenticates the UE for the first service, it receives a sixth indication message sent by the access network device; the first service is a service using an MBS session; the sixth indication message is used to indicate that the UE has joined an MBS session.

21. The method according to claim 20, characterized in that, The sixth instruction information includes: First type; the first type is used to characterize the service type of MBS; First region; the first region is used to characterize the service area information of MBS.

22. The method according to claim 20, characterized in that, The first request is a registration request; the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

23. The method according to claim 22, characterized in that, The method further includes: The system receives registration acceptance information sent by a first network element; the registration acceptance information includes fourth indication information; the fourth indication information is used to indicate that the system will request the first service providing device to authenticate the UE with respect to the first service. Send a registration success message to the first network element.

24. The method according to claim 20, characterized in that, The first request is a Protocol Data Unit (PDU) session establishment request, and the first request includes a first identifier; the first identifier is used to characterize the identity of the vessel to which the UE is located.

25. A first network element, characterized in that, include: The receiving module is used to receive the first request sent by the user equipment (UE). The first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a Multicast Broadcast Service (MBS) session; The processing module is used to determine that the second network element will add the UE to the MBS session after the authentication result of the first service providing device for the UE regarding the first service is successful. The first service is a service that uses MBS sessions.

26. A second network element, characterized in that, include: The processing module is used to add the UE to the multicast broadcast service (MBS) session after the UE requests to establish a first communication connection and the authentication result of the first service providing device for the UE regarding the first service is successful. The first communication connection is the communication connection to be established before establishing an MBS session; the first service is the service that uses the MBS session.

27. A user equipment, characterized in that, include: The sending module is used to send the first request to the first network element; The first request is used to request the establishment of a first communication connection, which is a communication connection to be established before establishing a Multicast Broadcast Service (MBS) session; The receiving module is used to receive the sixth indication information sent by the access network device after the authentication result of the first service providing device for the UE regarding the first service is successful. The first service is a service that uses an MBS session; the sixth indication information is used to indicate that the user has joined an MBS session.

28. A first network element, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the communication method as described in any one of claims 1 to 12.

29. A second network element, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the communication method as described in any one of claims 13 to 19.

30. A user equipment, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the communication method as described in any one of claims 20 to 24.

31. A communication system, characterized in that, The device includes a first network element, a second network element, and a user equipment, wherein the first network element is configured to implement the communication method according to any one of claims 1-12, the second network element is configured to implement the communication method according to any one of claims 13-19, and the user equipment is configured to implement the communication method according to claims 20-24.

32. A computer-readable storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1-12, 13-19, or 20-24.

33. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the communication method as described in any one of claims 1-12, 13-19, or 20-24.

Images