CN110650475A

CN110650475A - Session binding processing method and network equipment

Info

Publication number: CN110650475A
Application number: CN201810670351.1A
Authority: CN
Inventors: 黄震宁; 李爱华; 蔡慧
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2018-06-26
Filing date: 2018-06-26
Publication date: 2020-01-03
Anticipated expiration: 2038-06-26
Also published as: CN110650475B

Abstract

The invention provides a session binding processing method and network equipment, wherein the method comprises the following steps: the first network equipment receives a binding update request of a session; the binding update request carries original binding information and new binding information related to the session; and responding to the binding update request, and sending a response result to the second network equipment. The embodiment of the invention supports the updating of the binding information of the session, prevents the session interruption or invalidation caused by the change of the binding information of the session binding, and ensures the continuity of the session.

Description

Session binding processing method and network equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a session binding processing method and a network device.

Background

In order to achieve the goal of differentiated Service capability, resource grooming capability, network traffic optimization capability, etc., a Policy and Charging Control (PCC) system architecture is introduced into the existing packet network to perform Quality of Service (QoS) Control on packet data services according to the 3rd Generation Partnership Project (3 GPP) standard specification.

In order to ensure independent service, a session binding operation is provided, and the policy control function entity binds a session through a network identifier of the terminal sent by the access point and a network identifier of the terminal sent by the user plane function entity, or through a user identifier of the terminal sent by the policy control function entity and a user identifier of the terminal sent by the user plane function entity. The movement or change of the terminal may change some property parameters, and the change of the property parameters may cause the binding information of the session binding to change, thereby causing the failure of the original binding information and the interruption or failure of the original session.

Disclosure of Invention

The invention provides a session binding processing method and network equipment, which solve the problem of session interruption or failure caused by change of binding information of session binding.

The embodiment of the invention provides a session binding processing method, which is applied to first network equipment and comprises the following steps:

receiving a binding update request of a session; the binding update request carries original binding information and new binding information related to the session;

and responding to the binding update request, and sending a response result to the second network equipment.

An embodiment of the present invention further provides a network device, where the network device is a first network device, and the first network device includes: a processor; a memory coupled to the processor, and a transceiver coupled to the processor; the processor is used for calling and executing programs and data stored in the memory;

the transceiver is configured to: receiving a binding update request of a session; the binding update request carries original binding information and new binding information related to the session;

the processor is configured to: and responding to the binding update request, and controlling the transceiver to send a response result to the second network equipment.

An embodiment of the present invention further provides a network device, where the network device is a first network device, and the network device includes:

the first receiving module is used for receiving a binding update request of a session; the binding update request carries original binding information and new binding information related to the session;

and the response module is used for responding to the binding update request and sending a response result to the second network equipment.

The embodiment of the invention also provides a session binding processing method, which is applied to second network equipment and comprises the following steps:

sending a binding update request of the session; the binding update request carries original binding information and new binding information related to the session;

and receiving a response result fed back by the first network equipment after responding to the binding update request.

An embodiment of the present invention further provides a network device, where the network device is a second network device, and the second network device includes: a processor; a memory coupled to the processor, and a transceiver coupled to the processor; the processor is used for calling and executing programs and data stored in the memory;

the transceiver is configured to: sending a binding update request of the session; the binding update request carries original binding information and new binding information related to the session; and

An embodiment of the present invention further provides a network device, where the network device is a second network device, and the network device includes:

the first sending module is used for sending a binding update request of the session; the binding update request carries original binding information and new binding information related to the session;

and the second receiving module is used for receiving a response result fed back by the first network equipment after responding to the binding update request.

Embodiments of the present invention also provide a computer readable storage medium having stored thereon a computer program which, when being executed by a processor, implements the steps of the session binding processing method according to any one of claims 1 to 8, or implements the steps of the session binding processing method according to any one of claims 18 to 23.

The technical scheme of the invention has the beneficial effects that: after receiving the binding update request of the session binding, the first network device updates the binding information of the session according to the original binding information and the new binding information related to the session, so that session interruption or failure caused by change of the binding information of the session binding is prevented, and the continuity of the session is ensured.

Drawings

Fig. 1 is a schematic flowchart illustrating a session binding processing method on a first network device side according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a PCC network architecture of an LTE system according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a PCC network architecture of a 5G system according to an embodiment of the present invention;

FIG. 4 is a flowchart illustrating a session binding processing method according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating a binding registration flow according to an embodiment of the present invention;

FIG. 6 is a diagram illustrating a binding query flow according to an embodiment of the invention;

FIG. 7 is a diagram illustrating a binding update flow according to an embodiment of the invention;

FIG. 8 is a diagram illustrating a binding deregistration process according to an embodiment of the present invention;

FIG. 9 is a first diagram illustrating a binding update flow according to an embodiment of the present invention;

FIG. 10 is a second diagram illustrating a binding update flow according to an embodiment of the invention;

fig. 11 is a schematic block diagram of a first network device according to an embodiment of the present invention;

fig. 12 is a flowchart illustrating a session binding processing method on the second network device side according to an embodiment of the present invention;

fig. 13 is a schematic block diagram of a first network device according to an embodiment of the present invention;

fig. 14 is a block diagram showing a configuration of a network device according to an embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help the full understanding of the embodiments of the present invention. Thus, it will be apparent to those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

In addition, the terms "system" and "network" are often used interchangeably herein.

In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.

As shown in fig. 1, an embodiment of the present invention provides a session binding processing method, which specifically includes the following steps:

step 11: receiving a binding update request of a session; the binding update request carries the original binding information and the new binding information related to the session.

The session is referred to as a service session, and session binding is required to ensure continuity and integrity of the session. The session binding process of the embodiment of the invention comprises the following steps: registering binding information, deregistering binding information (or called deleting binding information), inquiring binding information, updating binding information and the like.

As shown in fig. 2, a schematic diagram of a PCC architecture in a Long Term Evolution (LTE) system is shown, where the main network elements include but are not limited to: a Policy and Charging Rules Function (PCRF) entity, a Policy and Charging Enforcement Function (PCEF) entity, an Application Function (AF) entity, an Online Charging System/Offline Charging System (OCS/OFCS), a Subscription Profile Repository (SPR), and the like. Wherein the content of the first and second substances,

the PCRF entity has the functionality of policy control decisions and flow-based charging control, providing the PCEF entity with network control functions with respect to traffic data flow detection, gating, QoS-based and flow-based charging (except credit control).

The PCEF entity is responsible for detecting a service data stream, performing a policy, and performing a flow-based charging function, and is generally disposed on a Gateway GPRS Support Node (GGSN) or a Packet data network Gateway (PGW).

The AF entity mainly carries out dynamic policy/charging control on the IP-CAN user plane behavior and is arranged on the service platform.

The SPR entity is a logical entity and is used to store information related to all subscribers or subscriptions, including services allowed by the subscribers, etc.

The OCS/OFCS is used for online/offline charging.

As shown in fig. 3, a schematic diagram of PCC architecture in a 5th Generation (5G) system is shown, whose main network elements include but are not limited to: a Policy Control Function (PCF) entity, a Session Management Function (SMF) entity, an Access Management Function (AMF) entity, a User Plane Function (UPF) entity, a Binding Session Function (BSF) entity (not shown in fig. 3), and an AF entity. The role of the PCF entity is similar to that of the PCRF entity in the LTE system. The first Network device may be a BSF (binding session Function) entity, and the second Network device may be a NF (Network Function Service provider) entity, such as a PCF (policy control Function) entity or an SMF (session management Function) entity.

Step 12: and responding to the binding update request, and sending a response result to the second network equipment.

After receiving the binding update request, the first network device updates the binding information of the corresponding session according to the original binding information and the new binding information in the binding update request, and feeds back an update result (i.e., a response result) to the second network device.

Further, the original binding information includes: the binding identification ID information and/or the original IP address information to which the session belongs. The binding identifier ID information is used to determine identity information of the binding information, that is, the binding information used to determine which session needs to be updated. The original IP address information is used to indicate an IP address before the update of the binding information. The new binding information includes: and the new IP address information is used for indicating the IP address after the update of the binding information, namely the IP address of the session needs to be updated to the new IP address.

Further, step 11 comprises: and receiving a binding update request of the session after the user plane function UPF entity is switched. Specifically, as shown in fig. 4, the session binding processing method includes the following steps:

step 41: the SMF entity determines the flow needed to perform the handover (migration) of the UPF entity.

Such as IPv6 multi-homed scenario, the user IP address may change, which may trigger the switching process of the UPF.

Step 42: the SMF entity sends a session establishment request to the target UPF entity (UPF2) and receives a corresponding session establishment response.

Step 43: and the SMF entity reports the session management strategy update to the PCF entity.

Step 44: the SMF entity selects a transit UPF entity (BP UPF entity) and temporarily maintains the session on the BP UPF.

Wherein, this process includes: the SMF entity sends a session establishment request to the BP UPF, and the BP UPF feeds back a session establishment response to the SMF entity.

Step 45: the SMF entity sends a session update request to the original UPF (UPF1) and receives a session update response fed back by the UPF 1.

Step 46: the SMF entity sends a session update request to the target UPF (UPF2) and receives a feedback IDE session update response to the UPF 2.

Step 45 and step 46 do not have a strict time sequence, and step 45 may be executed first, or step 46 may be executed first.

Step 47: and executing the UPF switching process.

Wherein the process comprises the following steps: the SMF entity and the AMF entity continue the information transmission of N1 and N2, the AMF entity sends an N2 request to a Radio Access Network (RAN) and receives an N2 response fed back by the request, and the AMF entity further sends a Packet Data Unit (PDU) session context request to the SMF entity and receives a PDU session context response fed back by the PDU. In addition, the SMF entity allocates a new IPv6 prefix to the terminal to implement the handover of the UPF1 to the UPF2, and performs step 48 or 49 when the handover is successful.

And 48: the SMF entity sends a session update request to the BP UPF and receives a session update response fed back by the BP UPF.

Step 49: triggering the binding conversation updating process.

The process includes

steps

11 and 12 as described above, taking the first network device as the BSF entity and the second network device as the SMF entity as an example, the process includes: the SMF entity sends a binding update request to the BSF entity, and the BSF entity responds to the binding update request, updates the original binding information into new binding information, for example, updates the prefix of the original IPv6 into a new IPv6 prefix, and releases the original IPv6 prefix for other terminals to use.

In the IPv6 multi-host scenario, in the PDU session handover anchor point process, after the SMF finishes updating the IPv6 address of the user, the SMF triggers the session management policy updating process to inform the PCF entity to release the IPv6 prefix. The PCF entity/SMF entity can further trigger the operation of binding management updating service to update the binding information in the BSF information.

It should be noted that there is no strict time sequence between the steps 48, and the steps 48 and 49 may be executed first.

Step 410: after the UPF is switched, the SMF entity further sends a session release request to the original UPF and receives a session release response fed back by the original UPF to release the session.

Wherein step 12 comprises: and updating the original binding information into new binding information according to the binding update request, and feeding back response success or no content in response to the second network equipment. Wherein, the response success indicates that the update of the binding information is successful, which can be indicated by signaling 200(OK), and the response No-Content indicates that the binding information is not found, which can be indicated by signaling 204(No Content).

As described above, the session binding process of the embodiment of the present invention includes: registering binding information, deregistering binding information, inquiring binding information, updating binding information and the like. The processes of inquiring the binding information, updating the binding information and the like are performed before the process of registering the binding information and after the process of deregistering the binding information. There is no strict sequence between querying binding information and updating binding information.

As shown in fig. 5, the process of registering the binding information includes the following steps:

step 51: the SMF/PCF entity sends a binding registration request to the BSF entity.

The binding registration request may be sent via POST signaling.

Step 52: in response to the binding registration request.

Binding information for the registration session.

Step 53: the response result is fed back through signaling 201 (Created).

As shown in fig. 6, the process of querying binding information includes the following steps:

step 61: the SMF/PCF entity sends a binding inquiry request to the BSF entity.

The binding query request may be sent via GET signaling.

Step 62: responding to the binding inquiry request.

The BSF entity locally searches for corresponding binding information.

And step 63: the response result is fed back through signaling 200 (OK).

As shown in fig. 7, the process of updating the binding information includes the following steps:

step 71: the SMF/PCF entity sends a binding update request to the BSF entity.

The binding update request may be sent via HTTP PATCH signaling or HTTP PUT signaling.

Step 72: in response to the binding update request.

The BSF entity locally updates the corresponding binding information.

Step 73: the response result is fed back through signaling 200 or signaling 204.

As shown in fig. 8, the process of deregistering binding information includes the steps of:

step 81: the SMF/PCF entity sends a binding de-registration request to the BSF entity.

The binding de-registration request may be sent via DELETE signaling.

Step 82: in response to the binding deregistration request.

The BSF entity locally deletes the corresponding binding information.

Step 83: the response result is fed back through signaling 204.

The binding update request in the binding information update process may be a hypertext Transfer Protocol (HTTP) PATCH request or an HTTP replace PUT request. The HTTP PATCH request refers to updating part of the binding information of the session, and the HTTP PUT request refers to updating all the binding information of the session.

When the update binding information is the request HTTP PATCH, as shown in fig. 9, the process of updating the binding information includes the following steps:

step 91: the SMF/PCF entity sends HTTP PATCH a request to the BSF entity.

The HTTP PATCH request carries a binding ID and an IP address.

And step 92: in response to HTTP PATCH the request.

The BSF entity locally updates the corresponding binding information.

Step 93: the response result is fed back through signaling 200 or signaling 204.

When the update binding information is an HTTP PUT request, as shown in fig. 10, the process of updating the binding information includes the following steps:

step 101: the SMF/PCF entity sends an HTTP PUT request to the BSF entity.

The HTTP PUT request carries a binding ID and an IP address.

Step 102: responding to the HTTP PUT request.

The BSF entity locally updates the corresponding binding information.

Step 103: the response result is fed back through signaling 200 or signaling 204.

In the session binding processing method of the embodiment of the invention, the first network device updates the binding information of the session according to the original binding information and the new binding information related to the session after receiving the binding update request of the session binding, thereby preventing the session from being interrupted or invalid due to the change of the binding information of the session binding and ensuring the continuity of the session.

The above embodiments are respectively introduced to the session binding processing method of the present invention, and the following embodiments will further describe the corresponding network device with reference to the drawings.

Specifically, as shown in fig. 11, when the network device is the first network device 1100, the network device of the embodiment of the present invention includes the following functional modules:

a first receiving module 1110, configured to receive a binding update request of a session; the binding update request carries original binding information and new binding information related to the session;

the response module 1120 is configured to respond to the binding update request and send a response result to the second network device.

Wherein, the binding update request is a hypertext transfer protocol HTTP PATCH PATCH request or an HTTP replacement PUT request.

Wherein, the original binding information comprises: the binding identification ID information and/or the original IP address information to which the session belongs.

Wherein the new binding information includes: information of the new IP address to which the session belongs.

Wherein, the response module 1120 comprises:

and the response unit is used for updating the original binding information into new binding information according to the binding update request and feeding back response success or response no content to the second network equipment.

Wherein, the first receiving module 1110 includes:

and the receiving unit is used for receiving the binding update request of the session after the user plane function UPF entity is switched.

The first network equipment is a Binding Session Function (BSF) entity.

The second network device is a policy control function PCF entity or a session management function SMF entity.

The embodiment of the first network device of the present invention is corresponding to the embodiment of the method described above, and all implementation means in the embodiment of the method described above are applicable to the embodiment of the network device, and the same technical effect can be achieved. After receiving the binding update request of the session binding, the first network device updates the binding information of the session according to the original binding information and the new binding information related to the session, so that session interruption or failure caused by change of the binding information of the session binding is prevented, and the continuity of the session is ensured.

The session binding processing method of the embodiment of the present invention is introduced from the first network side, and the session binding processing method of the second network device side will be further described with reference to the drawings.

As shown in fig. 12, an embodiment of the present invention provides a session binding processing method, which is applied to a second network device side, and specifically includes the following steps:

step 121: sending a binding update request of the session; the binding update request carries the original binding information and the new binding information related to the session.

The session binding process of the embodiment of the invention comprises the following steps: registering binding information, deregistering binding information (or called deleting binding information), inquiring binding information, updating binding information and the like. And when the binding information needs to be updated, sending a binding update request to the first network equipment so as to update the binding information of the session and ensure the continuity of the session.

Step 122: and receiving a response result fed back by the first network equipment after responding to the binding update request.

And after receiving the binding update request, the first network equipment updates the binding information of the corresponding session according to the original binding information and the new binding information in the binding update request, and feeds back the update result to the second network equipment.

The main network elements of the PCC architecture in the LTE system include, but are not limited to: PCRF entity, PCEF entity, AF entity, OCS/OFCS and SPR and the like. The main network elements of the PCC architecture in the 5G system include, but are not limited to: PCF entity, SMF entity, AMF entity, UPF entity, BSF entity, AF entity, etc. The first network device may be a BSF entity, and the second network device may be an NF Service provider entity, such as a PCF entity or an SMF entity.

Further, the original binding information includes: the binding identification ID information and/or the original IP address information to which the session belongs. Wherein the binding identification ID information is used to determine which session's binding information needs to be updated. The original IP address information is used to indicate an IP address before the update of the binding information. The new binding information includes: and the new IP address information is used for indicating the IP address after the update of the binding information.

In the session binding processing method of the embodiment of the invention, the second network device sends the binding update request to the first network device, the binding update request carries the original binding information and the new binding information related to the session, and the first network device can update the binding information of the session according to the binding update request, so that the session interruption or failure caused by the change of the binding information of the session binding is prevented, and the continuity of the session is ensured.

Specifically, as shown in fig. 13, when the network device is the second network device 1300, the network device of the embodiment of the present invention includes the following functional modules:

a first sending module 1310, configured to send a binding update request for a session; the binding update request carries original binding information and new binding information related to the session;

the second receiving module 1320 is configured to receive a response result fed back by the first network device after responding to the binding update request.

The first network equipment is a Binding Session Function (BSF) entity.

The second network device is a policy control function PCF entity or a session management function SMF entity. The second network device embodiment of the present invention is corresponding to the embodiment of the method described above, and all implementation means in the method embodiment are applicable to the embodiment of the terminal, and the same technical effect can be achieved. The second network equipment sends a binding update request to the first network equipment, the binding update request carries original binding information and new binding information related to the session, and the first network equipment can update the binding information of the session according to the binding update request, so that session interruption or failure caused by change of the binding information of the session binding is prevented, and the continuity of the session is ensured.

To better achieve the above object, as shown in fig. 14, an embodiment of the present invention further provides a network device, including: a processor 1400; a memory 1420 coupled to the processor 1400 through a bus interface, and a transceiver 1410 coupled to the processor 1400 through a bus interface; the memory 1420 is used to store programs and data used by the processor in performing operations; transmitting data information or pilot frequency through the transceiver 1410, and receiving an uplink control channel through the transceiver 1410; when the processor 1400 calls and executes the programs and data stored in the memory 1420, the following functions are implemented:

wherein, when the network device is a first network device,

a transceiver 1410 configured to receive and transmit data under the control of the processor 1400, and specifically configured to: receiving a binding update request of a session; the binding update request carries the original binding information and the new binding information related to the session.

The processor 1400 is used for reading the program in the memory 1420 and executing the following processes: and responding to the binding update request, and controlling the transceiver to send a response result to the second network equipment.

Wherein, the processor 1400 is specifically configured to: and updating the original binding information to new binding information according to the binding update request, and controlling the transceiver 1410 to feed back a response success or no content to the second network device.

The transceiver 1410 is specifically configured to: and receiving a binding update request of the session after the user plane function UPF entity is switched.

The first network equipment is a Binding Session Function (BSF) entity.

Wherein, when the network device is a second network device,

the transceiver 1410 is configured to: sending a binding update request of the session; the binding update request carries original binding information and new binding information related to the session; and receiving a response result fed back by the first network equipment after responding to the binding update request.

The first network equipment is a Binding Session Function (BSF) entity.

Where in fig. 14 the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors, represented by the processor 1400, and various circuits of memory, represented by the memory 1420, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1410 may be a number of elements including a transmitter and a transceiver providing a means for communicating with various other apparatus over a transmission medium. The processor 1400 is responsible for managing the bus architecture and general processing, and the memory 1420 may store data used by the processor 1400 in performing operations.

Those skilled in the art will appreciate that all or part of the steps for implementing the above embodiments may be performed by hardware, or may be instructed to be performed by associated hardware by a computer program that includes instructions for performing some or all of the steps of the above methods; and the computer program may be stored in a readable storage medium, which may be any form of storage medium.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements each process of the above-mentioned session binding processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

Furthermore, it is to be noted that in the device and method of the invention, it is obvious that the individual components or steps can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of performing the series of processes described above may naturally be performed chronologically in the order described, but need not necessarily be performed chronologically, and some steps may be performed in parallel or independently of each other. It will be understood by those skilled in the art that all or any of the steps or elements of the method and apparatus of the present invention may be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or any combination thereof, which can be implemented by those skilled in the art using their basic programming skills after reading the description of the present invention.

Thus, the objects of the invention may also be achieved by running a program or a set of programs on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future. It is further noted that in the apparatus and method of the present invention, it is apparent that each component or step can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of executing the series of processes described above may naturally be executed chronologically in the order described, but need not necessarily be executed chronologically. Some steps may be performed in parallel or independently of each other.

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A session binding processing method is applied to a first network device, and is characterized by comprising the following steps:

receiving a binding update request of a session; wherein, the binding update request carries the original binding information and the new binding information related to the session;

2. The session binding processing method according to claim 1, wherein the binding update request is a hypertext transfer protocol HTTP PATCH request or an HTTP replacement PUT request.

3. The session binding processing method according to claim 1, wherein the original binding information comprises: and binding identification ID information and/or original IP address information to which the session belongs.

4. The session binding processing method according to claim 1, wherein the new binding information comprises: new IP address information to which the session belongs.

5. The session binding processing method according to claim 1, wherein the step of responding to the binding update request and sending the response result to the second network device comprises:

and updating the original binding information into new binding information according to the binding update request, and feeding back response success or response no content to the second network equipment.

6. The session binding processing method according to claim 1, wherein the step of receiving a binding update request of the session comprises:

and receiving a binding update request of the session after the user plane function UPF entity is switched.

7. The session binding processing method according to claim 1, wherein the first network device is a binding session function, BSF, entity.

8. The session binding processing method of claim 1, wherein the second network device is a Policy Control Function (PCF) entity or a Session Management Function (SMF) entity.

9. A network device, the network device being a first network device, the first network device comprising: a processor; a memory coupled to the processor, and a transceiver coupled to the processor; the processor is used for calling and executing the programs and the data stored in the memory;

the transceiver is configured to: receiving a binding update request of a session; wherein, the binding update request carries the original binding information and the new binding information related to the session;

10. The network device of claim 9, wherein the binding update request is a hypertext transfer protocol (HTTP) PATCH (PATCH) request or an HTTP replace (PUT) request.

11. The network device of claim 9, wherein the original binding information comprises: and binding identification ID information and/or original IP address information to which the session belongs.

12. The network device of claim 9, wherein the new binding information comprises: new IP address information to which the session belongs.

13. The network device of claim 9, wherein the processor is specifically configured to: and updating the original binding information into new binding information according to the binding update request, and controlling the transceiver to feed back response success or no content to the second network equipment.

14. The network device of claim 9, wherein the transceiver is specifically configured to: and receiving a binding update request of the session after the user plane function UPF entity is switched.

15. The network device of claim 9, wherein the first network device is a Binding Session Function (BSF) entity.

16. The network device of claim 9, wherein the second network device is a Policy Control Function (PCF) entity or a Session Management Function (SMF) entity.

17. A network device, the network device being a first network device, comprising:

the first receiving module is used for receiving a binding update request of a session; wherein, the binding update request carries the original binding information and the new binding information related to the session;

18. A session binding processing method applied to a second network device is characterized by comprising the following steps:

sending a binding update request of the session; wherein, the binding update request carries the original binding information and the new binding information related to the session;

19. The session binding processing method of claim 18, wherein the binding update request is a hypertext transfer protocol (HTTP) PATCH (PATCH) request or an HTTP replace PUT (PUT) request.

20. The session binding processing method according to claim 18, wherein the original binding information comprises: and binding identification ID information and/or original IP address information to which the session belongs.

21. The session binding processing method according to claim 18, wherein the new binding information comprises: new IP address information to which the session belongs.

22. The session binding processing method according to claim 18, wherein the first network device is a binding session function, BSF, entity.

23. The session binding processing method of claim 18, wherein the second network device is a Policy Control Function (PCF) entity or a Session Management Function (SMF) entity.

24. A network device, the network device being a second network device, the second network device comprising: a processor; a memory coupled to the processor, and a transceiver coupled to the processor; the processor is used for calling and executing the programs and the data stored in the memory;

the transceiver is configured to: sending a binding update request of the session; wherein, the binding update request carries the original binding information and the new binding information related to the session; and

25. The network device of claim 24, wherein the binding update request is a hypertext transfer protocol (HTTP) PATCH (PATCH) request or an HTTP replace (PUT) request.

26. The network device of claim 24, wherein the original binding information comprises: and binding identification ID information and/or original IP address information to which the session belongs.

27. The network device of claim 24, wherein the new binding information comprises: new IP address information to which the session belongs.

28. The network device of claim 24, wherein the first network device is a Binding Session Function (BSF) entity.

29. The network device of claim 24, wherein the second network device is a Policy Control Function (PCF) entity or a Session Management Function (SMF) entity.

30. A network device, the network device being a second network device, comprising:

the first sending module is used for sending a binding update request of the session; wherein, the binding update request carries the original binding information and the new binding information related to the session;

31. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the session binding processing method according to any one of claims 1 to 8, or the steps of the session binding processing method according to any one of claims 18 to 23.