Message forwarding processing method, storage medium, electronic device and computer program product

Abstract

The embodiment of the invention provides a message forwarding processing method, a storage medium, an electronic device and a computer program product. The method comprises the following steps: receiving a strategy of an MBS session in an MBS session creation process sent by an AF; after the strategy of the MBS session is installed, the strategy installation result of the strategy of the MBS session is generated, the strategy installation result is reported to the AF through an interaction message with the AF, and the multicast / broadcast message is forwarded according to the strategy of the MBS session based on the strategy installation result. According to the method, the problem that the service message may not walk to the predicted MBS session policy, resulting in wrong policy QoS control, even service packet loss and the like is solved, the policy installation result of the MBS session is reported in time, the policy resources on the AF, the MB-SMF and the MB-UPF are ensured to be consistent, the validity of the subsequent policy operation of the AF on the MBS session is ensured, and the service packet loss and the like are avoided.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a message forwarding processing method, a storage medium, an electronic device, and a computer program product. Background Technology

[0002] When providing multicast / broadcast services, an MBS session (Multicast Broadcast Session) relies on the installed MBS session policies to control the forwarding of multicast / broadcast messages.

[0003] In an MBS session, the Application Function (AF) issues the MBS session policy. However, the Multicast / Broadcast-Session Management Function (MB-SMF) or the Multicast / Broadcast-User Plane Function (MB-UPF) fails to process this policy. In this case, neither the MB-SMF nor the MB-UPF has the policy resource, while the AF does. This can lead to situations where, during multicast / broadcast services, service packets may not reach the expected MBS session policy, resulting in incorrect QoS (Quality of Service) control or even packet loss.

[0004] No solution has yet been proposed for the problem that, during multicast / broadcast services, service packets may not reach the expected MBS session policy, leading to incorrect policy QoS control or even service packet loss. Summary of the Invention

[0005] This application provides a message forwarding processing method, storage medium, electronic device, and computer program product to at least solve the problem in the related art where, during multicast / broadcast services, service messages may not reach the expected MBS session policy, resulting in incorrect policy QoS control or even service packet loss.

[0006] According to one embodiment of this application, a message forwarding processing method is provided, applied to a multicast / broadcast session management function (MB-SMF), the method comprising:

[0007] The strategy of the MBS session during the MBS session creation process is received by the application function AF;

[0008] After installing the policy of the MBS session, the policy installation result of the MBS session is generated, and the policy installation result is reported to the AF through the interaction message between the AF and the AF.

[0009] Based on the installation results of the aforementioned strategy, multicast / broadcast messages are forwarded in accordance with the strategy of the MBS session.

[0010] According to another embodiment of this application, a message forwarding processing method is provided, applied to application function AF, the method comprising:

[0011] Send the MBS session policy mentioned in the MBS session creation process to the multicast / broadcast session management function MB-SMF;

[0012] After receiving the policy of the MBS session from the MB-SMF, generate and report the policy installation result through the interaction message between the MB-SMF and the MB-SMF;

[0013] Based on the installation results of the aforementioned strategy, multicast / broadcast messages are forwarded in accordance with the strategy of the MBS session.

[0014] According to another embodiment of this application, a message forwarding processing apparatus is provided, applied to a multicast / broadcast session management function (MB-SMF), the apparatus comprising:

[0015] The first receiving module is used to receive the MBS session strategy sent by the application function AF during the MBS session creation process;

[0016] The reporting module is used to generate the policy installation result of the MBS session after the policy of the MBS session is installed, and to report the policy installation result to the AF through the interaction message between the AF and the AF.

[0017] The first message forwarding module is used to forward multicast / broadcast messages based on the policy installation result and in accordance with the policy of the MBS session.

[0018] According to another embodiment of this application, a strategy resource processing apparatus is provided, applied to application function AF, the apparatus comprising:

[0019] The sending module is used to send the MBS session strategy during the MBS session creation process to the multicast / broadcast session management function MB-SMF;

[0020] The second receiving module is used to receive the policy installation result generated by the MB-SMF after the policy of the MBS session is installed and reported through the interaction message between the MB-SMF and the MB-SMF.

[0021] The second message forwarding module is used to forward multicast / broadcast messages based on the policy installation result and in accordance with the policy of the MBS session.

[0022] According to yet another embodiment of this application, a computer program product is also provided, including computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0023] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.

[0024] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0025] In this embodiment, the application function (AF) receives the policy of the MBS session during the MBS session creation process; after installing the policy of the MBS session, it generates the policy installation result of the MBS session policy and reports the policy installation result to the AF through interactive messages. Multicast / broadcast packets are forwarded using the policy of the MBS session. This solves the problem in related technologies where, during multicast / broadcast services, service packets may not reach the expected MBS session policy, leading to incorrect policy QoS control or even service packet loss. Timely reporting of the MBS session policy installation result ensures consistency between the AF and the policies on MB-SMF and MB-UPF, guaranteeing the effectiveness of subsequent AF policy operations and avoiding service packet loss. Attached Figure Description

[0026] Figure 1 This is a hardware structure block diagram of a computer device for a message forwarding processing method according to an embodiment of this application;

[0027] Figure 2 This is a flowchart of the message forwarding processing method according to the embodiments of this application. Figure 1 ;

[0028] Figure 3 This is the process of installing according to the strategy of the embodiments of this application. Figure 1 ;

[0029] Figure 4 This is the process of installing according to the strategy of the embodiments of this application. Figure 2 ;

[0030] Figure 5This is the process of installing according to the strategy of the embodiments of this application. Figure 3 ;

[0031] Figure 6 This is a flowchart of the message forwarding processing method according to the embodiments of this application. Figure 2 ;

[0032] Figure 7 This is the process of installing according to the strategy of the embodiments of this application. Figure 4 ;

[0033] Figure 8 This is the process of installing according to the strategy of the embodiments of this application. Figure 5 ;

[0034] Figure 9 This is the process of installing according to the strategy of the embodiments of this application. Figure 6 ;

[0035] Figure 10 This is the process of installing according to the strategy of the embodiments of this application. Figure 7 ;

[0036] Figure 11 This is a block diagram of a message forwarding processing apparatus according to embodiments of this application. Figure 1 ;

[0037] Figure 12 This is a block diagram of a message forwarding processing apparatus according to embodiments of this application. Figure 2 . Detailed Implementation

[0038] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0039] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0040] The methods and embodiments provided in this application can be executed in a computer device or similar computing device. Taking running on a computer device as an example, Figure 1 This is a hardware structure block diagram of a computer device for the message forwarding processing method according to an embodiment of this application, such as... Figure 1 As shown, a computer device may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor (MCU) or programmable logic device, etc.) and a memory 104 for storing data are also shown. The computer device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1The structure shown is for illustrative purposes only and does not limit the structure of the computer device described above. For example, the computer device may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0041] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the message forwarding processing method in this embodiment. The processor 102 executes various functional applications and board matching by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to computer devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0042] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer equipment. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0043] This embodiment provides a message forwarding processing method running on the aforementioned computer device. Figure 2 This is a flowchart of the message forwarding processing method according to the embodiments of this application. Figure 1 ,like Figure 2 As shown, when applied to MB-SMF, the process includes the following steps:

[0044] Step S202: Receive the MBS session strategy sent by AF during the MBS session creation process.

[0045] Step S204: After installing the policy of the MBS session, generate the policy installation result of the MBS session and report the policy installation result to the AF through the interaction message between the AF and the AF.

[0046] Step S206: Based on the policy installation results, forward multicast / broadcast messages in accordance with the MBS session policy.

[0047] In step S204 above, generating the policy installation result of the MBS session policy may specifically include: obtaining the installation status or installation condition of the MBS session policy, and generating the policy installation result based on the installation status or installation condition.

[0048] Through steps S202 to S206, the policy installation results are reported to the AF via interactive messages. Based on the policy installation results, multicast / broadcast packets are forwarded according to the policy of the MBS session. By reporting and using the policy installation results, the problem in related technologies where service packets may not reach the expected policy of the MBS session during multicast / broadcast services, resulting in incorrect policy QoS control or even service packet loss, can be solved. Timely reporting of the policy installation results of the MBS session ensures that the policies on the AF are consistent with those on the MB-SMF and MB-UPF, guaranteeing the effectiveness of subsequent policy operations by the AF and thus avoiding service packet loss.

[0049] In one embodiment, the AF sends the MBS session policy to the MB-SMF. After receiving the policy, the MB-SMF begins installing the MBS session policy. Once the policy is successfully installed on the MB-SMF, the MB-SMF sends the MBS session policy's Packet Detection Rule (PDR) to the MB-UPF. The MB-UPF installs the MBS session policy based on the PDR. After installing the MBS session policy, the MB-UPF returns the installation result to the MB-SMF. The MB-SMF receives the installation result from the MB-UPF, specifically through the PFCP-Session-Establish Response message on the N4mb port. The installation result includes whether the installation was successful or failed. Then, the policy installation result can be generated based on the MB-UPF installation result. Specifically, if the MB-UPF installation result is that the policy installation is successful and the MB-SMF installation result is successful, the generated policy will be considered as having successfully installed the policy. If the MB-UPF installation result is that the policy installation fails or the MB-SMF installation result fails, the generated policy will be considered as having failed to install the policy. Then, the policy installation result is reported to the AF via interactive messages. Further, if the policy installation is successful in both MB-SMF and MB-UPF (i.e., both MB-SMF and MB-UPF successfully installed the policy, resulting in a successful policy installation result), an installation success message is reported to the AF via added protocol fields or newly added fields in the interactive messages. For example, an installation success message can be reported via added protocol fields or newly added fields in the Nmb13 port messages. If the policy installation fails in MB-SMF or MB-UPF (i.e., either MB-SMF or MB-UPF failed to install the policy, resulting in a failed policy installation result), an installation failure message is reported to the AF via added protocol fields or newly added fields in the interactive messages. Specifically, an installation failure message can be reported via newly added fields in the Nmb13 port messages. Alternatively, no installation success message is reported to the AF; if the AF does not receive an installation success message, it defaults to installation failure. The protocol fields include: policy installation result and policy identifier; or the newly added fields include: policy installation result and policy identifier.

[0050] For example, when an MBS session comes online, the AF issues the policy for the MBS session, specifically through the mbsServInfo field of the Nmb13 port. Once the MB-SMF and MB-UPF successfully install the policy, the MB-SMF informs the AF that the policy has been successfully installed via an interactive message (specifically, the Nmbsmf-MBSSession-Create Response message). Figure 3This is the process for successfully installing the MBS session policy according to the embodiments of this application. Figure 1 ,like Figure 3 As shown, it includes:

[0051] S301, AF sends an Nmbsmf-MBSSession-Create Request message (carrying the mbsServInfo field) to MB-SMF. The mbsServInfo field is used to indicate the policy of the MBS session.

[0052] S302, after successfully installing the policy, MB-SMF sends a PFCP-Session-Establish Request message to MB-UPF, carrying the PDR of the MBS session policy.

[0053] S303, MB-UPF policy installation successful. MB-UPF responds with PFCP-Session-Establish Response message, carrying the Created-PDR field, indicating that the policy for the corresponding PDR MBS session was successfully installed.

[0054] S304, MB-SMF sends an Nmbsmf-MBSSession-Create Response message back to AF, carrying the mbsMedCompNum and SUCC_RES_ALLO fields, indicating that the policy was installed successfully.

[0055] In another embodiment, if the policy installation result is all failures and it is the first installation, a request message to release the MBS session is received from the AF, and a response message to release the MBS session is sent to the AF. After receiving the response message, the AF releases the MBS session.

[0056] For example, if the AF does not report that the policy installation of the MBS session is successful in the interaction message, it indicates that the policy installation of all MBS sessions has failed. The AF initiates an MBS session release request, and then the AF reconnects to the MBS session through the Nmbsmf-MBSSession-CreateRequest message.

[0057] Figure 4 This is the process of installing according to the strategy of the embodiments of this application. Figure 2 ,like Figure 4 As shown, it includes:

[0058] S401, AF sends an Nmbsmf-MBSSession-Create Request message (carrying the mbsServInfo field) to MB-SMF.

[0059] S402, MB-SMF sends an Nmbsmf-MBSSession-Create Response message to AF without carrying the SUCC-RES-ALLO and mbsMedCompNum fields, indicating that policy installation for all MBS sessions has failed.

[0060] S403, AF sends an Nmbsmf-MBSSession-Delete Request message to MB-SMF to release the MBS session.

[0061] In S404, the AF receives the Nmbsmf-MBSSession-Delete Response message. The AF then continues with the steps in S401 to trigger the re-establishment of the MBS session.

[0062] In another embodiment, if the policy installation fails partially, the AF resends the policy to be reinstalled (a partial policy of the MBS session) to the MB-SMF. The MB-SMF receives the policy to be reinstalled from the AF, reinstalls the policy, and then reports the policy reinstallation result to the AF via the aforementioned interactive message. Specifically, the process of reinstalling the policy is similar to the policy installation process of the MBS session described above, and will not be repeated here.

[0063] For example, when the AF receives a message in the interaction message that the policy part of the MBS session has been successfully installed, the AF will reinstall the policy of the previously failed MBS session multiple times in the subsequent Namf-MBSBroadcast-ContextUpdate Request message until the policies of all MBS sessions are successfully installed or the number of retry installations is reached. Figure 5 This is the process of installing according to the strategy of the embodiments of this application. Figure 3 ,like Figure 5 As shown, it includes:

[0064] S501, AF sends an Nmbsmf-MBSSession-Create Request message (carrying the mbsServInfo field) to MB-SMF.

[0065] In S502, MB-SMF sends an Nmbsmf-MBSSession-Create Response message to AF, carrying the SUCC-RES-ALL0 and mbsMedCompNum fields, indicating that the policy installation for some MBS sessions was successful, while the policy installation for the MBS sessions that were not reported indicates that the installation failed.

[0066] S503, AF sends a Namf-MBSBroadcast-ContextUpdate Request message to MB-SMF to reinstall the policies that failed in the previous policy installation results reported to AF.

[0067] In S504, MB-SMF sends a Namf-MBSBroadcast-ContextUpdate Response message to AF, carrying the SUCC-RES-ALLO and mbsMedCompNum fields, indicating the installation results of all re-attempted installation strategies.

[0068] The S503 and S504 operations are repeated multiple times until the policies for all MBS sessions are successfully installed or the retry count is reached (this retry count is configured on the AF), at which point the AF will stop updating the sessions.

[0069] This application also provides a message forwarding processing method. Figure 6 This is a flowchart of the message forwarding processing method according to the embodiments of this application. Figure 2 ,like Figure 6 As shown, when applied to AF, the process includes the following steps:

[0070] Step S602: Send the MBS session policy during the MBS session creation process to MB-SMF.

[0071] Step S604: Receive the policy installation result generated by MB-SMF and reported through interactive messages with MB-SMF after installing the policy of the MBS session.

[0072] Step S606: Based on the policy installation results, forward multicast / broadcast messages according to the policy of the MBS session.

[0073] By using the steps S602 to S606 above, the problem in related technologies that may occur during multicast / broadcast services, where service packets may not reach the expected policy of the MBS session, resulting in incorrect policy QoS control or even service packet loss, can be solved. The policy installation results of the MBS session can be reported in a timely manner to ensure that the policies on the AF are consistent with those on the MB-SMF and MB-UPF, and to ensure the effectiveness of subsequent policy operations by the AF, thereby avoiding service packet loss and other phenomena.

[0074] In one embodiment, if the MB-SMF installation policy is successful and the MB-UPF installation result is "installation policy successful" (at this time, the policy installation result is "installation successful"), the installation success message is received through the interaction message. That is, the MB-SMF reports through the interaction message, specifically through the protocol field added to the interaction message or the newly added field. Specifically, the installation success message reported by the MB-SMF can be received through the fields in the message of the Nmb13 port. The protocol field includes: policy installation result and policy identifier; or, the newly added field includes: information policy installation result and policy identifier.

[0075] Scenario 1: MB-SMF installation strategy fails; Scenario 2: MB-SMF installation strategy succeeds, but MB-UPF installation result is installation strategy failure. In both Scenario 1 and Scenario 2, the strategy installation result is installation failure. The installation success message is received through the interaction message, that is, MB-SMF reports through the interaction message. Specifically, it can be reported through the protocol fields added to the interaction message or newly added fields. Specifically, the installation failure message reported by MB-SMF can be received through the newly added fields in the Nmb13 port message. Alternatively, if no installation success message is received from MB-SMF, it is considered that the strategy installation result is installation failure, that is, MB-SMF or MB-UPF installation strategy fails.

[0076] For example, in the first scenario above, when an MBS session comes online, the AF sends the MBS session policy through the mbsServInfo field of the Nmb13 port. The MB-SMF fails to process this field, and the MB-SMF informs the AF of the policy installation failure through the Nmbsmf-MBSSession-CreateResponse message. Figure 7 This is the process of installing according to the strategy of the embodiments of this application. Figure 4 ,like Figure 7 As shown, it includes:

[0077] S701, AF sends an Nmbsmf-MBSSession-Create Request message (carrying the mbsServInfo field) to MB-SMF. MB-SMF fails to process this field, causing the MB-SMF installation strategy to fail.

[0078] S702, MB-SMF sends an Nmbsmf-MBSSession-Create Response message back to AF, which carries the mbsMedCompNum and ReportInd fields to indicate which MBS session's policy installation failed.

[0079] For example, in scenario two above, when an MBS session comes online, the MB-SMF sends a PDR (Policy Directive) for the MBS session to the UPF in the session creation request on the N4 port. If the UPF fails to process the PDR, it reports the PDR installation failure to the MB-SMF through the Failed Rule ID field in the protocol. The MB-SMF then informs the AF (Active AF) through the Nmbsmf-MBSSession-Create Response message that the policy installation for the corresponding MBS session has failed. Figure 8 This is the process of installing according to the strategy of the embodiments of this application. Figure 5 ,like Figure 8 As shown, it includes:

[0080] S801, AF sends an Nmbsmf-MBSSession-Create Request message (carrying the mbsServInfo field) to MB-SMF, and MB-SMF successfully processes the policy rule.

[0081] S802, MB-SMF sends a PFCP-Session-Establish Request message to MB-UPF, carrying the PDR of the MBS session policy.

[0082] S803, MB-UPF failed to process the policy, the rule was not installed successfully, MB-UPF responded with PFCP-Session-Establish Response message, carrying the Failed Rule ID field, indicating that the policy installation for the corresponding PDR MBS session failed.

[0083] S804, MB-SMF sends an Nmbsmf-MBSSession-Create Response message back to AF, which carries the mbsMedCompNum and ReportInd fields, indicating that the policy installation for the corresponding MBS session failed.

[0084] In another embodiment, if the policy installation result is a complete failure (i.e., the policy installation for all MBS sessions fails) and it is the first installation, a request message to release the MBS session is sent to the MB-SMF. That is, the MB-SMF is requested to release the MBS session through the request message. After receiving the request message, the MB-SMF releases the MBS session and sends a response message after releasing the MBS session. After receiving the response message to release the MBS session sent by the MB-SMF, the AF knows that the MBS session has been released.

[0085] For example, when the AF receives a message in the Nmbsmf-MBSSession-Create Response message indicating that all policies for the MBS session have failed to install, the AF initiates an MBS session release request. Afterward, the AF reconnects to the MBS session via the Nmbsmf-MBSSession-CreateRequest message. Figure 9 This is the process of installing according to the strategy of the embodiments of this application. Figure 6 ,like Figure 9 As shown, it includes:

[0086] S901, AF sends an Nmbsmf-MBSSession-Create Request message (carrying the mbsServInfo field) to MB-SMF.

[0087] S902, MB-SMF sends an Nmbsmf-MBSSession-Create Response message to AF, carrying all mbsMedCompNum and ReportInd fields, indicating that policy installation failed for all MBS sessions.

[0088] S903, AF sends an Nmbsmf-MBSSession-Delete Request message to MB-SMF to release the MBS session.

[0089] S904, AF receives the Nmbsmf-MBSSession-Delete Response message. Then AF continues with step 1a to trigger the re-establishment of the MBS session.

[0090] In another embodiment, if the policy installation result is a partial failure, the policy to be reinstalled (a partial policy of the MBS session) is sent to the MB-SMF, and the policy reinstallation result of the policy to be reinstalled is reported by the MB-SMF through interactive messages.

[0091] For example, when the AF receives a message in the Nmbsmf-MBSSession-Create Response message indicating that the installation of the policy part of the MBS session has failed, the AF will reinstall the policy of the previously failed MBS session multiple times in subsequent Namf-MBSBroadcast-ContextUpdate Request messages until the policies of all MBS sessions are successfully installed or the number of retry installations is reached. Figure 10 This is the process of installing according to the strategy of the embodiments of this application. Figure 7 ,like Figure 10 As shown, it includes:

[0092] S1001, AF sends an Nmbsmf-MBSSession-Create Request message (carrying the mbsServInfo field) to MB-SMF.

[0093] S1002, MB-SMF sends an Nmbsmf-MBSSession-Create Response message to AF, carrying the mbsMedCompNum and ReportInd fields, indicating that the policy installation for some MBS sessions was successful and the policy installation for others failed.

[0094] S1003, AF sends a Namf-MBSBroadcast-ContextUpdate Request message to MB-SMF to reinstall the policies that failed in the previous policy installation results reported to AF.

[0095] S1004, MB-SMF sends a Namf-MBSBroadcast-ContextUpdate Response message to AF, carrying the mbsMedCompNum and ReportInd fields, indicating the installation results of all strategies that were re-attempted for installation.

[0096] The operations in S1003 and S1004 are repeated multiple times until the policies for all MBS sessions are successfully installed or the number of retries is reached (this number of retries is configured on the AF), at which point the AF will stop updating the sessions.

[0097] In another embodiment, the AF can also record the number of times the policy to be reinstalled is sent. If the number of sending attempts reaches a preset number and the policy reinstallation fails, the sending of the policy to be reinstalled is stopped, meaning that the policy to be reinstalled does not need to be installed further. Specifically, the process of reinstalling the policy is similar to the policy installation process of the MBS session described above, and will not be repeated here.

[0098] In this embodiment, the protocol fields added to the interaction messages between MB-SMF and AF are used to indicate whether the policy installation of the MBS session was successful. The content can be SUCC-RES-ALLO and mbsMedCompNum, where SUCC-RES-ALLO indicates that the policy installation of the MBS session on MB-SMF was successful; mbsMedCompNum contains the policy identifier of the MBS session. An MBS session that does not report the SUCC-RES-ALLO field indicates that the policy installation failed. As shown in Table 1, the newly added fields set in the two messages of Nmb13 are used to indicate whether the initial policy installation was successful.

[0099] The AF can decide on subsequent operations based on whether the policy installation was successful. If the MB-SMF does not notify the AF of successful policy installation during the initial policy installation, it indicates that all policies have failed to install. In this case, the AF will proactively initiate MBS session release and then reconnect to the MBS session. If the MB-SMF notifies the AF of partial policy installation success during the initial policy installation, the AF will reinstall the policies of all failed MBS sessions via the Nmb13 interface message after the session is back online. In subsequent messages, the MB-SMF will continue to report the installation results of the reinstalled MBS session policies. If no policy is reported as successfully installed, meaning that all MBS session policies have failed to install during the reinstallation process, the AF will continue to retry the reinstallation step without initiating the session release process. The AF can be configured with a retransmission count to prevent ping-pong issues. The AF will stop the reinstallation step once all policies are successfully installed or the retry count is reached. Table 2 lists two newly added fields in the Nmb13 interface message design, used to indicate whether the reinstalled policies were successful.

[0100] Table 1

[0101]

[0102] Table 2

[0103]

[0104] When MB-SMF fails to process a policy for an MBS session, it will not report successful policy installation to AF via fields in the Nmb13 port message. When MB-UPF fails to process a policy for an MBS session, it will inform MB-SMF of the policy installation failure via the PFCP-Session-Establish Response message on the N4mb port. MB-SMF will not report successful policy installation to AF via the newly added fields in the Nmb13 port message. AF receives the policy installation result from the MB-SMF's report message. If no policy is successfully installed and reported on the first attempt, AF will notify MB-SMF to release the MBS session and then re-bring it online. If a policy is partially successfully installed and reported on the first attempt, AF will attempt to reinstall the failed policies multiple times in subsequent messages until all policies are successfully installed or the required number of retries is reached.

[0105] In another embodiment, the invention's functionality is achieved by adding new fields. A field is added to the messages exchanged between the MB-SMF and AF, indicating the policy installation result of the MBS session. The content can be ReportInd and mbsMedCompNum, where ReportInd contains either Resource-allocated-successfully or Resource-allocated-failure, indicating whether the policy installation of the MBS session on the MB-SMF was successful or failed; mbsMedCompNum contains the policy identifier of the MBS session. Table 3 lists the newly added fields designed for two messages in the Nmb13 port, used to report the policy installation result of the first MBS session.

[0106] The AF can decide on subsequent operations based on whether the policy installation is successful. When the MB-SMF informs the AF that all network element policies failed to install during the initial installation of policies for the MBS session, and no policies are successfully installed, the AF will proactively initiate MBS session release and then reconnect to the MBS session. When the MB-SMF informs the AF that some network element policies failed to install during the initial installation of policies for the MBS session, after the session is online, the AF will again inform the MB-SMF via the Nmb13 interface message to reinstall all failed policies. In subsequent messages, the MB-SMF will continue to report the reinstallation results. If all policy reinstallations fail, the AF will continue to retry the reinstallation process without initiating a session release procedure. The AF can be configured with a retransmission count to prevent ping-pong issues, and will stop the reinstallation process once all policies are successfully installed or the retry count is reached. Table 4 lists two newly added fields in the Nmb13 interface message design for reporting the reinstallation results of policies.

[0107] Table 3

[0108]

[0109] Table 4

[0110]

[0111] When MB-SMF fails to process a policy for an MBS session, it reports the policy installation failure to the AF via a newly added field in the Nmb13 port message. When MB-UPF fails to process a policy for an MBS session, it informs MB-SMF of the policy installation failure via the PFCP-Session-EstablishRespone message on the N4mb port. MB-SMF then reports the policy installation failure to the AF via the newly added field in the Nmb13 port message. The AF receives the policy installation result from the MB-SMF's report message. If the initial policy installation results in a complete failure, the AF will notify MB-SMF to release the session and re-bring it online. If the initial policy installation results in a partial failure, the AF will attempt to reinstall the MBS session's policies multiple times in subsequent messages until all policies are successfully installed or the required number of retries is reached.

[0112] This application also provides a message forwarding processing apparatus. Figure 11 This is a block diagram of a message forwarding processing apparatus according to embodiments of this application. Figure 1 ,like Figure 11 As shown, the device, applied to the multicast / broadcast session management function MB-SMF, includes:

[0113] The first receiving module 112 is used to receive the MBS session strategy sent by the application function AF during the MBS session creation process:

[0114] The reporting module 114 is used to generate the policy installation result of the MBS session after the policy of the MBS session is installed, and to report the policy installation result to the AF through the interaction message between the AF and the AF.

[0115] The first message forwarding module 116 is used to forward multicast / broadcast messages based on the policy installation result and in accordance with the policy of the MBS session.

[0116] This application also provides a strategy resource processing device. Figure 12 This is a block diagram of a message forwarding processing apparatus according to embodiments of this application. Figure 2 ,like Figure 12 As shown, the device is used for application function AF and includes:

[0117] The sending module 122 is used to send the MBS session strategy during the MBS session creation process to the multicast / broadcast session management function MB-SMF;

[0118] The second receiving module 124 is used to receive the policy installation result generated by the MB-SMF after the policy of the MBS session is installed and reported through the interaction message between the MB-SMF and the MB-SMF.

[0119] The second message forwarding module 126 is used to forward multicast / broadcast messages based on the policy installation result and in accordance with the policy of the MBS session.

[0120] This application also provides a computer program product, including computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0121] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0122] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0123] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0124] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0125] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0126] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0127] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A packet forwarding processing method, characterized by, The method is applied to a multicast / broadcast session management function (MB-SMF), and the method comprises the following steps: receiving a policy of a multicast / broadcast service (MBS) session sent by an application function (AF) in an MBS session creation process; generating a policy installation result of the MBS session after installing the policy of the MBS session, and reporting the policy installation result to the AF through an interactive message between the MB-SMF and the AF; based on the policy installation result, forwarding multicast / broadcast packets according to the policy of the MBS session.

2. The method of claim 1, wherein, Before the step of generating the policy installation result of the MBS session, the method further comprises the following steps: installing the policy of the MBS session; in the case that the MB-SMF policy installation is successful, sending a packet detection rule (PDR) of the policy of the MBS session to an MB-UPF; receiving an installation result sent by the MB-UPF after installing the policy of the MBS session based on the PDR.

3. The method of claim 2, wherein, reporting the policy installation result to the AF through an interactive message between the MB-SMF and the AF, comprising the following steps: in the case that the MB-SMF policy installation is successful and the installation result of the MB-UPF is that the policy installation is successful, reporting an installation success message to the AF through a protocol field added in the interactive message or a newly-added field; in the case that the MB-SMF policy installation fails or the installation result of the MB-UPF is that the policy installation fails, reporting an installation failure message to the AF through the protocol field added in the interactive message or the newly-added field, or not reporting the installation success message to the AF; wherein the protocol field comprises the policy installation result and a policy identifier; or the newly-added field comprises the policy installation result and the policy identifier.

4. The method of claim 1, wherein, The step of generating the policy installation result of the policy of the MBS session comprises the following steps: obtaining an installation state or an installation condition of the policy of the MBS session; generating the policy installation result according to the installation state or the installation condition.

5. The method of claim 1, wherein, The method further comprises the following steps: in the case that the policy installation result is all failed and is the first installation, receiving a request message for releasing the MBS session sent by the AF; sending a response message for releasing the MBS session to the AF.

6. The method of claim 1, wherein, The method further comprises the following steps: in the case that the policy installation result is partially failed, receiving a policy to be reinstalled sent by the AF; reporting a policy reinstallation result of the policy to be reinstalled to the AF through the interactive message.

7. A packet forwarding processing method characterized by comprising: The method is applied to an application function (AF), and the method comprises the following steps: sending a policy of a multicast / broadcast service (MBS) session to a multicast / broadcast session management function (MB-SMF) in an MBS session creation process; receiving a policy installation result generated and reported by the MB-SMF through an interactive message between the MB-SMF and the AF after installing the policy of the MBS session; based on the policy installation result, forwarding multicast / broadcast packets according to the policy of the MBS session.

8. The method of claim 7, wherein, The step of receiving the policy installation result generated and reported by the MB-SMF through the interactive message between the MB-SMF and the AF after installing the policy of the MBS session comprises the following steps: receive, from the MB-SMF, a successful installation message reported by the MB-SMF through a protocol field added in the interaction message or a new field in a case where the MB-SMF and the MB-UPF both successfully install the policy; receive, from the MB-SMF, a failed installation message reported by the MB-SMF through the protocol field added in the interaction message or the new field in a case where the MB-SMF or the MB-UPF fails to install the policy; wherein the protocol field comprises the policy installation result and a policy identifier, or the new field comprises an information policy installation result and a policy identifier.

9. The method of claim 7, wherein, The method further comprises: in a case where the policy installation result is all failed and it is a first installation, sending, to the MB-SMF, a request message for releasing an MBS session; receiving, from the MB-SMF, a response message for releasing the MBS session.

10. The method of claim 9, wherein, The method further comprises: in a case where the policy installation result is partially failed, sending, to the MB-SMF, a policy to be reinstalled; and receiving, from the MB-SMF, a policy reinstallation result of the policy to be reinstalled reported by the MB-SMF through the interaction message.

11. The method of claim 10, wherein, The method further comprises: recording a sending frequency of sending the policy to be reinstalled; in a case where the sending frequency reaches a preset frequency and the policy reinstallation result is installation failed, stopping sending the policy to be reinstalled.

12. A computer readable storage medium, characterized in that, The storage medium has stored therein a computer program, wherein the computer program is configured to execute the method recited in any one of claims 1 to 6, 7 to 11 when running.

13. An electronic device, comprising: The apparatus comprises a memory and a processor, the memory has stored therein a computer program, and the processor is configured to execute the computer program to execute the method recited in any one of claims 1 to 6, 7 to 11.

14. A computer program product, characterised in that, The apparatus comprises a computer program, which, when executed by a processor, implements the steps of the method recited in any one of claims 1 to 6, 7 to 11.

Images