[go: up one dir, main page]

WO2024217298A1 - Procédés et appareils de commande de tranche de réseau - Google Patents

Procédés et appareils de commande de tranche de réseau Download PDF

Info

Publication number
WO2024217298A1
WO2024217298A1 PCT/CN2024/086822 CN2024086822W WO2024217298A1 WO 2024217298 A1 WO2024217298 A1 WO 2024217298A1 CN 2024086822 W CN2024086822 W CN 2024086822W WO 2024217298 A1 WO2024217298 A1 WO 2024217298A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
terminal device
network
target terminal
network slice
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.)
Pending
Application number
PCT/CN2024/086822
Other languages
English (en)
Inventor
Hui Yang
Antonio INIESTA GONZALEZ
Gang Ren
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2024217298A1 publication Critical patent/WO2024217298A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control

Definitions

  • Embodiments of the disclosure generally relate to communication, and, more particularly, to methods and apparatuses for network slice control.
  • Network slicing is defined in the 3rd generation partnership project (3GPP) as a logical network that provides specific network capabilities and network characteristics and comprises radio access network (RAN) , core network (CN) , and transport network. It is a concept for running multiple logical customized networks on a shared common infrastructure complying with agreed service level agreements (SLAs) for different vertical industry customers and requested functionalities. Then, each “slice” or portion of the network can be allocated based on the specific needs of the application, use case or customer.
  • 3GPP 3rd generation partnership project
  • the main architectural principles for network slicing are defined in clause 5.15 of 3GPP technical specification (TS) 23.501 V18.0.0.
  • the related signaling procedures within the 5th generation core (5GC) happen at a few different stages such as registration, protocol data unit (PDU) session establishment, policy change, etc.
  • a user equipment needs to register in the network via an access and mobility management function (AMF) that supports proper network slices for the UE as defined in clause 5.15.5.2 of 3GPP TS 23.501 V18.0.0. Then, the UE may establish one or more PDU sessions to the required data network (DN) via the proper network slice instance as described in clause 5.15.5.3 of 3GPP TS 23.501 V18.0.0.
  • AMF access and mobility management function
  • One of the objects of the disclosure is to provide an improved solution for network slice control.
  • one of the problems to be solved by the disclosure is that currently some UEs do not support UE route selection policy (URSP) so that operators could not deploy the 5th generation (5G) new service of dynamic slice selection to some end users.
  • URSP UE route selection policy
  • a method performed by a first network node related to policy control may comprise determining, for a target terminal device, whether one or more conditions under which to update an allowed network slice for the target terminal device are met.
  • the method may further comprise, when determining that the one or more conditions are met, determining an updated allowed network slice for the target terminal device and providing to a second network node related to access and mobility management information related to the updated allowed network slice.
  • the first network node provides dynamic slice selection service to those terminal devices even if they do not support URSP. This could facilitate the deployment of 5G differentiated UE slicing services for all users independently on their terminal capabilities.
  • the method may further comprise determining whether the target terminal device has URSP capability.
  • the determining of whether the one or more conditions are met, the determining of the updated allowed network slice and the providing of the information related to the updated allowed network slice may be performed when determining that the target terminal device has no URSP capability.
  • the terminal device (s) having no URSP capability can receive dynamic slice service enabled via the first network node, while the terminal device (s) having URSP capability can still use the URSP capability for dynamic slice selection.
  • the method may further comprise receiving, from the second network node, identifiers of one or more allowed network slices of the target terminal device.
  • the method may further comprise determining whether the updated allowed network slice is one of the identified allowed network slices.
  • the information related to the updated allowed network slice may be provided to the second network node when determining that the updated allowed network slice is one of the identified allowed network slices.
  • the one or more conditions may comprise one or more of: a first condition that a location of the target terminal device is inside or outside an area; a second condition that current time is inside or outside a time period; a third condition that a network at an area where the target terminal device is located is or is to be in congested status, or changes from congested status to normal status; a fourth condition that an internal event of the first network node occurs; and a fifth condition that an trigger is received from another network node.
  • various factors such as UE location, time and network status can be used to flexibly define the condition (s) for network slice updating.
  • the method may further comprise one or more of: obtaining, from the second network node, information related to a location of the target terminal device; and obtaining, from a third network node related to network monitoring, information related to a network status at an area where the target terminal device is located.
  • the updated allowed network slice for the target terminal device may be determined based on a pre-configuration in the first network node.
  • the pre-configuration may comprise one or more rules each of which indicates, for the target terminal device or a terminal device group containing the target terminal device, the one or more conditions and a corresponding updated allowed network slice.
  • the operator can be allowed to flexibly control the dynamic slice selection service by using the pre-configuration, so for a target terminal device, the slice selection can be executed at the first network node side, without support by the terminal device’s capability of slice selection.
  • providing the information related to the updated allowed network slice may comprise receiving, from the second network node, a first request for creating an access and mobility (AM) policy association between the second network node and the first network node for the target terminal device.
  • Providing the information related to the updated allowed network slice may further comprise sending, to the second network node, a first response to the first request.
  • the first response may indicate the information related to the updated allowed network slice.
  • providing the information related to the updated allowed network slice may comprise receiving, from the second network node, a second request for modifying an AM policy association between the second network node and the first network node for the target terminal device.
  • Providing the information related to the updated allowed network slice may further comprise sending, to the second network node, a second response to the second request.
  • the second response may indicate the information related to the updated allowed network slice.
  • providing the information related to the updated allowed network slice may comprise sending, to the second network node, a third request for updating AM policies related to an AM policy association between the second network node and the first network node for the target terminal device.
  • the third request may indicate the information related to the updated allowed network slice.
  • Providing the information related to the updated allowed network slice may further comprise receiving, from the second network node, a third response to the third request.
  • the existing procedures related to AM policy association can be extended to support the dynamic slice selection service, and through such procedures, the second network node can get the information related to the updated allowed network slice for allocation of the updated allowed network slice to a terminal device.
  • providing the information related to the updated allowed network slice may comprise receiving, from the second network node, a fourth request for creating a UE policy association between the second network node and the first network node for the target terminal device.
  • Providing the information related to the updated allowed network slice may further comprise sending, to the second network node, a fourth response to the fourth request.
  • the fourth response may indicate the information related to the updated allowed network slice.
  • providing the information related to the updated allowed network slice may comprise receiving, from the second network node, a fifth request for modifying a UE policy association between the second network node and the first network node for the target terminal device.
  • Providing the information related to the updated allowed network slice may further comprise sending, to the second network node, a fifth response to the fifth request.
  • the fifth response may indicate the information related to the updated allowed network slice.
  • providing the information related to the updated allowed network slice may comprise sending, to the second network node, a sixth request for updating UE policies related to a UE policy association between the second network node and the first network node for the target terminal device.
  • the sixth request may indicate the information related to the updated allowed network slice.
  • Providing the information related to the updated allowed network slice may further comprise receiving, from the second network node, a sixth response to the sixth request.
  • the method may further comprise receiving, from the second network node, a third indicator indicating whether the second network node supports applying the updated allowed network slice to the target terminal device.
  • the determining of whether the one or more conditions are met, the determining of the updated allowed network slice and the providing of the information related to the updated allowed network slice may be performed when the received third indicator indicates that the second network node supports applying the updated allowed network slice to the target terminal device.
  • the information related to the updated allowed network slice may be provided to the second network node through a new service procedure between the first network node and the second network node.
  • a method performed by a second network node related to access and mobility management may comprise obtaining, from a first network node related to policy control, information related to an updated allowed network slice determined by the first network node for a target terminal device.
  • the method may further comprise, when the updated allowed network slice is different from currently selected network slice for the target terminal device, instructing the target terminal device to perform re-registration with the updated allowed network slice.
  • the second network node can provide dynamic slice selection service to those terminal devices even if they do not support URSP.
  • the second network node can allocate the updated allowed network slice through UE configuration update to a terminal device not supporting URSP. This could facilitate the deployment of 5G differentiated UE slicing services for all users independently on their terminal capabilities.
  • the method may further comprise, when the target terminal device has performed re-registration with the updated allowed network slice, establishing, for the target terminal device, one or more protocol data unit (PDU) sessions over the updated allowed network slice.
  • PDU protocol data unit
  • user traffic can be transferred through the PDU session (s) established over the updated allowed network slice to implement differentiated UE slicing services.
  • the one or more PDU sessions may be established based on the updated allowed network slice indicated by the target terminal device.
  • the second network node receives, from the target terminal device, one or more requests for establishing the one or more PDU sessions and the one or more requests do not indicate the updated allowed network slice
  • the one or more PDU sessions may be established based on the information related to the updated allowed network slice that is obtained from the first network node.
  • the PDU session (s) can be established over the updated allowed network slice no matter whether or not the target terminal device indicates the updated allowed network slice when initiating the establishment of the one or more PDU sessions.
  • the second network node may instruct the target terminal device to perform re-registration with the updated allowed network slice.
  • the updated configuration for the target terminal device may comprise the information related to the updated allowed network slice.
  • the method may further comprise determining whether a terminal device has URSP capability.
  • the method may further comprise establishing, for the terminal device, an AM policy association between the second network node and the first network node when the terminal device has no URSP capability.
  • the method may further comprise establishing, for the terminal device, a UE policy association between the second network node and the first network node when the terminal device has URSP capability.
  • the method may further comprise establishing, for a terminal device, a UE policy association between the second network node and the first network node irrespective of whether the terminal device has URSP capability.
  • the processing of the second network node can be simplified to let the first network node differentiate between the two types of terminal devices and perform different processing for them.
  • the terminal device (s) having no URSP capability can receive dynamic slice service enabled via the first network node, while the terminal device (s) having URSP capability can still use the URSP capability for dynamic slice selection.
  • obtaining the information related to the updated allowed network slice may comprise sending, to the first network node, a first request for creating an AM policy association between the second network node and the first network node for the target terminal device.
  • Obtaining the information related to the updated allowed network slice may further comprise receiving, from the first network node, a first response to the first request.
  • the first response may indicate the information related to the updated allowed network slice.
  • obtaining the information related to the updated allowed network slice may comprise sending, to the first network node, a second request for modifying an AM policy association between the second network node and the first network node for the target terminal device.
  • Obtaining the information related to the updated allowed network slice may further comprise receiving, from the first network node, a second response to the second request.
  • the second response may indicate the information related to the updated allowed network slice.
  • obtaining the information related to the updated allowed network slice may comprise receiving, from the first network node, a third request for updating AM policies related to an AM policy association between the second network node and the first network node for the target terminal device.
  • the third request may indicate the information related to the updated allowed network slice.
  • Obtaining the information related to the updated allowed network slice may further comprise sending, to the first network node, a third response to the third request.
  • the existing procedures related to AM policy association can be extended to support the dynamic slice selection service, and through such procedures, the second network node can get the information related to the updated allowed network slice for allocation of the updated allowed network slice to a terminal device.
  • obtaining the information related to the updated allowed network slice may comprise sending, to the first network node, a fourth request for creating a UE policy association between the second network node and the first network node for the target terminal device.
  • Obtaining the information related to the updated allowed network slice may further comprise receiving, from the first network node, a fourth response to the fourth request.
  • the fourth response may indicate the information related to the updated allowed network slice.
  • obtaining the information related to the updated allowed network slice may comprise sending, to the first network node, a fifth request for modifying a UE policy association between the second network node and the first network node for the target terminal device.
  • Obtaining the information related to the updated allowed network slice may further comprise receiving, from the first network node, a fifth response to the fifth request.
  • the fifth response may indicate the information related to the updated allowed network slice.
  • obtaining the information related to the updated allowed network slice may comprise receiving, from the first network node, a sixth request for updating UE policies related to a UE policy association between the second network node and the first network node for the target terminal device.
  • the sixth request may indicate the information related to the updated allowed network slice.
  • Obtaining the information related to the updated allowed network slice may further comprise sending, to the first network node, a sixth response to the sixth request.
  • the method may further comprise sending, to the first network node, a third indicator indicating whether the second network node supports applying the updated allowed network slice to the target terminal device.
  • the information related to the updated allowed network slice may be provided to the second network node through a new service procedure between the first network node and the second network node.
  • the method may further comprise sending, to the first network node, identifiers of one or more allowed network slices of the target terminal device.
  • a first network node related to policy control.
  • the first network node may comprise at least one processor and at least one memory.
  • the at least one memory may contain instructions executable by the at least one processor, whereby the first network node may be operative to determine, for a target terminal device, whether one or more conditions under which to update an allowed network slice for the target terminal device are met.
  • the first network node may be further operative to, when determining that the one or more conditions are met, determine an updated allowed network slice for the target terminal device and provide to a second network node related to access and mobility management information related to the updated allowed network slice.
  • the first network node may be operative to perform the method according to the above first aspect.
  • a second network node related to access and mobility management.
  • the second network node may comprise at least one processor and at least one memory.
  • the at least one memory may contain instructions executable by the at least one processor, whereby the second network node may be operative to obtain, from a first network node related to policy control, information related to an updated allowed network slice determined by the first network node for a target terminal device.
  • the second network node may be further operative to, when the updated allowed network slice is different from currently selected network slice for the target terminal device, instruct the target terminal device to perform re-registration with the updated allowed network slice.
  • the second network node may be operative to perform the method according to the above second aspect.
  • the computer program product may contain instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any of the above first and second aspects.
  • a computer readable storage medium may store thereon instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any of the above first and second aspects.
  • a first network node related to policy control.
  • the first network node may comprise a first determination module for determining, for a target terminal device, whether one or more conditions under which to update an allowed network slice for the target terminal device are met.
  • the first network node may further comprise a second determination module for, when determining that the one or more conditions are met, determining an updated allowed network slice for the target terminal device.
  • the first network node may further comprise a provision module for, when determining that the one or more conditions are met and after the updated allowed network slice is determined, providing to a second network node related to access and mobility management information related to the updated allowed network slice.
  • a second network node related to access and mobility management.
  • the second network node may comprise an obtaining module for obtaining, from a first network node related to policy control, information related to an updated allowed network slice determined by the first network node for a target terminal device.
  • the second network node may further comprise a control module for, when the updated allowed network slice is different from currently selected network slice for the target terminal device, instructing the target terminal device to perform re-registration with the updated allowed network slice.
  • a ninth aspect of the disclosure there is provided a method implemented in a communication system including a first network node related to policy control and a second network node related to access and mobility management.
  • the method may comprise steps of the methods according to the above first and second aspects.
  • the communication system may comprise a first network node related to policy control according to the above third or seventh aspect, and a second network node related to access and mobility management according to the above fourth or eighth aspect.
  • the first response, or the second response, or the third request may comprise a first indicator indicating the information related to the updated allowed network slice.
  • the fourth response, or the fifth response, or the sixth request may comprise a second indicator indicating the information related to the updated allowed network slice.
  • the first network node may be a policy control function (PCF) .
  • PCF policy control function
  • the second network node may be an access and mobility management function (AMF) .
  • AMF access and mobility management function
  • FIG. 1 is a flowchart illustrating a process for creating a UE policy association
  • FIG. 2 is a diagram illustrating different scenarios of registration procedure for initial registration
  • FIG. 3 is a diagram illustrating an exemplary communication system into which an embodiment of the disclosure is applicable
  • FIG. 4 is a flowchart illustrating a method performed by a first network node according to an embodiment of the disclosure
  • FIG. 5 is a flowchart illustrating a method performed by a first network node according to an embodiment of the disclosure
  • FIGs. 6A-6C are flowcharts for explaining the method of FIG. 4;
  • FIGs. 7A-7C are flowcharts for explaining the method of FIG. 4;
  • FIG. 8 is a flowchart illustrating a method performed by a first network node according to an embodiment of the disclosure
  • FIG. 9 is a flowchart illustrating a method performed by a first network node according to an embodiment of the disclosure.
  • FIG. 10 is a flowchart illustrating a method performed by a first network node according to an embodiment of the disclosure
  • FIG. 11 is a flowchart illustrating a method performed by a second network node according to an embodiment of the disclosure
  • FIG. 12 is a flowchart illustrating a method performed by a second network node according to an embodiment of the disclosure
  • FIGs. 13A-13C are flowcharts for explaining the method of FIG. 11;
  • FIGs. 14A-14C are flowcharts for explaining the method of FIG. 11;
  • FIGs. 15A-15B are flowcharts each illustrating a method performed by a second network node according to an embodiment of the disclosure
  • FIGs. 16A-16B are flowcharts each illustrating a method performed by a second network node according to an embodiment of the disclosure
  • FIGs. 17A-17C are flowcharts each illustrating an exemplary process according to an embodiment of the disclosure.
  • FIG. 18 is a flowchart illustrating an exemplary process according to an embodiment of the disclosure.
  • FIGs. 19A-19B are flowcharts illustrating an exemplary process according to an embodiment of the disclosure.
  • FIG. 20 is a block diagram illustrating an apparatus suitable for use in practicing some embodiments of the disclosure.
  • FIG. 21 is a block diagram illustrating a first network node according to an embodiment of the disclosure.
  • FIG. 22 is a block diagram illustrating a second network node according to an embodiment of the disclosure.
  • FIG. 23 is diagram illustrating an example of a communication system in accordance with some embodiments.
  • FIG. 24 is a block diagram of a host in accordance with various aspects described herein.
  • FIG. 25 is a diagram illustrating a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • a policy control function provides UE policy information control as described in clause 6.1.2.2 of 3GPP TS 23.503 V18.0.0.
  • UE route selection policy (URSP) is used by the UE to determine how to route outgoing traffic and it is described in clause 6.6.2 of 3GPP TS 23.503 V18.0.0.
  • the traffic can be routed to an established PDU session, can be offloaded to non-3GPP access outside a PDU session, or can trigger the establishment of a new PDU session.
  • Network slice selection policy (NSSP) is used by the UE to associate the matching application with single network slice selection assistance information (S-NSSAI) . It may include either a single value or a list of values of S-NSSAI (s) .
  • location criteria and time window are possible to be defined as route selection validation criteria.
  • the UE could select S-NSSAI based on location criteria and/or time window.
  • the procedure for Npcf_UEPolicyControl_Create Service is applicable when the network function (NF) service consumer creates a UE policy association in the following cases: 1) UE performs initial registration to the network, as defined in clause 5.5.1.2.2 of 3GPP TS 24.501 V18.0.0; 2) UE performs a mobility registration, if the UE operating in single-registration mode performs inter-system change from S1 mode to N1 mode, as defined in clause 5.5.1.3.2 of 3GPP TS 24.501 V18.0.0, and there is no existing UE Policy Association between access and mobility management function (AMF) and PCF for this UE; and 3) the AMF is relocated (between the different AMF sets) and the new AMF selects a new PCF.
  • AMF access and mobility management function
  • FIG. 1 illustrates the procedure used for the creation of a policy association.
  • the PCF represents the visited PCF (V-PCF) , if the NF service consumer is an AMF, and the PCF represents the home PCF (H-PCF) , if the NF service consumer is a V-PCF.
  • V-PCF visited PCF
  • H-PCF home PCF
  • the AMF When a UE registers to the network and a UE context is being established, if the AMF obtains from the UE a UE policy delivery protocol message as defined in Annex D of 3GPP TS 24.501 V18.0.0 and/or the authorized PC5 capability for 5G proximity services (ProSe) , and/or the authorized PC5 capability for vehicle-to-everything (V2X) communications, the AMF shall establish a UE policy association with the (V-) PCF, in case there is no existing UE policy association for the UE; otherwise, the AMF may establish a UE Policy Association with the (V-) PCF based on AMF local configuration. Note that in the roaming scenario, the visited AMF’s local configuration can indicate whether UE Policy delivery is needed based on the roaming agreement with the home public land mobile network (PLMN) of the UE.
  • PLMN home public land mobile network
  • the NF service consumer e.g. AMF
  • HTTP hypertext transfer protocol
  • URI Resource uniform resource identifier
  • PolicyAssociationRequest data structure
  • the (V-) (H-) PCF Upon the reception of the HTTP POST request, the (V-) (H-) PCF shall assign a UE policy association ID and determine the applicable UE policy as detailed in clause 4.2.2.2 of 3GPP TS 29.525 V18.0.0. For the successful case, at step 2, the (V-) (H-) PCF shall send a HTTP “201 Created” response having the URI for the created resource in the “Location” header field and the PolicyAssociation data type as response body. Further details about the procedure of FIG. 1 can be obtained from clause 4.2.2 of 3GPP TS 29.525 V18.0.0
  • registration procedure for initiation registration can be used by a UE for initial registration for 5G system (5GS) services.
  • the UE When the UE initiates the registration procedure for initial registration, the UE shall indicate “initial registration” in the 5GS registration type information element (IE) .
  • the UE When the UE initiates the registration procedure for emergency services, the UE shall indicate “emergency registration” in the 5GS registration type IE.
  • the UE When the UE initiates the initial registration for onboarding services in stand-alone non-public network (SNPN) , the UE shall indicate “SNPN onboarding registration” in the 5GS registration type IE.
  • SNPN non-public network
  • the UE When the UE initiates the initial registration procedure for disaster roaming services, the UE shall indicate “disaster roaming initial registration” in the 5GS registration type IE.
  • FIG. 2 illustrates different scenarios of registration procedure for initial registration.
  • the UE initiates the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF, starting timer T3510. If the initial registration request is accepted by the network, the AMF shall send a REGISTRATION ACCEPT message to the UE. If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5G mobility management (5GMM) cause value. Upon reception of the REGISTRATION ACCEPT or REGISTRATION REJECT message, the UE stops the timer T3510.
  • 5GMM 5G mobility management
  • the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3.
  • the AMF shall stop timer T3550 and change to state 5GMM-REGISTERED. Further details about the registration procedure for initial registration can be obtained from clause 5.5.1.2.2 of 3GPP TS 24.501 V18.1.0.
  • Some network operators expect to deploy solutions based on the deployment of multiple network slices and the capability of the network to select dynamically the slice to be used for every different application running in the UE (dynamic slice selection) .
  • This type of solutions can be easily supported in the network based on URSPs, where the network may dynamically update the URSPs to a UE when certain conditions are met or even deliver URSPs which already contain such conditions in the form of time window and location criteria.
  • the operator knows there will be a massive event (e.g. a concert) in a certain area during a specific time window, with potential congestion and traffic degradation in that area, but the operator wants to guarantee the traffic characteristic for some very important person (VIP) users when attending the event.
  • VIP very important person
  • the operator may deploy a dedicated network slice and assign this slice only to the VIP users in the event specific area and time window by using URSPs.
  • the present disclosure proposes an improved solution for network slice control.
  • the solution of the present disclosure will be described in detail with reference to FIGs. 3-25.
  • FIG. 3 is a diagram illustrating an exemplary communication system into which an embodiment of the disclosure is applicable.
  • the communication system comprises a user equipment (UE) 301, a (radio) access network ( (R) AN) 302, a user plane function (UPF) 303, a data network (DN) 304, a network slice-specific and SNPN authentication and authorization function (NSSAAF) 305, an authentication server function (AUSF) 306, an access and mobility management function (AMF) 307, a session management function (SMF) 308, a service communication proxy (SCP) 309, a network slice admission control function (NSACF) 310, a network slice selection function (NSSF) 311, a network exposure function (NEF) 312, a network repository function (NRF) 313, a policy control function (PCF) 314, a unified data management (UDM) 315, an application function (AF) 316, and a network data analytics function (NWDAF) 317.
  • SNPN refers to standalone non-
  • the term UE or terminal device may also be referred to as, for example, device, access terminal, mobile station, mobile unit, subscriber station, or the like. It may refer to any end device that can access a wireless communication network and receive services therefrom.
  • the UE or terminal device may include a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA) , or the like.
  • PDA personal digital assistant
  • a UE or terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE or terminal device and/or a network equipment.
  • the UE or terminal device may be a machine-to-machine (M2M) device, which may, in a 3GPP context, be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • machines or devices may include sensors, metering devices such as power meters, industrial machineries, bikes, vehicles, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, and so on.
  • the term “communication system” refers to a system following any suitable communication standards, such as the first generation (1G) , 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • the communications between a terminal device and a network node (or a network function) in the communication system may be performed according to any suitable generation communication protocols, including, but not limited to, 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • the specific terms used herein do not limit the present disclosure only to the communication system related to the specific terms, which however can be more generally applied to other communication systems.
  • FIG. 4 is a flowchart illustrating a method performed by a first network node related to policy control according to an embodiment of the disclosure.
  • the first network node related to policy control may be a PCF or any other network node (or network function) having similar functionality.
  • the network node (or network function) mentioned in this document may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the first network node determines, for a target terminal device, whether one or more conditions under which to update an allowed network slice for the target terminal device are met.
  • the target terminal device may be any terminal device whose owner has a demand for dynamic slice selection service.
  • the owner of the target terminal device may be a VIP user.
  • the updating of the allowed network slice may cover multiple cases.
  • a first case the target terminal device is registering to the network and is served by the first network node for the first time, and a first set of one or more conditions are met to trigger the updating.
  • a first allowed network slice corresponding to the first set of one or more conditions is determined for the first time.
  • the updating in the first case is from null to one.
  • a second case after the first allowed network slice has been determined, a second set of one or more conditions are met to trigger the updating.
  • a second allowed network slice corresponding to the second set of one or more conditions is determined.
  • corresponding allowed network slice may be determined.
  • the updating in the second case is from one to a different one.
  • the one or more conditions may be a first condition that a location of the target terminal device is inside or outside an area.
  • the area may be represented by a cell identifier (ID) , or a tracking area identity (TAI) , or a presence reporting area (PRA) , or the like.
  • the first network node may obtain, from a second network node related to access and mobility management, information related to a location of the target terminal device, which will be described later with reference to block 508 of FIG. 5.
  • the second network node related to access and mobility management may be an AMF or any other network node (or network function) having similar functionality.
  • the information related to the location of the target terminal device may be a cell ID, or a TAI, or a notification about the target terminal device entering or leaving a PRA, or the like.
  • the first network node Based on the obtained information related to the location of the target terminal device, the first network node can determine whether the first condition is met.
  • the one or more conditions may be a second condition that current time is inside or outside a time period.
  • the first network node can determine whether the second condition is met, based on its local time.
  • the one or more conditions may be a third condition that a network at an area where the target terminal device is located is or is to be in congested status, or changes from congested status to normal status.
  • the area may be represented by a cell ID, or a TAI, or the like.
  • the first network node may obtain, from a third network node related to network monitoring, information related to a network status at an area where the target terminal device is located, which will be described later with reference to block 510 of FIG. 5.
  • the third network node related to network monitoring may be an NWDAF, or any other network node (or network function) having similar functionality. Based on the obtained information related to the network status, the first network node can determine whether the third condition is met.
  • the one or more conditions may be a fourth condition that an internal event of the first network node occurs.
  • the internal event may be a time trigger (e.g. the current time is a predetermined time) or any other suitable event inside the first network node.
  • the first network node can determine that the fourth condition is met.
  • the one or more conditions may be a fifth condition that a trigger is received from another network node.
  • the another network node may include, but not limited to, an AF, an NWDAF, a charging function (CHF) , a unified data repository (UDR) , a time sensitive communication time synchronization function (TSCTSF) , etc.
  • the trigger may comprise e.g. predetermined application or service information.
  • the trigger may comprise e.g. network congestion information.
  • the trigger may comprise e.g. spending limit report.
  • the trigger may comprise e.g. a policy subscription change.
  • any two or more of the above first to fifth conditions may be combined as the one or more conditions.
  • the present disclosure is not limited to the above options and any other suitable option may be employed depending on the specific application scenario (e.g. as the operator requires) .
  • the first network node determines an updated allowed network slice for the target terminal device.
  • the updated allowed network slice for the target terminal device may be determined based on a pre-configuration in the first network node.
  • the pre-configuration comprises one or more rules each of which indicates, for the target terminal device or a terminal device group containing the target terminal device, the one or more conditions and a corresponding updated allowed network slice.
  • the pre-configuration may be from e.g. the operator of the network.
  • the updated allowed network slice specified in the pre-configuration may be represented in any suitable form such as S-NSSAI.
  • the pre-configuration may comprise two rules.
  • the first rule may specify that when the location of the target terminal device is inside an area (e.g. an area where a massive event is to be held) and the current time is inside a time period (e.g. a time period during which the massive event is to be held) , a first slice (e.g. a dedicated slice) is used.
  • the second rule may specify that when the location of the target terminal device is outside the area or the current time is outside the time period, a second slice (e.g. a normal slice) is used.
  • the first network node when determining that the one or more conditions are met and after the updated allowed network slice is determined, provides, to a second network node related to access and mobility management, information related to the updated allowed network slice.
  • the second network node related to access and mobility management may be an AMF or any other network node (or network function) having similar functionality.
  • the information related to the updated allowed network slice may be information for the updated allowed network slice used by the target terminal device, e.g. an S-NSSAI corresponding to the updated allowed network slice.
  • block 406 may be implemented as blocks 612-614 as shown in FIG. 6A, or blocks 616-618 as shown in FIG. 6B, or blocks 620-622 as shown in FIG. 6C.
  • the first network node receives, from the second network node, a first request for creating an access and mobility (AM) policy association between the second network node and the first network node for the target terminal device.
  • the AM policy association is an association by which AM policy control for a given terminal device can be performed between two network nodes.
  • the first network node sends, to the second network node, a first response to the first request.
  • the first response indicates the information related to the updated allowed network slice.
  • the first request may be Npcf_AMPolicyControl_Create Request and the first response may be Npcf_AMPolicyControl_Create Response.
  • the first network node receives, from the second network node, a second request for modifying an AM policy association between the second network node and the first network node for the target terminal device.
  • the first network node sends, to the second network node, a second response to the second request.
  • the second response indicates the information related to the updated allowed network slice.
  • the second request may be Npcf_AMPolicyControl_Update Request and the second response may be Npcf_AMPolicyControl_Update Response.
  • the first network node sends, to the second network node, a third request for updating AM policies related to an AM policy association between the second network node and the first network node for the target terminal device.
  • the third request indicates the information related to the updated allowed network slice.
  • the first network node receives, from the second network node, a third response to the third request.
  • the third request may be Npcf_AMPolicyControl_UpdateNotify Request and the third response may be Npcf_AMPolicyControl_UpdateNotify Response. More details about the procedures related to AM policy association can be obtained from 3GPP TS 29.507 V18.0.0, chapter 4.2.2 to chapter 4.2.4.
  • the information related to the updated allowed network slice may be indicated by the first response, or the second response, or the third request in various ways.
  • the first response, or the second response, or the third request may comprise a first indicator indicating the information related to the updated allowed network slice.
  • block 406 may be implemented as blocks 712-714 as shown in FIG. 7A, or blocks 716-718 as shown in FIG. 7B, or blocks 720-722 as shown in FIG. 7C.
  • the first network node receives, from the second network node, a fourth request for creating a UE policy association between the second network node and the first network node for the target terminal device.
  • the UE policy association is an association by which UE policy control for a given terminal device can be performed between two network nodes.
  • the first network node sends, to the second network node, a fourth response to the fourth request.
  • the fourth response indicates the information related to the updated allowed network slice.
  • the fourth request may be Npcf_UEPolicyControl_Create Request and the fourth response may be Npcf_UEPolicyControl_Create Response.
  • the first network node receives, from the second network node, a fifth request for modifying a UE policy association between the second network node and the first network node for the target terminal device.
  • the first network node sends, to the second network node, a fifth response to the fifth request.
  • the fifth response indicates the information related to the updated allowed network slice.
  • the fifth request may be Npcf_UEPolicyControl_Update Request and the fifth response may be Npcf_UEPolicyControl_Update Response.
  • the first network node sends, to the second network node, a sixth request for updating UE policies related to a UE policy association between the second network node and the first network node for the target terminal device.
  • the sixth request indicates the information related to the updated allowed network slice.
  • the first network node receives, from the second network node, a sixth response to the sixth request.
  • the sixth request may be Npcf_UEPolicyControl_UpdateNotify Request and the sixth response may be Npcf_UEPolicyControl_UpdateNotify Response. More details about the procedures related to UE policy association can be obtained from in 3GPP TS 29.525 V18.0.0, chapter 4.2.2 to chapter 4.2.4.
  • the information related to the updated allowed network slice may be indicated by the fourth response, or the fifth response, or the sixth request in various ways.
  • the fourth response, or the fifth response, or the sixth request may comprise a second indicator indicating the information related to the updated allowed network slice.
  • block 406 may be implemented through a new service procedure between the first network node and the second network node.
  • a request and a response may be communicated between the first network node and the second network node in the new service procedure.
  • the information related to the updated allowed network slice may be indicated by either the request or the response.
  • either the request or the response may comprise a indicator indicating the information related to the updated allowed network slice.
  • the first network node With the method of FIG. 4, it is possible for the first network node to provide dynamic slice selection service to those terminal devices even if they do not support URSP. This could facilitate the deployment of 5G differentiated UE slicing services for all users independently on their terminal capabilities.
  • FIG. 5 is a flowchart illustrating a method performed by a first network node related to policy control according to an embodiment of the disclosure. As shown, the method comprises blocks 508-510, and blocks 402-406 described above.
  • the first network node obtains, from a second network node related to access and mobility management, information related to a location of the target terminal device.
  • the second network node related to access and mobility management may be an AMF or any other network node (or network function) having similar functionality.
  • the information related to the location of the target terminal device may be a cell ID, or a TAI, or a notification about the target terminal device entering or leaving a PRA, or the like.
  • the second network node such as an AMF can manage the access and mobility of the target terminal device
  • the second network node can know the cell ID of the cell serving the target terminal device, or the TAI of the tracking area (TA) where the target terminal device is located.
  • the first network node can obtain the cell ID or the TAI from the second network node through any suitable procedure.
  • the first network node may send, to the second network node (e.g. an AMF) , a subscription request for subscribing to reporting a change of the target terminal device’s presence in PRA (s) which are the areas of interest.
  • the subscription request may include a list of PRA ID (s) .
  • PRA ID a short list of TAs and/or next generation RAN (NG-RAN) nodes and/or cells identifiers may be included.
  • the reporting may be requested for the specific condition when the target terminal device moves into or outside the specified PRA(s) .
  • the second network node may activate the relevant procedure which reports any change of the target terminal device’s presence in the specified PRA (s) .
  • the second network node may report the PRA ID (s) and indication (s) whether the target terminal device is inside or outside the PRA (s) to the first network node. More details about the example of PRA can be obtained from clause 5.6.11 of 3GPP TS 23.501 V18.0.0 and clause 6.1.2.5 of 3GPP TS 23.503 V18.0.0.
  • the first network node obtains, from a third network node related to network monitoring, information related to a network status at an area where the target terminal device is located.
  • the third network node related to network monitoring may be an NWDAF, or an OAM, or any other network node (or network function) having similar functionality.
  • the first network node may send, to the third network node, a subscription request for subscribing to a notification about presence or absence of congested status of the network at specified area (s) (e.g. in the form of cell ID, TAI, etc. ) .
  • the third network node may send a notification about the congested status and corresponding area (s) to the first network node. If the reported area (s) comprise the area where the target terminal device is located, the first network node may determine that the network at the area where the target terminal device is located is or is to be in congested status, or changes from congested status to normal status. Note that the congested status is merely an exemplary example for illustration purpose and other status of the network is also possible depending on the specific application scenario.
  • the first network node determines, for a target terminal device, whether one or more conditions under which to update an allowed network slice for the target terminal device are met. If the one or more conditions involve a location of the target terminal device, the determination at block 402 may be based on the information obtained at block 508. If the one or more conditions involve network status, the determination at block 402 may be based on the information obtained at block 510. Therefore, depending on the one or more conditions, either block 508 or block 510 in FIG. 5 may be an optional block.
  • the first network node determines an updated allowed network slice for the target terminal device.
  • the first network node provides, to the second network node related to access and mobility management, information related to the updated allowed network slice.
  • various factors such as UE location, time and network status can be used to flexibly define the condition (s) for network slice updating.
  • FIG. 8 is a flowchart illustrating a method performed by a first network node related to policy control according to an embodiment of the disclosure.
  • the first network node determines whether the target terminal device has URSP capability. For example, the determination at block 824 may be based on one or more of: 5G mobility management (5GMM) capability that is sent by the target terminal device and forwarded by a second network node related to access and mobility management (e.g. an AMF) ; an indication at terminal device level that is provisioned within policy data in a UDR; and an indication at terminal device level that is provisioned within subscription data in a UDR and provided by the second network node during a UE policy association establishment for the target terminal device.
  • 5GMM 5G mobility management
  • AMF access and mobility management
  • blocks 402 to 406 the determining of whether the one or more conditions are met, the determining of the updated allowed network slice and the providing of the information related to the updated allowed network slice are performed.
  • the terminal device (s) having no URSP capability can receive dynamic slice service enabled via the first network node, while the terminal device (s) having URSP capability can still use the URSP capability for dynamic slice selection.
  • FIG. 9 is a flowchart illustrating a method performed by a first network node related to policy control according to an embodiment of the disclosure.
  • the first network node receives, from a second network node related to access and mobility management, a third indicator indicating whether the second network node supports applying the updated allowed network slice to the target terminal device.
  • the third indicator may be included in the above-mentioned first request for creating an AM policy association between the second network node and the first network node for the target terminal device.
  • the third indicator may be included in the above-mentioned fourth request for creating a UE policy association between the second network node and the first network node for the target terminal device.
  • the first network node may determine whether the third indicator indicates that the second network node supports applying the updated allowed network slice to the target terminal device.
  • the determination result at block 928 is positive (when the third indicator indicates that the second network node supports applying the updated allowed network slice to the target terminal device)
  • blocks 402 to 406 the determining of whether the one or more conditions are met, the determining of the updated allowed network slice and the providing of the information related to the updated allowed network slice.
  • FIG. 10 is a flowchart illustrating a method performed by a first network node related to policy control according to an embodiment of the disclosure.
  • the first network node determines, for a target terminal device, whether one or more conditions under which to update an allowed network slice for the target terminal device are met.
  • the first network node determines an updated allowed network slice for the target terminal device.
  • the first network node receives, from a second network node related to access and mobility management, identifiers of one or more allowed network slices of the target terminal device. For example, the identifiers of one or more allowed network slices of the target terminal device may be received in the first request (e.g.
  • Npcf_AMPolicyControl_Create request Npcf_AMPolicyControl_Create request
  • the second request e.g. Npcf_AMPolicyControl_Update request
  • the fourth request e.g. Npcf_UEPolicyControl_Create request
  • the fifth request e.g. Npcf_UEPolicyControl_Update request
  • the first network node may determine whether the updated allowed network slice is one of the identified allowed network slices.
  • block 406 the providing of the information related to the updated allowed network slice.
  • FIG. 11 is a flowchart illustrating a method performed by a second network node related to access and mobility management according to an embodiment of the disclosure.
  • the second network node related to access and mobility management may be an AMF or any other network node (or network function) having similar functionality.
  • the second network node obtains, from a first network node related to policy control, information related to an updated allowed network slice determined by the first network node for a target terminal device.
  • the first network node related to policy control may be a PCF or any other network node (or network function) having similar functionality.
  • the information related to the updated allowed network slice may be information for the updated allowed network slice used by the target terminal device, e.g. an S-NSSAI corresponding to the updated allowed network slice.
  • block 1102 may be implemented as blocks 1312-1314 as shown in FIG. 13A, or blocks 1316-1318 as shown in FIG. 13B, or blocks 1320-1322 as shown in FIG. 13C.
  • the second network node sends, to the first network node, a first request for creating an AM policy association between the second network node and the first network node for the target terminal device.
  • the second network node receives, from the first network node, a first response to the first request.
  • the first response indicates the information related to the updated allowed network slice.
  • the first request may be Npcf_AMPolicyControl_Create Request and the first response may be Npcf_AMPolicyControl_Create Response.
  • the second network node sends, to the first network node, a second request for modifying an AM policy association between the second network node and the first network node for the target terminal device.
  • the second network node receives, from the first network node, a second response to the second request.
  • the second response indicates the information related to the updated allowed network slice.
  • the second request may be Npcf_AMPolicyControl_Update Request and the second response may be Npcf_AMPolicyControl_Update Response.
  • the second network node receives, from the first network node, a third request for updating AM policies related to an AM policy association between the second network node and the first network node for the target terminal device.
  • the third request indicates the information related to the updated allowed network slice.
  • the second network node sends, to the first network node, a third response to the third request.
  • the third request may be Npcf_AMPolicyControl_UpdateNotify Request and the third response may be Npcf_AMPolicyControl_UpdateNotify Response.
  • the information related to the updated allowed network slice may be indicated by the first response, or the second response, or the third request in various ways.
  • the first response, or the second response, or the third request may comprise a first indicator indicating the information related to the updated allowed network slice.
  • block 1102 may be implemented as blocks 1412-1414 as shown in FIG. 14A, or blocks 1416-1418 as shown in FIG. 14B, or blocks 1420-1422 as shown in FIG. 14C.
  • the second network node sends, to the first network node, a fourth request for creating a UE policy association between the second network node and the first network node for the target terminal device.
  • the second network node receives, from the first network node, a fourth response to the fourth request.
  • the fourth response indicates the information related to the updated allowed network slice.
  • the fourth request may be Npcf_UEPolicyControl_Create Request and the fourth response may be Npcf_UEPolicyControl_Create Response.
  • the second network node sends, to the first network node, a fifth request for modifying a UE policy association between the second network node and the first network node for the target terminal device.
  • the second network node receives, from the first network node, a fifth response to the fifth request.
  • the fifth response indicates the information related to the updated allowed network slice.
  • the fifth request may be Npcf_UEPolicyControl_Update Request and the fifth response may be Npcf_UEPolicyControl_Update Response.
  • the second network node receives, from the first network node, a sixth request for updating UE policies related to a UE policy association between the second network node and the first network node for the target terminal device.
  • the sixth request indicates the information related to the updated allowed network slice.
  • the second network node sends, to the first network node, a sixth response to the sixth request.
  • the sixth request may be Npcf_UEPolicyControl_UpdateNotify Request and the sixth response may be Npcf_UEPolicyControl_UpdateNotify Response.
  • the information related to the updated allowed network slice may be indicated by the fourth response, or the fifth response, or the sixth request in various ways.
  • the fourth response, or the fifth response, or the sixth request may comprise a second indicator indicating the information related to the updated allowed network slice.
  • block 1102 may be implemented through a new service procedure between the first network node and the second network node.
  • a request and a response may be communicated between the first network node and the second network node in the new service procedure.
  • the information related to the updated allowed network slice may be indicated by either the request or the response.
  • either the request or the response may comprise a third indicator indicating the information related to the updated allowed network slice.
  • the second network node instructs the target terminal device to perform re-registration with the updated allowed network slice.
  • the updating of the allowed network slice may cover multiple cases.
  • the target terminal device is registering to the network and is served by the first network node for the first time.
  • the network slice currently selected by the second network node for the target terminal device may be e.g. a default slice.
  • the target terminal device has registered to the network with a certain network slice or has established a PDU session over the certain network slice.
  • the network slice currently selected by the second network node for the target terminal device is the network slice currently used by the target terminal device.
  • the second network node may instruct the target terminal device to perform re-registration with the updated allowed network slice.
  • the updated configuration for the target terminal device comprises the information related to the updated allowed network slice. Note that if the updated allowed network slice is the same as the currently selected network slice for the target terminal device, the re-registration of the target terminal device is not necessary.
  • the second network node With the method of FIG. 11, it is possible for the second network node to provide dynamic slice selection service to those terminal devices even if they do not support URSP. With the information related to an updated allowed network slice provided by the first network node, the second network node can allocate the updated allowed network slice through UE configuration update to a terminal device not supporting URSP. This could facilitate the deployment of 5G differentiated UE slicing services for all users independently on their terminal capabilities.
  • FIG. 12 is a flowchart illustrating a method performed by a second network node related to access and mobility management according to an embodiment of the disclosure. As shown, the method comprises blocks 1102-1104 described above, and block 1206.
  • the method of FIG. 11 may correspond to e.g. a scenario where in response to the instruction from the second network node, the target terminal device performs re-registration with the updated allowed network slice; and because the target terminal device has no demand to transmit and/or receive user traffic, no PDU session is established.
  • the method of FIG. 12 may correspond to e.g. a scenario where in response to the instruction from the second network node, the target terminal device performs re-registration with the updated allowed network slice; and because the target terminal device has a demand to transmit and/or receive user traffic, one or more PDU sessions are established.
  • the second network node establishes, for the target terminal device, one or more PDU sessions over the updated allowed network slice. For example, when the second network node receives, from the target terminal device, one or more requests for establishing the one or more PDU sessions and the one or more requests indicate the updated allowed network slice (e.g. in “S-NSSAI” IE) , the one or more PDU sessions may be established based on the updated allowed network slice indicated by the target terminal device. The second network node may use the updated allowed network slice to discover a network node related to session management (e.g. an SMF) so as to establish the one or more PDU sessions.
  • a network node related to session management e.g. an SMF
  • the one or more PDU sessions may be established based on the information related to the updated allowed network slice that is obtained from the first network node. In this way, the PDU session (s) can be established over the updated allowed network slice no matter whether or not the target terminal device indicates the updated allowed network slice when initiating the establishment of the one or more PDU sessions.
  • user traffic can be transferred through the PDU session (s) established over the updated allowed network slice to implement differentiated UE slicing services.
  • FIG. 15A is a flowchart illustrating a method performed by a second network node related to access and mobility management according to an embodiment of the disclosure.
  • the second network node determines whether a terminal device has URSP capability.
  • the “terminal device” mentioned at block 1524 may be any terminal device served by the second network node.
  • the determination at block 1524 may be based on one or more of: 5GMM capability sent by the terminal device; and an indication at terminal device level that is provisioned within subscription data in a UDR.
  • the second network node establishes, for the terminal device, an AM policy association between the second network node and the first network node at block 1526.
  • the second network node may send, to the first network node, a request for creating an AM policy association between the second network node and the first network node for the terminal device. Then, the second network node may receive a response from the first network node. More details about the establishment of AM policy association can be obtained from 3GPP TS 29.507 V18.0.0, chapter 4.2.2.
  • the second network node establishes, for the terminal device, a UE policy association between the second network node and the first network node at block 1528.
  • the second network node may send, to the first network node, a request for creating a UE policy association between the second network node and the first network node for the terminal device. Then, the second network node may receive a response from the first network node. More details about the establishment of UE policy association can be obtained from 3GPP TS 29.525 V18.0.0, chapter 4.2.2.
  • the two types of terminal devices can be differentiated to allow the first network node to perform different processing for the two types of terminal devices.
  • the terminal device (s) having no URSP capability can receive dynamic slice service enabled via the first network node, while the terminal device (s) having URSP capability can still use the URSP capability for dynamic slice selection.
  • FIG. 15B is a flowchart illustrating a method performed by a second network node related to access and mobility management according to an embodiment of the disclosure.
  • the second network node establishes, for a terminal device, a UE policy association between the second network node and the first network node irrespective of whether the terminal device has URSP capability.
  • the “terminal device” mentioned at block 1530 may be any terminal device served by the second network node.
  • the processing of the second network node can be simplified to let the first network node differentiate between the two types of terminal devices and perform different processing for them.
  • the terminal device (s) having no URSP capability can receive dynamic slice service enabled via the first network node, while the terminal device (s) having URSP capability can still use the URSP capability for dynamic slice selection.
  • FIG. 16A is a flowchart illustrating a method performed by a second network node related to access and mobility management according to an embodiment of the disclosure.
  • the second network node sends, to the first network node, a third indicator indicating whether the second network node supports applying the updated allowed network slice to the target terminal device.
  • the third indicator may be included in the above-mentioned first request for creating an AM policy association between the second network node and the first network node for the target terminal device.
  • the third indicator may be included in the above-mentioned fourth request for creating a UE policy association between the second network node and the first network node for the target terminal device.
  • the third indicator indicates that the second network node supports applying the updated allowed network slice to the target terminal device.
  • the second network node obtains, from a first network node related to policy control, information related to an updated allowed network slice determined by the first network node for a target terminal device.
  • the second network node instructs the target terminal device to perform re-registration with the updated allowed network slice.
  • FIG. 16B is a flowchart illustrating a method performed by a second network node related to access and mobility management according to an embodiment of the disclosure.
  • the second network node sends, to the first network node, identifiers of one or more allowed network slices of the target terminal device.
  • the identifiers of one or more allowed network slices of the target terminal device may be sent in the first request (e.g. Npcf_AMPolicyControl_Create request) , or the second request (e.g. Npcf_AMPolicyControl_Update request) , or the fourth request (e.g. Npcf_UEPolicyControl_Create request) , or the fifth request (e.g.
  • the second network node obtains, from a first network node related to policy control, information related to an updated allowed network slice determined by the first network node for a target terminal device.
  • the second network node instructs the target terminal device to perform re-registration with the updated allowed network slice.
  • Block 1634 corresponds to block 1030 performed at the first network node side as described above. Because of the sending performed at block 1634, the first network node can determine whether the updated allowed network slice is one of the identified allowed network slices, and provide the information related to the updated allowed network slice to the second network node when the updated allowed network slice is one of the identified allowed network slices. Accordingly, possible failure of registration or establishment of PDU session over the updated allowed network slice due to network slice being invalid can be avoided.
  • FIGs. 17A-17C are flowcharts each illustrating an exemplary process according to an embodiment of the disclosure.
  • a typical use case is considered where there are two slices deployed in the network: a default slice (enhanced mobile broadband (eMBB) slice) ; and a dedicated slice (aConcert slice) .
  • eMBB enhanced mobile broadband
  • a dedicated slice aConcert slice
  • the operator would change the traffic established on PDU sessions towards the default slice to PDU sessions on the dedicated slice when the VIP users enter a concert area at specific time, in order to guarantee the VIP users’ experience in the case of possible network high load or congestion.
  • the processes shown in FIGs. 17A-17C are applicable to a solution for the above use case.
  • AM policy control between a PCF and an AMF is extended to dynamically provide an allowed slice to the AMF when a certain condition like location or time is met.
  • the AMF updates the allowed slice to the UE and triggers UE configuration update with the indication of registration.
  • the UE re-registers and establishes a new PDU session with/without the new allowed slice being indicated in the PDU Session Establishment procedure. Note that in the case of without the new allowed slice being indicated, the AMF would apply the new allowed slice to the PDU session when discovering an SMF instance.
  • the feature negotiation between the AMF and the PCF is also proposed to be executed.
  • the feature name may be “SliceSelection” .
  • the PCF may also check that the proposed “pcfAllowedSnssais” are among the ones allowed by the UE by checking “allowedSnssais” attribute received from the AMF.
  • the proposed “pcfAllowedSnssais” may be included by the PCF in the policy decision during AM policy session establishment, AM policy session Update and AM policy session UpdateNotify procedure by the PCF, as shown in FIGs. 17A-17C.
  • the AMF decides to establish AM Policy Association.
  • the AMF sends to the PCF an Npcf_AMPolicyControl_Create request.
  • the PCF may provide UE allowed slice to the AMF based on the obtained information (such as UE location etc. ) and according to operator policies (e.g. the PCF may provide concert slice as the only allowed slice for the UE if the UE is in the specific area and time for the concert) .
  • the AMF sends to the PCF an Npcf_AMPolicyControl_Update Request.
  • the PCF makes a policy decision.
  • the PCF may provide UE allowed slice to the AMF based on the obtained information (such as UE location etc. ) and according to operator policies (e.g. the PCF may provide concert slice as the only allowed slice for the UE if the UE is in the specific area and time for the concert) .
  • a PCF internal event occurs.
  • the PCF makes a policy decision.
  • the PCF may provide UE allowed slice to the AMF based on internal triggers or external triggers (such as relevant analytics information from an NWDAF, etc. ) and according to operator policies (e.g. the PCF may provide concert slice as the only allowed slice for the UE if the UE is in the specific area and time for the concert) .
  • UE policy control association between the PCF and the AMF is extended in a similar way as described in the above solution. Since it is assumed that the UEs do not support yet URSPs, the UEs will not include the UE Policy Container in the initial registration as described in 3GPP TS 24.501 V18.1.0, clause 5.5.1.2.2. So the AMF should be locally configured to trigger the UE Policy Association establishment even in case no UE Policy Container is received (as described in 3GPPG TS 29.525 V18.0.0, clause 4.2.2) .
  • a new service between the PCF and the AMF may be used for the transference of the new information described in the above two solutions.
  • the PCF determines the allowed S-NSSAI to a UE when certain UE/network condition is met and updates the AMF with UE allowed S-NSSAI info.
  • the AMF could trigger UE re-registration in UE configuration update procedure and a new PDU session could be established with the new allowed S-NSSAI.
  • the PCF for example by selecting the dedicated slice (concert) as the only allowed network slice for a VIP user when entering the specific area and time of the concert enables the switching of the VIP UE’s traffic from the potentially congested default slice (e.g. MBB) to the dedicated slice (concert) .
  • the potentially congested default slice e.g. MBB
  • FIG. 18 is a flowchart illustrating an exemplary process according to an embodiment of the disclosure.
  • the AMF receives the UE allowed slice from the PCF in Npcf_AMPolicyControl Create/Update/UpdateNotify procedure and detects that the UE allowed slice is changed, the AMF triggers update of UE configuration for re-registration with the new allowed slice.
  • the AMF sends UE Configuration Update Command containing the new allowed slice to the UE.
  • the UE Configuration Update Indication contained in the UE Configuration Update Command requires acknowledgement of the UE Configuration Update Command, then the UE shall send a UE Configuration Update complete message to the AMF.
  • the AMF also uses the Nudm_SDM_Info service operation to provide an acknowledgment to UDM that the UE received CAG information as part of the Mobility Restrictions (if the CAG information was updated) , or the Network Slicing Subscription Change Indication (if this was indicated in step 1) and acted upon it.
  • the AMF performs an update to the RAN.
  • the UE if the UE is configured with a new 5G-GUTI in step 2a via non-3GPP access and the UE is registered to the same PLMN via both 3GPP and non-3GPP access, then the UE passes the new 5G-GUTI to its 3GPP access’ lower layers. If the UE is configured with a new 5G-GUTI in step 2a over the 3GPP access, the UE passes the new 5G-GUTI to its 3GPP access’ lower layers.
  • NAS non-access stratum
  • CM-IDLE connection management IDLE
  • the UE shall initiate a Registration procedure immediately after the acknowledgement to re-negotiate the updated NAS parameter (s) with the network. Steps 3b, 3c and step 4 are skipped.
  • step 3b if a new Allowed NSSAI and/or a new Mapping Of Allowed NSSAI and/or a new Configured NSSAI provided by the AMF to the UE in step 1 does not affect the existing connectivity to AMF, the AMF needs not release the NAS signalling connection for the UE after receiving the acknowledgement in step 2 and immediate registration is not required. The UE can start immediately using the new Allowed NSSAI and/or the new Mapping Of Allowed NSSAI.
  • the AMF indicates to the SMF (s) the corresponding PDU Session ID (s) and each SMF releases the PDU Session (s) according to clause 4.3.4.2.
  • the UE cannot connect to an S-NSSAI included in the new Configured NSSAI for the Serving PLMN but not included in the new Allowed NSSAI until the UE performs a Registration procedure and includes a Requested NSSAI based on the new Configured NSSAI, following the requirements described in clause 5.15.5.2 of TS 23.501 V18.0.0. Steps 3c and 4 are skipped.
  • the AMF may, based on its policy, provide anyway an indication that a Registration procedure is required even though the UE Configuration Update Command in step 1 does not affect the existing connectivity to Network Slices: in such a case only step 3c is skipped.
  • step 3c if a new Allowed NSSAI and/or a new Mapping Of Allowed NSSAI and/or a new Configured NSSAI provided by the AMF to the UE in step 1 affects ongoing existing connectivity to AMF, then the AMF shall provide an indication that the UE shall initiate a Registration procedure.
  • the AMF shall release the NAS signalling connection for the UE by triggering the access network (AN) Release procedure, unless there is one established PDU Sessions associated with regulatory prioritized services. More details about the process of FIG. 18 can be obtained from 3GPP TS 23.502 v18.0.0, chapter 4.6.1 to chapter 4.6.3 and chapter 4.2.4.2.
  • FIGs. 19A-19B are flowcharts illustrating an exemplary process according to an embodiment of the disclosure. The process shown in FIGs. 19A-19B is applicable to two different solutions for a mixed scenario where a part of UEs have URSP capability and another part of UEs have no URSP capability in the network.
  • the first solution is PCF centric.
  • the AMF always establishes UE Policy Association (even when no UE Policy container is received) .
  • the PCF decides whether to send URSP updates or pcfAllowedSnssais based on one or more of: 5GMM capability that is sent by the UE and forwarded by the AMF; indication at UE level that is provisioned within PolicyData in a UDR (or indication at data plane) , e.g. the device +operating system (OS) used by the subscription supports URSP; indication at UE level that is provisioned within SubscriptionData in a UDR (UDM data) and provided by the AMF during the UE Policy Association establishment, e.g. the device + OS used by the subscription supports URSP.
  • the PCF may decide to send URSP updates when the UE supports URSP, and to send pcfAllowedSnssais when the UE does not support URSP.
  • the PCF could configure dynamic policies at UE level or data plane level that provides pcfAllowedSnssais and the new policies would result in values of pcfAllowedSnssais.
  • the second option is AMF centric. If the AMF is configured to do not use AM Policies. Then, the AMF decides whether to establish AM Policy Association (just for the purpose of receiving pcfAllowedSnssais) based on one or more of: 5GMM capability sent by the UE; indication at UE level that is provisioned within SubscriptionData in a UDR (UDM data) , e.g. indication indicating whether the UE (the device + OS used by the subscription) supports URSP. Thus, the AMF may decide to establish AM Policy Association when the UE does not support URSP, and to establish UE Policy Association when the UE supports URSP.
  • AM Policy Association just for the purpose of receiving pcfAllowedSnssais
  • the AMF decides whether to establish UE Policy Association based on one or more of: 5GMM capability sent by the UE; indication at UE level that is provisioned within SubscriptionData in a UDR (UDM data) , e.g. indication indicating whether the UE (the device + OS used by the subscription) supports URSP.
  • 5GMM capability sent by the UE
  • indication at UE level that is provisioned within SubscriptionData in a UDR (UDM data) e.g. indication indicating whether the UE (the device + OS used by the subscription) supports URSP.
  • the PCF upon the reception of AM Policy Association establishment, the PCF needs to determine whether to send pcfAllowedSnssais based on one or more of: 5GMM capability that is sent by the UE and forwarded by the AMF; indication at UE level that is provisioned within PolicyData in a UDR (or indication at data plane level) , e.g. the device + OS used by the subscription supports URSP; indication at UE level that is provisioned within SubscriptionData in a UDR (UDM data) and provided by the AMF during the UE Policy Association establishment, e.g. the device + OS used by the subscription supports URSP.
  • 5GMM capability that is sent by the UE and forwarded by the AMF
  • indication at UE level that is provisioned within PolicyData in a UDR or indication at data plane level
  • indication at UE level that is provisioned within SubscriptionData in a UDR (UDM data) and provided by the AMF during the UE Policy Association establishment e.g. the device
  • the PCF could configure dynamic policies at UE level or data plane level that provides pcfAllowedSnssais and the new policies would result in values of pcfAllowedSnssais.
  • step 21b the AMF always establishes UE policy associate with the PCF.
  • the PCF decides if pcfAllowedSnssais need be provided to the AMF in step 16.
  • step 16 the AMF decides to establish AM policy association with the PCF if the UE has no URSP capability. Note that other details of the process shown in FIGs. 19A-19B can be obtained from section 4.2.2.2.2 of 3GPP TS 23.502 V18.0.0.
  • the PCF could decide whether to update slice in URSP profile or not based on the configured condition (s) .
  • the UE (s) supporting URSP may receive the updated URSP profile from the PCF via the AMF and enforce the slice selection based on the updated URSP profile.
  • FIG. 20 is a block diagram illustrating an apparatus suitable for use in practicing some embodiments of the disclosure.
  • the apparatus 2000 may include a processor 2010, a memory 2020 that stores a program, and optionally a communication interface 2030 for communicating data with other external devices through wired and/or wireless communication.
  • the program includes program instructions that, when executed by the processor 2010, enable the apparatus 2000 to operate in accordance with the embodiments of the present disclosure, as discussed above. That is, the embodiments of the present disclosure may be implemented at least in part by computer software executable by the processor 2010, or by hardware, or by a combination of software and hardware.
  • the memory 2020 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memories, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories.
  • the processor 2010 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples.
  • FIG. 21 is a block diagram illustrating a first network node related to policy control according to an embodiment of the disclosure.
  • the first network node 2100 comprises a first determination module 2102, a second determination module 2104 and a provision module 2106.
  • the first determination module 2102 may be configured to determine, for a target terminal device, whether one or more conditions under which to update an allowed network slice for the target terminal device are met, as described above with respect to block 402.
  • the second determination module 2104 may be configured to, when determining that the one or more conditions are met, determine an updated allowed network slice for the target terminal device, as described above with respect to block 404.
  • the provision module 2106 may be configured to, when determining that the one or more conditions are met and after the updated allowed network slice is determined, provide to a second network node related to access and mobility management information related to the updated allowed network slice, as described above with respect to block 406.
  • FIG. 22 is a block diagram illustrating a second network node related to access and mobility management according to an embodiment of the disclosure.
  • the second network node 2200 comprises an obtaining module 2202 and a control module 2204.
  • the obtaining module 2202 may be configured to obtain, from a first network node related to policy control, information related to an updated allowed network slice determined by the first network node for a target terminal device, as described above with respect to block 1102.
  • the control module 2204 may be configured to, when the updated allowed network slice is different from currently selected network slice for the target terminal device, instruct the target terminal device to perform re-registration with the updated allowed network slice, as described above with respect to block 1104.
  • the modules described above may be implemented by hardware, or software, or a combination of both.
  • FIG. 23 shows an example of a communication system 3100 in accordance with some embodiments.
  • the communication system 3100 includes a telecommunication network 3102 that includes an access network 3104, such as a radio access network (RAN) , and a core network 3106, which includes one or more core network nodes 3108.
  • the access network 3104 includes one or more access network nodes, such as network nodes 3110a and 3110b (one or more of which may be generally referred to as network nodes 3110) , or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 3110 facilitate direct or indirect connection of user equipment (UE) , such as by connecting UEs 3112a, 3112b, 3112c, and 3112d (one or more of which may be generally referred to as UEs 3112) to the core network 3106 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 3100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 3100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 3112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 3110 and other communication devices.
  • the network nodes 3110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 3112 and/or with other network nodes or equipment in the telecommunication network 3102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 3102.
  • the core network 3106 connects the network nodes 3110 to one or more hosts, such as host 3116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 3106 includes one more core network nodes (e.g., core network node 3108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 3108.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC) , Mobility Management Entity (MME) , Home Subscriber Server (HSS) , Access and Mobility Management Function (AMF) , Session Management Function (SMF) , Authentication Server Function (AUSF) , Subscription Identifier De-concealing function (SIDF) , Unified Data Management (UDM) , Security Edge Protection Proxy (SEPP) , Network Exposure Function (NEF) , and/or a User Plane Function (UPF) .
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 3116 may be under the ownership or control of a service provider other than an operator or provider of the access network 3104 and/or the telecommunication network 3102, and may be operated by the service provider or on behalf of the service provider.
  • the host 3116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 3100 of FIG. 23 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM) ; Universal Mobile Telecommunications System (UMTS) ; Long Term Evolution (LTE) , and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G) ; wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi) ; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax) , Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile
  • the telecommunication network 3102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 3102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 3102. For example, the telecommunications network 3102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC) /Massive IoT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 3112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 3104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 3104.
  • a UE may be configured for operating in single-or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC) , such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio -Dual Connectivity (EN-DC) .
  • MR-DC multi-radio dual connectivity
  • the hub 3114 communicates with the access network 3104 to facilitate indirect communication between one or more UEs (e.g., UE 3112c and/or 3112d) and network nodes (e.g., network node 3110b) .
  • the hub 3114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 3114 may be a broadband router enabling access to the core network 3106 for the UEs.
  • the hub 3114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 3114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 3114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 3114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 3114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 3114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 3114 may have a constant/persistent or intermittent connection to the network node 3110b.
  • the hub 3114 may also allow for a different communication scheme and/or schedule between the hub 3114 and UEs (e.g., UE 3112c and/or 3112d) , and between the hub 3114 and the core network 3106.
  • the hub 3114 is connected to the core network 3106 and/or one or more UEs via a wired connection.
  • the hub 3114 may be configured to connect to an M2M service provider over the access network 3104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 3110 while still connected via the hub 3114 via a wired or wireless connection.
  • the hub 3114 may be a dedicated hub -that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 3110b.
  • the hub 3114 may be a non-dedicated hub -that is, a device which is capable of operating to route communications between the UEs and network node 3110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 24 is a block diagram of a host 3200, which may be an embodiment of the host 3116 of FIG. 23, in accordance with various aspects described herein.
  • the host 3200 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 3200 may provide one or more services to one or more UEs.
  • the host 3200 includes processing circuitry 3202 that is operatively coupled via a bus 3204 to an input/output interface 3206, a network interface 3208, a power source 3210, and a memory 3212.
  • processing circuitry 3202 that is operatively coupled via a bus 3204 to an input/output interface 3206, a network interface 3208, a power source 3210, and a memory 3212.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures such that the descriptions thereof are generally applicable to the corresponding components of host 3200.
  • the memory 3212 may include one or more computer programs including one or more host application programs 3214 and data 3216, which may include user data, e.g., data generated by a UE for the host 3200 or data generated by the host 3200 for a UE.Embodiments of the host 3200 may utilize only a subset or all of the components shown.
  • the host application programs 3214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC) , High Efficiency Video Coding (HEVC) , Advanced Video Coding (AVC) , MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC) , MPEG, G.711) , including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems) .
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG MPEG
  • VP9 Video Coding
  • audio codecs e.g., FLAC, Advanced Audio Coding (AAC) , MPEG, G.711
  • UEs e.g., handsets, desktop computers, wearable display systems, heads-up display systems
  • the host application programs 3214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 3200 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 3214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP) , Real-Time Streaming Protocol (RTSP) , Dynamic Adaptive Streaming over HTTP (MPEG-DASH) , etc.
  • FIG. 25 shows a communication diagram of a host 3302 communicating via a network node 3304 with a UE 3306 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as a UE 3112a of FIG. 23) , network node (such as network node 3110a of FIG. 23) , and host (such as host 3116 of FIG. 23 and/or host 3200 of FIG. 24) discussed in the preceding paragraphs will now be described with reference to FIG. 25.
  • host 3302 Like host 3200, embodiments of host 3302 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 3302 also includes software, which is stored in or accessible by the host 3302 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 3306 connecting via an over-the-top (OTT) connection 3350 extending between the UE 3306 and host 3302.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 3350.
  • the network node 3304 includes hardware enabling it to communicate with the host 3302 and UE 3306.
  • the connection 3360 may be direct or pass through a core network (like core network 3106 of FIG. 23) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 3106 of FIG. 23
  • one or more other intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 3306 includes hardware and software, which is stored in or accessible by UE 3306 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 3306 with the support of the host 3302.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 3306 with the support of the host 3302.
  • an executing host application may communicate with the executing client application via the OTT connection 3350 terminating at the UE 3306 and host 3302.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 3350 may extend via a connection 3360 between the host 3302 and the network node 3304 and via a wireless connection 3370 between the network node 3304 and the UE 3306 to provide the connection between the host 3302 and the UE 3306.
  • the connection 3360 and wireless connection 3370, over which the OTT connection 3350 may be provided, have been drawn abstractly to illustrate the communication between the host 3302 and the UE 3306 via the network node 3304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 3302 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 3306.
  • the user data is associated with a UE 3306 that shares data with the host 3302 without explicit human interaction.
  • the host 3302 initiates a transmission carrying the user data towards the UE 3306.
  • the host 3302 may initiate the transmission responsive to a request transmitted by the UE 3306.
  • the request may be caused by human interaction with the UE 3306 or by operation of the client application executing on the UE 3306.
  • the transmission may pass via the network node 3304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 3312, the network node 3304 transmits to the UE 3306 the user data that was carried in the transmission that the host 3302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 3314, the UE 3306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 3306 associated with the host application executed by the host 3302.
  • the UE 3306 executes a client application which provides user data to the host 3302.
  • the user data may be provided in reaction or response to the data received from the host 3302. Accordingly, in step 3316, the UE 3306 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 3306. Regardless of the specific manner in which the user data was provided, the UE 3306 initiates, in step 3318, transmission of the user data towards the host 3302 via the network node 3304.
  • the network node 3304 receives user data from the UE 3306 and initiates transmission of the received user data towards the host 3302.
  • the host 3302 receives the user data carried in the transmission initiated by the UE 3306.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3306 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the quality of service and thereby provide benefits such as improved user experience.
  • factory status information may be collected and analyzed by the host 3302.
  • the host 3302 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 3302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights) .
  • the host 3302 may store surveillance video uploaded by a UE.
  • the host 3302 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 3302 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices) , or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 3302 and/or UE 3306.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 3304. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 3302.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while monitoring propagation times, errors, etc.
  • the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.
  • exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device.
  • the computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc.
  • the function of the program modules may be combined or distributed as desired in various embodiments.
  • the function may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.
  • FPGA field programmable gate arrays
  • connection cover the direct and/or indirect connection between two elements. It should be noted that two blocks shown in succession in the above figures may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

Landscapes

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

Abstract

Sont divulgués des procédés et des appareils de commande de tranche de réseau. Selon un mode de réalisation, un premier nœud de réseau associé à une commande de politique détermine, pour un équipement terminal cible, si une ou plusieurs conditions dans lesquelles mettre à jour une tranche de réseau autorisée pour le dispositif terminal cible sont satisfaites. Lorsqu'il est déterminé que la ou les conditions sont satisfaites, le premier nœud de réseau détermine une tranche de réseau autorisée mise à jour pour l'équipement terminal cible et fournit à un second nœud de réseau associé à la gestion d'accès et de mobilité des informations relatives à la tranche de réseau autorisée mise à jour.
PCT/CN2024/086822 2023-04-19 2024-04-09 Procédés et appareils de commande de tranche de réseau Pending WO2024217298A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2023089257 2023-04-19
CNPCT/CN2023/089257 2023-04-19

Publications (1)

Publication Number Publication Date
WO2024217298A1 true WO2024217298A1 (fr) 2024-10-24

Family

ID=93152026

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/086822 Pending WO2024217298A1 (fr) 2023-04-19 2024-04-09 Procédés et appareils de commande de tranche de réseau

Country Status (1)

Country Link
WO (1) WO2024217298A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190268835A1 (en) * 2018-05-18 2019-08-29 Intel Corporation Ue indication to pcf whether or not to send ue policy
WO2022152616A2 (fr) * 2021-01-15 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils pour modifier une tranche de réseau
CN115299108A (zh) * 2020-03-19 2022-11-04 诺基亚技术有限公司 改进的服务连续性
US20230112434A1 (en) * 2021-09-30 2023-04-13 Mediatek Inc. Ursp enhancement for eps

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190268835A1 (en) * 2018-05-18 2019-08-29 Intel Corporation Ue indication to pcf whether or not to send ue policy
CN115299108A (zh) * 2020-03-19 2022-11-04 诺基亚技术有限公司 改进的服务连续性
WO2022152616A2 (fr) * 2021-01-15 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils pour modifier une tranche de réseau
US20230112434A1 (en) * 2021-09-30 2023-04-13 Mediatek Inc. Ursp enhancement for eps

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DONGEUN SUH, [ZTE, LG ELECTRONICS, ERICSSON, LENOVO, INTERDIGITAL, APPLE,SAMSUNG, NOKIA, NOKIA SHANGHAI BELL], SAMSUNG, NEC, VERIZ: "Support of network slice replacement", 3GPP DRAFT; S2-2303032; TYPE CR; CR 4083; ENS_PH3, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Athens, GR; 20230220 - 20230224, 10 February 2023 (2023-02-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052236322 *
VIVO: "Network slice replacement update for NSSF", 3GPP DRAFT; S2-2304912, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. Electronic meeting; 20230417 - 20230421, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052467103 *

Similar Documents

Publication Publication Date Title
JP7667826B2 (ja) 仮想化されたモバイルコアネットワークへの接続
CN113678423B (zh) 动态网络能力配置
US20240073848A1 (en) Network Slice in a Wireless Network
US20180352501A1 (en) Method And Apparatus For Virtualized Network Service Provision
WO2021223507A1 (fr) Procédé et appareil de communication, et puce
CN112400332A (zh) Pws消息和关联的区域信息的分段
CN112911631A (zh) 业务服务质量监测方法、设备及系统
WO2024217298A1 (fr) Procédés et appareils de commande de tranche de réseau
WO2024169729A1 (fr) Procédé et appareil de gestion de session
WO2024169845A1 (fr) Procédé et appareil de facturation
WO2024227388A1 (fr) Procédés et dispositifs d'indication d'informations
WO2025002402A1 (fr) Procédé et appareil d'exposition d'informations de domaine d'équipement utilisateur à une fonction d'application
WO2024159987A1 (fr) Procédés et appareils pour mise à jour de mappage ebi et arp
WO2023143097A1 (fr) Procédé et appareil destinés à un service de multidiffusion/diffusion
WO2024083103A1 (fr) Procédé et appareil d'authentification
WO2024138618A1 (fr) Procédé et appareil de gestion de session d'échange de clé internet (ike)
WO2024067680A9 (fr) Procédé et appareil de gestion de session
US20250081257A1 (en) Device-to-Network Relaying for an Emergency Service
WO2024126146A1 (fr) Procédé et appareil de gestion de session de qualité de service de réseau de données de bord
WO2024146809A1 (fr) Procédé et appareil pour services différenciés
WO2024172730A1 (fr) Conditions d'exécution pour cho avec pscell/scg associé
WO2024121402A1 (fr) Procédé et appareil de communication à relais
KR20240008925A (ko) 통신 방법 및 장치

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: 24791883

Country of ref document: EP

Kind code of ref document: A1