CN113316269A - Session management method and device - Google Patents

Session management method and device Download PDF

Info

Publication number
CN113316269A
CN113316269A CN202110467494.4A CN202110467494A CN113316269A CN 113316269 A CN113316269 A CN 113316269A CN 202110467494 A CN202110467494 A CN 202110467494A CN 113316269 A CN113316269 A CN 113316269A
Authority
CN
China
Prior art keywords
session
target
entity
request message
historical
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110467494.4A
Other languages
Chinese (zh)
Other versions
CN113316269B (en
Inventor
马涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
WUHAN HONGXU INFORMATION TECHNOLOGY CO LTD
Original Assignee
WUHAN HONGXU INFORMATION TECHNOLOGY CO LTD
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by WUHAN HONGXU INFORMATION TECHNOLOGY CO LTD filed Critical WUHAN HONGXU INFORMATION TECHNOLOGY CO LTD
Priority to CN202110467494.4A priority Critical patent/CN113316269B/en
Publication of CN113316269A publication Critical patent/CN113316269A/en
Application granted granted Critical
Publication of CN113316269B publication Critical patent/CN113316269B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections

Abstract

The invention provides a session management method and a session management device, wherein the method comprises the following steps: judging whether a first target historical session exists in a session record or not based on a session establishment request message sent to a UPF entity by an SMF entity; if judging that the first target historical conversation exists in the conversation record, updating the first target historical conversation based on the conversation establishment request message; the first target historical session is a historical session of which the session context comprises identity information of a target user carried by the session establishment request message. According to the session management method and device provided by the invention, after the first target historical session exists in the session record is determined according to the identity information of the target user carried by the session establishment request message, the first target historical session is updated based on the session establishment request message, the session management can be carried out on the N4 interface on the premise of not matching the SMF entity and the UPF entity, and the original deployment and operation modes of the SMF entity and the UPF entity are not interfered.

Description

Session management method and device
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a session management method and apparatus.
Background
A Fifth Generation (5G) mobile communication system architecture is composed of several Network Functions (NFs). The Session Management Function (SMF) is a control plane network element, and may manage establishment, modification, and release of a Session, and may also allocate and manage an IP of a user terminal. A User Plane Function (UPF) is a Data Plane network element, and may be used as a mobility anchor point of a Radio Access Technology (RAT), may also allocate an IP of a User terminal in response to a request of an SMF entity, may also be used as a connection point between a Protocol Data Unit (PDU) session and an external Data Network (DN), and may also perform packet routing and forwarding, etc. The N4 interface is an interface between the SMF entity and the UPF entity, and in the PDU Session procedure of the UE, an N4 Session, also called PFCP Session, is established simultaneously. An application layer Protocol of the N4 interface adopts a Packet Forwarding Control Protocol (PFCP) Protocol, and is used for defining ways of identifying, Forwarding, caching, marking, reporting and multi-access to a PDU by a UPF entity.
The PRCP session in the signaling flow of the N4 interface carries more valuable information, for example: identity information of the user, etc. Therefore, the session management of the N4 interface can improve the operation capability of the 5G communication network.
In the prior art, when session management is performed on an N4 interface, an SMF entity and a UPF entity need to be matched, which causes problems of deployment dispersion and complex cooperation process.
Disclosure of Invention
The invention provides a session management method and a session management device, which are used for solving the defects that in the prior art, session management needs to be carried out by matching an SMF entity and a UPF entity, the deployment is dispersed, the cooperation process is complex, and the session management without interfering with the original deployment operation mode of the SMF entity and the UPF entity is realized.
The invention provides a session management method, which is characterized by comprising the following steps:
judging whether a first target historical session exists in a session record or not based on a session establishment request message sent to a UPF entity by an SMF entity;
if judging that the session record contains a first target historical session, updating the first target historical session based on the session establishment request message;
the first target historical session is a historical session of which the session context includes the identity information of the target user carried by the session establishment request message.
According to a session management method provided by the present invention, after determining whether a first target historical session exists in a session record based on a session establishment request message sent by an SMF entity, the method further includes:
and if judging that the first target historical conversation does not exist in the conversation record, establishing a conversation corresponding to the target user, and updating the conversation corresponding to the target user based on the conversation establishment request message.
According to a session management method provided by the present invention, the method further comprises:
based on a session establishment response message which is returned to the SMF entity by the UPF entity and indicates that the response is successful, if judging that a second target historical session exists in a session record, updating the second target historical session based on the session establishment response message;
the second target historical session is a historical session of which the session context comprises a first target field carried by the session establishment response message; the first target field comprising: and the SMF entity allocates the identity to the UPF entity and the IP address of the SMF entity.
According to a session management method provided by the present invention, the method further comprises:
based on a session modification request message sent by the SMF entity to the UPF entity, if judging that a third target historical session exists in the session record, updating the third target historical session based on the session modification request message;
wherein, the third target history session is a history session whose session context includes a second target field carried by the session modification request message; the second target field comprising: and the UPF entity allocates the identity to the SMF entity and the IP address of the UPF entity.
According to a session management method provided by the present invention, the method further comprises:
based on a session modification response message which is returned to the SMF entity by the UPF entity and represents the successful response, if judging that a fourth target historical session exists, updating the fourth target historical session based on the session modification response message;
wherein the fourth target history session is a history session whose session context includes the first target field carried by the session modification response message.
According to a session management method provided by the present invention, the method further comprises:
based on a session deletion response message which is returned to the SMF entity by the UPF entity and represents that the response is successful, if judging that a fifth target historical session exists, deleting the fifth target historical session;
wherein the fifth target history session is a history session whose session context includes the first target field carried by the session deletion response message.
The present invention also provides a session management apparatus, including:
the judging module is used for judging whether a first target historical session exists in the session record or not based on a session establishment request message sent to the UPF entity by the SMF entity;
the updating module is used for updating the first target historical session based on the session establishment request message if judging that the session record contains the first target historical session;
the first target historical session is a historical session of which the session context includes the identity information of the target user carried by the session establishment request message.
The invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the session management method as described in any one of the above.
According to the session management method and device, after the first target historical session is determined to exist in the session record according to the identity information of the target user carried by the session establishment request message, the first target historical session is updated based on the session establishment request message, the session management can be performed on the N4 interface on the premise that the cooperation of the SMF entity and the UPF entity is not needed, the original deployment and operation modes of the SMF entity and the UPF entity are not interfered, and the session management is lower in complexity, higher in accuracy and higher in practicability.
Drawings
In order to more clearly illustrate the technical solutions of the present invention or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a flow chart of signaling transmission in a session management method provided by the present invention;
FIG. 2 is a flow chart of a session management method provided by the present invention;
FIG. 3 is a schematic structural diagram of a session management apparatus provided in the present invention;
fig. 4 is a schematic structural diagram of an electronic device provided in the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
It should be noted that, by deriving all signaling packets communicated between the SMF entity and the UPF entity, a Session Establishment Request message (Session Establishment Request) sent by the SMF entity to the UPF entity, a Session Establishment Response message (Session Establishment Response) returned by the UPF entity to the SMF entity, a Session Modification Request message (Session Modification Request) sent by the SMF entity to the UPF entity, a Session Modification Response message (Session Modification Response) returned by the UPF entity to the SMF entity, a Session Deletion Request message (Session Deletion Request) sent by the SMF entity to the UPF entity, and a Session Deletion Response message (Session Deletion Response) returned by the UPF entity to the SMF entity can be obtained.
Fig. 1 is a flow chart of signaling transmission in the session management method provided by the present invention. As shown in fig. 1, after the SMF entity sends a PFCP session establishment request message to the UPF entity, the UPF entity returns a PFCP session establishment response message to the SMF entity; after the SMF entity sends a PFCP session modification request message to the UPF entity, the UPF entity returns a PFCP session modification response message to the SMF entity; after the SMF entity sends the PFCF session deletion request message to the UPF entity, the UPF entity returns a PFCF session deletion response message to the SMF entity.
Fig. 2 is a flowchart illustrating a session management method provided in the present invention. The session management method of the present invention is described below in conjunction with fig. 2. As shown in fig. 2, the method includes: step 201, based on the session establishment request message sent by the SMF entity to the UPF entity, determining whether a first target historical session exists in the session record.
The first target historical session is a historical session of which the session context comprises identity information of a target user carried by the session establishment request message.
It should be noted that the Session Establishment Request message sent by the SMF entity to the UPF entity is a PFCP Session Establishment Request message (PFCP Session Establishment Request).
The session establishment request message may carry identity information of the target user.
The Identity information of the target user may include an Identity Document (ID) of the target user. The identification of the target user may include: at least one of an International Mobile Subscriber Identity (IMSI) or a Subscriber hidden Identifier (SUCI).
The session establishment request message may also carry information such as a CP F-SEID, identity information of the UPF entity, an IP address of the UPF, an identity allocated by the UPF entity to the SMF entity, an IP address of a User Equipment (UE), and identity information and an IP address of a 5G base station (next) generation NodeB, gNB, and the like.
The CP F-SEID may include: the SMF entity assigns the UPF entity with the identification, the IP address of the SMF entity and the like.
It should be noted that the identity allocated by the SMF entity to the UPF entity at least includes a Session Endpoint Identifier (SEID) allocated by the SMF entity to the UPF entity.
The identity information of the UPF entity may include a Tunnel Endpoint Identifier (TEID) and an IP of the UPF entity, and the like.
The identity assigned by the UPF entity to the SMF entity at least comprises the SEID assigned by the UPF entity to the SMF entity.
It should be noted that the identity of the target user carried in the session establishment request message may be used as a target field carried in the session establishment request message.
The identity information of the gNB may include the TEID of the gNB, etc.
It should be noted that information, such as the identity information of the target User, the CP F-SEID, the identity information of the UPF entity, the IP address of the UPF entity, the identity identifier allocated by the UPF entity to the SMF entity, the IP address of the User Equipment (UE), the identity information and the IP address of the 5G base station ((next) generation NodeB, gNB), and the like, carried by the session establishment request message may be referred to as an effective cell carried by the session establishment request message.
Based on the SMF entity sending a session establishment request message to the UPF entity, it may be determined whether a first target historical session exists in the session record.
Specifically, whether a history session including the identity information of the target user in the session context exists is searched in the session record.
Step 202, if it is judged and known that the first target historical session exists in the session record, updating the first target historical session based on the session establishment request message.
If the history session of which the session context includes the identity information of the target user is found in the session record, it indicates that the history session and the session establishment request message correspond to the target user. And taking the history session as a first target history session, and determining that the first target history session exists in the session record.
After determining that the first target historical session exists in the session record, the first target historical session may be backed up, and the first target historical session may be updated based on the valid information element carried by the session establishment request message.
Specifically, if a plurality of original information in the first target history session is inconsistent with the valid cells carried by the session establishment request message, the inconsistent valid cells may be correspondingly stored in the first target history session, and the original information in the first target history session is deleted; or if the effective cell carried by the session establishment request message includes the missing information in the first target historical session, supplementing the missing information according to the effective credit carried by the session establishment request message, and realizing the update of the first target historical session.
It should be noted that, after the first target history session is updated, the updated first target history session may be stored in the session record.
According to the embodiment of the invention, after the first target historical session is determined to exist in the session record according to the identity information of the target user carried by the session establishment request message, the first target historical session is updated based on the session establishment request message, the session management can be carried out on the N4 interface on the premise of not matching the SMF entity and the UPF entity, the original deployment and operation modes of the SMF entity and the UPF entity are not interfered, and the complexity of the session management is lower, the accuracy is higher and the practicability is higher.
Based on the content of the foregoing embodiments, after determining whether the first target historical session exists in the session record based on the session establishment request message sent by the SMF entity, the method further includes: and if judging that the first target historical conversation does not exist in the conversation record, establishing a conversation corresponding to the target user, and updating the conversation corresponding to the target user based on the conversation establishment request message.
Specifically, if the history session of which the session context includes the identity information of the target user is not found in the session record, it is indicated that the history session corresponding to the target user does not exist in the session record, that is, it is determined that the first target history session does not exist in the session record.
After determining that the first target historical session does not exist in the session record, a session corresponding to the target user can be created according to the identity information of the target user.
After the session corresponding to the target user is created, the information such as the CP F-SEID, the identity information and the IP address of the UPF entity, the IP address of the UE, the identity information and the IP address of the gNB, and the like, carried in the session establishment request message may be stored in the session corresponding to the target user, so as to update the session corresponding to the target user.
It should be noted that after creating and updating the session corresponding to the target user, the session corresponding to the target user may be stored in the session record.
It should be noted that, after creating and updating the session corresponding to the target user, the UPF entity may return a session establishment response message indicating that the response is successful to the SMF entity.
The embodiment of the invention establishes and updates the session corresponding to the target user after determining that the session context does not exist in the session record and the first target historical session including the identity information of the target user, can establish the session corresponding to the target user in a communication network based on the session establishment request message, can carry out session management on the N4 interface on the premise of not matching the SMF entity and the UPF entity, and does not interfere with the original deployment and operation modes of the SMF entity and the UPF entity.
Based on the content of the foregoing embodiments, the session management method further includes: and based on a session establishment response message which is returned to the SMF entity by the UPF entity and indicates that the response is successful, if the session record is judged and known to have the second target historical session, updating the second target historical session based on the session establishment response message.
The second target historical conversation comprises the historical conversation of the first target field carried by the conversation establishment response message for the conversation context; a first target field comprising: and the SMF entity assigns the identity and the IP address of the SMF entity to the UPF entity.
Specifically, the SMF entity may determine whether the response is successful according to a Cause value carried in a session establishment response message returned by the UPF entity.
And if the Cause value carried by the session establishment response message represents that the response is successful, determining that the SMF entity receives the session establishment response message representing that the response is successful, and further determining that the response is successful.
The session establishment response message returned by the UPF entity to the SMF entity can carry information such as the UP F-SEID, the identity information of the UPF entity, the IP address of the SMF entity, the identity allocated to the UPF entity by the SMF entity and the like besides the Cause value. The above information carried by the session establishment response message may be referred to as an active information element carried by the session establishment response message.
The identity allocated by the SMF entity to the UPF entity at least comprises the SEID allocated by the SMF entity to the UPF entity.
It should be noted that the identity and the IP address of the SMF entity, which are allocated to the UPF entity by the SMF entity carried in the session establishment response message, may be used as the first target field carried in the session establishment response message.
After the SMF entity receives the session establishment response message indicating that the response is successful, which is returned by the UPF entity, it may search, in the session record, whether there is a history session including the identity assigned to the UPF entity by the SMF entity and the IP address of the SMF entity in the session context, which are carried by the session establishment response message.
If the session context includes the historical session of the identity and the IP address of the SMF entity allocated to the UPF entity by the SMF entity carried in the session establishment response message, it is indicated that the historical session and the session modification response message correspond to the same user. And taking the history session as a fourth target history session, and determining that a second target history session exists in the session record.
It should be noted that the second target history session may be the same as or different from the first target history session. The second target history session is the same as the first target history session and both correspond to the target user.
After determining that the second target history session exists in the session record, the second target session may be backed up and updated based on the session establishment response message.
Specifically, according to inconsistent information in the valid cells carried by the session establishment response message in the second target history session or missing information in the second target history session, part or all of the valid cells carried by the session establishment response message may be correspondingly stored in the second target history session, so as to update the second target history session.
It should be noted that, after the second target history session is updated, the updated second target history session may be stored in the session record.
It should be noted that, if the SMF entity does not receive the session establishment response message returned by the UPF entity, or if the Cause value carried in the session establishment response message received by the SMF entity represents a response failure, it may be determined that the SMF entity fails to respond.
After determining that the SMF entity fails to respond, it may be determined whether the session corresponding to the target user in the session record is first created based on the session establishment request message carrying the identity information of the target user.
If it is determined that the session corresponding to the target user in the session record is first created based on the session establishment request message carrying the identity information of the target user, it may be indicated that the first request of the target user is rejected, and the session context of the session corresponding to the first created target user may be deleted.
If the session corresponding to the target user in the session record is judged to be not established for the first time based on the session establishment request message carrying the identity information of the target user, that is, the session corresponding to the target user is the first target history session, the updated first target history session in the session record can be rolled back, and the valid cell carried by the backed-up session establishment request message is recovered.
According to the embodiment of the invention, after the existence of the second target historical session of which the session context comprises the first target field carried by the session establishment response message in the session record is determined, the second target historical session is updated, so that the session management can be carried out on the N4 interface on the premise of not matching the SMF entity and the UPF entity, and the original deployment and operation modes of the SMF entity and the UPF entity are not interfered.
Based on the content of the foregoing embodiments, the session management method further includes: and updating the third target historical session based on the session modification request message if judging that the third target historical session exists in the session record based on the session modification request message sent by the SMF entity to the UPF entity.
The third target historical conversation is a historical conversation of which the conversation context comprises a second target field carried by the conversation modification request message; a second destination field comprising: and the UPF entity assigns the SMF entity with an identification and the IP address of the UPF entity.
It should be noted that the Session Modification Request message sent by the SMF entity to the UPF entity may be a PRCP Session Modification Request message (PFCP Session Modification Request).
The session modification request message sent by the SMF entity to the UPF entity may carry information such as the CP F-SEID, the identity information of the UPF entity, the IP address of the UPF entity, the identity allocated by the UPF entity to the SMF entity, the IP address of the UE, and the identity information and IP address of the gNB.
It should be noted that the identity and the IP address of the UPF entity, which are allocated to the SMF entity by the UPF entity carried in the session modification request message, may be used as the second target field carried in the session modification request message.
It should be noted that the information, such as the CP F-SEID, the identity information of the UPF entity, the IP address of the UE, and the identity information and the IP address of the gNB, carried in the session modification message may be referred to as an effective cell carried in the session modification request message.
After receiving the session modification request message sent by the SMF entity, the UPF entity may search in the session record whether there is a historical session including an identity assigned to the SMF entity by the UPF entity carried in the session modification request message and an IP address of the UPF entity in the session context.
If the session context includes the historical session of the identity and the IP address of the UPF entity allocated to the SMF entity by the UPF entity carried by the session modification request message, which is found in the session record, it is indicated that the historical session and the session modification request message correspond to the same user. And taking the history session as a third target history session, and determining that the third target history session exists in the session record.
It should be noted that the third target history session may be the same as or different from the first target history session or the second target history session.
After determining that the third target historical session exists in the session record, the third target historical session may be backed up, and the third target historical session may be updated based on the valid cell carried by the session modification request message.
Specifically, according to the inconsistent information in the effective cell carried by the session modification request message in the third target history session or the missing information in the third target history session, part or all of the effective cell carried by the session modification request message may be correspondingly stored in the third target history session, so as to update the third target history session.
It should be noted that, after the third target history session is updated, the updated third target history session may be stored in the session record.
It should be noted that, if a history session in which the session context includes the identity assigned to the UPF entity by the SMF entity carried by the session modification request message and the IP address of the SMF entity is not found in the session record, it is indicated that a history session corresponding to the same user as the session modification request message does not exist in the session record, that is, it is determined that a third target history session does not exist in the session record. If it is determined that the third target historical session does not exist in the session record, the derived session modification request message may be discarded.
According to the embodiment of the invention, after the third target historical session of which the session context comprises the target field is determined to exist in the session record through the target field carried by the session modification request message, the third target historical session is updated based on the session modification request message, the session management can be carried out on the N4 interface on the premise of not matching the SMF entity and the UPF entity, and the original deployment and operation modes of the SMF entity and the UPF entity are not interfered.
Based on the content of the foregoing embodiments, the session management method further includes: and based on the session modification response message which is returned to the SMF entity by the UPF entity and indicates that the response is successful, if the fourth target historical session is judged and known to exist, updating the fourth target historical session based on the session modification response message.
And the fourth target historical session is a historical session of which the session context comprises a first target field carried by the session modification response message.
It should be noted that the Session Modification Response message returned by the UPF entity to the SMF entity may be a PFCP Session Modification Response message (PFCP Session Modification Response).
The SMF entity may determine whether the response is successful according to the Cause value carried in the session establishment response message.
And if the Cause value carried by the session modification response message represents that the response is successful, determining that the SMF entity receives the session modification response message representing that the response is successful, and further determining that the response is successful.
The session modification response message returned from the UPF entity to the SMF entity may also carry information such as the identity information of the UPF entity, the IP address of the SMF entity, and the identity allocated by the SMF entity to the UPF entity, in addition to the Cause value. The above information carried by the session modification response message may be referred to as an active information element carried by the session modification response message.
It should be noted that the identity and the IP address of the SMF entity, which are allocated to the UPF entity by the SMF entity carried in the session modification response message, may be used as the first target field carried in the session modification response message.
After the SMF entity receives the session modification response message indicating that the response is successful, which is returned by the UPF entity, it may search, in the session record, whether there is a history session including the identity assigned to the UPF entity by the SMF entity and the IP address of the SMF entity in the session context, which are carried by the session modification response message.
If the session context includes the historical session of the identity and the IP address of the SMF entity allocated to the UPF entity by the SMF entity carried in the session modification response message, it is determined that the historical session and the session modification response message correspond to the same user. And taking the history session as a fourth target history session, and determining that the fourth target history session exists in the session record.
It should be noted that the fourth target history session may be the same as or different from the first target history session, the second target history session, or the third target history session.
After determining that the fourth target history session exists in the session record, the fourth target history session may be backed up and updated based on the session modification response message.
Specifically, according to the inconsistent information in the valid cell carried by the session modification response message in the fourth target history session or the missing information in the fourth target history session, part or all of the valid cell carried by the session modification response message may be correspondingly stored in the fourth target history session, so as to update the fourth target history session.
It should be noted that, after the fourth target history session is updated, the updated fourth target history session may be stored in the session record.
It should be noted that, if the SMF entity does not receive the session modification response message returned by the UPF entity, or if the Cause value carried in the session modification response message received by the SMF entity represents a response failure, it may be determined that the SMF entity fails to respond.
After determining that the SMF fails to respond, the updated third target historical session in the session record may be rolled back to recover the valid cell carried by the backed-up session modification request message.
According to the embodiment of the invention, after the fourth target historical session of which the session context comprises the target field carried by the session modification response message is determined to exist in the session record, the fourth target historical session is updated, so that the session management can be carried out on the N4 interface on the premise of not matching the SMF entity and the UPF entity, and the original deployment and operation modes of the SMF entity and the UPF entity are not interfered.
Based on the content of the foregoing embodiments, the session management method further includes: and based on a session deletion response message which is returned to the SMF entity by the UPF entity and indicates that the response is successful, if the fifth target history session is judged and known to exist, deleting the fifth target history session.
And the fifth target historical session is a historical session of which the session context comprises a first target field carried by the session deletion response message.
It should be noted that, before the session deletion response message indicating that the response is successful is returned to the SMF entity by the UPF entity, the SMF entity sends the session deletion request message to the UPF entity.
It should be noted that the Session Deletion Request message sent by the SMF entity to the UPF entity may be a PRCP Session Deletion Request message (PFCP Session Deletion Request).
The session deletion request message sent by the SMF entity to the UPF entity may carry information such as an IP address of the UPF entity, an IP address of the SMF entity, and an identity allocated to the SMF entity by the UPF entity.
It should be noted that the identity and the IP address of the UPF entity, which are allocated to the SMF entity by the UPF entity carried in the session deletion request message, may be used as the second target field carried in the session deletion request message.
After receiving the session deletion request message sent by the SMF entity, the UPF entity may search in the session record whether there is a historical session including an identity assigned to the SMF entity by the UPF entity carried by the session deletion request message and an IP address of the UPF entity in the session context.
If the session context includes the historical session of the identity and the IP address of the UPF entity allocated to the SMF entity by the UPF entity carried by the session deletion request message, which is found in the session record, it is indicated that the historical session and the session deletion request message correspond to the same user, and the historical session can be backed up. At this time, the UPF entity may return a session deletion response message indicating that the response was successful to the SMF entity.
If the session context does not find the historical session of the session context including the identity allocated to the SMF entity by the UPF entity carried by the session deletion request message and the IP address of the UPF entity in the session record, it indicates that there is no historical session corresponding to the same user as the session deletion request message in the session record, and the derived session deletion request message can be discarded.
The SMF entity may determine whether the response is successful according to the Cause value carried in the session establishment response message.
And if the Cause value carried by the session deletion response message represents that the response is successful, determining that the SMF entity receives the session deletion response message representing that the response is successful, and further determining that the response is successful.
The session deletion response message returned to the SMF entity by the UPF entity may carry information such as the IP address of the UPF entity, the IP address of the SMF entity, and the identity allocated to the UPF entity by the SMF entity, in addition to the Cause value.
It should be noted that the identity and the IP address of the SMF entity, which are allocated to the UPF entity by the SMF entity carried in the session deletion response message, may be used as the first target field carried in the session deletion response message.
After the SMF entity receives the session deletion response message indicating that the response is successful, which is returned by the UPF entity, it may search, in the session record, whether there is a history session including the identity assigned to the UPF entity by the SMF entity and the IP address of the SMF entity in the session context, which are carried by the session deletion response message.
If the session context includes the historical session of the identity and the IP address of the SMF entity allocated to the UPF entity by the SMF entity carried in the session deletion response message, it is determined that the historical session and the session deletion response message correspond to the same user. And taking the history session as a fifth target history session, and determining that the fifth target history session exists in the session record.
After determining that the fifth target history session exists in the session record, the fifth target history session may be deleted.
If it is determined that the fifth target historical session does not exist in the session record, the derived session deletion response message may be discarded.
According to the embodiment of the invention, after the fifth target historical session of which the session context comprises the target field carried by the session deletion response message is determined to exist in the session record, the fifth target historical session is updated, so that the session management can be carried out on the N4 interface on the premise of not matching the SMF entity and the UPF entity, and the original deployment and operation modes of the SMF entity and the UPF entity are not interfered.
Fig. 3 is a schematic structural diagram of a session management apparatus provided in the present invention. The session management method provided by the present invention is described below with reference to fig. 3, and the session management apparatus described below and the session management method described above may be referred to in correspondence with each other. As shown in fig. 3, the apparatus includes: a judging module 301 and an updating module 302.
The determining module 301 is configured to determine whether a first target historical session exists in the session record based on a session establishment request message sent by the SMF entity to the UPF entity.
An updating module 302, configured to update the first target history session based on the session establishment request message if it is determined that the first target history session exists in the session record.
The first target historical session is a historical session of which the session context comprises identity information of a target user carried by the session establishment request message.
Specifically, the judgment module 301 and the update module 302 are electrically connected.
The determining module 301 may search, in the session record, whether a historical session exists in the session context, where the historical session includes the identity information of the target user carried in the session establishment request message sent by the SMF entity to the UPF entity.
If the update module 302 finds the history session whose session context includes the identity information of the target user in the session record, it indicates that the history session and the session establishment request message correspond to the target user. And taking the history session as a first target history session, and determining that the first target history session exists in the session record.
After determining that the first target historical session exists in the session record, the updating module 302 may back up the identity information of the target user carried in the session establishment request message, so as to provide a data basis for subsequent session management. And the first target historical session may be updated based on the valid information element carried by the session establishment request message.
It should be noted that the updating module 302 may also be configured to update the second target history session based on the session establishment response message, if it is determined that the second target history session exists in the session record, based on the session establishment response message, which is returned by the UPF entity to the SMF entity and indicates that the response is successful.
The updating module 302 may be further configured to update the third target history session based on the session modification request message sent by the SMF entity to the UPF entity, if it is determined that the third target history session exists in the session record, the third target history session is updated based on the session modification request message.
The updating module 302 may further update the fourth target history session based on the session modification response message, if it is determined that the fourth target history session exists, based on the session modification response message that indicates that the response is successful and is returned to the SMF entity by the UPF entity.
The updating module 302 may further delete the fifth target history session if it is determined that the fifth target history session exists, based on a session deletion response message indicating that the response is successful, which is returned to the SMF entity by the UPF entity.
According to the embodiment of the invention, after the first target historical session is determined to exist in the session record according to the identity information of the target user carried by the session establishment request message, the first target historical session is updated based on the session establishment request message, the session management can be carried out on the N4 interface on the premise of not matching the SMF entity and the UPF entity, the original deployment and operation modes of the SMF entity and the UPF entity are not interfered, and the complexity of the session management is lower, the accuracy is higher and the practicability is higher.
Fig. 4 illustrates a physical structure diagram of an electronic device, which may include, as shown in fig. 4: a processor (processor)410, a communication Interface 420, a memory (memory)430 and a communication bus 440, wherein the processor 410, the communication Interface 420 and the memory 430 are communicated with each other via the communication bus 440. Processor 410 may invoke logic instructions in memory 430 to perform a session management method comprising: judging whether a first target historical session exists in a session record or not based on a session establishment request message sent to a UPF entity by an SMF entity; if judging that the first target historical conversation exists in the conversation record, updating the first target historical conversation based on the conversation establishment request message; the first target historical session is a historical session of which the session context comprises identity information of a target user carried by the session establishment request message.
In addition, the logic instructions in the memory 430 may be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
In another aspect, the present invention also provides a computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform a session management method provided by the above methods, the method comprising: judging whether a first target historical session exists in a session record or not based on a session establishment request message sent to a UPF entity by an SMF entity; if judging that the first target historical conversation exists in the conversation record, updating the first target historical conversation based on the conversation establishment request message; the first target historical session is a historical session of which the session context comprises identity information of a target user carried by the session establishment request message.
In yet another aspect, the present invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, is implemented to perform the session management method provided above, the method comprising: judging whether a first target historical session exists in a session record or not based on a session establishment request message sent to a UPF entity by an SMF entity; if judging that the first target historical conversation exists in the conversation record, updating the first target historical conversation based on the conversation establishment request message; the first target historical session is a historical session of which the session context comprises identity information of a target user carried by the session establishment request message.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (9)

1. A session management method, comprising:
judging whether a first target historical session exists in a session record or not based on a session establishment request message sent to a UPF entity by an SMF entity;
if judging that the session record contains a first target historical session, updating the first target historical session based on the session establishment request message;
the first target historical session is a historical session of which the session context includes the identity information of the target user carried by the session establishment request message.
2. The session management method according to claim 1, wherein after determining whether the first target historical session exists in the session record based on the session establishment request message sent by the SMF entity to the UPF entity, the method further comprises:
and if judging that the first target historical conversation does not exist in the conversation record, establishing a conversation corresponding to the target user, and updating the conversation corresponding to the target user based on the conversation establishment request message.
3. The session management method according to claim 1 or 2, wherein the method further comprises:
based on a session establishment response message which is returned to the SMF entity by the UPF entity and indicates that the response is successful, if judging that a second target historical session exists in a session record, updating the second target historical session based on the session establishment response message;
the second target historical session is a historical session of which the session context comprises a first target field carried by the session establishment response message; the first target field comprising: and the SMF entity allocates the identity to the UPF entity and the IP address of the SMF entity.
4. The session management method according to claim 3, wherein the method further comprises:
based on a session modification request message sent by the SMF entity to the UPF entity, if judging that a third target historical session exists in the session record, updating the third target historical session based on the session modification request message;
wherein, the third target history session is a history session whose session context includes a second target field carried by the session modification request message; the second target field comprising: and the UPF entity allocates the identity to the SMF entity and the IP address of the UPF entity.
5. The session management method according to claim 4, wherein the method further comprises:
based on a session modification response message which is returned to the SMF entity by the UPF entity and represents the successful response, if judging that a fourth target historical session exists, updating the fourth target historical session based on the session modification response message;
wherein the fourth target history session is a history session whose session context includes the first target field carried by the session modification response message.
6. The session management method according to claim 5, wherein the method further comprises:
based on a session deletion response message which is returned to the SMF entity by the UPF entity and represents that the response is successful, if judging that a fifth target historical session exists, deleting the fifth target historical session;
wherein the fifth target history session is a history session whose session context includes the first target field carried by the session deletion response message.
7. A session management apparatus, comprising:
the judging module is used for judging whether a first target historical session exists in the session record or not based on a session establishment request message sent to the UPF entity by the SMF entity;
the updating module is used for updating the first target historical session based on the session establishment request message if judging that the session record contains the first target historical session;
the first target historical session is a historical session of which the session context includes the identity information of the target user carried by the session establishment request message.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the session management method according to any of claims 1 to 6 are implemented when the processor executes the program.
9. A non-transitory computer readable storage medium, having stored thereon a computer program, when being executed by a processor, for implementing the steps of the session management method according to any one of claims 1 to 6.
CN202110467494.4A 2021-04-28 2021-04-28 Session management method and device Active CN113316269B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110467494.4A CN113316269B (en) 2021-04-28 2021-04-28 Session management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110467494.4A CN113316269B (en) 2021-04-28 2021-04-28 Session management method and device

Publications (2)

Publication Number Publication Date
CN113316269A true CN113316269A (en) 2021-08-27
CN113316269B CN113316269B (en) 2022-07-19

Family

ID=77371299

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110467494.4A Active CN113316269B (en) 2021-04-28 2021-04-28 Session management method and device

Country Status (1)

Country Link
CN (1) CN113316269B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114051047A (en) * 2021-10-29 2022-02-15 恒安嘉新（北京）科技股份公司 Backup method and device of session message, network equipment and storage medium
CN114244850A (en) * 2021-11-18 2022-03-25 深圳市领创星通科技有限公司 Data packet processing method and device, computer equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580324A (en) * 2017-09-22 2018-01-12 中国电子科技集团公司第三十研究所 A kind of method for GSM IMSI secret protections
CN108462735A (en) * 2017-02-21 2018-08-28 华为技术有限公司 A kind of methods, devices and systems of selection conversation management functional entity
CN109429362A (en) * 2017-06-20 2019-03-05 华为技术有限公司 Conversation processing method and device
US20190182876A1 (en) * 2016-08-23 2019-06-13 Huawei Technologies Co., Ltd. Session management method and device
CN111083718A (en) * 2018-10-22 2020-04-28 中国移动通信有限公司研究院 Session management method, network function and network system
CN111752717A (en) * 2020-07-08 2020-10-09 广州爱浦路网络技术有限公司 SMF intelligent expansion method and device and SMF session establishment communication method
US20210084713A1 (en) * 2018-02-15 2021-03-18 Telefonaktiebolaget Lm Ericsson (Publ) Method for providing a breakout pdu session for local ip access

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190182876A1 (en) * 2016-08-23 2019-06-13 Huawei Technologies Co., Ltd. Session management method and device
CN108462735A (en) * 2017-02-21 2018-08-28 华为技术有限公司 A kind of methods, devices and systems of selection conversation management functional entity
CN109429362A (en) * 2017-06-20 2019-03-05 华为技术有限公司 Conversation processing method and device
CN107580324A (en) * 2017-09-22 2018-01-12 中国电子科技集团公司第三十研究所 A kind of method for GSM IMSI secret protections
US20210084713A1 (en) * 2018-02-15 2021-03-18 Telefonaktiebolaget Lm Ericsson (Publ) Method for providing a breakout pdu session for local ip access
CN111083718A (en) * 2018-10-22 2020-04-28 中国移动通信有限公司研究院 Session management method, network function and network system
CN111752717A (en) * 2020-07-08 2020-10-09 广州爱浦路网络技术有限公司 SMF intelligent expansion method and device and SMF session establishment communication method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA等: "S2-165588 "Interim agreement for MMF-SMF split and Update of Solution 4.16 (Signalling layer integrity between MM and SM entities)"", 《3GPP TSG_SA\WG2_ARCH》 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114051047A (en) * 2021-10-29 2022-02-15 恒安嘉新（北京）科技股份公司 Backup method and device of session message, network equipment and storage medium
CN114051047B (en) * 2021-10-29 2023-06-09 恒安嘉新（北京）科技股份公司 Session message backup method and device, network equipment and storage medium
CN114244850A (en) * 2021-11-18 2022-03-25 深圳市领创星通科技有限公司 Data packet processing method and device, computer equipment and storage medium
CN114244850B (en) * 2021-11-18 2022-09-02 深圳市领创星通科技有限公司 Data packet processing method and device, computer equipment and storage medium

Also Published As

Publication number Publication date
CN113316269B (en) 2022-07-19

Similar Documents

Publication Publication Date Title
CN107172666B (en) Method and device for keeping local service of mobile terminal when switching communication cell
CN110139387B (en) Uplink small data transmission method, network side DU and network side CU
JP3686038B2 (en) Method and system for obtaining identification information about a party monitored in a communication network
CN113316269B (en) Session management method and device
CN116405461A (en) Data processing method, network element equipment and readable storage medium
CN109246762B (en) Local service distribution method and device
CN103249096B (en) A kind of switching handling method, equipment and system
CN111263407A (en) Data communication shunting method, device and system
CN114554550A (en) Communication method and device for 5G access network and edge cloud gateway
CN110167094B (en) Routing method, device, equipment, system and storage medium
EP3035770B1 (en) Call service implementation method and device
CN113038394B (en) Session binding relationship processing method and device, electronic equipment and readable medium
CN111405638B (en) Node N4-U tunnel selection method and device
CN107743316A (en) A kind of reminding method, mobile terminal and storage device for recovering network connection
CN114500237A (en) Communication method and system
CN103874240A (en) Signaling initiation method and apparatus, and gateway device
KR101567410B1 (en) call processing server
CN108307457B (en) Message routing method and device
CN105187236B (en) A kind of method of network flow migration
CN106161513B (en) Method and equipment for realizing rapid content distribution
CN112333788A (en) Session management method and device under N2 interface switching scene
CN102612099A (en) Re-establishment method and device of service bearer
CN114630355B (en) Fault recovery method, device, equipment and storage medium based on core network
CN108055200B (en) Data packet sending method, mobile router and network equipment
CN115209564B (en) Network slice matching method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant