CN108289306B - Flow conflict processing method and device - Google Patents

Flow conflict processing method and device Download PDF

Info

Publication number
CN108289306B
CN108289306B CN201710018520.9A CN201710018520A CN108289306B CN 108289306 B CN108289306 B CN 108289306B CN 201710018520 A CN201710018520 A CN 201710018520A CN 108289306 B CN108289306 B CN 108289306B
Authority
CN
China
Prior art keywords
user
processing
entity
cudb
user data
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.)
Active
Application number
CN201710018520.9A
Other languages
Chinese (zh)
Other versions
CN108289306A (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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201710018520.9A priority Critical patent/CN108289306B/en
Priority to PCT/CN2017/117484 priority patent/WO2018130053A1/en
Publication of CN108289306A publication Critical patent/CN108289306A/en
Application granted granted Critical
Publication of CN108289306B publication Critical patent/CN108289306B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a flow conflict processing method and a device, wherein the method comprises the following steps: when a public user database CUDB entity receives a request message for reading user data, judging whether a processing instance identifier of a user is stored locally; if the processing instance identification of the user is locally stored, and the stored processing instance identification of the user is inconsistent with the processing instance identification of the user in the user data reading request message, the CUDB entity determines that a flow conflict exists; and when the CUDB entity returns a read user data response message, carrying information indicating that the flow conflict exists and a processing instance identifier of the user stored in the CUDB entity in the read user data response message.

Description

Flow conflict processing method and device
Technical Field
The present invention relates to the field of mobile communications, and in particular, to a method and an apparatus for processing a flow conflict.
Background
Mobile communication has now progressed to the 4G stage. Compared with the previous generations, the network architecture of 4G is mainly characterized by being based on all-IP transmission. Fig. 1 is a 4G network architecture, where functions of network elements in the 4G network architecture are as follows:
a terminal (UE) is mainly accessed to a 4G network through a wireless air interface and obtains services, and the terminal exchanges information with a base station through the air interface and exchanges information with a Mobility Management Entity (MME) of a core network through a Non-Access Stratum signaling (NAS).
A base station (RAN, radio Access Network) is responsible for scheduling air interface resources of a terminal Access Network and managing connection of air interfaces.
A mobile management entity: the core network control plane entity is mainly responsible for authentication, authorization and subscription check of the user so as to ensure that the user is a legal user; user mobility management, including location registration and temporary identity allocation; maintaining IDLE (IDLE) and connected (CONNECT) states and state transitions; switching in a CONNECT state; maintenance of Packet Data Network (PDN) connection and bearer, including functions of session management such as creation, modification, and deletion; and triggering paging and other functions in the user IDLE state.
Serving gateway (SGW, serving GW): the core network user plane functional entity is mainly responsible for interaction with PDN GW under roaming condition; receiving a downlink data packet in a user IDLE state, caching and informing an MME (mobility management entity) to page a user; and the user plane anchor point crossing the base station, the user plane anchor point crossing the mobility of 2G/3G/4G and the like.
Packet Data gateway (PDN GW, packet Data network GW): the core network user plane functional entity is an access point of a terminal accessing a PDN network, is responsible for allocating a user IP address, establishing, modifying and deleting a network-triggered bearer, also has the functions of controlling charging and the like of Quality of Service (QoS), and is an anchor point for switching between a user in a 3GPP system and a non-3 GPP system, thereby ensuring the IP address to be unchanged and ensuring the Service continuity.
Since 4G mainly serves people and people, and as support for communication between objects and objects, the demand for mobile networks is more diverse and the mobile networks are more complex in the 5G era. The Function modularization and Network Function (NF) stateless processing can simplify the 5G Network and flexibly meet various requirements of the mobile Network. Network functions are stateless, requiring service processing to be separated from data, and using a distributed architecture with multiple instances of the same component.
Fig. 2 is a 5G network architecture with service processing and data separated, where the functions of network elements in the 5G network architecture are as follows:
common User Database (CUDB, centralized User Database): at a minimum, user dynamic data, such as mobile line management context, session context, user state, etc., is stored.
Control Plane function (CP): the system comprises a mobility management function (MM), a session management function (SM) and the like, and is mainly responsible for authentication, authorization and subscription check of a user so as to ensure that the user is a legal user; user mobility management, including location registration and temporary identifier allocation; maintaining IDLE and CONNECT states and state transitions; switching in the CONNECT state; the maintenance of Protocol Data Unit (PDU) session, including the functions of session management such as creation, modification and deletion; and triggering functions such as paging and the like in the IDLE state of the user.
User Plane function (UP, user Plane): the core network user plane functional entity is responsible for allocating user IP addresses and has the functions of QoS control charging and the like.
After the functions are modularized, the modules are arranged in a blueprint mode and the like to form network functions. The components in the network function can adopt a distributed architecture, and the same component has multiple instances. When the component for processing the user related signaling realizes the stateless processing, the component for processing the user signaling has multiple instances, the service processing is completely separated from the data, the signaling related to the user is received, the forwarding module of the network function selects one component instance for processing, and the component instance releases the user data after processing the user signaling message.
Fig. 3 is a scenario of a user PDU session setup and handover collision, where the CP may be composed of multiple network functions, each network function may be composed of multiple components, and each component may be a multiple instance.
In step 301, the ue initiates a session establishment request message to the CP, and the forwarding module in the CP selects instance 1 (CP 1) to process the message.
In step 302, cp1 sends a read user data request message to CUDB requesting all data of the user.
Step 303, the cudb returns a response message for reading the user data to the CP1, carrying the user data and status information.
In step 304, cp1 sends a setup user plane request message to UP.
In step 305, up returns a set up user plane response message to CP1.
In step 306, the cp1 sends a radio tunnel setup request message to the source Radio Access Network (RAN).
In step 307, the ran returns a radio tunnel setup response message to the CP1.
In step 308, cp1 sends an update user plane request message to UP.
In step 309, the source RAN determines to initiate handover, sends a handover request message to the CP, and the forwarding module in the CP selects instance 2 (CP 2) to process the message.
In step 310, cp2 sends a read user data request message to CUDB requesting all data of the user.
In step 311, the cudb returns a response message for reading the user data to the CP2, carrying the user data and status information.
In step 312, the cp2 does not obtain the information of the new session established by the user.
Step 313, the cp2 sends a handover request message to the target RAN, where the message carries session information.
In step 314, UP returns an update user plane response message to CP1.
In step 315, the target RAN returns a handover preparation failure message to the CP2 because the session information in the wireless transparent container is inconsistent with the session information sent by the core network.
In step 316, the cp2 returns a handover failure message to the source RAN.
In step 317, the CP1 returns a PDU session establishment response message to the UE.
In step 318, cp1 sends a write user data request message to CUDB to write the user data.
In step 319, the cudb returns a write user data response message to CP1.
In step 320, the cp1 deletes the local user context information.
It can be seen that in the PDU session establishment procedure, if there are other procedures of the user, different processing instances may be selected, resulting in unpredictable results, such as handover failure.
Disclosure of Invention
In order to solve the above technical problem, embodiments of the present invention provide a method and an apparatus for processing a flow conflict.
The method for processing the flow conflict provided by the embodiment of the invention comprises the following steps:
when the CUDB entity receives a request message for reading user data, judging whether a processing instance identifier of a user is stored locally;
if the processing instance identification of the user is locally stored, and the stored processing instance identification of the user is inconsistent with the processing instance identification of the user in the user data reading request message, the CUDB entity determines that a flow conflict exists;
and when the CUDB entity returns a read user data response message, the read user data response message carries information indicating that the process conflict exists and a processing instance identifier of the user stored in the CUDB entity.
In the embodiment of the present invention, the method further includes:
when the CUDB entity receives a user data reading request message sent by a network function entity by utilizing a first processing instance, judging whether a processing instance identifier of a user is stored locally;
and when the processing instance identification of the user is not stored locally, storing the processing instance identification of the first processing instance locally as the processing instance identification of the user.
In an embodiment of the present invention, the method further includes:
when the CUDB entity receives a user data reading request message sent by a network function entity by using a second processing instance, judging whether a processing instance identifier of a user is stored locally;
and if the processing instance identification of the user is locally stored and the stored processing instance identification of the user is the processing instance identification of the second processing instance, determining that the flow conflict exists.
In the embodiment of the present invention, the method further includes:
and when the CUDB entity receives a request for writing user data, deleting the processing instance identification of the user stored locally.
A method for processing a flow conflict according to another embodiment of the present invention includes:
when a network functional entity receives a user signaling, selecting a processing example for the user signaling and forwarding the user signaling to the processing example;
the processing example sends a user data reading request message to a CUDB entity and receives a user data reading response message sent by the CUDB entity;
and if the read user data response message carries information indicating that the process conflict exists, the processing instance forwards the user signaling to a processing instance corresponding to the processing instance identification of the user stored in the CUDB entity.
In this embodiment of the present invention, the sending, by the processing instance, a user data reading request message to the CUDB entity includes:
when a processing example receives a user signaling, judging whether the processing example has user data;
if there is no user data on this process instance, a read user data request message is sent to the CUDB.
In the embodiment of the present invention, the read user data response message further carries a processing instance identifier of the user stored in the CUDB entity.
In the embodiment of the present invention, the network function entity at least includes: a mobility management function entity and a session management function entity.
In this embodiment of the present invention, the processing example at least includes: any one of the mobility management function entities handles an instance of a component of the user signaling, and any one of the session management function entities handles an instance of a component of the user signaling.
The CUDB entity provided by the embodiment of the invention comprises:
the judging unit is used for judging whether the processing instance identification of the user is locally stored or not when receiving the user data reading request message;
a decision unit, configured to determine that a flow conflict exists if the processing instance identifier of the user is locally stored, and the stored processing instance identifier of the user is inconsistent with the processing instance identifier of the user in the user data read request message;
and the indicating unit is used for carrying information indicating that the process conflict exists and a processing example identifier of the user stored in the CUDB entity in the response message of the read user data when the response message of the read user data is returned.
In an embodiment of the present invention, the determining unit is specifically configured to: when a request message for reading user data sent by a network function entity by using a first processing instance is received, judging whether a processing instance identifier of a user is stored locally;
the CUDB entity further comprises: and the storage unit is used for storing the processing instance identifier of the first processing instance to the local as the processing instance identifier of the user when the processing instance identifier of the user is not stored locally.
In an embodiment of the present invention, the determining unit is specifically configured to: when a request message for reading user data sent by a network function entity by using a second processing instance is received, judging whether a processing instance identifier of a user is stored locally;
the decision unit is specifically configured to: and if the processing instance identification of the user is locally stored and the stored processing instance identification of the user is the processing instance identification of the second processing instance, determining that the flow conflict exists.
In an embodiment of the present invention, the CUDB entity further includes:
and the deleting unit is used for deleting the processing instance identification of the user stored locally when a request for writing the user data is received.
Another embodiment of the present invention provides a network function entity, including:
the forwarding unit is used for selecting a processing example for the user signaling and forwarding the user signaling to the processing example when the user signaling is received;
the interactive unit is used for sending a user data reading request message to the CUDB entity through the processing example and receiving a user data reading response message sent by the CUDB entity;
and a conflict processing unit, configured to forward, by the processing instance, the user signaling to a processing instance corresponding to the processing instance identifier of the user stored in the CUDB entity, if the read user data response message carries information indicating that a flow conflict exists.
In an embodiment of the present invention, the interaction unit is specifically configured to: when a processing example receives a user signaling, judging whether the processing example has user data; if there is no user data on this process instance, a read user data request message is sent to the CUDB.
In the embodiment of the present invention, the read user data response message further carries a processing instance identifier of the user stored in the CUDB entity.
In this embodiment of the present invention, the network function entity at least includes: a mobility management function entity and a session management function entity.
In this embodiment of the present invention, the processing example at least includes: any one of the mobility management function entities handles an instance of a component of the user signaling, and any one of the session management function entities handles an instance of a component of the user signaling.
In the technical scheme of the embodiment of the invention, when a network functional entity receives a request message, a processing example is selected for the request message; acquiring a processing instance identifier of a user from a unified data management CUDB entity by using the processing instance; the processing example judges whether the processing example identification of the user is consistent with the local processing example identification; and when the processing instance identification of the user is inconsistent with the local processing instance identification, forwarding the request message to the processing instance corresponding to the processing instance identification of the user for processing. By adopting the technical scheme of the embodiment of the invention, the same user can be ensured, only one processing example can process the signaling of the same user at the same time, and when the service flow conflicts, a proper flow conflict processing strategy can be adopted, so that the service experience of the user is improved.
Drawings
The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed herein.
FIG. 1 is an EPC network architecture diagram;
FIG. 2 is a diagram of a 5G network architecture with separation of traffic processing and data;
FIG. 3 is a scenario diagram of user PDU session establishment and handover conflicts for a 5G network architecture based on traffic handling and data separation;
FIG. 4 is a flowchart of a scenario of user PDU session establishment and handover conflicts in accordance with an embodiment of the present invention;
FIG. 5 is a flow diagram of a user PDU session establishment and location update scenario according to an embodiment of the present invention;
FIG. 6 is a flowchart of a scenario of a network-side triggered PDU session establishment and handover conflict according to an embodiment of the present invention;
fig. 7 is a first flowchart of a method for processing a flow conflict according to an embodiment of the present invention;
FIG. 8 is a second flowchart illustrating a method for processing a flow conflict according to an embodiment of the present invention;
FIG. 9 is a diagram illustrating the structural components of a CUDB entity according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a network functional entity according to an embodiment of the present invention.
Detailed Description
So that the manner in which the features and technical contents of the embodiments of the present invention can be understood in detail, a detailed description of the embodiments of the present invention will be given below with reference to the accompanying drawings.
In the network function of stateless processing, a plurality of processes may be performed simultaneously by the same user, and the plurality of processes are processed on different processing instances, so that the processing instances cannot detect the conflict and cannot adopt an appropriate processing strategy.
Based on this, the embodiment of the present invention provides a flow conflict processing method, where a flow conflict detection module is added in the CUDB to detect whether a user has a flow conflict. The processing example of the network function of the stateless processing receives the signaling of the user, when the processing example (the new processing example) reads the user data from the CUDB, if the CUDB detects that the user has a flow conflict, and returns the user data to the processing example, the processing example indicates the flow conflict of the network function and indicates the old processing example identifier. When receiving a user data response, the new processing instance determines that a flow conflict exists, and forwards a user signaling to a processing instance corresponding to an old processing instance identifier carried by a response message, namely the same user, and only one processing instance processes the signaling of the same user at the same time, so that the processing instance can adopt a proper processing strategy to process the flow conflict, and the flow success rate is improved.
Fig. 7 is a first schematic flowchart of a method for processing a flow conflict according to an embodiment of the present invention, and as shown in fig. 7, the method includes:
step 701: when the CUDB entity receives the user data reading request message, whether the processing instance identification of the user is stored locally is judged.
In the embodiment of the present invention, the method further includes:
when the CUDB entity receives a user data reading request message sent by a network function entity by utilizing a first processing instance, judging whether a processing instance identifier of a user is stored locally;
and when the processing instance identification of the user is not stored locally, storing the processing instance identification of the first processing instance locally as the processing instance identification of the user.
Step 702: and if the processing instance identification of the user is locally stored and the stored processing instance identification of the user is not consistent with the processing instance identification of the user in the user data reading request message, the CUDB entity determines that the flow conflict exists.
Specifically, when receiving a user data reading request message sent by a network function entity by using a second processing instance, the CUDB entity determines whether to locally store a processing instance identifier of a user;
and if the processing instance identification of the user is locally stored and the stored processing instance identification of the user is the processing instance identification of the second processing instance, determining that the flow conflict exists.
Step 703: and when the CUDB entity returns a read user data response message, carrying information indicating that the flow conflict exists and a processing instance identifier of the user stored in the CUDB entity in the read user data response message.
In the embodiment of the invention, when the CUDB entity receives a request for writing user data, the locally stored processing instance identifier of the user is deleted.
In the technical scheme of the embodiment of the invention, a flow conflict detection module is added in the CUDB and is used for detecting whether a user has flow conflicts. For each user, the CUDB may maintain process instance identification information that is processing the user signaling. When the CUDB receives a user data reading request message of the user, if the CUDB finds that the processing instance identification information of the user is not stored in the CUDB, the CUDB stores the processing instance identification of the processing instance sending the request message. When the CUDB receives the user data writing request message, the CUDB clears the processing example identification information of the user stored in the CUDB. If the CUDB stores the processing instance identification information of the user and receives the user data reading request message of the user, the processing instance identification in the new user data reading request message is not stored. When the CUDB receives the user data reading request message, if the processing instance identification of the user is stored, and the stored processing instance identification of the user is inconsistent with the processing instance identification of the user in the received user data reading request message, the CUDB determines that the user has a flow conflict, and carries information indicating that the flow conflict exists and the processing instance identification information of the user stored in the CUDB in the returned user data reading response message.
Fig. 8 is a second flowchart of a flow conflict processing method according to an embodiment of the present invention, and as shown in fig. 8, the method includes:
step 801: when receiving user signaling, the network function entity selects a processing instance for the user signaling and forwards the user signaling to the processing instance.
Step 802: and the processing example sends a user data reading request message to the CUDB entity and receives a user data reading response message sent by the CUDB entity.
Specifically, when a processing instance receives a user signaling, whether the processing instance has user data is judged;
if there is no user's data on this process instance, a read user data request message is sent to the CUDB.
In the embodiment of the present invention, the read user data response message further carries a processing instance identifier of the user stored in the CUDB entity.
Step 803: and if the read user data response message carries information indicating that the process conflict exists, the processing instance forwards the user signaling to a processing instance corresponding to the processing instance identification of the user stored in the CUDB entity.
In the embodiment of the present invention, the network function entity at least includes: a mobility management function entity and a session management function entity. In addition, other network functional entities capable of processing user signaling are also included.
In this embodiment of the present invention, the processing example at least includes: any one of the mobility management function entities processes the instance of the component of the user signaling, and any one of the session management function entities processes the instance of the component of the user signaling. In addition, the embodiment also includes an example of any one of other network functional entities which can process the user signaling and process the user signaling.
In the technical scheme of the embodiment of the invention, the network function of the stateless processing receives the signaling of the user, the forwarding module of the network function forwards the user signaling to the processing example of the user, and the processing example forwards the user signaling to the processing example corresponding to the user example processing identifier stored in the CUDB after receiving the information indicating that the flow conflict exists in the CUDB. The user processing example receives the user signaling, and sends a user data reading request message to the CUDB when the user data does not exist on the processing example. When the processing instance of the user receives the response message of reading the user data returned by the CUDB, if the message is found to carry the information indicating that the flow conflict exists, the processing instance of the user forwards the user signaling to the processing instance corresponding to the instance processing identification information stored in the CUDB carried in the response message of reading the user data.
The following describes the scheme of the embodiment of the present invention in further detail with reference to specific application scenarios.
The first embodiment is as follows: one embodiment of a scenario for user PDU session setup and handover collision is shown in fig. 4.
In step 401, the ue initiates a session establishment request message to the CP, and the forwarding module in the CP selects instance 1 (CP 1) to process the message.
In step 402, cp1 sends a read user data request message to CUDB requesting all data of the user.
In step 403, the CUDB stores the CP1 identification.
And step 404, the process conflict detection module of the CUDB detects that no process conflict exists, and returns a read user data response message to the CP1, wherein the read user data response message carries user data.
In step 405, CP1 sends a set UP user plane request message to the UP.
In step 406, UP returns a set up user plane response message to CP1.
In step 407, the cp1 sends a radio tunnel setup request message to the RAN.
In step 408, the ran returns a radio tunnel setup response message to CP1.
In step 409, cp1 sends an update user plane request message to UP.
In step 410, the source RAN decides to initiate a handover, sends a handover required message to the CP, and the forwarding module in the CP selects instance 2 (CP 2) to process the message.
In step 411, the cp2 sends a read user data request message to the CUDB requesting all data of the user.
In step 412, the process conflict detection module of the cudb determines that the processing instance identification information (the identification of CP 1) stored by the user is inconsistent with the processing instance identification (the identification of CP 2) of the sending end of the received user data reading request, and then determines that a process conflict exists.
In step 413, CUDB returns a read user data response message to CP2, carrying information indicating that there is a flow conflict, and carrying processing instance identification information (identification of CP 1) of the user saved in CUDB.
And step 414, the CP2 forwards the switching requirement message to the CP1 according to the information indicating that the flow conflict exists in the read user data response message.
In step 415, the cp1 receives the handover required message and detects that the user is still performing the session establishment procedure, and may adopt an appropriate processing strategy, such as suspending the PDU session establishment procedure and then processing the handover.
In step 416, the cp1 sends a handover request message to the RAN, where the message carries session information (including newly established session information).
In step 417, up returns an update user plane response message to CP1.
In step 418, the cp1 continues to process the handover message until the handover procedure is finished.
In step 419, cp1 detects that the PDU session establishment procedure is not completed for the user, and continues to process the PDU session establishment procedure.
In step 420, the cp1 returns a PDU session setup response message to the UE.
In step 421, cp1 sends a write user data request message to the CUDB to write the user data.
In step 422, the CUDB clears the user process instance identification information.
In step 423, the cudb returns a write user data response message to CP1.
Step 424, cp1 deletes the local user context information.
The second embodiment: one embodiment of a user PDU session setup and location update scenario is shown in figure 5.
Step 501, UE initiates a session establishment request message to CP, and the forwarding module in CP selects instance 1 (CP 1) to process the message.
In step 502, cp1 sends a read user data request message to CUDB requesting all data of the user.
In step 503, the CUDB stores the CP1 identification.
And step 504, the CUDB flow conflict detection module detects that no flow conflict exists, and returns a user data reading response message to the CP1, wherein the user data is carried by the user data.
In step 505, CP1 sends a set UP user plane request message to the UP.
In step 506, UP returns a set up user plane response message to CP1.
In step 507, the cp1 transmits a radio tunnel setup request message to the RAN.
In step 508, the ran returns a radio tunnel setup response message to CP1.
In step 509, cp1 sends an update user plane request message to the UP.
Step 510, due to the reason of moving, the UE initiates a location update request message to the CP, and the forwarding module in the CP selects instance 2 (CP 2) to process the message.
In step 511, the cp2 sends a read user data request message to the CUDB to request all data of the user.
In step 512, the process conflict detection module of the cudb determines that the processing instance identification information (the identification of CP 1) stored by the user is inconsistent with the processing instance identification (the identification of CP 2) of the sending end of the received user data reading request, and then determines that a process conflict exists.
In step 513, the CUDB returns a read user data response message to the CP2, carrying information indicating that there is a flow conflict, and carrying processing instance identification information (identification of CP 1) of the user stored in the CUDB.
Step 514, the cp2 forwards the location update request message to the CP1 according to the information indicating that the flow conflict exists in the read user data response message.
In step 515, the cp1 receives the location update request message and detects that the user is still performing the session establishment procedure, and may adopt an appropriate processing strategy, such as ending the PDU session establishment procedure and then processing the location update request message.
In step 516, cp1 sends a delete user plane request message to UP, informs UP to delete the PDU session being created, and sends a radio tunnel delete request message to RAN.
In step 517, cp1 starts processing the location update request message.
In step 518, UP returns an update user plane response message to CP1.
In step 519, the ran returns a radio tunnel deletion response message to the CP1.
In step 520, the cp1 continues to process the location update message until the location update procedure is finished.
In step 521, the cp1 sends a write user data request message to the CUDB, writing the user data.
Step 522, CUDB clears the user process instance identification information.
Step 523, cudb returns a write user data response message to CP1.
In step 524, cp1 deletes the local user context information.
Example three: one embodiment of a scenario where handover and network side triggered PDU session setup collisions is illustrated in fig. 6.
Step 601, the source RAN decides to initiate handover, sends a handover required message to the CP, and the forwarding module in the CP selects instance 2 (CP 2) to process the message.
Step 602, cp2 sends a read user data request message to CUDB requesting all data of the user.
Step 603, CUDB saves the CP2 identification.
And step 604, the CUDB flow conflict detection module detects that no flow conflict exists, and returns a user data reading response message to the CP2, wherein the user data is carried by the user data.
In step 605, the cp2 sends a handover request message to the RAN.
Step 606, as there is downlink data of UE to be sent but there is no corresponding PDU session, SCEF or other network element sends a network side session establishment request message to CP, and the forwarding module in CP selects instance 1 (CP 1) to process the message.
In step 607, cp1 sends a read user data request message to CUDB requesting all data of the user.
In step 608, the process conflict detection module of the cudb determines that the processing instance identification information (identification of CP 2) stored by the user is inconsistent with the processing instance identification (identification of CP 1) of the sending end of the received user data reading request, and then determines that a process conflict exists.
In step 609, CUDB returns a read user data response message to CP1, carrying information indicating that there is a flow conflict, and carrying processing instance identification information (identification of CP 2) of the user stored in CUDB.
In step 610, the CP1 forwards the session establishment request message to the CP2 according to the information indicating the existence of the flow conflict in the read user data response message.
In step 611, the cp2 receives the network side session establishment request message, and detects that the user is still performing the handover process, and may adopt an appropriate processing policy, such as continuing the handover, to cache the network side session establishment request message.
In step 612, cp2 continues to process the handover message until the handover procedure process is finished.
In step 613, the cp2 detects that the user still has the buffered PDU network side session establishment request message not processed, and continues to process the buffered network side session establishment request message.
In step 614, the cp2 processes the session establishment procedure on the network side until the session establishment procedure on the network side is finished.
Step 615, CP2 sends a write user data request message to the CUDB, writing the user data.
At step 616, the CUDB clears the user process instance identification information.
Step 617, the cudb returns a write user data response message to CP2.
Step 618, the cp2 deletes the local user context information.
Fig. 9 is a schematic structural component diagram of a CUDB entity according to an embodiment of the present invention, where as shown in fig. 9, the CUDB entity includes:
a determining unit 91, configured to determine whether to store a processing instance identifier of a user locally when receiving a user data reading request message;
a decision unit 92, configured to determine that a flow conflict exists if the processing instance identifier of the user is locally stored, and the stored processing instance identifier of the user is inconsistent with the processing instance identifier of the user in the user data reading request message;
an indicating unit 93, configured to, when a read user data response message is returned, carry information indicating that a process conflict exists and a processing instance identifier of a user stored in a CUDB entity in the read user data response message.
In this embodiment of the present invention, the determining unit 91 is specifically configured to: when a request message for reading user data sent by a network functional entity by using a first processing instance is received, judging whether a processing instance identifier of a user is locally stored;
the CUDB entity further comprises: the storage unit 94 is configured to, when the processing instance identifier of the user is not locally stored, store the processing instance identifier of the first processing instance to the local as the processing instance identifier of the user.
In this embodiment of the present invention, the determining unit 91 is specifically configured to: when a request message for reading user data sent by a network function entity by using a second processing instance is received, judging whether a processing instance identifier of a user is stored locally;
the decision unit is specifically configured to: and if the processing instance identification of the user is locally stored and the stored processing instance identification of the user is the processing instance identification of the second processing instance, determining that the flow conflict exists.
In an embodiment of the present invention, the CUDB entity further includes:
a deleting unit 95, configured to delete the locally stored processing instance identifier of the user when the write user data request is received.
Fig. 10 is a schematic structural diagram of a network functional entity according to an embodiment of the present invention, and as shown in fig. 10, the network functional entity includes:
a forwarding unit 1001, configured to select a processing instance for a user signaling when receiving the user signaling, and forward the user signaling to the processing instance;
an interaction unit 1002, configured to send a user data reading request message to a CUDB entity through the process instance, and receive a user data reading response message sent by the CUDB entity;
a conflict processing unit 1003, configured to, if the read user data response message carries information indicating that a process conflict exists, forward the user signaling to a processing instance corresponding to the processing instance identifier of the user stored in the CUDB entity by the processing instance.
In this embodiment of the present invention, the interaction unit 1002 is specifically configured to: when a processing example receives a user signaling, judging whether the processing example has user data; if there is no user's data on this process instance, a read user data request message is sent to the CUDB.
In the embodiment of the present invention, the read user data response message further carries a processing instance identifier of the user stored in the CUDB entity.
In this embodiment of the present invention, the network function entity at least includes: a mobility management function entity and a session management function entity.
In this embodiment of the present invention, the processing example at least includes: any one of the mobility management function entities handles an instance of a component of the user signaling, and any one of the session management function entities handles an instance of a component of the user signaling.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims (18)

1. A flow conflict processing method, the method comprising:
when the CUDB entity receives a request message for reading user data, judging whether a processing instance identifier of a user is stored locally;
if the processing instance identification of the user is locally stored, and the stored processing instance identification of the user is inconsistent with the processing instance identification of the user in the user data reading request message, the CUDB entity determines that a flow conflict exists;
and when the CUDB entity returns a read user data response message, carrying information indicating that the flow conflict exists and a processing instance identifier of the user stored in the CUDB entity in the read user data response message.
2. The method for processing flow conflict according to claim 1, further comprising:
when the CUDB entity receives a user data reading request message sent by a network function entity by utilizing a first processing instance, judging whether a processing instance identifier of a user is stored locally;
and when the processing instance identification of the user is not stored locally, storing the processing instance identification of the first processing instance locally as the processing instance identification of the user.
3. The flow conflict processing method according to claim 2, further comprising:
when the CUDB entity receives a user data reading request message sent by a network function entity by using a second processing instance, judging whether a processing instance identifier of a user is stored locally;
and if the processing instance identification of the user is locally stored and the stored processing instance identification of the user is the processing instance identification of the second processing instance, determining that the flow conflict exists.
4. The flow conflict processing method according to any one of claims 1 to 3, wherein the method further comprises:
and when the CUDB entity receives a request for writing user data, deleting the locally stored processing instance identification of the user.
5. A method for processing flow conflict, the method comprising:
when a network functional entity receives a user signaling, selecting a processing example for the user signaling and forwarding the user signaling to the processing example;
the processing example sends a user data reading request message to a CUDB entity and receives a user data reading response message sent by the CUDB entity;
and if the read user data response message carries information indicating that the flow conflict exists, the processing instance forwards the user signaling to a processing instance corresponding to the processing instance identifier of the user stored in the CUDB entity.
6. The process conflict handling method of claim 5, wherein the process instance sends a read user data request message to the CUDB entity, comprising:
when a processing example receives a user signaling, judging whether the processing example has user data;
if there is no user data on this process instance, a read user data request message is sent to the CUDB.
7. The process conflict handling method according to claim 5, wherein the read user data response message further carries a handling instance id of the user stored in the CUDB entity.
8. The flow conflict processing method according to any one of claims 5 to 7, wherein the network function entity at least comprises: a mobility management function entity and a session management function entity.
9. The method for processing flow conflict according to any one of claims 5 to 7, wherein the processing instance at least comprises: any one of the mobility management function entities handles an instance of a component of the user signaling, and any one of the session management function entities handles an instance of a component of the user signaling.
10. A CUDB entity, wherein the CUDB entity comprises:
the judging unit is used for judging whether the processing instance identification of the user is locally stored or not when receiving the user data reading request message;
a decision unit, configured to determine that a flow conflict exists if the processing instance identifier of the user is locally stored, and the stored processing instance identifier of the user is inconsistent with the processing instance identifier of the user in the user data read request message;
and the indicating unit is used for carrying information indicating that the flow conflict exists and the processing instance identifier of the user stored in the CUDB entity in the read user data response message when the read user data response message is returned.
11. The CUDB entity of claim 10, wherein the determining unit is specifically configured to: when a request message for reading user data sent by a network function entity by using a first processing instance is received, judging whether a processing instance identifier of a user is stored locally;
the CUDB entity further comprises: and the storage unit is used for storing the processing instance identification of the first processing instance to the local as the processing instance identification of the user when the processing instance identification of the user is not stored locally.
12. The CUDB entity of claim 11, wherein the determining unit is specifically configured to: when a request message for reading user data sent by a network function entity by using a second processing instance is received, judging whether a processing instance identifier of a user is stored locally;
the decision unit is specifically configured to: and if the processing instance identification of the user is locally stored and the stored processing instance identification of the user is the processing instance identification of the second processing instance, determining that the flow conflict exists.
13. The CUDB entity according to any one of claims 10-12, wherein the CUDB entity further comprises:
and the deleting unit is used for deleting the processing instance identification of the locally stored user when the request for writing the user data is received.
14. A network function entity, characterized in that the network function entity comprises:
the forwarding unit is used for selecting a processing example for the user signaling and forwarding the user signaling to the processing example when the user signaling is received;
the interactive unit is used for sending a user data reading request message to the CUDB entity through the processing example and receiving a user data reading response message sent by the CUDB entity;
and a conflict processing unit, configured to forward, by the processing instance, the user signaling to a processing instance corresponding to the processing instance identifier of the user stored in the CUDB entity, if the read user data response message carries information indicating that a flow conflict exists.
15. The network functional entity of claim 14, wherein the interaction unit is specifically configured to: when a processing example receives a user signaling, judging whether the processing example has user data; if there is no user data on this process instance, a read user data request message is sent to the CUDB.
16. The network function entity of claim 14, wherein the read user data response message further carries an identity of the processing instance of the user stored in the CUDB entity.
17. Network function entity according to any of claims 14 to 16, characterized in that the network function entity comprises at least: a mobility management function entity and a session management function entity.
18. The network functional entity according to any of claims 14 to 16, wherein the processing instance comprises at least: any one of the mobility management function entities handles an instance of a component of the user signaling, and any one of the session management function entities handles an instance of a component of the user signaling.
CN201710018520.9A 2017-01-10 2017-01-10 Flow conflict processing method and device Active CN108289306B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710018520.9A CN108289306B (en) 2017-01-10 2017-01-10 Flow conflict processing method and device
PCT/CN2017/117484 WO2018130053A1 (en) 2017-01-10 2017-12-20 Flow conflict processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710018520.9A CN108289306B (en) 2017-01-10 2017-01-10 Flow conflict processing method and device

Publications (2)

Publication Number Publication Date
CN108289306A CN108289306A (en) 2018-07-17
CN108289306B true CN108289306B (en) 2023-03-10

Family

ID=62831446

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710018520.9A Active CN108289306B (en) 2017-01-10 2017-01-10 Flow conflict processing method and device

Country Status (2)

Country Link
CN (1) CN108289306B (en)
WO (1) WO2018130053A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11039369B2 (en) * 2018-08-10 2021-06-15 Mediatek Inc. Handling 5G QoS rules on QoS operation errors
US20200113009A1 (en) * 2018-10-06 2020-04-09 Mediatek Inc. Handling Of Invalid Mandatory Information In Mobile Communications
CN115442853A (en) * 2021-06-04 2022-12-06 华为技术有限公司 Wireless communication method and device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102148689A (en) * 2010-02-09 2011-08-10 中兴通讯股份有限公司 Policy and charging rules function entity selection method, device and system
CN102834823A (en) * 2010-02-11 2012-12-19 瑞典爱立信有限公司 Data management at a directory database
CN103402187A (en) * 2013-07-08 2013-11-20 大唐移动通信设备有限公司 Procedure processing method and device for downlink signaling messages
CN104769555A (en) * 2012-06-18 2015-07-08 艾克特菲欧有限公司 Enhanced data management virtualization system
CN105075225A (en) * 2012-12-24 2015-11-18 瑞典爱立信有限公司 Enabling external access to multiple services on a local server
WO2016026535A1 (en) * 2014-08-22 2016-02-25 Telefonaktiebolaget Lm Ericsson (Publ) A method, system and device for accessing data storage in a telecommunications network.

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102148689A (en) * 2010-02-09 2011-08-10 中兴通讯股份有限公司 Policy and charging rules function entity selection method, device and system
CN102834823A (en) * 2010-02-11 2012-12-19 瑞典爱立信有限公司 Data management at a directory database
CN104769555A (en) * 2012-06-18 2015-07-08 艾克特菲欧有限公司 Enhanced data management virtualization system
CN105075225A (en) * 2012-12-24 2015-11-18 瑞典爱立信有限公司 Enabling external access to multiple services on a local server
CN103402187A (en) * 2013-07-08 2013-11-20 大唐移动通信设备有限公司 Procedure processing method and device for downlink signaling messages
WO2016026535A1 (en) * 2014-08-22 2016-02-25 Telefonaktiebolaget Lm Ericsson (Publ) A method, system and device for accessing data storage in a telecommunications network.

Also Published As

Publication number Publication date
WO2018130053A1 (en) 2018-07-19
CN108289306A (en) 2018-07-17

Similar Documents

Publication Publication Date Title
CN108632915B (en) Method, device and equipment for moving terminal between 4G network and 5G network
US11706702B2 (en) Network entity, user equipment and method for the control and use of network slices
CN109600802B (en) Data transmission method, related equipment and system
CN109429370B (en) Information processing method and device
CN116406002A (en) Paging of wireless devices over a wireless network
US11297542B2 (en) Base station handover method, system, and computer storage medium
CN108419270A (en) A kind of service distributing implementation method and device
WO2019033796A1 (en) Session processing method and related device
CN101001252A (en) Registration method and consultation method and device of user safety algorithmic
CN101677470A (en) Processing method, device and system of service request
WO2018059401A1 (en) Network switching method, device and system, and network access method and device
US20210014720A1 (en) Relocation Method and Apparatus
CN101572862B (en) Method and equipment for supporting intercommunication between 3G system and LTE system
CN108289306B (en) Flow conflict processing method and device
CN113796156B (en) Communication network component and method for processing service requests
US8718640B2 (en) Method for triggering roaming retry and a home location register
CN105101311B (en) Bearer switching method, equipment and system
CN107277882B (en) Data routing method, device and base station
CN101527935B (en) Processing method and device in scheduling of resources
CN108307454B (en) Network switching method and device
CN108616978B (en) Method and device for performing stateless processing on network function entity
CN108476384B (en) Data transmission method and related device
CN103067849B (en) A kind ofly to stop using, the method and apparatus of multiplexing gprs service
CN108260097B (en) Method for solving roaming charging error during eSRVCC switching and eMSC
CN111417167B (en) Method and device for supporting edge calculation when user moves

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