WO2023079075A1 - Commande de surveillance d'usages lors de relocalisation de smf - Google Patents

Commande de surveillance d'usages lors de relocalisation de smf Download PDF

Info

Publication number
WO2023079075A1
WO2023079075A1 PCT/EP2022/080817 EP2022080817W WO2023079075A1 WO 2023079075 A1 WO2023079075 A1 WO 2023079075A1 EP 2022080817 W EP2022080817 W EP 2022080817W WO 2023079075 A1 WO2023079075 A1 WO 2023079075A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
data
entity
management entity
policy control
Prior art date
Application number
PCT/EP2022/080817
Other languages
English (en)
Inventor
Maria Belen PANCORBO MARCOS
Stefan Rommer
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023079075A1 publication Critical patent/WO2023079075A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/775—Account specifications on parallel communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/78—Redistributing amount between accounts
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention generally relates to Policy Control in mobile networks, and more specifically, the invention relates to the selection of the Policy Control Function at Session Management Function relocation.
  • 3GPP TS 23.503 clause 6.1.1.2.2 specifies that the same Policy Control Function (PCF) shall be selected for all the SM Policy associations to the same SUPI, DNN or S-NSSAI when usage monitoring applies. This is to enable having the same PCF for monitor the remaining volume/time defined for a DNN or S-NSSAI.
  • PCF selected for a SM Policy Association checks if usage monitoring applies for the DNN or S-NSSAI, then if there is already a PCF serving a PDU Session for the SUPI, DNN, or S-NSSAI, the PCF instructs the Session Management Function (SMF) to establish a SM Policy Association to the existing PCF.
  • the assumption for this procedure to work is that the Binding Support Function (BSF) selection is done using the DNN or S-NSSAI.
  • BSF Binding Support Function
  • a problematic aspect of the described procedure is that if the SMF is relocated, e.g., in Session and Service Continuity (SSC) mode 3, that may lead to a change of PCF for the PDU Session that may cause inconsistencies when usage monitoring applies.
  • SSC Session and Service Continuity
  • a further problematic aspect of the described procedure is that it fails if the BSF selection is done using the User Equipment (UE) IP address.
  • UE User Equipment
  • 3GPP TS 23.501 clause 4.3.2.2.4 Multiple PDU Sessions towards the same DNN and S- NSSAI disclose that the same SMF is selected for all PDU Sessions to the same DNN or S- NSSAI of a SUPI to facilitate the selection of the same PCF to allow usage monitoring to work properly. Then it is the SMF internal logic that ensures that the same PCF serves all PDU Sessions for a SUPI, DNN, or S-NSSAI.
  • an AMF that requires the SMF to use the PCF ID sent shall also indicate “Same PCF Selection Indication”. This indication is set only when the UDM is configured with the PCF Selection Assistance information for a DNN, S-NSSAI that the AMF mandate selecting the same PCF for UE and for PDU Session to a DNN. S-NSSAI.
  • An object of the invention is to enable usage monitoring control at SMF relocation by enabling the selection of the same PCF.
  • a first aspect of the invention relates to a method performed by a first session management entity in a communications network, the method comprises transmitting to an access and mobility management entity an identifier of a policy control entity associated with a first data session of a user.
  • the method is triggered and/or performed at a relocation of the session management entity allocated to the first data session.
  • the identifier of the policy control entity is transmitted from the first session management entity to the access and mobility management entity together with a request or indication of the session management entity relocation.
  • a second aspect of the invention relates to a method performed by a second session management entity in a communications network, the method comprises selecting at an access and mobility management entity the second session management entity for a second data session of the user; transmitting from the access and mobility management entity to the second session management entity, at establishment of the second data session, the identifier of the policy control entity; establishing a policy association for the second data session between the second session management entity and the policy control entity using the identifier of the policy control entity.
  • the method is triggered and/or performed at a relocation of the session management entity allocated to the first data session.
  • the transmitting from the access and mobility management entity to the second session management entity the identifier of the policy control entity takes place if the first data session or the second data session are with a Session and Service Continuity mode 3.
  • the policy control entity serves all the data sessions to the same data network and/or slice of the user.
  • the identifier of the policy control entity is transmitted from the access and mobility management entity to the second session management entity together with an indication that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the establishing a policy association for the second data session comprises selecting at the second session management entity the policy control entity based on the identifier of the policy control entity.
  • a third aspect of the invention relates to a method performed by an access and mobility management entity in a communications network, the method comprises receiving from a first session management entity an identifier of a policy control entity associated with a first data session of a user; selecting at the access and mobility management entity a second session management entity for a second data session of the user; transmitting from the access and mobility management entity to the second session management entity, at establishment of the second data session, the identifier of the policy control entity;
  • the method is triggered and/or performed at a relocation of the session management entity allocated to the first data session.
  • the identifier of the policy control entity is transmitted from the first session management entity to the access and mobility management entity together with a request or indication of the session management entity relocation. ln some embodiments, the identifier of the policy control entity is stored at the access and mobility management entity in the data session context for the first data session and the access and mobility management entity fetches the identifier of the policy control entity from the data session context based on the first data session.
  • the access and mobility management entity fetches the identifier of the policy control entity from the data session context based on the identifier of the first data session provided by the User Equipment.
  • the transmitting from the access and mobility management entity to the second session management entity the identifier of the policy control entity takes place if the first data session or the second data session are with a Session and Service Continuity mode 3.
  • the policy control entity serves all the data sessions to the same data network and/or slice of the user.
  • the method further includes receiving at the access and mobility management entity from a data management entity Policy Selection Assistance Info indicating that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the identifier of the policy control entity is transmitted from the access and mobility management entity to the second session management entity together with an indication that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • a fourth aspect of the invention relates to a method performed by a data management entity in a communications network, the method comprises transmitting to an access and mobility management entity Policy Selection Assistance Info indicating that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the first and second session management entities are a first and a second Session Management Functions
  • the access and mobility management entity is an Access and Mobility Management Function
  • the policy control entity is a Policy Control Function
  • the data management entity is a Unified Data Management, UDM, entity
  • the first and second data session are a first and a second PDU sessions
  • the data session context is a PDU Session Context
  • the policy association is a SM Policy Association
  • SUPI Subscription Permanent Identifier
  • DNN Data Network Name
  • the slice is identified by a Single Network Slice Selection Assistance Information, S-NSSAI.
  • aspects of the invention relate to mobile network nodes, particularly a first and second session management entities, an access and mobility management entity, and a data management entity, each configured to perform the respective methods as described herein.
  • Other aspects of the invention relate to computer program and computer program products.
  • the solution enables that the same PCF is selected, therefore there are no synchronization problems when it comes to quota information in the UDR.
  • FIG. 1 is a networked system in accordance with particular embodiments of the solution described herein.
  • Figure 2 is a signaling diagram illustrating a procedure according to particular embodiments of the solution described herein.
  • Figures 3A-3C show a signaling diagram illustrating a procedure according to particular embodiments of the solution described herein.
  • Figure 4 is a flowchart illustrating a method performed by a mobile network node according to particular embodiments of the solution described herein.
  • Figure 5 is a flowchart illustrating a method performed by a mobile network node according to particular embodiments of the solution described herein.
  • Figure 6 is a flowchart illustrating a method performed by a mobile network node according to particular embodiments of the solution described herein.
  • Figure 7 is a flowchart illustrating a method performed by a mobile network node according to particular embodiments of the solution described herein.
  • FIG. 8 is a block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.
  • FIG. 9 is a block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.
  • FIG. 10 is a block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.
  • FIG. 1 is an example networked system 100 in accordance with example embodiments of the present disclosure.
  • Figure 1 specifically illustrates User Equipment (UE) 101, which may be in communication with a (Radio) Access Network (RAN) 102 and Access and Mobility Management Function (AMF) 106 and User Plane Function (UPF) 103.
  • UE User Equipment
  • RAN Radio
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • the AMF 106 may, in turn, be in communication with core network services including Session Management Function (SMF) 107 and Policy Control Function (PCF) 111.
  • the core network services may also be in communication with an Application Server/ Application Function (AS/AF) 113.
  • Other networked services also include Network Slice Selection Function (NSSF) 108, Authentication Server Function (AUSF) 105, User Data Management (UDM) 112, Network Exposure Function (NEF) 109, Network Repository Function (NRF) 110 and Data Network (DN) 104.
  • NSSF Network Slice Selection Function
  • AUSF Authentication Server Function
  • UDM User Data Management
  • NEF Network Exposure Function
  • NRF Network Repository Function
  • DN Data Network
  • an AMF 106, SMF 107, UPF 103, PCF 111, AUSF 105, NRF 110, UDM 112, NEF 109, AF 113, and NSSF 108 are each considered to be an NF.
  • One or more additional instances of the network functions (NF) may be incorporated into the networked system.
  • the solution described herein aims to enable usage monitoring control at SMF relocation by enabling the selection of the same PCF.
  • this disclosure provides a method performed by a first and second session management entities, an access and mobility management entity, a policy control entity, and a data management entity.
  • the first and second session management entities are SMFs
  • the access and mobility management entity is an AMF
  • the policy control entity is a PCF
  • the data management entity is a UDM.
  • This disclosure provides a method performed in a communications network, the method comprises transmitting from a first session management entity to an access and mobility management entity an identifier of a policy control entity associated with a first data session of a user; selecting at the access and mobility management entity a second session management entity for a second data session of the user; transmitting from the access and mobility management entity to the second session management entity, at establishment of the second data session, the identifier of the policy control entity; establishing a policy association for the second data session between the second session management entity and the policy control entity using the identifier of the policy control entity.
  • the method is triggered and/or performed at a relocation of the session management entity allocated to the first data session.
  • the identifier of the policy control entity is transmitted from the first session management entity to the access and mobility management entity together with a request or indication of the session management entity relocation.
  • the identifier of the policy control entity is stored at the access and mobility management entity in the data session context for the first data session and the access and mobility management entity fetches the identifier of the policy control entity from the data session context based on the first data session.
  • the access and mobility management entity fetches the identifier of the policy control entity from the data session context based on the identifier of the first data session provided by the User Equipment.
  • the transmitting from the access and mobility management entity to the second session management entity the identifier of the policy control entity takes place if the first data session or the second data session are with a Session and Service Continuity mode 3.
  • the policy control entity serves all the data sessions to the same data network and/or slice of the user.
  • the method further comprises receiving at the access and mobility management entity from a data management entity Policy Selection Assistance Info indicating that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the identifier of the policy control entity is transmitted from the access and mobility management entity to the second session management entity together with an indication that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • establishing a policy association for the second data session comprises selecting at the second session management entity the policy control entity based on the identifier of the policy control entity. In some embodiments, the method further comprises distributing or synchronizing at the policy control entity the usage monitoring remaining quota between all SM Policy Associations and/or data sessions to the same data network and/or slice of the user.
  • the first and second session management entities are a first and a second Session Management Functions, SMF
  • the access and mobility management entity is an Access and Mobility Management Function, AMF
  • the policy control entity is a Policy Control Function
  • the data management entity is a Unified Data Management, UDM
  • entity entity
  • the first and second data session are a first and a second PDU sessions
  • the data session context is a PDU Session Context
  • the policy association is a SM Policy Association
  • SUPI Subscription Permanent Identifier
  • the data network is identified by a Data Network Name, DNN
  • the slice is identified by a Single Network Slice Selection Assistance Information, S-NSSAI.
  • This disclosure further provides a method performed by a first session management entity in a communications network, the method comprises transmitting to an access and mobility management entity an identifier of a policy control entity associated with a first data session of a user.
  • the method is triggered and/or performed at a relocation of the session management entity allocated to the first data session.
  • the identifier of the policy control entity is transmitted from the first session management entity to the access and mobility management entity together with a request or indication of the session management entity relocation.
  • the first and second session management entities are a first and a second Session Management Functions
  • the access and mobility management entity is an Access and Mobility Management Function
  • the policy control entity is a Policy Control Function
  • the data management entity is a Unified Data Management, UDM, entity
  • the first and second data session are a first and a second PDU sessions
  • the data session context is a PDU Session Context
  • the policy association is a SM Policy Association
  • SUPI Subscription Permanent Identifier
  • DNN Data Network Name
  • the slice is identified by a Single Network Slice Selection Assistance Information, S-NSSAI.
  • This disclosure further provides a method performed by a second session management entity in a communications network, the method comprises selecting at an access and mobility management entity the second session management entity for a second data session of the user; transmitting from the access and mobility management entity to the second session management entity, at establishment of the second data session, the identifier of the policy control entity; establishing a policy association for the second data session between the second session management entity and the policy control entity using the identifier of the policy control entity.
  • the method is triggered and/or performed at a relocation of the session management entity allocated to the first data session.
  • the transmitting from the access and mobility management entity to the second session management entity the identifier of the policy control entity takes place if the first data session or the second data session are with a Session and Service Continuity mode 3.
  • the policy control entity serves all the data sessions to the same data network and/or slice of the user.
  • the identifier of the policy control entity is transmitted from the access and mobility management entity to the second session management entity together with an indication that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • establishing a policy association for the second data session comprises selecting at the second session management entity the policy control entity based on the identifier of the policy control entity.
  • the first and second session management entities are a first and a second Session Management Functions
  • the access and mobility management entity is an Access and Mobility Management Function
  • the policy control entity is a Policy Control Function
  • the data management entity is a Unified Data Management, UDM, entity
  • the first and second data session are a first and a second PDU sessions
  • the data session context is a PDU Session Context
  • the policy association is a SM Policy Association
  • SUPI Subscription Permanent Identifier
  • DNN Data Network Name
  • the slice is identified by a Single Network Slice Selection Assistance Information, S-NSSAI.
  • This disclosure further provides a method performed by an access and mobility management entity in a communications network, the method comprises receiving from a first session management entity an identifier of a policy control entity associated with a first data session of a user; selecting at the access and mobility management entity a second session management entity for a second data session of the user; transmitting from the access and mobility management entity to the second session management entity, at establishment of the second data session, the identifier of the policy control entity.
  • the method is triggered and/or performed at a relocation of the session management entity allocated to the first data session.
  • the identifier of the policy control entity is transmitted from the first session management entity to the access and mobility management entity together with a request or indication of the session management entity relocation.
  • the identifier of the policy control entity is stored at the access and mobility management entity in the data session context for the first data session and the access and mobility management entity fetches the identifier of the policy control entity from the data session context based on the first data session.
  • the access and mobility management entity fetches the identifier of the policy control entity from the data session context based on the identifier of the first data session provided by the User Equipment.
  • the transmitting from the access and mobility management entity to the second session management entity the identifier of the policy control entity takes place if the first data session or the second data session are with a Session and Service Continuity mode 3.
  • the policy control entity serves all the data sessions to the same data network and/or slice of the user.
  • the method further comprises receiving at the access and mobility management entity from a data management entity Policy Selection Assistance Info indicating that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the identifier of the policy control entity is transmitted from the access and mobility management entity to the second session management entity together with an indication that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the first and second session management entities are a first and a second Session Management Functions
  • the access and mobility management entity is an Access and Mobility Management Function
  • the policy control entity is a Policy Control Function
  • the data management entity is a Unified Data Management, UDM, entity
  • the first and second data session are a first and a second PDU sessions
  • the data session context is a PDU Session Context
  • the policy association is a SM Policy Association
  • SUPI Subscription Permanent Identifier
  • the data network is identified by a Data Network Name, DNN
  • the slice is identified by a Single Network Slice Selection Assistance Information, S-NSSAI.
  • This disclosure further provides a method performed by a data management entity in a communications network, the method comprises transmitting to an access and mobility management entity Policy Selection Assistance Info indicating that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the first and second session management entities are a first and a second Session Management Functions
  • the access and mobility management entity is an Access and Mobility Management Function
  • the policy control entity is a Policy Control Function
  • the data management entity is a Unified Data Management, UDM, entity
  • the first and second data session are a first and a second PDU sessions
  • the data session context is a PDU Session Context
  • the policy association is a SM Policy Association
  • SUPI Subscription Permanent Identifier
  • DNN Data Network Name
  • the slice is identified by a Single Network Slice Selection Assistance Information, S-NSSAI.
  • the solution disclosed herein includes:
  • the old SMF transfers the PCF identifier, PCF ID, for the Old PDU Session ID to the AMF, which is stored in the PDU Session Context at the AMF.
  • the SMF When the SMF requests SMF relocation to the AMF, it includes the PCF ID for the PDU Session, which is sent to the new SMF at the time that the PDU Session is relocated.
  • the AMF selects the SMF for the new PDU Session and transfers the PCF ID to the newly selected SMF.
  • the AMF determines the PCF ID based on the PDU Session Context in AMF.
  • the newly selected SMF establishes a SM Policy Association to the PCF ID received from AMF, that serves all PDU Sessions to the same DNN, S-NSSAI of a SUPI.
  • the PCF ID distributes the usage monitoring remaining quota between all SM Policy Associations to the same DNN, S-NSSAI of a SUPI.
  • a change of SMF for a PDU Session with SSC mode 3 applies transfers the PCF ID for the Old PDU Session ID that is stored in the PDU Session Context at the SMF.
  • - PDU Session establishment includes an additional check in the AMF to set the Same PCF Selection Indication to the SMF, and include the PCF ID stored in the PDU Session Context for this DNN, S-NSSAI.
  • the same PCF will be selected when the SMF is reallocated.
  • This disclosure also provides mobile network nodes, particularly a first and second session management entities, an access and mobility management entity, and a data management entity, each configured to perform the respective methods as described herein.
  • This disclosure also provides the corresponding computer program and computer program products comprising code, for example in the form of a computer program, that when run on processing circuitry of the mobile network nodes causes the mobile network nodes to perform the disclosed methods.
  • Figure 2 is a signaling diagram illustrating a procedure for usage monitoring control at SMF relocation.
  • the procedure is performed by a UE 101, RAN 102, AMF 106, a LIPF1 103, a UPF2 103, a SMF1 107 and a SMF2 107.
  • the procedure comprises the following steps:
  • Step I The SMF determines that the serving UPF or the SMF needs to be changed. If the "Indication of application relocation possibility" attributes in the PCC rule indicates no DNAI change takes place once selected for this application, the SMF determines that the SMF can not be changed.
  • Step 1a If the UPF (PSA) cannot connect to the target DNAI(s) that SMF received from SM- PCF, the SMF invokes Nsmf_PDUSession_SMContextStatusNotify Request (target DNAI information) service operation to the AMF.
  • the SMF also indicate the SMF selection is expected.
  • Step 2 If the SMF had sent an early notification to the AF and the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF waits for a notification response from the AF. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure.
  • the SMF1 includes the PCF ID along with the SMF relocation indication.
  • the SMF invokes the Namf_Communication_N1 N2MessageTransfer (PDU Session ID, SMF Reallocation requested indication, PCF ID, N1 SM container (PDU Session Modification Command (Cause, PCO (PDU Session Address Lifetime value)))) where PDU Session ID indicates the existing PDU Session to be relocated, the PCF ID for the for the PDU Session to be relocated and Cause indicates that a PDU Session re-establishment to the same DN is required.
  • PDU Session ID SMF Reallocation requested indication
  • PCF ID N1 SM container
  • PDU Session Modification Command (Cause, PCO (PDU Session Address Lifetime value)))
  • Step 3a The AMF forwards the NAS message to the UE.
  • the UE can provide the release timer value to the upper layers if received in the PDU Session Modification Command.
  • the AMF stores the PCF ID In the PDU Session context information.
  • Step 3b The UE acknowledges the PDU Session Modification Command.
  • Step 3c The AMF forwards the N1 SM container (PDU Session Modification Command ACK) received from the (R)AN to the SMF1 via Nsmf_PDUSession_UpdateSMContext service operation.
  • N1 SM container PDU Session Modification Command ACK
  • Step 3d The SMF1 replies with a Nsmf_PDUSession_UpdateSMContext Response.
  • Step 4 If the UE receives PDU Session Modification Command, the UE may decide to initiate the PDU Session Establishment procedure, to the same DN with the following differences:
  • Step 5 After the new PDU Session is established the UE starts using the IP address/prefix associated with the new PDU Session for all new traffic and may also proactively move existing traffic flow (where possible) from the old PDU Session to the new PDU Session.
  • Step 6 The old PDU Session is released either by the UE before the timer provided in step 3 expires (e.g., once the UE has consolidated all traffic on new PDU Session or if the session is no more needed) or by the SMF upon expiry of this timer.
  • Figures 3A-3C show a signaling diagram illustrating a procedure for usage monitoring control at SMF relocation.
  • the procedure is performed by a UE 101 , RAN 102, AMF 106, a UPF 103, a SMF 107, PCF 111 , UDM 112, and a DN 104.
  • This procedure is based on the PDU Session Establishment in Non-roaming and Roaming with Local Breakout procedure disclosed in 3GPP TS 23.502, section 4.3.2.2.1.
  • the procedure comprises the following steps:
  • Step I From UE to AMF: NAS Message (S-NSSAI(s), UE Requested DNN, PDU Session ID, Request type, Old PDU Session ID, N1 SM container (PDU Session Establishment Request, [Port Management Information Container])).
  • S-NSSAI S-NSSAI(s)
  • UE Requested DNN PDU Session ID
  • Request type PDU Session ID
  • N1 SM container PDU Session Establishment Request, [Port Management Information Container]
  • Step 2 The AMF selects an SMF.
  • Step 3 From AMF to SMF: Either Nsmf_PDUSession_CreateSMContext Request (SUPI, selected DNN, UE requested DNN, S-NSSAI(s), PDU Session ID, AMF ID, Request Type, [PCF ID, Same PCF Selection Indication], Priority Access, [Small Data Rate Control Status], N1 SM container (PDU Session Establishment Request), User location information, Access Type, RAT Type, PEI, GPSI, UE presence in LADN service area, Subscription For PDU Session Status Notification, DNN Selection Mode, Trace Requirements, Control Plane CloT 5GS Optimisation indication, Control Plane Only indicator, Satellite backhaul category, [PVS FQDN(s) and/or PVS IP address(es), Onboarding Indication], Disaster Roaming service indication) or Nsmf_PDUSession_UpdateSMContext Request (SUPI, DNN, S-NSSAI(s), SM Context ID, AMF ID,
  • the AMF checks if the PCF Selection Assistance info from the UDM as follows:
  • the AMF includes in Nsmf_PDUSession_CreateSMContext Request both the Same PCF Selection Indication and the PCF ID selected by the AMF, this PCF ID identifies the H-PCF,
  • the AMF includes in Nsmf_PDUSession_CreateSMContext Request both the Same PCF Selection Indication and the PCF ID stored in the PDU Session level context for the Old PDU Session ID, this PCF ID identifies the H-PCF.
  • the AMF may include a PCF ID in the Nsmf_PDUSession_CreateSMContext Request based on operator policies. This PCF ID identifies the H-PCF in the non-roaming case and the V-PCF in the local breakout roaming case.
  • Step 4 If Session Management Subscription data for corresponding SUPI, DNN and S- NSSAI of the HPLMN is not available, then SMF retrieves the Session Management Subscription data using Nudm_SDM_Get (SUPI, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]) and subscribes to be notified when this subscription data is modified using Nudm_SDM_Subscribe (SUPI, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]).
  • Nudm_SDM_Get SUPI, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]
  • UDM may get this information from UDR by Nudr_DM_Query (SUPI, Subscription Data, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]) and may subscribe to notifications from UDR for the same data by Nudr_DM_subscribe.
  • Nudr_DM_Query SUPI, Subscription Data, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]
  • a Policy Selection Assistance Info is provided by the UDM to AMF at Registration, indicating that the same PCF is selected for all PDU Sessions to the same SUPI, DNN, and/or S- NSSAI.
  • the indication indicates that the same PCF is selected for all PDU Sessions to the same SUPI, DNN, and/or S-NSSAI.
  • the PCF Selection Assistance info comprises a list of combination of DNN and S-NSSAI that indicates that the same PCF needs to be selected for both the AM/LIE Policy Control association of this SlIPI and all SM Policy Control associations to this DNN, S-NSSAI of this SUPI or only for all SM Policy Control associations to this DNN, S-NSSAI of this SLIPI.
  • the same PCF is selected for all PDU sessions of a UE to the same DNN, S-NSSAI, each of them is indicated in the list of S-NSSAI, DNN combinations in the PCF Selection Assistance Info. This allows selection of the same PCF selection for usage monitoring when SSC mode applies.
  • Step 5 From SMF to AMF: Either Nsmf_PDUSession_CreateSMContext Response (Cause, SM Context ID or N1 SM container (PDU Session Reject (Cause))) or an Nsmf_PDUSession_UpdateSMContext Response depending on the request received in step 3.
  • Nsmf_PDUSession_CreateSMContext Response (Cause, SM Context ID or N1 SM container (PDU Session Reject (Cause))
  • Nsmf_PDUSession_UpdateSMContext Response depending on the request received in step 3.
  • Step 6 Optional Secondary authentication/authorization.
  • Step 7a If dynamic PCC is to be used for the PDU Session, the SMF performs PCF selection. If the Request Type indicates "Existing PDU Session" or "Existing Emergency PDU Session", the SMF shall use the PCF already selected for the PDU Session.
  • Step 7b The SMF may perform an SM Policy Association Establishment procedure to establish an SM Policy Association with the PCF and get the default PCC Rules for the PDU Session.
  • the GPSI, PVS FQDN(s) and/or PVS IP address(es) and the Onboarding Indication shall be included if available at SMF in the case of ON-SNPN.
  • the SMF may provide information on the Policy Control Request Trigger condition(s) that have been met by an SMF initiated SM Policy Association Modification procedure.
  • the SMF selects the PCF ID for the SM Policy Association in step 7b.
  • Step 8 If the Request Type in step 3 indicates "Initial request", the SMF selects an SSC mode for the PDU Session. The SMF also selects one or more UPFs as needed. In the case of PDU Session Type IPv4 or IPv6 or IPv4v6, the SMF allocates an IP address/prefix for the PDU Session (unless configured otherwise). In the case of PDU Session Type IPv6 or IPv4v6, the SMF also allocates an interface identifier to the UE for the UE to build its linklocal address. For Unstructured PDU Session Type the SMF may allocate an IPv6 prefix for the PDU Session and N6 point-to-point tunnelling (based on UDP/IPv6). For Ethernet PDU Session Type, neither a MAC nor an IP address is allocated by the SMF to the UE for this PDU Session.
  • Step 9 SMF may perform an SMF initiated SM Policy Association Modification procedure to provide information on the Policy Control Request Trigger condition(s) that have been met.
  • Step 10 If Request Type indicates "initial request", the SMF initiates an N4 Session Establishment procedure with the selected UPF(s), otherwise it initiates an N4 Session Modification procedure with the selected UPF(s).
  • Step 10a The SMF sends an N4 Session Establishment/Modification Request to the UPF and provides Packet detection, enforcement and reporting rules to be installed on the UPF for this PDU Session.
  • Step 10b The UPF acknowledges by sending an N4 Session Establishment/Modification Response.
  • Step 11 SMF to AMF: Namf_Communication_N1 N2MessageTransfer (PDU Session ID, N2 SM information (PDU Session ID, QFI(s), QoS Profile(s), CN Tunnel Info, S-NSSAI from the Allowed NSSAI, Session-AMBR, PDU Session Type, User Plane Security Enforcement information, UE Integrity Protection Maximum Data Rate, RSN, PDU Session Pair ID), N1 SM container (PDU Session Establishment Accept ([QoS Rule(s) and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s)], selected SSC mode, S-NSSAI(s), UE Requested DNN, allocated IPv4 address, interface identifier, Session-AMBR, selected PDU Session Type, [Reflective QoS Timer] (if available), [P-CSCF address(es)], [Control Plane Only indicator], [He
  • the AMF fetches the PCF ID from the PDU Session Context at the AMF based on the Old PDU Session ID provided by the UE.
  • the PCF ID was stored after it was received from SMF in step 2 in Figure 2.
  • Step 12 AMF to (R)AN: N2 PDU Session Request (N2 SM information, NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept)), [CN assisted RAN parameters tuning]). If the N2 SM information is not included in the step 11, an N2 Downlink NAS Transport message is used instead. Step 13. (R)AN to UE: The (R)AN may issue AN specific signalling exchange with the UE that is related with the information received from SMF. For example, in the case of a NG- RAN, an RRC Connection Reconfiguration may take place with the UE establishing the necessary NG-RAN resources related to the QoS Rules for the PDU Session request received in step 12.
  • Step 14 N2 PDU Session Response (PDU Session ID, Cause, N2 SM information (PDU Session ID, AN Tunnel Info, List of accepted/rejected QFI(s), User Plane Enforcement Policy Notification)).
  • Step 15 AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (SM Context ID, N2 SM information, Request Type).
  • Step 16a The SMF initiates an N4 Session Modification procedure with the UPF.
  • the SMF provides AN Tunnel Info to the UPF as well as the corresponding forwarding rules.
  • Step 16b The UPF provides an N4 Session Modification Response to the SMF.
  • Step 16c If Request Type in step 3 indicates neither "Emergency Request” nor "Existing Emergency PDU Session” and, if the SMF has not yet registered for this PDU Session, then the SMF registers with the UDM using Nudm_UECM_Registration (SUPI, DNN, S-NSSAI of HPLMN, PDU Session ID, SMF Identity, Serving Node PLMN ID, [NID]) for a given PDU Session.
  • the UDM stores following information: SUPI, SMF identity and the associated DNN, S-NSSAI of HPLMN, PDU Session ID and Serving Network (PLMN ID, [NID]).
  • the UDM may further store this information in UDR by Nudr_DM_Update (SUPI, Subscription Data, UE context in SMF data). If the UDM has existing applicable event exposure subscriptions for events detected in SMF for this UE or any of the groups this UE belongs to (possibly retrieved from UDR), UDM invokes the Nsmf_EventExposure_Subscribe service for creating the event exposure subscriptions.
  • Nudr_DM_Update SUPI, Subscription Data, UE context in SMF data.
  • Step 18 SMF to AMF: Nsmf_PDUSession_SMContextStatusNotify (Release)
  • Step 19 SMF to UE: In the case of PDU Session Type IPv6 or IPv4v6, the SMF generates an IPv6 Router Advertisement and sends it to the UE. If Control Plane CloT 5GS Optimisation is enabled for this PDU Session the SMF sends the IPv6 Router Advertisement via the AMF for transmission to the UE using the Mobile Terminated Data Transport in Control Plane CloT 5GS Optimisation procedures, otherwise the SMF sends the IPv6 Router Advertisement via N4 and the UPF. Step 20. When the trigger for 5GS Bridge information available is armed, then the SMF may initiate the SM Policy Association Modification.
  • Step 21 If the PDU Session establishment failed after step 4, the SMF unsubscribes to the modifications of Session Management Subscription data for the corresponding (SlIPI, DNN, S-NSSAI of the HPLMN).
  • Figure 4 is a flowchart illustrating a method performed by a session management entity or SMF 107.
  • step 401 there is a relocation of the session management entity allocated to the first data session.
  • the SMF transmits to an access and mobility management entity an identifier of a policy control entity associated with a first data session of a user.
  • Figure 5 is a flowchart illustrating a method performed by a session management entity or SMF 107.
  • the SMF selects at an access and mobility management entity the second session management entity for a second data session of the user.
  • the SMF transmits from the access and mobility management entity to the second session management entity, at establishment of the second data session, the identifier of the policy control entity.
  • the SMF establishes a policy association for the second data session between the second session management entity and the policy control entity using the identifier of the policy control entity.
  • FIG. 6 is a flowchart illustrating a method performed by an access and mobility management entity or AM F 106.
  • the AMF receives from a first session management entity an identifier of a policy control entity associated with a first data session of a user.
  • the AMF receives at the access and mobility management entity from a data management entity Policy Selection Assistance Info indicating that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • the AMF selects at the access and mobility management entity a second session management entity for a second data session of the user.
  • the AMF transmits from the access and mobility management entity to the second session management entity, at establishment of the second data session, the identifier of the policy control entity.
  • FIG. 7 is a flowchart illustrating a method performed by a data management entity or UDM 112.
  • the UDM transmits to an access and mobility management entity Policy Selection Assistance Info indicating that the same policy control entity is selected for all data sessions to the same data network and/or slice of the user.
  • FIG. 8 is a block diagram illustrating elements of a mobile network node 800 of a mobile communications network.
  • the mobile network node 800 is an SMF 107, according to the embodiments described herein.
  • the mobile network node may include network interface circuitry 801 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the network.
  • the mobile network node may also include a processing circuitry 802 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 803 (also referred to as memory) coupled to the processing circuitry.
  • the memory circuitry 803 may include computer readable program code that when executed by the processing circuitry 802 causes the processing circuitry to perform operations according to embodiments disclosed herein.
  • processing circuitry 802 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 802 and/or network interface circuitry 801. For example, processing circuitry 802 may control network interface circuitry 801 to transmit communications through network interface circuitry 801 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 803, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 802, processing circuitry 802 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).
  • FIG. 9 is a block diagram illustrating elements of a mobile network node 900 of a mobile communications network.
  • the mobile network node 900 is an AMF 106 according to the embodiments described herein.
  • the mobile network node may include network interface circuitry 901 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the network.
  • the mobile network node may also include a processing circuitry 902 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 903 (also referred to as memory) coupled to the processing circuitry.
  • the memory circuitry 903 may include computer readable program code that when executed by the processing circuitry 902 causes the processing circuitry to perform operations according to embodiments disclosed herein.
  • processing circuitry 902 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 902 and/or network interface circuitry 901. For example, processing circuitry 902 may control network interface circuitry 901 to transmit communications through network interface circuitry 901 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 903, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 902, processing circuitry 902 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).
  • FIG 10 is a block diagram illustrating elements of a mobile network node 1000 of a mobile communications network.
  • the mobile network node 1000 is a UDM 112 according to the embodiments described herein.
  • the mobile network node may include network interface circuitry 1001 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the network.
  • the mobile network node may also include a processing circuitry 1002 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1003 (also referred to as memory) coupled to the processing circuitry.
  • the memory circuitry 1003 may include computer readable program code that when executed by the processing circuitry 1002 causes the processing circuitry to perform operations according to embodiments disclosed herein.
  • processing circuitry 1002 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 1002 and/or network interface circuitry 1001. For example, processing circuitry 1002 may control network interface circuitry 1001 to transmit communications through network interface circuitry 1001 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1003, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1002, processing circuitry 1002 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).
  • Embodiments within the scope of the present invention may also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon.
  • Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer.
  • Such tangible computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures.
  • Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
  • Computer-executable instructions also include program modules that are executed by computers in standalone or network environments.
  • program modules include routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types.
  • Computer executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.
  • Embodiments of the invention may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
  • Communication at various stages of the described system can be performed through a local area network, a token ring network, the Internet, a corporate intranet, 802.11 series wireless signals, fiber-optic network, radio or microwave transmission, etc.
  • a token ring network such as a token ring network
  • the Internet such as a token ring network
  • a corporate intranet such as a corporate intranet

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé permettant une commande de surveillance d'usages lors de relocalisation de SMF par permission de sélection d'une même PCF. Le procédé consiste à transmettre, d'une première entité de gestion de session à une entité de gestion d'accès et de mobilité, un identifiant d'une entité de commande de politique associée à une première session de données d'un utilisateur ; à sélectionner au niveau de l'entité de gestion d'accès et de mobilité une seconde entité de gestion de session pour une seconde session de données de l'utilisateur ; à transmettre de l'entité de gestion d'accès et de mobilité à la seconde entité de gestion de session, lors de l'établissement de la seconde session de données, de l'identifiant de l'entité de commande de politique ; à établir une association de politique pour la seconde session de données entre la seconde entité de gestion de session et l'entité de commande de politique à l'aide de l'identifiant de l'entité de commande de politique.
PCT/EP2022/080817 2021-11-08 2022-11-04 Commande de surveillance d'usages lors de relocalisation de smf WO2023079075A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP21383009 2021-11-08
EP21383009.4 2021-11-08

Publications (1)

Publication Number Publication Date
WO2023079075A1 true WO2023079075A1 (fr) 2023-05-11

Family

ID=78725416

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/080817 WO2023079075A1 (fr) 2021-11-08 2022-11-04 Commande de surveillance d'usages lors de relocalisation de smf

Country Status (1)

Country Link
WO (1) WO2023079075A1 (fr)

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17)", 17 June 2021 (2021-06-17), XP052053386, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/Latest_SA2_Specs/DRAFT_INTERIM/Archive/23501-h10_CRs_Implemented.zip 23501-h10_CRs_Implemented.docx> [retrieved on 20210617] *
3GPP TS 23.501
3GPP TS 23.502
3GPP TS 23.503
ERICSSON: "PCF selection for multiple PDU Sessions to the same DNN and S-NSSAI", vol. SA WG2, no. Split, HR; 20191014 - 20191018, 4 October 2019 (2019-10-04), XP051801258, Retrieved from the Internet <URL:https://ftp.3gpp.org/Meetings_3GPP_SYNC/SA2/Docs/S2-1909046.zip S2-1909046_23502CR1720 PCFselSameS-NSSAI_DNN.docx> [retrieved on 20191004] *
NOKIA ET AL: "SMF Reallocation requested Indication", vol. CT WG4, no. Vilnius, Lithuania; 20181015 - 20181019, 18 October 2018 (2018-10-18), XP051574498, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fct/WG4%5Fprotocollars%5Fex%2DCN4/TSGCT4%5F86bis%5FVilnus/Docs/C4%2D187495%2Ezip> [retrieved on 20181018] *

Similar Documents

Publication Publication Date Title
US11523268B2 (en) Communications method and apparatus
US11737156B2 (en) Establishing a session or cellular Internet of Things packet transmission
US11153929B2 (en) System and methods for session management
US20210105196A1 (en) Support group communications with shared downlink data
US20230337322A1 (en) Network exposure function and wireless device with releasable connection
US20220369206A1 (en) Non-Public Network Overload and Congestion Control
US11159976B2 (en) Handling of mapped EPS bearer context for invalid QoS flow description
JP7272736B2 (ja) サービス加入方法、当該方法を実行するためのチップ、情報伝達装置およびプログラム、並びにネットワーク機能ネットワーク要素
JP2020504559A (ja) Ｐｄｕセッション管理
WO2020164763A1 (fr) Procédés et appareils pour transmission de données par données sur strate de non-acces (donas) de substitution dans un scénario d&#39;itinérance
US11284458B2 (en) Handling of mapped EPS bearer context with duplicate EPS bearer ID
WO2021095655A1 (fr) Système et procédé pour permettre les politiques et la facturation d&#39;un équipement d&#39;utilisateur présentant une ou plusieurs identités d&#39;utilisateur
WO2021089739A1 (fr) Établissement d&#39;une session pdu sans ressources de plan utilisateur
CN109819530B (zh) 一种通信方法及装置
US20240196263A1 (en) Handling of heterogeneous support for user equipment slice maximum bit rate (s-mbr)
WO2023079075A1 (fr) Commande de surveillance d&#39;usages lors de relocalisation de smf
US20240121157A1 (en) Methods, systems, and computer readable media for automatically triggering network slice selection assistance information (nssai) availability information updates with network slice selection function (nssf)
WO2024109127A1 (fr) Système et procédés de commande de mobilité de flux

Legal Events

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

Ref document number: 22812657

Country of ref document: EP

Kind code of ref document: A1