Method and apparatus for providing a configuration for providing a service to a terminal device - Patents.com

Abstract

An embodiment of the present disclosure relates to a method and an apparatus for providing a configuration for providing a service to a terminal device. A first aspect of the present disclosure provides a method performed by a first network function. The method may include sending a request to a second network function to provide at least one service parameter to a UE or a group of UEs (S201) and receiving a response from the second network function as to whether the request is approved or not (S202). According to an embodiment of the present disclosure, after the first network function sends a request to provide at least one service parameter to a terminal device, the first network function can recognize whether the request is approved or not.

Description

[Technical field]

[0001] The present disclosure relates generally to technologies of communication systems, and more particularly to a method and apparatus for providing a configuration for providing a service to a terminal device. [Background technology]

[0002] This section introduces aspects that may aid in a better understanding of the present disclosure and, as such, the statements in this section are to be read in this light and not as admissions of prior art or non-prior art.

[0003] In a communications network, a terminal device may be served by a network function through connections established directly or indirectly (across access networks and core networks, and / or other terminal devices).

[0004] Typically, the configuration of a service (such as the configuration regarding communication resources for establishing a connection, which may affect the quality of service from the server to the terminal device) can be determined based on the subscription information of the terminal device, which is stored in the communication network.

[0005] In some scenarios, the network function may also desire / need to provide configuration to the core network to affect the establishment of said connections and / or services for the terminal equipment, etc. Summary of the Invention

[0006] This Summary provides a simplified introduction to some of the concepts that are described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0007] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these and other problems. Various embodiments may be proposed that address one or more of the problems disclosed herein. In accordance with embodiments of the present disclosure, methods and apparatus may be utilized to provide a configuration for providing services to a terminal device.

[0008] A first aspect of the present disclosure provides a method performed by a first network function, the method may include sending a request to a second network function to provide at least one service parameter to a UE or a group of UEs, and receiving a response from the second network function regarding whether the request is granted or not.

[0009] In an embodiment of the present disclosure, the request may be approved if the at least one service parameter belongs to subscription data in a third network function.

[0010] In an embodiment of the present disclosure, the third network function may include a Unified Data Manager (UDM). The third network function may include a Policy Control Function (PCF).

[0011] In an embodiment of the present disclosure, the response may include a validity time of the at least one service parameter.

[0012] In an embodiment of the present disclosure, the at least one service parameter may include a service identity (ID). The at least one service parameter may include an ID of the UE or a group of the UEs.

[0013] In an embodiment of the present disclosure, the at least one service parameter may further include a service provider ID. The at least one service parameter may further include service-related data that is part of subscription data for the UE or the group of UEs. The service-related data may include slicing information, and / or a Data Network Name (DNN), and / or a Single Network Slice Selection Assistance Information (S-NSSAI).

[0014] In an embodiment of the present disclosure, the identity of the service may be associated with any one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF influenced traffic routing, or service specific parameter provisioning, or service area restrictions, or traffic steering policies requiring PCF policy evaluation. The service provider may include an AF, or a Machine Type Communication (MTC) provider.

[0015] In an embodiment of the present disclosure, the request may be approved if the service indicated by the ID of the service is approved for the UE or a group of UEs and / or if the service-related data includes a DNN and / or S-NSSAI that belongs to a list of subscribed DNNs and / or S-NSSAIs.

[0016] In an embodiment of the present disclosure, the first network function may include an application function (AF), and the second network function may include a network exposure function (NEF).

[0017] A second aspect of the present disclosure provides a method performed by a second network function, which may include receiving a first request from a first network function to provide at least one service parameter to a UE or group of UEs, sending a second request to a third network function to request whether the first network function is authorized to provide the at least one service parameter for the UE or group of UEs, receiving a response to the second request from the third network function indicating an authorization result, and sending a response to the first network function regarding whether the first request was approved.

[0018] In an embodiment of the present disclosure, the first request and / or the second request may be granted if the at least one service parameter belongs to subscription data in the third network function.

[0019] In an embodiment of the present disclosure, the third network function may include a Unified Data Manager (UDM). The third network function may include a Policy Control Function (PCF).

[0020] In an embodiment of the present disclosure, the response to the first request and / or the response to the second request may include a validity time of the at least one service parameter.

[0021] In an embodiment of the present disclosure, the method may further include, if the first request and / or the second request is approved, storing the at least one service parameter in a fourth network function.

[0022] In an embodiment of the present disclosure, the fourth network function may include a Unified Data Repository (UDR).

[0023] In an embodiment of the present disclosure, the at least one service parameter may include a service identity (ID). The at least one service parameter may include an ID of the UE or a group of the UEs.

[0024] In an embodiment of the present disclosure, the at least one service parameter may further include a service provider ID. The at least one service parameter may further include service-related data that is part of subscription data for the UE or the group of UEs. The service-related data may include slicing information, and / or a Data Network Name (DNN), and / or a Single Network Slice Selection Assistance Information (S-NSSAI).

[0025] In an embodiment of the present disclosure, the identity of the service may be associated with any one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF influenced traffic routing, or service specific parameter provisioning, or service area restrictions, or traffic steering policies requiring PCF policy evaluation. The service provider may include an AF, or a Machine Type Communication (MTC) provider.

[0026] In an embodiment of the present disclosure, the first request and / or the second request may be approved if the service indicated by the ID of the service is approved for the UE or a group of UEs and / or if the service-related data includes a DNN and / or S-NSSAI belonging to a list of subscribed DNNs and / or S-NSSAIs.

[0027] In an embodiment of the present disclosure, the fourth network function may inform a fifth network function of the at least one service parameter.

[0028] In an embodiment of the present disclosure, the fifth network function may include a policy control function (PCF).

[0029] In an embodiment of the present disclosure, the first network function may include an application function (AF), and the second network function may include a network exposure function (NEF).

[0030] A third aspect of the present disclosure provides a method performed by a third network function, which may include receiving a request from a second network function to provide whether a first network function is authorized to provide at least one service parameter to a UE or a group of UEs, and sending a response to the second network function indicating an authorization result.

[0031] In an embodiment of the present disclosure, the request may be approved if the at least one service parameter belongs to subscription data in the third network function.

[0032] In an embodiment of the present disclosure, the third network function may include a UDM or a PCF, and the second network function may include a NEF.

[0033] In an embodiment of the present disclosure, the response may include a validity time of the at least one service parameter.

[0034] In an embodiment of the present disclosure, the at least one service parameter may include a service identity (ID). The at least one service parameter may include an ID of the UE or a group of the UEs.

[0035] In an embodiment of the present disclosure, the at least one service parameter may further include a service provider ID. The at least one service parameter may further include service-related data that is part of subscription data for the UE or the group of UEs. The service-related data may include slicing information, and / or a Data Network Name (DNN), and / or a Single Network Slice Selection Assistance Information (S-NSSAI).

[0036] In an embodiment of the present disclosure, the identity of the service may be associated with any one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF influenced traffic routing, or service specific parameter provisioning, or service area restrictions, or traffic steering policies requiring PCF policy evaluation. The service provider may include an AF, or a Machine Type Communication (MTC) provider.

[0037] In an embodiment of the present disclosure, the request may be approved if the service indicated by the ID of the service is approved for the UE or a group of UEs and / or if the service-related data includes a DNN and / or S-NSSAI that belongs to a list of subscribed DNNs and / or S-NSSAIs.

[0038] A fourth aspect of the present disclosure provides a first network function, which may have one or more processors and one or more memories having computer program code, which may be configured, in conjunction with the one or more processors, to cause the first network function to at least send a request to a second network function to provide at least one service parameter to a UE or a group of UEs, and to receive a response from the second network function regarding whether the request is granted.

[0039] In an embodiment of the present disclosure, the first network function may further be made to perform a method according to any of the above-mentioned embodiments.

[0040] A fifth aspect of the present disclosure provides a second network function, which may have one or more processors and one or more memories having computer program code. The one or more memories and the computer program code, together with the one or more processors, may be configured to at least: cause the second network function to receive from a first network function a first request to provide at least one service parameter to a UE or group of UEs; send to a third network function a second request to determine whether the first network function is authorized to provide the at least one service parameter for the UE or group of UEs; receive from the third network function a response to the second request indicating a result of the authorization; and send to the first network function a response as to whether the first request is authorized.

[0041] In an embodiment of the present disclosure, the second network function may further be made to perform the method according to any of the above-mentioned embodiments.

[0042] A sixth aspect of the present disclosure provides a third network function, which may have one or more processors and one or more memories having computer program code, the one or more memories and the computer program code may be configured, together with the one or more processors, to cause the third network function to at least receive a request from a second network function to provide whether the first network function is authorized to provide at least one service parameter to a UE or a group of UEs, and to send a response to the second network function indicating an authorization result.

[0043] In an embodiment of the present disclosure, the third network function may further be made to perform the method according to any of the above-mentioned embodiments.

[0044] A seventh aspect of the present disclosure provides a computer readable medium having computer program code embodied therein for use with network functionality, the computer program code including code for performing a method according to any one of the preceding embodiments.

[0045] An eighth aspect of the present disclosure provides a first network function, the first network function may have a sending unit configured to send a request to a second network function for at least one service parameter to be provided by the first network function to a terminal device, the first network function may further have a receiving unit configured to receive a response from the second network function regarding whether the request is approved or not.

[0046] A ninth aspect of the present disclosure provides a second network function, the second network function may have a receiving unit configured to receive a request from a first network function for at least one service parameter to be provided by the first network function to a terminal device, the second network function may further have a transmitting unit configured to transmit a response to the first network function regarding whether the request is approved or not.

[0047] A tenth aspect of the present disclosure provides a third network function, which may have a receiving unit configured to receive a request from a second network function for at least one service parameter to be provided to a terminal device by a first network function, and may further have a sending unit configured to send a response to the second network function regarding whether the request is approved or not.

[0048] According to an eleventh aspect of the present disclosure, there is provided a method implemented in a communication system that may include a host computer, a base station, and a UE. The method may include providing user data at the host computer. Optionally, the method may include initiating a transmission at the host computer conveying the user data to the UE over a cellular network having the base station.

[0049] According to a twelfth aspect of the present disclosure, there is provided a communication system including a host computer, the host computer may have a processing circuit configured to provide user data and a communication interface configured to transfer the user data to a cellular network for transmission to a UE, the cellular network may have a base station having a wireless interface and a processing circuit.

[0050] According to a thirteenth aspect of the present disclosure, there is provided a communication system including a host computer, the host computer may have a processing circuit configured to provide user data and a communication interface configured to transfer the user data to a cellular network for transmission to a UE, the UE may have a wireless interface and a processing circuit.

[0051] According to a fourteenth aspect of the present disclosure, there is provided a method implemented in a communication system that may include a host computer, a base station, and a UE, the method may include receiving, at the host computer, user data transmitted from the UE to the base station.

[0052] According to a fifteenth aspect of the present disclosure, there is provided a communication system including a host computer, the host computer may have a communication interface configured to receive user data originating from a transmission from a UE to a base station, the UE may have a wireless interface and a processing circuit.

[0053] According to a sixteenth aspect of the present disclosure, there is provided a method implemented in a communications system that may include a host computer, a base station, and a UE, the method may include receiving, at the host computer, user data from the base station originating from a transmission received by the base station from the UE.

[0054] According to a seventeenth aspect of the present disclosure, there is provided a communication system that may include a host computer having a communication interface configured to receive user data originating from a transmission from a UE to a base station, the base station having a wireless interface and processing circuitry.

[0055] According to an embodiment of the present disclosure, a method or apparatus is provided for providing a configuration for providing a service to a terminal device, in particular, after a first network function sends a request to provide at least one service parameter to a terminal device, the first network function may obtain a response as to whether the request is approved or not. [Brief description of the drawings]

[0056] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of several embodiments of the present disclosure in the accompanying drawings, in which the same reference numerals generally refer to the same components in the embodiments of the present disclosure.

[0057] [Figure 1A] FIG. 1A illustrates an exemplary procedure for service parameter provisioning.

[0058] [Figure 1B] FIG. 1B is a diagram showing an example of a slice selection flow.

[0059] [Figure 1C] FIG. 1C illustrates an exemplary network exposure function in 5GC.

[0060] [Diagram 2] FIG. 2 is a flow chart illustrating a method performed by a first network function according to an embodiment of the present disclosure.

[0061] [Figure 3A] FIG. 3A is a flow chart illustrating a method performed by a second network function according to an embodiment of the present disclosure.

[0062] [Figure 3B] FIG. 3B is a flow chart illustrating additional steps of a method performed by a second network function in accordance with an embodiment of the present disclosure.

[0063] [Figure 3C] FIG. 3C is a flow chart illustrating additional steps of a method performed by a second network function according to an embodiment of the present disclosure.

[0064] [Figure 3D] FIG. 3D is a flow chart illustrating another method performed by a second network function according to an embodiment of the disclosure.

[0065] [Figure 4] FIG. 4 is a flow chart illustrating a method performed by a third network function according to an embodiment of the present disclosure.

[0066] [Figure 5A] FIG. 5A illustrates a high-level solution overview of some embodiments of the present disclosure.

[0067] [Figure 5B] FIG. 5B is a call flow diagram illustrating an exemplary UDM-based early approval procedure.

[0068] [Figure 6]FIG. 6 is an exemplary call flow diagram for providing a configuration for providing a service to a terminal device according to an embodiment of the present disclosure.

[0069] [Figure 7A] FIG. 7A is a block diagram illustrating an apparatus for a first network function, a second network function, and a third network function according to an embodiment of the present disclosure.

[0070] [Figure 7B] FIG. 7B is a block diagram illustrating a computer-readable storage medium according to an embodiment of the present disclosure.

[0071] [Figure 8A] FIG. 8A is a schematic diagram illustrating units of an apparatus for a first network function according to an embodiment of the present disclosure.

[0072] [Figure 8B] FIG. 8B is a schematic diagram illustrating units of an apparatus for a second network function according to an embodiment of the present disclosure.

[0073] [Figure 8C] FIG. 8C is a schematic diagram illustrating units of an apparatus for a third network function according to an embodiment of the present disclosure.

[0074] [Figure 9] FIG. 9 is a block diagram illustrating a telecommunications network connected to a host computer through an intermediate network in accordance with some embodiments of the present disclosure.

[0075] [Figure 10] FIG. 10 is a block diagram illustrating a host computer communicating with a UE via a base station over a partially wireless connection in accordance with some embodiments of the disclosure.

[0076] [Figure 11]FIG. 11 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure.

[0077] [Figure 12] FIG. 12 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure.

[0078] [Figure 13] FIG. 13 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure.

[0079] [Figure 14] FIG. 14 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0080] Some of the embodiments contemplated in this disclosure will be described more fully with reference to the accompanying drawings. However, the subject matter disclosed herein encompasses other embodiments within its scope. The subject matter disclosed should not be construed as being limited to only the described embodiments, but rather, these embodiments are provided as examples to inform those skilled in the art of the scope of the subject matter.

[0081] In general, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is clearly given and / or a different meaning is implied from the context. All references to elements, apparatus, components, means, steps, etc. should be interpreted in an open-ended manner as meaning at least one instance of the element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless a context with another step is explicitly stated and / or the need for a particular context with another step is implied. Any feature of any embodiment disclosed herein may be applied to any other embodiment, where appropriate. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the following embodiments will become apparent from the following description.

[0082] Throughout this specification, references to features, advantages, or similar words do not imply that all of the features and advantages that may be realized in the present disclosure should or are present in any single embodiment of the present disclosure. Rather, words referring to features and advantages are understood to mean that the particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the features, advantages, and characteristics described in the present disclosure can be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in any embodiment of the present disclosure may be recognized in a particular embodiment.

[0083] As used herein, the term "network" or "communications network / system" refers to a network / system conforming to any suitable communications standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), etc. Furthermore, communications between terminal equipment and network nodes in a communications network may be performed according to any suitable generation communications protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), 4G, 4.5G, 5G communications protocols, and / or any other protocols now known or to be developed in the future.

[0084] The term "function" refers to an apparatus / device / node / entity having an access function in a communication system for a terminal device to access the network or receive services from the network. The function may include a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a server node / function (such as a service capability server / application server (SCS / AS), a group communication service application server (GCS AS), an application function (AF)), an exposure node / function (such as a service capability exposure function, a mobility management entity, a network exposure function (NEF)), a unified data management (UDM), a home subscriber server (HSS), a session management function (SMF), an access and mobility management function (AMF), a mobility management entity (MME), a controller or any other suitable device in a wireless communication network. A BS may be, for example, a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, or a low power node (femto, pico, etc.).

[0085] Further examples of network functions may include multi-standard radio (MSR) radio equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a positioning node, etc.

[0086] More generally, however, a network function may represent any suitable device (or group of devices) capable of, configured to, arranged to, and / or operable to enable and / or provide terminal device access to a wireless communication network or to provide some service to terminal devices having access to the wireless communication network.

[0087] For example, in embodiments of the present disclosure, such functionality may be implemented in any type of hardware and / or software, such as a standalone device, a virtual machine, a cloud-implemented server, and / or a distributed server.

[0088] The term "terminal equipment" encompasses equipment capable of communicating with network entities / functions such as base stations or with other wireless equipment by transmitting and / or receiving radio signals. Thus, the term terminal equipment encompasses, but is not limited to, mobile phones, stationary or mobile wireless devices for machine-to-machine communication, built-in or embedded wireless cards, externally inserted wireless cards, vehicles, etc.

[0089] As yet another particular example, in an Internet of Things (IoT) scenario, a terminal device, also called an IoT device, may represent a machine or other equipment that performs monitoring, sensing and / or measurement, etc., and transmits results of such monitoring, sensing and / or measurement, etc. to another terminal device and / or network equipment. The terminal device in this case may be a Machine-to-Machine (M2M) device, which in the context of the 3rd Generation Partnership Project (3GPP) may be called a Machine Type Communication (MTC) device.

[0090] As one particular example, the terminal equipment may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or equipment are sensors, metering devices such as power meters, industrial machines, or home or personal appliances, e.g., personal wearables such as refrigerators, televisions, clocks, etc. In other scenarios, the terminal equipment may represent a vehicle or other equipment, e.g., a medical device, capable of monitoring, sensing, and / or reporting its own operating status or other functions related to its operation.

[0091] As used herein, the terms "first", "second", etc. refer to different elements. The singular forms "a" and "an" are intended to include the plural unless the context clearly indicates otherwise. The terms "comprises", "comprising", "has", "having", "includes", and / or "including" as used herein specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence of one or more other features, elements, components, and / or combinations thereof. The term "based on" should be interpreted as "based at least in part on". The terms "one embodiment" and "an embodiment" should be interpreted as "at least one embodiment". The term "another embodiment" should be interpreted as "at least one other embodiment". Further definitions (both explicit and implied) are set forth below.

[0092] There are several solutions provided to the network function to provide service specific parameters.

[0093] FIG. 1A illustrates an exemplary procedure for service parameter provisioning.

[0094] For example, 3GPP TS (Technical Specification) 23.502 Rel-16 V16.6.0 (Figure 1A corresponds to Figure 4.15.6.7-1 of this TS) specifies an NEF service procedure so that the AF can provide service-specific parameters to the 5G system through the NEF.

[0095] In step 1, the AF may create an AF request. For example, the AF request sent to the NEF may include the following information:

[0096] 1) Service Description

[0097] Combining DNN and S-NSSAI

[0098] AF Service Identifier

[0099] Application Identifier

[0100] 2) (one or more) target UEs or groups of UEs

[0101] GPSI (Universal Public Subscriber Identifier), UE IPv4 / IPv6 / MAC address, UE group ID, arbitrary UE ID

[0102] 3) Service parameters

[0103] Configuration parameters for V2X (Vehicle to everything)

[0104] This procedure is defined as common to all services. In the current release of the specification, it is intended for use in the V2X UC (V2X Use Case).

[0105] In steps 2 and 3, the NEF authorizes the request received from the AF (e.g., the NEF checks whether the AF is authorized to call the API (Application Program Interface) / operation) and stores the information in the UDR as "application data".

[0106] If the target UE is reachable according to the UE policy delivery procedure specified in 3GPP TS 23.502 V16.6.0 subclause 4.2.4.3, the service parameters are delivered by the PCF to the target UE using steps 5 and 6. If a UE policy delivery failure is notified to the PCF, it may subscribe to the "Connectivity state change (IDLE or CONNECTED)" event as specified in subclause 5.2.2.3.

[0107] In step 4, the AF may receive a response from the NEF indicating that the request was successfully received. However, the problem is that the AF does not know whether the request to configure the service for the UE was approved or not, and the AF can only rely on the successful receipt response provided by the NEF when the request is made.

[0108] In 3GPP Rel 17, a new Work Item Description (WID) has been created for enhanced support for Edge Computing in 5GC (5G Core Networks) and based on the recommendation in TR (Technical Report) 23.748 V2.0.0, Key Issue #1: DNS-based solutions for multiple PDU sessions (clause 9.1.1 of the TR), it is proposed to reuse and enhance this procedure to allow the AF to influence the UE Route Selection Policy (URSP) decision for the UE.

[0109] The UE route may be related to network slicing. The concept of network slicing is used to meet the diverse requirements of various 5G use cases. Various network services with different characteristics will be made available to third party applications / users / operators as capabilities to enable various new business models. A particular network service can be instantiated according to the on-demand requirements of the third party user / operator and the business policies between the network service provider and the service consumer.

[0110] It is expected that in the future there will be many different types of dedicated core networks for different uses. The relationship between a specific use and a network service with special characteristics can be dynamic and flexible to support flexible / agile business models. For example, at the beginning of a special use, the traffic of the special use may still be served by a common network for basic network services. As the number of special or VIP users increases, dedicated network services are instantiated to support the required functions and enable flexible business models. Furthermore, as mentioned by 3GPP, typically one default CN is associated with one or more dedicated core networks. If a dedicated core network is not available or there is not enough information, the special use UE is directed to a default CN for basic network services or to a dedicated network slice or DCN (Dedicated Core Network) with service provider specific policies.

[0111] The 5GC provides policy information, such as the UE Route Selection Policy (URSP), to the UE, which is used by the UE to determine whether detected application traffic can be associated with an established PDU (Protocol Data Unit) session, offloaded to a non-3GPP access outside the PDU session, or trigger the establishment of a new PDU session.

[0112] Part of the URSP is the Network Slicing Selection Policy (NSSP), which is used by the UE to associate a matching application with a particular network slice, so that the UE can run the application with a connection setup in the designated network slice with predefined characteristics and quality of service that can satisfy a given business model.

[0113] Currently, URSP / NSSP rules can be pre-configured in the UE or provided to the UE by 5GC using the PCF. The PCF selects the applicable URSP / NSSP rules for each UE based on subscription information, local configuration, and operator policies (which can take dynamic conditions such as UE location, ToD (time of day) as input).

[0114] Additionally, 3GPP Rel17 has an ongoing WID that allows the AF to influence the applicable URSP for a UE or group of UEs by providing input information to the PCF via the NEF and UDR, used in determining the applicable URSP (3GPP TR 23.748).

[0115] The establishment of user plane connectivity to a data network via a network slice has two steps:

[0116] Performing a 5GC registration procedure to select an AMF that supports the required network slice;

[0117] Establishing one or more PDU sessions with the required data network in the selected network slice.

[0118] UE is in PLMN (Public Land Mobile Network) Cashier When operating the application, the UE provides the network with a Request-NSSAI that contains the S-NSSAI(s) corresponding to the slice(s) for which the UE wishes to register. The UE associates the application with the S-NSSAI based on the NSSP of the URSP rule.

[0119] FIG. 1B is a diagram showing an example of a slice selection flow.

[0120] The 3GPP-specified network slice selection flow (quoted from TS 23.502) is shown in Figure 1B (Figure 1B corresponds to Figure 4.2.2.2.3-1 of TS).

[0121] The selection of a set of network slices for a UE is typically triggered by the AMF that first contacts during the registration procedure by interacting with the NSSF.

[0122] In step 4a [conditional], a slice selection request (request NSSAI (Network Slice Selection Assistance Information), subscribing S-NSSAI, TAI (tracking area identity), and PLMN ID of SUPI (subscription permanent identifier)) is sent from the initial AMF to the NSSF.

[0123] If there is a need for slice selection, for example if the initial AMF cannot provide all of the (one or more) S-NSSAIs from the requested NSSAI allowed by the subscription information, the initial AMF sends a Slice Selection Request to the NSSF. The initial AMF sends the requested NSSAI, the subscribed S-NSSAI, the PLMN ID of the SUPI, and the TAI of the UE to the NSSF.

[0124] In step 4b [Conditional], a Slice Selection Response (AMF set or list of AMF addresses, allowed NSSAI, [NSI ID], [NRF] (Network Repository Function), [Rejected (S-NSSAI) (1 or more), cause value (1 or more))] is sent from the NSSF to the initial AMF.

[0125] The NSSF returns a list of (one or more) candidate AMFs to the initial AMF based on the allowed NSSAI and the target AMF set or configuration.

[0126] As per 3GPP specifications, the NSSF makes slice selection decisions based on this information, local configuration and other available information (including RAN capabilities in the UE's current tracking area or analysis information provided by the NWDAF (Network Data Analysis Function)).

[0127] The set of network slices for a UE may be changed at any time while the UE is registered in the network and may be initiated by either the network or the UE.

[0128] When URSP rules are updated or their validity changes, it may be necessary on the UE side to re-evaluate the association of existing applications to PDU sessions. The UE may also re-evaluate the association of applications to PDU sessions for the following reasons: Periodic re-evaluation based on UE implementation - The existing PDU session used to route the application's traffic based on the URSP rules is released.

[0129] If the re-evaluation leads to a change in the association of the application to a PDU session, e.g., if the application should be associated with a different PDU session or a new PDU session needs to be established, the UE may implement such a change in a timely manner based on the implementation.

[0130] 5GC is designed to accommodate various services, e.g., large-scale IoT, critical communications, and enhanced mobile broadband, respectively. To enable third parties / UEs to access information about services provided by the network (e.g., connectivity information, QoS, mobility, etc.) and dynamically customize network capabilities for different and diverse use cases within the limits set by the operator, 5GC provides network exposure functionality that allows third parties or UEs to appropriately access / exchange network information.

[0131] FIG. 1C illustrates an exemplary network exposure function in 5GC.

[0132] The Network Exposure Function (NEF) supports the exposure of such capabilities of network functions by utilizing information collected through 3GPP network internal interfaces and exposing it to Application Functions (AFs) through appropriate APIs. The exposure architecture as specified by 5CG according to TS 23.501 V16.6.0 is shown below (Figure 1C corresponds to Figure 4.2.3-5 of said TS):

[0133] However, existing 3GPP procedures specified for NEF / UDM service APIs lack proper and optimal early validation / check of specific service information requested by the AF against the authorized values ​​provisioned for the UE in the subscription information in the UDR (e.g., the DNN / S-NSSAI requested for the URSP rule may not belong to the list of authorized S-NSSAI / DNN combinations for the UE).

[0134] Indeed, the network (e.g. PCF) does this kind of validation later in the service specific parameters provisioning procedure to avoid sending wrong information in the URSP to the UE, but this kind of validation may happen much later than when the AF makes the request (if the UE is not yet registered or depending on the UE's location). As a result, the AF may get the desired response to the AF request for service specific parameters provisioning, but it is not actually a valid request, and later (e.g. hours later) when the UE connects to the network or accesses a certain location, the PCF may perform this validation and skip the request because it is not valid. The problem is that the AF does not notice this error and trusts the desired response provided by the NEF at the time of the request.

[0135] FIG. 2 is a flow chart illustrating a method performed by a first network function according to an embodiment of the present disclosure.

[0136] As shown in FIG. 2, the method performed by the first network function 200 may include sending a request to a second network function to provide at least one service parameter to a terminal device by the first network function (S201), and receiving a response from the second network function as to whether the request has been approved or not (S202).

[0137] In an embodiment of the present disclosure, the at least one service parameter may be for a terminal device or a group of terminal devices that includes the terminal device.

[0138] Further, the terminal device may include a UE as an example, That is, in step S201, at least one service parameter may be provided to a UE or a group of UEs.

[0139] According to an embodiment of the present disclosure, the first network function can get a response as to whether the request is approved or not. Early approval and verification for configuration from the first network function can be performed. Thus, the first network function can be more aware of the status of the service to the terminal device. The efficiency for providing and / or configuring the service by the first network function can be improved.

[0140] In an embodiment of the present disclosure, the terminal device may include a user equipment (UE) indicated by a SUPI, a GPSI, etc., or any other type of device capable of communicating with a wireless station.

[0141] In an embodiment of the present disclosure, the request may be approved if at least one service parameter belongs to the subscription data in the third network function.

[0142] In an embodiment of the present disclosure, the third network function may include a UDM or a PCF.

[0143] According to an embodiment, the request may be approved if at least one service parameter belongs to subscription data in a third network function, such as a UDM. In particular, since the UDM currently performs approval for many other published functions, it would be efficient to enhance the current UDM to further have the ability to approve requests from the first network function.

[0144] In an embodiment of the present disclosure, the response may include a validity time of at least one service parameter.

[0145] According to an embodiment of the present disclosure, by using the validity time of at least one service parameter, the first network function can know when a configuration needs to be re-requested / updated.

[0146] In an embodiment of the present disclosure, the at least one service parameter may include an identification (ID) of a service. The at least one service parameter may include an ID of a terminal device.

[0147] According to an embodiment of the present disclosure, some parameters, such as an ID indicating a service and / or an ID indicating a terminal device, may be recommended or required. For example, by using these parameters, the request may at least indicate that a particular service for a particular terminal device is to be configured by the first network function.

[0148] In an embodiment of the present disclosure, the at least one service parameter may further include a service provider ID. The at least one service parameter may further include service-related data that is part of subscription data for the terminal device. The service-related data may include slicing information, and / or a data network name (DNN), and / or a single network slice selection assistance information (S-NSSAI).

[0149] In an embodiment of the present disclosure, the ID of the service may be associated with any existing service or may be associated with a new service. For example, in an embodiment of the present disclosure, the ID of the service may be associated with any one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF influenced traffic routing, or service specific parameter provisioning, or service area restrictions, or a traffic steering policy requiring PCF policy evaluation. The service provider may include an AF, or a machine type communication (MTC) provider.

[0150] In an embodiment, a service provider refers to an MTC service provider or any other content service provider (e.g., Netflix, YouTube®), which may be identified from the perspective of the NEF northbound API by an AFId or SCSAsId (Service Capability Server / Application Server Id) or mtcProviderId.

[0151] In an embodiment of the present disclosure, a request may be approved if the service indicated by the service ID is approved for the terminal equipment and / or if the service-related data includes a DNN and / or S-NSSAI that belongs to a list of subscribed DNNs and / or S-NSSAIs.

[0152] According to an embodiment of the present disclosure, the ID of the service may indicate any kind of service that may be provided to the terminal device by the first network function. Furthermore, different additional parameters may also be included in the request based on different services.

[0153] In an embodiment of the present disclosure, the first network function may include an application function (AF), and the second network function may include a network exposure function (NEF).

[0154] FIG. 3A is a flow chart illustrating a method performed by a second network function according to an embodiment of the present disclosure.

[0155] The method performed by the second network function 300 may include receiving a request from the first network function for the first network function to provide at least one service parameter to a terminal device (S301) and sending a response to the first network function regarding whether the request has been approved or not (S302).

[0156] FIG. 3B is a flow chart illustrating additional steps of a method performed by a second network function in accordance with an embodiment of the present disclosure.

[0157] In an embodiment of the present disclosure, the method may further include determining whether the first network function is approved for the service for the terminal device based on a local policy (S303), and if the first network function is approved, sending a request to a third network function (S304), and receiving a response from the third network function regarding whether the request is approved (S305).

[0158] It should be understood that the second network function need not send an exactly identical request when sending a request to a third network function. For example, some parameters may be removed or added. Further, some parameters may be mapped from an external format / value to an internal format / value.

[0159] In an embodiment of the present disclosure, a request (such as the first request and / or the second request) may be granted if at least one service parameter belongs to subscription data in a third network function.

[0160] In an embodiment of the present disclosure, the third network function may include a Unified Data Manager (UDM) or PCF.

[0161] In an embodiment of the present disclosure, the response (such as the response to the first request and / or the response to the second request) may include a validity time of at least one service parameter.

[0162] In an embodiment of the present disclosure, the at least one service parameter may be for a terminal device or a group of terminal devices that includes the terminal device.

[0163] FIG. 3C is a flow chart illustrating additional steps of a method performed by a second network function according to an embodiment of the present disclosure.

[0164] In an embodiment of the present disclosure, the method may further include storing (S306) the at least one service parameter in the fourth network function if the request is approved. The at least one service parameter may be stored if the first request and / or the second request is approved.

[0165] In an embodiment of the present disclosure, the fourth network function may include a Unified Data Repository (UDR).

[0166] According to an embodiment of the present disclosure, if the request is approved, at least one service parameter may be stored to configure the service for the terminal device.

[0167] FIG. 3D is a flow chart illustrating another method performed by a second network function according to an embodiment of the disclosure.

[0168] As shown in FIG. 3D, the method performed by the second network function may include receiving a first request from the first network function to provide at least one service parameter to the UE or group of UEs (S307), sending a second request to a third network function to request whether the first network function is authorized to provide the at least one service parameter to the UE or group of UEs (S308), receiving a response to the second request from the third network function indicating the result of the authorization (S309), and sending a response to the first network function regarding whether the first request was approved (S310).

[0169] In an embodiment of the present disclosure, the at least one service parameter may include an identity (ID) of the service. The at least one service parameter may include an ID of a terminal device. The ID may be of a UE of a group of UEs.

[0170] In an embodiment of the present disclosure, the at least one service parameter may further include a service provider ID. The at least one service parameter may further include service-related data that is part of subscription data for the terminal device. The service-related data may include slicing information, and / or a data network name (DNN), and / or a single network slice selection assistance information (S-NSSAI).

[0171] In an embodiment of the present disclosure, the identity of the service may be associated with any one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF influenced traffic routing, or service specific parameter provisioning, or service area restrictions, or traffic steering policies requiring PCF policy evaluation. The service provider may include an AF, or a machine type communication (MTC) provider.

[0172] In an embodiment of the present disclosure, a request (such as the first request and / or the second request) may be approved if the service indicated by the service ID is approved for the terminal equipment and / or if the service-related data includes a DNN and / or S-NSSAI that belongs to a list of subscribed DNNs and / or S-NSSAIs.

[0173] In an embodiment of the present disclosure, the fourth network function may inform the fifth network function of the at least one service parameter.

[0174] In an embodiment of the present disclosure, the fifth network function may include a policy control function (PCF).

[0175] According to an embodiment of the present disclosure, after the PCF receives at least one service parameter (or at least a portion of the service parameter including a policy for providing a service to a terminal device), the policy may be delivered to the UE as specified in the 3GPP TS.

[0176] In an embodiment of the present disclosure, the first network function may include an application function (AF), and the second network function may include a network exposure function (NEF).

[0177] FIG. 4 is a flow chart illustrating a method performed by a third network function according to an embodiment of the present disclosure.

[0178] The method performed by the third network function 400 may include receiving a request from the second network function to provide at least one service parameter to a terminal device by the first network function (S401) and sending a response to the second network function regarding whether the request has been approved or not (S402).

[0179] In S401, the request may be for providing whether the first network function is authorized to provide at least one service parameter to a UE or a group of UEs, and in S402, the response may indicate the result of the authorization.

[0180] In an embodiment of the present disclosure, the request may be approved if at least one service parameter belongs to the subscription data in the third network function.

[0181] In an embodiment of the present disclosure, the third network function may include a UDM or a PCF, and the second network function may include a NEF.

[0182] In an embodiment of the present disclosure, the response may include a validity time of at least one service parameter.

[0183] In an embodiment of the present disclosure, the at least one service parameter may be for a terminal device or a group of terminal devices that includes the terminal device.

[0184] In an embodiment of the present disclosure, the at least one service parameter may include a service identity (ID) and / or a terminal device ID. The terminal device ID may be for a UE of a group of UEs.

[0185] In an embodiment of the present disclosure, the at least one service parameter may further include an ID of a service provider. The at least one service parameter may further include service-related data that is part of subscription data for the terminal device. The subscription data for the terminal device may be for a UE of a group of UEs. The service-related data may include slicing information, and / or a data network name (DNN), and / or a single network slice selection assistance information (S-NSSAI).

[0186] In an embodiment of the present disclosure, the identity of the service may be associated with any one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF influenced traffic routing, or service specific parameter provisioning, or service area restrictions, or traffic steering policies requiring PCF policy evaluation. The service provider may include an AF, or a machine type communication (MTC) provider.

[0187] In an embodiment of the present disclosure, the request may be approved if the service indicated by the ID of the service is approved for the terminal device and / or if the service-related data includes a DNN and / or S-NSSAI that belongs to a list of subscribed DNNs and / or S-NSSAIs. The service indicated by the ID of the service is approved for the UE of the group of UEs.

[0188] FIG. 5A illustrates a high-level solution overview of some embodiments of the present disclosure.

[0189] As shown in FIG. 5A, in step 1, an AF request may be made by an AF located in a location such as a data network (eg, an operator or the Internet).

[0190] In step 2, the AF calls the extended NEF service API (ie, Nnef_ServiceParameter_Create) and sends its request to the NEF, including the target UE(s), service description and policy (eg, AFServiceId, AppId, UE ID(s), domain descriptor).

[0191] In step 2a, the NEF approves the received AF request based on local SLA (Service Level Agreement) policy, i.e. the AF is approved and authorized to use the service and the DNN / S-NSSAI mapped from the AFServiceId is authorized to use the external ID (based on the local SLA) and to use the external ID for the internal SUPI / Group ID using UDM.

[0192] Preferably, some parameters (e.g., ID of the service = URSP, or AF session with QoS, ID of the terminal device) may be mandatory. The remaining parameters are optional, but the UDM can approve the request based on these two minimum parameters (service id and device id). Other parameters (e.g., MTC provider Id) may be added. And based on the service, e.g., URSP, additional parameters, e.g., NSSAI / DNN, are also required. More preferably, all these parameters may need to be approved for the device, i.e., 1) the service (e.g., URSP), 2) the MTC provider (service provider generating multiple applications) (e.g., google.com), 3) service-related parameters (e.g., in case of URSP, NSSAI / DNN are mandatory when URSP is requested).

[0193] A local policy may be per subscriber / device, i.e., the local policy is not common to all devices. It is a policy provisioned per device (e.g., for device-1, a URSP requested by MTC provider-1 is accepted as long as the NSSAI / DNN requested in the URSP is also provisioned in device-1).

[0194] In step 2b (improved step), the NEF performs authorization through the UDM to verify whether the UE or group of UEs is authorized to use the requested service-specific information (DNN / S-NSSAI and other service information).

[0195] In step 3, the NEF stores the information in the UDR as "application data".

[0196] In step 4, the NEF responds to the AF after successfully storing the AF request in the UDR.

[0197] Step 5a (precondition): The PCF subscribes to notifications of data changes in the UDR when the UE is registered.

[0198] In step 5b, the PCF receives notification of data changes in the application specific information from the UDR via the Nudr_DM_Notify service.

[0199] In step 6, the PCF initiates UE policy delivery as specified in 3GPP TS 23.502, clause 4.2.4.3. If the PCF is notified of UE policy delivery failure, it may subscribe to the "Connection state change (IDLE or CONNECTED)" event.

[0200] The PCF should check that the S-NSSAI / DNN provided by the UDR for a given service for the URSP belongs to the list of subscribed S-NSSAI / DNNs (also provisioned as part of the policy data in the UDR).

[0201] FIG. 5B is an exemplary call flow diagram illustrating a UDM-based early approval procedure.

[0202] FIG. 5B shows an exemplary solution for enabling the NEF to perform early authorization (step 2b in FIG. 5A) to immediately reject a request when service-specific information is not approved for a UE or a group of UEs.

[0203] This solution can be used as a general procedure for initial validation / approval for other service specific information requests by the AF, e.g., service specific parameter provisioning, URSP, SAR (Service Area Restrictions) and traffic steering policies that require PCF policy evaluation.

[0204] As shown in FIG. 5B, the AF may send "Nnef_service_specific_create" (including UE-ID, Service Specific Info) to the NEF to trigger such a procedure for early service-specific authorization.

[0205] The NEF confirms that the AF is authorized to call the API with the requested service-specific parameters. So In this case, the NEF requests further early authorization for a specific UE or UE group from the UDM by sending “Nudm_Service_Specific_Aothorization” (including UE-ID, Service Specific Info).

[0206] If the service is authorized for the particular UE(s) including all additional parameters required by the AF, the UDM returns a success response which may include a validity time. The authorization expires when the validity time is reached. This forces a re-authorization (e.g. initiated by the NEF or AF) to ensure that the service specific information is still authorized.

[0207] The NEF may receive a "Nudm_Service_Specific_Authorization_Response" from the UDM. The acknowledgement may include the indication "OK" and a validity time.

[0208] Then, the NEF operates according to the flow (similar to FIG. 5B, see Solution #1, step 3) and stores the service-specific information in the UDR.

[0209] The NEF can respond to the AF with assurance that the request is indeed authorized for a specific UE(s) by sending an "Nnef_service_specific_create_response".

[0210] It should be understood that the terminology / names for the new messages are merely examples and not limiting.

[0211] As an alternative solution, the NEF could contact the PCF and have the PCF perform the early authorization instead of the UDM (the subscribed DNN / S-NSSAI is also part of the policy data). However, since the UDM currently performs per-UE authorization for other publishing functions (e.g., event publishing, NIDD (non-IP data delivery), parameter provisioning), the UDM may be preferable in terms of consistency in centralizing the authorization in a single NF rather than performing it in various NFs upon AF requests. Furthermore, the PCF is contacted later, when informed by the UDR. Thus, the involvement of the same NF twice (early and late) for the same procedure may lead to a solution where the NEF stores service-specific information directly in the UDR instead of via the PCF, and the PCF ensures that the information stored in the UDR is properly authorized.

[0212] Another, less preferred but still applicable, embodiment is for the NEF to reuse the existing UDM SDM (Subscriber Data Management) service to obtain the DNN / NSSAI. However, there is a lot of AM data in the same resource that is not of interest to the NEF (e.g. RAT (Radio Access Technology) restrictions, UPU (UE Parameter Update) information, SOR (Steering of Roaming) information, timers, etc.), which would require adaptation in the SDM anyway. Furthermore, and more importantly, it does not address per-UE service authorization (prior to consistent DNN / NSSAI checking). That is, a UE may have a proper DNN / NSSAI, but may not be authorized to use this service by the AF (in this case it is the URSP rule, but the existing NIDD may fall into this general procedure, since the DNN by the NEF / AF must also match the subscription data), or the UE may be authorized for the service invoked by the AF (e.g. URSP change) but not for the AF / MTC provider it requests. The Nudm_SDM service is not intended or capable of doing this.

[0213] The embodiments of the present disclosure provide a general procedure for early verification / authorization that can be reused for current and / or future service-specific information requests by AFs that require PCF policy evaluation, e.g., URSP, SAR (Service Area Restriction). Before contacting the PCF / UDR, the NEF may request authorization per subscriber based on different levels (service, DNN / NSSAI), so that the AF is responded with an appropriate response (either OK or "request forbidden"), saving resources / signaling in the 5GC network and providing the AF with a reliable response immediately.

[0214] The UDM can further verify that management of the requested UE group (or any UE) is authorized for the requesting AF / MTC provider, and possibly that the DNN / NSSAI (in this particular case; service dependent) is also applicable for that group.

[0215] It may be the operator's task to ensure that the provisioned information for both the group of UEs and the individual UE members is consistent, e.g., all UEs in a group have DNN / NSSAI applicable / authorized for the group.

[0216] FIG. 6 is an exemplary call flow diagram for providing a configuration for providing a service to a terminal device according to an embodiment of the present disclosure.

[0217] Step 2b may be an extension step of the existing 3GPP R16 service parameter provisioning procedure. Furthermore, the procedure may be enhanced by using new parameters in the existing steps.

[0218] Step 1 shows the creation of an AF request by the AF / AS (Application Function / Application Server).

[0219] Step 2 shows that the AF calls the enhanced NEF service API (i.e., Nnef_ServiceParameter_create) service operation to create a new request and sends the request to the NEF. The request may contain the following information: 1) Service description DNN + S-NSSAI combination, AF service identifier, application identifier. 2) Target UE or group of UEs (one or more) GPSI, UE IPv4 / IPv6 / MAC address, UE group ID, optional UE ID. 3) Service parameters UE route policy (traffic descriptor, application / domain descriptor, location / time conditions, etc.).

[0220] Steps 2a-1 and 2a-2 show that the NEF authorizes the AF based on local SLA (Service Level Agreement) policy (partner managed), and the NEF translates the external UE ID or group ID into an internal ID through the UDM service.

[0221] Step 2b (extension step) shows that the NEF uses the extended UDM service to verify that the S-NSSAI / DNN and other service information received from the AF belongs to the list of subscribed / authorized S-NSSAI / DNN and services in the UDM subscription data (see Figure 5). If the authorization fails (e.g., if the DNN is not subscribed for the UE, if the UE does not allow the AF or such specific AF to dynamically change the URSP rules), the UDM returns a negative response to the AF, which is mapped to an HTTP 403 response (forbidden). In this way, the AF is informed that it should not attempt the request until the conditions change (e.g., until the UE allows such AF to affect the URSP rules).

[0222] Step 3 shows that the NEF stores the AF request information, along with the assigned transaction reference ID, in the UDR as part of the application data.

[0223] Step 4 shows the NEF response to AF after storing the AF request data in the UDR.

[0224] Step 5 shows that the (one or more) PCFs receive Nudr_DM_Notify notifications of data changes from the UDR when the UE is registered with the network and the PCF has subscribed for notifications of data changed in the UDR by invoking Nudr_DM_Subscribe (AF Service Parameter Provisioning Information (SUPI)).

[0225] Step 6 indicates that the PCF initiates UE policy delivery as specified in 3GPP TS 23.502 V16.6.0 subclause 4.2.4.3. If the PCF is notified of UE policy delivery failure, it may subscribe to the "Connectivity State Change (IDLE or CONNECTED)" event as specified in subclause 5.2.2.3.

[0226] In such a specific implementation, advantages of the embodiments of the present disclosure include introducing a method to enhance early approval and validation of AF infuenced URSP changes (and other service-specific AF requests) and exposing such capabilities to third-party applications, allowing enterprise service providers to control end-user slice tenant utilization and further improve slice utilization efficiency. An optimized procedure for AF-infuenced PCF determination for URSPs may be provided.

[0227] FIG. 7A is a block diagram illustrating an apparatus for a first network function, a second network function, and a third network function according to an embodiment of the present disclosure.

[0228] As shown in Figure 7A, the first / second / third network function 200 / 300 / 400 may have one or more processors 701 / 703 / 705 and one or more memories 702 / 704 / 706 having computer program code. The one or more memories and the computer program code may be configured to cause the first / second / third network function 200 / 300 / 400, using the one or more processors, to perform at least a method according to any one of the above-mentioned embodiments as shown in Figures 2 to 4.

[0229] For example, the first network function 200 is configured to at least send a request to a second network function to provide at least one service parameter to a terminal device by the first network function, and receive a response from the second network function as to whether the request has been approved.

[0230] In another example, the first network function 200 may be caused to at least send a request to a second network function to provide at least one service parameter to a UE or group of UEs, and receive a response from the second network function as to whether the request is approved.

[0231] For example, the second network function is configured to at least receive a request from the first network function to provide at least one service parameter to the terminal equipment by the first network function, and to send a response to the first network function as to whether the request has been approved.

[0232] In another example, the second network function may be caused to at least receive from the first network function a first request to provide at least one service parameter to the UE or group of UEs, send a second request to a third network function requesting whether the first network function is authorized to provide the at least one service parameter to the UE or group of UEs, receive a response to the second request from the third network function indicating the result of the authorization, and send a response to the first network function as to whether the first request was approved.

[0233] For example, the third network function is configured to at least receive a request from the second network function to provide at least one service parameter to the terminal equipment by the first network function, and to send a response to the second network function as to whether the request has been approved.

[0234] In another example, the third network function may be configured to at least receive a request from the second network function to provide whether the first network function is authorized to provide at least one service parameter to a UE or group of UEs, and to send a response to the second network function indicating the result of the authorization.

[0235] Processors 701, 703, 705 may be any type of processing component, such as one or more microprocessors or microcontrollers, as well as other digital hardware such as digital signal processors (DSPs), dedicated digital logic, etc. Memory 702, 704, 706 may be any type of storage component, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc.

[0236] FIG. 7B is a block diagram illustrating a computer-readable storage medium according to an embodiment of the present disclosure.

[0237] As shown in Figure 7B, computer readable medium 700 may have computer program code embodied therein for use with first network function / second network function / short message service function 707. Computer program code 707 may have code for performing any of the methods described above, such as those shown in Figures 2-4.

[0238] For example, the computer program code 707 may have code for the first network function 200 , the second network function 300 , or the third network function 400 .

[0239] The computer readable storage medium 700 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive.

[0240] FIG. 8A is a schematic diagram illustrating units of an apparatus for a first network function according to an embodiment of the present disclosure.

[0241] As shown in FIG. 8A, for example, the apparatus 200 for a first network function may have a transmitting unit 8001 configured to transmit a request to a second network function to request that the first network function provide at least one service parameter to a terminal device, and a receiving unit 8002 configured to receive a response from the second network function regarding whether the request has been approved or not.

[0242] In another example, the sending unit 8001 may be configured to send a request to a second network function to provide at least one service parameter to a user equipment (UE) or a group of UEs, and the receiving unit 8002 may be configured to receive a response from the second network function regarding whether the request is granted or not.

[0243] FIG. 8B is a schematic diagram illustrating units of an apparatus for a second network function according to an embodiment of the present disclosure.

[0244] For example, as shown in FIG. 8B, the apparatus 300 for the second network function may have a receiving unit 8003 configured to receive a request from the first network function to provide at least one service parameter to the terminal equipment by the first network function, and a transmitting unit 8004 configured to transmit a response to the first network function regarding whether the request has been approved or not.

[0245] In another example, the receiving unit 8003 may be configured to receive a first request from a first network function to provide at least one service parameter to the UE or group of UEs. The transmitting unit 8004 may be configured to transmit a second request to a third network function to request whether the first network function is authorized to provide at least one service parameter to the UE or group of UEs. The receiving unit 8003 may be configured to receive a response to the second request from the third network function indicating a result of the authorization. The transmitting unit 8004 may be configured to transmit the response to the first network function regarding whether the first request is authorized or not.

[0246] FIG. 8C is a schematic diagram illustrating units of an apparatus for a third network function according to an embodiment of the present disclosure.

[0247] For example, as shown in FIG. 8C , the apparatus 400 for a third network function may have a receiving unit 8005 configured to receive a request from the second network function to provide at least one service parameter to a terminal device by the first network function, and a transmitting unit 8006 configured to transmit a response to the second network function regarding whether the request has been approved or not.

[0248] In another example, the receiving unit 8005 may be configured to receive a request to provide whether the first network function is authorized to provide at least one service parameter to the UE or group of UEs, and the sending unit 8006 may be configured to send a response indicating the result of the authorization to the second network function.

[0249] The term "unit" may have its conventional meaning in the electronics, electric equipment, and / or electronics fields and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logic semiconductor and / or discrete devices, computer programs or instructions, etc. for performing a respective task, procedure, computation, output, and / or display function, such as those described in this disclosure.

[0250] These units allow the first network function 200, the second network function 300, and / or the third network function 400 to arrange any computing and storage resources from at least one network function / node / device / entity / apparatus in the communication system without requiring a fixed processor or memory. Virtualization technology and network computing technology can be introduced to improve the utilization efficiency of network resources and the flexibility of the network.

[0251] Exemplary embodiments of the present disclosure may further provide a method implemented in a communication system.

[0252] According to an embodiment of the present disclosure, there is provided a method implemented in a communication system that may include a host computer, a base station, and a UE. The method may include providing user data at the host computer. Optionally, the method may include initiating a transmission at the host computer carrying the user data to the UE over a cellular network having the base station.

[0253] According to an embodiment of the present disclosure, a communication system is provided that includes a host computer. The host computer may have a processing circuit configured to provide user data and a communication interface configured to transfer the user data to a cellular network for transmission to a UE. The cellular network may have a base station having a wireless interface and the processing circuit.

[0254] According to an embodiment of the present disclosure, a communication system is provided that includes a host computer. The host computer may have a processing circuit configured to provide user data and a communication interface configured to transfer the user data to a cellular network for transmission to a UE. The UE may have a wireless interface and a processing circuit.

[0255] According to an embodiment of the present disclosure, there is provided a method implemented in a communication system that may include a host computer, a base station, and a UE. The method may include receiving, at the host computer, user data transmitted from the UE to the base station.

[0256] According to an embodiment of the present disclosure, there is provided a communication system including a host computer. The host computer may have a communication interface configured to receive user data originating from a transmission from a UE to a base station. The UE may have a wireless interface and a processing circuit.

[0257] According to an embodiment of the present disclosure, there is provided a method implemented in a communication system that may include a host computer, a base station, and a UE, The method may include receiving, at the host computer, user data from the base station originating from a transmission received by the base station from the UE.

[0258] According to an embodiment of the present disclosure, a communication system is provided that may include a host computer. The host computer may have a communication interface configured to receive user data originating from a transmission from a UE to a base station. The base station may have a wireless interface and processing circuitry.

[0259] FIG. 9 is a block diagram illustrating a telecommunications network connected to a host computer through an intermediate network in accordance with some embodiments of the present disclosure.

[0260] Referring to Fig. 9, according to an embodiment, a communication system includes a telecommunications network 910, such as a 3GPP type cellular network, consisting of an access network 911, such as a wireless access network, and a core network 914. The access network 911 has a number of base stations 912a, 912b, 912c, such as NBs, eNBs, gNBs, or other types of wireless access points, each of which defines a corresponding coverage area 913a, 913b, 913c. Each base station 912a, 912b, 912c can be connected to the core network 914 using a wired or wireless connection 915. A first UE 991 located in the coverage area 913c is configured to wirelessly connect to or be paged by the corresponding base station 912c. A second UE 992 in the coverage area 913a can be wirelessly connected to the corresponding base station 912a. Although multiple UEs 991, 992 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is within the coverage area or is connected to a corresponding base station 912.

[0261] The telecommunications network 910 is itself connected to a host computer 930, which may be implemented in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 930 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connections 921 and 922 between the telecommunications network 910 and the host computer 930 may extend directly from the core network 914 to the host computer 930, or may go through an optional intermediate network 920. The intermediate network 920 may be one or a combination of two or more of a public network, a private network, a hosted network, and if present, the intermediate network 920 may be a backbone network or the Internet, and in particular the intermediate network 920 may have two or more sub-networks (not shown).

[0262] The communication system of FIG. 9 generally provides connectivity between connected UEs 991, 992 and a host computer 930. This connectivity may be described as an over-the-top (OTT) connection 950. The host computer 930 and connected UEs 991, 992 are configured to communicate data and / or signaling over the OTT connection 950 using the access network 911, the core network 914, any intermediate networks 920, and possibly further infrastructure (not shown) as intermediaries. The OTT connection 950 may be transparent in the sense that participating communication devices through which the OTT connection 950 passes are unaware of the routing of uplink and downlink communications. For example, the base station 912 will not be informed or need to be informed of past routing of inbound downlink communications with data originating from the host computer 930 being forwarded (e.g., handed over) to the connected UE 991. Similarly, the base station 912 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 991 towards the host computer 930 .

[0263] FIG. 10 is a block diagram illustrating a host computer communicating with a UE via a base station over a partially wireless connection in accordance with some embodiments of the disclosure.

[0264] An exemplary implementation of the UE, base station, and host computer discussed in the previous paragraphs according to one embodiment is described with reference to FIG. 10. In the communication system 1000, the host computer 1010 has hardware 1015 including a communication interface 1016 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 1000. The host computer 1010 further has a processing circuit 1018 that may have storage and / or processing capabilities. In particular, the processing circuit 1018 may have one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) configured to execute instructions. The host computer 1010 further has software 1011 stored in the host computer 1010 or accessible by the host computer 1610 and executable by the processing circuit 1018. The software 1011 includes a host application 1012. The host application 1012 may be operable to provide services to a remote user, such as the UE 1030, that connects via an OTT connection 1050 that terminates at the UE 830 and the host computer 1010. In providing services to the remote user, the host application 1012 may provide user data that is transmitted using the OTT connection 1050.

[0265] The communication system 1000 further includes a base station 1020 provided in the communication system, the base station 1020 having hardware 1025 enabling communication with the host computer 1010 and the UE 1030. The hardware 1025 may include a communication interface 1026 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 1000, as well as a wireless interface 1027 for setting up and maintaining at least a wireless connection 1070 with a UE 1030 located within a coverage area (not shown in FIG. 10) served by the base station 1020. The communication interface 1026 may be configured to facilitate a connection 1060 to the host computer 1010. The connection 1060 may be direct or may go through a core network (not shown in FIG. 10) of the telecommunications system and / or through one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1025 of the base station 1020 further includes processing circuitry 1028, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) configured to execute instructions. The base station 1020 also has software 1021 stored internally or accessible via an external connection.

[0266] The communication system 1000 further includes the UE 1030 already mentioned. Its hardware 1035 may include a wireless interface 1037 configured to set up and maintain a wireless connection 1070 with a base station serving the coverage area in which the UE 1030 is currently located. The hardware 1035 of the UE 1030 further includes a processing circuit 1038, which may have one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) configured to execute instructions. The UE 1030 further includes software 1031 stored in or accessible by the UE 1030 and executable by the processing circuit 1038. The software 1031 includes a client application 1032. The client application 1032 is operable to provide services to a human or non-human user via the UE 1030 with the support of the host computer 1010. At the host computer 1010, an executing host application 1012 can communicate with an executing client application 1032 via the UE 1030 and an OTT connection 1050 that terminates at the host computer 1010. In providing services to a user, the client application 1032 may receive request data from the host application 1012 and provide user data in response to the request data. The OTT connection 1050 can transfer both the request data and the user data. The client application 1032 can interact with the user and generate the user data to provide.

[0267] It should be noted that the host computer 1010, base station 1020, and UE 1030 shown in Figure 10 may be similar to or identical to the host computer 930, one of the base stations 912a, 912b, 912c, and one of the UEs 991, 992, respectively, of Figure 9. That is, the internal operation of these entities may be similar to that shown in Figure 10, and independently, the surrounding network topology may be as shown in Figure 9.

[0268] 10, the OTT connection 1050 is depicted abstractly to illustrate communication between the host computer 1010 and the UE 1030 via the base station 1020, without explicitly showing intermediate devices or the exact routing of messages through these devices. The network infrastructure may make routing decisions that may be configured to be hidden from the UE 1030, or from the host computer 1010 operated by the service provider, or both. The network infrastructure may further make decisions to dynamically change the routing while the OTT connection 1050 is active (e.g., based on load balancing considerations or network reconfiguration).

[0269] The wireless connection 1070 between the UE 1030 and the base station 1020 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 1030 using the OTT connection 1050 of which the wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve latency and power consumption, thereby providing advantages such as lower complexity, reduced time required to access a cell, better responsiveness, extended battery life, etc.

[0270] Measurement procedures may be provided to monitor data rates, latency, and other network operation aspects that one or more embodiments improve. Additionally, there may be optional network functionality to reconfigure the OTT connection 1050 between the host computer 1010 and the UE 1030 in response to variations in the measurement results. The measurement procedures and / or network functionality to reconfigure the OTT connection 1050 may be implemented in the software 1011 and hardware 1015 of the host computer 1010, or in the software 1031 and hardware 1035 of the UE 1030, or both. In some embodiments, sensors (not shown) may be provided in or associated with the communication equipment through which the OTT connection 1050 passes, and may participate in the measurement procedures by providing values ​​of the above-exemplified monitored quantities, or other physical quantities from which the software 1011, 1031 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1050 may include message formats, retransmission settings, priority routing, and the like. The reconfiguration need not impact the base station 1020 and may be unknown or imperceptible to the base station 1020. Such procedures and functions would be known and practiced in the art. In a particular embodiment, the measurements may involve dedicated UE signaling that facilitates the host computer 1010 measurements of throughput, propagation time, delay, etc. The measurements may be performed by having the OTT connection 1050 send messages, particularly empty or "dummy" messages, while the software 1011 and 1031 monitor propagation times, errors, etc.

[0271] FIG. 11 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with respect to FIG. 9 and FIG. 10. To simplify the disclosure, only drawing references to FIG. 11 are included in this section. In step 1110, the host computer provides user data. In sub-step 1111 of step 1110 (which may be optional), the host computer provides the user data by executing a host application. In step 1120, the host computer initiates a transmission carrying the user data to the UE. In step 1130 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In step 1140 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0272] FIG. 12 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with respect to FIG. 9 and FIG. 10. To simplify the disclosure, only drawing references to FIG. 12 are included in this section. In method step 1210, the host computer provides user data. In an optional substep (not shown), the host computer provides the user data by executing a host application. In step 1220, the host computer initiates a transmission carrying the user data to the UE. The transmission may be passed through the base station according to the teachings of the embodiments described throughout this disclosure. In step 1230 (which may be optional), the UE receives the user data carried in the transmission.

[0273] FIG. 13 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with respect to FIG. 9 and FIG. 10. To simplify the disclosure, only drawing references to FIG. 13 are included in this section. In step 1310 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data. In substep 1321 (which may be optional) of step 1320, the UE provides the user data by executing a client application. In substep 1311 (which may be optional) of step 1310, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from a user. Regardless of the specific manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in substep 1330 (which may be optional). At method step 1340, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0274] FIG. 14 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with respect to FIG. 9 and FIG. 10. To simplify the disclosure, only a drawing reference to FIG. 14 is included in this section. In step 1410 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1420 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1430 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0275] In general, various exemplary embodiments of the present disclosure may be implemented by hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but the present disclosure is not limited thereto. Although various aspects of the exemplary embodiments of the present disclosure may be illustrated and described using block diagrams, flow charts, or some other visual representations, it is understood that these blocks, devices, systems, techniques, or methods described herein may be implemented, as non-limiting examples, in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0276] It should therefore be understood that at least some aspects of the exemplary embodiments of the present disclosure may be embodied in a variety of components, such as integrated circuit chips and modules. It will therefore be understood that the exemplary embodiments of the present disclosure may be realized in an apparatus embodied as an integrated circuit, which may include circuitry (and possibly firmware) for implementing at least one of a data processor, a digital signal processor, a baseband circuit, and a radio frequency circuit that may be configurable to operate in accordance with the exemplary embodiments of the present disclosure.

[0277] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure may be implemented in computer-executable instructions, such as one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer-executable instructions may be stored on a computer-readable medium, such as a hard disk, an optical disk, a removable storage medium, a semiconductor memory, a RAM, etc. As will be appreciated by those skilled in the art, the functionality of the program modules may be combined or distributed as desired in various embodiments. Furthermore, the functionality may be implemented in whole or in part in firmware or hardware equivalents, such as integrated circuits, field programmable gate arrays (FPGAs), etc.

[0278] The present disclosure includes any novel feature or combination of features expressly disclosed herein, or any generalized form thereof. Various modifications and adaptations to the foregoing exemplary embodiments of the present disclosure will become apparent to those skilled in the relevant art in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure. Claims

Claims

1. A method performed by a first network function for early service-specific admission, comprising: Sending a request to a second network function for providing at least one service parameter to a user equipment (UE) or a group of UEs (S201); receiving a response from the second network function as to whether the request was approved (S202); The at least one service parameter is The identity of the service provider; and / or service-related data that is part of subscription data for the UE or group of UEs; A method, wherein the service-related data includes slicing information and / or a data network name (DNN) and / or single network slice selection assistance information (S-NSSAI). receiving (S202) a response from the second network function as to whether the request has been approved, The method of claim 1 , further comprising receiving a response that the request is approved based on the at least one service parameter belonging to subscription data in a third network function.

3. The method of claim 2, wherein the third network function includes a unified data management (UDM).

4. The method according to claim 1 , wherein the response includes a validity time of the at least one service parameter.

5. The at least one service parameter is Service identification information; and / or The method of claim 1 , further comprising: an identification of the UE or a group of the UEs.

6. 6. The method of claim 5, wherein the service identity is associated with one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF-influenced traffic routing, or service specific parameter provisioning, or service area restriction, or a traffic steering policy requiring PCF policy evaluation. receiving (S202) a response from the second network function as to whether the request has been approved, The method of claim 5 or 6, comprising receiving a response that the request is approved based on the service indicated by the service identification information being approved for the UE or group of UEs and / or if the service-related data includes a DNN and / or S-NSSAI belonging to a list of subscribed DNNs and / or S-NSSAIs.

8. A method according to any one of claims 1 to 7, wherein the service provider includes an AF or a machine type communications (MTC) provider.

9. the first network function comprises an Application Function (AF); and / or 9. The method of claim 1, wherein the second network function comprises a network exposure function (NEF).

10. A method performed by a second network function for early service-specific admission, comprising: Receiving a first request from a first network function to provide at least one service parameter to a UE or a group of UEs (S307); sending a second request to a third network function requesting whether the first network function is authorized to provide the at least one service parameter to the UE or the group of UEs (S308); receiving a response to the second request from the third network function indicating an approval result (S309); and sending a response to the first network function as to whether the first request was approved (S310); The at least one service parameter is The identity of the service provider; and / or service-related data that is part of subscription data for the UE or group of UEs; A method, wherein the service-related data includes slicing information and / or a data network name (DNN) and / or single network slice selection assistance information (S-NSSAI).

11. The method described in claim 10, wherein the response to the second request indicating an approval result includes a result that the second request is approved, and the response regarding whether the first request is approved includes a result that the first request is approved, both of which are based on the at least one service parameter belonging to subscription data within the third network function.

12. The method of claim 10 or 11, wherein the third network function includes a unified data management (UDM).

13. A method according to any one of claims 10 to 12, wherein the response to the first request and / or the response to the second request includes a validity time of at least one service parameter.

14. 14. The method according to claim 10, further comprising storing the at least one service parameter in a fourth network function if the first request and / or the second request is approved.

15. The method of claim 14, wherein the fourth network function includes a unified data repository (UDR).

16. 16. A method according to claim 14 or 15, wherein the fourth network function informs a fifth network function regarding the at least one service parameter.

17. The method of claim 16 , wherein the fifth network function comprises a Policy Control Function (PCF).

18. The at least one service parameter: Service identification information, and / or 18. The method of claim 10, further comprising an identity of the UE or a group of the UEs.

19. The service identity is associated with one of a UE Route Selection Policy (URSP), or an AF session with QoS, or AF-influenced traffic routing, or service specific parameter provisioning, or service area restriction, or a traffic steering policy requiring PCF policy evaluation; and / or The method of claim 18 , wherein the service provider comprises an AF or a machine type communications (MTC) provider.

20. The method described in claim 19, wherein the response to the second request indicating an approval result includes a result that the second request is approved, and the response regarding whether the first request is approved or not includes a result that the first request is approved, both of which are based on the service indicated by the service identification information being approved for the UE or a group of UEs, and / or the service-related data including a DNN and / or S-NSSAI belonging to a list of subscribed DNNs and / or S-NSSAIs.

21. A first network function (200), One or more processors (701); one or more memories (702) having computer program code therein; A first network function (200), wherein the one or more memories and the computer program code, together with the one or more processors, are configured to cause the first network function to perform the method of any one of claims 1 to 9.

22. A second network function (300), One or more processors (703); one or more memories (704) having computer program code therein; A second network function (300), wherein the one or more memories and the computer program code, together with the one or more processors, are configured to cause the second network function to perform the method of any one of claims 10 to 20.

Images