Method for managing slice allocation - Patents.com

Abstract

[0006] Methods, apparatuses, and systems for providing management of network slices are disclosed. In one aspect, a wireless communication method is disclosed. The method includes receiving, by a network-side function operating in a wireless network in which network services are provided as one or more network slices, a request for allocation information associated with network slice selection assistance information. The process further includes transmitting, by the network-side function, the allocation information related to the network slice information in response to the request.

Description

[Technical field]

[0001] This patent document is generally directed to wireless communications. [Background technology]

[0002] Mobile communication technologies are moving the world towards an increasingly connected and networked society. The rapid growth of mobile communications and technological advances have led to further demand for capacity and connectivity. Other aspects such as energy consumption, device cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Various techniques, including new methods, are being discussed to provide higher quality of service, longer battery life, and improved performance. Summary of the Invention [Means for solving the problem]

[0003] This patent document describes, among other things, techniques that enable management of network slices.

[0004] In one aspect, a wireless communication method is disclosed. The method includes receiving, by a network side function operating in a wireless network in which network services are provided as one or more network slices, a request for allocation information associated with network slice selection assistance information. The process further includes transmitting, by the network side function in response to the request, the allocation information related to the network slice information.

[0005] In another aspect, another wireless communication method is disclosed. The method includes sending, by a first network side function, a request for slice allocation information to a second network side function. The method further includes receiving, by the first network side function, the slice allocation information from the second network side function, where the slice allocation information is determined by the second network side function.

[0006] In another aspect, another wireless communication method is disclosed. The method includes storing, by a first network side function, slice allocation information regarding a slice for which a network service is provided. The method further includes enforcing, by the first network side function, the slice allocation information.

[0007] In another aspect, another wireless communication method is disclosed. The method includes sending a request for slice allocation information for a home network from a first network side function to a second network side function. The method further includes receiving, at the first network side function, a response to the request from the second network side function, the response including the slice allocation information for the home network. The method further includes enforcing, by the first network side function, the slice allocation information for the home network according to the network slice information.

[0008] In another aspect, another wireless communication method is disclosed. The method includes determining, by a slice allocation management (SQM) function, slice allocation information according to network slice information. The method further includes sending, by the SQM function, the slice allocation information to an access and mobility management function (AMF). The method further includes receiving, at the SQM function, a notification of an overflow of the slice allocation information from the AMF.

[0009] In another exemplary aspect, a communications apparatus is disclosed, the apparatus including a processor configured to implement the methods described above.

[0010] In yet another exemplary aspect, a computer program storage medium is disclosed that includes code stored thereon that, when executed by a processor, causes the processor to implement the methods described above.

[0011] These and other aspects are described herein. The present invention further provides, for example, the following: (Item 1) 1. A wireless communication method, the method comprising: receiving, by a network side function operating in a wireless network in which network services are provided as one or more network slices, a request for allocation information associated with network slice information; transmitting, by the network side function, in response to the request, the allocation information relating to the network slice information; A method comprising: (Item 2) 2. The method of claim 1, wherein the request is received from an Access and Mobility Function (AMF) in the wireless network. (Item 3) 2. The method of claim 1, wherein the request is received from a network side function other than AMF. (Item 4) A method according to any of items 1-3, wherein the allocation information comprises a limit on the number of wireless devices that are allowed to register with the network slice identified by the network slice information. (Item 5) 5. A method according to any of items 1-4, wherein the allocation information comprises a limit on the number of protocol data unit (PDU) sessions that can operate within the network slice identified by the network slice information. (Item 6) 6. The method of claim 1, wherein the allocation information comprises a maximum data rate supported by a network slice identified by the network slice information. (Item 7) 1. A wireless communication method, the method comprising: sending, by a first network-side function, a request for slice allocation information to a second network-side function; receiving, by the first network-side function, the slice allocation information from the second network-side function; Including, The method, wherein the slice allocation information is determined by the second network side function. (Item 8) The method of item 7, further comprising receiving, in a first network side function, information that the network slice is subject to allocation management. (Item 9) 8. The method of claim 7, wherein the request includes one or more of network slice information, capabilities of the first network side function, or an identification of the first network side function. (Item 10) 10. The method of claim 9, wherein the first network side function stores local allocation information of the network slice information. (Item 11) 1. A wireless communication method, the method comprising: storing, by a first network-side function, slice allocation information regarding slices for which a network service is provided; implementing, by the first network-side function, the slice allocation information; A method comprising: (Item 12) notifying the second network side function of an overflow of the slice allocation information by the first network side function; The first network side function transmits a back-off timer value to a user equipment (UE) according to network slice information when the overflow occurs. 12. The method of claim 11, further comprising: (Item 13) 1. A wireless communication method, the method comprising: sending a request for slice allocation information for a home network from a first network side function to a second network side function; receiving, at the first network-side function, from the second network-side function, a response to the request including the slice allocation information for the home network; implementing, by the first network side function, the slice allocation information for the home network according to the network slice information; A method comprising: (Item 14) The method described in item 13, further comprising, in a first network side function, receiving information that the home network is subject to allocation management in accordance with the network slice information. (Item 15) A method according to any of items 7-14, wherein the first network side function is an Access and Mobility Management Function (AMF) and the second network side function is a Slice Allocation Management (SQM) function. (Item 16) 1. A wireless communication method, the method comprising: determining slice allocation information according to the network slice information through a slice allocation management (SQM) function; Sending the slice allocation information to an access and mobility management function (AMF) by the SQM function; receiving, in the SQM function, a notification of an overflow of the slice allocation information from the AMF; A method comprising: (Item 17) A method according to any of items 7-16, wherein the slice allocation information comprises a limit on the number of wireless devices allowed to register in the network slice identified by the network slice information, the limit including a maximum number of user equipment. (Item 18) The method of claim 16, wherein the enforcing includes approving the registration of a user equipment in the network slice when a total number of user equipments served by the network slice is less than or equal to a maximum number, and rejecting the registration of the user equipment in the network slice when a total number of the user equipments served by the network slice exceeds the maximum number. (Item 19) The method according to any of items 7-18, wherein the slice allocation information includes a maximum number of protocol data unit (PDU) sessions served by the network slice identified by the network slice information. (Item 20) The method of any of items 7-19, wherein the slice allocation information includes a maximum data rate supported by a network slice identified by the network slice information. (Item 21) A method according to any of items 1-20, wherein the network slice information is network slice selection assistance information (NSSAI) of a 5G network. (Item 22) A communication device comprising a processor, the processor configured to implement the method defined in any one or more of items 1-21. (Item 23) A computer program product storing code which, when executed by a processor, causes the processor to implement a method defined in any one or more of items 1-21. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 depicts a network architecture according to some example embodiments.

[0013] [Diagram 2] FIG. 2 depicts an example architecture including slice allocation management (SQM) functionality according to some illustrative embodiments.

[0014] [Diagram 3] FIG. 3 illustrates an example of a process for slice allocation management when a UE is not roaming in accordance with some demonstrative embodiments.

[0015] [Figure 4] FIG. 4 depicts slice allocations stored in a slice allocation management function that are transmitted to a network function, such as an access and mobility management function, to be enforced on roaming user equipment in accordance with some demonstrative embodiments.

[0016] [Diagram 5] FIG. 5 depicts a process for application functionality for managing slice allocation information according to some example embodiments.

[0017] [Figure 6] FIG. 6 depicts an example method according to some exemplary embodiments.

[0018] [Figure 7] FIG. 7 depicts another example of a method according to some exemplary embodiments.

[0019] [Figure 8] FIG. 8 depicts yet another example of a method according to some exemplary embodiments.

[0020] [Figure 9] FIG. 9 depicts yet another example of a method according to some exemplary embodiments.

[0021] [Figure 10] FIG. 10 depicts yet another example of a method according to some exemplary embodiments.

[0022] [Figure 11] FIG. 11 illustrates an example of a wireless communication system in accordance with some demonstrative embodiments.

[0023] [Figure 12] FIG. 12 depicts an example block diagram of a portion of a wireless system in accordance with some exemplary embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] Certain features are described using the example of a fifth generation (5G) wireless protocol, however, the applicability of the disclosed techniques is not limited to only 5G wireless systems.

[0025] This patent document relates to a network slice, which is a logical network that provides specific network capabilities and network characteristics. A network slice instance is a set of network function instances and required resources (such as computing, storage, and networking resources) that form a deployed network slice.

[0026] Network slices are a tool for operators to provide specific network capabilities for their own services or third-party services. Operators need a solution to determine slice allocation information (such as the maximum number of UEs registered in a network slice, the maximum number of PDU sessions in the network slice, and the maximum data rate supported by the network slice). This information is a key input to scale the network slice and provide it with sufficient resources. This information is also used to fulfill any service layer agreements with third-party applications.

[0027] This patent document describes techniques for managing slice allocation information for network slices.

[0028] Figure 1 depicts a network architecture according to some example embodiments. Figure 1 depicts a user equipment (UE) 150 in communication with a radio access network (RAN) 145, which is part of a visited public land mobile network (vPLMN) 110A. The UE 150 is roaming from its home network, hPLMN 110B. Components of the architecture are described below.

[0029] The UE 150 may include devices such as a mobile phone, a tablet, or other mobile device.

[0030] The RAN 145 includes base stations.

[0031] An Access and Mobility Management Function (AMF) 135A in the vPLMN 110A, and an AMF 135B in the hPLMN 110B. Each AMF includes the following functionality: registration management, attachment management, reachability management, and mobility management. This function also performs access authentication and access authorization. The AMF is a non-access stratum (NAS) security termination and relays session management (SM) NAS between the UE and the SMF, etc.

[0032] A Session Management Function (SMF) 130A in the vPLMN 110A, and an hSMF 130B in the hPLMN 110B. Each SMF includes the following functionality: session establishment, modification and release, UE Internet Protocol (IP) address allocation and management (which may include optional authorization functions, UP function selection and control, downlink data notification, etc.).

[0033] A User Plane Function (UPF) 140A in the vPLMN 110A, and an hUPF 140B in the hPLMN 110B. Each UPF includes the following functionality: acting as an anchor point for intra / inter-radio access technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, Quality of Service (QoS) handling for the user plane, downlink packet buffering, and downlink data notification triggering, etc.

[0034] A Network Exposure Function (NEF) 115A in the vPLMN 110A, and an hNEF 115B in the hPLMN 110B. Each NEF supports the exposure of network capabilities and events to application functions. Third party application functions can invoke services provided by the network through the NEF, and the NEF performs authentication and authorization of third party applications. The NEF also provides translation between information exchanged with the AF and information exchanged with internal network functions.

[0035] An Application Function (AF) 120A in the vPLMN 110A, and an AF 120B in the hPLMN 110B. Each AF interacts with the 3GPP® Core Network (CN) and provides services to support, for example: application influence on traffic routing, access to network exposure functions, interaction with a policy framework for policy control, etc. Application functions may be delegated by an operator and allowed to interact directly with network functions. Application functions may not be allowed by an operator to directly access network functions and may use an external exposure framework via the NEF to interact with network functions.

[0036] A network slice selection function (NSSF) 125A in the vPLMN 110A, and an hNSSF 125B in the hPLMN 110B. Each NSSF selects a set of network slice instances to serve the UE and determines the allowed network slice selection assistance information (NSSAI) that the UE is allowed to use within its current registration area. In roaming, there is one NSSF in the vPLMN and one NSSF in the hPLMN. When determining the allowed NSSAI, the vNSSF queries the hNSSF as to whether the network slice is allowed.

[0037] In some exemplary embodiments, the network slice information may be an NSSAI and / or single slice selection assistance information (S-NSSAI).

[0038]

[0023] Figure 2 illustrates an example of the architecture depicted in Figure 1 modified in accordance with some exemplary embodiments. The architecture of Figure 2 includes a slice allocation management (SQM) function for handling slice allocation.

[0039] A slice allocation management (SQM) 155A in the vPLMN 110A, and an hSQM 125B in the hPLMN 110B. Each SQM manages slice allocation for each slice. The SQM stores the following information for each network slice: allocation information indicating the maximum number of UEs that can be registered in the network slice, allocation information indicating the maximum number of PDU sessions in the network slice, and allocation information indicating the maximum data rate supported by the network slice.

[0040] The slice information stored in the SQM is not exclusively stored in the SQM. The SQM manages the global value of the allocation information to enforce the allocation, divides the global value into local values ​​based on a service level agreement (SLA), and sends the local value to a network function such as the AMF. The SQM may be notified by the network function if the local allocation is overflowing, and the SQM may update the local allocation of the network function. When the global value of the allocation is overflowing, the SQM notifies the Operations, Administration, and Management (OAM) function and the AF. When a UE is roaming from an hPLMN to a vPLMN, each network may have an associated SQM, i.e., a home SQM (hSQM) in the hPLMN and a visited SQM (vSQM) in the vPLMN.

[0041] The slice allocation information in the SQM can be managed by the application function via the NEF. Multiple allocation values ​​are possible for a single type per network slice, e.g., the AF can store different allocation values ​​for the maximum number of UEs registered in the network slice and be notified when one of the allocations is overflowing.

[0042] 3 illustrates an example process for slice allocation management when the UE is not roaming. For example, FIG. 3 illustrates how slice allocations stored in the SQM are sent to a network function, such as the AMF, to be enforced.

[0043] In 301, the UE 315 sends a registration request message to the AMF 320. In the message, the UE includes a requested single NSSAI (S-NSSAI).

[0044] At 302, the AMF 320 sends a slice selection request to the NSSF 325 to select a network slice for the UE 315. The AMF 320 provides the NSSF 325 with the requested S-NSSAI, the subscribed S-NSSAI, and the UE location.

[0045] In 303, the NSSF 325 determines the allowed NSSAIs for the UE 315. The allowed NSSAIs are a list of NSSAIs that the UE is allowed to use in its current registration area. The NSSF returns the allowed NSSAIs to the AMF. For each S-NSSAI in the allowed NSSAIs, the NSSF includes an indication of whether the S-NSSAI is subject to allocation enforcement.

[0046] In 304, if an S-NSSAI subject to allocation enforcement exists in the allowed NSSAI and the AMF does not have local allocation information for the S-NSSAI, the AMF sends a message to the SQM for allocation information for the S-NSSAI. The request message may include the S-NSSAI, AMF capability information, and / or an AMF identifier.

[0047] In 305, the SQM determines local allocation information for the AMF and returns the local allocation information to the AMF. The AMF stores the local allocation information in the S-NSSAI. When the AMF pair is deployed, the SQM determines the local allocation information for each AMF pair.

[0048] For the first UE to be registered in a network slice in the AMF, 304 and 305 are performed. If the AMF has already stored the local allocation information of the S-NSSAI and the local allocation information has not overflowed, the AMF does not need to query the SQM again. When the SQM decides to update the allocation information, the SQM subscribes to and sends the update information to the associated AMF.

[0049] At 306, when the local allocation information is stored in the AMF, the AMF enforces the allocation information. If the maximum number of UEs does not exceed the maximum number for the network slice, the AMF continues to register additional UEs. If the maximum number of UEs exceeds the maximum number for the network slice, the AMF rejects registering additional UEs.

[0050] At 307, the AMF continues the registration procedure.

[0051] At 308, the AMF returns a registration acknowledgement message to the UE.

[0052] At 309, the AMF continues to enforce slice allocation as detailed below.

[0053] The AMF tracks the number of UEs registered in a network slice (S-NSSAI is in the UE's authorized NSSAI). The AMF updates the number when a UE is newly registered in the AMF or deregistered in the AMF, or when a UE is handed over to a new AMF or handed over from another AMF. Each UE context in the AMF includes an authorized NSSAI. The number of UEs registered in the AMF for a network slice is compared with the maximum number allowed from the allocation information.

[0054] The AMF tracks the number of PDU sessions in the network slice (a PDU session is associated with an S-NSSAI). The AMF updates the number of sessions when a PDU session is newly established or released in the AMF, or when a PDU session is handed over to a new AMF or passed to the AMF from another AMF. Each UE context in the AMF includes a PDU session identifier and an associated S-NSSAI. In some implementations, when a UE deactivates a PDU session due to radio resource limitations, the AMF does not need to update the number of tracked PDU sessions. The number of PDU sessions for the network slice is compared with the maximum allowable number of PDU sessions from the allocation information.

[0055] The AMF tracks the data rate used by the network slice as described below and compares it with the maximum data rate supported by the network slice from the allocation information. The AMF has a maximum data rate for the network slice and a maximum data rate for each UE registered in the network slice. The maximum data rate per slice for each UE can be from the UE subscription data or from the PCF (Policy Control Function). The AMF sums up the network slice data rates for all UEs in the network slice for a UE that is registered in the network slice, has established a PDU session in the network slice, and is in a connected state if radio resources are allocated to the PDU session. Alternatively, the RAN may report the maximum data rate of the network slice to the AMF per UE or per slice when a new QoS flow is established, released, or updated in the slice, and the AMF updates the allocation tracking accordingly.

[0056] At 310, when the allocation information overflows, the AMF sends a notification to the SQM. The notification message includes an AMF identifier and an allocation type.

[0057] In 311, the SQM may adjust the allocation information for the AMF. The SQM may return new allocation information indicating that additional allocations have been allowed by the AMF, or may return information indicating that additional allocations will not be allowed by the AMF. The SQM may also update new allocation information for other AMFs.

[0058] In 312, if a new allocation is received, the AMF performs allocation enforcement as in 309. If no additional allocation is allowed, the AMF sends a NAS message with a cause value indicating that the network slice is overloaded. The NAS message may also include a back-off timer to the UE associated with the slice. The UE should not initiate a service request or registration request towards the slice before the back-off timer expires. Below are some examples showing how to inform the UE:

[0059] a) During the UE registration procedure, if any of the allocation information of the requested S-NSSAI overflows, the AMF sends a registration rejection message to the UE, including the S-NSSAI in which the rejected NSSAI was requested. The cause value is set to "S-NSSAI is not available in the current registration area". A back-off timer may also be sent to the UE, so that the UE will not request the same S-NSSAI before the back-off timer expires if the UE is in the same registration area. If the UE moves out of the registration area, the UE may initiate a registration procedure and request the S-NSSAI again. If the AMF receives new allocation information of the S-NSSAI from the SQM, the AMF may send a new allowed NSSAI including the S-NSSAI in a UE configuration update message to the UE, so that the UE can use this S-NSSAI again.

[0060] b) During the PDU session establishment / modification procedure, if the AMF determines that the maximum number of PDU sessions in the network slice or the maximum data rate supported by the network slice is overflowing, the AMF sends a NAS message to the UE, where the NAS message includes a back-off timer and a NAS message received from the UE. The UE will not send the same NAS message before the back-off timer expires.

[0061] From time to time after 304, the SQM may request that the AMF report the usage of the network slice (including the number of registered UEs, the number of PDU sessions, and the data rate used by the slice). The report may be sent from the AMF once, periodically, or intermittently.

[0062] FIG. 4 depicts slice allocations stored in the SQM, which are sent to a network function, such as the AMF, to be enforced for roaming UEs.

[0063] In 401, the UE initiates a registration request including an S-NSSAI requested to the AMF.

[0064] At 402, the AMF sends a request to the vNSSF to select a network slice for the UE. The AMF provides the vNSSF with a requested S-NSSAI, a subscribed S-NSSAI, and a UE location.

[0065] At 403, the vNSSF determines an allowed NSSAI for the UE. The allowed NSSAI is a list of S-NSSAIs that the UE is allowed to use within the current registration area. If the vNSSF has not cached mapping slice information for the hPLMN for the allowed NSSAI, the vNSSF sends a slice selection request to the hNSSF in the home PLMN (hPLMN). The message may include the allowed NSSAI.

[0066] At 404, the hNSSF determines the mapping slice information in the hPLMN for the allowed NSSAIs and returns it to the vNSSF. For each S-NSSAI in the mapped slice information in the HPLMN, the hNSSF includes an indication of whether the mapped S-NSSAI is subject to allocation enforcement.

[0067] At 405, the NSSF returns to the AMF the allowed NSSAIs along with the mapped slice information in the HPLMN. For each S-NSSA in the allowed NSSAIs, the NSSF also includes an indication of whether the S-NSSAI is subject to allocation enforcement. For each S-NSSA in the mapped slice information in the HPLMN, the vNSSF includes an indication of whether the mapped S-NSSAI is subject to allocation enforcement.

[0068] In 406, if an S-NSSAI in the allowed NSSAI is subject to allocation enforcement and the AMF does not have local allocation information for this S-NSSAI, the AMF requests allocation information for the S-NSSAI from the SQM in the vPLMN. The request message may include the S-NSSAI, AMF capability information, and / or an AMF identifier.

[0069] In 407, the SQM in the VPLMN determines local allocation information for the AMF and returns it to the AMF. The AMF stores the local allocation information of the S-NSSAI in the vPLMN. When the AMF pair is deployed, the SQM determines the local allocation information for each AMF pair.

[0070] At 408, if an S-NSSAI in the mapped slice information in the HPLMN is subject to allocation enforcement and the AMF does not have local allocation information for this mapped S-NSSAI, the AMF requests allocation information for the mapped S-NSSAI from the vSQM. The request message may include the S-NSSAI in the hPLMN, AMF capability information, an AMF identifier, and / or a home PLMN identifier.

[0071] At 409, the vSQM forwards the request to the hSQM in the home PLMN based on the home PLMN identifier.

[0072] At 410, the hSQM determines local allocation information for the AMF and returns the local allocation information to the vSQM. The hSQM may determine the local allocation information based on an inter-PLMN service level agreement. When an AMF pair is deployed, the SQM determines the local allocation information for each AMF pair.

[0073] At 411, the vSQM forwards local allocation information regarding the AMF. The AMF stores the local allocation information of the S-NSSAI in the hPLMN.

[0074] For the first UE registered in the network slice in the AMF, 406 and 411 are performed. If the AMF has already stored the local allocation information of the S-NSSAI in the vPLMN or hPLMN, the AMF does not need to query the vSQM or hSQM again.

[0075] At 406 and 407, when the vSQM decides to update the allocation information, the vSQM sends the update information to the associated AMF.

[0076] At 408 and 411, when the hSQM decides to update the allocation information, the hSQM sends the update information to the associated AMF, either directly or via the vSQM.

[0077] The AMF may also query allocation information from the hSQM without involving the vSQM, in which case step 408 is sent to the hSQM and step 410 is sent to the AMF.

[0078] At 412, when the local allocation information is stored in the AMF, the AMF enforces the allocation information for each S-NSSAI in the vPLMN, each S-NSSAI in the hPLMN, or both. If the maximum number of UEs in the network slice does not exceed the allocation, the AMF continues to register additional UEs. If the maximum number of UEs exceeds the maximum number for the network slice, the AMF rejects registering additional UEs.

[0079] At 413, the AMF continues with the remainder of the registration process.

[0080] At 414, the AMF returns a registration acknowledgement message to the UE.

[0081] At 415, the AMF continues to enforce slice allocation for each S-NSSAI in the vPLMN and / or each S-NSSAI in the hPLMN, or both, as detailed below.

[0082] The AMF tracks the number of UEs registered in the network slice (the S-NSSAI is within the UE's allowed NSSAI and / or the mapped S-NSSAI in the hPLMN is within the corresponding mapped NSSAI in the hPLMN for the allowed NSSAI). The AMF updates the number of UEs when additional UEs are registered in the AMF or when a UE is deregistered in the AMF or when a UE is handed over to a new AMF or handled from another AMF. Each UE context in the AMF includes the allowed NSSAI and the corresponding mapped NSSAI in the hPLMN. The number of UEs registered in the AMF for the network slice is compared with the maximum number allowed from the allocation information.

[0083] The AMF tracks the number of PDU sessions in the network slice (PDU sessions associated with an S-NSSAI in the vPLMN) and tracks the number of home-routed PDU sessions in the network slice (PDU sessions associated with a mapped S-NSSAI in the hPLMN). The AMF updates the number of PDU sessions when a new PDU session is established or released in the AMF, or when a PDU session is handed over to the AMF from another AMF or handled to the AMF from another AMF. Each UE context in the AMF includes a PDU session identifier, an associated S-NSSAI in the vPLMN, and a corresponding mapped NSSAI in the hPLMN. When the UE deactivates a PDU session by radio resources, the AMF does not need to update the number of tracked PDU sessions. The number of PDU sessions for the network slice is compared with the maximum allowable number of PDU sessions from the allocation information.

[0084] The AMF tracks the data rate used by the network slice as described below and is compared with the maximum data rate supported by the network slice from the allocation information. For each UE registered in the network slice, the AMF has the maximum data rate of the network slice. The maximum data rate per slice can be determined from subscription data or from a policy control function (PCF). The AMF can sum up the data rates for all UEs registered in the network slice with an established PDU session in the network slice and in a connected state, meaning that radio resources are allocated to the PDU session. For S-NSSAI in the hPLMN, the AMF may calculate the UEs that have established a home-routed PDU session. Alternatively, the RAN may report the maximum data rate of the network slice to the AMF per UE or per slice when a new QoS flow is established, released, or updated, so that the AMF updates the allocation tracking.

[0085] At 416, if the allocation information of the S-NSSAI in the vPLMN overflows, the AMF sends a notification message to the vSQM. The notification message includes an AMF identifier and an allocation type.

[0086] In 417, the vSQM may adjust the allocation information for the AMF. The vSQM may send a message indicating the additional allocation allocated to the AMF, or may not send the additional allocation to the AMF.

[0087] At 418, if the allocation information of the S-NSSAI in the hPLMN overflows, the AMF sends a notification message to the vSQM. The notification message includes an AMF identifier and an allocation type, and / or a home PLMN identifier.

[0088] At 419, the vSQM forwards the notification to the hSQM.

[0089] At 420, the hSQM may adjust allocation information for the AMF. The hSQM may send a message indicating additional allocation to the vSQM, or may not send additional allocation to the vSQM. The hSQM may update the allocation information without involving the vSQM. In this case, 420 is sent directly to the AMF.

[0090] At 421, the vSQM sends an allocation update message to the AMF.

[0091] In 422, if a new allocation is received, the AMF performs allocation enforcement 412. If no new additional allocation is received, the AMF sends a NAS message with a cause value indicating that the network slice is overloaded. The NAS message may also include a back-off timer associated with the slice to the UE. The UE should not initiate a service request or registration request towards this slice before the back-off timer expires. Below are some examples showing how to inform the UE:

[0092] a) During the UE registration process, if any parameter of the allocation information of the requested S-NSSAI overflows (e.g., the number of registered UEs, the number of PDU sessions, the data rate), the AMF sends a registration rejection message to the UE, in which the rejected NSSAI includes the requested and rejected S-NSSAI. The cause of the rejection is set to "S-NSSAI is not available in the current registration area". A back-off timer may be sent to the UE, so that the UE will not request the same S-NSSAI before the back-off timer expires if the UE is in the same registration area. When the UE moves out of the registration area, the UE may initiate another registration and request the S-NSSAI again. If the AMF receives new allocation information for the S-NSSAI from the SQM, the AMF may send a new allowed NSSAI including the S-NSSAI in a UE Configuration Update message to the UE, so that the UE can use the S-NSSAI again.

[0093] b) During the PDU session establishment / modification procedure, if the AMF determines that an allocation including the maximum number of PDU sessions in the network slice or the maximum data rate supported by the network slice is overflowing, the AMF sends a NAS message to the UE, which includes a back-off timer and a NAS message received from the UE. Thus, the UE will not send the same NAS message before the back-off timer expires.

[0094] At any time after 406 or 409, the vSQM or hSQM may request that the AMF report network slice usage, including the number of registered UEs, the number of PDU sessions, and the data rate used by the slice. The report can be sent once, periodically, or intermittently.

[0095] FIG. 5 depicts a process for an Application Function (AF) to manage slice allocation information stored in the SQM.

[0096] In 501, the AF sends a request to update the allocation information stored in the SQM. If the AF is not delegated, the AF request is sent to the NEF. The message includes the AF identifier, the S-NSSAI, and the associated allocation information.

[0097] At 502, the NEF performs authorization for AF. If successful, the NEF forwards the AF request to the SQM.

[0098] At 503, the SQM stores the new allocation information for the S-NSSAI.

[0099] In 504, the SQM updates the allocation information of the S-NSSAI in the AMF. In case of roaming, this message may be sent directly to the AMF or via the vSQM.

[0100] At 505, the SQM sends a request response to the NEF.

[0101] At 506, the NEF sends a request response to the AF.

[0102] 6 illustrates an example of a method according to some exemplary embodiments. At 610, the method includes receiving, by a network-side function operating in a wireless network in which network services are provided as one or more network slices, a request for allocation information associated with the network slice selection assistance information. At 620, the method includes transmitting, by the network-side function in response to the request, the allocation information for the NSSAI.

[0103] 7 depicts another example of a method according to some demonstrative embodiments. At 710, the method includes sending, by a first network-side function, a request for slice allocation information to a second network-side function. At 720, the method includes receiving, by the first network-side function, slice allocation information from the second network-side function, the slice allocation information being determined by the second network-side function.

[0104] 8 illustrates another example of a method according to some demonstrative embodiments. At 810, the method includes storing, by a first network-side function, slice allocation information regarding slices for which a network service is provided. At 820, the method includes enforcing, by the first network-side function, the slice allocation information.

[0105] 9 depicts another example of a method according to some exemplary embodiments. At 910, the method includes sending a request for slice allocation information for a home network from a first network-side function to a second network-side function. At 920, the method further includes receiving, at the first network-side function, a response to the request from the second network-side function including the slice allocation information for the home network. At 930, the method includes enforcing, by the first network-side function, the slice allocation information for the home network according to the NSSAI.

[0106] 10 depicts another example of a method according to some demonstrative embodiments. At 1010, the method includes determining, by a slice allocation management (SQM) function, slice allocation information according to the NSSAI. At 1020, the method includes sending, by the SQM function, the slice allocation information to an access and mobility management function (AMF). At 1030, the method includes receiving, at the SQM function, a notification from the AMF of an overflow of the slice allocation information.

[0107] 11 illustrates an example of a wireless communication system 1100 to which techniques according to one or more embodiments of the present technology may be applied. The wireless communication system 1100 may include one or more base stations (BSs) 1105a, 1105b, one or more wireless devices 1110a, 1110b, 1110c, 1110d, and a core network 1125. The base stations 1105a, 1105b may provide wireless services to the wireless devices 1110a, 1110b, 1110c, and 1110d in one or more wireless sectors. In some implementations, the base stations 1105a, 1105b include directional antennas to produce two or more directional beams to provide wireless coverage in different sectors.

[0108] The core network 1125 can communicate with one or more base stations 1105a, 1105b. The core network 1125 provides connectivity with other wireless communication systems and with wired communication systems. The core network can include one or more service subscription databases to store information associated with subscribed wireless devices 1110a, 1110b, 1110c, and 1110d. The first base station 1105a can provide wireless services based on a first wireless access technology, while the second base station 1105b can provide wireless services based on a second wireless access technology. The base stations 1105a and 1105b can be co-located or separately installed in a region according to a deployment scenario. The wireless devices 1110a, 1110b, 1110c, and 1110d can support multiple different wireless access technologies. The techniques and embodiments described herein can be implemented by the base stations of the wireless devices described herein.

[0109] FIG. 12 is a block diagram representation of a portion of a wireless station according to one or more embodiments of the present technology may be applied. A wireless station 1205, such as a base station or wireless device (or UE), may include processor electronics 1210, such as a microprocessor, that implements one or more of the wireless techniques presented herein. The wireless station 1205 may include transceiver electronics 1215 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as an antenna 1220. The wireless station 1205 may include other communication interfaces for transmitting and receiving data. The wireless station 1205 may include one or more memories (not explicitly shown) configured to store information, such as data and / or instructions. In some implementations, the processor electronics 1210 may include at least a portion of the transceiver electronics 1215. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the wireless station 1205. In some embodiments, the wireless station 1205 may be configured to perform the methods described herein.

[0110] It should be understood that this document discloses techniques that may be embodied in various embodiments for establishing and managing multicast sessions in various scenarios. The disclosed embodiments, modules, and functional operations described herein can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed herein and their structural equivalents, or in a combination of one or more of them. The disclosed embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by or for controlling the operation of a data processing apparatus. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition producing a machine-readable propagated signal, or one or more combinations thereof. The term "data processing apparatus" encompasses all apparatus, devices, and machines for processing data, including, by way of example, a programmable processor, a computer, or multiple processors or computers. An apparatus may include, in addition to hardware, code that creates an execution environment for the computer program, such as code constituting a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The propagated signal may be an artificially generated signal, for example a machine-generated electrical, optical, or electromagnetic signal, generated so as to encode information for transmission to a suitable receiver device.

[0111] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a single file dedicated to the program, in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), or in multiple collaborative files (e.g., files that store one or more modules, subprograms, or portions of code). A computer program can be deployed to run on one computer, or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0112] The processes and logic flows described herein may be implemented by one or more programmable processors running on one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be implemented by, and apparatus may be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0113] Processors suitable for executing computer programs include, by way of example, both general purpose and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory, or both. The essential elements of a computer are a processor for carrying out instructions, and one or more memory devices for storing instructions and data. Generally, a computer will include one or more mass storage devices, such as magnetic, magneto-optical, or optical disks, for storing data, or be operatively coupled to receive data from or transfer data to them, or both. However, a computer does not require such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, by way of example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices, magnetic disks, such as internal hard disks or removable disks, magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0114] Although this patent document contains many details, these should not be construed as limitations on the scope of any invention or what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of a particular invention. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in a combination and may even be initially claimed as such, one or more features from a claimed combination may, in some cases, be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

[0115] Similarly, although operations are depicted in the figures in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or in sequential order, or that all of the illustrated operations be performed in order to achieve desirable results.Furthermore, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[0116] Only some implementations and examples have been described; other implementations, enhancements, and variations can be made based on what is described and illustrated in this patent document.

Claims

1. 1. A wireless communication method, the method comprising: A network side function operating in a wireless network receives a request for allocation information associated with network slice information from an Access and Mobility Function (AMF) in the wireless network, in which a network service is provided as one or more network slices; the network side function transmitting, in response to the request, the allocation information relating to the network slice information; The network side function receives an over-allocation notification from the AMF in response to a determination by the AMF that an allocation corresponding to the allocation information has been exceeded; adjusting the allocation information in response to the over-allocation notification; A method comprising:

2. 2. The method of claim 1, wherein the allocation information comprises a limit on a number of wireless devices that are allowed to register in a network slice identified by the network slice information.

3. 2. The method of claim 1, wherein the allocation information comprises a limit on a number of protocol data unit (PDU) sessions that are operational within a network slice identified by the network slice information.

4. 2. The method of claim 1, wherein the allocation information comprises a maximum data rate supported by a network slice identified by the network slice information.

5. 1. A wireless communication method, the method comprising: An Access and Mobility Function (AMF) sending a request for slice allocation information to a Slice Allocation Management (SQM) function; The AMF receives the slice allocation information from the SQM function, the slice allocation information being determined by the SQM function, the slice allocation information including at least one of a limit on a number of wireless devices allowed to be registered in a network slice identified by the network slice information, a limit on a number of Protocol Data Unit (PDU) sessions that are operable in the network slice identified by the network slice information, or a maximum value of a data rate supported by the network slice identified by the network slice information; The AMF performs tracking of at least one of the number of the wireless devices, the number of the PDU sessions, or the data rate; In response to an overflow determination that an allocation corresponding to at least one of the number of the wireless devices, the number of the PDU sessions, or the data rate has been exceeded, the AMF transmits an over-allocation notification to the SQM function. A method comprising:

6. The method according to claim 5, further comprising: receiving, in the AMF, information that the network slice is subject to allocation management.

7. The method of claim 5 , wherein the request includes one or more of the network slice information, the capability of the AMF, or an identity of the AMF.

8. The method comprises: The AMF stores the slice allocation information regarding a slice to which a network service is provided; The AMF enforces the slice allocation information. The method of claim 5 further comprising:

9. The method of claim 8, further comprising: the AMF transmitting, in response to the overflow determination, a back-off timer value to a user equipment (UE) according to the network slice information.

10. 1. A wireless communication method, the method comprising: sending a request from an Access and Mobility Function (AMF) to a Visited Slice Allocation Management (SQM) function for slice allocation information related to a home network to be forwarded to a home SQM; receiving, in the AMF, from the visited SQM function, a response to the request including the slice allocation information; The AMF enforces the slice allocation information for the home network according to network slice information, the slice allocation information including at least one of a limit on a number of wireless devices allowed to be registered in the network slice identified by the network slice information, a limit on a number of Protocol Data Unit (PDU) sessions that can operate in the network slice identified by the network slice information, or a maximum value of a data rate supported by the network slice identified by the network slice information, and tracking of at least one of the number of wireless devices, the number of PDU sessions, or the data rate is performed by the AMF. A method comprising:

11. The method according to claim 10, further comprising: receiving, in the AMF, information that the home network is subject to allocation management according to the network slice information.

12. The method according to any one of claims 2, 5 to 11, wherein the limit on the number of wireless devices comprises a maximum number of user equipment.

Images