WO2018130053A1 - 一种流程冲突处理方法及装置 - Google Patents

一种流程冲突处理方法及装置 Download PDF

Info

Publication number
WO2018130053A1
WO2018130053A1 PCT/CN2017/117484 CN2017117484W WO2018130053A1 WO 2018130053 A1 WO2018130053 A1 WO 2018130053A1 CN 2017117484 W CN2017117484 W CN 2017117484W WO 2018130053 A1 WO2018130053 A1 WO 2018130053A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
processing
processing instance
cudb
entity
Prior art date
Application number
PCT/CN2017/117484
Other languages
English (en)
French (fr)
Inventor
刘合伦
涂小勇
郑芳庭
蒋栋栋
翟义强
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018130053A1 publication Critical patent/WO2018130053A1/zh

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

Definitions

  • This document relates to, but is not limited to, the field of mobile communications, and in particular, to a process conflict processing method and apparatus.
  • Figure 1 is a 4G network architecture.
  • the functions of each network element in the 4G network architecture are as follows:
  • the terminal accesses the 4G network through the wireless air interface and obtains the service.
  • the terminal exchanges information through the air interface and the base station, and performs mobility management through the non-access stratum signaling (NAS, Non-Access Stratum) and the core network.
  • Entity Mobility Management Entity
  • the base station (RAN, Radio Access Network) is responsible for the air interface resource scheduling of the terminal accessing the network and the connection management of the air interface.
  • Mobile management entity The core network control plane entity is mainly responsible for authentication, authorization and contract checking of users to ensure that users are legitimate users; user mobility management, including location registration and temporary identity allocation; maintenance idle (IDLE) and connection (CONNECT) state and state transition; switching in CONNECT state; packet data network (PDN) connection and bearer maintenance, including session management functions such as creation, modification, and deletion; triggering paging in user IDLE state And other functions.
  • user mobility management including location registration and temporary identity allocation
  • maintenance idle (IDLE) and connection (CONNECT) state and state transition switching in CONNECT state
  • PDN packet data network
  • bearer maintenance including session management functions such as creation, modification, and deletion
  • session management functions such as creation, modification, and deletion
  • triggering paging in user IDLE state And other functions.
  • SGW Service Gateway
  • Serving GW The core network user plane function entity, which is mainly responsible for the interaction with the PDN GW in the case of roaming; receiving the downlink data packet for buffering in the IDLE state and notifying the MME to page the user; Anchor points and user plane anchors across 2G/3G/4G mobility.
  • GWN GW Packet Data Network
  • An entity is an access point for a terminal to access a PDN network. It is responsible for allocating user IP addresses, establishing, modifying, and deleting bearers triggered by the network. It also has functions such as quality of service (QoS) control and accounting.
  • QoS quality of service
  • An anchor point for switching between the 3GPP system and the non-3GPP system, thereby ensuring that the IP address is unchanged and ensuring business continuity.
  • FIG. 2 is a 5G network architecture for service processing and data separation.
  • the functions of each network element in the 5G network architecture are as follows:
  • CUDB Stores at least user dynamic data, such as mobile line management context, session context, user status, and so on.
  • Control Plane including mobility management function (MM) and session management function (SM), etc., mainly responsible for authentication, authorization, and subscription checking of users to ensure that users are legitimate users; user mobility Management, including location registration and temporary identity assignment; maintenance of IDLE and CONNECT status and state transition; handover in CONNECT state; maintenance of protocol data unit (PDU) session, including session management of creation, modification and deletion Function; triggers paging and other functions in the IDLE state.
  • CM mobility management function
  • SM session management function
  • User Plane The core network user plane function entity, which is responsible for assigning user IP addresses and having QoS control and accounting functions.
  • the components are arranged by blueprints and the like to form a network function.
  • the components in the network function can adopt a distributed architecture and multiple instances of the same component.
  • the component processing user-related signaling implements stateless processing
  • the component that processes the signaling of the user is multi-instance
  • the service processing is completely separated from the data
  • the signaling related to the user is received
  • the forwarding function of the network function selects a component instance for processing. After the component instance processes the user signaling message, the user data is released.
  • Embodiments of the present invention provide a process conflict processing method and apparatus.
  • the CUDB entity determines whether the local processing instance identifier is stored locally;
  • the CUDB entity determines that there is a process conflict
  • the read user data response message carries information indicating that there is a process conflict and a processing instance identifier of the user saved in the CUDB entity.
  • the method further includes:
  • the CUDB entity When the CUDB entity receives the read user data request message sent by the network function entity by using the first processing instance, it determines whether the processing instance identifier of the user is stored locally;
  • the processing instance identifier of the user is not stored locally, the processing instance identifier of the first processing instance is stored locally as the processing instance identifier of the user.
  • the method further includes:
  • the CUDB entity When the CUDB entity receives the read user data request message sent by the network function entity by using the second processing instance, it determines whether the processing instance identifier of the user is stored locally;
  • processing instance identifier of the user is stored locally, and the processing instance identifier of the stored user is the processing instance identifier of the second processing instance, it is determined that there is a process conflict.
  • the method further includes:
  • the CUDB entity When the CUDB entity receives the write user data request, the locally stored user's processing instance identifier is deleted.
  • the processing instance When the network function entity receives the user signaling, the processing instance is selected for the user signaling and Transmitting the user signaling to the processing instance;
  • the processing instance sends a read user data request message to the CUDB entity, and receives a read user data response message sent by the CUDB entity;
  • the processing instance forwards the user signaling to a processing instance corresponding to the processing instance identifier of the user saved in the CUDB entity.
  • the processing instance sends a read user data request message to the CUDB entity, including:
  • the processing instance When the processing instance receives the user signaling, it is determined whether the user has data on the processing instance;
  • a read user data request message is sent to the CUDB.
  • the read user data response message further carries a processing instance identifier of the user saved in the CUDB entity.
  • the network function entity includes: a mobility management function entity and a session management function entity.
  • the processing example includes: an instance of any one of a component of the mobility management function entity that processes user signaling, and an instance of a component of the session management function entity that processes user signaling.
  • the determining unit is configured to: when receiving the read user data request message, determine whether the local processing instance identifier is stored locally;
  • a decision unit configured to determine that there is a process conflict if the processing instance identifier of the user is stored locally, and the processing instance identifier of the stored user is inconsistent with the processing instance identifier of the user in the read user data request message;
  • the indicating unit configured to return the read user data response message, carries the information indicating that there is a process conflict and the processing instance identifier of the user saved in the CUDB entity in the read user data response message.
  • the determining unit is configured to: when receiving the read user data request message sent by the network function entity by using the first processing instance, determine whether the local processing instance identifier of the user is stored;
  • the device further includes: a storage unit, configured to store 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.
  • a storage unit configured to store 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.
  • the determining unit is configured to: when receiving the read user data request message sent by the network function entity by using the second processing instance, determine whether the local processing instance identifier of the user is stored;
  • the determining unit is configured to: if the processing instance identifier of the user is stored locally, and the processing instance identifier of the stored user is the processing instance identifier of the second processing instance, it is determined that there is a process conflict.
  • the device further includes:
  • the delete unit is set to delete the processing instance identifier of the locally stored user when receiving the write user data request.
  • a forwarding unit configured to: when receiving user signaling, select a processing instance for the user signaling and forward the user signaling to the processing instance;
  • An interaction unit configured to send a read user data request message to the CUDB entity by using the processing instance, and receive a read user data response message sent by the CUDB entity;
  • a conflict processing unit configured to: if the read user data response message carries information indicating that there is a process conflict, the processing instance forwards the user signaling to a processing instance identifier of a user saved in the CUDB entity Processing example.
  • the interaction unit is configured to: when the processing instance receives the user signaling, determine whether the user has data of the user; if there is no user data on the processing instance, send the data to the CUDB. Read the user data request message.
  • the read user data response message further carries a processing instance identifier of the user saved in the CUDB entity.
  • the network function entity includes: a mobility management function entity and a session management function entity.
  • the processing example includes: an instance of any one of a component of the mobility management function entity that processes user signaling, and an instance of a component of the session management function entity that processes user signaling.
  • the network function entity selects a processing instance for the request message when receiving the request message, and obtains the processing instance identifier of the user from the unified data management CUDB entity by using the processing instance; Whether the processing instance identifier of the user is consistent with the local processing instance identifier; when the processing instance identifier of the user is inconsistent with the local processing instance identifier, the request message is forwarded to the processing instance corresponding to the processing instance identifier of the user. deal with.
  • the same user can be ensured that only one processing instance can process the signaling of the same user at the same time.
  • an appropriate process conflict processing policy can be adopted to improve the user service experience.
  • Figure 1 is a 4G network architecture diagram
  • 2 is a 5G network architecture diagram of service processing and data separation
  • 3 is a scenario diagram of user PDU session establishment and handover conflicts of a 5G network architecture based on service processing and data separation;
  • FIG. 4 is a flowchart of a scenario in which a user PDU session establishment and handover conflict occurs according to an embodiment of the present invention
  • FIG. 5 is a flowchart 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 PDU session establishment and handover conflict triggered by a network side according to an embodiment of the present invention
  • FIG. 7 is a schematic flowchart 1 of a process conflict processing method according to an embodiment of the present invention.
  • FIG. 8 is a second schematic flowchart of a process conflict processing method according to an embodiment of the present invention.
  • FIG. 9 is a first schematic structural diagram of a process conflict processing apparatus according to an embodiment of the present invention.
  • FIG. 10 is a second schematic structural diagram of a process conflict processing apparatus according to an embodiment of the present invention.
  • CP may be composed of multiple network functions
  • each network function may be composed of multiple components
  • each component may be multiple instances.
  • Step 301 The UE initiates a session establishment request message to the CP, and the forwarding module in the CP selects instance 1 (CP1) to process the message.
  • CP1 instance 1
  • Step 302 The CP1 sends a read user data request message to the CUDB requesting all data of the user.
  • step 303 the CUDB returns a read user data response message to the CP1, carrying the user's data and status information.
  • step 304 the CP1 sends a setup user plane request message to the UP.
  • step 305 the UP returns a user plane response message to the CP1.
  • step 306 the CP1 sends a wireless tunnel establishment request message to the source radio access network (RAN).
  • RAN radio access network
  • step 307 the RAN returns a wireless tunnel setup response message to CP1.
  • Step 308 the CP1 sends an update user plane request message to the UP.
  • Step 309 the source RAN decides to initiate the handover, sends a handover request message to the CP, and the forwarding module in the CP selects instance 2 (CP2) to process the message.
  • CP2 instance 2
  • Step 310 The CP2 sends a read user data request message to the CUDB requesting all data of the user.
  • step 311 the CUDB returns a read user data response message to the CP2, carrying the user's data and status information.
  • step 312 the CP2 does not obtain the information that the user newly establishes the session.
  • Step 313 The CP2 sends a handover request message to the target RAN, where the message carries session information.
  • step 314 UP returns an update user plane response message to CP1.
  • 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.
  • step 316 the CP2 returns a handover failure message to the source RAN.
  • step 317 the CP1 returns a PDU session establishment response message to the UE.
  • step 318 the CP1 sends a write user data request message to the CUDB to write the user data.
  • step 319 the CUDB returns a write user data response message to the CP1.
  • step 320 the CP1 deletes the local user context information.
  • the embodiment of the present invention provides a process conflict processing method, and adds a process conflict detection module to the CUDB, and is configured to detect whether the user has a process conflict.
  • a processing example of a network function that is statelessly processed receives user signaling, and when the processing instance (new processing instance) reads user data to the CUDB, if the CUDB detects that the user has a process conflict, when the user data is returned to the processing instance, Indicates a network function flow conflict and indicates the old processing instance ID.
  • the new processing instance When receiving the user data response, the new processing instance determines that there is a process conflict, and forwards the user signaling to the processing instance corresponding to the old processing instance identifier carried in the response message, that is, the same user, and only one processing instance processes the same at the same time.
  • the user's signaling so that the processing instance can take appropriate processing strategies to handle process conflicts and improve the process success rate.
  • FIG. 7 is a schematic flowchart 1 of a process conflict processing method according to an embodiment of the present invention. As shown in FIG. 7, the method includes:
  • Step 701 When receiving the read user data request message, the CUDB entity determines whether the local processing instance identifier is stored locally.
  • the method further includes:
  • the CUDB entity When the CUDB entity receives the read user data request message sent by the network function entity by using the first processing instance, it determines whether the processing instance identifier of the user is stored locally;
  • the processing instance identifier of the user is not stored locally, the processing instance identifier of the first processing instance is stored locally as the processing instance identifier of the user.
  • Step 702 If the processing instance identifier of the user is stored locally, and the processing instance identifier of the stored user is inconsistent with the processing instance identifier of the user in the read user data request message, the CUDB entity determines that there is a process conflict.
  • the CUDB entity when the CUDB entity receives the read user data request message sent by the network function entity by using the second processing instance, determining whether the local processing instance identifier is stored locally;
  • processing instance identifier of the user is stored locally, and the processing instance identifier of the stored user is the processing instance identifier of the second processing instance, it is determined that there is a process conflict.
  • Step 703 When the CUDB entity returns a read user data response message, the read user data response message carries information indicating that there is a process conflict and a processing instance identifier of the user saved in the CUDB entity.
  • the processing instance identifier of the locally stored user is deleted.
  • a process conflict detection module is added to the CUDB, and is set to detect whether the user has a process conflict.
  • the CUDB can save the processing instance identification information that is processing the user signaling.
  • the processing instance identifier of the processing instance of the sending request message is saved.
  • the CUDB clears the processing instance identification information of the user saved in the CUDB.
  • the processing instance identification information of the user has been saved in the CUDB, and the user's read user data request message is received, the processing instance identifier in the new read user data request message is not saved.
  • the CUDB receives the read user data request message, if it finds that the processing instance identifier of the user has been saved, and the processing instance identifier of the saved user and the processing instance identifier of the user in the received read user data request message are inconsistent, CUDB determines that the user has a process conflict. In the returned read user data response message, the carrying finger The information indicating the conflict of the process is displayed, and the processing instance identification information of the user saved in the CUDB is carried.
  • FIG. 8 is a schematic flowchart 2 of a process conflict processing method according to an embodiment of the present invention. As shown in FIG. 8 , the method includes:
  • Step 801 When receiving the 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 The processing instance sends a read user data request message to the CUDB entity, and receives a read user data response message sent by the CUDB entity.
  • the processing instance when the processing instance receives the user signaling, determining whether the user has data of the user on the processing instance;
  • a read user data request message is sent to the CUDB.
  • the read user data response message further carries a processing instance identifier of the user saved in the CUDB entity.
  • Step 803 If the read user data response message carries information indicating that there is a process conflict, the processing instance forwards the user signaling to a processing instance corresponding to the processing instance identifier of the user saved in the CUDB entity. .
  • the network function entity includes: a mobility management function entity and a session management function entity.
  • it includes other network functional entities that can handle user signaling.
  • the processing example includes: an instance of any one of a component of the mobility management function entity that processes user signaling, and an instance of a component of the session management function entity that processes user signaling.
  • an instance of any of the other network function entities that can handle user signaling, which handles user signaling is also included.
  • the network function of the stateless processing receives the signaling of the user, and the forwarding function of the network function forwards the user signaling to the processing instance of the user, and the processing instance receives the information indicating that the process conflict exists after receiving the CUDB indication. And forwarding the user signaling to the processing instance corresponding to the instance processing identifier of the user saved in the CUDB.
  • the processing instance of the user receives the signaling of the user, and sends a read user data request message to the CUDB when there is no data of the user on the processing instance.
  • the processing instance of the user When the processing instance of the user receives the read user data response message returned by the CUDB, if the message is found If the information indicating the existence of the process conflict is carried, the user signaling is forwarded to the processing instance corresponding to the instance processing identifier information saved in the CUDB carried in the read user data response message.
  • one embodiment of a scenario of user PDU session establishment and handover conflicts As shown in FIG. 4, one embodiment of a scenario of user PDU session establishment and handover conflicts.
  • Step 401 The UE initiates a session establishment request message to the CP, and the forwarding module in the CP selects instance 1 (CP1) to process the message.
  • CP1 instance 1
  • Step 402 The CP1 sends a read user data request message to the CUDB requesting all data of the user.
  • step 403 the CUDB saves the identifier of the CP1.
  • Step 404 The process conflict detection module of the CUDB detects that there is no process conflict, returns a read user data response message to the CP1, and carries the user data.
  • step 405 the CP1 sends a setup user plane request message to the UP.
  • step 406 the UP returns to establish a user plane response message to the CP1.
  • step 407 the CP1 sends a wireless tunnel establishment request message to the RAN.
  • step 408 the RAN returns a wireless tunnel setup response message to CP1.
  • step 409 the CP1 sends an update user plane request message to the UP.
  • Step 410 The source RAN decides to initiate the handover, and sends a handover request message to the CP.
  • the forwarding module in the CP selects instance 2 (CP2) to process the message.
  • step 411 the CP2 sends a read user data request message to the CUDB requesting all data of the user.
  • Step 412 The process conflict detection module of the CUDB determines that the user has saved the processing instance identification information (the identifier of the CP1), and is inconsistent with the received processing instance identifier (the identifier of the CP2) of the sending end of the user data request. Process conflicts.
  • Step 413 The CUDB returns a read user data response message to the CP2, carrying information indicating that there is a process conflict, and carrying the processing instance identification information (identification of the CP1) of the user saved in the CUDB.
  • Step 414 The CP2 forwards the handover requirement message to the CP1 according to the information indicating that the process conflict exists in the read user data response message.
  • the CP1 receives the handover request message, and detects that the user is still in the session establishment process, and may adopt an appropriate processing policy, such as suspending the PDU session establishment process, and then processing the handover.
  • Step 416 The CP1 sends a handover request message to the RAN, where the message carries session information (including newly established session information).
  • step 417 the UP returns an update user plane response message to the CP1.
  • step 418 CP1 continues to process the handover message until the handover procedure ends.
  • step 419 the CP1 detects that the user still has a PDU session establishment procedure, and continues to process the PDU session establishment process.
  • step 420 the CP1 returns a PDU session establishment response message to the UE.
  • step 421 the CP1 sends a write user data request message to the CUDB, and writes the user data.
  • step 422 the CUDB clears the user processing instance identification information.
  • step 423 the CUDB returns a write user data response message to the CP1.
  • CP1 deletes local user context information.
  • FIG. 1 An embodiment of a user PDU session setup and location update scenario is shown in FIG. 1
  • Step 501 The UE initiates a session establishment request message to the CP, and the forwarding module in the CP selects instance 1 (CP1) to process the message.
  • CP1 instance 1
  • Step 502 The CP1 sends a read user data request message to the CUDB requesting all data of the user.
  • step 503 the CUDB saves the identifier of the CP1.
  • Step 504 The process conflict detection module of the CUDB detects that there is no process conflict, returns a read user data response message to the CP1, and carries the user data.
  • step 505 the CP1 sends a setup user plane request message to the UP.
  • step 506 the UP returns a user plane response message to the CP1.
  • step 507 the CP1 sends a wireless tunnel establishment request message to the RAN.
  • step 508 the RAN returns a wireless tunnel setup response message to CP1.
  • step 509 the CP1 sends an update user plane request message to the UP.
  • Step 510 The UE initiates a location update request message to the CP due to mobility, etc., and the forwarding module in the CP selects instance 2 (CP2) to process the message.
  • CP2 instance 2
  • step 511 the CP2 sends a read user data request message to the CUDB requesting all data of the user.
  • Step 512 The process conflict detection module of the CUDB determines that the user has saved the processing instance identification information (the identifier of the CP1), and is inconsistent with the received processing instance identifier (the identifier of the CP2) of the sending end of the user data request. Process conflicts.
  • the CUDB returns a read user data response message to the CP2, carrying information indicating that there is a process conflict, and carrying the processing instance identification information (identification of the CP1) of the user saved in the CUDB.
  • Step 514 The CP2 forwards the location update request message to the CP1 according to the information indicating that the process conflict exists in the read user data response message.
  • the CP1 receives the location update request message, and detects that the user is still in the session establishment process, and may adopt an appropriate processing policy, such as ending the PDU session establishment process and processing the location update request message.
  • Step 516 The CP1 sends a delete user plane request message to the UP, and notifies the UP to delete the PDU session being created, and sends a wireless tunnel deletion request message to the RAN.
  • step 517 CP1 starts processing the location update request message.
  • step 518 the UP returns an update user plane response message to the CP1.
  • step 519 the RAN returns a wireless tunnel deletion response message to CP1.
  • step 520 CP1 continues to process the location update message until the location update process ends.
  • step 521 the CP1 sends a write user data request message to the CUDB, and writes the user data.
  • step 522 the CUDB clears the user processing instance identification information.
  • step 523 the CUDB returns a write user data response message to the CP1.
  • step 524 CP1 deletes local user context information.
  • FIG. 6 is an embodiment of a scenario in which a handover and a PDU session establishment collision triggered by a network side are established.
  • step 601 the source RAN decides to initiate the handover, and sends a handover request message to the CP.
  • the forwarding module in the CP selects instance 2 (CP2) to process the message.
  • Step 602 The CP2 sends a read user data request message to the CUDB requesting all data of the user.
  • step 603 the CUDB saves the identifier of the CP2.
  • Step 604 The process conflict detection module of the CUDB detects that there is no process conflict, returns a read user data response message to the CP2, and carries the user's data.
  • step 605 the CP2 sends a handover request message to the target RAN.
  • Step 606 Since the downlink data of the UE needs to be sent but there is no corresponding PDU session, the SCEF or other network element sends a network side session establishment request message to the CP, and the forwarding module in the CP selects instance 1 (CP1) to process the message.
  • the SCEF or other network element sends a network side session establishment request message to the CP, and the forwarding module in the CP selects instance 1 (CP1) to process the message.
  • step 607 the CP1 sends a read user data request message to the CUDB requesting all data of the user.
  • Step 608 The process conflict detection module of the CUDB determines that the user has saved the processing instance identification information (the identifier of the CP2), and is inconsistent with the received processing instance identifier (the identifier of the CP1) of the sending end of the user data request. Process conflicts.
  • step 609 the CUDB returns a read user data response message to the CP1, carrying information indicating that there is a process conflict, and carrying the processing instance identification information (identification of the CP2) of the user saved in the CUDB.
  • Step 610 The CP1 forwards the network side session establishment request message to the CP2 according to the information indicating that the process conflict exists in the read user data response message.
  • Step 611 the CP2 receives the network side session establishment request message, and detects that the user is still To perform the handover process, an appropriate processing policy may be adopted, such as the handover continues, and the network side session establishment request message is cached.
  • step 612 the CP2 continues to process the handover message until the handover procedure ends.
  • Step 613 The CP2 detects that the cached PDU network side session establishment request message is not processed, and continues to process the cached network side session establishment request message.
  • step 614 the CP2 processes the network side session establishment process until the network side session establishment process ends.
  • step 615 the CP2 sends a write user data request message to the CUDB, and writes the user data.
  • step 616 the CUDB clears the user processing instance identification information.
  • step 617 the CUDB returns a write user data response message to the CP2.
  • step 618 the CP2 deletes the local user context information.
  • FIG. 9 is a first schematic structural diagram of a process conflict processing apparatus according to an embodiment of the present invention. As shown in FIG. 9, the apparatus includes:
  • the determining unit 91 is configured to: when receiving the read user data request message, determine whether the local processing instance identifier is stored locally;
  • the determining unit 92 is configured to determine that there is a process conflict if the processing instance identifier of the user is locally stored, and the processed instance identifier of the stored user is inconsistent with the processing instance identifier of the user in the read user data request message;
  • the indicating unit 93 is configured to: when the read user data response message is returned, carry the information indicating that there is a process conflict and the processing instance identifier of the user saved in the CUDB entity in the read user data response message.
  • the determining unit 91 is configured to: when receiving the read user data request message sent by the network function entity by using the first processing instance, determine whether the local processing instance identifier of the user is stored;
  • the device further includes: a storage unit 94, configured to store the processing instance identifier of the first processing instance locally, as the user, when the processing instance identifier of the user is not stored locally Processing instance ID.
  • a storage unit 94 configured to store the processing instance identifier of the first processing instance locally, as the user, when the processing instance identifier of the user is not stored locally Processing instance ID.
  • the determining unit 91 is configured to: when receiving the read user data request message sent by the network function entity by using the second processing instance, determine whether the local processing instance identifier of the user is stored;
  • the determining unit 92 is configured to: if the processing instance identifier of the user is stored locally, and the processing instance identifier of the stored user is the processing instance identifier of the second processing instance, it is determined that there is a process conflict.
  • the device further includes:
  • the deleting unit 95 is configured to delete the processing instance identifier of the locally stored user when receiving the write user data request.
  • FIG. 10 is a second structural diagram of a process conflict processing apparatus according to an embodiment of the present invention. As shown in FIG. 10, the apparatus includes:
  • the forwarding unit 1001 is configured to: when receiving user signaling, select a processing instance for the user signaling and forward the user signaling to the processing instance;
  • the interaction unit 1002 is configured to send a read user data request message to the CUDB entity by using the processing instance, and receive a read user data response message sent by the CUDB entity;
  • the conflict processing unit 1003 is configured to: if the read user data response message carries information indicating that there is a process conflict, the processing instance forwards the user signaling to a processing instance identifier of a user saved in the CUDB entity Corresponding processing examples.
  • the interaction unit 1002 is configured to: when the processing instance receives the user signaling, determine whether the user has data on the processing instance; if there is no user data on the processing instance, then the CUDB is sent to the CUDB. Send a read user data request message.
  • the read user data response message further carries a processing instance identifier of the user saved in the CUDB entity.
  • the network function entity includes: a mobility management function entity and a session management function entity.
  • the processing example includes: an instance of any one of a component of the mobility management function entity that processes user signaling, and an instance of a component of the session management function entity that processes user signaling.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented by the processor to implement the method described in the foregoing embodiments.
  • Computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules, or other data. , removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer.
  • communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media.
  • a modulated data signal such as a carrier wave or other transport mechanism
  • These computer program instructions can be provided to a general purpose computer, a special purpose computer, An processor of an embedded processor or other programmable data processing device to generate a machine such that instructions executed by a processor of a computer or other programmable data processing device are generated for implementation in a flow or a flow of flowcharts and/or Or a block diagram of a device in a box or a function specified in a plurality of boxes.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the embodiment of the present invention can ensure that the same user can process the signaling of the same user at the same time.
  • an appropriate process conflict handling policy can be adopted to improve the user service experience.

Landscapes

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

Abstract

一种流程冲突处理方法及装置，所述方法包括：公共用户数据库CUDB实体接收到读取用户数据请求消息时，判断本地是否存储用户的处理实例标识(701)；如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识与所述读取用户数据请求消息中的用户的处理实例标识不一致，则所述CUDB实体确定存在流程冲突(702)；所述CUDB实体返回读取用户数据响应消息时，在所述读取用户数据响应消息中携带指示存在流程冲突的信息以及所述CUDB实体中保存的用户的处理实例标识(703)。

Description

一种流程冲突处理方法及装置 技术领域
本文涉及但不限于移动通信领域，尤其涉及一种流程冲突处理方法及装置。
背景技术
移动通信目前已经发展到4G阶段。4G的网络架构和前几代相比，主要特点是基于全IP传输。图1是一种4G网络架构，4G网络架构中每个网元的功能如下：
终端(UE，User Equipment)，主要通过无线空口接入4G网络并获得服务，终端通过空口和基站交互信息，通过非接入层信令(NAS，Non-Access Stratum)和核心网的移动性管理实体(MME，Mobility Management Entity)交互信息。
基站(RAN，Radio Access Network)，负责终端接入网络的空口资源调度和以及空口的连接管理。
移动管理实体：核心网控制面实体，主要负责对用户的鉴权、授权以及签约检查，以保证用户是合法用户；用户移动性管理，包括位置注册和临时标识分配；维护空闲(IDLE)和连接(CONNECT)状态以及状态迁移；在CONNECT状态下的切换；分组数据网(PDN，Packet Data network)连接以及承载的维护，包括创建、修改和删除等会话管理的功能；用户IDLE状态下触发寻呼等功能。
服务网关(SGW，Serving GW)：核心网用户面功能实体，主要负责漫游情况下和PDN GW的交互；用户IDLE状态下收到下行数据包进行缓存并通知MME寻呼用户；跨基站的用户面锚点以及跨2G/3G/4G移动性的用户面锚点等功能。
分组数据网关(PDN GW，Packet Data network GW)：核心网用户面功 能实体，是终端接入PDN网络的接入点，负责分配用户IP地址，网络触发的承载建立、修改和删除，还具有服务质量(QoS，Quality of Service)控制计费等功能，是用户在3GPP系统内以及和非3GPP系统之间切换的锚点，从而保证IP地址不变，保证业务连续性。
因为4G主要为人和人服务，到了5G时代，随着对物和物之间通讯的支持，对移动网络的需求更加多样，移动网络将更加复杂。功能组件化和网络功能(NF，Network Function)无状态处理，可以简化5G网络，灵活的满足移动网络的多样需求。网络功能无状态处理，要求业务处理与数据分离，并使用分布式架构，同一组件多实例。
图2是一种业务处理与数据分离的5G网络架构，5G网络架构中每个网元的功能如下：
公共用户数据库(CUDB，Centralized User Database)：至少存储了用户动态数据，如移动行管理上下文、会话上下文、用户状态等。
控制面功能(CP，Control Plane)：包括移动性管理功能(MM)和会话管理功能(SM)等，主要负责对用户的鉴权、授权以及签约检查，以保证用户是合法用户；用户移动性管理，包括位置注册和临时标识分配；维护IDLE和CONNECT状态以及状态迁移；在CONNECT状态下的切换；协议数据单元(PDU，Protocol Data Unit)会话的维护，包括创建、修改和删除等会话管理的功能；用户IDLE状态下触发寻呼等功能。
用户面功能(UP，User Plane)：核心网用户面功能实体，负责分配用户IP地址，具有QoS控制计费等功能。
功能组件化后，通过蓝图等方式编排组件，组成网络功能。网络功能中的组件，可以采用分布式架构，同一组件多实例。处理用户相关信令的组件实现无状态处理时，处理用户的信令的组件多实例，业务处理与数据完全分离，收到用户相关的信令，网络功能的转发模块选择一个组件实例进行处理，组件实例处理用户信令消息后，把用户数据释放。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种流程冲突处理方法及装置。
本发明实施例提供的流程冲突处理方法，包括：
CUDB实体接收到读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识与所述读取用户数据请求消息中的用户的处理实例标识不一致，则所述CUDB实体确定存在流程冲突；
所述CUDB实体返回读取用户数据响应消息时，在所述读取用户数据响应消息中携带指示存在流程冲突的信息以及所述CUDB实体中保存的用户的处理实例标识。
本发明实施例中，所述方法还包括：
所述CUDB实体接收到网络功能实体利用第一处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
当本地没有存储用户的处理实例标识时，将所述第一处理实例的处理实例标识存储至本地，作为所述用户的处理实例标识。
本发明实施例中，所述方法还包括：
所述CUDB实体接收到网络功能实体利用第二处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识为所述第二处理实例的处理实例标识，则确定存在流程冲突。
本发明实施例中，所述方法还包括：
当所述CUDB实体接收到写入用户数据请求时，将本地存储的用户的处理实例标识删除。
本发明另一实施例提供的流程冲突处理方法，包括：
网络功能实体接收到用户信令时，为所述用户信令选择处理实例并将所 述用户信令转发给所述处理实例；
所述处理实例向CUDB实体发送读取用户数据请求消息，接收所述CUDB实体发送的读取用户数据响应消息；
如果所述读取用户数据响应消息中携带指示存在流程冲突的信息，则所述处理实例将所述用户信令转发给所述CUDB实体中保存的用户的处理实例标识对应的处理实例。
本发明实施例中，所述处理实例向CUDB实体发送读取用户数据请求消息，包括：
当处理实例接收到用户信令时，判断本处理实例上是否具有用户的数据；
如果本处理实例上没有用户的数据，则向CUDB发送读取用户数据请求消息。
本发明实施例中，所述读取用户数据响应消息还携带所述CUDB实体中保存的用户的处理实例标识。
本发明实施例中，所述网络功能实体包括：移动性管理功能实体、会话管理功能实体。
本发明实施例中，所述处理实例包括：移动性管理功能实体中的任一个处理用户信令的组件的实例、会话管理功能实体中的任一个处理用户信令的组件的实例。
本发明实施例提供的流程冲突处理装置，包括：
判断单元，设置为接收到读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
决策单元，设置为如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识与所述读取用户数据请求消息中的用户的处理实例标识不一致，则确定存在流程冲突；
指示单元，设置为返回读取用户数据响应消息时，在所述读取用户数据响应消息中携带指示存在流程冲突的信息以及CUDB实体中保存的用户的处理实例标识。
本发明实施例中，所述判断单元，是设置为：接收到网络功能实体利用第一处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
所述装置还包括：存储单元，设置为当本地没有存储用户的处理实例标识时，将所述第一处理实例的处理实例标识存储至本地，作为所述用户的处理实例标识。
本发明实施例中，所述判断单元，是设置为：接收到网络功能实体利用第二处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
所述决策单元，是设置为：如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识为所述第二处理实例的处理实例标识，则确定存在流程冲突。
本发明实施例中，所述装置还包括：
删除单元，设置为当接收到写入用户数据请求时，将本地存储的用户的处理实例标识删除。
本发明另一实施例提供的流程冲突处理装置，包括：
转发单元，设置为接收到用户信令时，为所述用户信令选择处理实例并将所述用户信令转发给所述处理实例；
交互单元，设置为通过所述处理实例向CUDB实体发送读取用户数据请求消息，接收所述CUDB实体发送的读取用户数据响应消息；
冲突处理单元，设置为如果所述读取用户数据响应消息中携带指示存在流程冲突的信息，则所述处理实例将所述用户信令转发给所述CUDB实体中保存的用户的处理实例标识对应的处理实例。
本发明实施例中，所述交互单元，是设置为：当处理实例接收到用户信令时，判断本处理实例上是否具有用户的数据；如果本处理实例上没有用户的数据，则向CUDB发送读取用户数据请求消息。
本发明实施例中，所述读取用户数据响应消息还携带所述CUDB实体中保存的用户的处理实例标识。
本发明实施例中，所述网络功能实体包括：移动性管理功能实体、会话管理功能实体。
本发明实施例中，所述处理实例包括：移动性管理功能实体中的任一个处理用户信令的组件的实例、会话管理功能实体中的任一个处理用户信令的组件的实例。
本发明实施例中，网络功能实体接收到请求消息时，为所述请求消息选择处理实例；利用所述处理实例从统一数据管理CUDB实体中获取用户的处理实例标识；所述处理实例判断所述用户的处理实例标识与本地的处理实例标识是否一致；当用户的处理实例标识与本地的处理实例标识不一致时，将所述请求消息转发给与所述用户的处理实例标识相对应的处理实例进行处理。采用本发明实施例，可以保证同一用户，在同一时刻，只有一个处理实例处理同一用户的信令，在业务流程冲突时，可以采取合适的流程冲突处理策略，提高用户业务体验。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是4G网络架构图；
图2是一种业务处理与数据分离的5G网络架构图；
图3是基于业务处理与数据分离的5G网络架构的用户PDU会话建立和切换冲突的场景图；
图4是本发明实施例的用户PDU会话建立和切换冲突的场景的流程图；
图5是本发明实施例的用户PDU会话建立和位置更新场景的流程图；
图6是本发明实施例的网络侧触发的PDU会话建立和切换冲突的场景的流程图；
图7为本发明实施例的流程冲突处理方法的流程示意图一；
图8为本发明实施例的流程冲突处理方法的流程示意图二；
图9为本发明实施例的流程冲突处理装置的结构组成示意图一；
图10为本发明实施例的流程冲突处理装置的结构组成示意图二。
本发明的实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
图3是一个用户PDU会话建立和切换冲突的场景，其中CP可能是由多个网络功能组成，每个网络功能可以由多个组件组成，每个组件都可以是多实例。
步骤301，UE发起会话建立请求消息给CP，CP中的转发模块选择实例1(CP1)处理该消息。
步骤302，CP1向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤303，CUDB向CP1返回读取用户数据响应消息，携带用户的数据和状态信息。
步骤304，CP1向UP发送建立用户面请求消息。
步骤305，UP返回建立用户面响应消息给CP1。
步骤306，CP1向源无线接入网(RAN)发送无线隧道建立请求消息。
步骤307，RAN返回无线隧道建立响应消息给CP1。
步骤308，CP1向UP发送更新用户面请求消息。
步骤309，源RAN决定发起切换，发送切换请求消息给CP，CP中的转发模块选择实例2(CP2)处理该消息。
步骤310，CP2向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤311，CUDB向CP2返回读取用户数据响应消息，携带用户的数据和状态信息。
步骤312，CP2没有获取用户新建立会话的信息。
步骤313，CP2向目标RAN发送切换请求消息，消息中携带会话信息。
步骤314，UP返回更新用户面响应消息给CP1。
步骤315，目标RAN因为无线透明容器中的会话信息和核心网下发的会话信息不一致，返回切换准备失败消息给CP2。
步骤316，CP2向源RAN返回切换失败消息。
步骤317，CP1向UE返回PDU会话建立响应消息。
步骤318，CP1向CUDB发送写入用户数据请求消息，写入该用户数据。
步骤319，CUDB向CP1返回写入用户数据响应消息。
步骤320，CP1删除本地用户上下文信息。
可以看到，在PDU会话建立流程中，如果又有用户的其他流程，可能会选择到不同的处理实例，导致不可预知的后果，如切换失败。
无状态处理的网络功能，同一个用户可能会有多个流程同时进行，多个流程在不同的处理实例上处理，导致处理实例无法检测到这种冲突，不能采取合适的处理策略。
基于此，本发明实施例提出了一种流程冲突处理方法，在CUDB中增加一个流程冲突检测模块，设置为检测用户是否有流程冲突。无状态处理的网络功能的处理实例，收到用户的信令，处理实例(新的处理实例)向CUDB读取用户数据时，如果CUDB检测到用户存在流程冲突时，向处理实例返回用户数据时，指示网络功能流程冲突，并指示老的处理实例标识。新的处理实例在收到用户数据响应时，确定存在流程冲突，转发用户信令到响应消息携带的老的处理实例标识对应的处理实例，即同一用户，在同一时刻，只有一个处理实例处理同一用户的信令，从而使得处理实例可以采取合适的处理策略处理流程冲突，提高流程成功率。
图7为本发明实施例的流程冲突处理方法的流程示意图一，如图7所示，所述方法包括：
步骤701：CUDB实体接收到读取用户数据请求消息时，判断本地是否存储用户的处理实例标识。
本发明实施例中，所述方法还包括：
所述CUDB实体接收到网络功能实体利用第一处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
当本地没有存储用户的处理实例标识时，将所述第一处理实例的处理实例标识存储至本地，作为所述用户的处理实例标识。
步骤702：如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识与所述读取用户数据请求消息中的用户的处理实例标识不一致，则所述CUDB实体确定存在流程冲突。
可选地，所述CUDB实体接收到网络功能实体利用第二处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识为所述第二处理实例的处理实例标识，则确定存在流程冲突。
步骤703：所述CUDB实体返回读取用户数据响应消息时，在所述读取用户数据响应消息中携带指示存在流程冲突的信息以及所述CUDB实体中保存的用户的处理实例标识。
本发明实施例中，当所述CUDB实体接收到写入用户数据请求时，将本地存储的用户的处理实例标识删除。
本发明实施例中，在CUDB中增加一个流程冲突检测模块，设置为检测用户是否有流程冲突。对每一个用户，CUDB可以保存正在处理该用户信令的处理实例标识信息。CUDB收到该用户的读取用户数据请求消息时，如果发现CUDB中还没有保存用户的处理实例标识信息，则保存发送请求消息的处理实例的处理实例标识。CUDB在收到写入用户数据请求消息时，会清空CUDB中保存的用户的处理实例标识信息。如果CUDB中已保存了用户的处理实例标识信息，又收到了用户的读取用户数据请求消息，则不保存新的读取用户数据请求消息中的处理实例标识。CUDB收到读取用户数据请求消息时，如果发现已保存了用户的处理实例标识，且保存的用户的处理实例标识和收到的读取用户数据请求消息中的用户的处理实例标识不一致，则CUDB确定用户存在流程冲突，在返回的读取用户数据响应消息中，携带指 示存在流程冲突的信息，且携带CUDB中保存的用户的处理实例标识信息。
图8为本发明实施例的流程冲突处理方法的流程示意图二，如图8所示，所述方法包括：
步骤801：网络功能实体接收到用户信令时，为所述用户信令选择处理实例并将所述用户信令转发给所述处理实例。
步骤802：所述处理实例向CUDB实体发送读取用户数据请求消息，接收所述CUDB实体发送的读取用户数据响应消息。
可选地，当处理实例接收到用户信令时，判断本处理实例上是否具有用户的数据；
如果本处理实例上没有用户的数据，则向CUDB发送读取用户数据请求消息。
本发明实施例中，所述读取用户数据响应消息还携带所述CUDB实体中保存的用户的处理实例标识。
步骤803：如果所述读取用户数据响应消息中携带指示存在流程冲突的信息，则所述处理实例将所述用户信令转发给所述CUDB实体中保存的用户的处理实例标识对应的处理实例。
本发明实施例中，所述网络功能实体包括：移动性管理功能实体、会话管理功能实体。此外，还包括其他可以处理用户信令的网络功能实体。
本发明实施例中，所述处理实例包括：移动性管理功能实体中的任一个处理用户信令的组件的实例、会话管理功能实体中的任一个处理用户信令的组件的实例。此外，还包括其他可以处理用户信令的网络功能实体中的任一个处理用户信令的组件的实例。
本发明实施例中，无状态处理的网络功能，收到用户的信令，网络功能的转发模块把用户信令转发给用户的处理实例，处理实例在收到CUDB的指示存在流程冲突的信息后，把用户信令转发给CUDB中保存的用户的实例处理标识对应的处理实例。用户的处理实例，收到了用户的信令，在本处理实例上没有该用户的数据时，向CUDB发送读取用户数据请求消息。用户的处理实例收到CUDB返回的读取用户数据响应消息时，如果发现消息 中携带了指示存在流程冲突的信息，则把用户信令转发给读取用户数据响应消息中携带的CUDB中保存的实例处理标识信息对应的处理实例。
下面结合具体应用场景对本发明实施例的方案做进一步详细描述。
如图4所示是用户PDU会话建立和切换冲突的场景的一个实施例。
步骤401，UE发起会话建立请求消息给CP，CP中的转发模块选择实例1(CP1)处理该消息。
步骤402，CP1向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤403，CUDB保存CP1的标识。
步骤404，CUDB的流程冲突检测模块检测到没有流程冲突，向CP1返回读取用户数据响应消息，携带用户的数据。
步骤405，CP1向UP发送建立用户面请求消息。
步骤406，UP返回建立用户面响应消息给CP1。
步骤407，CP1向RAN发送无线隧道建立请求消息。
步骤408，RAN返回无线隧道建立响应消息给CP1。
步骤409，CP1向UP发送更新用户面请求消息。
步骤410，源RAN决定发起切换，发送切换需求消息给CP，CP中的转发模块选择实例2(CP2)处理该消息。
步骤411，CP2向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤412，CUDB的流程冲突检测模块判断该用户已保存处理实例标识信息(CP1的标识)，且和收到的读取用户数据请求的发送端的处理实例标识(CP2的标识)不一致，则认为存在流程冲突。
步骤413，CUDB向CP2返回读取用户数据响应消息，携带指示存在流程冲突的信息，且携带CUDB中保存的用户的处理实例标识信息(CP1的标识)。
步骤414，CP2根据读取用户数据响应消息中的指示存在流程冲突的信息，转发切换需求消息给CP1。
步骤415，CP1收到切换需求消息，同时检测到该用户还在进行会话建立过程，可以采取合适的处理策略，比如挂起PDU会话建立过程，再处理切换。
步骤416，CP1向RAN发送切换请求消息，消息中携带会话信息(包括新建立的会话信息)。
步骤417，UP返回更新用户面响应消息给CP1。
步骤418，CP1继续处理切换消息，直到切换流程处理结束。
步骤419，CP1检测到该用户还有PDU会话建立流程没有结束，继续处理PDU会话建立流程。
步骤420，CP1向UE返回PDU会话建立响应消息。
步骤421，CP1向CUDB发送写入用户数据请求消息，写入该用户数据。
步骤422，CUDB清空该用户处理实例标识信息。
步骤423，CUDB向CP1返回写入用户数据响应消息。
步骤424，CP1删除本地用户上下文信息。
如图5所示是用户PDU会话建立和位置更新场景的一个实施例。
步骤501，UE发起会话建立请求消息给CP，CP中的转发模块选择实例1(CP1)处理该消息。
步骤502，CP1向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤503，CUDB保存CP1的标识。
步骤504，CUDB的流程冲突检测模块检测到没有流程冲突，向CP1返回读取用户数据响应消息，携带用户的数据。
步骤505，CP1向UP发送建立用户面请求消息。
步骤506，UP返回建立用户面响应消息给CP1。
步骤507，CP1向RAN发送无线隧道建立请求消息。
步骤508，RAN返回无线隧道建立响应消息给CP1。
步骤509，CP1向UP发送更新用户面请求消息。
步骤510，由于移动等原因，UE发起位置更新请求消息给CP，CP中的转发模块选择实例2(CP2)处理该消息。
步骤511，CP2向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤512，CUDB的流程冲突检测模块判断该用户已保存处理实例标识信息(CP1的标识)，且和收到的读取用户数据请求的发送端的处理实例标识(CP2的标识)不一致，则认为存在流程冲突。
步骤513，CUDB向CP2返回读取用户数据响应消息，携带指示存在流程冲突的信息，且携带CUDB中保存的用户的处理实例标识信息(CP1的标识)。
步骤514，CP2根据读取用户数据响应消息中的指示存在流程冲突的信息，转发位置更新请求消息给CP1。
步骤515，CP1收到位置更新请求消息，同时检测到该用户还在进行会话建立过程，可以采取合适的处理策略，比如结束PDU会话建立过程再处理位置更新请求消息。
步骤516，CP1向UP发送删除用户面请求消息，通知UP删除正在创建的PDU会话，向RAN发送无线隧道删除请求消息。
步骤517，CP1开始处理位置更新请求消息。
步骤518，UP返回更新用户面响应消息给CP1。
步骤519，RAN返回无线隧道删除响应消息给CP1。
步骤520，CP1继续处理位置更新消息，直到位置更新流程处理结束。
步骤521，CP1向CUDB发送写入用户数据请求消息，写入该用户数据。
步骤522，CUDB清空该用户处理实例标识信息。
步骤523，CUDB向CP1返回写入用户数据响应消息。
步骤524，CP1删除本地用户上下文信息。
如图6所示是切换和网络侧触发的PDU会话建立冲突的场景的一个实施例。
步骤601，源RAN决定发起切换，发送切换需求消息给CP，CP中的转发模块选择实例2(CP2)处理该消息。
步骤602，CP2向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤603，CUDB保存CP2的标识。
步骤604，CUDB的流程冲突检测模块检测到没有流程冲突，向CP2返回读取用户数据响应消息，携带用户的数据。
步骤605，CP2向目标RAN发送切换请求消息。
步骤606，由于有UE的下行数据需要发送，但没有对应的PDU会话，SCEF或其他网元发送网络侧会话建立请求消息给CP，CP中的转发模块选择实例1(CP1)处理该消息。
步骤607，CP1向CUDB发送读取用户数据请求消息，请求该用户所有数据。
步骤608，CUDB的流程冲突检测模块判断该用户已保存处理实例标识信息(CP2的标识)，且和收到的读取用户数据请求的发送端的处理实例标识(CP1的标识)不一致，则认为存在流程冲突。
步骤609，CUDB向CP1返回读取用户数据响应消息，携带指示存在流程冲突的信息，且携带CUDB中保存的用户的处理实例标识信息(CP2的标识)。
步骤610，CP1根据读取用户数据响应消息中的指示存在流程冲突的信息，转发网络侧会话建立请求消息给CP2。
步骤611，CP2收到网络侧会话建立请求消息，同时检测到该用户还在 进行切换过程，可以采取合适的处理策略，比如切换继续进行，缓存网络侧会话建立请求消息。
步骤612，CP2继续处理切换消息，直到切换流程处理结束。
步骤613，CP2检测到该用户还有缓存的PDU网络侧会话建立请求消息没有处理，则继续处理缓存的网络侧会话建立请求消息。
步骤614，CP2处理网络侧会话建立流程，直到网络侧会话建立流程结束。
步骤615，CP2向CUDB发送写入用户数据请求消息，写入该用户数据。
步骤616，CUDB清空该用户处理实例标识信息。
步骤617，CUDB向CP2返回写入用户数据响应消息。
步骤618，CP2删除本地用户上下文信息。
图9为本发明实施例的流程冲突处理装置的结构组成示意图一，如图9所示，所述装置包括：
判断单元91，设置为接收到读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
决策单元92，设置为如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识与所述读取用户数据请求消息中的用户的处理实例标识不一致，则确定存在流程冲突；
指示单元93，设置为返回读取用户数据响应消息时，在所述读取用户数据响应消息中携带指示存在流程冲突的信息以及CUDB实体中保存的用户的处理实例标识。
本发明实施例中，所述判断单元91，是设置为：接收到网络功能实体利用第一处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
所述装置还包括：存储单元94，设置为当本地没有存储用户的处理实例标识时，将所述第一处理实例的处理实例标识存储至本地，作为所述用户 的处理实例标识。
本发明实施例中，所述判断单元91，是设置为：接收到网络功能实体利用第二处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
所述决策单元92，是设置为：如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识为所述第二处理实例的处理实例标识，则确定存在流程冲突。
本发明实施例中，所述装置还包括：
删除单元95，设置为当接收到写入用户数据请求时，将本地存储的用户的处理实例标识删除。
图10为本发明实施例的流程冲突处理装置的结构组成示意图二，如图10所示，所述装置包括：
转发单元1001，设置为接收到用户信令时，为所述用户信令选择处理实例并将所述用户信令转发给所述处理实例；
交互单元1002，设置为通过所述处理实例向CUDB实体发送读取用户数据请求消息，接收所述CUDB实体发送的读取用户数据响应消息；
冲突处理单元1003，设置为如果所述读取用户数据响应消息中携带指示存在流程冲突的信息，则所述处理实例将所述用户信令转发给所述CUDB实体中保存的用户的处理实例标识对应的处理实例。
本发明实施例中，所述交互单元1002，是设置为：当处理实例接收到用户信令时，判断本处理实例上是否具有用户的数据；如果本处理实例上没有用户的数据，则向CUDB发送读取用户数据请求消息。
本发明实施例中，所述读取用户数据响应消息还携带所述CUDB实体中保存的用户的处理实例标识。
本发明实施例中，所述网络功能实体包括：移动性管理功能实体、会话管理功能实体。
本发明实施例中，所述处理实例包括：移动性管理功能实体中的任一个处理用户信令的组件的实例、会话管理功能实体中的任一个处理用户信令的组件的实例。
本发明实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述实施例所述的方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理单元的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本发明的可选实施例而已，并非用于限定本发明的保护范围。
工业实用性
采用本发明实施例可以保证同一用户，在同一时刻，只有一个处理实例处理同一用户的信令，在业务流程冲突时，可以采取合适的流程冲突处理策略，提高用户业务体验。

Claims (18)

  1. 一种流程冲突处理方法，所述方法包括：
    公共用户数据库CUDB实体接收到读取用户数据请求消息时，判断本地是否存储用户的处理实例标识(701)；
    如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识与所述读取用户数据请求消息中的用户的处理实例标识不一致，则所述CUDB实体确定存在流程冲突(702)；
    所述CUDB实体返回读取用户数据响应消息时，在所述读取用户数据响应消息中携带指示存在流程冲突的信息以及所述CUDB实体中保存的用户的处理实例标识(703)。
  2. 根据权利要求1所述的流程冲突处理方法，所述方法还包括：
    所述CUDB实体接收到网络功能实体利用第一处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
    当本地没有存储用户的处理实例标识时，将所述第一处理实例的处理实例标识存储至本地，作为所述用户的处理实例标识。
  3. 根据权利要求2所述的流程冲突处理方法，所述方法还包括：
    所述CUDB实体接收到网络功能实体利用第二处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
    如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识为所述第二处理实例的处理实例标识，则确定存在流程冲突。
  4. 根据权利要求1至3任一项所述的流程冲突处理方法，所述方法还包括：
    当所述CUDB实体接收到写入用户数据请求时，将本地存储的用户的处理实例标识删除。
  5. 一种流程冲突处理方法，所述方法包括：
    网络功能实体接收到用户信令时，为所述用户信令选择处理实例并将所述用户信令转发给所述处理实例(801)；
    所述处理实例向公共用户数据库CUDB实体发送读取用户数据请求消息，接收所述CUDB实体发送的读取用户数据响应消息(802)；
    如果所述读取用户数据响应消息中携带指示存在流程冲突的信息，则所述处理实例将所述用户信令转发给所述CUDB实体中保存的用户的处理实例标识对应的处理实例(803)。
  6. 根据权利要求5所述的流程冲突处理方法，其中，所述处理实例向CUDB实体发送读取用户数据请求消息，包括：
    当处理实例接收到用户信令时，判断本处理实例上是否具有用户的数据；
    如果本处理实例上没有用户的数据，则向CUDB发送读取用户数据请求消息。
  7. 根据权利要求5所述的流程冲突处理方法，其中，所述读取用户数据响应消息还携带所述CUDB实体中保存的用户的处理实例标识。
  8. 根据权利要求5至7任一项所述的流程冲突处理方法，其中，所述网络功能实体包括：移动性管理功能实体、会话管理功能实体。
  9. 根据权利要求5至7任一项所述的流程冲突处理方法，其中，所述处理实例包括：移动性管理功能实体中的任一个处理用户信令的组件的实例、会话管理功能实体中的任一个处理用户信令的组件的实例。
  10. 一种流程冲突处理装置，所述装置包括：
    判断单元(91)，设置为接收到读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
    决策单元(92)，设置为如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识与所述读取用户数据请求消息中的用户的处理实例标识不一致，则确定存在流程冲突；
    指示单元(93)，设置为返回读取用户数据响应消息时，在所述读取用户数据响应消息中携带指示存在流程冲突的信息以及公共用户数据库CUDB实体中保存的用户的处理实例标识。
  11. 根据权利要求10所述的流程冲突处理装置，其中，所述判断单元， 是设置为接收到网络功能实体利用第一处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
    所述装置还包括：存储单元(94)，设置为当本地没有存储用户的处理实例标识时，将所述第一处理实例的处理实例标识存储至本地，作为所述用户的处理实例标识。
  12. 根据权利要求11所述的流程冲突处理装置，其中，
    所述判断单元，是设置为接收到网络功能实体利用第二处理实例发送的读取用户数据请求消息时，判断本地是否存储用户的处理实例标识；
    所述决策单元，是设置为如果本地存储用户的处理实例标识，且所存储的用户的处理实例标识为所述第二处理实例的处理实例标识，则确定存在流程冲突。
  13. 根据权利要求10至12任一项所述的流程冲突处理装置，所述装置还包括：
    删除单元(95)，设置为当接收到写入用户数据请求时，将本地存储的用户的处理实例标识删除。
  14. 一种流程冲突处理装置，所述装置包括：
    转发单元(1001)，设置为接收到用户信令时，为所述用户信令选择处理实例并将所述用户信令转发给所述处理实例；
    交互单元(1002)，设置为通过所述处理实例向公共用户数据库CUDB实体发送读取用户数据请求消息，接收所述CUDB实体发送的读取用户数据响应消息；
    冲突处理单元(1003)，设置为如果所述读取用户数据响应消息中携带指示存在流程冲突的信息，则所述处理实例将所述用户信令转发给所述CUDB实体中保存的用户的处理实例标识对应的处理实例。
  15. 根据权利要求14所述的流程冲突处理装置，其中，
    所述交互单元，是设置为当处理实例接收到用户信令时，判断本处理实例上是否具有用户的数据；如果本处理实例上没有用户的数据，则向CUDB发送读取用户数据请求消息。
  16. 根据权利要求14所述的流程冲突处理装置，其中，所述读取用户数据响应消息还携带所述CUDB实体中保存的用户的处理实例标识。
  17. 根据权利要求14至16任一项所述的流程冲突处理装置，其中，所述网络功能实体包括：移动性管理功能实体、会话管理功能实体。
  18. 根据权利要求14至16任一项所述的流程冲突处理装置，其中，所述处理实例包括：移动性管理功能实体中的任一个处理用户信令的组件的实例、会话管理功能实体中的任一个处理用户信令的组件的实例。
PCT/CN2017/117484 2017-01-10 2017-12-20 一种流程冲突处理方法及装置 WO2018130053A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710018520.9 2017-01-10
CN201710018520.9A CN108289306B (zh) 2017-01-10 2017-01-10 一种流程冲突处理方法及装置

Publications (1)

Publication Number Publication Date
WO2018130053A1 true WO2018130053A1 (zh) 2018-07-19

Family

ID=62831446

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/117484 WO2018130053A1 (zh) 2017-01-10 2017-12-20 一种流程冲突处理方法及装置

Country Status (2)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022252651A1 (zh) * 2021-06-04 2022-12-08 华为技术有限公司 一种无线通信方法及装置

Families Citing this family (2)

* 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

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102834823A (zh) * 2010-02-11 2012-12-19 瑞典爱立信有限公司 目录数据库处的数据管理
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.

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102148689B (zh) * 2010-02-09 2016-01-20 中兴通讯股份有限公司 策略和计费规则功能实体的选择方法、装置及系统
US9384254B2 (en) * 2012-06-18 2016-07-05 Actifio, Inc. System and method for providing intra-process communication for an application programming interface
WO2014101935A1 (en) * 2012-12-24 2014-07-03 Telefonaktiebolaget L M Ericsson (Publ) Enabling external access to multiple services on a local server
CN103402187B (zh) * 2013-07-08 2017-04-05 大唐移动通信设备有限公司 一种下行信令消息流程处理的方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102834823A (zh) * 2010-02-11 2012-12-19 瑞典爱立信有限公司 目录数据库处的数据管理
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.

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Service Requirements for the User Data Convergence (UDC", 3GPP TR 22.985, 31 December 2015 (2015-12-31), XP051294771 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022252651A1 (zh) * 2021-06-04 2022-12-08 华为技术有限公司 一种无线通信方法及装置

Also Published As

Publication number Publication date
CN108289306B (zh) 2023-03-10
CN108289306A (zh) 2018-07-17

Similar Documents

Publication Publication Date Title
US11743075B2 (en) Communication method and apparatus
WO2018145669A1 (zh) 一种业务分流实现方法及装置
CN109600802B (zh) 数据传输方法、相关设备及系统
CN106961748B (zh) 控制ue上下文和ue连接的方法和设备
WO2018126535A1 (zh) 一种会话管理方法及装置
JP6568231B2 (ja) ユーザー・プレーンベアラの確立を制御する方法及び装置
JP5021772B2 (ja) トラッキングエリアの更新或いは切替プロセスにおいてリソースが誤ってリリースされることを防ぐ方法
WO2019101074A1 (zh) 一种通信方法、装置及系统
US9332426B2 (en) Communication system, communication method, and communication program
WO2008128452A1 (fr) Procédé, système et nœud cn pour transfert de charge dans la zone commune
WO2009135431A1 (zh) 用户信息通知方法、系统和装置
US20140321365A1 (en) Mobile communication network system, communication control method, non-transitory computer readable medium storing program therefor
US11445420B2 (en) User device, radio communication system, and radio communication method
WO2014186968A1 (zh) 位置区管理方法和核心网控制器
WO2018059401A1 (zh) 网络切换方法、装置及系统，网络接入方法及装置
US11343724B2 (en) User equipment context management method, apparatus, and device
JP2018524845A (ja) アクセス方法及び、対応するアクセスノード、端末と通信ネットワーク
WO2018130053A1 (zh) 一种流程冲突处理方法及装置
WO2017028637A1 (zh) 网关的恢复处理方法及装置
EP4319297A2 (en) Communication method and communications apparatus
WO2018041097A1 (zh) 网络切换方法及装置
CN105027660B (zh) 一种ps业务恢复方法、msc/vlr及mme
US11991516B2 (en) Session migration method and apparatus
WO2018001301A1 (zh) 用户设备的控制方法、装置及系统和网关
WO2018108012A1 (zh) 一种网络功能实体进行无状态处理的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17892031

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17892031

Country of ref document: EP

Kind code of ref document: A1