Authorization method for network slice

Abstract

Systems and methods for wireless communication are disclosed herein. In one embodiment, the systems and methods are configured to receive, by a mobility management function (AMF) from a network function (NF), slice information including at least one of a quality of service (QoS) profile of a slice or a service area of the slice. The AMF can determine that a wireless communication device is authorized to access the slice based on the service area of the slice. The AMF can send, to a radio access network, the QoS profile including a slice-specific aggregate maximum bit rate (AMBR) specific to the slice.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, and more specifically to systems and methods for licensing network slicing. Background Technology

[0002] There are no existing systems or methods for retrieving slice information, such as slice-specific aggregated maximum bit rate (AMBR) and service area of ​​a slice. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues presented in the prior art, and to provide additional features that will become apparent when viewed in conjunction with the accompanying drawings and the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and are not intended to be limiting, and that various modifications may be apparent to those skilled in the art who read this disclosure while remaining within the scope of this disclosure.

[0004] In some embodiments, a wireless communication method includes: receiving slice information from a network function (NF) by a mobility management function (AMF), the slice information including at least one of a quality of service (QoS) profile for the slice or a service area of ​​the slice; and at least one of the following operations: determining by the AMF that a wireless communication device is authorized to access the slice based on the service area of ​​the slice, or sending by the AMF a QoS profile including a slice-specific AMBR specific to the slice to a radio access network. The radio access network performs rate control for the slice of the wireless communication device based on the slice-specific AMBR.

[0005] In some embodiments, a wireless communication method includes: receiving a QoS profile from an AMF for the wireless access network, the QoS profile including a slice-specific AMBR specific to the slice, and performing rate control for the slice of the wireless communication device based on the slice-specific AMBR.

[0006] The foregoing and other aspects, and their embodiments, are described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0007] Various exemplary embodiments of this solution are described in detail below with reference to the accompanying drawings. The drawings are provided for illustrative purposes only and depict only exemplary embodiments of this solution to aid the reader's understanding. Therefore, the drawings should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0008] Figure 1 This is a block diagram illustrating an example network system architecture according to an embodiment of the present disclosure.

[0009] Figure 2 This is a block diagram illustrating an example slice deployment according to an embodiment of the present disclosure.

[0010] Figure 3 This is a signaling diagram illustrating an example process for retrieving slice information from an Authentication, Authorization, and Accounting (AAA-S) server according to an embodiment of the present disclosure.

[0011] Figure 4 This is a signaling diagram illustrating an example process for retrieving slice information from Unified Data Management (UDM) according to an embodiment of the present disclosure.

[0012] Figure 5 This is a signaling diagram illustrating an example process for retrieving slice information from a Policy Control Function (PCF) according to an embodiment of the present disclosure.

[0013] Figure 6 This is a flowchart illustrating an example method for retrieving and using slice information from an NF according to an embodiment of the present disclosure.

[0014] Figure 7A A block diagram of an example base station according to some embodiments of the present disclosure is shown.

[0015] Figure 7B A block diagram of an example user equipment (UE) according to some embodiments of the present disclosure is shown. Detailed Implementation

[0016] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to manufacture and use this solution. It will be apparent to those skilled in the art that various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example method. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art should understand that the methods and techniques disclosed herein present various steps or behaviors in a sample order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0017] In some wireless communication networks, the Maximum Stream Bit Rate (MBR) is a QoS parameter used for rate control. For example, the AMBR (which is a type of MBR) is used to control the rate of non-guaranteed stream bit rate (non-GBR) streams. Based on aggregation granularity, the AMBR can be Protocol Data Unit (PDU) session-AMBR, User Equipment (UE)-AMBR, etc. The PDU session-AMBR controls the aggregated maximum bit rate for a PDU session. The UE-AMBR controls the aggregated maximum bit rate for all active PDU sessions for a given UE. Next-generation radio access networks (NR) can implement both UE-AMBR and PDU-AMBR.

[0018] In some wireless communication networks (e.g., 5G System (5GS) networks), operators can use network slicing to deploy multiple network slices to provide the same functionality to different groups of UEs. A network slice is a network architecture with software or virtual network capabilities that divides the physical network architecture into software / virtual components. A slice refers to a portion of the physical network infrastructure provided for a specific scenario or customer use case (e.g., according to a Service Level Agreement (SLA)). Each slice includes resources (dedicated to that slice or shared among multiple slices), such as, but not limited to, network bandwidth, processing power, storage, etc. When a UE accesses the network, it can access multiple slices simultaneously using network slices. Network slices may vary for various supported functions and different network function optimizations. Operators have specified requirements for implementing slice-specific AMBRs. A slice-specific AMBR (or slice-AMBR) is an AMBR that limits the aggregate bit rate of all non-GBR radio bearers for a given slice. The retrieval and execution of slice-specific AMBRs have not yet been specified. Furthermore, traditionally, slice authorization does not consider the UE's current location. In some deployments (such as, but not limited to, those deployments for specific slices deployed for enterprises), access to these slices is not subject to any geographical restrictions.

[0019] Figure 1 This is a block diagram illustrating an example network system architecture 100 according to an embodiment of the present disclosure. Reference Figure 1 The example of network system architecture 100 is the 5GS architecture. Network system architecture 100 includes various NFs such as, but not limited to, AMF 102, Session Management Function (SMF) 106, User Plane Function (UPF) 108, UDM 112, PCF 114, Application Function (AF) 116, etc.

[0020] AMF 102 includes functionalities such as, but not limited to, UE mobility management, reachability management, and connectivity management. For example, AMF 102 is where the Communication Protocol (CP) interface N2 and the Non-Access Stratum (NAS) CP interface N1 of the Radio Access Network (RAN) are defined. CP interface N2 is used for the communication link between the RAN (e.g., 5G Access Network (AN) 104) and AMF 102. NAS CP interface N1 is used for the communication link between UE 101 (e.g., a wireless communication device) and AMF 102. AMF 102 also performs NAS encryption and integrity protection. UE 101 is connected to 5G-AN 104.

[0021] In addition, AMF 102 assigns Session Management (SM) NAS to the appropriate SMF (e.g., SMF 106) via CP interface N11. SMF 106 includes functions such as, but not limited to, UE Internet Protocol (IP) address allocation and management, user plane (UP) function selection and control, PDU connection management, etc.

[0022] In some implementations, UPF 108 serves as an anchor point for intra-RAT or inter-RAT mobility. UPF 108 can also be an external PDU session point interconnected with a data network 110 connected to UPF 108. At this point, UPF 108 is connected to SMF 106 via CP interface N4. UPF 108 can route and forward packets as indicated by SMF 106. When UE 101 is in idle mode, UPF 108 can buffer downlink (DL) data. UPF 108 is connected to 5G-AN 104.

[0023] UDM 112 can store subscription profiles of UEs (including but not limited to UE 101). UDM 112 is connected to AMF 102 via CP interface N8. UDM 112 is connected to SMF 106 via CP interface N10.

[0024] PCF 114 can generate policies (e.g., policing and enforcement elements) for managing network behavior based on subscriptions and instructions from AF 116. PCF 114 is connected to AF 116 via a suitable communication link. PCF 114 can also provide policy rules to CP functions (e.g., AMF 102 and SMF 106), which are configured to enforce these policy rules. For example, PCF 114 can provide policy rules to SMF 106 via CP interface N7.

[0025] Each of the communication links, CP interfaces, connections, etc. shown as lines between two of the elements 101-116 can be any suitable wired or wireless connection.

[0026] Figure 2 This is a block diagram illustrating an example slice deployment 200 according to an embodiment of the present disclosure. References Figure 1-2 Slice deployment 200 can be implemented for network system architecture 100. UE 101 connects to NR 202, which in turn connects to AMF 102. NR 202 is used to refer to the communication network formed by base stations (e.g., gNodeB (gNB) etc.). NR 202 corresponds to... Figure 1The NAS CP interface N1 is shown. SMF 106 may include multiple SMFs such as, but not limited to, SMFs 212, 213, 222, 232, 233, and 234. In the slice deployment 200 shown, SMFs 212, 213, 222, 232, 233, and 234 are deployed in different slices. For example, SMFs 212 and 213 are deployed in slice 201. SMF 222 is deployed in slice 202. SMFs 232, 233, and 234 are deployed in slice 203. UE 101 can access different slices 201, 202, and 203 simultaneously. Each of slices 201, 202, and 203 corresponds to a set of resources such as, but not limited to, network bandwidth, processing power, storage, etc. UE 101 can connect to different SMFs (e.g., SMFs 232, 233, and 234) in the same slice (e.g., slice 203). Different SMFs 232, 233, and 234 can be connected to different data networks (DNs) identified and distinguished by different data network names (DNNs), such that each of the different DNs is identified by one of the different DNNs.

[0027] Traditionally, for UE 101 to access slices (e.g., slices 201, 202, and 203), further authentication and authorization by AAA-S may be required. AAA-S can be hosted by the Home Public Terrestrial Mobile Network (H-PLMN) operator or a third party with a business relationship with the H-PLMN operator. Traditionally, during the registration process, based on the authentication and authorization results from AAA-S, AMF 102 can determine whether to add a single Network Slice Selection Assistance Information (S-NSSAI) to the currently permitted NSSAI. However, traditionally, such operations have only been used for authentication and authorization.

[0028] This disclosure relates to reusing and extending current procedures and messaging within them to provide additional information to AMF 102. Current procedures can be public procedures such as the authentication and authorization procedures mentioned above, the contract acquisition procedures, the policy association creation procedures, or other suitable procedures. In this regard, Figure 3 This is a signaling diagram illustrating an example process 300 for retrieving slice information from AAA-S 306 according to an embodiment of this disclosure. (See reference...) Figure 1-3 The slice information provided to AMF 102 includes at least QoS profile information for each specific slice (e.g., including slice-AMBR) and service area (e.g., restricted area, limited area, etc.). Slice information is information exchanged (directly or indirectly) between AMF 102 and AAA-S 306, in addition to other signaling / messages exchanged in common processes.

[0029] Regarding QoS profile information, AMF 102 can retrieve QoS profile information from AAA-S 306. AMF 102 can send QoS profile information to NR 202 in response to UE 101 entering connected mode (e.g., UE 101 connecting to NR 202) or after UE 101 enters connected mode. In some examples, the QoS profile information includes at least the slice-AMBR (in addition to other information such as, but not limited to, UE-specific AMBR, PDU-specific AMBR, Guaranteed Stream Bit Rate (GBR) of GFBR flows, QoS Class Identifier (QCI), etc.). Based on the QoS profile information, in scenarios where UE 101 accesses multiple SMFs (e.g., SMFs 232, 233, and 234) in the same slice, NR 202 can perform rate control on the entire slice (e.g., slice 203). For example, NR 202 (including base stations such as, but not limited to, gNB) can perform slice-AMBR at the rates of multiple SMFs 232, 233, and 234 of the same slice 203 accessed by UE101.

[0030] Regarding the service area of ​​a specific slice, which applies to UE 101 in AMF 102. Figure 3 The process shown can be used for more granular access control.

[0031] General Reference Figure 3 In the first example, AMF 102 may send the current location of UE 101 (such as, but not limited to, Current Tracking Area Identifier (TAI), NR Node Identifier (ID), Cell ID, etc.) to AAA-S 306. Upon receiving the current location of UE 101, AAA-S 306 determines whether UE 101 is permitted to access a slice (e.g., slice 203) at that current location. In response to determining that UE 101 is permitted (assuming other authentication and authorization are successful), AAA-S 306 may return the service area of ​​the slice (e.g., slice 203) to AMF 102. In some examples, the additional authentication and authorization includes at least AAA-S 306 authenticating UE 101 using the EAP procedure based on the EAP ID, and in response to determining that EAP authentication failed, disallowing UE 101 from accessing the slice. In response to determining that UE 101 is not permitted, AAA-S 306 may reject the request for that slice and indicate an appropriate reason / justification.

[0032] In the second example, in response to successful authentication and authorization, or during an Extensible Authentication Protocol (EAP) message exchange, AAA-S 306 can provide the service area of ​​a slice (e.g., slice 203) to AMF 102, regardless of the current location of UE 101. In this example, in response to AMF 102 receiving the service area of ​​the slice, AMF 102 checks whether the current location of UE 101 is within that service area. In response to determining that the current location of UE 101 is not within the service area, AMF 102 excludes the S-NSSAI of the slice from the allowed NSSAIs. On the other hand, in response to determining that the current location of UE 101 is within the service area, AMF 102 includes the S-NSSAI of the slice in the allowed NSSAIs.

[0033] At point 311, AMF 102 triggers slice-specific authentication and authorization as a public process. That is, AMF 102 can trigger the initiation of a slice-specific authentication and authorization process for S-NSSAI applications requiring slice-specific authentication and authorization. In some examples, AMF 102 can trigger the slice-specific authentication and authorization process based on any change to the contract information. In alternative examples, AAA-S 306 can trigger or otherwise instruct AMF 102 to trigger the slice-specific authentication and authorization process.

[0034] In some examples where network slice-specific authentication and authorization are triggered as a result of the registration process, AMF 102 can determine, based on UE context information stored in AMF 102, that UE 101 has already been authenticated after the registration process during the first access for some or all S-NSSAIs subject to network slice-specific authentication and authorization. Depending on the result of the previous run of network slice-specific authentication and authorization during the first access (e.g., success or failure), AMF 102 can determine, based on any network policy, to skip or omit network slice-specific authentication and authorization for some S-NSSAIs during the second access. That is, in response to determining that one or more S-NSSAIs have been successfully authenticated and authorized during the network slice-specific authentication and authorization for the first access, AMF 102 can determine to skip the network slice-specific authentication and authorization for one or more S-NSSAIs. This second access follows the first access.

[0035] In some examples where S-NSSAIs requiring network slice-specific authentication and authorization are included in the allowed NSSAIs for each access type, AMF 102 can select the access type for performing network slice-specific authentication and authorization procedures based on network policy.

[0036] Although the certification and authorization process is Figure 3 The example is used here, but other common procedures such as, but not limited to, the contract-acquisition procedure, the policy-association-creation procedure, or other suitable procedures can be used to exchange AMF 102 slice information.

[0037] At position 312, AMF 102 sends a message to UE 101 requesting the UE user ID (e.g., EAP ID, EAP authentication ID, etc.) for EAP authentication used for S-NSSAI. This message includes a request for the EAP ID (referred to as the EAP ID request) and the S-NSSAI. The S-NSSAI included in this message is the H-PLMN's S-NSSAI, not a locally mapped S-NSSAI value. This message is sent via NAS Mobility Management (MM) transmission.

[0038] At 313, UE 101 sends a response back to AMF 102 via a NAS MM transmission, wherein this NAS MM transmission message includes an EAP ID response containing the requested EAP ID for S-NSSAI. The NAS MM transmission message also includes the S-NSSAI received at 312.

[0039] At 314, AMF 102 sends a message to the Authentication Server Function (AUSF) 302 (e.g., via Nausf_Communication_EAPMessage_Transfer). This message includes an EAP ID response (containing the requested EAP ID for S-NSSAI), the AAA-S address of AAA-S 306, the General Public Subscription Identifier (GIPSI), and the S-NSSAI. In the first example where AMF 102 sends the current location of UE 101 to AAA-S 306, the current location of UE 101 can also be included in the message sent at 314. As mentioned above, the current location can be one or more of the current TA, NR node ID, or cell ID for UE 101. In the second example, where AAA-S 306 can provide the service area of ​​the slice to AMF 102 regardless of the current location of UE 101, the current location of UE 101 is not sent at 314.

[0040] At 315, in an implementation where AAA-P 304 is present, AUSF 302 forwards the message to the Authentication, Authorization, and Accounting Agent (AAA-P) 304 (e.g., because AAA-S 306 is a third party). AUSF 302 may invoke the Naaa_Communication_EAPmessageTransfer service to forward the message. The forwarded message includes an EAP ID response (which contains an EAP ID for S-NSSAI), the AAA-S address of AAA-S 306, GIPSI, and S-NSSAI. In a first example where AMF 102 sends the current location of UE 101 to AAA-S 306, the current location of UE 101 may also be included in the message forwarded at 315. In a second example where AAA-S 306 can provide the service area of ​​the slice to AMF 102 regardless of the current location of UE 101, the current location of UE 101 is not forwarded at 315.

[0041] At 316, AAA-P 304 associates the AAA-S address of AAA-S 306 with the S-NSSAI and forwards the EAP ID response (whose packet is for the EAP ID containing the S-NSSAI), GIPSI, and S-NSSAI to AAA-S 306 (using the AAA-S address of AAA-S 306). In the first example where AMF 102 sends the current location of UE 101 to AAA-S 306, the current location of UE 101 can also be included in the message forwarded at 316. In the second example where AAA-S 306 can provide the service area of ​​the slice to AMF 102 regardless of the current location of UE 101, the current location of UE 101 is not forwarded at 316. The EAP ID response can also be referred to as an EAP identification message. The current location of UE 101 (in the first example but not in the second example), the EAP ID response, GIPSI, and S-NSSAI can be sent to AAA-S 306 as part of the authentication and authorization process, where other aspects are subject to other types of authentication and authorization. In some examples, these other aspects include at least AAA-S 306 authenticating UE 101 using the EAP process based on the EAP ID, and disallowing UE 101 from accessing the slice in response to determining that EAP authentication has failed.

[0042] Alternatively, in an implementation where AAA-P 304 is absent (because AAA-S 306 belongs to the H-PLMN operator and not a third party), AUSF 302 can directly forward messages to AAA-S address of AAA-S 306 that include an EAP ID response (containing an EAP ID for S-NSSAI), GIPSI, and S-NSSAI in the authentication request. For the first example where AMF 102 sends the current location of UE 101 to AAA-S 306, the current location of UE 101 can also be included in the authentication request sent directly to AAA-S 306. For the second example where AAA-S 306 can provide the service area of ​​the slice to AMF 102 regardless of the current location of UE 101, the current location of UE 101 is not sent.

[0043] AAA-S 306 and UE 101 exchange EAP messages at points 317-324 for EAP authentication. One or more iterations of one or more of the blocks in 317-324 can be performed.

[0044] In the first example where AMF 102 sends the current location of UE 101 to AAA-S 306, in response to receiving the current location of UE 101 (e.g., at 316 or directly from AMF 302), AAA-S 306 can determine whether the current location of UE 101 is within the service area of ​​the slice. In response to determining that the current location of UE 101 is not within the service area of ​​the slice, the authentication request (e.g., received by AAA-S 306 at 316) is rejected. For example, AAA-S 306 can send an authentication response (including at least an EAP message, GPSI, and S-NSSAI) to AAA-P304 at 317. The EAP message includes at least one of an indication of rejection or an appropriate reason (e.g., authentication failure due to the current location of UE 101 being outside the service area of ​​the slice). In the example where AAA-P 304 exists, AAA-S 306 sends an authentication response to AAA-P 304 at 317, and AAA-P 304 forwards the EAP message, GPSI, and S-NSSAI to AUSF 302 via Nausf_Communication_EAPMessageTransfer at 318. Alternatively, in the scenario where AAA-P 304 does not exist, AAA-S 306 sends the authentication response directly to AUSF 302. At 319, AUSF 302 can forward the EAP message, GPSI, and S-NSSAI to AMF 102 via Namf_Communication_N1N2MessageTransfer. AMF 102 accordingly receives a rejection indication and appropriate reason (e.g., authentication failure due to UE 101's current location being outside the service area of ​​the slice) at 319, and 320-329 can be omitted if AAA-S 306 has determined that UE 101 is not within the service area of ​​the slice.

[0045] On the other hand, in response to determining in the first example that the current location of UE 101 is within the service area of ​​the slice, or in the second example regardless of the current location of UE 101, AAA-S 306 can provide the service area of ​​the slice to AMF 102, and AAA-S 306 can provide the service area at 317. For example, AAA-S 306 can send an authentication response (including at least an EAP message, GPSI, and S-NSSAI) to AAA-P 304 at 317. The EAP message includes at least an indication of authorization and service area. In the example where AAA-P 304 is present, at 317, AAA-S 306 sends an authentication response (including the service area) to AAA-P 304, and at 318, AAA-P 304 forwards the EAP message (including the service area), GPSI, and S-NSSAI to AMF 302 via Nausf_Communication_EAPMessageTransfer. Alternatively, in scenarios where AAA-P 304 is absent, AAA-S 306 directly sends an authentication response (including the service area) to AMF 302. At 319, AMF 302 can forward the EAP message (including the service area), GPSI, and S-NSSAI to AMF 102 via Namf_Communication_N1N2MessageTranfser. AMF 102 then receives the authorization and service area instructions accordingly.

[0046] Upon receiving a service area for a slice identified by an S-NSSAI, AMF 102 determines whether to allow UE 101 to access the slice based on the current UE location. If AMF 102 determines that UE 101's current location is not within the service area of ​​the slice, AMF 102 may suspend the authentication and authorization process for that slice, and steps 320-329 may be omitted. In scenarios where the authentication and authorization process is triggered by the allocation or update of an allowed S-NSSAI (e.g., during registration), the S-NSSAI for that slice is excluded from the allowed NSSAIs.

[0047] On the other hand, in response to AMF 102 determining that UE 101's current location is within the service area of ​​the slice, AMF 102 includes the slice's S-NSSAI in the allowed NSSAIs and continues to perform the slice authentication and authorization process 320-329. For example, at 320, AMF 102 sends the slice's EAP message and S-NSSAI to UE 101 via NAS MM transmission. At 321, AMF 102 receives the EAP message and S-NSSAI from UE 101 via NAS MM transmission. UE 101 performs the general EAP procedure and completes authentication based on the EAP ID and key.

[0048] At 322, AMF 102 sends messages to AUSF 302 (e.g., via Nausf_Communication_EAPMessage_Transfer). Such messages include EAP messages, AAA-S addresses for AAA-S 306, GIPSI, and S-NSSAI.

[0049] At 323, in an implementation where AAA-P 304 exists, AUSF 302 may invoke the Nausf_Communication_EAPmessageTransfer service to forward the EAP message, the AAA-S address of AAA-S 306, GIPSI, and S-NSSAI to AAA-P 304. At 324, AAA-P 304 associates the AAA-S address of AAA-S 306 with the S-NSSAI and sends an authentication request to AAA-S 306 (using the AAA-S address of AAA-S 306), the authentication request including the EAP message, GIPSI, and S-NSSAI. Alternatively, in a scenario where AAA-P 304 does not exist, AUSF 302 directly sends an authentication request to AAA-S 306, the authentication request including the EAP message, GIPSI, and S-NSSAI.

[0050] AAA-S 306 performs EAP authentication in response to the authentication request received at 324. At 325, AAA-S 306 sends an authentication response to AAA-P 304, which includes an EAP success / failure message, GPSI, and S-NSSAI. The EAP success / failure message indicates whether EAP authentication was successful or unsuccessful. At 326, AAA-P 304 forwards the EAP success / failure message, GPSI, and S-NSSAI to AUSF 302 via Nausf_Communication_EAPmessageTransfer. In scenarios where AAA-P 304 is not present, AAA-S 306 sends the EAP success / failure message, GPSI, and S-NSSAI directly to AUSF 302. At 327, AUSF 302 sends the EAP success / failure message, GPSI, and S-NSSAI to AMF 102 via Namf_Communication_N1N2messageTransfer.

[0051] In some examples, AAA-S 306 can provide a QoS profile to AMF 102 via AUSF 302. For example, in a scenario where AAA-P 304 is present, the QoS profile for that slice (including the slice-specific AMBR for that slice) can be sent to AAA-P 304 as part of the authentication response at 325. At 326, the QoS profile included in the Nausf_Communication_EAPmessageTransfer message can be relayed from AAA-P 304 to AUSF 302. Alternatively, in examples where AAA-P 304 is absent, AAA-S 306 can send the QoS profile directly to AUSF 302 along with the EAP success / failure message, GPSI, and S-NSSAI. At 327, AUSF 302 can forward the QoS profile to AMF 102 as part of the Namf_Communication_N1N2messageTransfer message. AMF102 determines the slice-specific AMBR included in the QoS profile based on any operator policy and sends the slice-specific AMBR to NR 202.

[0052] As an alternative to transmitting service area information at locations 317-319, the service area of ​​the slice can also be transmitted at locations 325-327. For example, even though UE 101's current location is within the service area of ​​the slice in the first example, or regardless of UE 101's current location in the second example, AAA-S 306 can provide the service area of ​​the slice to AMF 102 at location 325. In the example where AAA-P 304 is present, at location 325, AAA-S 306 sends the service area of ​​the slice as part of the authentication response to AAA-P 304, and at location 326, AAA-P 304 forwards the service area of ​​the slice as part of the authentication response to AMF 302 via Nausf_Communication_EAPMessageTransfer. Alternatively, in the scenario where AAA-P 304 is absent, AAA-S 306 directly sends the service area of ​​the slice to AMF 302. At 327, AMF 302 can forward the service area of ​​the slice to AMF 102 via Namf_Communication_N1N2MessageTransfer. AMF 102 accordingly receives the authorization and service area indication. In response to receiving the service area of ​​the slice identified by S-NSSAI at 327, AMF 102 can determine whether to allow UE 101 to access the slice based on the current UE location.

[0053] At 328, AMF 102 sends a NAS MM transport message to UE 101, including an EAP success / failure message. In response to determining that a new allowed NSSAI or a new rejected NSSAI needs to be delivered to UE 101, or in response to determining that AMF 102 needs to reassign, AMF 102 initiates a UE configuration update procedure at 329 (for each access type). In response to determining that network slice-specific authentication and authorization have failed for all S-NSSAIs among the allowed NSSAIs, AMF 102 performs a network-initiated deregistration procedure, and AMF 102 includes a list of rejected S-NSSAIs in an explicit deregistration request message, each with an appropriate rejection reason value indicating the corresponding rejection reason.

[0054] In some embodiments, AAA-S 306 may request the revocation of authorization for a network slice designated by S-NSSAI in a revocation authorization request message. During such a process, AAA-S 306 may update the slice's QoS profile and service area. The updated QoS profile (with an updated slice-specific AMBR) and the updated service area may be sent to AMF 102 in any suitable manner. AAA-S 306 may also request re-authentication and re-authorization for the slice designated by S-NSSAI in a re-authentication request message. In response to AMF 102 receiving the re-authentication request, AMF 102 triggers a slice-specific authentication and authorization process, such as, but not limited to, referencing... Figure 3 The process described. During the recertification and reauthorization process, AAA-S 306 may also include updated slice information at 317 or 325.

[0055] Figure 4 This illustrates an embodiment of the present disclosure for use from UDM 112 ( Figure 1 The signaling diagram for the example process of retrieving slice information is shown in section 400. (Reference) Figure 1-4 Process 400 involves AMF 102 retrieving slice information from UDM 112, such as, but not limited to, slice QoS profiles (including at least slice-specific AMBRs) and service areas.

[0056] At 410, UE 101 is in connected mode and connected to 102 to receive subscription data. During the registration and handover (HO) procedures, in response to determining that AMF 102 has no subscription data for UE 101, AMF 102 retrieves (e.g., using Nudm_SDM_Get) access and mobility subscription data, SMF selection subscription data, and the UE context from the SMF data from UDM 112 at 420 and 430. Slice information can be retrieved from UDM 112 simultaneously at 420 and 430 using Nudm_SDM_Get. That is, in response to determining that AMF 102 has no subscription data for UE 101, slice information can be requested at 420 and received at 430 along with access and mobility subscription data, SMF selection subscription data, and the UE context from the SMF data from UDM 112 (e.g., using Nudm_SDM_Get). In response to AMF 102 sending a Nudm_SDM_Get message to UDM 112, UDM 112 can obtain slice information from the Unified Data Repository (UDR) (not shown). UDM 112 retrieves slice information from the UDR by querying the UDR for slice information (e.g., using Nudr_DM_Query).

[0057] At 440, AMF 102 can determine the allowed NSSAIs and slice-specific AMBRs. For example, if a subscribed NSSAI is included as part of the subscription data in the Nudm_SDM_Get message at 430, then the slice QoS profile for each subscribed S-NSSAI is also included. AMF 102 can determine whether an active PDU session exists for the slice corresponding to each subscribed S-NSSAI. In response to determining the active PDU session for the slice, AMF 102 generates a slice-specific AMBR included in the subscribed slice QoS profile based on operator policies. In response to determining the slice-specific AMBR, AMF 102 sends the slice-specific AMBR to UE 450 via CP interface N1, or to NR 202 (e.g., 5G-AN 104) via CP interface N2.

[0058] If a subscribed S-NSSAI is included in the Nudm_SDM_Get message as part of the subscription data at point 430, the service area of ​​each subscribed S-NSSAI can also be included. AMF 102 can determine whether UE 101 is allowed to access the slice based on the current UE location. In response to determining that UE 101 is not allowed to access the slice because the current UE location is outside the service area, and the registration process or HO process is triggered by the allocation or update of an allowed S-NSSAI (e.g., during registration), the S-NSSAI corresponding to that slice is excluded from the allowed NSSAIs.

[0059] In some embodiments, in response to receiving a success response from UDM 112 indicating that the subscription data and slice information have been received by AMF 102 at 430, AMF 102 subscribes to UDM 112 (e.g., using Nudm_SDM_Subscribe) to be notified in response to any changes to the requested subscription data. UDM 112 subscribes to UDR (e.g., using Nudr_DM_Subscribe) to be notified in response to any modifications to the requested subscription data.

[0060] In response to the UDR determining that the subscription data has changed, the UDR pushes the updated subscription data to UDM 112 via Nudr_DM_Subscribe. UDM 112 then notifies AMF 102 via Nudm_SDM_Subscribe. In response to AMF 102 receiving the updated subscription data from UDM 112, AMF 102 checks the slice information received from UDM 112, where the slice information corresponds to the updated subscription data. In response to determining that the slice-specific AMBR has changed and that an active PDU session exists for that slice, AMF 102 updates the slice-specific AMBR for that slice to the updated slice-specific AMBR included in the updated subscription QoS profile, and then sends the updated slice-specific AMBR to NR202 (e.g., 5G-AN 104) via CP interface N2.

[0061] In some examples, in response to determining that the service area of ​​an S-NSSAI has changed and that such an S-NSSAI is included in the allowed NSSAIs, AMF 102 checks whether UE 101 is allowed access to the slice based on the current UE location. In response to determining that UE 101's current location is outside the service area of ​​the slice, AMF 102 can release all PDU sessions for that slice. AMF 102 can generate a new allowed NSSAI or a new registration area based on the slice's service area and UE 101's current UE location. When UE 101 moves within the registration area, UE 101 does not need to initiate mobility registration.

[0062] For example, to ensure that UE 101 can access certain slices, AMF 102 can generate a registration area for UE 101 that includes the service areas of those slices (e.g., if Tracking Area 1 (TA1) is not included in the service area of ​​slice A, then such TA1 is excluded from the registration). However, excluding TA1 from the registration is optional for registration area generation. The registration area can still include TA1. However, the S-NSSAI of slice A is not included in the allowed NSSAIs.

[0063] Figure 5 This illustrates an embodiment of the present disclosure for use from PCF 114 ( Figure 1 The signaling diagram for the example process of retrieving slice information (500). (Reference) Figure 1-5Process 500 involves AMF 102 retrieving slice information from PCF 114, such as, but not limited to, the slice's QoS profile (including at least the slice-specific AMBR) and service area. In other words, process 500 is similar to process 400, except that it retrieves slice information from PCF 114 instead of UDM 112. In roaming scenarios, AMF 102 retrieves slice information from V-PCF (the visited PCF), and V-PCF can retrieve slice information from H-PCF (the home PCF). In some examples, in response to V-PCF receiving slice information from H-PCF, V-PCF can modify the slice information, such as, but not limited to, adjusting the slice-specific AMBR based on the visited operator, adding / removing the service area of ​​the slice, etc. Because H-PLMN may not know the topology in the visited PLMN (V-PLMN), the service area of ​​the slice can be generated by V-PCF. Therefore, PCF 114 can represent both V-PCF and H-PCF.

[0064] At 510, UE 101 is in connected mode and connected to AMF 102 to receive subscription data. During the registration and HO procedures, AMF 102 can create or update its association with PCF 114.

[0065] In response to determining that AMF 102 has not yet obtained the access and mobility policy of UE 101, or in response to determining that the access and mobility policy in AMF 102 is no longer valid, AMF 102 requests PCF 114 to apply the operator policy for UE 101 from PCF 114.

[0066] For example, at 520, AMF 102 sends an Npcf_AMPolicyControl_Create message to PCF 114 to establish an access and mobility policy control association with PCF 114. At 530, PCF 114 responds to the Npcf_AMPolicyControl_Create service operation by providing AM-related policy information (e.g., service area restrictions) in the Npcf_AMPolicyControl_Create message. PCF 114 may also include slice information in the Npcf_AMPolicyControl_Create message at 530.

[0067] At 540, AMF 102 can determine the allowed NSSAIs and slice-specific AMBRs. For example, slice information includes the slice QoS profile for each subscribed S-NSSAI in the Npcf_AMPolicyControl_Create message received by AMF 102 at 530. AMF 102 can determine whether an active PDU session exists for the slice corresponding to each subscribed S-NSSAI. In response to determining that an active PDU session exists for that slice, AMF 102 sends the slice-specific AMBR to the NR 202 to be executed (e.g., 5G-AN 104).

[0068] Slice information includes the service area of ​​each subscribed S-NSSAI in the Npcf_AMPolicyControl_Create message received by AMF 102 at 530. AMF 102 can determine whether UE 101 is allowed to access the slice based on the current UE location. In response to determining that UE 101's current location is outside the service area of ​​the slice, and the process 500 is triggered by the allocation or update of an allowed S-NSSAI (e.g., during registration), the S-NSSAI corresponding to that slice is excluded from the allowed NSSAIs.

[0069] In some examples, AMF 102 may subscribe to PCF 114 to be notified in response to any changes to slice information. If slice information changes, and AMF 102 subscribes to PCF 114 to be notified of this change, PCF 114 pushes (sends) the updated slice information to AMF 102. The updated slice information may include an updated slice-specific AMBR for the given slice, wherein the updated slice-specific AMBR is included as part of the updated slice information. In response to AMF 102 receiving the updated slice information, AMF 102 determines to trigger a certain process. In response to determining that the slice-specific AMBR of the slice has changed, and that an active PDU session for that slice exists, AMF 102 may update the slice-specific AMBR included in the updated subscribed QoS profile and send the updated slice AMBR to NR 202 (5G-AN 104) to be executed.

[0070] In some examples, in response to determining that the service area of ​​an S-NSSAI has changed and that such an S-NSSAI is included in the allowed NSSAIs, AMF 102 checks whether UE 101 is allowed to access the slice based on the current UE location. In response to determining that UE 101's current location is outside the service area of ​​the slice, AMF 102 can release all PDU sessions for that slice. AMF 102 can generate a new allowed NSSAI or a new registration area based on the slice's service area and UE 101's current UE location.

[0071] Figure 6 This is a flowchart illustrating an example method 600 for retrieving and using slice information from an NF according to an embodiment of the present disclosure. Reference Figure 1-6 Method 600 is executed by AMF 102. NF can be AAA-S 306 (e.g.) Figure 3 As shown), UDM112 (as shown) Figure 4 (as shown), PCF 114 (as shown) Figure 5 (as shown) or the Network Slice Selection Function (NSSF).

[0072] At 610, AMF 102 receives slice information from NF. This slice information includes at least one of the slice's QoS profile or service area. In the example where NF is AAA-S 306, AMF 102 can receive this slice information using 317-319 and / or 325-327. In the example where NF is UDM 112, AMF 102 can receive this slice information using 430. In the example where NF is PCF 114, AMF 102 can receive this slice information using 530. In the example where NF is NSSF, in response to NSSF receiving a request from AMF 102, NSSF sends a response to AMF 102 including the allowed NSSAI for the applicable access type. NSSF may include slice information in the response. This slice information includes at least the QoS profile (containing a slice-specific AMBR) for each slice identified by S-NSSAI and the service area for each slice identified by S-NSSAI.

[0073] In some examples, AMF 102 can store slice information from the UE context in its storage device. During the registration and HO process (while AMF 102 remains unchanged), AMF 102 can check the slice information stored in the UE context to obtain the allowed NSSAI generation or update.

[0074] At 620, AMF 102 performs at least one of the following operations: determines that UE 101 is authorized to access the slice based on the service area of ​​the slice, or sends a QoS profile including an AMBR specific to that slice to RN 202 (e.g., 5G-AN104). RN 202 may perform slice-specific rate control for UE 101 based on the slice-specific AMBR. In the example where NF is AAA-S 306, UDM 112, or PCF 114, AMF 102, AMF 102 may determine that UE 101 is authorized to access the slice, or may send a QoS profile including an AMBR specific to that slice to RN 202. Figure 3-5 The described method sends a QoS profile, including the slice-specific AMBR, to RN202. In the example where NF is NSSF, in response to AMF 102 receiving a service area, AMF 102 can generate a registration area based on the allowed NSSAI and the corresponding service area. In response to AMF 102 receiving a QoS profile, AMF 102 can send a QoS profile, including the slice-specific AMBR, to RN 202.

[0075] In some embodiments, when a PDU session of a slice is established, or an uplink connection of an established PDU session in a slice is activated, AMF 102 can send the slice QoS profile of that slice to NR 202. NR 202 can use parameters of the QoS profile (e.g., a slice-specific AMBR) to control the bit rate of the non-GBR stream across the entire slice. AMF 102 locates the S-NSSAI of the slice that identifies the PDU session ID associated with the PDU session and confirms the slice-specific AMBR. In some examples, when the first PDU session of a slice is established, or the first uplink connection of an established PDU session in a slice is activated, AMF 102 may only include the slice-specific AMBR to NR 202.

[0076] To send an updated slice-specific AMBR, AMF 102 can initiate a CP interface N2 request to NR 202 including the updated slice-specific AMBR. When UE 101 moves to a new NR during an HO procedure, in response to AMF 102 receiving the updated slice-specific AMBR from NF (e.g., UDM 112 or PCF 114), AMF 102 can notify the new NR of the updated slice-specific AMBR. This notification (including the updated slice-specific AMBR) can be combined with any existing N2 messages sent from AMF 102 to the NF, for example, by utilizing existing N2 messages to deliver the notification via an Extended Information Element (IE). In scenarios where no suitable existing N2 message is available, AMF 102 can send the notification itself in a separate N2 message.

[0077] Figure 7A A block diagram of an example base station 702 according to some embodiments of the present disclosure is shown. Figure 7B A block diagram of an example UE 101 according to some embodiments of the present disclosure is shown. References Figure 1-7B Base station 702 and UE 101 may include components and elements configured to support known or conventional operating features that do not need to be described in detail herein. In one illustrative embodiment, as described above, base station 702 and UE 101 may be used to transmit (e.g., send and receive) data symbols in a wireless communication environment such as network system architecture 100 and slice deployment 200. For example, base station 702 may be a base station (e.g., gNodeB (gNB) etc.), a server, a node, or any suitable computing device for implementing NFs (e.g., AMF 102, SMF 106, UPF 108, UDM 112, PCF 114, AF116, etc.) and providing networks 104, 110, and 202.

[0078] Base station 702 includes a transceiver module 710, an antenna 712, a processor module 714, a memory module 716, and a network communication module 718. Modules 710, 712, 714, 716, and 718 are operably coupled to and interconnected with each other via a data communication bus 720. UE 101 includes a UE transceiver module 730, a UE antenna 732, a UE memory module 734, and a UE processor module 736. Modules 730, 732, 734, and 736 are operably coupled to and interconnected with each other via a data communication bus 740. Base station 702 communicates with UE 101 or another base station via a communication channel, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0079] As will be understood by those skilled in the art, base station 702 and UE 101 may also include, in addition to Figure 7A and Figure 7B Any number of modules other than those shown. The various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are generally described according to their functionality. Whether this functionality is implemented as hardware, firmware, or software depends on the specific application and design constraints imposed on the system as a whole. The embodiments described herein can be implemented in a suitable manner for each specific application, but any decision on implementation should not be construed as limiting the scope of this disclosure.

[0080] According to some embodiments, UE transceiver 730 includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 732. A duplex switch (not shown) may alternatively couple the RF transmitter or receiver to the antenna in a time-duplex manner. Similarly, according to some embodiments, transceiver 710 includes an RF transmitter and an RF receiver, each of which has circuitry coupled to an antenna 712 or an antenna of another base station. A duplex switch may alternatively couple the RF transmitter or receiver to the antenna 712 in a time-duplex manner. The operation of the two transceiver modules 710 and 730 can be coordinated in time such that receiver circuitry is coupled to antenna 732 so that transmissions are received via a wireless transmission link at the same time the transmitter is coupled to antenna 712. In some embodiments, there is tight time synchronization with a minimum guard time between changes in duplex direction.

[0081] UE transceiver 730 and transceiver 710 are configured to communicate via a wireless data communication link and cooperate with RF antenna arrangements 712 / 732 that are appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 730 and transceiver 710 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to the application of specific standards and related protocols. Rather, UE transceiver 730 and base transceiver 710 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0082] Transceiver 710 and transceivers of another base station (such as, but not limited to, transceiver 710) are configured to communicate via a wireless data communication link and cooperate with an RF antenna arrangement appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, transceiver 710 and the transceiver of the other base station are configured to support industry standards such as LTE and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to the application of specific standards and related protocols. Rather, transceiver 710 and the transceiver of the other base station may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0083] According to various embodiments, base station 702 may be a base station such as, but not limited to, an eNB, serving eNB, target eNB, femtocell, or picocell. Base station 702 may be an RN, a conventional station, a DeNB, a gNB, or an IAB anchor point. In some embodiments, UE 101 may be embodied in various types of user equipment such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 714 and 736 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, controller, microcontroller, state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0084] Furthermore, the methods or algorithms disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules 714 and 736 respectively, or in any practical combination thereof. Memory modules 716 and 734 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this respect, memory modules 716 and 734 can be coupled to processor modules 710 and 730 respectively, such that processor modules 710 and 730 can read information from and write information to memory modules 716 and 734 respectively. Memory modules 716 and 734 can also be integrated into their respective processor modules 710 and 730. In some embodiments, memory modules 716 and 734 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 710 and 730 respectively. Memory modules 716 and 734 may each include non-volatile memory for storing instructions to be executed by processor modules 710 and 730, respectively.

[0085] Network communication module 718 typically represents the hardware, software, firmware, processing logic, and / or other components of base station 702 that enable bidirectional communication between transceiver 710 and other network components and communication nodes communicating with base station 702. For example, network communication module 718 may be configured to support Internet or WiMAX traffic. In deployments, but not limited to, network communication module 718 provides an 802.3 Ethernet interface, enabling transceiver 710 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 718 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). In some embodiments where base station 702 is an IAB anchor point, network communication module 718 includes a fiber optic transmission connection configured to connect base station 702 to a core network. The terms “configured for,” “configured to,” and variations thereof used herein with respect to a particular operation or function refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform a particular operation or function.

[0086] While various embodiments of the present solution have been described above, it should be understood that they are presented merely by way of example and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations provided to enable those skilled in the art to understand the exemplary features and functionality of the present solution. However, those skilled in the art should understand that the present solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as will be understood by those skilled in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0087] It should also be understood that any reference to elements in this document using names such as “first”, “second”, etc., does not generally restrict the number or order of these elements. Rather, these names serve as a convenient means of distinguishing two or more elements or instances of elements. Therefore, references to first and second elements do not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0088] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0089] Those skilled in the art will also understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not lead to a departure from the scope of this disclosure.

[0090] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor), multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration for performing the functions described herein.

[0091] If implemented as software, these functions can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium capable of transferring computer programs or code from one place to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and is accessible to a computer.

[0092] In this application, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0093] Furthermore, in embodiments of this solution, memory or other memory, as well as communication components, may be used. It should be understood that, for clarity, the above description refers to embodiments of this solution with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without departing from this solution. For example, a function illustrated as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing said function and not strict indications of logical or physical structure or organization.

[0094] Various modifications to the embodiments described herein will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be given the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method, the method comprising: The Mobility Management Function (AMF) receives slice information of wireless communication devices from the Unified Data Management (UDM), the slice information including the slice-specific Aggregated Maximum Bit Rate (AMBR); and The AMF sends the slice information, including the slice-specific AMBR, to the radio access network, wherein, in response to receiving the slice information, the radio access network performs rate control for the slice of the wireless communication device based on the slice-specific AMBR.

2. The method according to claim 1, wherein The wireless access network is the next-generation wireless access network (NR). The NR is supported by multiple base stations; The AMF is implemented on a server with a processor and memory; and The wireless communication device accesses multiple Session Management Functions (SMFs) within the same slice.

3. The method according to claim 1, wherein, The wireless access network performs rate control on the slice by performing rate control on all active PDU sessions in the same slice based on the slice-specific AMBR, and the wireless communication device establishes at least one PDU session in the same slice.

4. The method according to claim 1, further comprising: The AMF receives updated contract data; The AMF determines that updating the slice information with the updated contract data includes updating the slice-specific AMBR; as well as The AMF sends the updated slice-specific AMBR to the radio access network.

5. A wireless communication device, comprising: At least one processor, said processor being configured to: The transceiver receives slice information of the wireless communication device from the Unified Data Management (UDM) system, the slice information including the slice-specific Aggregated Maximum Bit Rate (AMBR); and The transceiver transmits the slice information, including the slice-specific AMBR, to the radio access network, wherein, in response to receiving the slice information, the radio access network performs rate control for the slice of the wireless communication device based on the slice-specific AMBR.

6. The wireless communication device according to claim 5, wherein The wireless access network is the next-generation wireless access network (NR). The NR is supported by multiple base stations; The wireless communication device is a Mobility Management Function (AMF), which is implemented on a server having a processor and memory; and The wireless communication device accesses multiple Session Management Functions (SMFs) within the same slice.

7. The wireless communication device according to claim 5, wherein, The wireless access network performs rate control on the slice by performing rate control on all active PDU sessions in the same slice based on the slice-specific AMBR, and the wireless communication device establishes at least one PDU session in the same slice.

8. The wireless communication device according to claim 5, wherein, At least one processor is also configured to: Receive updated subscription data via transceiver; Determining to update the slice information with the updated contract data includes updating the slice-specific AMBR; and The updated slice-specific AMBR is sent to the wireless access network via the transceiver.

9. A wireless communication method, the method comprising: The Unified Data Management (UDM) sends slice information of wireless communication devices to the Mobility Management Function (AMF), and the slice information includes the slice-specific Aggregated Maximum Bit Rate (AMBR). and The AMF sends the slice information, including the slice-specific AMBR, to the radio access network, and in response to receiving the slice information, the radio access network performs rate control for the slice of the wireless communication device based on the slice-specific AMBR.

10. The method of claim 9, wherein The wireless access network is the next-generation wireless access network (NR). The NR is supported by multiple base stations; The AMF is implemented on a server with a processor and memory; and The wireless communication device accesses multiple Session Management Functions (SMFs) within the same slice.

11. The method according to claim 9, wherein, The wireless access network performs rate control on the slice by performing rate control on all active PDU sessions in the same slice based on the slice-specific AMBR, and the wireless communication device establishes at least one PDU session in the same slice.

12. The method of claim 9, wherein the AMF is configured to: Receive updated contract data; Determining to update the slice information with the updated contract data includes updating the slice-specific AMBR; and The updated slice-specific AMBR is sent to the wireless access network.

13. A wireless communication device, comprising: At least one processor, said processor being configured to: This enables the Unified Data Management (UDM) to transmit slice information of wireless communication devices to the Mobility Management Function (AMF) via a transmitter. The slice information includes the slice-specific Aggregated Maximum Bit Rate (AMBR). and The AMF sends the slice information, including the slice-specific AMBR, to the radio access network, and in response to receiving the slice information, the radio access network performs rate control for the slice of the wireless communication device based on the slice-specific AMBR.

14. The wireless communication device according to claim 13, wherein The wireless access network is the next-generation wireless access network (NR). The NR is supported by multiple base stations; The AMF is implemented on a server with a processor and memory; and The wireless communication device accesses multiple Session Management Functions (SMFs) within the same slice.

15. The wireless communication device according to claim 13, wherein, The wireless access network performs rate control on the slice by performing rate control on all active PDU sessions in the same slice based on the slice-specific AMBR, and the wireless communication device establishes at least one PDU session in the same slice.

16. The wireless communication device according to claim 13, wherein the wireless communication device is configured to: Receive updated contract data; Determining to update the slice information with the updated contract data includes updating the slice-specific AMBR; and The updated slice-specific AMBR is sent to the wireless access network.

17. A computer-readable medium having code stored thereon, said code, when executed by a processor, capable of implementing the method according to any one of claims 1 to 4.

18. A computer-readable medium having code stored thereon, said code, when executed by a processor, capable of implementing the method according to any one of claims 9 to 12.

Images