Method, device, storage medium and program product for handling mbs session

Abstract

Embodiments of the present application provide a kind of MBS session processing method, equipment, storage medium and program product, method includes: receiving the session association message sent by second network node, second network node is one of AMF and MB-SMF, session association message is associated with at least one second MBS session, at least one second MBS session is the MBS session of second network node;According to session association message, at least one second MBS session is compared with at least one first MBS session, and the comparison result is obtained, wherein, at least one first MBS session is the MBS session of first network node, and first network node is the other of AMF and MB-SMF;In response to the comparison result indicating that at least one second MBS session is inconsistent with at least one first MBS session, MBS session processing is performed, to make the MBS session of first network node consistent with the MBS session of second network node.So, it can reduce the waste of communication resources.

Description

Technical Field

[0001] This application relates to the field of communication equipment technology, and in particular to a method, device, storage medium and program product for processing MBS sessions. Background Technology

[0002] In 5G (5th Generation Mobile Communication Technology), to transmit service data in Multicast Broadcast Service (MBS), user equipment (UE) devices requiring MBS need to be added to the MBS session. The Access and Mobility Management Function (AMF) and the Multicast / Broadcast Session Management Function (MB-SMF), as core functions in the 5G system, work together to enable user devices to be added to the MBS session.

[0003] However, due to factors such as MB-SMF and AMF maintaining their respective resources, 5G base station (gNodeb) disaster recovery session release and reconstruction, and MBS session process conflicts, the MBS sessions on AMF and MB-SMF may be inconsistent, resulting in a waste of communication resources. Summary of the Invention

[0004] This application provides a method, device, storage medium, and program product for processing MBS sessions, which helps to reduce the waste of communication resources.

[0005] In a first aspect, embodiments of this application provide a method for processing an MBS session, applied to a first network node, wherein the first network node is one of an AMF and an MB-SMF, the method comprising:

[0006] Receive a session association message sent by a second network node, the second network node being the other of the AMF and the MB-SMF, the session association message being associated with at least one second MBS session, the at least one second MBS session being an MBS session of the second network node;

[0007] According to the session association message, the at least one second MBS session is compared with at least one first MBS session to obtain a comparison result, wherein the at least one first MBS session is the MBS session of the first network node;

[0008] In response to the comparison result indicating that the at least one second MBS session is inconsistent with the at least one first MBS session, MBS session processing is performed to make the MBS session of the first network node consistent with the MBS session of the second network node.

[0009] Secondly, embodiments of this application provide a method for processing MBS sessions, applied to a second network node, the second network node being either an AMF or an MB-SMF, the method comprising:

[0010] A session association message is sent to a first network node, which is the other of the AMF and the MB-SMF. The session association message is associated with at least one second MBS session, which is an MBS session of the second network node.

[0011] The session association message is used to instruct the first network node to compare the at least one second MBS session with at least one first MBS session to obtain a comparison result, wherein the at least one first MBS session is the MBS session of the first network node; and, in response to the comparison result indicating that the at least one second MBS session is inconsistent with the at least one first MBS session, to perform MBS session processing to make the MBS session of the first network node consistent with the MBS session of the second network node.

[0012] Thirdly, embodiments of this application provide a communication device, including: one or more processors; and a memory storing one or more programs thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the MBS session processing method as described in the first and second aspects.

[0013] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the MBS session processing method described in the first and second aspects.

[0014] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the MBS session processing method described in the first and second aspects.

[0015] In this embodiment, a session association message is received from a second network node, which is either an AMF or an MB-SMF. The session association message is associated with at least one second MBS session, which is an MBS session of the second network node. Based on the session association message, at least one second MBS session is compared with at least one first MBS session to obtain a comparison result. At least one first MBS session is an MBS session of the first network node, which is the other of the AMF and MB-SMF. In response to the comparison result indicating that at least one second MBS session is inconsistent with at least one first MBS session, MBS session processing is performed to make the MBS session of the first network node consistent with the MBS session of the second network node. Thus, MBS sessions of the AMF and MB-SMF can be compared, and MBS session processing can be performed when the MBS sessions of the AMF and MB-SMF are inconsistent, thereby achieving MBS session consistency between the AMF and MB-SMF and reducing the waste of communication resources. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the structure of a 5G communication system in related technologies;

[0017] Figure 2 A flowchart illustrating an embodiment of the MBS session processing method provided in this application;

[0018] Figure 3 A flowchart illustrating the process of establishing an MBS session in related technologies;

[0019] Figure 4 A flowchart illustrating an embodiment of another MBS session processing method provided in this application;

[0020] Figure 5 A schematic diagram of the structure of an embodiment of the communication device provided in this application. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions provided in this application will be described in detail below with reference to the accompanying drawings.

[0022] Exemplary embodiments will be described more fully below with reference to the accompanying drawings; however, the described exemplary embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will enable those skilled in the art to fully understand the scope of this application.

[0023] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of a feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded.

[0025] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0026] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in common dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this application, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in the embodiments of this application.

[0027] The embodiments of this application will be further described below with reference to the accompanying drawings.

[0028] Please see Figure 1 This is a schematic diagram of the architecture of a 5G system in related technologies. For example... Figure 1 As shown, a 5G system may specifically include the following functional entities:

[0029] UE (User Equipment): This refers to user equipment, such as mobile phones and other terminal devices, which is the interface through which users communicate with the network. It connects to the Radio Access Network (RAN) through a wireless interface (such as the Uu interface) and supports various wireless communication functions, including voice calls and data transmission.

[0030] NG-RAN (Next-Generation Radio Access Network): This refers to the next-generation radio access network. It includes equipment such as base stations, responsible for transmitting and receiving radio signals and managing radio resources, providing radio access services to UEs. NG-RAN communicates with UEs via the Uu interface and connects to the core network (such as functional entities like AMF and SMF) via interfaces such as N3.

[0031] AMF (Access and Mobility Management Function): It is primarily responsible for UE access control, mobility management, and registration management. For example, when a UE enters a new cell or moves, the AMF handles the relevant access and handover procedures. It communicates with the UE through the N1 interface, with the RAN through the N2 interface, and with the SMF through the N11 interface, etc.

[0032] SMF (Session Management Function): Primarily responsible for managing session creation, modification, and release. It controls the paths and policies of the User Plane (UP) and collaborates with entities such as the User Plane Function (UPF) to handle user data traffic. SMF communicates with the UPF via the N4 interface and with the AMF via the N11 interface, among other things.

[0033] MB-SMF (Multicast Service Management Function): This is a dedicated management entity for multicast services, responsible for managing the establishment, maintenance, and termination of MBS (Multicast Broadcast Service) sessions. It communicates with other functional entities (such as AMF and SMF) through the N11mb interface to manage multicast services.

[0034] UPF (User Plane Function): It is primarily responsible for user data forwarding, routing, and flow control. The UPF is the user data processing node in the core network; it communicates with the RAN via the N3 interface and with the SMF via the N4 interface, etc.

[0035] MB-UPF (Multicast Broadcast User Plane Function): This is a user plane function entity specifically designed to handle multicast broadcast services, responsible for forwarding and broadcasting multicast data. It works in conjunction with other functional entities such as MB-SMF to enable data transmission during MBS sessions.

[0036] AF / AS (Application Function / Application Server): It provides various application services, such as video streaming and software updates. It can initiate multicast service requests to the core network (such as MB-SMF) to provide its content to multiple UEs via multicast.

[0037] MBSF (Multicast Broadcast Service Function): This function is primarily responsible for authorization and security policy management of multicast services. It communicates with other functional entities (such as MB-SMF) through the Nmb interface to ensure the legitimacy and security of multicast services.

[0038] MBSTF (Multicast Broadcast Service Traffic Function): This function controls and manages multicast broadcast service traffic, including operations such as traffic aggregation and distribution.

[0039] UDM (Unified Data Management): It is primarily responsible for storing and managing user-related data, such as user identity information and subscription data. It communicates with functional entities like SMF through the N10 interface, providing user data support for functions such as session management.

[0040] PCF (Policy Control Function): It is primarily responsible for formulating and managing network policies, such as access policies and billing policies. It communicates with other functional entities (such as MB-SMF) through the N7mb interface to provide policy support for multicast service management.

[0041] NEF (Network Exposure Function): It is primarily responsible for exposing network capabilities to third-party applications, such as providing network information to application servers. It communicates with other functional entities (such as PCF) through interfaces like the N30 interface.

[0042] In 5G systems, MBS (Multicast Broadcast Service) sessions are a communication mechanism established to provide broadcast or multicast services to multiple user terminals. This differs from unicast communication, which is point-to-point, while MBS is one-to-many.

[0043] Establishing an MBS session is fundamental to the communication process. Only after successfully establishing an MBS session can a user terminal (UE) receive broadcast or multicast content from the network side, such as software updates, news broadcasts, live sports events, and other services. For example, when a television station broadcasts a sports event live via a 5G network, an MBS session needs to be established first so that numerous viewers' UEs can receive the live broadcast signal.

[0044] The specific processing flow for establishing an MBS session can be divided into the following stages: triggering phase, notification phase, paging phase, service request and message passing phase, and session activation and confirmation phase, as detailed below:

[0045] Triggering phase:

[0046] MB-SMF triggers session activation: The MB-SMF receives a multicast service request from the AF / AS, or triggers the MBS session activation process according to predefined policies, etc. This may be because there is new multicast content (such as a live broadcast of a sports event) that needs to be broadcast to the UE.

[0047] Notification phase:

[0048] Session activation message is passed to SMF: MB-SMF sends a session activation message to SMF, informing SMF that an MBS session is to be established.

[0049] MBS_Session_Notification Request and Response: After receiving the message, the SMF sends an MBS_Session_Notification request to the AMF. Upon receiving the request, the AMF processes it accordingly and returns an MBS_Session_Notification response. This process informs the AMF that a new MBS session needs to be processed, and also allows the AMF to prepare the necessary resources.

[0050] Paging phase:

[0051] AMF Paging of Idle Mode UEs: The AMF is responsible for paging UEs in idle mode. This is because when a UE is in idle mode, it may not be aware of any new MBS sessions that need to be joined. The AMF's paging operation can wake up these UEs and prepare them to receive MBS session-related information.

[0052] Service request and message passing phase:

[0053] After receiving a paging message, the UE initiates a service request. Then, an MBS_Session_Notification response message is transmitted between the AMF and SMF. Next, the AMF forwards relevant information to the RAN via a Namf_Communication_N1N2MessageTransfer message. Simultaneously, the SMF sends an N2 request to the UPF for establishing user plane connection paths and related operations.

[0054] Session activation and confirmation phase:

[0055] MB-SMF performs session activation and confirmation message transmission: MB-SMF activates the session and finally sends the activation information to the UE through an activation message, informing the UE that the MBS session has been successfully established and the UE can start receiving the corresponding broadcast or multicast content.

[0056] However, during 5G communication, factors such as the MB-SMF and AMF maintaining their respective resources, the release and reconstruction of 5G base station (gNodeb) disaster recovery sessions, and MBS session process conflicts may lead to inconsistencies in MBS sessions on the AMF and MB-SMF, resulting in a waste of communication resources.

[0057] Based on this, embodiments of this application provide a method, apparatus, storage medium, and program product for processing MBS sessions. The method involves receiving a session association message sent by a second network node (either an AMF or an MB-SMF), where the second network node is associated with at least one second MBS session, which is an MBS session of the second network node. According to the session association message, the at least one second MBS session is compared with at least one first MBS session to obtain a comparison result, where at least one first MBS session is an MBS session of a first network node, and the first network node is the other of the AMF and MB-SMF. In response to the comparison result indicating that at least one second MBS session is inconsistent with at least one first MBS session, MBS session processing is performed to make the MBS session of the first network node consistent with the MBS session of the second network node. In this way, MBS sessions of the AMF and MB-SMF can be compared, and MBS session processing can be performed when there is inconsistency between the MBS sessions of the AMF and MB-SMF, thereby achieving MBS session consistency between the AMF and MB-SMF and reducing the waste of communication resources.

[0058] Based on the aforementioned 5G communication system, the following are embodiments of MBS session processing methods, devices, storage media, and program products.

[0059] Please refer to Figure 2 This is a flowchart illustrating the MBS session processing method provided in an embodiment of this application. The method is applied to a first network node, which is either an AMF or an MB-SMF. Figure 2 As shown, the processing method for this MBS session includes the following steps S201 to S203.

[0060] Step S201: Receive the session association message sent by the second network node.

[0061] In this step, the second network node is either AMF or MB-SMF. For example, the first network node could be AMF, and the second network node could be MB-SMF; or, the first network node could be MB-SMF, and the second network node could be AMF.

[0062] The aforementioned session association message can be a message associated with at least one second MBS session. Specifically, the session association message can include MBS indication information indicating the at least one second MBS session, such as the MBS session's identification information (ID).

[0063] For example, the session association message may directly carry the identification information of at least one second MBS session; or, the session association message may include a list of MBS sessions associated with the second network node (which may be referred to as the "second MBS session list" for ease of distinction later), which includes the identification information (ID) of the second MBS session, and so on.

[0064] The aforementioned at least one second MBS session is an MBS session of a second network node, and the aforementioned at least one second MBS session is associated with the aforementioned first network node, that is, each second MBS session is an MBS session established by the interaction between the first network node and the second network node during the session establishment process.

[0065] The aforementioned receipt of a session association message sent by the second network node may be an instance where the second network node actively sends a session association message to the first network node.

[0066] For example, in the case where the first network node is AMF and the second network node is MB-SMF, MB-SMF may periodically send session association messages to AMF so that AMF can periodically know about MBS sessions in MB-SMF; or, MB-SMF may respond to a first triggering instruction and trigger the sending of session association messages to AMF, and the first triggering instruction may be generated based on user operations, etc.

[0067] In some embodiments, before step S201, the following steps are also included:

[0068] Send a session request message to the second network node;

[0069] Step S201 above may include:

[0070] Receive the session association message returned by the second network node in response to the session request message.

[0071] In this embodiment, the first network node can request the second network node to provide corresponding session association messages through a session request message, thereby enabling the first network node to proactively learn about the MBS sessions in the second network node.

[0072] The aforementioned sending of a session request message to the second network node can be performed by the first network node according to a preset message sending rule, which may be periodically executing the sending of session request messages to the second network node; or it can be triggered by a second triggering instruction, which may be generated based on user operations, etc.

[0073] For example, if the first network node is AMF and the second network node is MB-SMF, AMF can send a session request message to MB-SMF when the preset period arrives, and MB-SMF can respond to the session request message sent by AMF by sending a session association message to AMF.

[0074] It should be noted that the aforementioned session request message may be a request message used to request information on all MBS sessions in the second network node. In this case, the session association message fed back by the second network node in response to the session request message may include information on all MBS sessions in the second network node, and the aforementioned at least one second MBS session may be an MBS session associated with the first network node determined by the first network node based on the session association message.

[0075] For example, if an MB-SMF has established MBS sessions with multiple AMFs (i.e., the MBS sessions in the MB-SMF include MBS sessions associated with the multiple AMFs), and the MB-SMF receives a session request message from any of the AMFs (i.e., the first network node), the MB-SMF can send a session association message to that AMF carrying information about the MBS sessions associated with the multiple AMFs, and that AMF can learn from the session association message about at least one second MBS session associated with itself.

[0076] In some implementations, sending a session request message to the second network node includes:

[0077] Send a session request message to the second network node, carrying the node identification information of the first network node;

[0078] The aforementioned session association message received in response to the session request message from the second network node may include:

[0079] The system receives a second MBS session list in response to a session request message from a second network node. The second MBS session list includes information about at least one second MBS session, which is an MBS session associated with the first network node determined by the second network node based on node identification information in the MBS session of the second network node. The session request message includes the second MBS session list.

[0080] In this embodiment, the first network node can request a second MBS session list from the second network node, which includes information about at least one second MBS session, by using a session request message carrying its node identifier information.

[0081] The node identification information mentioned above can be any information used to indicate the second network node. For example, if the first network node is AMF and the second network node is MB-SMF, the node identification information can be the AMF's Network Function ID (NFID), etc.

[0082] The second network node's feedback of the second MBS session list can be achieved by the second network node responding to the session request message by determining, based on the node identification information, at least one second MBS session associated with the first network node from all MBS sessions in the second network node, generating a second MBS session list that includes information about at least one second MBS session, and sending the second MBS session list to the first network node associated with the node identification information.

[0083] Step S202: Based on the session association message, compare at least one second MBS session with at least one first MBS session to obtain the comparison result.

[0084] In this step, the aforementioned at least one first MBS session can be an MBS session in a first network node, and the at least one first MBS session is associated with a second network node.

[0085] The above comparison of at least one second MBS session with at least one first MBS session based on the session association message can be achieved by comparing the information of at least one second MBS session with the information of at least one first MBS session in the session association message to obtain the above comparison result.

[0086] In some implementations, step S201 may include at least one of the following:

[0087] The session identifier (MBS session ID) of at least one second MBS session is compared with the session identifier of at least one first MBS session to obtain a first comparison result, the comparison result including the first comparison result;

[0088] The service cell information (MBS service area) of at least one second MBS session is compared with the service cell information of at least one first MBS session to obtain a second comparison result, which includes the second comparison result.

[0089] In this embodiment, by comparing at least one of the session identifier and service cell information of the MBS session, the comparison result can be obtained, thereby ensuring that the session identifier and service cell information of the MBS session between the AMF and MB-SMF remain consistent.

[0090] The aforementioned first network node performs the comparison of the session identifier of at least one second MBS session with the session identifier of at least one first MBS session, and performs the comparison of the service cell information of at least one second MBS session with the service cell information of at least one first MBS session, which may be based on the same session association message.

[0091] Alternatively, the aforementioned first session association message may include a first session association message, and the first network node, in response to the first session association message, performs a comparison of the session identifier of at least one second MBS session with the session identifier of at least one first MBS session; and the aforementioned first session association message may include a second session association message, and the first network node, in response to the second session association message, performs a comparison of the service cell information of at least one second MBS session with the service cell information of at least one first MBS session.

[0092] In addition, when the first network node requests a session association message from the second network node through a session request message, the first network node may request the session identifier of at least one second MBS session and the service cell information of at least one second MBS session through a single request message; or, it may request the session identifier of at least one second MBS session and the service cell information of at least one second MBS session from the second network node through different request messages.

[0093] For example, a session identifier for at least one second MBS session can be obtained from a second network node by using a predefined first session request message (such as an MBSListRetrieval message); and service cell information for at least one second MBS session can be obtained from a second network node by using a predefined second session request message (such as an MBSProfileRetrieval message).

[0094] Step S203: In response to the comparison result indicating that at least one second MBS session is inconsistent with at least one first MBS session, perform MBS session processing to make the MBS session of the first network node consistent with the MBS session of the second network node.

[0095] In this step, the first network node can perform MBS session processing based on the above comparison results, if it is determined that at least one second MBS session is inconsistent with at least one first MBS session, so as to make the MBS session of the first network node consistent with the MBS session of the second network node.

[0096] As can be seen from the above, the comparison results may include at least one of the first comparison results and the second comparison results. The first comparison result is obtained by comparing the session identifier of at least one second MBS session with the session identifier of at least one first MBS session. The second comparison result is obtained by comparing the service cell information of at least one second MBS session with the service cell information of at least one first MBS session.

[0097] In the case where the first comparison result is obtained by comparing the session identifier of at least one second MBS session with the session identifier of at least one first MBS session, if the first comparison result indicates that there is at least one MBS session with a different session identifier between at least one second MBS session and at least one first MBS session, the first network node can perform MBS session processing to make the session identifiers of the MBS sessions of the first network node consistent with those of the MBS sessions of the second network node.

[0098] Similarly, in the case where the service cell information of at least one second MBS session and the service cell information of at least one first MBS session are compared to obtain a second comparison result, if the second comparison result indicates that there is at least one MBS session with different service cell information between at least one second MBS session and at least one first MBS session, the first network node can perform MBS session processing to make the service cell information between the MBS session of the first network node and the MBS session of the second network node consistent.

[0099] The first network node performing MBS session processing may be executing preset MBS session processing operations to ensure that the MBS session of the first network node is consistent with the MBS session of the second network node. These MBS session processing operations may include releasing or rebuilding inconsistent MBS sessions.

[0100] In some implementations, step S203 may include:

[0101] Release or rebuild the first target MBS session. The first target MBS session is defined as: at least one first MBS session that has a different MBS session from at least one second MBS session.

[0102] A session processing message is sent to the second network node. The session processing message is used to instruct the second network node to release or rebuild the second target MBS session. The second target MBS session is: at least one second MBS session that is different from at least one first MBS session.

[0103] In this embodiment, the first network node may release or rebuild a first target MBS session that is different from its own MBS session with the second network node; or, it may instruct the second network node to release or rebuild a second target MBS session that is different from its own MBS session with the first network node through a session processing message, thereby making the processing method more flexible.

[0104] For example, if the aforementioned at least one first MBS session includes MBS session 1 (i.e., the first target MBS session), and at least one of the session identifier and service cell information differs between MBS session 1 and at least one second MBS session, then the first network node may release or rebuild MBS session 1; or, if the aforementioned at least one second MBS session includes MBS session 2 (i.e., the second target MBS session), and at least one of the session identifier and service cell information differs between MBS session 2 and at least one first MBS session, then the first network node may send a first session processing message to the second network node, and the second network node, in response to the first session processing message, releases or rebuilds MBS session 2.

[0105] The first network node may release the first target MBS session if the first target MBS session exists in the first network node but does not exist in the second network node. For example, if at least one first MBS session includes MBS session 2 and at least one second MBS session does not include an MBS session with the same session identifier as MBS session 2, then the first network node may release MBS session 2.

[0106] Furthermore, the first network node can also reconstruct the first target MBS session in a situation where the first target MBS session does not exist in the first network node, but exists in the second network node. For example, if at least one first MBS session does not contain MBS session 3, but at least one second MBS session contains an MBS session with the same session identifier as MBS session 3, then the first network node can reconstruct MBS session 3.

[0107] Similarly, the process of releasing and reconstructing the second target MBS session by the second network node can be referred to the process of releasing and reconstructing the first target MBS session by the first network node, and will not be repeated here.

[0108] In some implementations, when the first network node is an AMF and the second network node is an MB-SMF, the above method further includes:

[0109] Receive a first context creation request message sent by MB-SMF. The first context creation request message carries the first service cell information of the second MBS session. The first service cell information includes indication information of at least one broadcast area (MBS service area).

[0110] If at least one broadcast area contains a target broadcast area that is not supported by the AMF, a first indication message is sent to the MB-SMF. The first indication message is used to indicate the target broadcast area.

[0111] In this embodiment, if there is a broadcast area that the AMF does not support in the first service cell information of the second MBS session carried in the first context creation request message, the AMF can send a first indication message to the MB-SMF so that the MB-SMF can know the target broadcast area that the AMF does not support.

[0112] The aforementioned first context creation request message can be a message sent by the MB-SMF to the AMF during the MBS session establishment process, carrying the first service cell information of the MB-SMF's second MBS session. For example, the first context creation request message can be as follows: Figure 3 The Namf_MBSBroadcast_ContextCreate Request message shown.

[0113] It should be noted that, if the MB-SMF learns of a target broadcast area that the AMF does not support based on the first indication information, the MB-SMF will send the corresponding second MBS session to other AMFs that support the target broadcast area according to the target broadcast area.

[0114] The aforementioned first indication information can be any information capable of indicating the target broadcast area, and it may include at least one of fields and icons. For example, the first indication information may be a newly added "unknownTAIList" field, etc.

[0115] The aforementioned AMF sending the first indication information to the MB-SMF can be achieved by carrying the first indication information in a first preset message, which is then sent from the AMF to the MB-SMF. This first preset message can be a specially configured message for carrying the first indication information.

[0116] In some implementations, sending the first instruction information to the MB-SMF includes:

[0117] In response to the context creation request message, a reply message carrying the first indication information is sent to the MB-SMF.

[0118] In this embodiment, the AMF can carry first indication information in the response message to the context creation request message, thereby further reducing the consumption of communication resources.

[0119] The above response message is the message sent by the AMF to the MB-SMF in response to the context creation request message. For example, the response message could be as follows: Figure 3 The Namf_MBSBroadcast_ContextCreate Response message shown.

[0120] In some implementations, when the first network node is an AMF and the second network node is an MB-SMF, the above method further includes:

[0121] Receive the second context creation request message sent by MB-SMF. The second context creation request message carries the second service cell information of the second MBS session. The second service cell information includes the indication information of the network side equipment under each broadcast area.

[0122] If the number of network-side devices indicated by the second service cell information is greater than the target capacity, then at least one network-side device is determined, wherein the target capacity is the maximum number of network-side devices that the AMF can support in processing the second MBS session, and at least one network-side device is a network-side device that is not supported by the AMF.

[0123] Send a second indication message to MB-SMF, the second indication message being used to instruct at least one network-side device.

[0124] In this embodiment, if the number of network-side devices indicated by the second service cell information of the second MBS session carried in the first context creation request message is greater than the maximum supportable capacity (i.e. target capacity) of the AMF, the AMF can send a second indication message to the MB-SMF so that the MB-SMF can know that there are at least one network-side device beyond the support of the AMF.

[0125] It should be noted that when the MB-SMF learns about at least one network-side device based on the second indication information, the MB-SMF will send the corresponding second MBS session to other AMFs according to the at least one network-side device.

[0126] The aforementioned second indication information can be any information capable of indicating the at least one network-side device, and may include at least one of fields and icons. For example, the second indication information may be the device identifier of the at least one network-side device.

[0127] The AMF sending the second instruction information to the MB-SMF can be achieved by carrying the second instruction information in a second preset message. The AMF then sends this second preset message to the MB-SMF. This second preset message can be a specially configured message for carrying the second instruction information.

[0128] In some implementations, sending the second instruction information to the MB-SMF includes:

[0129] In response to the second context creation request message, a context state notification request message is sent to the MB-SMF, wherein the second indication information is configured in the existing parameters of the context state notification request message.

[0130] In this embodiment, the AMF can carry second indication information in the context state notification request message in response to the context creation request message, thereby further reducing the consumption of communication resources.

[0131] The aforementioned context state notification request message is a message sent by the AMF to the MB-SMF in response to the context creation request message. For example, the AMF in... Figure 3 The Namf_MBSBroadcast_ContextStatusNotifyRequest message (i.e., the context status notification request message) sent to MB-SMF indicates the gNodeb ID corresponding to the gNodeb that has exceeded its capacity by enumerating the value "NG_RAN_ExceedCapacity" (i.e., the second indication information) in the operationEvents-ngranFailureEventList-ngranFailureIndication of the existing operationEvents parameter.

[0132] To facilitate understanding of the MBS session processing method described above in this application, an example of a practical application scenario is provided. In this practical application scenario, AMF is used as the first network node, and MB-SMF is used as the second network node. The specific processing procedure in this practical application scenario is as follows:

[0133] 1. Add two pairs of messages between AMF (i.e., the first network node) and SMF (i.e., the second network node): MBSListRetrieval message (i.e., the first session request message) and MBSProfileRetrieval message (i.e., the second session request message).

[0134] a) Add ServiceOperations to section 5.3.2.12 of the TS29.532 specification for MBSListRetrieval.

[0135] Prerequisite: The MB-SMF has notified the AMF to create, modify, and release multiple MBS sessions through business processes such as MBS session creation, modification, and deletion. At this time, multiple MBS session contexts are stored on both the AMF and MB-SMF.

[0136] AMF sends an MBSListRetrieval message carrying the AMF's NFID (i.e., node identification information) to MB-SMF. MB-SMF then returns a list of all MBS session contexts (i.e., MBS session lists) corresponding to the AMF stored in its own SMF, such as the MbsSessionId list, based on the NFID carried by the AMF.

[0137] AMF can be configured to schedule the MBSListRetrieval messages to be sent periodically.

[0138] When AMF determines that the MBS session list context stored locally is inconsistent with that returned by MB-SMF, the following principles apply:

[0139] For an MBS session that exists on the AMF but not on the MB-SMF, the AMF can release the session locally.

[0140] For an MBS session that does not exist on the AMF but exists on the MB-SMF, the AMF can send a release message for the corresponding MBS session to the MB-SMF.

[0141] Currently, in MBS business scenarios, there is no process where AMF actively initiates the MBS session release notification to MB-SMF. It is necessary to add the releasedIndByAMF parameter to the Namf_MBSBroadcast_ContextStatusNotify Request message (an existing message) that AMF actively sends to MB-SMF. The value of releasedIndByAMF can indicate to MB-SMF that the release of this MBS session was initiated by AMF.

[0142] At the same time, when the AMF enters the maintenance state or the AMF actively releases the MBS session during maintenance, the AMF also needs to actively notify the MB-SMF to release the MBS session. The value of releasedIndByAMF can indicate whether the SMF needs to rebuild the MBS session in other AMFs in the pool.

[0143] In section 6.5.6 of the TS29.518 specification, releasedIndByAMF is added, as shown in Table 6.5.6.2.4-1, Table 1, and Table 2 below.

[0144] Table 6.5.6.2.4-1:Definition of type ContextStatusNotification

[0145]

[0146] Table 1Enumeration: ReleasedIndByAMF

[0147]

[0148] Table 2Definition of type MBSSessionList

[0149]

[0150] By following the steps above, the AMF can either release the inconsistent MBS session list locally or send an MBS session message to the MB-SMF, thus ensuring that the MBS session lists on the AMF and MB-SMF are consistent.

[0151] b) In section 5.3.3.13 of the TS29.532 specification, add ServiceOperations for MBSProfileRetrieval.

[0152] After AMF obtains MBSListRetrieval from MB-SMF, it immediately retrieves the Profile of each MBS session through MBSProfileRetrieval (carrying the MBS session ID, i.e., mbsSessionId, obtained in step a above). (The Profile contains the specific MBS service area information corresponding to the MBS session ID). MB-SMF returns the MBS session Profile based on mbsSessionId (MBS session ID), as shown in Table 3.

[0153] Table 3Definition of type MBSSessionProfile

[0154]

[0155] When AMF determines that the locally stored MBS session profile and the one returned by MB-SMF are inconsistent, the following principles apply:

[0156] If the AMF has more TAs corresponding to MBS sessions stored locally than the SMF, the AMF will release the MBS sessions for the gNodeb under these TAs.

[0157] If the number of TAs stored on the AMF is less than that on the SMF, the AMF will rebuild the MBS session on the gNodeb under this portion of the TAs.

[0158] Through the above steps, the AMF releases or rebuilds MBS sessions for inconsistent TAs in all MBS session lists, ensuring that the MBS service area information (TA) contained in the corresponding MBS session on the AMF and MB-SMF is consistent.

[0159] The above-mentioned "adding two pairs of messages between AMF and SMF: MBSListRetrieval and MBSProfileRetrieval" is a consistency check initiated proactively by AMF. Through AMF's proactive consistency check, inconsistencies in MBS session resources on AMF and MB-SMF can be detected in advance, and actions taken after inconsistency is detected can ensure consistency.

[0160] Points 2 and 3 below are examples of actions taken by the AMF to notify the MB-SMF when the MBS session resources determined by the AMF are inconsistent with those of the MB-SMF.

[0161] 2. In the Namf_MBSBroadcast_ContextCreate Response message, AMF adds an "unknownTAIList" field to notify MB-SMF that AMF does not support this TA.

[0162] In section 6.5.6.2.3 of the TS29.518 specification, ContextCreateRspData is defined as follows, with the addition of the unknownTAIList parameter, as shown in Table 6.5.6.2.3-1 below.

[0163] Table 6.5.6.2.3-1:Definition of type ContextCreateRspData

[0164]

[0165] After receiving the unknownTAIList, MB-SMF will no longer repeatedly send MBS session creation information to avoid increasing the system load on AMF and MB-SMF.

[0166] 3. In the Namf_MBSBroadcast_ContextStatusNotify Request message, AMF adds the enumeration value "NG_RAN_Exceed capacity" to indicate the gNodeb ID corresponding to the gNodeb that the MB-SMF exceeds its capacity.

[0167] In section 6.5.6.3.6 of the TS29.518 specification, NgranFailureIndication is defined as follows, with the addition of the enumeration value "NG_RAN_Excced capacity", as shown in Table 6.5.6.3.6-1 below.

[0168] Table 6.5.6.3.6-1:Enumeration NgranFailureIndication

[0169]

[0170] After receiving NgranFailureIndicatio, MB-SMF can send MBS session creation messages separately for these gNodeb, thus preventing MBS sessions under these gNodeb from remaining uncreated.

[0171] In this embodiment, a session association message is received from a second network node, which is either an AMF or an MB-SMF. The session association message is associated with at least one second MBS session, which is an MBS session of the second network node. Based on the session association message, at least one second MBS session is compared with at least one first MBS session to obtain a comparison result. At least one first MBS session is an MBS session of the first network node, which is the other of the AMF and MB-SMF. In response to the comparison result indicating that at least one second MBS session is inconsistent with at least one first MBS session, MBS session processing is performed to make the MBS session of the first network node consistent with the MBS session of the second network node. Thus, MBS sessions of the AMF and MB-SMF can be compared, and MBS session processing can be performed when the MBS sessions of the AMF and MB-SMF are inconsistent, thereby achieving MBS session consistency between the AMF and MB-SMF and reducing the waste of communication resources.

[0172] Please see Figure 4This is a flowchart illustrating another MBS session processing method provided in an embodiment of this application. The method is applied to a second network node, which is either an AMF or an MB-SMF. Figure 4 As shown, the method includes:

[0173] Step S401: Send a session association message to the first network node, where the first network node is the other one between AMF and MB-SMF. The session association message is associated with at least one second MBS session, where the at least one second MBS session is an MBS session of the second network node.

[0174] The session association message is used to instruct the first network node to compare at least one second MBS session with at least one first MBS session to obtain a comparison result, wherein at least one first MBS session is the MBS session of the first network node; and, in response to the comparison result indicating that at least one second MBS session is inconsistent with at least one first MBS session, MBS session processing is performed to make the MBS session of the first network node consistent with the MBS session of the second network node.

[0175] In some implementations, after sending the session association message to the first network node, the method further includes:

[0176] Receive a session processing message sent by a first network node. The session processing message is used to indicate a second target MBS session. The second target MBS session is an MBS session that is different from at least one first MBS session among at least one second MBS session.

[0177] In response to a session processing message, the second target MBS session is released or rebuilt.

[0178] In some implementations, the second target MBS session includes at least one of the following:

[0179] An MBS session having a different session identifier from at least one second MBS session;

[0180] MBS sessions that have different service cell information from at least one second MBS session.

[0181] In some implementations, before sending the session association message to the first network node, the following steps are also included:

[0182] Receive a session request message sent by the first network node;

[0183] Send a session association message to the first network node, including:

[0184] In response to the session request message, a session association message is sent to the first network node.

[0185] In some implementations, the session request message carries the node identification information of the first network node;

[0186] In response to the session request message, a session association message is sent to the first network node, including:

[0187] Based on node identification information, at least one second MBS session associated with the first network node is determined in the MBS session of the second network node.

[0188] Based on at least one second MBS session, an MBS session list is sent to the first network node. The MBS session list includes information about at least one second MBS session, and the session association message includes the MBS session list.

[0189] In some implementations, the first network node is AMF and the second network node is MB-SMF.

[0190] In some implementations, the method further includes:

[0191] Send a first context creation request message to the AMF. The first context creation request message carries the first service cell information of the second MBS session. The first service cell information includes indication information of at least one broadcast area.

[0192] Receive first indication information sent by AMF, the first indication information being used to indicate at least one target broadcast area that is not supported by AMF in the broadcast area.

[0193] In some implementations, receiving the first indication information sent by the AMF includes:

[0194] Receive the response message sent by the AMF in response to the context creation request message, the response message carrying first indication information.

[0195] In some implementations, the method further includes:

[0196] Send a second context creation request message to the AMF. The second context creation request message carries the second service cell information of the second MBS session. The second service cell information includes the indication information of the network side equipment under each broadcast area.

[0197] The system receives a second indication message sent by the AMF in response to the second context creation request message. The second indication message is sent when it is determined that the number of network-side devices indicated by the second service cell information is greater than the target capacity. The target capacity is the maximum number of network-side devices that the AMF can support in processing the second MBS session. The second indication message is used to indicate network-side devices that are not supported by the AMF.

[0198] In some implementations, receiving second indication information sent by the AMF in response to the second context creation request message includes:

[0199] Receive the context state notification request message sent by the AMF in response to the second context creation request message, wherein the second indication information is configured in the existing parameters of the context state notification request message.

[0200] It should be noted that the above Figure 4 The implementation methods of the MBS session processing method shown are the same as those described above. Figure 2 The implementation methods of the MBS session processing methods shown are similar in their implementation process and the beneficial effects they can achieve, and will not be described again here.

[0201] Please see Figure 5 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device includes the aforementioned bus routing node. Figure 5 As shown, the communication device 500 includes:

[0202] One or more processors 510;

[0203] The memory 520 stores one or more programs that, when executed by one or more processors 510, cause the one or more processors 510 to implement the MBS session processing method described in any of the above embodiments.

[0204] Memory 520, as a non-transitory network system, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory 520 may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 520 may optionally include remotely located memories 520 relative to processor 510, which can be connected to processor 510 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0205] The memory 520 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 520 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 520 and is called and executed by the processor 510 using the methods of the embodiments of this application.

[0206] The processor 510 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0207] In some embodiments, the communication device further includes:

[0208] Input / output interfaces are used to implement information input and output;

[0209] The communication interface is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0210] The bus transmits information between various components of the device (e.g., processor 510, memory 520, input / output interface, and communication interface);

[0211] The processor 510, memory 520, input / output interface, and communication interface can communicate with each other within the device via a bus.

[0212] One embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions for performing the MBS session processing method described in any of the embodiments above.

[0213] An embodiment of this application also provides a computer program product, including a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform a processing method that implements the MBS session described in any of the above embodiments.

[0214] The system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will know that as the system architecture evolves and new application scenarios emerge, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0215] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0216] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0217] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0218] The above description, with reference to the accompanying drawings, illustrates some embodiments of this application, but does not limit the scope of the invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this invention should be considered within the scope of this application.

Claims

1. A method for processing MBS sessions, characterized in that, Applied to a first network node, wherein the first network node is one of AMF and MB-SMF, the method includes: Receive a session association message sent by a second network node, the second network node being the other of the AMF and the MB-SMF, the session association message being associated with at least one second MBS session, the at least one second MBS session being an MBS session of the second network node; According to the session association message, the at least one second MBS session is compared with at least one first MBS session to obtain a comparison result, wherein the at least one first MBS session is the MBS session of the first network node; In response to the comparison result indicating that the at least one second MBS session is inconsistent with the at least one first MBS session, MBS session processing is performed to make the MBS session of the first network node consistent with the MBS session of the second network node.

2. The method according to claim 1, characterized in that, The step of performing MBS session processing to make the MBS session of the first network node consistent with the MBS session of the second network node includes at least one of the following: Release or rebuild the first target MBS session, wherein the first target MBS session is: among the at least one first MBS session, there is an MBS session that is different from the at least one second MBS session; A session processing message is sent to the second network node, the session processing message being used to instruct the second network node to release or rebuild the second target MBS session, the second target MBS session being: among the at least one second MBS session, there is an MBS session that is different from the at least one first MBS session.

3. The method according to claim 1, characterized in that, The comparison of the at least one second MBS session with at least one first MBS session to obtain the comparison result includes at least one of the following: The session identifier of the at least one second MBS session is compared with the session identifier of the at least one first MBS session to obtain a first comparison result, the comparison result including the first comparison result; The service cell information of the at least one second MBS session is compared with the service cell information of the at least one first MBS session to obtain a second comparison result, the comparison result including the second comparison result.

4. The method according to claim 1, characterized in that, Before receiving the session association message sent by the second network node, the method further includes: Send a session request message to the second network node; The receipt of the session association message sent by the second network node includes: Receive the session association message returned by the second network node in response to the session request message.

5. The method according to claim 4, characterized in that, Sending a session request message to the second network node includes: Send a session request message carrying the node identification information of the first network node to the second network node; The receipt of the session association message from the second network node in response to the session request message includes: The system receives an MBS session list from the second network node in response to the session request message. The MBS session list includes information about at least one second MBS session, which is an MBS session associated with the first network node determined by the second network node based on the node identification information in the MBS sessions of the second network node. The session request message includes the MBS session list.

6. The method according to claim 1, characterized in that, The first network node is the AMF, and the second network node is the MB-SMF.

7. The method according to claim 6, characterized in that, The method further includes: Receive a first context creation request message sent by the MB-SMF, the first context creation request message carrying first service cell information of the second MBS session, the first service cell information including indication information of at least one broadcast area; If a target broadcast area that is not supported by the AMF exists in at least one broadcast area, a first indication message is sent to the MB-SMF, the first indication message being used to indicate the target broadcast area.

8. The method according to claim 7, characterized in that, Sending the first indication information to the MB-SMF includes: In response to the context creation request message, a reply message carrying the first indication information is sent to the MB-SMF.

9. The method according to claim 6, characterized in that, The method further includes: Receive the second context creation request message sent by the MB-SMF. The second context creation request message carries the second service cell information of the second MBS session. The second service cell information includes indication information of network-side devices under each broadcast area. If the number of network-side devices indicated by the second service cell information is greater than the target capacity, then at least one network-side device is determined, wherein the target capacity is the maximum number of network-side devices that the AMF can support in processing the second MBS session, and the at least one network-side device is a network-side device that is not supported by the AMF. Send a second indication message to the MB-SMF, the second indication message being used to instruct the at least one network-side device.

10. The method according to claim 9, characterized in that, Sending the second indication information to the MB-SMF includes: In response to the second context creation request message, a context state notification request message is sent to the MB-SMF, wherein the second indication information is configured in the existing parameters of the context state notification request message.

11. A method for processing MBS sessions, characterized in that, Applied to a second network node, which is one of AMF and MB-SMF, the method includes: A session association message is sent to a first network node, which is the other of the AMF and the MB-SMF. The session association message is associated with at least one second MBS session, which is an MBS session of the second network node. The session association message is used to instruct the first network node to compare the at least one second MBS session with at least one first MBS session to obtain a comparison result, wherein the at least one first MBS session is the MBS session of the first network node; and, in response to the comparison result indicating that the at least one second MBS session is inconsistent with the at least one first MBS session, to perform MBS session processing to make the MBS session of the first network node consistent with the MBS session of the second network node.

12. The method according to claim 11, characterized in that, After sending the session association message to the first network node, the method further includes: Receive a session processing message sent by the first network node, the session processing message being used to indicate a second target MBS session, the second target MBS session being an MBS session that is different from the at least one first MBS session among the at least one second MBS sessions; In response to the session processing message, the second target MBS session is released or rebuilt.

13. The method according to claim 12, characterized in that, The second target MBS session includes at least one of the following: An MBS session having a different session identifier from the at least one second MBS session; MBS sessions that have different service cell information from the at least one second MBS session.

14. The method according to claim 11, characterized in that, Before sending the session association message to the first network node, the method further includes: Receive the session request message sent by the first network node; Sending the session association message to the first network node includes: In response to the session request message, the session association message is sent to the first network node.

15. The method according to claim 14, characterized in that, The session request message carries the node identification information of the first network node; The step of sending the session association message to the first network node in response to the session request message includes: Based on the node identification information, at least one second MBS session associated with the first network node is determined in the MBS session of the second network node; Based on the at least one second MBS session, an MBS session list is sent to the first network node, the MBS session list including information of the at least one second MBS session, and the session association message including the MBS session list.

16. The method according to claim 11, characterized in that, The first network node is the AMF, and the second network node is the MB-SMF.

17. The method according to claim 16, characterized in that, The method further includes: Send a first context creation request message to the AMF. The first context creation request message carries the first service cell information of the second MBS session. The first service cell information includes indication information of at least one broadcast area. Receive first indication information sent by the AMF, the first indication information being used to indicate a target broadcast area that the AMF does not support in the at least one broadcast area.

18. The method according to claim 17, characterized in that, The receipt of the first indication information sent by the AMF includes: Receive the response message sent by the AMF in response to the context creation request message, the response message carrying the first indication information.

19. The method according to claim 16, characterized in that, The method further includes: Send a second context creation request message to the AMF. The second context creation request message carries the second service cell information of the second MBS session. The second service cell information includes indication information of network-side devices under each broadcast area. The system receives a second indication message sent by the AMF in response to the second context creation request message. The second indication message is sent when it is determined that the number of network-side devices indicated by the second service cell information is greater than the target capacity. The target capacity is the maximum number of network-side devices that the AMF can support in processing the second MBS session. The second indication message is used to indicate network-side devices that are not supported by the AMF.

20. The method according to claim 19, characterized in that, The receipt of the second indication information sent by the AMF in response to the second context creation request message includes: The AMF receives a context state notification request message in response to the second context creation request message, wherein the second indication information is configured in the existing parameters of the context state notification request message.

21. An electronic device, comprising: One or more processors; A memory that stores one or more programs, which, when executed by one or more processors, cause the one or more processors to perform the following: The method for processing an MBS session according to any one of claims 1-20.

22. A computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to perform the following: The method for processing an MBS session according to any one of claims 1-20.

23. A computer program product comprising a computer program, which, when executed by a processor, implements, as follows: The method for processing an MBS session according to any one of claims 1-20.

Images