EP3979707B1 - Procédé de déclenchement de la modification de trajet dans le plan d'utilisateur d'un système de communication - Google Patents

Procédé de déclenchement de la modification de trajet dans le plan d'utilisateur d'un système de communication Download PDF

Info

Publication number
EP3979707B1
EP3979707B1 EP21192955.9A EP21192955A EP3979707B1 EP 3979707 B1 EP3979707 B1 EP 3979707B1 EP 21192955 A EP21192955 A EP 21192955A EP 3979707 B1 EP3979707 B1 EP 3979707B1
Authority
EP
European Patent Office
Prior art keywords
function entity
session
user plane
management function
terminal device
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
EP21192955.9A
Other languages
German (de)
English (en)
Other versions
EP3979707A1 (fr
Inventor
Fenqin Zhu
Dekui SUN
Wenfu Wu
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP3979707A1 publication Critical patent/EP3979707A1/fr
Application granted granted Critical
Publication of EP3979707B1 publication Critical patent/EP3979707B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/249—Reselection being triggered by specific parameters according to timing information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment

Definitions

  • This application relates to the field of communications technologies, and in particular, to a method for initiating user plane path modification.
  • mobility management and session management are separately implemented by two entities: a core access and mobility management function (Core Access and Mobility Management Function, AMF) and a session management function (Session Management Function, SMF).
  • AMF Core Access and Mobility Management Function
  • SMF Session Management Function
  • the AMF is responsible for mobility management for terminal devices, including making a tracking area list (Tracking Area List, TA List).
  • the SMF is responsible for session management, including: selecting a user plane function (User Plane Function, UPF), establishing a packet data unit (Packet Data Unit, PDU) session, and so on.
  • UPF User Plane Function
  • PDU Packet Data Unit
  • UPFs may be classified into N3 UPFs and PDU session anchor UPFs (PDU Session Anchor, PSA for short) based on different functions for which the UPFs are responsible.
  • the N3 UPF is connected to a radio access network (Radio Access Network, RAN) through an N3 interface
  • the PSA is connected to a data network through an N6 interface.
  • Each UPF has a particular service range.
  • a service range of an N3 UPF is a sum of service ranges of RANs connected to the N3 UPF.
  • the N3 UPF and the PSA can generally provide relatively good services for the terminal when the terminal device is located within a service range of the N3 UPF and an optimal service area of the PSA.
  • the terminal device is a mobile terminal device such as a mobile phone
  • a location of the terminal device is not permanent.
  • 5G compared with a 4 th generation (4 th Generation, 4G) mobile communications technology
  • a deployment location of a UPF is relatively flexible, a service range of the UPF varies greatly with the deployment location, and mobility management and session management are separately implemented by two entities. Therefore, to better serve data communication of the terminal device, a user plane path needs to be re-established.
  • a mechanism for initiating user plane path re-establishment is not clearly defined. In view of this, embodiments of this application provide a method for initiating user plane path re-establishment.
  • US 2014/242939 A1 discloses that the local reporting may be performed at different granularity levels.
  • US 2010/189076 A1 disclose a method for processing GTP in mobile communication system.
  • This application provides a method for initiating user plane path modification, to better serve a session of a terminal device, and thereby improving user experience.
  • a session management function entity, a mobility management function entity, a user plane function entity, and the like in the embodiments of this application are merely names, and the names constitute no limitation on devices.
  • network elements or entities corresponding to the session management function entity, the mobility management function entity, and the user plane function entity may have other names.
  • the session management function entity may be a session management function (Session Management Function, SMF)
  • the mobility management function entity may be a core access and mobility management function (Core Access and Mobility Management Function, AMF)
  • the user plane function entity may be a user plane function (User Plane Function, UPF), and so on.
  • SMF Session Management Function
  • AMF Core Access and Mobility Management Function
  • UPF User Plane Function
  • the session management function entity, the mobility management function entity, the user plane function entity, and the like in the embodiments of this application may also have other functions besides functions in the embodiments of this application. This is not specifically limited in the embodiments of this application.
  • the mobility management function entity may also have other functions besides a function of sending location information of a terminal device to the session management function entity. This is not specifically limited in the embodiments of this application.
  • the session management function entity, the mobility management function entity, the user plane function entity, or the like in the embodiments of this application may be implemented by one physical device, or may be implemented by a plurality of physical devices jointly. This is not specifically limited in the embodiments of this application.
  • each of the session management function entity, the mobility management function entity, the user plane function entity, and the like in the embodiments of this application may be a logical function module in a physical device, or may be a logical function module including a plurality of physical devices. This is not specifically limited in the embodiments of this application.
  • a method for initiating user plane path re-establishment in the embodiments of this application may be applied to a communications system 100 shown in FIG. 1 .
  • the communications system 100 includes a session management function entity 110 and a mobility management function entity 120.
  • a session for which user plane path re-establishment is initiated may be a packet data unit (Packet Data Unit, PDU) session, or a public data network (Public Data Network, PDN) session, or another session. This is not limited in this application.
  • an embodiment of this application provides a method for initiating user plane path re-establishment, including the following steps.
  • Step 200a A session management function entity 110 determines, based on first location information of a terminal device, a session service area to which a current session of the terminal device belongs.
  • the first location information is location information of the terminal device received by the session management function entity 110 in a process of establishing the current session or in a process of handover from a first user plane function entity to a second user plane function entity.
  • the first user plane function entity is configured to serve a session of the terminal device before the handover to the second user plane function entity.
  • the second user plane function entity is configured to serve the current session.
  • the process of establishing the current session in this embodiment of this application includes a process of initially establishing the current session and a process of re-establishing a session to the current session.
  • the first location information may be carried in a request message sent to the session management function entity for initially establishing the current session, or carried in a message particularly for sending the first location information, or carried in a request message in a process of re-establishing a session to the current session, or carried in a path switching request message. This is not limited in this embodiment of this application.
  • Step 210a A mobility management function entity 120 sends second location information of the terminal device to the session management function entity 110, and the session management function entity 110 receives the second location information of the terminal device sent by the mobility management function entity 120.
  • Step 220a After receiving the second location information of the terminal device sent by the mobility management function entity 120, if determining that the second location information is not within the session service area, the session management function entity 110 instructs the terminal device to initiate a re-establishment procedure for the current session.
  • the session management function entity 110 determines that the second location information is within the session service area, this procedure ends, and the session management function entity 110 no longer instructs the terminal device to initiate the re-establishment procedure for the current session.
  • the session service area may also be referred to as a packet data unit session service area (PDU Session Service Area, PSSA).
  • PDU Session Service Area PDU Session Service Area
  • the session service area is a logical concept.
  • the session management function entity 110 may determine the session service area in the following manner: using, by the session management function entity 110, the first location information of the terminal device as a center, to determine a center location of the session service area, and then determining a size of the session service area.
  • the size of the session service area may be determined according to a preconfigured policy. For example, a quantity of cells included in the session service area, a quantity of tracking areas (Tracking Area, TA) included in the session service area, and the like are preconfigured.
  • TA Tracking Area
  • the session management function entity 110 may alternatively determine the size of the session service area in the following manner: determining, by the session management function entity 110, the size of the session service area based on a service area of a user plane function entity serving the current session and/or based on a mobility pattern of the terminal device, where the mobility pattern includes at least one of a moving range of the terminal device, a moving speed of the terminal device, and a moving track of the terminal device.
  • the PDU session is used as an example.
  • the user plane function entity serving the current session may be an anchor UPF serving the current session.
  • a session service area may be defined as the service area of the anchor UPF serving the current session.
  • a smaller session service area may be defined, so that user plane path switching can be performed early after a location of the terminal device is relatively stable.
  • the mobility pattern of the terminal device may be specifically determined based on subscription information, or a historical moving track of the terminal device.
  • the session management function entity may also consider other factors, to better serve a session of the terminal device.
  • the session service area determined by the session management function entity may include the service area of the user plane function entity serving the current session, as shown in FIG. 3a , or may include only a part of the service area of the user plane function entity serving the current session, as shown in FIG. 3b .
  • step 220a in addition to determining whether the second location information is within the session service area, a step of determining whether the second location information is within the service area of the user plane function entity serving the current session needs to be added. Specifically, when determining that the second location information is not within the session service area or the service area of the user plane function entity serving the current session, the session management function entity 110 instructs the terminal device to initiate the re-establishment procedure for the current session. Otherwise, this procedure ends.
  • FIG. 2b shows another method for initiating user plane path re-establishment provided in an embodiment of this application. Based on the method for initiating user plane path re-establishment shown in FIG 2a , a concept of a location report granularity of a terminal device is introduced. Specifically, the method for initiating user plane path re-establishment includes the following steps.
  • Step 200a A session management function entity 110 determines, based on first location information of a terminal device, a session service area to which a current session of the terminal device belongs.
  • the first location information is location information of the terminal device received by the session management function entity 110 in a process of establishing the current session or in a process of handover from a first user plane function entity to a second user plane function entity.
  • the first user plane function entity is configured to serve a session of the terminal device before the handover to the second user plane function entity.
  • the second user plane function entity is configured to serve the current session.
  • the process of establishing the current session in this embodiment of this application includes a process of initially establishing the current session and a process of re-establishing a session to the current session.
  • Step 200b The session management function entity 110 determines a location report granularity of the terminal device based on the session service area, where the location report granularity is used to indicate a range for a mobility management function entity 120 to report location information of the terminal device to the session management function entity 110.
  • Step 200c The session management function entity 110 sends the location report granularity to the mobility management function entity 120, and the mobility management function entity 120 receives the location report granularity.
  • Step 200d The mobility management function entity 120 performs step 210a if determining that second location information of the terminal device is not within the location report granularity.
  • the mobility management function entity 120 determines that the second location information of the terminal device is within the location report granularity, this procedure ends, and the mobility management function entity 120 no longer sends the second location information of the terminal device to the session management function entity 110.
  • Step 210a The mobility management function entity 120 sends the second location information of the terminal device to the session management function entity 110.
  • Step 220a After receiving the second location information of the terminal device sent by the mobility management function entity 120, if determining that the second location information is not within the session service area, the session management function entity 110 instructs the terminal device to initiate a re-establishment procedure for the current session.
  • the session management function entity 110 determines that the second location information is within the session service area, this procedure ends, and the session management function entity 110 no longer instructs the terminal device to initiate the re-establishment procedure for the current session.
  • use of the location report granularity reduces a quantity of signaling for the mobility management function entity to report location information of the terminal device to the session management function entity. Therefore, the mobility management function entity does not need to report location information of the terminal device to every session function entity each time the mobility management function receives the location information of the terminal.
  • step 200a, step 210a, and step 220a refer to the implementations of the method for initiating user plane path re-establishment shown in FIG. 2a . Details are not described herein again.
  • the session management function entity 110 may determine the location report granularity of the terminal device based on the session service area in the following manners.
  • the session management function entity obtains at least one location report requirement, where the at least one location report requirement includes at least one piece of area information, and the at least one piece of area information is used to indicate a range in which the terminal device needs to report location information; and then, the session management function entity determines the location report granularity based on the session service area and the at least one piece of area information, where the location report granularity is an intersection of the session service area and the at least one piece of area information.
  • a PDU session is used as an example.
  • the session management function entity may further need to consider other location report requirements.
  • a charging requirement also requires that the mobility management function entity report the location information of the terminal device.
  • the session management function entity selects a finest report granularity of these requirements as the location report granularity for the PDU session.
  • area information of the charging requirement is one TAI. If the session service area is one group of TAIs, a location report granularity defined by the session management function entity is one TAI instead of one group of TAIs of the session service area.
  • the session management function entity may obtain at least one location report requirement for the terminal device from at least one of other network element devices, or the session management function entity may locally generate at least one location report requirement based on a requirement of the session management function entity.
  • the other network element devices are devices different from a network element device on which the session management function entity is located.
  • the session management function entity determines the location report granularity based on only the session service area.
  • the location report granularity is usually not larger than a range of the session service area.
  • a specific relationship between the location report granularity and a size of the session service area may be determined according to a preset policy.
  • an embodiment of this application provides another method for initiating user plane path re-establishment.
  • Step 220a in the method for initiating user plane path re-establishment shown in FIG. 2a is replaced by step 400 in the method for initiating user plane path re-establishment shown in FIG. 4a , and other steps in FIG. 4a are the same as the other steps in FIG. 2a . Therefore, for specific implementations of the method for initiating user plane path re-establishment shown in FIG. 4a , refer to the specific implementations of the method for initiating user plane path re-establishment shown in FIG. 2a . Details are not described herein again.
  • an embodiment of this application further provides a method for initiating user plane path re-establishment.
  • Step 220a in the method for initiating user plane path re-establishment shown in FIG. 2b is replaced by step 400 in the method for initiating user plane path re-establishment shown in FIG. 4b , and other steps in FIG. 4b are the same as the other steps in FIG. 2b . Therefore, for specific implementations of the method for initiating user plane path re-establishment shown in FIG. 4b , refer to the specific implementations of the method for initiating user plane path re-establishment shown in FIG. 2b . Details are not described herein again.
  • the session management function entity 110 initiates a handover procedure.
  • the handover procedure is used to switch from the user plane function entity serving the current session to a target user plane function entity, and the target user plane function entity is configured to serve a session of the terminal device after the handover procedure is completed.
  • step 200a in the methods for initiating user plane path re-establishment shown in FIG. 4a and FIG. 4b , when the first location information is location information of the terminal device received in a process of handover from the first user plane function entity to the second user plane function entity, the user plane function entity serving the current session in the handover procedure initiated by session management function entity 110 in step 400 is the second user plane function entity.
  • the user plane function entity serving the current session in the handover procedure initiated by the session management function entity 110 in step 400 is a user plane function entity that serves the current session after the current session is established.
  • the user plane function entities may be PDU session anchor UPFs.
  • the first user plane function entity, the second user plane function entity, the target user plane function entity, the user plane entity serving the current session, and the like in the procedures of initiating user plane path re-establishment shown in FIG. 2a , FIG. 2b , FIG 4a and FIG. 4b in the embodiments of this application are different PDU session anchor UPFs.
  • a PDU session is used as an example.
  • the user plane function entities are PDU session anchor UPFs
  • due to introduction of the session service area in the embodiments of this application when the terminal device moves back and forth at edges of an area 1 and an area 2 shown in FIG. 5 , a ping-pong effect caused by frequent handover between two anchor UPFs is avoided.
  • the area 1 is a service area of one anchor UPF
  • the area 2 is a service area of another anchor UPF.
  • an embodiment of this application further provides another method for modifying a user plane path, including the following steps.
  • Step 600 A mobility management function entity 120 sends first location information of a terminal device to a session management function entity, and the session management function entity 110 receives the first location information of the terminal device sent by the mobility management function entity 120.
  • Step 610 After receiving the first location information of the terminal device sent by the mobility management function entity 120, the session management function entity 110 performs step 620 if determining that the first location information is not within a first service area, where the first service area is a service area of a first user plane function entity, and the first user plane function entity is configured to serve a current session of the terminal device.
  • this procedure ends. In other words, the session management function entity 110 no longer performs step 620 and subsequent steps.
  • Step 620 The session management function entity 110 selects a first target user plane function entity based on the first location information, where the first target user plane function entity serves a session of the terminal device through a modified user plane path.
  • Step 630 The session management function entity 110 initiates a user plane path modification procedure for the current session.
  • Step 640 The session management function entity 110 establishes a forwarding tunnel after determining that the first user plane function entity has buffered data, where the forwarding tunnel is a tunnel between the first target user plane function entity and the first user plane function entity, so that the first user plane function entity sends the buffered data to the first target user plane function entity through the forwarding tunnel.
  • Step 650 The session management function entity 110 deletes the forwarding tunnel after receiving a flag that is sent by the first user plane function entity and that indicates completion of sending the buffered data; or the session management function entity 110 starts a forwarding timer after establishing the forwarding tunnel, and deletes the forwarding tunnel after preset duration of the forwarding timer expires.
  • step 640 and step 650 in the method for initiating user plane path modification shown in FIG. 6 are not mandatory.
  • only step 600 to step 630 may be performed, or only step 600 to step 640 may be performed, or only step 600 to step 640 may be performed.
  • steps may be determined based on actual requirements. For example, when the first user plane function entity has no buffered data, only step 600 to step 630 may be performed.
  • the session management function entity serves current sessions of a plurality of terminal devices, and when some of the terminal devices move out of corresponding user plane function entities serving their current sessions, the session management function entity initiates user plane path modification procedures for the current sessions of these terminal devices, without the need of considering user plane path modification procedures for current sessions of other terminal devices among the current sessions of the plurality of terminal device.
  • a location report granularity may be further added, to decrease a quantity of messages that the mobility management function entity needs to report.
  • the session management function entity 110 determines a location report granularity of the terminal device based on the first service area, and sends the location report granularity to the mobility management function entity 120.
  • the location report granularity is used to instruct the mobility management function entity 120 to report a range of location information of the terminal device to the session management function entity 110.
  • the mobility management function entity 120 determines whether the first location information of the terminal device is within the location report granularity of the terminal device. If the mobility management function entity 120 determines that the first location information is within the location report granularity of the terminal device, this procedure ends. If the mobility management function entity 120 determines that the first location information of the terminal device is not within the location report granularity, the mobility management function entity 120 performs step 600.
  • the session management function entity may determine the location report granularity of the terminal device based on only the first service area. For example, the location report granularity is set to the first service area or a multiple of the first service area, for example, 0.5 times the first service area. A specific multiple may be correspondingly set based on a mobility pattern of the terminal, for example, a moving speed and a moving range, or may be preconfigured. This is not limited herein. Generally, the location report granularity is not larger than the first service area.
  • the session management function entity determines, based on second location information of the terminal device, a session service area to which the current session belongs, where the second location information is location information of the terminal device received by the session management function entity in a process of establishing the current session of the terminal device or in a process of handover from a second user plane function entity to a third user plane function entity, the second user plane function entity is configured to serve a session of the terminal device before the handover to the third user plane function entity, and the third user plane function entity is configured to serve the current session. Then, the session management function entity determines the location report granularity of the terminal device based on the first service area and the session service area, where the location report granularity is not larger than an intersection area of the first service area and the session service area.
  • the first user plane function entity may be an N3 UPF
  • the second user plane function entity and the third user plane function entity may be anchor UPFs.
  • an anchor UPF stays unchanged. Therefore, this manner for determining the location report granularity is applicable to a PDU session in an SSC mode 2 or an SSC mode 3.
  • the session management function entity obtains at least one location report requirement, where the at least one location report requirement includes at least one piece of area information, and the at least one piece of area information is used to indicate a range in which the terminal device needs to report location information. Then, the session management function entity determines the location report granularity based on the first service area and the at least one piece of area information, where the location report granularity is an intersection of the first service area and the at least one piece of area information.
  • the session management function entity may obtain at least one location report requirement from other network element devices, or may generate at least one location report requirement based on a requirement of the session management function entity.
  • a charging requirement also requires that the mobility management function entity report the location information of the terminal device.
  • the session management function entity selects a finest report granularity of these requirements as the location report granularity for the PDU session.
  • the second specific implementation for determining the location report granularity and the third specific implementation for determining the location report granularity may be combined, to determine the location report granularity.
  • the location report granularity is determined based on the first service area, a session service area, and at least one piece of area information. In this case, the location report granularity is not larger than an intersection of the first service area, the session service area, and the at least one piece of area information.
  • FIG. 7 shows a communications system.
  • the communications system shown in FIG. 7 is a specific implementation form of the communications system shown in FIG. 1 .
  • the communications system shown in FIG. 7 includes an AMF, an SMF, a UPF, a policy control function (Policy Control function, PCF), a UDM, an authentication server function (Authentication Server Function, AUSF), and a radio access network (Radio Access Network, RAN).
  • the RAN is also referred to as an AN or a data network (Data Network, DN).
  • an N3 UPF and an anchor UPF in the communications system shown in FIG. 7 are integrated into one physical device as different logical function modules and are configured to serve a current PDU session of a terminal device. Therefore, one UPF is used for illustration in FIG. 7 . However, it should be noted that the N3 UPF and the anchor UPF may be alternatively integrated into different physical devices, respectively.
  • the terminal device is connected to the AMF through N1, the AMF is connected to the RAN through N2, the N3 UPF is connected to the RAN through N3, the SMF is connected to the N3 UPF and the anchor UPF through N4, the anchor UPF is connected to the DN through N6, the SMF is connected to the PCF through N7, and the AMF is connected to the UDM through N8.
  • An interface between UPFs is N9, and specifically an interface between the N3 UPF and the anchor UPF, an interface between N3 UPFs, and an interface between anchor UPFs are all N9.
  • the SMF is connected to the UDM through N10, the AMF is connected to the SMF through N11, the AUSF is connected to the AMF through N12, the AUSF is connected to the UDM through N13, the AMF is connected to another AMF through N14, and the AMF is connected to the PCF through N15.
  • the session management function entity in the methods for initiating user plane path re-establishment shown in FIG. 2a and FIG. 2b or FIG. 4a and FIG. 4b in the embodiments of this application is equivalent to the SMF shown in FIG. 7
  • the mobility management function entity in the methods for initiating user plane path re-establishment shown in FIG. 2a and FIG. 2b or FIG. 4a and FIG. 4b in the embodiments of this application is equivalent to the AMF shown in FIG. 7
  • the user plane function entity in the methods for initiating user plane path re-establishment shown in FIG. 2a and FIG. 2b or FIG. 4a and FIG. 4b in the embodiments of this application is equivalent to the UPF shown in FICz 7.
  • the user plane function management entity in the method for initiating user plane path re-establishment shown in FIG. 2a or FIG. 2b in the embodiments of this application may be equivalent to a PDU session anchor UPF
  • the second user plane function entity and the third user plane function entity in the method for initiating user plane path re-establishment shown in FIG. 4a or FIG. 4b are equivalent to PDU session anchor UPFs
  • the first user plane function entity and the first target user plane function entity in the method for initiating user plane path re-establishment shown in FIG. 4a or FIG. 4b are equivalent to N3 UPFs.
  • the following describes the technical solution for initiating user plane path re-establishment for a PDU session in this application by using the communications system shown in FIG. 7 as an example.
  • a process of initially establishing a PDU session or re-establishing a PDU session includes the following steps.
  • Step 800 A terminal device sends a PDU session establishment request to an AMF, to initiate an establishment process for establishing a PDU session, where the PDU session establishment request may be carried in a non access stratum (Non Access Stratum, NAS) message or another message, and the PDU session establishment request includes parameter information required by a network (which is an AMF or an SMF) to establish the PDU session for the terminal device.
  • the AMF selects an SMF based on the parameter information included in the PDU session establishment request and location information of the terminal device.
  • Step 801 The AMF sends a session establishment request message to the selected SMF, where the session establishment request message includes the location information of the terminal device and the parameter information required for establishing the PDU session.
  • the location information of the terminal device is a current cell ID or TAI of the terminal device, and the location information of the terminal device is obtained from a RAN.
  • the AMF may also send a TA list to the selected SMF.
  • the SMF selects an N3 UPF and a PDU session anchor UPF based on the parameter information required for establishing the PDU session and the location information of the terminal device that are included in the session establishment request.
  • the N3 UPF and the anchor UPF are integrated into one physical device.
  • a process of establishing a tunnel between the N3 UPF and the anchor UPF needs to be added to the PDU session establishment procedure. For a specific process, refer to the prior art. Details are not described in this embodiment of this application.
  • Step 802 The SMF obtains PDU session-related subscription information of the terminal device from a UDM.
  • Step 803 The SMF obtains PDU session-related policy information of the terminal device from a PCF.
  • Step 804 The SMF generates an N4 message based on the obtained PDU session-related subscription information and policy information of the terminal device, sends the N4 message to a UPF, to create a user plane resource required for the PDU session, and configures, for the UPF, information required for the PDU session, such as a forwarding rule and a reporting rule.
  • Step 805 For a PDU session in an SSC mode 1, the SMF determines, based on a service area of a selected N3 UPF, a location report granularity for the PDU session; and for a PDU session in an SSC mode 2 or an SSC mode 3, the SMF determines a PDU session service area (PSSA for short) based on the location information of the terminal device included in the session establishment request message, and then determines, based on a service area of an N3 UPF and the PSSA, a location report granularity for the PDU session of the terminal device. The SMF stores the determined location report granularity.
  • PSSA PDU session service area
  • the SMF may also need to consider other requirements such as a charging requirement. If another requirement, for example, a charging requirement, also requires that the AMF report the location information of the terminal device, the SMF selects a finest report granularity of these requirements as the location report granularity for the PDU session. For example, when a charging requirement requires that the PDU session be charged by TAI, a report granularity defined based on a charging policy is one TAI. If the service area of the N3 UPF is one group of TAIs, the location report granularity defined by the SMF is one TAI instead of one group of TAIs of the service area of the UPF.
  • the SMF determines the location report granularity based on only the service area of the N3 UPF. Assuming that the service area of the N3 UPF is a subset of the TA list, the report granularity is the service area of the UPF. In this case, when the terminal device moves out of the service area of the N3 UPF, the AMF reports new location information of the terminal device to the SMF.
  • Step 806 The SMF generates a session establishment response message based on the location report granularity, and sends the session establishment response message to the AMF, where the session establishment response message includes the location report granularity and an N2 message, and the N2 message includes an SM N2 message and an SM NAS message.
  • Step 807 After receiving the session establishment response message, the AMF obtains and stores the location report granularity, generates a PDU session establishment response, and sends the PDU session establishment response NAS message and the SM N2 message to a RAN.
  • the AMF generates the PDU session establishment response based on the SM NAS received from the SMF, and sends, to an AN, both the PDU session establishment response and the SM N2 information received from the SMF.
  • the PDU session establishment response may be carried in a NAS message or other messages.
  • Step 808 The RAN configures an RRC link based on the SM N2 information message, and sends a PDU session establishment response to the terminal device.
  • Step 809 The RAN sends an N2 message to the AMF, where the N2 message includes an SM N2 message, and the SM N2 information includes N3 downlink tunnel information of the RAN.
  • Step 810 The AMF forwards the SM N2 information to the SMF.
  • Step 811 The SMF updates the UPF.
  • Step 812 The SMF sends a response message to the AMF.
  • FIG. 9 shows a user plane path switching method in an Xn handover procedure by using a PDU session in an SSC mode 1 as an example.
  • an original user plane path of a terminal device is terminal device ⁇ S-RAN (source RAN) ⁇ N3 UPF1 ⁇ anchor UPF
  • the user plane path switching method in an Xn handover procedure shown in FIG. 9 includes the following steps.
  • Step 900 After determining that the terminal device needs to be handed over to a T-RAN (target RAN), the S-RAN performs the Xn-based handover procedure between the S-RAN and the T-RAN.
  • the Xn-based handover procedure may include context transfer, data forwarding, and the like.
  • the T-RAN initiates an N3 tunnel update process after the handover is completed.
  • Step 901 The T-RAN sends an N2 message to an AMF.
  • the N2 message includes current cell information and/or a current TAI of the terminal device.
  • the N2 message also carries SM N2 information, and the SM N2 information includes downlink tunnel information of the T-RAN corresponding to all active PDU sessions.
  • Step 902 After receiving the N2 message, the AMF determines that the SM N2 information has included the downlink tunnel information of the T-RAN corresponding to all active PDU sessions, and sends path update messages to SMFs corresponding to all the PDU sessions included in the SM N2 information, where the path update message includes a current location, for example, the cell ID and/or the TAI, of the terminal device.
  • the AMF determines that the SM N2 information has included the downlink tunnel information of the T-RAN corresponding to all active PDU sessions, and sends path update messages to SMFs corresponding to all the PDU sessions included in the SM N2 information, where the path update message includes a current location, for example, the cell ID and/or the TAI, of the terminal device.
  • the AMF determines, based on a location report granularity for each PDU session that is not included in the SM N2 message and corresponding current location information of the terminal device, whether to send a location update notification message for the terminal device to a corresponding SMF.
  • the AMF sends a session update notification message to each SMF to which a location update notification message needs to be sent, and sends, to the corresponding SMF, the current location information, for example, the cell ID or the TAI, of the terminal device.
  • Step 903 The SMF determines, based on the current location information of the terminal device and a service area of the N3 UPF1 for the PDU session, whether user plane path modification is required, for example, whether to add a new N3 UPF, switch an N3 UPF, or delete an N3 UPF from the original user plane path.
  • the anchor UPF (that is, a PDU session anchor UPF) stays unchanged.
  • the SMF determines that a new N3 UPF is required, the SMF selects a new N3 UPF (corresponding to an N3 UPF2 in the figure) based on information such as the location of the UE.
  • a new N3 UPF (corresponding to an N3 UPF2 in the figure) based on information such as the location of the UE.
  • an actual procedure is deleting the N3 UPF1 in the original user plane path.
  • an actual procedure is adding the N3 UPF2 to the user plane path.
  • Step 904 The SMF sends, to an N3 UPF2, a message to establish a user plane path (the user plane path is an N9 tunnel and an N3 tunnel).
  • the SMF establishes only an N9 tunnel and an N3 uplink tunnel.
  • the SMF establishes an N9 tunnel and an N3 tunnel (including an uplink and a downlink).
  • Step 905 The SMF instructs the anchor UPF to update the user plane path.
  • Step 906 If the SMF selects a new N3 UPF (for example, the N3 UPF2 shown in FIG. 9 , which means that N3 UPF switching has been performed) for the PDU session, the SMF determines a new location report granularity based on a service area of the N3 UPF2. The SMF sends a session update response message to the AMF, where the session update response message includes the new location report granularity.
  • a new N3 UPF for example, the N3 UPF2 shown in FIG. 9 , which means that N3 UPF switching has been performed
  • the session update response message further carries an SM N2 message
  • the SM N2 message includes N3 uplink tunnel information of the N3 UPF2 corresponding to the PDU session.
  • Step 907 For a PDU session for which N3 tunnel switching is required, the AMF sends, to the T-RAN, an SM N2 message sent by the SMF.
  • Step 908 The SMF initiates a PDU session for deleting the N3 UPF1.
  • a user plane path after the switching is terminal device ⁇ T-RAN ⁇ N3 UPF2 ⁇ anchor UPF.
  • the user plane path switching method shown in FIG. 9 is also applicable to other connected-mode-based handover procedures, for example, an N2-based handover procedure.
  • FIG. 10 shows a user plane path switching procedure in a registration procedure.
  • a PDU session in an SSC mode 1 in the communications system shown in FIG. 7 is used as an example.
  • a type of a specific registration procedure in this embodiment may be periodic registration, or location update registration triggered by moving of the terminal device.
  • the user plane switching procedure shown in FIG. 10 includes the following steps.
  • Step 1000 The terminal device sends a registration request to an AMF, where a type of the registration request may be a periodic registration request or a location update registration request.
  • the registration request may be carried in a NAS message or other messages.
  • a RAN selects an AMF based on a temporary ID of the terminal device, and sends the registration request and current location information (for example, a cell ID and/or a TAI) of the terminal device to the AMF.
  • the terminal device may request activation of some or all PDU sessions by using the registration request.
  • Step 1001 If determining that real ID information of the terminal device is not stored, the AMF requests ID information from the terminal device.
  • Step 1002 The AMF initiates an authentication procedure based on a requirement of the AMF.
  • Step 1003 The AMF sends a location update request to a UDM, registers the AMF as a serving AMF for the terminal device, and obtains user subscription data from the UDM.
  • Step 1004 If the terminal device requests activation of a PDU session by using the registration request, the AMF sends a session update request message to an SMF corresponding to the PDU session for which activation has been requested, where the session update request message includes the location information, for example, the cell ID and/or the TAI, of the terminal device.
  • the AMF checks corresponding location report granularity information of the terminal device and current location information of the terminal device. If the terminal device has currently moved out of a subscribed-to location report granularity for the session, the AMF sends a session update request to the SMF, and the AMF sends a current location (for example, the cell ID and/or the TAI) of the terminal device to the SMF by using this message.
  • a current location for example, the cell ID and/or the TAI
  • Step 1005 The SMF determines, based on the current location information of the terminal device and a service area of an N3 UPF1 for the PDU session, whether user plane path modification is required, for example, whether to add a new N3 UPF, switch an N3 UPF, or delete an original N3 UPF from a path.
  • the SMF determines that a new N3 UPF needs to be selected, the SMF selects a new N3 UPF (an N3 UPF2 shown in FIG. 10 ) based on information such as the location information of the terminal device.
  • a new N3 UPF an N3 UPF2 shown in FIG. 10
  • an actual procedure is deleting the N3 UPF1 from the path.
  • an actual procedure is adding the N3 UPF2 to the path.
  • Step 1006 The SMF sends an N4 message to an N3 UPF2, to establish a user plane path (the user plane path is N3 and N9 tunnels). For a PDU session that does not need to be activated, the SMF establishes only an N9 tunnel and an N3 uplink tunnel. For a PDU session that needs to be activated, the SMF establishes an N9 tunnel and N3 uplink and downlink tunnels.
  • Step 1007 The N3 UPF2 sends an N4 response message to the SMF.
  • Step 1008 The SMF instructs an anchor UPF to update the user plane path.
  • Step 1009 The anchor UPF sends an N4 response message to the SMF.
  • Step 1010 Perform other steps of the registration procedure. For example, the SMF determines a new location report granularity based on the new N3 UPF (namely, the N3 UPF2) for the PDU session, and the SMF sends the new location report granularity for the PDU session to the AMF. For a PDU session that needs to be activated, the SMF establishes an N3 tunnel for the UE.
  • the new N3 UPF namely, the N3 UPF2
  • FIG. 11 shows a user plane path switching procedure upon a service request of a terminal device.
  • a PDU session in an SSC mode 1 in the communications system shown in FIG. 7 is used as an example.
  • the procedure specifically includes the following steps.
  • Step 1100 The terminal device sends a service request to an AMF.
  • a RAN adds current location information, for example, a cell ID and/or a TAI, of the terminal device to the service request.
  • the service request may be carried in a NAS message or other messages. This is not limited herein.
  • Step 1101 The AMF performs authentication on the terminal device based on a requirement of the AMF.
  • Step 1102 If the terminal device requests activation of one or more PDU sessions by using the service request, the AMF sends a session update request to an SMF corresponding to the PDU session, and the AMF sends the current location information of the terminal device to the SMF by using the session update request.
  • the AMF checks location report granularities for other PDU sessions of the terminal device that do not need to be activated. If the current location information of the terminal device has moved out of ranges of the subscribed-to location report granularities, the AMF sends session update requests to SMFs corresponding to these PDU sessions, to send the current location information (for example, the cell ID and/or the TAI) of the terminal device to the SMFs.
  • the AMF sends session update requests to SMFs corresponding to these PDU sessions, to send the current location information (for example, the cell ID and/or the TAI) of the terminal device to the SMFs.
  • Step 1103 Upon receiving the current location information of the terminal device, the SMF determines, based on the current location information of the terminal device and a service area of an N3 UPF1, whether to add a new N3 UPF, delete an N3 UPF, or switch an N3 UPF for a user plane path. If the SMF determines that a new N3 UPF is required, the SMF selects an N3 UPF2 based on information such as the location of the terminal device.
  • Step 1104 The SMF sends an N4 message to the N3 UPF2, to establish an N9 tunnel between the N3 UPF2 and an anchor UPF. For a PDU session that does not need to be activated, the SMF establishes only an N9 tunnel and an N3 uplink tunnel. For a PDU session that needs to be activated, the SMF establishes an N9 tunnel and N3 uplink and downlink tunnels. If the service request is network-triggered, for the PDU session that needs to be activated, the N4 message is also used to establish a forwarding tunnel between the N3 UPF1 and the N3 UPF2.
  • Step 1105 The N3 UPF2 sends an N4 response message to the SMF.
  • Step 1106 The SMF sends an N4 message to the anchor UPF, to update the user plane path (the N9 tunnel) for the PDU session.
  • Step 1107 The anchor UPF sends an N4 response message to the SMF.
  • Step 1108 If the service request is network-triggered, the SMF sends an N4 message to the N3 UPF1, to establish a forwarding tunnel between the N3 UPF1 and the N3 UPF2, where the N4 message is also used to delete an N9 tunnel between the N3 UPF1 and the anchor UPF.
  • Step 1109 The N3 UPF1 sends an N4 response message to the SMF.
  • Step 1110 If an N3 UPF change has occurred, the SMF determines a new location report granularity for the PDU session based on a service range of a new N3 UPF (for example, the N3 UPF2 in FIG. 11 ).
  • the SMF sends a session update response message to the AMF, where the message includes the new location report granularity for the PDU session.
  • the message further includes SM N2 information, and the SM N2 information includes N3 uplink tunnel information of the N3 UPF2.
  • steps 1112 to 1118 do not need to be performed.
  • Step 1111 The AMF sends an N2 message to the RAN, where the N2 message includes an SM N2 message sent by the SMF.
  • Step 1112 The RAN performs RRC reconfiguration with the terminal device, to allocate a resource to the PDU session that is just activated. Uplink data is sent from the RAN to the N3 UPF2.
  • Step 1113 The RAN sends an N2 response message to the AMF, where the N2 response message carries SM N2 information, and the SM N2 message includes N3 downlink tunnel information of the RAN.
  • Step 1114 The AMF sends an N11 message to the SMF, where the N11 message includes the SM N2 information sent by the RAN.
  • Step 1115 The SMF updates a session policy.
  • Step 1116 The SMF sends an N4 message to the N3 UPF2, to update an N3 tunnel of the N3 UPF2. Downlink data is sent from the N3 UPF2 to the RAN, and downlink forwarding data is sent from the N3 UPF1 to the RAN by using the N3 UPF2.
  • Step 1117 The N3 UPF1 sends a completion flag to the SMF after sending a last piece of buffered data is completed.
  • the SMF sends a forwarding tunnel deletion request-N4 message to the N3 UPF1 and the N3 UPF2, to instruct the N3 UPF1 and the N3 UPF2 to delete the forwarding tunnel.
  • the SMF sets a forwarding timer locally, and after the forwarding timer expires, the SMF sends a forwarding tunnel deletion request-N4 message to the N3 UPF1 and the N3 UPF2, to instruct the N3 UPF1 and the N3 UPF2 to delete the forwarding tunnel.
  • the N3 UPF1 and the N3 UPF2 After receiving the forwarding tunnel deletion request, the N3 UPF1 and the N3 UPF2 delete the forwarding tunnel; and the N3 UPF1 and the N3 UPF2 each send a forwarding tunnel deletion response to the SMF, to notify the SMF of completion of deleting the forwarding tunnel.
  • the forwarding tunnel deletion request and the forwarding tunnel deletion response may be carried in N4 messages or other messages. This is not limited herein.
  • Step 1118 The SMF sends an N11 response message to the AMF. Step 1118 may be performed previous to step 1117.
  • FIG. 12 shows a PDU session re-establishment procedure.
  • a PDU session in an SSC mode 2 or an SSC mode 3 in the communications system shown in FIG. 7 is used as an example.
  • an SMF determines a PDU session service area (also referred to as a PSSA) based on after-move location information of the terminal device.
  • a PDU session service area also referred to as a PSSA
  • the PDU session re-establishment procedure includes the following steps:
  • Step 1200 Before the terminal device moves, a PDU session anchor of the terminal device is an anchor UPF1. After the terminal device moves, a procedure such as a re-registration procedure or a handover procedure may be triggered, and the terminal device, whether in an idle mode or a connected mode, may initiate a service request (Service request, SR) process to trigger activation of a PDU session.
  • a service request Service request, SR
  • Step 1201 In the re-registration procedure or the handover procedure, an AMF determines, based on a location report granularity of the terminal device, whether to notify an SMF of location information of the terminal device. If the AMF determines to notify an SMF of location information of a terminal device after determining a location report granularity for a PDU session of the terminal device, the AMF sends the location information of the terminal device to the SMF. The location information of the terminal device may be sent together with other N11 messages to the SMF.
  • Step 1202 The SMF determines whether the location information of the terminal device is within the PSSA for the PDU session, to determine whether to initiate a PDU session re-establishment procedure.
  • the SMF performs step 1203 if determining to instruct the terminal device to initiate a PDU session re-establishment procedure.
  • the PDU session re-establishment procedure means establishing a PDU session in a same data network.
  • Step 1203 The SMF sends a NAS message to the terminal device, to instruct the UE to initiate PDU session re-establishment, where the NAS message is sent by using the AMF.
  • Step 1204 The terminal device initiates PDU session re-establishment after receiving the NAS message sent by the SMF.
  • An anchor for a new PDU session is an anchor UPF2.
  • the terminal device releases an original PDU session before the PDU session re-establishment.
  • the terminal device releases an original PDU session based on a requirement after the new PDU session is established.
  • the embodiments of this application further provide apparatuses for initiating user plane path re-establishment shown in FIG. 13a and shown in FIG. 14a .
  • the apparatus shown in FIG. 13a in the embodiments of this application is corresponding to the methods for initiating user plane path re-establishment shown in FIG. 2a and FIG. 2b in the embodiments of this application. Therefore, for implementations of the apparatus shown in FIG. 13a in the embodiments of this application, refer to the implementations of the methods for initiating user plane path re-establishment shown in FIG. 2a and FIG. 2b . Details are not described herein again.
  • FIG. 14a in the embodiments of this application is corresponding to the methods for initiating user plane path re-establishment shown in FIG. 4a and FIG. 4b in the embodiments of this application. Therefore, for implementations of the apparatus shown in FIG. 14a in the embodiments of this application, refer to the implementations of the methods for initiating user plane path re-establishment shown in FIG. 4a and FIG. 4b . Details are not described herein again.
  • an embodiment of this application provides an apparatus for initiating user plane path re-establishment, including a processing module 13 10a and a receiving module 1320a.
  • the processing module 1310a is configured to determine, based on first location information of a terminal device, a session service area to which a current session of the terminal device belongs.
  • the first location information is location information of the terminal device received by a session management function entity in a process of establishing the current session or in a process of handover from a first user plane function entity to a second user plane function entity.
  • the first user plane function entity is configured to serve a session of the terminal device before the handover to the second user plane function entity.
  • the second user plane function entity is configured to serve the current session.
  • the receiving module 1320a is configured to receive second location information of the terminal device sent by a mobility management function entity.
  • the processing module 1310a is further configured to: when determining that the second location information received by the receiving module is not within the session service area, instruct the terminal device to initiate a re-establishment procedure for the current session or initiate a handover procedure.
  • the handover procedure is used to switch from the user plane function entity serving the current session to a target user plane function entity.
  • the target user plane function entity is configured to serve a session of the terminal device after the handover procedure is completed.
  • the session service area includes a service area of the user plane function entity serving the current session.
  • the processing module 13 10a is configured to: when determining that the second location information is neither within the session service area nor within the service area of the user plane function entity serving the current session, instruct the terminal device to initiate a re-establishment procedure for the current session or initiate a handover procedure.
  • the processing module 1310a may determine the session service area in the following implementation manner: using the first location information of the terminal device as a center, to determine a center location of the session service area; and determining a size of the session service area.
  • the processing module 1310a may determine the size of the session service area in the following manner: determining the size of the session service area based on the service area of the user plane function entity serving the current session and/or based on a mobility pattern of the terminal device, where the mobility pattern includes at least one of a moving range of the terminal device, a moving speed of the terminal device, and a moving track of the terminal device.
  • the processing module 1310a determines a location report granularity of the terminal device based on the session service area, where the location report granularity is used to indicate a range for the mobility management function entity to report location information of the terminal device to the session management function entity; and a sending module 1330 of the apparatus sends the location report granularity determined by the processing module to the mobility management function entity.
  • the processing module 1310a obtains at least one location report requirement, where the at least one location report requirement includes at least one piece of area information, and the at least one piece of area information is used to indicate a range in which the terminal device needs to report location information; and then determines the location report granularity based on the session service area and the at least one piece of area information, where the location report granularity is an intersection of the session service area and the at least one piece of area information.
  • a hardware structure of the apparatus may be a session management function device shown in FIG. 13b .
  • the processing module 1310a shown in FIG. 13a may be implemented by a processor 1310b, and the receiving module 1320a and the sending module 1330a may be implemented by a communications interface 1320b.
  • the session management function device shown in FIG. 13b further includes a memory 1330b.
  • the memory 1330b is configured to store a software program, data information sent and received through the communications interface 1320b, and the like.
  • the processor 1310b is configured to: read the software program and the data that are stored in the memory 1330b, and implement the method shown in FIG. 2a or FIG. 2b in the embodiments of this application.
  • the processor 1310b may be a general-purpose central processing unit (Central Processing Unit, CPU), a microprocessor, an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is configured to perform related operations, to implement the technical solutions provided in the embodiments of this application.
  • CPU Central Processing Unit
  • ASIC Application-Specific Integrated Circuit
  • the session management function device also includes other components mandatory for implementing normal running. Further, based on a specific requirement, a person skilled in the art should understand that the session management function device may further include hardware components for implementing other additional functions. In addition, a person skilled in the art should understand that the session management function device may alternatively include only components or modules mandatory for implementing the embodiments of this application, instead of including all components shown in FIG. 13b .
  • a person of ordinary skill in the art may understand that all or some of the processes of the methods in the embodiments may be implemented by a computer program instructing related hardware.
  • the program may be stored in a computer readable storage medium. When the program runs, the processes of the methods in the embodiments are performed.
  • the foregoing storage medium may include a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM).
  • an embodiment of this application provides an apparatus for initiating user plane path re-establishment, including a processing module 1410a and a receiving module 1420a.
  • the receiving module 1420a is configured to receive first location information of a terminal device sent by a mobility management function entity.
  • the processing module 1410a is configured to: when determining that the first location information received by the receiving module 1420a is not within a first service area, select a first target user plane function entity based on the first location information, and initiate a user plane path re-establishment procedure for a current session.
  • the first service area is a service area of a first user plane function entity
  • the first user plane function entity is configured to serve the current session of the terminal device
  • the first target user plane function entity serves a session of the terminal device through a re-established user plane path.
  • the processing module 1410a determines a location report granularity of the terminal device based on the first service area, where the location report granularity is used to indicate a range for the mobility management function entity to report location information of the terminal device to a session management function entity; and a sending module 1430a of the apparatus is configured to send the location report granularity to the mobility management entity.
  • the processing module 1410a determines, based on second location information of the terminal device, a session service area to which the current session belongs, and determines the location report granularity of the terminal device based on the first service area and the session service area, where the second location information is location information of the terminal device received by the session management function entity in a process of establishing the current session of the terminal device or in a process of handover from a second user plane function entity to a third user plane function entity, the second user plane function entity is configured to serve a session of the terminal device before the handover to the third user plane function entity, the third user plane function entity is configured to serve the current session, and the location report granularity is not larger than an intersection area of the first service area and the session service area.
  • the processing module 1410a obtains at least one location report requirement, where the at least one location report requirement includes at least one piece of area information, and the at least one piece of area information is used to indicate a range in which the terminal device needs to report location information; and determines the location report granularity based on the first service area and the at least one piece of area information, where the location report granularity is an intersection of the first service area and the at least one piece of area information.
  • the processing module 1410a after initiating the user plane path re-establishment for the current session, the processing module 1410a establishes a forwarding tunnel if determining that the first user plane function entity has buffered data, where the forwarding tunnel is a tunnel between the first target user plane function entity and the first user plane function entity, so that the first user plane function entity sends the buffered data to the first target user plane function entity through the forwarding tunnel.
  • the processing module 1410a deletes the forwarding tunnel after determining that the receiving module has received a flag that is sent by the first user plane function entity and that indicates completion of sending the buffered data; or starts a forwarding timer after establishing the forwarding tunnel, and deletes the forwarding tunnel after preset duration of the forwarding timer expires.
  • a hardware structure of the apparatus may be a session management function device shown in FIG. 14b .
  • the processing module 1410a shown in FIG. 14a may be implemented by a processor 1410b, and the receiving module 1420a and the sending module 1430a may be implemented by a communications interface 1420b.
  • the session management function device shown in FIG. 14b further includes a memory 1430b.
  • the memory 1430b is configured to store a software program, data information sent and received through the communications interface 1420b, and the like.
  • the processor 1410b is configured to: read the software program and the data that are stored in the memory 1430b, and implement the method shown in FIG. 2a or FIG. 2b in the embodiments of this application.
  • the processor 1410b may be a general-purpose central processing unit (Central Processing Unit, CPU), a microprocessor, an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is configured to perform related operations, to implement the technical solutions provided in the embodiments of this application.
  • CPU Central Processing Unit
  • ASIC Application-Specific Integrated Circuit
  • the session management function device also includes other components mandatory for implementing normal running. Further, based on a specific requirement, a person skilled in the art should understand that the session management function device may further include hardware components for implementing other additional functions. In addition, a person skilled in the art should understand that the session management function device may alternatively include only components or modules mandatory for implementing the embodiments of this application, instead of including all components shown in FIG. 14b .
  • a person of ordinary skill in the art may understand that all or some of the processes of the methods in the embodiments may be implemented by a computer program instructing related hardware.
  • the program may be stored in a computer readable storage medium. When the program runs, the processes of the methods in the embodiments are performed.
  • the foregoing storage medium may include a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM).
  • All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof.
  • the embodiments may be implemented completely or partially in a form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses.
  • the computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, through a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, through infrared, radio, and microwave, or the like) manner.
  • the computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid state disk Solid State Disk (SSD)), or the like.
  • a magnetic medium for example, a floppy disk, a hard disk, or a magnetic tape
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state disk Solid State Disk (SSD)
  • this application may be provided as a method, a system, or a computer program product. Therefore, this application may use a form of hardware only embodiments, software only embodiments, or embodiments with a combination of software and hardware. Moreover, this application may use a form of a computer program product that is implemented on one or more computer-usable storage media (including but not limited to a disk memory, a CD-ROM, an optical memory, and the like) that include computer usable program code.
  • a computer-usable storage media including but not limited to a disk memory, a CD-ROM, an optical memory, and the like
  • These computer program instructions may be provided for a processor of a general-purpose computer, a dedicated computer, an embedded processor, or any other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or the any other programmable data processing device generate an apparatus for implementing a specific function defined in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • These computer program instructions may alternatively be stored in a computer readable memory that can guide a computer or any other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory generate an artifact that includes an instruction apparatus.
  • the instruction apparatus implements a specific function defined in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • These computer program instructions may alternatively be loaded onto a computer or another programmable data processing device, so that a series of operations and steps are performed on the computer or the another programmable device to generate computer-implemented processing. Therefore, the instructions executed on the computer or the another programmable device provide steps for implementing a specific function defined in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

Landscapes

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

Claims (7)

  1. Procédé de déclenchement d'une modification de trajet de plan d'utilisateur, comprenant :
    l'envoi (600, 1004, 1102), par une entité de fonction de gestion de mobilité (120), de premières informations de position d'un dispositif terminal à une entité de fonction de gestion de session (110) ;
    la réception (600, 1004, 1102), par l'entité de fonction de gestion de session (110), des premières informations de position en provenance de l'entité de fonction de gestion de mobilité (120) ;
    la détermination (610, 903, 1005, 1103), par l'entité de fonction de gestion de session (110), que les premières informations de position ne se trouvent pas à l'intérieur d'une première zone de service, la première zone de service étant une zone de service d'une première entité de fonction de plan d'utilisateur servant une session du dispositif terminal ;
    en réponse à la détermination, la sélection (620, 903, 1005, 1103), par l'entité de fonction de gestion de session (110), d'une première entité de fonction de plan d'utilisateur cible sur la base des premières informations de position ; et
    le déclenchement (630, 1006, 1104), par l'entité de fonction de gestion de session (110), d'une procédure pour modifier le trajet de plan d'utilisateur pour la session, dans lequel la session est servie par la première entité de fonction de plan d'utilisateur cible par l'intermédiaire du trajet de plan d'utilisateur modifié.
  2. Procédé selon la revendication 1, comprenant en outre :
    la détermination, par l'entité de fonction de gestion de session, d'une granularité de signalement de position du dispositif terminal sur la base de la première zone de service, dans lequel la granularité de signalement de position est utilisée pour indiquer une plage pour que l'entité de fonction de gestion de mobilité signale des informations de position du dispositif terminal à l'entité de fonction de gestion de session ;
    l'envoi, par l'entité de fonction de gestion de session, de la granularité de signalement de position à l'entité de fonction de gestion de mobilité ; et
    la réception, par l'entité de fonction de gestion de mobilité, de la granularité de signalement de position en provenance de l'entité de fonction de gestion de session.
  3. Procédé selon la revendication 2, comprenant en outre :
    la détermination, par l'entité de fonction de gestion de session sur la base de secondes informations de position du dispositif terminal, d'une zone de service de session à laquelle la session appartient, dans lequel les secondes informations de position sont des informations de position du dispositif terminal reçues par l'entité de fonction de gestion de session lors d'un processus d'établissement de la session du dispositif terminal ou lors d'un processus de transfert depuis une deuxième entité de fonction de plan d'utilisateur à une troisième entité de fonction de plan d'utilisateur, la deuxième entité de fonction de plan d'utilisateur est configurée pour servir une session du dispositif terminal avant le transfert à la troisième entité de fonction de plan d'utilisateur, et la troisième entité de fonction de plan d'utilisateur est configurée pour servir la session ; et
    la détermination, par l'entité de fonction de gestion de session, de la granularité de signalement de position du dispositif terminal sur la base de la première zone de service comprend :
    la détermination, par l'entité de fonction de gestion de session, de la granularité de signalement de position du dispositif terminal sur la base de la première zone de service et de la zone de service de session, dans lequel la granularité de signalement de position n'est pas plus grande qu'une zone d'intersection de la première zone de service et de la zone de service de session.
  4. Procédé selon la revendication 2, comprenant en outre :
    l'obtention, par l'entité de fonction de gestion de session, d'au moins une exigence de signalement de position, dans lequel l'au moins une exigence de signalement de position comprend au moins une information de zone, et l'au moins une information de zone est utilisée pour indiquer une plage dans laquelle le dispositif terminal doit signaler des informations de position ; et
    la détermination, par l'entité de fonction de gestion de session, de la granularité de signalement de position sur la base de la première zone de service comprend :
    la détermination, par l'entité de fonction de gestion de session, de la granularité de signalement de position sur la base de la première zone de service et de l'au moins une information de zone, dans lequel la granularité de signalement de position est une intersection de la première zone de service et de l'au moins une information de zone.
  5. Procédé selon l'une quelconque des revendications 1 à 4, comprenant en outre :
    l'établissement, par l'entité de fonction de gestion de session, d'un tunnel de transfert après la détermination que la première entité de fonction de plan d'utilisateur comporte des données en mémoire tampon, dans lequel le tunnel de transfert est un tunnel entre la première entité de fonction de plan d'utilisateur cible et la première entité de fonction de plan d'utilisateur et pour que la première entité de fonction de plan d'utilisateur envoie les données en mémoire tampon à la première entité de fonction de plan d'utilisateur cible par l'intermédiaire du tunnel de transfert.
  6. Procédé selon la revendication 5, comprenant en outre :
    le démarrage, par l'entité de fonction de gestion de session, d'un minuteur de transfert après l'établissement du tunnel de transfert, et la suppression du tunnel de transfert après l'expiration d'une durée prédéfinie du minuteur de transfert.
  7. Procédé selon la revendication 5, comprenant en outre :
    la suppression, par l'entité de fonction de gestion de session, du tunnel de transfert après la réception d'un indicateur provenant de la première entité de fonction de plan d'utilisateur et indiquant l'achèvement de l'envoi des données en mémoire tampon.
EP21192955.9A 2017-03-17 2018-02-23 Procédé de déclenchement de la modification de trajet dans le plan d'utilisateur d'un système de communication Active EP3979707B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201710161100.6A CN108696822B (zh) 2017-03-17 2017-03-17 一种发起用户面路径重建的方法、装置及通信系统
EP18767026.0A EP3598800B1 (fr) 2017-03-17 2018-02-23 Procédé et appareil d'initialisation d'une modification de trajet de plan utilisateur et système de communication
PCT/CN2018/077025 WO2018166336A1 (fr) 2017-03-17 2018-02-23 Procédé et appareil d'initialisation d'un rétablissement de trajet de plan utilisateur et système de communication

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP18767026.0A Division EP3598800B1 (fr) 2017-03-17 2018-02-23 Procédé et appareil d'initialisation d'une modification de trajet de plan utilisateur et système de communication
EP18767026.0A Division-Into EP3598800B1 (fr) 2017-03-17 2018-02-23 Procédé et appareil d'initialisation d'une modification de trajet de plan utilisateur et système de communication

Publications (2)

Publication Number Publication Date
EP3979707A1 EP3979707A1 (fr) 2022-04-06
EP3979707B1 true EP3979707B1 (fr) 2023-10-25

Family

ID=63521714

Family Applications (2)

Application Number Title Priority Date Filing Date
EP18767026.0A Active EP3598800B1 (fr) 2017-03-17 2018-02-23 Procédé et appareil d'initialisation d'une modification de trajet de plan utilisateur et système de communication
EP21192955.9A Active EP3979707B1 (fr) 2017-03-17 2018-02-23 Procédé de déclenchement de la modification de trajet dans le plan d'utilisateur d'un système de communication

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP18767026.0A Active EP3598800B1 (fr) 2017-03-17 2018-02-23 Procédé et appareil d'initialisation d'une modification de trajet de plan utilisateur et système de communication

Country Status (7)

Country Link
US (2) US11224085B2 (fr)
EP (2) EP3598800B1 (fr)
JP (1) JP6987866B2 (fr)
KR (1) KR102231693B1 (fr)
CN (3) CN110278529B (fr)
BR (1) BR112019014020A2 (fr)
WO (1) WO2018166336A1 (fr)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102293669B1 (ko) * 2017-05-08 2021-08-25 삼성전자 주식회사 5g 셀룰러망의 세션 연속성 지원 방안
US20190007992A1 (en) * 2017-07-03 2019-01-03 Electronics And Telecommunications Research Institute Network triggered service request method and user equipment (ue) triggered service request method
CN111200849B (zh) * 2018-11-19 2022-08-09 大唐移动通信设备有限公司 一种用户路由更新方法及设备
CN111328115B (zh) * 2018-12-14 2022-03-11 大唐移动通信设备有限公司 一种数据发送方法及设备
CN111757340B (zh) * 2019-03-28 2023-04-18 华为技术有限公司 一种确定服务区域的方法、装置及系统
CN111757312A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种会话的处理方法及装置
CN112449395B (zh) * 2019-08-28 2022-09-02 中国联合网络通信集团有限公司 一种数据传输方法、核心网设备和amf
CN112449394B (zh) * 2019-08-28 2022-09-16 中国联合网络通信集团有限公司 一种数据传输方法和核心网设备
CN112584327B (zh) * 2019-09-30 2022-04-05 华为技术有限公司 一种更新用户面路径的方法、装置及系统
CN112584437B (zh) * 2019-09-30 2023-03-28 中国移动通信有限公司研究院 一种数据分流方法及装置
CN112654070B (zh) * 2019-10-12 2022-02-08 大唐移动通信设备有限公司 用户终端间的通信方法、装置、设备及存储介质
CN111277470B (zh) * 2020-02-19 2022-07-26 联想(北京)有限公司 一种用户面功能切换方法、装置、系统和存储介质
CN112291752B (zh) * 2020-11-16 2022-08-12 中国联合网络通信集团有限公司 一种网络注册方法及装置
US11451954B1 (en) * 2021-02-03 2022-09-20 Sprint Communications Company L.P. Wireless communication service delivery using multiple data network names (DNNs)
US20220408353A1 (en) * 2021-06-18 2022-12-22 Commscope Technologies Llc User plane function selection and hosting for real-time applications
CN113676986B (zh) * 2021-07-21 2024-04-09 武汉虹旭信息技术有限责任公司 获取终端位置的方法及系统
WO2023043286A1 (fr) * 2021-09-17 2023-03-23 엘지전자 주식회사 Procédé et appareil pour fournir un mbs dans un système de communication sans fil
CN117042069B (zh) * 2023-09-28 2024-02-27 新华三技术有限公司 应用于5g核心网中的路径切换方法、装置及电子设备

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039506B (zh) * 2006-03-15 2011-02-02 华为技术有限公司 一种移动管理实体/用户面实体迁移方法
CN101094509B (zh) * 2006-06-20 2010-09-08 华为技术有限公司 演进网络及用户设备锚点迁移的方法
EP1914930A1 (fr) * 2006-10-17 2008-04-23 Matsushita Electric Industrial Co., Ltd. Sélection d'une entité de plan utilisateur dans un système de communication mobile comportant des zones de réserve de chevauchement
EP1914928A1 (fr) * 2006-10-17 2008-04-23 Matsushita Electric Industrial Co., Ltd. Enregistrement d'un service de multidiffusion par des entités de gestion de la mobilité
CN103607793B (zh) * 2007-10-25 2017-08-25 思达伦特网络有限责任公司 用于移动节点的互通网关
KR101521886B1 (ko) * 2009-01-23 2015-05-28 삼성전자주식회사 이동통신 시스템에서 지티피 처리를 위한 장치 및 방법
US8971845B2 (en) * 2013-02-26 2015-03-03 Cisco Technology, Inc. Systems, methods and media for location reporting at a charging area level granularity
US9439163B2 (en) * 2013-12-23 2016-09-06 Cellco Partnership Processing of a coarse location request for a mobile device
CN106102106B (zh) * 2016-06-20 2020-03-24 电信科学技术研究院 一种终端接入的方法、装置及网络架构
WO2018038503A1 (fr) * 2016-08-22 2018-03-01 삼성전자 주식회사 Procédé et appareil d'exploitation d'un système de communication sans fil doté d'une gestion de mobilité et d'une gestion de session séparées
CN108617032B (zh) * 2017-01-09 2019-12-27 电信科学技术研究院 一种ue空闲态处理方法、mm功能实体及sm功能实体
US10448239B2 (en) * 2017-02-06 2019-10-15 Qualcomm Incorporated Mechanism to enable optimized user plane anchoring for minimization of user plane relocation due to user equipment mobility

Also Published As

Publication number Publication date
BR112019014020A2 (pt) 2020-02-11
CN110278529A (zh) 2019-09-24
CN108696822A (zh) 2018-10-23
EP3979707A1 (fr) 2022-04-06
WO2018166336A1 (fr) 2018-09-20
US20190274181A1 (en) 2019-09-05
CN110290471B (zh) 2020-06-19
EP3598800B1 (fr) 2021-10-27
US11224085B2 (en) 2022-01-11
CN110290471A (zh) 2019-09-27
US11805567B2 (en) 2023-10-31
KR20190077514A (ko) 2019-07-03
CN110278529B (zh) 2021-09-14
CN108696822B (zh) 2019-08-23
US20220086942A1 (en) 2022-03-17
JP6987866B2 (ja) 2022-01-05
EP3598800A4 (fr) 2020-02-26
KR102231693B1 (ko) 2021-03-23
JP2020502928A (ja) 2020-01-23
EP3598800A1 (fr) 2020-01-22

Similar Documents

Publication Publication Date Title
EP3979707B1 (fr) Procédé de déclenchement de la modification de trajet dans le plan d'utilisateur d'un système de communication
CN111436087B (zh) 一种pdu会话切换方法及其装置
JP2020502928A5 (fr)
EP2582177B1 (fr) Système de communication mobile, procédé de sélection de noeud de réseau de coeur et station de base et station mobile utilisées à ces fins
JP5313681B2 (ja) 移動体通信システムにおける接続再確立の方法
CN111567099B (zh) 用户装置
CN105191411B (zh) 用于改变基于接近服务的无线接入技术的方法和装置
CN109819485B (zh) 一种通信方法、装置及系统
CN101304600A (zh) 安全能力协商的方法及系统
WO2013014847A1 (fr) Système de communication sans fil, station de base, nœud de contrôle, station mobile, procédé correspondant à ces éléments, et support lisible par un ordinateur
WO2022007484A1 (fr) Procédé de redirection, dispositif de réseau, dispositif terminal et support de stockage lisible
WO2008113283A1 (fr) Procédé et équipement de suivi de signalisation
WO2012152130A1 (fr) Procédé et dispositif de traitement de support
JP2010068233A (ja) 無線通信システム、無線通信方法および無線基地局装置
CN102427599B (zh) 数据传输方法和设备
WO2018041097A1 (fr) Procédé et dispositif de commutation de réseau
JP7300538B2 (ja) アンカーポイント制御装置及びアンカーポイント制御方法
WO2012109998A1 (fr) Procédé et dispositif pour maintenir actives des connexions de délestage de trafic ip sélectionnées durant un transfert intercellulaire
WO2018001301A1 (fr) Procédé, appareil et système de commande d'équipement d'utilisateur, et passerelle de réseau
WO2015024424A1 (fr) Procédés d'activation et de désactivation d'isr
WO2018001247A1 (fr) Procédé, appareil, et système de commande d'équipement utilisateur, et passerelle de réseau
CN117837208A (zh) 一种在会话管理功能故障和重新选择之后的会话更新的方法
CN115152270A (zh) 一种用于服务连续性的方法
WO2018098788A1 (fr) Procédé et appareil de libération de support d'accès sans fil

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210825

AC Divisional application: reference to earlier application

Ref document number: 3598800

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/08 20090101ALN20230517BHEP

Ipc: H04W 36/32 20090101ALI20230517BHEP

Ipc: H04W 76/22 20180101ALI20230517BHEP

Ipc: H04W 64/00 20090101ALI20230517BHEP

Ipc: H04W 76/19 20180101ALI20230517BHEP

Ipc: H04W 36/24 20090101AFI20230517BHEP

INTG Intention to grant announced

Effective date: 20230602

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AC Divisional application: reference to earlier application

Ref document number: 3598800

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018060238

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20231025

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1625983

Country of ref document: AT

Kind code of ref document: T

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240126

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240225

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240126

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240125

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240226

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240116

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240125

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240103

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602018060238

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231025

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

26N No opposition filed

Effective date: 20240726

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20240223