Secure Access Control in Communication Systems
By introducing additional information into the OAuth access token, the authorization process is enhanced, and the problem of OAuth access authorization in 5G communication systems is solved, and access control at the resource level and group level is realized, improving the security of data access.
Patent Information
- Application Number
- CN202080043695.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-06-15
- Filing Date
- 2020-06-09
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-06-09
AI Technical Summary
In the existing 5G communication system, OAuth access authorization is only performed at the service level, and access authorization at the resource level and group level cannot be effectively performed, making it difficult to guarantee data access security.
By introducing additional information into the OAuth access token, the authorization process is enhanced, allowing the authorization server to identify resource level and group level access rights in the access token, ensuring that service consumers are authorized to access specific resources or network function groups.
It realizes not only authorization at the service level, but also access control at the resource level and group level in 5G systems, enhancing the security and management capabilities of data access.
Smart Images

Figure CN113994727B_ABST
Abstract
Description
Technical Field
[0001] The field of the present disclosure relates generally to communication systems and, more particularly, but not exclusively, to secure access control within such systems. Background Art
[0002] This section introduces aspects that may help to better understand the present invention. Therefore, the statements in this section should be read in this light and should not be understood as an admission of what is included in the prior art or what is not included in the prior art.
[0003] Fourth generation (4G) wireless mobile telecommunication technology, also known as Long Term Evolution (LTE) technology, is designed to provide high capacity mobile multimedia with high data rates particularly for human interaction. The next or fifth generation (5G) technology is intended not only for human interaction but also for machine type communications in so-called Internet of Things (IoT) networks.
[0004] Designed to enable massive IoT services (e.g., large numbers of devices with limited capacity) and mission-critical IoT services (e.g., requiring high reliability), 5G networks support improvements to traditional mobile communications services in the form of enhanced mobile broadband (eMBB) services, which provide improved wireless Internet access to mobile devices.
[0005] In an example communication system, a user equipment such as a mobile terminal (user) (5G UE in a 5G network or, more broadly, UE) communicates with a base station or an access point of the access network (referred to as 5G AN in a 5G network) over an air interface. Illustratively, the access point (e.g., gNB or N3IWF or TNGF or W-AGF, depending on the type of 5G access network: supporting NR radio defined by 3GPP, supporting untrusted non-3GPP access to 5GC, supporting trusted non-3GPP access to 5GC (5G Core) or supporting wired access to 5GC) is part of the access network of the communication system. For example, in a 5G network, the document entitled "Technical Specification Group Services and System Aspects; System Architecture of 5G Systems"
[0006] The 5G Technical Specification (TS) 23.501, V16.0.2 of (Technical Specification Group Services and System Aspects; System Architecture for the 5G System) describes an access network referred to as 5GAN, the disclosure of which is incorporated herein by reference in its entirety. Typically, an access point (e.g., gNB or N3IWF or TNGF or W-AGF, depending on the type of 5G access network) provides a UE with access to a core network (CN or 5GC), which then provides the UE with access to other UEs and / or data networks such as packet data networks (e.g., the Internet).
[0007] TS 23.501 goes on to define the 5G Service-Based Architecture (SBA), which models services as network functions (NFs) that communicate with each other using representational state transfer application programming interfaces (Restful APIs).
[0008] In addition, the disclosure of 5G Technical Specification (TS) 33.501, V15.4.0, entitled "Technical Specification Group Services and System Aspects; Security Architecture and Procedures for the 5G System", which further describes security management details related to 5G networks, is incorporated herein by reference in its entirety.
[0009] Access to network entities is an important security management consideration in any communication system. However, securing access in certain situations can present challenges. Summary of the invention
[0010] The illustrative embodiments provide improved techniques for secure access control in communication systems.
[0011] For example, in an illustrative embodiment according to authorization server functionality, a method includes: receiving a request from a service consumer in a communication system for access to a service type and one or more resources associated with the service type. The method determines whether the service consumer is authorized to access the service type and one or more resources associated with the service type. The method generates an access token that identifies one or more service producers for the service type and one or more resources associated with the service type that the service consumer is authorized to access, and sends the access token to the service consumer. The service consumer can then use the access token to access the one or more services and the one or more resources.
[0012] In another illustrative embodiment according to authorization server functionality, a method includes: receiving a request for access to a service type from a service consumer in a communication system. The method determines whether the service consumer is authorized to access the service type and one or more network function groups associated with the service type. The method generates an access token, the access token identifying one or more service producers for the service type that the service consumer is authorized to access or is not authorized to access and one or more network function groups associated with the service type, and the method sends the access token to the service consumer. The service consumer can then use the access token to access the one or more services.
[0013] In an illustrative embodiment, in a 5G system the service consumer is a network function (NF) and the authorization server function is a network repository function (NRF).
[0014] Further illustrative embodiments are provided in the form of a non-transitory computer-readable storage medium having executable program code contained therein, which, when executed by a processor, causes the processor to perform the above steps. Still further illustrative embodiments include an apparatus having a processor and a memory configured to perform the above steps. In addition, methods, non-transitory computer-readable storage media, and apparatus from the perspective of a service consumer are provided in other embodiments.
[0015] Advantageously, the access authorization levels provided by the illustrative embodiments not only allow for authorization at the service level, but also perform access authorization at the resource level, as well as authorization at the group level.
[0016] These and other features and advantages of the embodiments described herein will become more apparent from the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1A communication system is illustrated with which one or more illustrative embodiments may be implemented.
[0018] Figure 2 A processing architecture of network entities involved in secure access control in a communication system according to an illustrative embodiment is shown.
[0019] Figure 3 A data storage architecture is illustrated with which one or more illustrative embodiments may be implemented.
[0020] Figure 4A A message flow of a secure allowed resource access control method in a communication system according to an illustrative embodiment is illustrated.
[0021] Figure 4B A message flow of a secure allowed group access control method in a communication system according to another illustrative embodiment is illustrated.
[0022] Figure 5 An illustration of a table of access token request types in accordance with an illustrative embodiment.
[0023] Figure 6 A table of access token claim types is shown in accordance with an illustrative embodiment.
[0024] Figure 7 A secure allowed resource access control method in a communication system according to an illustrative embodiment is illustrated.
[0025] Figure 8 A secure allowed group access control method in a communication system according to an illustrative embodiment is illustrated. DETAILED DESCRIPTION
[0026] Embodiments will be described herein in conjunction with example communication systems and associated technologies for providing secure access control of network entities in communication systems. However, it should be understood that the scope of the claims is not limited to the specific type of communication systems and / or processes disclosed. Alternative processes and operations may be used to implement embodiments in a variety of other types of communication systems. For example, although described in the context of a wireless cellular system utilizing 3GPP system elements such as 3GPP Next Generation Systems (5G), the disclosed embodiments may be applicable to various other types of communication systems in a straightforward manner.
[0027] According to the illustrative embodiments implemented in the 5G communication system environment, one or more 3GPP technical specifications (TS) and technical reports (TR) provide further explanations of the interacting user equipment and network elements / functions and / or operations using one or more illustrative embodiments (e.g., 3GPP TS 23.501 and 3GPP TS33.501 mentioned above). Other 3GPP TS / TR documents provide other routine details that will be appreciated by those of ordinary skill in the art. For example, 3GPP TS 23.502, V16.0.2, entitled "Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2", and 3GPP TS 29.510, V15.3.0, entitled "Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services", the disclosures of which are incorporated herein by reference in their entirety, will be referenced below. However, while the illustrative embodiments are well suited for implementation associated with the above-mentioned 5G-related 3GPP standards, alternative embodiments are not limited to any particular standard.
[0028] In addition, the illustrative embodiments will be explained here in the context of the Open Systems Interconnection model (OSI model), which is a model that conceptually characterizes the communication functions of a communication system such as, for example, a 5G network. The OSI model is generally conceptualized as a layered stack in which a given layer serves the upper layers and is served by the lower layers. Typically, the OSI model includes seven layers, with the top layer of the stack being the application layer (layer 7), followed by the presentation layer (layer 6), the session layer (layer 5), the transport layer (layer 4), the network layer (layer 3), the data link layer (layer 2), and the physical layer (layer 1). Those of ordinary skill in the art will understand the functions and interactions of the various layers, and therefore, further details of each layer will not be described here. However, it should be understood that while the illustrative embodiments are well suited to implementations utilizing the OSI model, alternative embodiments are not limited to any particular communication function model.
[0029] The illustrative embodiments relate to key management associated with a service-based architecture (SBA) for a 5G network. Figure 1 and Figure 2 A general description of the main components of a 5G network is described in the background.
[0030] Figure 1 1 shows a communication system 100 in which an illustrative embodiment is implemented. It should be understood that the elements shown in the communication system 100 are intended to represent the main functions provided within the system, such as UE access functions, mobility management functions, authentication functions, serving gateway functions, etc. Figure 1 The blocks shown in the figure refer to specific elements in the 5G network that provide these main functions. However, in other embodiments, other network elements may be used to implement some or all of the main functions represented. In addition, it should be understood that not all functions of the 5G network are depicted in the figure. Figure 1 Rather, the functions are shown to facilitate the explanation of the illustrative embodiments. Subsequent figures may depict some additional elements / functionality.
[0031] Thus, as shown, the communication system 100 includes a user equipment (UE) 102, which communicates with an access point 104 (gNB or N3IWF or TNGF or W-AGF, depending on the type of 5G access network) via an air interface 103. In some embodiments, UE 102 is a mobile station, and such a mobile station may include, for example, a mobile phone, a computer, or any other type of communication device. Therefore, the term "user equipment" used herein is intended to be interpreted broadly to cover various different types of mobile stations, user stations, or more generally, communication devices (including examples of combinations of data cards inserted into laptops or other devices such as smartphones or other cellular devices). In one or more illustrative embodiments, the user equipment refers to an Internet of Things device. Such communication devices are also intended to include devices commonly referred to as access terminals. In other embodiments, the UE may be hosted by a residential gateway connected to the 5G core network via wired access.
[0032] In one embodiment, UE 102 consists of a Universal Integrated Circuit Card (UICC) part and a Mobile Equipment (ME) part. UICC is the user-related UE part, which contains at least one Universal User Identity Module (USIM) and appropriate application software. USIM securely stores permanent subscription identifiers and their associated keys for identifying and authenticating users accessing the network. ME is the user-independent UE part, which contains terminal equipment (TE) functions and various mobile terminal (MT) functions.
[0033] Note that in one example, the permanent subscription identifier is the International Mobile Subscriber Identity (IMSI) of the UE. In one embodiment, the IMSI is a fixed 15-digit length and consists of a 3-digit Mobile Country Code (MCC), a 3-digit Mobile Network Code (MNC), and a 9-digit Mobile Station Identification Number (MSIN). In 5G communication systems, the IMSI is called a Subscription Permanent Identifier (SUPI). In the case where the IMSI is used as the SUPI, the MSIN provides the user identity. Therefore, it is usually only necessary to encrypt the MSIN part of the IMSI. The MNC part and the MCC part of the IMSI provide routing information, which the service network uses to route to the correct home network. When the MSIN of the SUPI is encrypted, it is called a Subscription Hidden Identifier (SUCI).
[0034] Illustratively, access point 104 is part of an access network of communication system 100. Such an access network includes, for example, a 5G system having multiple base stations and one or more associated radio network control functions. In some embodiments, the base stations and the radio network control functions are logically separate entities, but in some embodiments, they are implemented in the same physical network element (e.g., a base station router or a cellular access point).
[0035] The access point 104 in this illustrative embodiment is operably coupled to a mobility management function 106. In a 5G network, the mobility management function is implemented by an access and mobility management function (AMF). In some embodiments, a security anchor function (SEAF) is also implemented by the AMF, which connects the UE to the mobility management function. As used herein, a mobility management function is an element or function (i.e., entity) in the core network (CN) portion of a communication system that manages or otherwise participates (through the access point 104) in network operations such as access and mobility operations (including authentication / authorization) of the UE. The AMF is also more generally referred to herein as an access and mobility management entity.
[0036] In this illustrative embodiment, the AMF 106 is operably coupled to subscriber functions, such as one or more functions residing in the subscriber's home network or elsewhere. Some of these functions include a unified data management (UDM) function and an authentication server function (AUSF). The AUSF and UDM (individually or collectively) are also more generally referred to as authentication entities in this document. The UDM supports an authentication credential repository and processing function (ARPF) that typically stores long-term security credentials used in authentication. In addition, user functions include, but are not limited to, a network slice selection function (NSSF), a network exposure function (NEF), a network storage function (NRF), and a policy control function (PCF). One or more of the user functions may be operably coupled to a unified data repository (UDR) 109 and are therefore considered to be UDR clients 108, which will be discussed in further detail below.
[0037] In an illustrative embodiment, a subscriber of the UE maintains a mobile subscription with an operator of a core network or another mobile network. Note that the UE typically subscribes to a so-called Home Public Land Mobile Network (HPLMN) in which some or all user functions reside. If the UE is roaming (not in the HPLMN), it typically connects to a Visited Public Land Mobile Network (VPLMN), also referred to as a Serving Network. Some or all of the Mobility Management Functions 106 may reside in the VPLMN, in which case the functions in the VPLMN communicate with the functions in the HPLMN as needed. However, in a non-roaming scenario, the Mobility Management Functions 106 and the UDR Client 108 may reside in the same communication network or elsewhere as needed.
[0038] The access point 104 is also operably coupled to a serving gateway function, namely a session management function (SMF) 110, which is operably coupled to a user plane function (UPF) 112. The UPF 112 is operably coupled to a packet data network, such as the Internet 114. As is known in 5G and other communication networks, the user plane (UP) or data plane carries network user traffic, while the control plane (CP) carries signaling traffic. The SMF 110 supports functions related to UP subscriber sessions, such as the establishment, modification, and release of PDU sessions. The UPF 112 supports functions that facilitate UP operations, such as packet routing and forwarding, communication with data networks (e.g., Figure 1 114) of interconnection, policy implementation and data buffering.
[0039] Understandably, Figure 1 is a simplified diagram because Figure 1Not all communication links and connections between network functions (NFs) and other system elements are shown in the figure. A person skilled in the art who is provided with various 3GPP TS / TRs will understand that Figure 1 Various links and connections not explicitly shown or that may be otherwise summarized.
[0040] When certain network elements are not the focus of the illustrative embodiments but can be found in appropriate 3GPP5G documents, further typical operations and functions of these network elements are not described in detail here. It should be understood that Figure 1 The specific arrangement of system elements in the embodiment is merely an example, and additional or alternative elements of other types and arrangements may be used to implement the communication system in other embodiments. For example, in other embodiments, the system 100 includes other elements / functionality not explicitly shown here. In addition, although the communication system 100 in the embodiment of FIG. Figure 1 Only a single element / function is shown in the embodiments, but this is only for simplicity and clarity of illustration. A given alternative embodiment may include a greater number of such system elements, as well as additional or alternative elements of the type normally associated with conventional system implementations.
[0041] It should also be noted that although Figure 1 The system elements are illustrated as single functional blocks, but the various subnets that make up the 5G network are divided into so-called network slices. A network slice (network partition) includes a series of network function (NF) sets (i.e., function chains) for each corresponding service type using network function virtualization (NFV) on a common physical infrastructure. Network slices are instantiated according to the needs of a given service, such as eMBB services, large-scale IoT services, and mission-critical IoT services. Therefore, when an instance of a network slice or function is created, the network slice or function is instantiated. In some embodiments, this involves installing or otherwise executing the network slice or function on one or more hosting devices of the underlying physical infrastructure. UE 102 is configured to access one or more of these services via access point 104 (gNB or N3IWF or TNGF or W-AGF, depending on the type of 5G access network). NFs can also access the services of other NFs.
[0042] Figure 2 2 is a block diagram of a processing architecture 200 of two components (e.g., network entities that may include network functions and other network elements of the communication system) involved in secure access control in a communication system in an illustrative embodiment. It should be understood that more than two components may be involved in secure access control according to the illustrative embodiments. Thus, Figure 2 The processing architecture associated with any two components that communicate directly or indirectly is illustrated. Thus, in the illustrative embodiment, each participant in the secure access control method is understood to be configured with Figure 2The processing architecture shown.
[0043] As shown, the network function / element 202 includes a processor 212 coupled to a memory 216 and an interface circuit 210. The processor 212 of the network function / element 202 includes a security access control processing module 214, which can be implemented at least in part in the form of software executed by the processor. The processing module 214 performs security access control described in conjunction with subsequent figures and other ways herein. The memory 216 of the network function / element 202 includes a security access control storage module 218, which stores data generated or otherwise used during security access control operations.
[0044] As further shown, the network function / element 204 includes a processor 222 coupled to a memory 226 and an interface circuit 220. The processor 222 of the network function / element 204 includes a security access control processing module 224 that may be implemented at least in part in the form of software executed by the processor 222. The processing module 224 performs the security access control described in conjunction with subsequent figures and other aspects of this document. The memory 226 of the network function / element 204 includes a security access control storage module 228 that stores data generated or otherwise used during security access control operations.
[0045] The processors 212 and 222 of the respective components 202 and 204 may include, for example, a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), or other types of processing devices or integrated circuits, as well as portions or combinations of these elements. Such integrated circuit devices and portions or combinations thereof are examples of the term "circuitry" as used herein. Various other arrangements of hardware and associated software or firmware may be used to implement the illustrative embodiments.
[0046] The memories 216 and 226 of the respective components 202 and 204 may be used to store one or more software programs executed by the respective processors 212 and 222 to implement at least a portion of the functionality described herein. For example, the software code executed by the processors 212 and 222 may be used to implement secure access control operations and other functionality as described in conjunction with subsequent figures in a straightforward manner.
[0047] Thus, a given one of memories 216 or 226 may be considered an example of what is more generally referred to herein as a computer program product or more generally as a processor-readable storage medium having executable program code contained therein. Other examples of processor-readable storage media may include any combination of disks or other types of magnetic or optical media. Illustrative embodiments may include articles of manufacture that include such computer program products or other processor-readable storage media.
[0048] The memory 216 or 226 may more specifically include, for example, electronic random access memory (RAM), such as static RAM (SRAM), dynamic RAM (DRAM), or other types of volatile or non-volatile electronic memory. The latter may include, for example, non-volatile memory, such as flash memory, magnetic RAM (MRAM), phase change RAM (PC-RAM), or ferroelectric RAM (FRAM). The term "memory" as used herein is intended to be interpreted broadly and may additionally or alternatively include, for example, read-only memory (ROM), disk-based memory, or other types of storage devices, as well as portions or combinations of such devices.
[0049] The interface circuits 210 and 220 of the respective components 202 and 204 illustratively include transceivers or other communication hardware or firmware that allow the associated system elements to communicate with each other in the manner described herein.
[0050] according to Figure 2 It is apparent that network function / element 202 is configured to communicate with network function / element 204, and vice versa, via their respective interface circuits 210 and 220. The communication involves network function / element 202 sending data to network function / element 204, and network function / element 204 sending data to network function / element 202. However, in alternative embodiments, other network elements or other components may be operably coupled between and to components 202 and 204. The term "data" as used herein is intended to be broadly interpreted to encompass any type of information that may be sent between components, including but not limited to messages, tokens, identifiers, keys, indicators, user data, control data, authentication data, and the like.
[0051] It should be understood that Figure 2 The specific arrangement of components shown in is only an example, and many alternative configurations are used in other embodiments. For example, any given network element / function can be configured to include additional or alternative components and support other communication protocols.
[0052] In the illustrative embodiment, as will be further explained below, the network function / element 202 is a NF such as a UDM, PCF, or NEF, and the network function / element 204 is a NF such as an NRF (Authorization Server).
[0053] In view of the above illustrative architecture, an illustrative embodiment of secure access control between one or more NFs will be further described below.Before such description, some major shortcomings will be described in the context of 5G networks, which are at least partly the motivation for developing illustrative embodiments.
[0054] Although two NFs that need to communicate (e.g., one NF can access the services of another NF) can be located in different PLMNs, some NFs in the same PLMN also need to communicate. In either scenario (inter-PLMN communication or intra-PLMN communication), the SBA communication model includes security methods that enable "NF service consumers" (service clients) to be authenticated and authorized to access services provided by "NF service producers" (service servers). One of the authorization methods supported in the 3GPP TS 33.501 (Release 15) cited above is based on the OAuth 2.0 (herein referred to as "OAuth") access token method. In the 5G system, the following model is adopted when using OAuth: (i) NRF is the OAuth authorization server; (ii) NF service consumer is the OAuth client; and (iii) NF service producer is the OAuth resource server.
[0055] The NF service consumer (client) discovers the NF service producer (resource server) through NRF and then obtains an access token to present to the NF service producer when invoking the service application programming interface (API) request.
[0056] In 5G SBA, OAuth-based service access authorization is only at the service level, not at the level of resources accessible through the service (e.g., data / dataset level or NF group level). In other words, 23.501 / 23.502 only allow restrictions on which NFs can use a service at the service level. Each service allows a set of operations (methods), but access and updates are managed only at the service level. There is no existing method to check whether a NF consumer is authorized to access a specific dataset or other resource accessible through a service.
[0057] This question raises a fundamental question, especially in relation to Figure 3 The UDR-related issues shown. Note that the UDR itself can be considered as an NF. The functions supported by the UDR are defined in Section 6.2.11 of TS23.501, including, for example, the storage and retrieval of subscription data by the UDM, the storage and retrieval of policy data by the PCF, the storage and retrieval of structured data for exposure, and so on.
[0058] Figure 3The data storage architecture 300 in a 5G system is illustrated. More specifically, as shown, UDM 302, PCF 304, and NEF 306 are operably coupled to UDR 310. UDR 310 includes a data access provider module 312 and a data storage 314. UDR 310 provides a Nudr_DataRepository (as shown, Nudr) service to all NF consumers (e.g., in this example, UDM 302, PCF 304, and NEF 306). Any NF can use the Nudr interface to access resources managed by UDR 310, which include (UE's) subscription data, policy data, structured data for exposure, and application data, as shown. For the Nudr_DataRepository service, UDR operations do not have specific access rights.
[0059] The following Data Set Identifiers are currently defined: Subscription Data, Policy Data, Application Data, and Data for Exposure. The subscription information of the UE (Subscription Data) is very sensitive information and must be accessible only to the UDM NF. Other NFs (such as NEF or PCF) must not be able to obtain access rights to the Nudr_DataRepository service, and other NFs are able to freely access all types of data including UE subscription data. Therefore, it is desirable to restrict the UDM to access only data related to the Subscription Data Set Identifier = Subscription Data.
[0060] As another example, it is desired to restrict the PCF to access only data associated with a Data Set Identifier = Policy Data.
[0061] In general, it is recognized here that different types of data within NF can have different data access authorizations. NF must be able to have an authorization management mechanism to ensure the security of data access.
[0062] Another required functionality is to restrict consumer access based on each NF producer group identifier (Id). For example, this functionality allows only certain UDM (AUSF or UDM or PCF, respectively) consumers to access certain UDM (AUSF or UDM or PCF, respectively) NF Group Ids. For example, this functionality aims to associate certain UDM (AUSF or UDM or PCF, respectively) Group Ids with certain enterprise user groups or public safety users and restrict access to NF instances (serving these specific group IDs) to some specific consumer NFs (e.g. associated with some specific slices).
[0063] The illustrative embodiments provide the above and other desired features. For example, in some embodiments, UDR dataset-based access control is provided, where the idea is to enhance the OAuth process to convey additional information in the access token (e.g., JavaScript Object Notation (JSON) Web Token) to enable the NF producer to verify whether the NF (NF consumer) making the request is authorized to access the resources / datasets managed by the NF producer. In other embodiments, group Id-based access control is provided, where the idea is to enhance the OAuth process to convey additional information in the JSON Web Token to enable the NF producer to verify whether the NF (NF consumer) making the request is authorized to access the resources associated with the group Id served by the NF producer.
[0064] That is, the illustrative embodiments add an access authorization level that not only allows authorization at the NF service level, but also goes beyond one level by performing resource level access authorization on API requests from NF consumers.
[0065] For example, in one or more illustrative embodiments, as part of the discovery process, the NRF checks whether the NF consumer is allowed to access the requested resource / data set.
[0066] Based on the configuration of the expected NF / NF service, the type of NF service consumer and the requested data set, the NRF determines whether to allow the NF service consumer to discover the expected NF instance.
[0067] When access to the requested data set is not allowed for the NF type of the NF consumer, the NRF rejects the discovery request.
[0068] When access to the requested Group Id is not allowed for the NF Type of the NF Consumer, the NRF rejects the Discovery Request.
[0069] In the access token request (i.e., Nnrf_AccessToken_Get Request), the NF service consumer includes the name of the data-set and / or group Id that it wants to access. This is respectively Figure 4A and Figure 4B Described in.
[0070] like Figure 4A As shown in the message flow 400 in (data set ID), in step 410, the NF service consumer 402 registers with the NRF 404 (authorization server).
[0071] In step 412, the NF service consumer 402 sends an access token request to the NRF 404. As shown in the figure, the access token request includes the expected NF service name, NF type, consumer NF type, OAuth client ID, and expected dataset ID.
[0072] At step 414, NRF 404 authorizes the client and generates an access token.
[0073] In step 416 , the NRF 404 sends an access token response (ie, Nnrf_AccessToken_Get Response) to the NF service consumer 402 .
[0074] If the NF service consumer 402 is authorized to access the data set within the target NF, the NRF 404 includes all resources (Uniform Resource Identifiers (URIs)) in the access token.
[0075] like Figure 4B As shown in the message flow 420 in (target NF group ID), in step 430, the NF service consumer 402 registers with the NRF 404 (authorization server).
[0076] In step 432, the NF service consumer 402 sends an access token request to the NRF 404. As shown in the figure, the access token request includes the expected NF service name, NF type, consumer NF type, OAuth client ID, and target NF group ID.
[0077] In step 434, NRF 404 authorizes the client and generates an access token.
[0078] In step 436 , the NRF 404 sends an access token response (ie, Nnrf_AccessToken_Get Response) to the NF service consumer 402 .
[0079] If the NF service consumer 402 is authorized to access the target NF group, the NRF 404 includes an indication of the group and / or group members in the access token.
[0080] Note that in some embodiments, the NF service consumer 402 does not include the target NF group ID in its access token request. In this case, for example, the NRF 404 will grant access to certain UDM / UDR group IDs only if the NF service consumer 402 is known to be associated with certain slices.
[0081] Accordingly, the NF service consumer 402 may issue a request containing one or more group IDs, or may issue a request without any group ID. The NRF 404 may then appropriately issue a token associated with one or more group IDs (possibly associated with an authorized group ID or a prohibited group ID), regardless of whether the NF service consumer request contains a group ID.
[0082] Note also that in the illustrative embodiment, the access token has an expiration time associated with it.
[0083] Figure 5 A table 500 of access token request types according to an illustrative embodiment is illustrated. Note that the bottom of the table indicates a new data set ID and target NF group ID. Table 500 represents an enhancement to the access token request type table in 3GPP TS 29.510 described above.
[0084] Figure 6 Table 600 of access token claim types according to an illustrative embodiment is shown. Note that the attribute names and descriptions of the new dataset ID and target NF Group ID are indicated at the bottom of the table. The type AccessTokenClaims is enhanced to include a new claim named "allowedResources". This contains the resource URIs of all resources that the NF service consumer can access in the NF producer. In addition, a new attribute "allowedNFGroup Id" is introduced. In some embodiments, this attribute contains a whitelist of allowed NF Group Ids or a blacklist of NF Group Ids that the consumer is not allowed to target. Table 600 is an enhancement of the access token claim type table in TS 29.510. In some embodiments, when the target NF producer is a UDR, the allowedResources claim is mandatory to include.
[0085] Figure 7 A secure allowed resource access control method 700 is shown as viewed from the perspective of a requesting service consumer in a communication system according to an illustrative embodiment. As shown, step 702 sends a request to an authorization server function in the communication system to access a service type and one or more resources associated with the service type. Step 704 receives an access token that identifies one or more service producers for the service type that is authorized to access and one or more resources associated with the service type. Step 706 uses the access token to access the service type and one or more resources associated with the service type at a service provider in the communication system. As described above, the steps of the method are performed by a service consumer of the communication system.
[0086] Figure 8A secure allowed group access control method 800 from the perspective of a requesting service consumer in a communication system is shown in accordance with an illustrative embodiment. As shown, step 802 sends a request to an authorization server function in the communication system to access a service type and one or more network function groups associated with the service type. Step 804 receives an access token that identifies one or more service producers for the service type that the device is authorized to access and one or more network function groups associated with the service type. Step 806 uses the access token to access one or more service producers in the communication system for the service type and one or more network function groups associated with the service type. As described above, the steps of the method are performed by a service consumer of the communication system.
[0087] Please note that, as mentioned above, Figure 8 The service consumer issues a request including one or more group IDs, and in an alternative embodiment, the request does not include any group IDs. The authorization service function may then, as appropriate, issue access tokens associated with one or more group IDs (which may be associated with authorized group IDs or prohibited group IDs), regardless of whether the service consumer request includes a group ID.
[0088] Combination Figures 1 to 8 The specific processing operations and other system functions described are presented only by way of illustrative examples and should not be construed as limiting the scope of the present disclosure in any way. Alternative embodiments may use other types of processing operations and messaging protocols. For example, in other embodiments, the order of the steps may be changed, or certain steps may be performed at least partially simultaneously with each other rather than sequentially. In addition, one or more steps may be repeated periodically, or multiple instances of the method may be performed in parallel with each other.
[0089] It should therefore be emphasized again that the various embodiments described herein are presented by way of illustrative examples only and should not be construed as limiting the scope of the claims. For example, alternative embodiments may utilize different communication system configurations, user equipment configurations, base station configurations, authentication and key agreement protocols, key pair provisioning and use procedures, messaging protocols, and message formats than those described above in the context of the illustrative embodiments. These and many other alternative embodiments within the scope of the appended claims will be apparent to those skilled in the art.
Claims
1. A device for communication, comprising: at least one processor; at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving a request from a service consumer in a communication system for access to a service type and one or more resources associated with the service type; determining whether the service consumer is authorized to access the service type and the one or more resources associated with the service type; Based on determining that the service consumer is authorized to access the service type and the one or more resources associated with the service type, generating an access token, the access token identifying one or more service producers for the service type that the service consumer is authorized to access and the one or more resources associated with the service type; as well as Sending the access token to the service consumer; wherein said at least one processor, said at least one memory and said computer program code are part of an authorization server function in said communication system, The determining step further includes: performing service-level authorization and resource-level authorization to determine the access rights that the access token will contain. 2 . The apparatus of claim 1 , wherein the one or more resources comprise one or more data sets.
3. The apparatus according to claim 1, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the apparatus to: send a rejection message in response to the request to the service consumer based on determining that the service consumer is not authorized one or more of the service level authorization and the resource level authorization.
4. The apparatus according to claim 1, wherein in a 5G system, the service consumer is a network function (NF) and the authorization server function is a network repository function (NRF).
5. A method for communication, performed by an authorization server function in a communication system, the method comprising: receiving, from a service consumer in the communication system, a request for access to a service type and one or more resources associated with the service type; determining whether the service consumer is authorized to access the service type and the one or more resources associated with the service type; Based on determining that the service consumer is authorized to access the service type and the one or more resources associated with the service type, generating an access token, the access token identifying one or more service producers for the service type that the service consumer is authorized to access and the one or more resources associated with the service type; as well as Sending the access token to the service consumer, The determining step includes: performing service-level authorization and resource-level authorization to determine the access rights that the access token will contain. The method of claim 5 , wherein the one or more resources include one or more data sets.
7. The method according to claim 5, further comprising: Based on determining that the service consumer is not authorized to perform one or more of the service-level authorization and the resource-level authorization, a rejection message in response to the request is sent to the service consumer.
8. A non-transitory computer-readable storage medium having executable program code embodied therein, which, when executed by a processor associated with an authorization server function, causes the authorization server function to perform the method of claim 5.
9. An apparatus for communication, comprising: at least one processor; at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: sending a request to an authorization server function in a communication system for access to a service type and one or more resources associated with the service type; receiving, based on the service type and the one or more resources associated with the service type being authorized to access, an access token identifying one or more service producers for the service type and the one or more resources associated with the service type that the device is authorized to access; as well as accessing the service type and the one or more resources associated with the service type at a service producer in the communication system using the access token; wherein the at least one processor, the at least one memory and the computer program code are part of a service consumer in the communication system, The access token includes access rights determined based on service-level authorization and resource-level authorization.
10. The apparatus of claim 9, wherein the one or more resources include one or more data sets.
11. The apparatus of claim 10, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the apparatus to: A denial message is received in response to the request based on one or more of the service level authorization and the resource level authorization not being authorized for access.
12. The apparatus of claim 9, wherein in a 5G system, the service consumer is a network function (NF) and the authorization server function is a network repository function (NRF).
13. A method for communication, performed by a service consumer of a communication system, the method comprising: sending a request to an authorization server function in the communication system for access to a service type and one or more resources associated with the service type; Based on the service type and the one or more resources associated with the service type being authorized to access, receiving an access token, the access token identifying one or more service producers for the service type and the one or more resources associated with the service type being authorized to access; as well as accessing the service type and the one or more resources associated with the service type at a service producer in the communication system using the access token; The access token includes access rights determined based on service-level authorization and resource-level authorization. The method of claim 13 , wherein the one or more resources include one or more data sets.
15. A non-transitory computer readable storage medium having executable program code embodied therein, the executable program code, when executed by a processor associated with a service consumer, causing the service consumer to perform the steps of claim 13.
