Communication method and apparatus, electronic device, and storage medium

Abstract

A communication method, device, electronic equipment and storage medium, the method is applied to a core network device, and the method comprises the following steps: receiving a PDU session modification request sent by an access network device, wherein the PDU session modification request comprises an MBS session identifier, and the MBS session identifier is used to represent an MBS session to which a terminal requests to join; and determining whether to accept the terminal to join the MBS session; wherein the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device. Thus, the core network device can provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of communication, and particularly relates to a communication method and device, electronic equipment and storage medium. BACKGROUND

[0002] In the related art, the multicast and broadcast service in the 5G communication system can only support the terminal accessing the core network in the 3GPP mode. However, with the development of the non-3GPP access network, how to enable the multicast and broadcast service in the 5G communication system to support the terminal in the non-3GPP access mode is an urgent problem to be solved. SUMMARY

[0003] To overcome the problems in the related art, the present disclosure provides a communication method and device, electronic equipment and storage medium.

[0004] According to a first aspect of an embodiment of the present disclosure, a communication method is provided, applied to a core network device, and the method comprises:

[0005] receiving a PDU session modification request sent by an access network device, wherein the PDU session modification request comprises an MBS session identifier, and the MBS session identifier is used to represent an MBS session requested to join by a terminal;

[0006] determining whether to accept the terminal to join the MBS session;

[0007] wherein the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP mode through the trusted non-3GPP access network device.

[0008] According to a second aspect of an embodiment of the present disclosure, a communication method is provided, applied to a terminal, wherein the terminal communicates with a core network device in a non-3GPP mode through an access network device, and the access network device is a trusted non-3GPP access network device;

[0009] the method comprises:

[0010] sending a PDU session modification request to the access network device, wherein the access network device is configured to send the PDU session modification request to the core network device;

[0011] the PDU session modification request comprises an MBS session identifier, and the MBS session identifier is used to represent an MBS session requested to join by the terminal, and the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session.

[0012] According to a third aspect of an embodiment of the present disclosure, a communication method is provided, applied to an application function network element in a core network device, and the method comprises:

[0013] sending a first request message to a first network element, the first request message comprising at least one temporary mobile group identity and at least one MBS service area to be identified, the at least one MBS service area to be identified comprising an MBS service area corresponding to an access network device;

[0014] The first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined; the access network device is a trusted non-3GPP access network device, and a terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; and the first request message is used for the first network element to allocate the at least one temporary mobile group identity to the at least one MBS service area to be identified according to the first request message, so as to create at least one MBS session.

[0015] According to a fourth aspect of the embodiments of the present disclosure, a communication method is provided, which is applied to a first network element in a core network device, the first network element being a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined;

[0016] The method comprises:

[0017] receiving a first request message sent by an application function network element, the first request message comprising at least one temporary mobile group identity and at least one MBS service area to be identified, the at least one MBS service area to be identified comprising an MBS service area corresponding to an access network device; wherein the access network device is a trusted non-3GPP access network device, and a terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device;

[0018] allocating the at least one temporary mobile group identity to the at least one MBS service area to be identified according to the first request message, so as to create at least one MBS session.

[0019] According to a fifth aspect of the embodiments of the present disclosure, a communication apparatus is provided, which is applied to a core network device, and the apparatus comprises:

[0020] The first receiving module is configured to receive a PDU session modification request sent by a terminal through an access network device, the PDU session modification request comprising an MBS session identity, the MBS session identity being used to represent an MBS session requested to be joined by the terminal;

[0021] The determining module is configured to determine whether to accept the terminal to join the MBS session;

[0022] The access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0023] According to a sixth aspect of the embodiments of the present disclosure, a communication apparatus is provided, applied to a terminal, the terminal communicates with a core network device in a non-3GPP manner through an access network device, the access network device is a trusted non-3GPP access network device; the apparatus comprises:

[0024] The second sending module is configured to send a PDU session modification request to the access network device, and the access network device is configured to send the PDU session modification request to the core network device.

[0025] The PDU session modification request comprises an MBS session identifier, the MBS session identifier is used to represent an MBS session that the terminal requests to join, and the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session.

[0026] According to a seventh aspect of the embodiments of the present disclosure, a communication apparatus is provided, applied to an application function network element in a core network device.

[0027] The apparatus comprises:

[0028] The third sending module is configured to send a first request message to a first network element, the first request message comprises at least one temporary mobile group identifier and at least one MBS service area to be identified, and the at least one MBS service area to be identified comprises an MBS service area of a corresponding access network device.

[0029] The first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined; the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; and the first request message is used for the first network element to allocate the at least one temporary mobile group identifier to the at least one MBS service area to be identified according to the first request message, so as to create at least one MBS session.

[0030] According to an eighth aspect of the embodiments of the present disclosure, a communication apparatus is provided, applied to a first network element in a core network device, the first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined;

[0031] The apparatus comprises:

[0032] a third receiving module configured to receive a first request message sent by an application function network element, the first request message comprising at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified comprising an MBS service area of a corresponding access network device, wherein the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device;

[0033] a creating module configured to allocate the at least one temporary mobile group identifier to the at least one MBS service area to be identified according to the first request message, to create at least one MBS session.

[0034] According to a ninth aspect of the embodiments of the present disclosure, an electronic device is provided, comprising:

[0035] a processor;

[0036] a memory for storing processor-executable instructions;

[0037] The processor is configured to perform the steps of any of the methods in the first aspect of the present disclosure, or the steps of any of the methods in the second aspect of the present disclosure, or the steps of any of the methods in the third aspect of the present disclosure, or the steps of any of the methods in the fourth aspect of the present disclosure.

[0038] According to a tenth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, which stores computer program instructions, the program instructions being executed by a processor to implement the steps of any of the methods in the first aspect of the present disclosure, or the steps of any of the methods in the second aspect of the present disclosure, or the steps of any of the methods in the third aspect of the present disclosure, or the steps of any of the methods in the fourth aspect of the present disclosure.

[0039] In the technical solution provided by the embodiments of the present disclosure, the terminal accesses the core network device in a trusted non-3GPP manner, and forwards the PDU session modification request to the core network device through the trusted non-3GPP access network device, so that the core network device can determine whether to accept the terminal to join the MBS session according to the PDU session modification request, and the core network device can provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0040] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0041] The above mentioned and / or additional aspects and advantages of the present disclosure will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:

[0042] Figure 1 An exemplary communication architecture diagram to which embodiments of the present disclosure apply is shown.

[0043] Figure 2 is a flowchart of a communication method according to an exemplary embodiment.

[0044] Figure 3 is a flowchart of a communication method according to an exemplary embodiment.

[0045] Figure 4 is a flowchart of a communication method according to an exemplary embodiment.

[0046] Figure 5 is a flowchart of a communication method according to an exemplary embodiment.

[0047] Figure 6 is a flowchart of a communication method according to an exemplary embodiment.

[0048] Figure 7 is a flowchart of a communication method according to an exemplary embodiment.

[0049] Figure 8 is a flowchart of a communication method according to an exemplary embodiment.

[0050] Figure 9 is a flowchart of a communication method according to an exemplary embodiment.

[0051] Figure 10 is a flowchart of a communication method according to an exemplary embodiment.

[0052] Figure 11 is a flowchart of a communication method according to an exemplary embodiment.

[0053] Figure 12 is a flowchart of a communication method according to an exemplary embodiment.

[0054] Figure 13 is a flowchart of a communication method according to an exemplary embodiment.

[0055] Figure 14 is a flowchart of a communication method according to an exemplary embodiment.

[0056] Figure 15 is a flowchart of a communication method according to an exemplary embodiment.

[0057] Figure 16 is a flowchart of a communication method according to an example embodiment.

[0058] Figure 17 is a flowchart of a communication method according to an example embodiment.

[0059] Figure 18 is a flowchart of a communication method according to an example embodiment.

[0060] Figure 19 is a flowchart of a communication method according to an example embodiment.

[0061] Figure 20 is a flowchart of a communication method according to an example embodiment.

[0062] Figure 21 is an interaction diagram of a communication method according to an example embodiment.

[0063] Figure 22 is a block diagram of a communication apparatus according to an example embodiment.

[0064] Figure 23 is a block diagram of a communication apparatus according to an example embodiment.

[0065] Figure 24 is a block diagram of a communication apparatus according to an example embodiment.

[0066] Figure 25 is a block diagram of a communication apparatus according to an example embodiment.

[0067] Figure 26 is a block diagram of a communication apparatus according to an example embodiment.

[0068] Figure 27 is a block diagram of an electronic device according to an example embodiment.

[0069] Figure 28 is a block diagram of an electronic device according to an example embodiment. DETAILED DESCRIPTION

[0070] The example embodiments will be described in detail herein with reference to the attached drawings. The following description is made with reference to the accompanying drawings, in which like reference numerals represent like elements, and secondary reference numerals represent elements with secondary names for the elements having the primary reference numerals in the drawings. The following description of example embodiments is not representative of all embodiments consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0071] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This application is intended to cover any variations, uses or adaptations of the disclosure that are deemed to fall within the general principles of the disclosure and include commonly known or customary practice in the art. The specification and examples are to be considered exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

[0072] It should be understood that the present disclosure is not limited to the precise structures as herein described and illustrated in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the claims that follow.

[0073] To solve the problems in the related art, the present disclosure provides a communication method, device, system, electronic device and medium.

[0074] The embodiments of the present disclosure can be applied to a 4G (fourth generation mobile communication system) evolution system, such as a long term evolution (LTE) system, or can also be applied to a 5G (fifth generation mobile communication system) system, such as an access network using a new radio access technology (New RAT), a cloud radio access network (CRAN) and the like.

[0075] Figure 1 An exemplary communication architecture diagram to which the embodiments of the present disclosure are applicable is shown. It should be understood that the embodiments of the present disclosure are not limited to Figure 1 In the system shown, in addition, Figure 1 The device in the system shown can be hardware, or software divided in function, or a structure combined with the above two.

[0076] Referring to Figure 1 The communication architecture diagram shown:

[0077] The AMF can be an access and mobility management function (AMF) in 5G. The mobility management network element is responsible for the access and mobility management of the terminal in the mobile network. Among them, the AMF is responsible for terminal access and mobility management, NAS message routing, session management function (SMF) selection, etc. The AMF can be used as an intermediate network element to transmit session management messages between the terminal and the SMF.

[0078] SMF can be a session management network element in the 5G architecture, responsible for forwarding path management, such as issuing packet forwarding policies to user plane network elements and instructing them to process and forward packets according to these policies. This session management network element can also be responsible for session management, such as session creation / modification / deletion, user plane network element selection, and the allocation and management of user plane tunnel information.

[0079] UPF can be the user plane function entity in the 5G architecture, which is responsible for packet processing and forwarding.

[0080] UDM can be a data management network element used to handle terminal device identification, access authentication, registration, and mobility management. In 5G communication systems, this data management network element can be a unified data management (UDM) network element.

[0081] like Figure 1 As shown in the embodiments of this disclosure, the communication architecture may further include a PCF (policy control function), and in other embodiments, the PCF may also be a policy and charging control function (PCRF). The PCF or PCRF is responsible for policy control decisions and flow-based charging control.

[0082] In addition, such as Figure 1 As shown, this communication architecture also includes network elements such as MB-SMF, MB-UPF, MBSTF, NEF, MBSF, and AF. These network elements, along with AMF, UPF, SMF, and UDM, can be collectively referred to as core network equipment. This core network equipment supports terminal access via 3GPP networks, such as gNB and eNB, as well as access via non-3GPP networks, such as Wi-Fi and satellite. Non-3GPP access networks can connect to the 5G network through N3IWF (Non-3GPP Interworking Function), which accesses the 5G network through the N2 and N3 interfaces.

[0083] MB-SMF is a Multicast / Broadcast Session Management Function, mainly for implementing session management of multicast and broadcast services; MB-UPF is a Multicast / Broadcast User Plane Function, mainly for implementing user plane forwarding function of multicast and broadcast services; MBSTF is a Multicast / Broadcast Service Transport Function, mainly for being an anchor point of MBS (Multimedia Broadcast Service) data flow, a general data packet transmission function, and supporting IP multicast applications such as frames, multi-streams, and packet FEC (Forward Error Correction); NEF can be a Network Exposure Function, located between a 5G core network and an external third-party application function (there can also be some internal AFs, responsible for managing the opening of network data to the outside, and all external applications that want to access the internal data of the 5G core network must pass through the NEF. The NEF provides corresponding security protection to ensure the security of external applications to the 3gpp network, provides external application QoS (Quality of Service) customization capability opening, mobility state event subscription, AF request distribution, and other functions; MBSF can be a Multicast / Broadcast Service Function, mainly for supporting MBS services, including controlling MBSTF and deciding transmission parameters. AF can be an Application Function, which is similar to an application server, interacts with other 5G core network control plane NFs, and provides service services. AF can exist for different application services, can be owned by an operator or a trusted third party, and optionally, the AF network element can also be an AS (Application Server) network element.

[0084] In some embodiments, a network storage network element can also be included in the system architecture for maintaining real-time information of all network function services in the network. In a 5G communication system, the network storage network element can be a network repository function (NRF) network element. A lot of network element information can be stored in the network repository network element, such as SMF information, UPF information, AMF information, etc. The network elements such as AMF, SMF, UPF, etc. in the network can be connected to the NRF. On the one hand, the network elements can register their own network element information to the NRF. On the other hand, other network elements can obtain the information of the network elements that have been registered from the NRF. Other network elements (such as AMF) can request the NRF to obtain optional network elements according to network element type, data network identifier, unknown area information, etc. If a domain name system (DNS) server is integrated in the NRF, the corresponding selection function network element (such as AMF) can request the NRF to obtain other network elements to be selected, such as SMF.

[0085] As shown in Figure 1 The communication architecture also includes a TNAN (Trusted Non-3GPP Access Network), which includes a trusted non-3GPP access point (TNAP) to provide wireless access services for terminals. The TNAN also includes a TNFG (Satellite Access Gateway Function). The TNAP and the TNFG can be collectively referred to as access network devices.

[0086] Referring to Figure 1This communication architecture also includes UE (user equipment), also known as a terminal, or access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device, etc. This terminal must have at least non-3GPP access capabilities and NAS (Non-Access Stratum) capabilities. The terminal can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, or IoT terminal device, such as fire detection sensors, smart water / electricity meters, factory monitoring equipment, etc. This terminal can connect to a trusted non-3GPP access network (TNAN) and register with the 5G core network.

[0087] based on Figure 1 The communication architecture shown allows the terminal to access the 5G system via TNAN, and the 5G system can provide multicast and broadcast services to the terminal that accesses the 5G core network in a non-3GPP manner.

[0088] It is understood that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0089] Figure 2 This is a flowchart illustrating a communication method according to an exemplary embodiment, applied to core network equipment, such as... Figure 2 As shown, the method includes:

[0090] S201. The core network device receives a PDU session modification request sent by the access network device. The PDU session modification request includes an MBS session identifier, which is used to identify the MBS session that the terminal requests to join.

[0091] S202, The core network equipment determines whether to accept the terminal joining the MBS session.

[0092] Among them, the access network equipment is a trusted non-3GPP access network equipment, and the terminal communicates with the core network equipment in a non-3GPP manner through the trusted non-3GPP access network equipment.

[0093] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message, and forwarded to the core network device by the access network device. The PDU session modification request can include one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the disclosure.

[0094] In an example, before step S201 is performed, the core network device can send a first request message to the first network element through an application function network element, the first request message including at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified including an MBS service area corresponding to an access network device; the first network element assigns the at least one temporary mobile group identifier to each MBS service area to be identified according to the first request message, to create at least one MBS session. The first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network exposure function network element and a multicast and broadcast service function network element combined.

[0095] It can be understood that the MBS service area to be identified can include an MBS service area corresponding to a 3GPP access network, and / or an MBS service area corresponding to a non-3GPP access network.

[0096] In an example, after the core network device establishes the MBS session, the core network device can send the MBS session identifier of the established one or more MBS sessions to the terminal, and the terminal can determine the relevant information of each MBS session according to the MBS session identifier, and then determine whether to join the one or more MBS sessions established by the core network device according to the MBS session information.

[0097] In an example, the MBS session identifier can include at least one of the following: a temporary mobile group identifier (TMGI), synchronization status information (SSM), MBS service area information, session description information, and access type information. In some optional examples, the access type information can also be radio access technology (RAT) type information.

[0098] For example, the MBS session identifier can include access type information or RAT type information, which can represent a trusted non-3GPP access method.

[0099] In another example, the MBS service area information includes at least one of the following: a cell ID, a tracking area indicator list (TAI list), geographic area information, civic address information, and zone information, which can be identified by the access network device and mapped to an area covered by the non-3GPP access point. The zone information can be a zone information identifier corresponding to the zone information.

[0100] It can be understood that the cell ID, the tracking area indicator list, the geographic area information, the civic address information, and the zone information can all be identified by the access network device or the terminal as a certain geographic area. The MBS service area information can be represented by the cell ID, the tracking area indicator list, the geographic area information, the civic address information, and the zone information. For example, an MBS session can be uniquely identified by an address or an area corresponding to the cell ID.

[0101] The data amount corresponding to the cell ID, or the tracking area indicator list, or the zone information identifier is less than that of the geographic area information and / or the civic address information.

[0102] In the case where the MBS service area information includes an MBS service area corresponding to a non-3GPP access network, the MBS service area information can include zone information, which can be used to represent an area covered by the non-3GPP access network.

[0103] In yet another example, in the case where the MBS service area information is included in any MBS session identifier and the MBS service area information includes geographic area information and / or civic address information, the geographic area information and / or the civic address information is translated into a cell ID, a tracking area indicator list, or a zone information identifier by a first network element.

[0104] That is, the geographic area information and / or the civic address information can be translated into a cell ID, a tracking area indicator list, or a zone information identifier by a first network element, and then the translated MBS service area information is sent to the terminal to reduce the amount of data transmitted.

[0105] In some possible implementations, the step S202 can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join an MBS session according to MBS subscription data received from a UDM network element and / or according to a terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate an enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0106] In some optional embodiments, in the case that the SMF accepts the terminal to join the MBS session, the SMF can respond by sending N2 SM information to the access network device, the N2 SM information can include one or more of the PDU session identifier, the MBS session identifier, the updated PDU session information, and the mapping information between the unicast QoS flow and the multicast QoS flow; if there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between the unicast QoS flow and the multicast QoS flow. In the case that the SMF does not accept the terminal to join the MBS session, the PDU session modification rejection message can be forwarded to the terminal by the access network device.

[0107] In an example, the trusted non-3GPP access network device includes a trusted non-3GPP access point, the trusted non-3GPP access point is provided by a trusted non-3GPP satellite, or is provided by a wireless router.

[0108] It is worth noting that the wireless router can be any device that provides a wireless access point for a wireless local area network, such as a wireless gateway, a wireless bridge, and the like.

[0109] In addition, as a specific implementation form of the trusted non-3GPP access network, the satellite can serve as a trusted non-3GPP access point (TNAP) to provide wireless access services for the terminal. Correspondingly, in the case that the trusted non-3GPP access point is provided by a trusted non-3GPP satellite, the trusted non-3GPP access device can further include a satellite access gateway function network element (S-AGF), which is equivalent to a trusted non-3GPP access gateway function (TNGF) in the trusted non-3GPP access network. The satellite can communicate with the S-AGF through a Ta interface. The S-AGF can communicate with the AMF through an N2 interface, which can be an enhanced N2 interface so that the S-AGF and the AMF can reliably communicate.

[0110] In the embodiments of the present disclosure, the terminal accesses the core network device in a trusted non-3GPP manner, and forwards the PDU session modification request to the core network device through the trusted non-3GPP access network device, so that the core network device can determine whether to accept the terminal to join the MBS session according to the PDU session modification request, and so that the core network device can provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0111] Figure 3 is a flow chart of a communication method according to an example embodiment, applied to a core network device, such as Figure 3 as shown, the method comprises:

[0112] S301, the core network device receives a PDU session modification request sent by an access network device, the PDU session modification request comprising an MBS session identifier, the MBS session identifier being used to represent an MBS session that the terminal requests to join.

[0113] S302, the core network device determines whether to accept the terminal to join the MBS session.

[0114] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0115] S303, in the case of determining to accept the terminal to join any MBS session, the core network device determines to transmit MBS session data by shared MBS traffic in response to determining that the access network device supports MBS.

[0116] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0117] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point being provided by a trusted non-3GPP satellite, or by a wireless router.

[0118] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can comprise one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the present disclosure.

[0119] In some possible implementations, step S302 can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to MBS subscription data received from a UDM network element, and / or according to a terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join has not been enabled, the SMF can accept the terminal to join the MBS session and indicate the enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0120] In some alternative embodiments, in case the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, the N2 information request can include one or more of the PDU session identity, the MBS session identity, the updated PDU session information, the mapping information between the unicast QoS flow and the multicast QoS flow; if there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identity and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0121] In an example, the non-3GPP radio is configured for the MBS session by the access network device according to the first signaling in response to determining that the access network device supports MBS and determining that the MBS session joined by the terminal is in an active state, the first signaling including a PDU session modification command exchanged between the access network device and the terminal.

[0122] Specifically, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. In case the access network device determines that it supports MBS, the access network device can perform first signaling exchange with the terminal, the first signaling being used for the access network device to configure non-3GPP radio resources for the terminal for the multicast or broadcast MBS session according to the first signaling, the first signaling including a PDU session modification command. In a possible implementation, in case the access network device does not support MBS, the access network device can reconfigure the radio resources for unicast transmission of MBS session data through the related PDU session.

[0123] In an alternative embodiment, the access network device can send a PDU session modification response to the core network device, the PDU session modification response being carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in case the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0124] In an example embodiment, transmitting MBS session data using shared MBS traffic can include the MB-UPF sending a multicast PDU to the access network device through an N3mb interface corresponding to the MBS session, so that all terminals joining the MBS session through the access network device share the interface to receive MBS session data.

[0125] In the embodiments of the present disclosure, the core network device determines whether to accept the terminal to join the MBS session by receiving the PDU session modification request forwarded by the trusted non-3GPP access network device, and in the case of accepting the terminal to join any MBS session, if the access network device supports MBS, the MBS session data is transmitted by using shared MBS traffic, which ensures that the MBS session data is transmitted by using shared MBS traffic by the access network device supporting MBS, and realizes the support of multicast and broadcast services provided to the terminal accessing in the non-3GPP mode.

[0126] Figure 4 is a flowchart of a communication method according to an exemplary embodiment, applied to a core network device, as shown in Figure 4 The method comprises:

[0127] S401, the core network device receives the PDU session modification request sent by the access network device, and the PDU session modification request comprises an MBS session identifier, which is used to represent the MBS session requested by the terminal to join.

[0128] S402, the core network device determines whether to accept the terminal to join the MBS session.

[0129] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP mode through the trusted non-3GPP access network device.

[0130] S403, in the case of determining to accept the terminal to join any MBS session, the core network device determines to transmit the MBS session data by using shared MBS traffic in response to determining that the access network device supports MBS.

[0131] S404, the core network device sends the MBS session data to the access network device, and the access network device is used to transmit the MBS session data through a non-3GPP radio bearer, and transmit the MBS session data to the terminal by using a PTP (Point To Point) or PTM (Point To Multipoint) mode.

[0132] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP mode through the trusted non-3GPP access network device.

[0133] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, and the trusted non-3GPP access point is provided by a trusted non-3GPP satellite or a wireless router.

[0134] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can include one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the disclosure.

[0135] In some possible embodiments, step S402 can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to the MBS subscription data received from the UDM network element and / or according to the terminal indication received from the MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate the enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0136] In yet some alternative embodiments, in the case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, which can include one or more of the PDU session identifier, the MBS session identifier, the updated PDU session information, and the mapping information between the unicast QoS flow and the multicast QoS flow. If there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0137] In an example, the non-3GPP radio is configured by the access network device according to the first signaling in response to determining that the access network device supports MBS and determining that the MBS session joined by the terminal is in an active state. The first signaling includes a PDU session modification command exchanged between the access network device and the terminal.

[0138] Specifically, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. In the case that the access network device determines that it supports MBS, the access network device can perform first signaling exchange with the terminal, the first signaling being used for the access network device to configure non-3GPP radio resources for the multicast or broadcast MBS session for the terminal according to the first signaling, and the first signaling including a PDU session modification command. In a possible embodiment, if the access network device does not support MBS, the access network device can reconfigure the radio resources to perform unicast transmission of MBS session data through the related PDU session.

[0139] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, which can be carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in the case where the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0140] In an exemplary embodiment, transmitting MBS session data using shared MBS traffic can include: the MB-UPF sending a multicast PDU to the access network device through an N3mb interface corresponding to the MBS session, so that all terminals joining the MBS session through the access network device share the interface to receive MBS session data.

[0141] In an example, whether the access network device uses PTP or PTM can be determined according to the MBS session data. If the MBS session data is unicast data, PTP can be used to send the corresponding terminal. If the MBS session data is multicast data or broadcast data, PTM can be used to send to one or more corresponding terminals.

[0142] In the embodiments of the present disclosure, the core network device determines whether to accept the terminal to join the MBS session by receiving the PDU session modification request forwarded by the trusted non-3GPP access network device, and in the case where the terminal is accepted to join any MBS session, if the access network device supports MBS, the MBS session data is transmitted using shared MBS traffic, ensuring that the MBS session data is transmitted using shared MBS traffic by the access network device supporting MBS, and realizing the support of multicast and broadcast services provided to the terminal accessed in a non-3GPP manner.

[0143] Figure 5 is a flowchart of a communication method according to an exemplary embodiment, applied to a core network device, as shown in Figure 5 The method comprises:

[0144] S501, the core network device receives the PDU session modification request sent by the access network device, and the PDU session modification request comprises an MBS session identifier, which is used to represent the MBS session requested by the terminal to join.

[0145] S502, the core network device determines whether to accept the terminal to join the MBS session.

[0146] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0147] S503, in a case that the core network device determines to accept the terminal to join any MBS session, in response to determining that the access network device does not support MBS, the core network device determines to transmit MBS session data by separate MBS traffic.

[0148] The access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0149] In an example, the trusted non-3GPP access network device includes a trusted non-3GPP access point, and the trusted non-3GPP access point is provided by a trusted non-3GPP satellite or a wireless router.

[0150] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can include one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the disclosure.

[0151] In some possible embodiments, step S502 can be performed by an SMF network element in the core network device. The SMF network element can determine whether to accept the terminal to join the MBS session according to MBS subscription data received from a UDM network element and / or according to a terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate an enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0152] In yet some alternative embodiments, in a case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, and the N2 information request can include one or more of a PDU session identifier, an MBS session identifier, updated PDU session information, and mapping information between unicast QoS flows and multicast QoS flows. If there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of a relationship between a multicast MBS session context and a PDU session context of the terminal according to the MBS session identifier and the mapping information between unicast QoS flows and multicast QoS flows.

[0153] In an example, the non-3GPP radio is configured for the MBS session according to the first signaling in response to the access network device determining that the access network device supports MBS and determining that the MBS session joined by the terminal is in an active state. The first signaling includes a PDU session modification command exchanged between the access network device and the terminal.

[0154] In particular, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. In a case where the access network device determines that it supports MBS, the access network device can perform first signaling exchange with the terminal, the first signaling being used for the access network device to configure non-3GPP radio resources for the terminal for the multicast or broadcast MBS session according to the first signaling, the first signaling including a PDU session modification command. In a possible implementation, if the access network device does not support MBS, the access network device can reconfigure the radio resources for unicast transmission of MBS session data through the related PDU session.

[0155] In an alternative embodiment, the access network device can send a PDU session modification response to the core network device, which can be carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and, in a case where the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0156] In an example embodiment, transmitting MBS session data using separate MBS traffic can include the MB-UPF sending multicast PDUs to the UPF through an N19mb interface corresponding to the MBS session, there being only one interface per MBS session and corresponding UPF, i.e. all PDU sessions provided by each UPF share the interface, causing the UPF to forward the multicast MBS session data to the access network device in unicast, and the access network device to forward the MBS session data to the terminal in unicast. The MBS session data is transmitted through a radio bearer corresponding to a related QoS flow of the related PDU session, i.e. the MBS session data is transmitted to the access network device through the PDU session and forwarded by the access network device to the terminal. The related QoS flow can be carried by the N2 information request described above.

[0157] In the embodiments of the present disclosure, the core network device determines whether to accept the terminal to join the MBS session by receiving the PDU session modification request forwarded by the trusted non-3GPP access network device, and in the case of accepting the terminal to join any MBS session, if the access network device does not support MBS, the MBS session data is transmitted by using the separate MBS traffic, so that the access network device which does not support MBS can transmit the MBS session data through the PDU session, ensuring that the access network device can still effectively transmit the MBS session data in the case of not supporting MBS, and realizing the support of providing multicast and broadcast services to the terminal accessing in the non-3GPP mode.

[0158] Figure 6 is a flowchart of a communication method according to an exemplary embodiment, applied to a core network device, as shown in Figure 6 The method comprises:

[0159] S601, the core network device receives the PDU session modification request sent by the access network device, and the PDU session modification request comprises an MBS session identifier, the MBS session identifier being used to represent the MBS session requested by the terminal to join.

[0160] S602, the core network device determines whether to accept the terminal to join the MBS session.

[0161] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP mode through the trusted non-3GPP access network device.

[0162] S603, in the case of determining to accept the terminal to join any MBS session, the core network device determines to transmit the MBS session data by using the separate MBS traffic in response to determining that the access network device does not support MBS.

[0163] S604, the core network device sends the MBS session data to the access network device, and the access network device is used for unicast transmission through the related PDU session, and the MBS session data is sent to the terminal by using the PTP mode.

[0164] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP mode through the trusted non-3GPP access network device.

[0165] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, and the trusted non-3GPP access point is provided by a trusted non-3GPP satellite, or by a wireless router.

[0166] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message, and forwarded to the core network device through the access network device. The PDU session modification request can include one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the disclosure.

[0167] In some possible implementation manners, the step S602 can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to the MBS subscription data received from the UDM network element, and / or according to the terminal indication received from the MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate the enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0168] In yet some optional embodiments, in the case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, which can include one or more of the PDU session identifier, the MBS session identifier, the updated PDU session information, and the mapping information between the unicast QoS flow and the multicast QoS flow. If there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0169] In an example, the related PDU session is configured for the MBS session by the access network device in response to determining that the access network device does not support MBS, and determining that the MBS session joined by the terminal is in an active state.

[0170] Specifically, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. In the case that the access network device determines that it does not support MBS, the access network device can configure the radio resources for unicast transmission of MBS session data through the related PDU session, i.e., the access network device can configure the related PDU session for the MBS session joined by the terminal in the case that it determines that it does not support MBS.

[0171] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, which can be carried by the N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in the case where the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0172] In an exemplary embodiment, transmitting MBS session data using separate MBS traffic can include: the MB-UPF sending multicast PDUs to the UPF through the N19mb interface corresponding to the MBS session, there being only one interface per MBS session and corresponding UPF, i.e., all PDU sessions provided by each UPF share the interface, causing the UPF to forward multicast MBS session data to the access network device in a unicast manner, and the access network device forwarding the MBS session data to the terminal in a unicast manner. Wherein the MBS session data is transmitted through the radio bearer corresponding to the relevant QoS flow of the relevant PDU session, i.e., the MBS session data is transmitted to the access network device through the PDU session, and the MBS session data is forwarded to the terminal by the access network device. The relevant QoS flow can be carried by the N2 information request described above.

[0173] In an example, the access network device can transmit MBS session data to the terminal in a PTP manner, which can be multicast or broadcast MBS session data transmitted to the terminal that joins the MBS session through the access network device through a PDU session.

[0174] In the embodiments of the present disclosure, the core network device determines whether to accept the terminal joining the MBS session by receiving the PDU session modification request forwarded by the trusted non-3GPP access network device, and in the case where the terminal is accepted to join any MBS session, if the access network device does not support MBS, the MBS session data is transmitted using separate MBS traffic, so that the access network device that does not support MBS can transmit the MBS session data through the PDU session in a point-to-point manner using separate MBS traffic, ensuring that the access network device can still effectively transmit the MBS session data in the case where it does not support MBS, and realizing support for providing multicast and broadcast services to terminals accessed in a non-3GPP manner.

[0175] Figure 7 is a flowchart of a communication method according to an exemplary embodiment, applied to an access network device, which is a trusted non-3GPP access network device, and a terminal communicates with a core network device in a non-3GPP manner through the trusted non-3GPP access network device; as shown in Figure 7 the method comprises:

[0176] S701, the access network device receives a PDU session modification request sent by the terminal.

[0177] S702. The access network device sends a PDU session modification request to the core network device. The PDU session modification request includes an MBS session identifier, which is used to identify the MBS session that the terminal requests to join. The PDU session modification request is used by the core network device to determine whether to accept the terminal joining the MBS session.

[0178] In one example, the trusted non-3GPP access network device includes a trusted non-3GPP access point, which is provided by a trusted non-3GPP satellite or by a wireless router.

[0179] Specifically, the PDU session modification request can be sent by the terminal via an uplink NAS message and forwarded to the core network device through the access network device. This PDU session modification request may include one or more MBS session identifiers; this disclosure does not limit the number of MBS session identifiers.

[0180] In some possible implementations, the core network device's determination of whether to accept a terminal joining an MBS session may specifically be performed by an SMF (Signal-Mobile Function) element within the core network device. This SMF element can determine whether to accept the terminal joining the MBS session based on MBS subscription data received from a UDM (Uniform Demand Module) element, and / or based on terminal instructions received from an MB-SMF element. If the MBS session the terminal requests to join is not yet enabled, the SMF may accept the terminal's joining and indicate the enabling time to the terminal; alternatively, the SMF may refuse the terminal's joining. If the MBS session the terminal requests to join is inactive, the SMF may accept the terminal's joining.

[0181] In some alternative embodiments, when the SMF accepts the terminal joining the MBS session, the SMF can send an N2 information request to the access network device. The N2 information request may include one or more of the following: PDU session identifier, MBS session identifier, updated PDU session information, and mapping information between unicast QoS streams and multicast QoS streams. If there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the terminal's PDU session context based on the MBS session identifier and the mapping information between unicast QoS streams and multicast QoS streams.

[0182] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, so that the core network device can provide multicast and broadcast services to the terminal accessing through the non-3GPP manner.

[0183] Figure 8 FIG. 8 is a flowchart of a communication method according to an example embodiment, applied to an access network device, the access network device being a trusted non-3GPP access network device, and a terminal communicating with a core network device through the trusted non-3GPP access network device in a non-3GPP manner; as shown in FIG. 8, the method comprises: Figure 8

[0184] S801, the access network device receives a PDU session modification request sent by the terminal.

[0185] S802, the access network device sends the PDU session modification request to the core network device, the PDU session modification request comprising an MBS session identifier, the MBS session identifier being used to represent the MBS session requested by the terminal to join, and the PDU session modification request being used for the core network device to determine whether to accept the terminal to join the MBS session.

[0186] S803, in the case that the core network device accepts the terminal to join the MBS session, the access network device configures radio resources for the MBS session in response to determining that the MBS session is in an active state.

[0187] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point being provided by a trusted non-3GPP satellite, or by a wireless router.

[0188] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device through the access network device. The PDU session modification request can comprise one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the present disclosure.

[0189] In some possible implementations, the core network device determining whether to accept the terminal to join the MBS session can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to the MBS subscription data received from a UDM network element, and / or according to the terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join has not been enabled, the SMF can accept the terminal to join the MBS session and indicate the enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session. ​

[0190] In some optional embodiments, in a case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, the N2 information request can include one or more of the PDU session identifier, the MBS session identifier, the updated PDU session information, and the mapping information between the unicast QoS flow and the multicast QoS flow; if there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0191] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, the PDU session modification response can be carried by the N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in a case that the access network device does not support MBS, indicate to the core network device the unicast QoS flow received by the access network device.

[0192] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, and configures the radio resource of the multicast or broadcast MBS session for the terminal when the MBS session is in an active state after accepting the terminal to join the MBS session, ensuring that the access network device can support sending the MBS session data sent by the core network device to the terminal through radio, so that the core network device can provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0193] Figure 9 is a flowchart of a communication method according to an exemplary embodiment, applied to an access network device, the access network device being a trusted non-3GPP access network device, and a terminal communicating with a core network device in a non-3GPP manner through the trusted non-3GPP access network device; as shown in Figure 9 the method comprises:

[0194] S901, the access network device receives a PDU session modification request sent by a terminal.

[0195] S902, the access network device sends the PDU session modification request to the core network device, the PDU session modification request including an MBS session identifier, the MBS session identifier being used to represent an MBS session requested by the terminal to join, and the PDU session modification request being used for the core network device to determine whether to accept the terminal to join the MBS session.

[0196] S903. When the access network device determines that the core network device accepts the terminal joining the MBS session and that the access network device supports MBS, in response to determining that the MBS session is active, the access network device exchanges a first signaling with the terminal. The first signaling is used by the access network device to configure non-3GPP radio resources for the multicast or broadcast MBS session for the terminal according to the first signaling. The first signaling includes a PDU session modification command.

[0197] In one example, the trusted non-3GPP access network device includes a trusted non-3GPP access point, which is provided by a trusted non-3GPP satellite or by a wireless router.

[0198] Specifically, a PDU session modification request can be sent by the terminal via an uplink NAS message and forwarded to the core network device by the access network device. This PDU session modification request may include one or more MBS session identifiers; this disclosure does not limit the number of MBS session identifiers.

[0199] In some possible implementations, the core network device's determination of whether to accept a terminal joining an MBS session may specifically be performed by an SMF (Signal-Mobile Function) element within the core network device. This SMF element can determine whether to accept the terminal joining the MBS session based on MBS subscription data received from a UDM (Uniform Demand Module) element, and / or based on terminal instructions received from an MB-SMF element. If the MBS session the terminal requests to join is not yet enabled, the SMF may accept the terminal's joining and indicate the enabling time to the terminal; alternatively, the SMF may refuse the terminal's joining. If the MBS session the terminal requests to join is inactive, the SMF may accept the terminal's joining.

[0200] In some alternative embodiments, when the SMF accepts the terminal joining the MBS session, the SMF can send an N2 information request to the access network device. The N2 information request may include one or more of the following: PDU session identifier, MBS session identifier, updated PDU session information, and mapping information between unicast QoS streams and multicast QoS streams. If there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the terminal's PDU session context based on the MBS session identifier and the mapping information between unicast QoS streams and multicast QoS streams.

[0201] In an example, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. The access network device can perform a first signaling exchange with the terminal, the first signaling being for the access network device to configure the terminal with non-3GPP radio resources for the multicast or broadcast MBS session according to the first signaling, the first signaling comprising a PDU session modification command. In a possible implementation, if the access network device does not support MBS, the access network device can reconfigure the radio resources for unicast transmission of MBS session data over the related PDU session.

[0202] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, the PDU session modification response being carried by a N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and, in the case that the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0203] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, and after accepting the terminal to join the MBS session, performs a signaling exchange with the terminal when the MBS session is in an active state, and configures the terminal with radio resources for the multicast or broadcast MBS session according to the exchanged signaling, so that the core network device can provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0204] Figure 10 is a flowchart of a communication method according to an example embodiment, applied to an access network device, the access network device being a trusted non-3GPP access network device, and a terminal communicating with a core network device in a non-3GPP manner through the trusted non-3GPP access network device; as shown in Figure 9 the method comprises:

[0205] S1001, the access network device receives a PDU session modification request sent by a terminal.

[0206] S1002, the access network device sends the PDU session modification request to the core network device, the PDU session modification request comprising an MBS session identifier, the MBS session identifier being used to represent an MBS session requested by the terminal to join, and the PDU session modification request being used for the core network device to determine whether to accept the terminal to join the MBS session.

[0207] S1003、In a case where the access network device determines that the core network device accepts the terminal to join the MBS session and the access network device supports the MBS, the access network device performs a first signaling exchange with the terminal in response to determining that the MBS session is in an active state, the first signaling being used for the access network device to configure, for the terminal, non-3GPP radio resources of the multicast or broadcast MBS session according to the first signaling, the first signaling including a PDU session modification command.

[0208] S1004、The access network device receives the MBS session data sent by the core network device, transmits the MBS session data through a non-3GPP radio bearer, and transmits the MBS session data to the terminal in a PTP or PTM manner.

[0209] In an example, the trusted non-3GPP access network device includes a trusted non-3GPP access point, the trusted non-3GPP access point being provided by a trusted non-3GPP satellite or by a wireless router.

[0210] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can include one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the disclosure.

[0211] In some possible implementations, the core network device determining whether to accept the terminal to join the MBS session can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to MBS subscription data received from a UDM network element and / or according to a terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate an enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0212] In yet some alternative embodiments, in a case where the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, the N2 information request including one or more of a PDU session identifier, an MBS session identifier, updated PDU session information, and mapping information between unicast QoS flows and multicast QoS flows. If the MBS session does not exist in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of a relationship between the multicast MBS session context and a PDU session context of the terminal according to the MBS session identifier and the mapping information between unicast QoS flows and multicast QoS flows.

[0213] In an example, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. The access network device can perform a first signaling exchange with the terminal, the first signaling being for the access network device to configure the terminal with non-3GPP radio resources for the multicast or broadcast MBS session according to the first signaling, the first signaling comprising a PDU session modification command. In a possible implementation, if the access network device does not support MBS, the access network device can reconfigure the radio resources for unicast transmission of MBS session data through the related PDU session.

[0214] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, which can be carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and, in the case that the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0215] In an example embodiment, the MBS session data sent by the core network device can be transmitted using shared MBS traffic, specifically, the MB-UPF sends a multicast PDU to the access network device through an N3mb interface corresponding to the MBS session, so that all terminals that join the MBS session through the access network device share the interface to receive MBS session data.

[0216] In an example, the access network device can use PTP or PTM according to the MBS session data, if the MBS session data is unicast data, it can be sent to the corresponding terminal in the form of PTP, if the MBS session data is multicast data or broadcast data, it can be sent to one or more corresponding terminals in the form of PTM.

[0217] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, and after accepting the terminal to join the MBS session, performs a signaling exchange with the terminal when the MBS session is in an active state, and configures the terminal with radio resources for the multicast or broadcast MBS session according to the exchanged signaling, and then sends the MBS session data to the terminal in the form of PTP or PTM based on the non-3GPP radio bearer MBS session data, so that the core network device can provide multicast and broadcast services to terminals accessed through non-3GPP.

[0218] Figure 11is a flow chart of a communication method according to an exemplary embodiment, applied to an access network device, the access network device being a trusted non-3GPP access network device, and a terminal communicates with a core network device in a non-3GPP manner through the trusted non-3GPP access network device; as shown in Figure 9 the method comprises:

[0219] S1101, the access network device receives a PDU session modification request sent by the terminal.

[0220] S1102, the access network device sends the PDU session modification request to the core network device, the PDU session modification request comprising an MBS session identifier, the MBS session identifier being used to represent an MBS session that the terminal requests to join, and the PDU session modification request being used for the core network device to determine whether to accept the terminal to join the MBS session.

[0221] S1103, in a case where it is determined that the core network device accepts the terminal to join the MBS session and the access network device does not support MBS, the access network device configures radio resources for unicast transmission of MBS data through a related PDU session in response to determining that the MBS session is in an active state.

[0222] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point being provided by a trusted non-3GPP satellite, or by a wireless router.

[0223] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can comprise one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the present disclosure.

[0224] In some possible implementation manners, the core network device determining whether to accept the terminal to join the MBS session can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to MBS subscription data received from a UDM network element, and / or according to a terminal indication received from an MB-SMF network element. If the MBS session that the terminal requests to join has not been enabled, the SMF can accept the terminal to join the MBS session and indicate an enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session that the terminal requests to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0225] In some optional embodiments, in a case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, the N2 information request can include one or more of the PDU session identifier, the MBS session identifier, the updated PDU session information, and the mapping information between the unicast QoS flow and the multicast QoS flow; if there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0226] In an example, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. The access network device can perform a first signaling exchange with the terminal, the first signaling being used for the access network device to configure non-3GPP radio resources for the terminal for the multicast or broadcast MBS session according to the first signaling, the first signaling including a PDU session modification command. In a possible implementation, if the access network device does not support MBS, the access network device can reconfigure the radio resources for unicast transmission of MBS session data through the related PDU session.

[0227] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, the PDU session modification response being carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in a case that the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0228] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, and after accepting the terminal to join the MBS session, configures radio resources for unicast transmission of MBS data through the related PDU session when the MBS session is in an active state, ensuring that the access network device can still effectively transmit MBS session data in a case that the access network device does not support MBS, and enabling the core network device to provide multicast and broadcast services to terminals accessing in a non-3GPP manner.

[0229] Figure 12 is a flowchart of a communication method according to an example embodiment, applied to an access network device, the access network device being a trusted non-3GPP access network device, and a terminal communicating with a core network device in a non-3GPP manner through the trusted non-3GPP access network device; as Figure 9As shown, the method comprises:

[0230] S1201, the access network device receives the PDU session modification request sent by the terminal.

[0231] S1202, the access network device sends the PDU session modification request to the core network device, the PDU session modification request comprising an MBS session identifier, the MBS session identifier being used to represent the MBS session that the terminal requests to join, the PDU session modification request being used for the core network device to determine whether to accept the terminal to join the MBS session.

[0232] S1203, in the case that the core network device accepts the terminal to join the MBS session and the access network device does not support the MBS, the access network device configures radio resources for unicast transmission of MBS data through the related PDU session in response to determining that the MBS session is in an active state.

[0233] S1204, the access network device receives the MBS session data sent by the core network device, unicasts the MBS session data through the related PDU session, and sends the MBS session data to the terminal in a PTP manner.

[0234] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point being provided by a trusted non-3GPP satellite or by a wireless router.

[0235] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can comprise one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the present disclosure.

[0236] In some possible implementations, the core network device determining whether to accept the terminal to join the MBS session can be performed by an SMF network element in the core network device. The SMF network element can determine whether to accept the terminal to join the MBS session according to MBS subscription data received from a UDM network element and / or according to a terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join has not been enabled, the SMF can accept the terminal to join the MBS session and indicate an enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0237] In some alternative embodiments, in case the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, the N2 information request can comprise one or more of the PDU session identity, the MBS session identity, the updated PDU session information, the mapping information between the unicast QoS flow and the multicast QoS flow; in case there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identity and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0238] In an example, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. The access network device can perform a first signaling exchange with the terminal, the first signaling being for the access network device to configure non-3GPP radio resources for the terminal for the multicast or broadcast MBS session according to the first signaling, the first signaling comprising a PDU session modification command. In a possible implementation, in case the access network device does not support MBS, the access network device can reconfigure the radio resources for unicast transmission of MBS session data through the related PDU session.

[0239] In an alternative embodiment, the access network device can send a PDU session modification response to the core network device, the PDU session modification response can be carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in case the access network device does not support MBS, indicate to the core network device the unicast QoS flow received by the access network device.

[0240] In an example embodiment, the MBS session data sent by the core network device can be sent through a separate MBS traffic, specifically, the MB-UPF sends a multicast PDU to the UPF through an N19mb interface corresponding to the MBS session, there is only one interface for each MBS session and corresponding UPF, i.e. all PDU sessions provided by each UPF share the interface, so that the UPF forwards the multicast MBS session data to the access network device through unicast, and the access network device forwards the MBS session data to the terminal through unicast. Wherein, the MBS session data is sent to the access network device through the related QoS flow of the related PDU session, i.e. the MBS session data is sent to the access network device through the PDU session, and the MBS session data is forwarded to the terminal by the access network device. The related QoS flow can be carried by the N2 information request described above.

[0241] In an example, the access network device transmits MBS session data to the terminal in a PTP manner, which can be multicast or broadcast MBS session data, and transmits the MBS session data to the terminal that joins the MBS session through the access network device through a PDU session respectively.

[0242] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, and after accepting the terminal to join the MBS session, unicasts through the related PDU session when the MBS session is in an active state, and transmits MBS session data to the terminal in a PTP manner, which ensures that the access network device can still effectively transmit MBS session data in the case of not supporting MBS, and enables the core network device to provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0243] Figure 13 Fig. 1 is a flowchart of a communication method according to an example embodiment, which is applied to a terminal, the terminal communicates with a core network device through an access network device in a non-3GPP manner, and the access network device is a trusted non-3GPP access network device; as shown in Fig. 1, the method comprises the following steps. Figure 13

[0244] S1301, the terminal sends a PDU session modification request to the access network device, the access network device is used for sending the PDU session modification request to the core network device, the PDU session modification request comprises an MBS session identifier, the MBS session identifier is used to represent an MBS session requested by the terminal to join, and the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session.

[0245] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point is provided by a trusted non-3GPP satellite, or is provided by a wireless router.

[0246] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device through the access network device. The PDU session modification request can comprise one or more MBS session identifiers, and the number of MBS session identifiers is not limited in the present disclosure.

[0247] ​In some possible implementation, the core network device determining whether to accept the terminal to join the MBS session can be specifically performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to the MBS subscription data received from a UDM network element, and / or according to the terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate the enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0248] In some possible implementation, the core network device determining whether to accept the terminal to join the MBS session can be specifically performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to the MBS subscription data received from a UDM network element, and / or according to the terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate the enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0249] In the embodiments of the present disclosure, the terminal accesses the core network device in a non-3GPP manner through the non-3GPP access network device, and forwards the PDU session modification request sent by the terminal to the core network device through the trusted non-3GPP access network device, so that the core network device determines whether to accept the terminal to join the MBS session, and the core network device can provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0250] Figure 14 Fig. 1 is a flowchart of a communication method according to an example embodiment, which is applied to a terminal, the terminal communicates with a core network device in a non-3GPP manner through an access network device, and the access network device is a trusted non-3GPP access network device. As shown in Fig. 1, the method comprises the following steps. Figure 14

[0251] S1401, the terminal sends a PDU session modification request to the access network device, the access network device is used for sending the PDU session modification request to the core network device, the PDU session modification request comprises an MBS session identifier, the MBS session identifier is used to represent an MBS session requested by the terminal to join, and the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session.

[0252] ​S1402, the terminal performs first signaling exchange with the access network device, the first signaling is used for the access network device to configure non-3GPP radio resources of a multicast or broadcast MBS session for the terminal according to the first signaling, and the first signaling includes a PDU session modification command.

[0253] In an example, the trusted non-3GPP access network device includes a trusted non-3GPP access point, the trusted non-3GPP access point is provided by a trusted non-3GPP satellite or by a wireless router.

[0254] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can include one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the disclosure.

[0255] In some possible embodiments, the core network device determining whether to accept the terminal to join the MBS session can be performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to MBS subscription data received from a UDM network element and / or according to a terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate an enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0256] In yet some optional embodiments, in the case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, the N2 information request can include one or more of a PDU session identifier, an MBS session identifier, updated PDU session information, and mapping information between unicast QoS flows and multicast QoS flows; if there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of a relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between unicast QoS flows and multicast QoS flows.

[0257] In an example, step S1402 can be performed after the core network device accepts the terminal to join the MBS session and the access network device responds to the MBS session being in an active state. In a possible embodiment, if the access network device does not support MBS, the access network device can reconfigure the radio resources to perform unicast transmission of MBS session data through the related PDU session.

[0258] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, which can be carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and, in the case that the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0259] In the embodiments of the present disclosure, the terminal accesses the core network device in a non-3GPP manner through the non-3GPP access network device, and forwards the PDU session modification request sent by the terminal to the core network device through the trusted non-3GPP access network device, so that the core network device determines whether to accept the terminal to join the MBS session, and enables the access network device to configure wireless resources for the terminal based on the first signaling exchange with the access network device, ensuring that the terminal can reliably communicate through the MBS session, and enabling the core network device to provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0260] Figure 15 Fig. 1 is a flowchart of a communication method according to an exemplary embodiment, which is applied to a terminal, the terminal communicates with a core network device in a non-3GPP manner through an access network device, and the access network device is a trusted non-3GPP access network device; as shown in Fig. 1, the method comprises: Figure 15

[0261] S1501, the terminal sends a PDU session modification request to the access network device, the access network device is used to send the PDU session modification request to the core network device, the PDU session modification request comprises an MBS session identifier, the MBS session identifier is used to represent an MBS session requested by the terminal to join, and the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session.

[0262] S1502, the terminal receives MBS session data; wherein the MBS session data is MBS session data transmitted by the access network device through a non-3GPP radio bearer and sent in a PTP or PTM manner; or the MBS session data is unicast transmitted by the access network device through a related PDU session and sent in a PTP manner.

[0263] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point is provided by a trusted non-3GPP satellite, or by a wireless router.

[0264] ​Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message, and forwarded to the core network device by the access network device. The PDU session modification request can include one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the disclosure.

[0265] In some possible embodiments, the core network device determining whether to accept the terminal to join the MBS session can be specifically performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to MBS subscription data received from a UDM network element, and / or according to a terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate an enabling time to the terminal, or the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0266] In yet some alternative embodiments, in the case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, which can include one or more of the PDU session identifier, the MBS session identifier, the updated PDU session information, and the mapping information between the unicast QoS flow and the multicast QoS flow. If there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0267] In an example, the non-3GPP radio is configured for the MBS session by the access network device according to the first signaling in response to determining that the access network device supports MBS and determining that the MBS session joined by the terminal is in an active state. The first signaling includes a PDU session modification command, which is exchanged between the access network device and the terminal.

[0268] Specifically, the access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. In the case that the access network device determines that it supports MBS, the access network device can perform first signaling exchange with the terminal. The first signaling is used for the access network device to configure non-3GPP radio resources for the multicast or broadcast MBS session for the terminal according to the first signaling, and the first signaling includes a PDU session modification command.

[0269] In another example, the related PDU session is configured by the access network in response to determining that the access network device does not support MBS and determining that the MBS session joined by the terminal is in an active state.

[0270] In a case where the access network device determines that it does not support MBS, the access network device can configure radio resources for unicast transmission of MBS session data through the related PDU session, i.e., the access network device can configure the related PDU session for the MBS session joined by the terminal in a case where it determines that it does not support MBS.

[0271] The access network device can configure radio resources for the MBS session in response to the MBS session being in an active state. The access network device can perform a first signaling exchange with the terminal, the first signaling being used for the access network device to configure multicast or broadcast radio resources for the MBS session for the terminal according to the first signaling, the first signaling including a PDU session modification command. In a possible implementation, if the access network device does not support MBS, the access network device can reconfigure the radio resources for unicast transmission of MBS session data through the related PDU session.

[0272] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, which can be carried by an N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and, in a case where the access network device does not support MBS, to indicate to the core network device the unicast QoS flow received by the access network device.

[0273] In an example embodiment, the MBS session data sent by the core network device can be transmitted using shared MBS traffic, specifically, the MB-UPF sends multicast PDUs to the access network device through an N3mb interface corresponding to the MBS session, so that all terminals joining the MBS session through the access network device share the interface to receive MBS session data.

[0274] In an example, the use of PTP or PTM by the access network device can be determined according to the MBS session data, if the MBS session data is unicast data, it can be sent to the corresponding terminal in the form of PTP, if the MBS session data is multicast data or broadcast data, it can be sent to one or more corresponding terminals in the form of PTM.

[0275] In another example embodiment, the MBS session data sent by the core network device can be sent in a separate MBS traffic, specifically, the MB-UPF sends multicast PDUs to the UPF through the N19mb interface corresponding to the MBS session, each MBS session and the corresponding UPF has only one interface, that is, all PDU sessions provided by each UPF share the interface, so that the UPF forwards the multicast MBS session data to the access network device in a unicast manner, and the access network device forwards the MBS session data to the terminal in a unicast manner. Wherein, the MBS session data is transmitted to the access network device through the related QoS flow of the related PDU session, that is, the MBS session data is transmitted to the access network device through the PDU session, and the access network device forwards the MBS session data to the terminal. The related QoS flow can be carried by the N2 information request described above.

[0276] In an example, the access network device transmits the MBS session data to the terminal in a PTP manner, which can be multicast or broadcast MBS session data transmitted to the terminal that joins the MBS session through the access network device through a PDU session.

[0277] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, and after accepting the terminal to join the MBS session, the MBS session data is transmitted to the terminal in a unicast manner through the related PDU session when the MBS session is in an active state, or the MBS session data is transmitted to the terminal in a PTP or PTM manner based on a non-3GPP radio bearer, which ensures that the access network device can effectively transmit the MBS session data in the case of supporting or not supporting MBS, so that the core network device can provide multicast and broadcast services to the terminal accessing through a non-3GPP manner.

[0278] Those skilled in the art should understand that the MBS session establishment can include two processes. The first process is that the core network device establishes the MBS session; the second process is that the terminal applies to join the MBS session and transmits data to the terminal by the core network device, such as an AF network element. The above-mentioned embodiments describe the second process of the communication architecture of the terminal accessing the core network device through a non-3GPP manner. The following embodiments will describe the first process corresponding to the core network device establishing the MBS session.

[0279] Figure 16 is a flow chart of a communication method according to an example embodiment, which is applied to an application function network element in a core network device, as shown in Figure 16 The method comprises:

[0280] S1601, the application function network element sends a first request message to the first network element, the first request message includes at least one temporary mobile group identifier, and at least one to be identified MBS service area, and the at least one to be identified MBS service area includes the MBS service area corresponding to the access network device.

[0281] Wherein, the first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network exposure function network element and a multicast and broadcast service function network element combined; the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; the first request message is used for the first network element to allocate at least one temporary mobile group identifier to at least one to be identified MBS service area according to the first request message, so as to create at least one MBS session.

[0282] It can be understood that the first network element can allocate one temporary mobile group identifier to each to be identified MBS service area, thereby creating one MBS session, that is, each MBS session corresponds to only one MBS service area and one temporary mobile group identifier, and the temporary mobile group identifier can be used to uniquely identify the MBS session.

[0283] Wherein, the to be identified MBS service area can include the MBS service area corresponding to the non-3GPP access network, and / or the MBS service area corresponding to the 3GPP access network.

[0284] In the embodiments of the present disclosure, by sending the first request message including the MBS service area corresponding to the trusted non-3GPP access network device to the first network element through the application function network element, the first network element allocates a temporary mobile group identifier to the MBS service area to identify the MBS service area corresponding to the non-3GPP access network device, thereby establishing an MBS session supporting the non-3GPP access network device, so that the core network device can provide multicast and broadcast services to the terminal accessing in a non-3GPP manner.

[0285] Figure 17 is a flowchart of a communication method according to an exemplary embodiment, which is applied to an application function network element in a core network device, as shown in Figure 17 The method comprises:

[0286] S1701, the application function network element sends a first request message to the first network element, the first request message includes at least one temporary mobile group identifier, and at least one to be identified MBS service area, and the at least one to be identified MBS service area includes the MBS service area corresponding to the access network device.

[0287] The first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element combined with the network exposure function network element and the multicast and broadcast service function network element; the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; and the first request message is used for the first network element to assign at least one temporary mobile group identifier to at least one to-be-identified MBS service area according to the first request message, so as to create at least one MBS session.

[0288] In S1702, the application function network element sends the MBS session identifier of each MBS session to the terminal, and the MBS session identifier is used to inform the terminal of MBS session information, and the MBS session information is used for the terminal to determine whether to join any one or more MBS sessions in the at least one MBS session.

[0289] In an example, after the core network device establishes the MBS session, the core network device can send the MBS session identifier of the established one or more MBS sessions to the terminal, and the terminal can determine the related information of each MBS session according to the MBS session identifier, and then determine whether to join the one or more MBS sessions established by the core network device according to the MBS session information.

[0290] In an example, the MBS session identifier can include at least one of the following: a temporary mobile group identifier (TMGI), synchronization status information (SSM), MBS service area information, session description information, and access type information. In some optional examples, the access type information can also be radio access technology (RAT) type information.

[0291] For example, the MBS session identifier can include access type information or RAT type information, which can represent a trusted non-3GPP access manner.

[0292] It can be understood that the MBS session can be uniquely identified by the temporary mobile group identifier, or by the synchronization status information, the MBS service area information, the session description information, or the access type information.

[0293] In another example, the MBS service area information includes at least one of the following: a cell ID, a tracking area indicator list (TAI list), geographic area information, civic address information, and zone information, which can be recognized by an access network device (e.g., a non-3GPP access network device) and mapped to an area covered by a non-3GPP access point. The zone information can be an area information identifier corresponding to the zone information.

[0294] It can be understood that the cell ID, the TAI list, the geographic area information, the civic address information, and the zone information can all be recognized by an access network device or a terminal as a certain geographic area. The MBS service area information can be represented by the cell ID, the TAI list, the geographic area information, the civic address information, and the zone information. For example, an MBS session can be uniquely identified by an address or an area corresponding to a cell ID.

[0295] In the case where the MBS service area information includes an MBS service area corresponding to a non-3GPP access network, the MBS service area information can include zone information, which can be used to represent an area covered by the non-3GPP access network.

[0296] In the embodiments of the present disclosure, the first network element is enabled to allocate a temporary mobile group identifier to the MBS service area corresponding to the non-3GPP access network device to identify the MBS service area corresponding to the non-3GPP access network device, and to establish an MBS session supporting the non-3GPP access network device, so that the core network device can provide multicast and broadcast services to terminals accessing in a non-3GPP manner. In addition, the terminal can be enabled to determine the information of each MBS session based on the MBS session identifier, and to determine whether to join one or more MBS sessions according to the MBS session information, so that the core network device can provide multicast and broadcast services to terminals accessing in a non-3GPP manner.

[0297] Figure 18 FIG. 1 is a flowchart of a communication method according to an example embodiment, which is applied to a first network element in a core network device. The first network element can be a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined, as shown in FIG. 2. The method includes the following steps. Figure 18

[0298] ​S1801、The first network element receives a first request message, the first request message comprising at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified comprising an MBS service area corresponding to an access network device.

[0299] S1802、The first network element allocates, according to the first request message, the at least one temporary mobile group identifier to the at least one MBS service area to be identified, to create at least one MBS session.

[0300] It can be understood that the first network element can allocate one temporary mobile group identifier to each MBS service area to be identified, to create one MBS session, that is, each MBS session corresponds to only one MBS service area and one temporary mobile group identifier.

[0301] The MBS service area to be identified can comprise an MBS service area corresponding to a non-3GPP access network and / or an MBS service area corresponding to a 3GPP access network.

[0302] In the embodiments of the present disclosure, the first network element receives the first request message sent by the application function network element, the first request message comprising an MBS service area corresponding to a trusted non-3GPP access network device, and allocates a temporary mobile group identifier to the MBS service area to identify the MBS service area corresponding to the non-3GPP access network device, to further establish an MBS session supporting the non-3GPP access network device, so that the core network device can provide multicast and broadcast services to terminals accessing in a non-3GPP manner.

[0303] Figure 19 is a flowchart of a communication method according to an exemplary embodiment, the method being applied to a first network element in a core network device, the first network element being a network exposure function network element, or a multicast and broadcast service function network element, or a network element combined from the network exposure function network element and the multicast and broadcast service function network element, as shown in Figure 19 The method comprises:

[0304] S1901、The first network element receives a first request message, the first request message comprising at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified comprising an MBS service area corresponding to an access network device.

[0305] S1902、The first network element allocates, according to the first request message, the at least one temporary mobile group identifier to the at least one MBS service area to be identified, to create at least one MBS session.

[0306] S1903, in a case that the first network element includes the MBS service area information in the MBS session identification of any MBS session, and the MBS service area information includes the geographic area information and / or the civic address information, the geographic area information and / or the civic address information is translated into the cell identification, or the list of tracking area identifications, or the area information identification.

[0307] In an example, the MBS session identification can include at least one of the following: a temporary mobile group identification (TMGI), synchronization status message (SSM), MBS service area information, session description information, access type information. In some optional examples, the access type information can also be radio access technology (RAT) type information.

[0308] For example, the MBS session identification can include the access type information or the RAT type information, which can represent a trusted non-3GPP access method.

[0309] In another example, the MBS service area information includes at least one of the following: a cell identification (Cell ID), a list of tracking area identifications (TAI list), geographic area information, civic address information, area information, which can be identified by an access network device and mapped to an area covered by a non-3GPP access point. The area information can be an area information identification corresponding to the area information.

[0310] In another example, the MBS service area information includes at least one of the following: a cell identification (Cell ID), a list of tracking area identifications (TAI list), geographic area information, civic address information, area information, which can be identified by an access network device, such as a non-3GPP access network device, and mapped to an area covered by a non-3GPP access point. The area information can be an area information identification corresponding to the area information.

[0311] It can be understood that the cell identification, the list of tracking area identifications, the geographic area information, the civic address information, and the area information can all be identified by an access network device or a terminal as a certain geographic area. The MBS service area information can be represented by the cell identification, the list of tracking area identifications, the geographic area information, the civic address information, and the area information. For example, the MBS session can be uniquely identified by the address or area corresponding to the cell identification.

[0312] wherein the corresponding data amount of the cell identity, or the tracking area identity list, or the area information identifier is less than the data amount of the geographical area information and / or the civic address information.

[0313] In an example, after step S1903, the core network device can send the translated MBS service area information to the terminal through the application function network element.

[0314] In the embodiments of the present disclosure, the first network element receives the first request message including the MBS service area corresponding to the trusted non-3GPP access network device sent by the application function network element, and allocates a temporary mobile group identity to the MBS service area to identify the MBS service area corresponding to the non-3GPP access network device, thereby establishing an MBS session supporting the non-3GPP access network device, and in the case that the MBS session is identified by the MBS service area information, and the MBS service area information is characterized by the geographical area information and / or the civic address information, the first network element can translate the geographical area information and / or the civic address information into a cell identity, or a tracking area identity list, or an area information identifier with a lower data amount, so that the core network device can provide multicast and broadcast services to the terminal accessing through the non-3GPP manner while effectively reducing the data amount of transmission.

[0315] In order to enable those skilled in the art to better understand the technical solutions provided by the present disclosure, the present disclosure further provides the following exemplary embodiments as shown in Figure 20 、 Figure 21 .

[0316] Figure 20 is a flow chart of a communication method according to an exemplary embodiment, which is applied to a core network device including an application function network element and a first network element, the first network element being a network exposure function network element, or a multicast and broadcast service function network element, or a network exposure function network element and a multicast and broadcast service function network element combined, as shown in Figure 20 , the method comprises:

[0317] S2001, the application function network element sends a first request message to the first network element, the first request message including at least one temporary mobile group identity and at least one MBS service area to be identified, and the at least one MBS service area to be identified including an MBS service area corresponding to an access network device.

[0318] S2002, the first network element allocates at least one temporary mobile group identity to each MBS service area to be identified according to the first request message, to create at least one MBS session.

[0319] S2003, in a case that the first network element includes the MBS service area information in any MBS session identifier, and the MBS service area information includes the geographic area information and / or the civic address information, the geographic area information and / or the civic address information are translated into the cell identifier, the tracking area identifier list, or the area information identifier.

[0320] S2004, the application function network element sends the MBS session identifier of each MBS session to the terminal, the MBS session identifier is used to inform the terminal of the MBS session information, and the MBS session information is used for the terminal to determine whether to join any one or more MBS sessions in the at least one MBS session.

[0321] The access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0322] In step S2004, the application function network element sends the MBS session identifier of each MBS session to the terminal can be sending the MBS session identifier translated by the first network element to the terminal.

[0323] In an example, the MBS session identifier can include at least one of the following: a temporary mobile group identifier (TMGI), synchronization status information (SSM), MBS service area information, session description information, and access type information. In some optional examples, the access type information can also be radio access technology (RAT) type information.

[0324] For example, the MBS session identifier can include access type information or RAT type information, which can represent a trusted non-3GPP access method.

[0325] In another example, the MBS service area information includes at least one of the following: a cell identifier (Cell ID), a tracking area identifier list (TAI list), geographic area information, civic address information, and area information, which can be recognized by the access network device and mapped to an area covered by a non-3GPP access point. Wherein, the area information can be an area information identifier corresponding to the area information.

[0326] In another example, the MBS service area information includes at least one of the following: a cell ID, a tracking area indicator list (TAI list), geographic area information, civic address information, and zone information, which can be identified by an access network device, such as a non-3GPP access network device, and mapped to an area covered by a non-3GPP access point. The zone information can be an area information identifier corresponding to the zone information.

[0327] It can be understood that the cell ID, the TAI list, the geographic area information, the civic address information, and the zone information can all be identified by an access network device or a terminal as a certain geographic area. The MBS service area information can be represented by the cell ID, the TAI list, the geographic area information, the civic address information, and the zone information. For example, an MBS session can be uniquely identified by an address or an area corresponding to the cell ID.

[0328] The data amount corresponding to the cell ID or the TAI list or the zone information identifier is less than that of the geographic area information and / or the civic address information.

[0329] In the embodiments of the present disclosure, the core network device sends, to the first network element, a first request message including an MBS service area corresponding to a trusted non-3GPP access network device through an application function network element, and allocates a temporary mobile group identifier to the MBS service area to identify the MBS service area corresponding to the non-3GPP access network device, thereby establishing an MBS session supporting the non-3GPP access network device. In the case where the MBS session is identified by MBS service area information and the MBS service area information is represented by geographic area information and / or civic address information, the first network element can translate the geographic area information and / or the civic address information into a cell ID or a TAI list or zone information identifier with a lower data amount, so that the core network device can provide multicast and broadcast services to terminals accessing through a non-3GPP manner while effectively reducing the data amount of transmission.

[0330] Figure 21 is a communication method according to an example embodiment, as shown in the interaction diagram of the communication method shown in FIG. 10. Figure 21 The method includes the following steps.

[0331] S2101, the terminal sends a PDU session modification request to the core network device through the access network device.

[0332] S2102, the core network device determines whether to accept the terminal to join the corresponding MBS session.

[0333] S2103, in a case that the core network device determines to accept the terminal to join any MBS session, in response to determining that the access network device supports MBS, the core network device determines to transmit MBS session data by shared MBS traffic.

[0334] S2104, in a case that the access network device determines that it supports MBS, in response to determining that the MBS session is in an active state, the access network device performs first signaling exchange with the terminal.

[0335] S2105, the access network device configures non-3GPP radio resources of the multicast or broadcast MBS session for the terminal according to the first signaling.

[0336] S2106, the core network device transmits MBS session data to the access network device by shared MBS traffic.

[0337] S2107, the access network device is configured to transmit MBS session data by non-3GPP radio bearer and transmit the MBS session data to the terminal in PTP or PTM mode.

[0338] S2108, in a case that the core network device determines to accept the terminal to join any MBS session, in response to determining that the access network device does not support MBS, the core network device determines to transmit MBS session data by individual MBS traffic.

[0339] S2109, in a case that the access network device determines that it does not support MBS, in response to determining that the MBS session is in an active state, the access network device configures radio resources to transmit MBS session data by unicast through a related PDU session.

[0340] S2110, the core network device transmits MBS session data to the access network device by individual MBS traffic.

[0341] S2111, the access network device transmits the MBS session data to the terminal by unicast through a related PDU session and in PTP mode.

[0342] Wherein, the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0343] It is worth noting that the above steps S2103 to S2107 and steps S2108 to S2111 can be selectively executed, that is, corresponding to different types of non-3GPP access network devices, the communication system can execute steps S2103 to S2107 or execute steps S2108 to S2111.

[0344] In an example, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point is provided by a trusted non-3GPP satellite, or, is provided by a wireless router.

[0345] It is worth mentioning that the wireless router can be any device providing a wireless access point for a wireless local area network, such as a wireless gateway, a wireless bridge, and the like.

[0346] In addition, as a specific implementation form of the trusted non-3GPP access network, the satellite can serve as a trusted non-3GPP access point (TNAP) to provide wireless access services for the terminal. Accordingly, in the case where the trusted non-3GPP access point is provided by a trusted non-3GPP satellite, the trusted non-3GPP access device can further comprise a satellite access gateway function (S-AGF), which is equivalent to a trusted non-3GPP access gateway function (TNGF) in the trusted non-3GPP access network. The satellite can communicate with the S-AGF through a Ta interface. The S-AGF can communicate with the AMF through an N2 interface, which can be an enhanced N2 interface so that the S-AGF and the AMF can reliably communicate.

[0347] Specifically, the PDU session modification request can be sent by the terminal through an uplink NAS message and forwarded to the core network device by the access network device. The PDU session modification request can comprise one or more MBS session identifiers, and the number of MBS session identifiers is not limited by the present disclosure.

[0348] In some possible implementations, the core network device determining whether to accept the terminal to join the MBS session can be specifically performed by an SMF network element in the core network device, which can determine whether to accept the terminal to join the MBS session according to the MBS subscription data received from a UDM network element, and / or according to the terminal indication received from an MB-SMF network element. If the MBS session requested by the terminal to join is not enabled, the SMF can accept the terminal to join the MBS session and indicate the enabling time to the terminal, or, the SMF can also reject the terminal to join. If the MBS session requested by the terminal to join is in an inactive state, the SMF can accept the terminal to join the MBS session.

[0349] In some optional embodiments, in a case that the SMF accepts the terminal to join the MBS session, the SMF can send an N2 information request to the access network device, the N2 information request can include one or more of the PDU session identifier, the MBS session identifier, the updated PDU session information, and the mapping information between the unicast QoS flow and the multicast QoS flow; if there is no MBS session in the trusted non-3GPP access network, the SMF can create an MBS session context for the MBS session in the trusted non-3GPP access network, and inform the trusted non-3GPP access network of the relationship between the multicast MBS session context and the PDU session context of the terminal according to the MBS session identifier and the mapping information between the unicast QoS flow and the multicast QoS flow.

[0350] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, the PDU session modification response can be carried by the N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in a case that the access network device does not support MBS, indicate to the core network device the unicast QoS flow received by the access network device.

[0351] In an exemplary embodiment, the MBS session data sent by the core network device can be transmitted by sharing MBS traffic, specifically, the MB-UPF sends a multicast PDU to the access network device through an N3mb interface corresponding to the MBS session, so that all terminals joining the MBS session through the access network device share the interface to receive MBS session data.

[0352] In an example, the access network device can use PTP or PTM according to the MBS session data, if the MBS session data is unicast data, it can be sent to the corresponding terminal in the form of PTP, if the MBS session data is multicast data or broadcast data, it can be sent to one or more corresponding terminals in the form of PTM.

[0353] In an optional embodiment, the access network device can send a PDU session modification response to the core network device, the PDU session modification response can be carried by the N2 information response. The PDU session modification response can be used to indicate to the core network device whether the access network device supports MBS, and in a case that the access network device does not support MBS, indicate to the core network device the unicast QoS flow received by the access network device.

[0354] In an example embodiment, the MBS session data sent by the core network device can be sent in a separate MBS traffic, specifically, the MB-UPF sends multicast PDUs to the UPF through the N19mb interface corresponding to the MBS session, each MBS session and the corresponding UPF has only one interface, that is, all PDU sessions provided by each UPF share the interface, so that the UPF forwards the multicast MBS session data to the access network device in a unicast manner, and the access network device forwards the MBS session data to the terminal in a unicast manner. The MBS session data is transmitted through the radio bearer corresponding to the related QoS flow of the related PDU session, that is, the MBS session data is transmitted to the access network device through the PDU session, and the MBS session data is forwarded to the terminal by the access network device. The related QoS flow can be carried by the N2 information request described above.

[0355] In an example, the access network device sends the MBS session data to the terminal in a PTP manner, which can be multicast or broadcast MBS session data transmitted to the terminal that joins the MBS session through the access network device through a PDU session.

[0356] In the embodiments of the present disclosure, the trusted non-3GPP access network device forwards the PDU session modification request sent by the terminal to the core network device, so that the core network device determines whether to accept the terminal to join the MBS session, and after accepting the terminal to join the MBS session, the MBS session data is transmitted to the terminal in a unicast manner through the related PDU session when the MBS session is in an active state, or the MBS session data is transmitted to the terminal in a PTP or PTM manner based on a non-3GPP radio bearer, which ensures that the access network device can effectively transmit the MBS session data in the case of supporting or not supporting MBS, so that the core network device can provide multicast and broadcast services to the terminal accessed through a non-3GPP manner.

[0357] Based on the same inventive concept, the embodiments of the present disclosure also provide the following communication devices.

[0358] Figure 22 is a block diagram of a communication device according to an example embodiment, which is applied to a core network device, as Figure 22 As shown in the figure, the communication device 2200 includes:

[0359] The first receiving module 2201 is configured to receive the PDU session modification request sent by the access network device, and the PDU session modification request includes the MBS session identifier, which is used to represent the MBS session requested by the terminal to join;

[0360] The determining module 2202 is configured to determine whether to accept the terminal to join the MBS session;

[0361] The access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

[0362] Optionally, the trusted non-3GPP access network device includes a trusted non-3GPP access point, and the trusted non-3GPP access point is provided by a trusted non-3GPP satellite or by a wireless router.

[0363] Optionally, the core network device includes an application function network element and a first network element, and the first network element is a network exposure function network element, or is a multicast and broadcast service function network element, or is a network exposure function network element and a multicast and broadcast service function network element combined.

[0364] Optionally, the communication device 2200 is configured to:

[0365] Optionally, the communication device 2200 is configured to:

[0366] Optionally, the communication device 2200 is configured to:

[0367] Optionally, the communication device 2200 is configured to:

[0368] Optionally, the communication device 2200 is configured to:

[0369] Optionally, the communication device 2200 is configured to:

[0370] Optionally, the communication device 2200 is configured to:

[0371] Optionally, the communication device 2200 is configured to:

[0372] In a case that the MBS service area information includes the geographic area information and / or the civic address information, the geographic area information and / or the civic address information are translated into the cell identity, the list of tracking area identities, or the area information identity by the first network element.

[0373] Optionally, the communication apparatus 2200 comprises:

[0374] The first determining module is configured to, in a case that the terminal is determined to join any MBS session, determine to transmit the MBS session data by the shared MBS traffic in response to determining that the access network device supports the MBS.

[0375] Optionally, the communication apparatus 2200 comprises:

[0376] The fourth sending module is configured to send the MBS session data to the access network device, the access network device being configured to transmit the MBS session data by the non-3GPP radio bearer and transmit the MBS session data to the terminal by the PTP or the PTM manner.

[0377] Optionally, the non-3GPP radio is configured by the access network device in response to determining that the access network device supports the MBS and determining that the MBS session joined by the terminal is in an active state according to the first signaling, the first signaling including a PDU session modification command exchanged between the access network device and the terminal.

[0378] Optionally, the communication apparatus 2200 comprises:

[0379] The second determining module is configured to, in a case that the terminal is determined to join any MBS session, determine to transmit the MBS session data by the separate MBS traffic in response to determining that the access network device does not support the MBS.

[0380] Optionally, the communication apparatus 2200 comprises:

[0381] The fifth sending module is configured to send the MBS session data to the access network device, the access network device being configured to transmit the MBS session data by the related PDU session in a unicast manner and transmit the MBS session data to the terminal by the PTP manner.

[0382] Optionally, the related PDU session is configured by the access network device in response to determining that the access network device does not support the MBS and determining that the MBS session joined by the terminal is in an active state.

[0383] Figure 23is a block diagram of a communication apparatus according to an exemplary embodiment, applied to an access network device, the access network device being a trusted non-3GPP access network device, and a terminal communicates with a core network device in a non-3GPP manner through the trusted non-3GPP access network device;

[0384] The communication apparatus 2300 comprises:

[0385] The second receiving module 2301 is configured to receive a PDU session modification request sent by the terminal.

[0386] The first sending module 2302 is configured to send the PDU session modification request to the core network device, the PDU session modification request comprising an MBS session identifier, the MBS session identifier being used to represent an MBS session that the terminal requests to join, and the PDU session modification request being used for the core network device to determine whether to accept the terminal to join the MBS session.

[0387] Optionally, the trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point being provided by a trusted non-3GPP satellite or by a wireless router.

[0388] Optionally, the communication apparatus 2300 comprises:

[0389] The configuration module is configured to, in a case where it is determined that the core network device accepts the terminal to join the MBS session, configure radio resources for the MBS session in response to determining that the MBS session is in an active state.

[0390] Optionally, the configuration module is configured to:

[0391] In a case where the access network device supports MBS, perform first signaling exchange with the terminal, the first signaling being used for the access network device to configure non-3GPP radio resources of a multicast or broadcast MBS session for the terminal according to the first signaling, and the first signaling comprising a PDU session modification command.

[0392] Optionally, the communication apparatus 2300 comprises:

[0393] The fourth receiving module is configured to receive MBS session data sent by the core network device, transmit the MBS session data through a non-3GPP radio bearer, and transmit the MBS session data to the terminal in a PTP or PTM manner.

[0394] Optionally, the configuration module is configured to:

[0395] In a case where the access network device does not support MBS, configure radio resources to perform unicast transmission of MBS data through a related PDU session.

[0396] Optionally, the communication apparatus 2300 comprises:

[0397] The fifth receiving module is configured to receive MBS session data sent by the core network device, unicasts the MBS session data through a related PDU session, and sends the MBS session data to the terminal in a PTP manner.

[0398] Figure 24 is a block diagram of a communication apparatus according to an exemplary embodiment, which is applied to a terminal, the terminal communicates with a core network device in a non-3GPP manner through an access network device, and the access network device is a trusted non-3GPP access network device;

[0399] As shown in Figure 24 , the communication apparatus 2400 includes:

[0400] The second sending module 2401 is configured to send a PDU session modification request to the access network device, and the access network device is configured to send the PDU session modification request to the core network device;

[0401] The PDU session modification request includes an MBS session identifier, the MBS session identifier is used to represent an MBS session that the terminal requests to join, and the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session.

[0402] Optionally, the trusted non-3GPP access network device includes a trusted non-3GPP access point, and the trusted non-3GPP access point is provided by a trusted non-3GPP satellite or a wireless router.

[0403] Optionally, the communication apparatus 2400 includes:

[0404] The exchange module is configured to perform first signaling exchange with the access network device, the first signaling is used for the access network device to configure non-3GPP radio resources of a multicast or broadcast MBS session for the terminal according to the first signaling, and the first signaling includes a PDU session modification command.

[0405] Optionally, the communication apparatus 2400 includes:

[0406] The sixth receiving module is configured to receive MBS session data;

[0407] The MBS session data is MBS session data sent by the access network device through a non-3GPP radio bearer and sent in a PTP or PTM manner.

[0408] Or, the MBS session data is unicasted by the access network device through a related PDU session and sent in a PTP manner.

[0409] Optionally, the non-3GPP radio is configured according to the first signaling by the access network device in response to determining that the access network device supports MBS and determining that the MBS session joined by the terminal is in an active state; the first signaling comprises a PDU session modification command exchanged between the access network device and the terminal.

[0410] Optionally, the related PDU session is configured by the access network in response to determining that the access network device does not support MBS and determining that the MBS session joined by the terminal is in an active state.

[0411] Figure 25 is a block diagram of a communication apparatus according to an exemplary embodiment, applied to an application function network element in a core network device, such as Figure 25 As shown in FIG. 25, the communication apparatus 2500 comprises:

[0412] A third sending module 2501 configured to send a first request message to a first network element, the first request message comprising at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified comprising an MBS service area of a corresponding access network device;

[0413] The first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element combined by the network exposure function network element and the multicast and broadcast service function network element; the access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; the first request message is used for the first network element to assign the at least one temporary mobile group identifier to the at least one MBS service area to be identified according to the first request message, so as to create at least one MBS session.

[0414] Optionally, the communication apparatus 2500 comprises:

[0415] A sixth sending module configured to send an MBS session identifier of each MBS session to the terminal, the MBS session identifier being used to inform the terminal of MBS session information, the MBS session information being used for the terminal to determine whether to join any one or more MBS sessions in the at least one MBS session;

[0416] The MBS session identifier comprises at least one of the following: a temporary mobile group identifier, synchronization state information, MBS service area information, session description information, and access type information.

[0417] The MBS service area information comprises at least one of the following: a cell identifier, a tracking area identifier list, geographical area information, civic address information, and area information, the area information being identifiable by the access network device and being mapped to an area covered by a non-3GPP access point.

[0418] Figure 26 is a block diagram of a communication apparatus according to an exemplary embodiment, applied to a first network element in a core network device, the first network element being a network exposure function network element, or being a multicast and broadcast service function network element, or being a network element after the network exposure function network element and the multicast and broadcast service function network element are combined;

[0419] As shown in Figure 26 , the communication apparatus 2600 includes:

[0420] A third receiving module 2601, configured to receive a first request message sent by an application function network element, the first request message including at least one temporary mobile group identifier, and at least one to-be-identified MBS service area, the at least one to-be-identified MBS service area including an MBS service area corresponding to an access network device; wherein the access network device is a trusted non-3GPP access network device, and a terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device;

[0421] A creating module 2602, configured to allocate the at least one temporary mobile group identifier to the at least one to-be-identified MBS service area according to the first request message, to create at least one MBS session.

[0422] Optionally, the communication apparatus 2600 includes:

[0423] A translating module, configured to include MBS service area information in an MBS session identifier of any MBS session, and in the case that the MBS service area information includes geographic area information and / or civic address information, translate the geographic area information and / or the civic address information into a cell identifier, or a tracking area identifier list, or area information identifier.

[0424] Figure 27 is a block diagram of an electronic device 2700 according to an exemplary embodiment. The electronic device 2700 can be provided as a terminal, for example, the electronic device 2700 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0425] Referring to Figure 27 , the electronic device 2700 can include one or more of the following components: a processing component 2702, a memory 2704, a power supply component 2706, a multimedia component 2708, an audio component 2710, an input / output (I / O) interface 2712, a sensor component 2714, and a communication component 2716.

[0426] The processing component 2702 generally controls the overall operation of the electronic device 2700. The processing component 2702 can be or include one or more processors 2720 to execute instructions. The processing component 2702 can also include one or more modules to facilitate interaction between the processing component 2702 and other components. For example, the processing component 2702 can include a multimedia module to facilitate the interaction between the multimedia component 2708 and the processing component 2702.

[0427] The memory 2704 is configured to store various types of data to support operations of the electronic device 2700. Examples of such data include instructions for any application or methods operating on the electronic device 2700, contact data, phonebook data, messages, pictures, videos, and so on. The memory 2704 can be implemented by any type of volatile or non-volatile memory or a combination thereof such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disc or optical disc.

[0428] The power component 2706 provides power to the various components of the electronic device 2700. The power component 2706 can include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the electronic device 2700.

[0429] The multimedia component 2708 includes a screen providing an output interface between the electronic device 2700 and a user. In some embodiments, the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes the touch panel, the screen can be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense a touch, a slide, and a gesture on the touch panel. The touch sensors can not only sense a boundary of a touching or sliding action, but also detect duration and pressure related to the touching or sliding action. In some embodiments, the multimedia component 2708 includes a front camera and / or a rear camera. When the electronic device 2700 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front and rear cameras can be a fixed optical lens system or have a focal length and optical zoom capability.

[0430] The audio component 2710 is configured to output and / or input audio signals. For example, the audio component 2710 includes a microphone (MIC) that is configured to receive an external audio signal when the electronic device 2700 is in a particular mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 2704 or transmitted via the communication component 2716. In some embodiments, the audio component 2710 also includes a speaker for outputting audio signals.

[0431] The I / O interface 2712 provides an interface between the processing component 2702 and peripheral interface modules, which can include a keypad, a click wheel, buttons, and so on. The buttons can include, but are not limited to, a home button, a volume button, a start button, and a lock button.

[0432] The sensor component 2714 includes one or more sensors for providing status assessments of various aspects of the electronic device 2700. For example, the sensor component 2714 can detect an open / closed position of the electronic device 2700, relative positioning of components, such as a display and a keypad of the electronic device 2700, a change of location of the electronic device 2700 or a component of the electronic device 2700, the presence or absence of user contact with the electronic device 2700, an orientation or acceleration / deceleration of the electronic device 2700, and a temperature change of the electronic device 2700. The sensor component 2714 can include a proximity sensor configured to detect presence of a nearby object without any physical touch. The sensor component 2714 can further include a light sensor such as a CMOS or CCD image sensor for use in an imaging application. In some embodiments, the sensor component 2714 can further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0433] The communication component 2716 is configured to facilitate wired or wireless communication between the electronic device 2700 and external devices. The electronic device 2700 can access a wireless network based on a corresponding communication standard, such as WiFi, 2G, or 3G, or a combination thereof. In an example embodiment, the communication component 2716 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an example embodiment, the communication component 2716 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technology.

[0434] In an exemplary embodiment, the electronic device 2700 can be implemented with one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, or other electronic elements, for performing the above-described methods.

[0435] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions, such as the memory 2704 including instructions, is also provided, which can be executed by the processor 2720 of the electronic device 2700 to complete the above-described methods. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disc, and an optical data storage device, etc.

[0436] In another exemplary embodiment, a computer program product is also provided, which contains a computer program capable of being executed by a programmable apparatus, and the computer program has code portions for executing the above-described communication method when executed by the programmable apparatus.

[0437] Figure 28 is a block diagram of an electronic device according to an exemplary embodiment. For example, the electronic device 2800 can be provided as a core network or other network logical entity in an access network. Referring to Figure 28 , the electronic device 2800 includes a processing component 2822, which further includes one or more processors, and memory resources represented by a memory 2832, for storing instructions executable by the processing component 2822, such as application programs. The application programs stored in the memory 2832 can include one or more than one module each corresponding to a set of instructions. In addition, the processing component 2822 is configured to execute the instructions to perform the steps of the communication method provided by the above-described method embodiments.

[0438] The electronic device 2800 can also include a power supply component 2826 configured to perform power management of the apparatus 2800, a wired or wireless network interface 2850 configured to connect the electronic device 2800 to a network, and an input / output interface 2858. The electronic device 2800 can operate based on an operating system stored in the memory 2832, such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM or the like.

[0439] In another exemplary embodiment, there is also provided a computer program product comprising a computer program capable of being executed by a programmable apparatus, the computer program having code portions for performing the communication method described above when executed by the programmable apparatus.

[0440] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the present disclosure. It is intended that the present disclosure cover any and all variations of the present disclosure including those variations that can be incorporated into the above detailed description and making use of known additives and known terminology. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

Claims

1. A communication method characterized by comprising: The method is applied to a core network device, and the method comprises: After a first MBS session is created, a first MBS session identifier of at least one of the first MBS sessions is sent to a terminal, wherein the first MBS session identifier comprises at least one of access type information and area information, the access type information is used to indicate a trusted non-3GPP access mode, and the area information can be identified by an access network device and mapped to an area covered by a non-3GPP access point; A PDU session modification request sent by the access network device is received, the PDU session modification request comprises an MBS session identifier, the MBS session identifier is used to represent an MBS session requested to be joined by the terminal, and the MBS session requested to be joined by the terminal is any one or more of the first MBS sessions; It is determined whether to accept the terminal to join the MBS session; The access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP mode through the trusted non-3GPP access network device.

2. The method of claim 1, wherein, The trusted non-3GPP access network device comprises a trusted non-3GPP access point, the trusted non-3GPP access point is provided by a trusted non-3GPP satellite or a wireless router.

3. The method according to any one of claims 1 or 2, characterized in that, The core network device comprises an application function network element and a first network element, the first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined; The method comprises: The application function network element sends a first request message to the first network element, the first request message comprises at least one temporary mobile group identifier and at least one MBS service area to be identified, and the at least one MBS service area to be identified comprises an MBS service area corresponding to the access network device; The first network element allocates the at least one temporary mobile group identifier to each of the MBS service areas to be identified according to the first request message, so as to create at least one of the first MBS sessions.

4. The method of claim 3, wherein, The first MBS session identifier of at least one of the first MBS sessions is sent to a terminal, which comprises: The application function network element sends the first MBS session identifier of each of the first MBS sessions to the terminal, the first MBS session identifier is used to inform the terminal of MBS session information, and the MBS session information is used for the terminal to determine whether to join any one or more of the first MBS sessions; The first MBS session identifier further comprises at least one of the following: a temporary mobile group identifier, synchronization state information, MBS service area information, and session description information; The MBS service area information comprises at least one of the following: a cell identifier, a tracking area identifier list, geographical area information, and civic address information.

5. The method of claim 4, wherein, The method comprises: In a case that the MBS service area information is included in any of the first MBS session identifiers, and the MBS service area information includes geographic area information and / or civic address information, the geographic area information and / or civic address information is translated by the first network element into the cell identity, the list of tracking area identities, or the area information identity.

6. The method of claim 1 or 2, wherein, The method comprises: In a case that it is determined to accept the terminal to join any of the MBS sessions, it is determined to transmit MBS session data using shared MBS traffic in response to determining that the access network device supports MBS.

7. The method of claim 6, wherein, The method comprises: The MBS session data is transmitted to the access network device, which is configured to transmit the MBS session data through a non-3GPP radio bearer and using PTP or PTM mode to the terminal.

8. The method of claim 7, wherein, The non-3GPP radio is configured by the access network device for the MBS session joined by the terminal in response to determining that the access network device supports MBS and determining that the MBS session joined by the terminal is in an active state, and the first signaling includes a PDU session modification command exchanged between the access network device and the terminal.

9. The method of claim 1 or 2, wherein, The method comprises: In a case that it is determined to accept the terminal to join any of the MBS sessions, it is determined to transmit MBS session data using separate MBS traffic in response to determining that the access network device does not support MBS.

10. The method of claim 8, wherein, The method comprises: The MBS session data is transmitted to the access network device, which is configured to transmit the MBS session data through a related PDU session in unicast mode and using PTP mode to the terminal.

11. The method of claim 10, wherein, The related PDU session is configured by the access network device for the MBS session joined by the terminal in response to determining that the access network device does not support MBS and determining that the MBS session joined by the terminal is in an active state.

12. A communication method characterized by comprising: Applied to a terminal, the terminal communicates with a core network device in a non-3GPP manner through an access network device, and the access network device is a trusted non-3GPP access network device. The method comprises: A first MBS session identifier of at least one first MBS session is received, which is sent by the core network device, wherein the first MBS session identifier is used to indicate at least one of access type information and area information, the access type information is used to indicate a trusted non-3GPP access manner, and the area information can be recognized by the access network device and mapped to an area covered by a non-3GPP access point; A PDU session modification request is sent to the access network device, which is configured to send the PDU session modification request to the core network device; The PDU session modification request includes an MBS session identifier, which is used to represent an MBS session requested to be joined by the terminal, and the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session, and the MBS session requested to be joined by the terminal is any one or more MBS sessions in the first MBS sessions.

13. The method of claim 12, wherein, The trusted non-3GPP access network device includes a trusted non-3GPP access point, which is provided by a trusted non-3GPP satellite or a wireless router.

14. The method according to claim 12 or 13, characterized in that, The method includes: performing a first signaling exchange with the access network device, the first signaling being used by the access network device to configure non-3GPP radio resources for the terminal according to the first signaling for a multicast or broadcast MBS session, the first signaling including a PDU session modification command.

15. The method of claim 12 or 13, wherein, The method includes: receiving MBS session data; wherein the MBS session data is transmitted by the access network device through a non-3GPP radio bearer and in a PTP or PTM manner; or The MBS session data is transmitted by the access network device through a related PDU session in a unicast manner and in a PTP manner.

16. The method of claim 15, wherein, The non-3GPP radio is configured by the access network device for the MBS session joined by the terminal in response to determining that the access network device supports MBS and that the MBS session joined by the terminal is in an active state, and the first signaling includes a PDU session modification command obtained by the access network device through exchange with the terminal.

17. The method of claim 15, wherein, The related PDU session is configured by the access network in response to determining that the access network device does not support MBS and that the MBS session joined by the terminal is in an active state.

18. A method of communication, comprising: An application function network element applied in a core network device, the method includes: sending a first request message to a first network element, the first request message including at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified including an MBS service area of a corresponding access network device; wherein the first network element is a network exposure function network element or a multicast and broadcast service function network element or a network element combined after the network exposure function network element and the multicast and broadcast service function network element; the access network device is a trusted non-3GPP access network device, and a terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; the first request message is used by the first network element to assign the at least one temporary mobile group identifier to the at least one MBS service area to be identified according to the first request message, so as to create at least one first MBS session; after creating the first MBS session, sending a first MBS session identifier of the at least one first MBS session to the terminal, wherein the first MBS session identifier includes at least one of access type information and area information, the access type information being used to indicate a trusted non-3GPP access mode, and the area information being identifiable by an access network device and being mapped to an area covered by a non-3GPP access point; the first MBS session identifier is used to inform the terminal of MBS session information, and the MBS session information is used by the terminal to determine whether to join any one or more MBS sessions in the at least one first MBS session.

19. The method of claim 18, wherein, The MBS session identifier further includes at least one of: a temporary mobile group identifier, synchronization state information, MBS service area information, session description information; The MBS service area information includes at least one of: a cell identifier, a tracking area identifier list, geographical area information, civic address information.

20. A method of communication, comprising: The method is applied to a first network element in a core network device, and the first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined. The method includes: receiving a first request message sent by an application function network element, the first request message including at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified including an MBS service area of a corresponding access network device; wherein the access network device is a trusted non-3GPP access network device, and a terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; allocating the at least one temporary mobile group identifier to the at least one MBS service area to be identified according to the first request message, to create at least one first MBS session; each first MBS session corresponds to a first MBS session identifier, wherein the first MBS session identifier includes at least one of access type information and area information, the access type information is used to indicate a trusted non-3GPP access manner, and the area information can be identified by an access network device and mapped to an area covered by a non-3GPP access point; The first MBS session identifier is used to inform the terminal of MBS session information, and the MBS session information is used by the terminal to determine whether to join any one or more MBS sessions in the at least one first MBS session.

21. The method of claim 20, wherein, The method includes: In the case that the MBS service area information is included in the first MBS session identifier of any first MBS session, and the MBS service area information includes geographical area information and / or civic address information, the geographical area information and / or the civic address information are translated into a cell identifier, or a tracking area identifier list, or area information identifier.

22. A communications device, characterized by The method is applied to a core network device, and the device includes: A seventh sending module is configured to send a first MBS session identifier of at least one first MBS session to a terminal after the first MBS session is created, wherein the first MBS session identifier includes at least one of access type information and area information, the access type information is used to indicate a trusted non-3GPP access manner, and the area information can be identified by an access network device and mapped to an area covered by a non-3GPP access point; A first receiving module is configured to receive a PDU session modification request sent by a terminal through an access network device, the PDU session modification request including an MBS session identifier, the MBS session identifier being used to represent an MBS session requested to be joined by the terminal, and the MBS session requested to be joined by the terminal being any one or more MBS sessions in the first MBS session; determining whether to accept the terminal to join the MBS session; The access network device is a trusted non-3GPP access network device, and the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device.

23. A communications device, characterized by The application is applied to a terminal, the terminal communicates with a core network device in a non-3GPP manner through an access network device, and the access network device is a trusted non-3GPP access network device; the device comprises: The seventh receiving module is configured to receive first MBS session identifiers of at least one first MBS session sent by the core network device, wherein the first MBS session identifiers comprise at least one of access type information and area information, the access type information is used to indicate a trusted non-3GPP access manner, and the area information can be identified by an access network device and mapped to an area covered by a non-3GPP access point; The second sending module is configured to send a PDU session modification request to the access network device, and the access network device is used to send the PDU session modification request to the core network device; The PDU session modification request comprises an MBS session identifier, the MBS session identifier is used to represent an MBS session requested by the terminal to join, the PDU session modification request is used for the core network device to determine whether to accept the terminal to join the MBS session, and the MBS session requested by the terminal to join is any one or more MBS sessions in the first MBS sessions.

24. A communications device, characterized by The application is applied to an application function network element in a core network device. The device comprises: The third sending module is configured to send a first request message to a first network element, the first request message comprises at least one temporary mobile group identifier and at least one MBS service area to be identified, and the at least one MBS service area to be identified comprises an MBS service area of a corresponding access network device; The first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element after the network exposure function network element and the multicast and broadcast service function network element are combined, the access network device is a trusted non-3GPP access network device, the terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device, and the first request message is used for the first network element to allocate the at least one temporary mobile group identifier to the at least one MBS service area to be identified according to the first request message, so as to create at least one first MBS session; The eighth sending module is configured to send first MBS session identifiers of at least one first MBS session to a terminal after the first MBS sessions are created, wherein the first MBS session identifiers comprise at least one of access type information and area information, the access type information is used to indicate a trusted non-3GPP access manner, and the area information can be identified by an access network device and mapped to an area covered by a non-3GPP access point. The first MBS session identifier is used to inform the terminal of MBS session information, which is used by the terminal to determine whether to join any one or more MBS sessions in the at least one first MBS session.

25. A communications device, characterized by The first network element is a network exposure function network element, or a multicast and broadcast service function network element, or a network element combined from the network exposure function network element and the multicast and broadcast service function network element. The apparatus comprises: The third receiving module is configured to receive a first request message sent by an application function network element, the first request message comprising at least one temporary mobile group identifier and at least one MBS service area to be identified, the at least one MBS service area to be identified comprising an MBS service area corresponding to an access network device; wherein the access network device is a trusted non-3GPP access network device, and a terminal communicates with the core network device in a non-3GPP manner through the trusted non-3GPP access network device; The creating module is configured to allocate the at least one temporary mobile group identifier to the at least one MBS service area to be identified according to the first request message, to create at least one first MBS session; Each first MBS session corresponds to a first MBS session identifier, wherein the first MBS session identifier comprises at least one of access type information and area information, the access type information being used to indicate a trusted non-3GPP access manner, and the area information being capable of being recognized by an access network device and mapped to an area covered by a non-3GPP access point; The first MBS session identifier is used to inform the terminal of MBS session information, which is used by the terminal to determine whether to join any one or more MBS sessions in the at least one first MBS session.

26. An electronic device, comprising: Comprise: A processor; A memory for storing processor-executable instructions; The processor is configured to perform the steps of any one of claims 1-11, or the steps of any one of claims 12-17, or the steps of any one of claims 18-19, or the steps of any one of claims 20-21.

27. A computer-readable storage medium having stored thereon computer program instructions, wherein, The program instructions, when executed by the processor, implement the steps of any one of claims 1-11, or the steps of any one of claims 12-17, or the steps of any one of claims 18-19, or the steps of any one of claims 20-21.

Images