Method and system for network slice charging

By not using AppID in the wireless communication system, using network slicing and user data usage for billing, the problem of poor user privacy exposure and billing management is solved, and flexible and accurate billing management is achieved.

CN118923084APending Publication Date: 2024-11-08APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093885.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-03-24
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

When billing for application providers, the use of application identifiers (AppIDs) may expose user privacy, and there are difficulties in managing billing for different application versions and platforms, affecting the flexibility of network slicing.

Method used

By not using AppID as a mandatory field in the traffic descriptor, using network slicing and user data usage to generate billing information, the network service provider can independently of the application provider's data exchange amount, according to the service level of each user Protocol and data usage are billed.

Benefits of technology

Effectively protect user privacy, improve the flexibility of network slicing management and billing accuracy, avoid the deployment challenges brought about by specific billing for each application, and achieve flexibility between users and application providers Service level agreement management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923084A_ABST
    Figure CN118923084A_ABST
Patent Text Reader

Abstract

A web application server comprising communication circuitry and at least one processor is disclosed. The at least one processor is configured to receive, from a plurality of user equipments (UEs) and via the communication circuitry, a plurality of requests to receive service data from a plurality of application providers; determining an amount of service data exchanged between an application provider and a group of UEs of the plurality of UEs requesting service data over the one or more network slices; generating first charging information corresponding to the application provider according to a criterion including an amount of service data exchanged with the application provider through the one or more network slices; and generating second charging information corresponding to each UE in the group of UEs according to the data use condition of each UE in the group of UEs independent of the characteristics of the one or more network slices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments described herein generally relate to methods and systems that enable network providers to bill application providers. Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to send data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLANs) (commonly referred to as Wi-Fi within industry organizations). ® ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to communicate between base stations of the RAN (which may also sometimes be referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices referred to as user equipment (UE). The 3GPP RAN may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) for communication between base stations and UEs. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to as 5G RAT, 5G NR RAT, or NR in this document). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.

[0005] The base stations used by the RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also often denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (also sometimes referred to as a gNodeB or gNB).

[0006] The RAN provides communication services together with external entities through its connection with the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core Network (EPC), while NG-RAN may utilize the 5G Core Network (5GC). BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0008] Figure 1 An example environment is depicted in which the embodiments described herein may be practiced.

[0009] Figure 2 Depicts an example network interface diagram of a network in which embodiments described herein may be practiced.

[0010] Figure 3 Depicted is an example flow diagram illustrating the exchange of events between various 5G functions according to some embodiments.

[0011] Figure 4 Depicted is a flow diagram of operations for generating billing information for an application provider and a plurality of user equipments (UEs) in accordance with some embodiments.

[0012] Figure 5 A flowchart of operations for generating billing information for an application provider according to some embodiments is depicted.

[0013] Figure 6 A flowchart of operations for generating billing information for an application provider according to some embodiments is depicted.

[0014] Figure 7 Depicted is an example architecture of a wireless communication system in a cellular carrier domain according to embodiments disclosed herein.

[0015] Figure 8 A system for performing signaling between a UE and a network device according to embodiments disclosed herein is depicted. DETAILED DESCRIPTION

[0016] Reference will now be made specifically to the representative embodiments / aspects shown in the accompanying drawings. It should be understood that the following description is not intended to limit the embodiments to a preferred embodiment. On the contrary, it is intended to cover alternatives, modifications and equivalent forms that may be included in the spirit and scope of the embodiments defined by the appended claims.

[0017] Embodiments described herein include methods and systems for generating billing information for an application provider and / or multiple user equipment (UE) for data exchanged between the UE and the application provider via a core network and a radio access network (RAN). When a user requests data from an application provider using an application executed on one of multiple UEs, the user's request is routed to the application provider according to a UE routing policy (URSP). The URSP includes a traffic descriptor, which may include an application identifier (AppID). The AppID identifies a specific application that the user is using on the UE. Therefore, when the AppID is used to identify data exchanged between the application provider and the UE through a network service provider, and is used to bill the application provider for data exchanged with multiple UEs through one or more network slices, the user's privacy may be at risk.

[0018] The network service provider may provide one or more network slices for the application provider to provide application data to the UE. The network service provider may allocate necessary resources to each network slice according to the service level agreement with multiple users and / or other criteria, including but not limited to the number of users who expect to request data from the application provider, the type of data requested by the multiple users (such as audio, video, etc.), latency, throughput, etc. The network service provider may then charge the application provider for the services provided by using the network slices.

[0019] A UE may be allocated one of the one or more network slices allocated by the network service provider for the UE to request services and / or data from the application provider. The UE may use the allocated network slice to request services and / or data from the application provider to exchange data with the application provider. The UE may select a network slice according to a URSP rule configured at the UE. As described herein, the URSP rule includes a traffic descriptor, which may be one or more instances of an AppID, an IP 3-tuple as described in 3GPP TS25.503, a non-IP descriptor, and / or a data network name.

[0020] As described herein, according to some embodiments, and as a non-limiting example, a network service provider may bill users of UEs at the granularity of a protocol data unit (PDU) session, a service flow, a quality of service (QoS) flow, and the network service provider may bill an application provider for one or more network slices used to provide services and / or data to multiple UEs according to the total amount of data (e.g., service data) exchanged with the application provider.

[0021] In one example, the total amount of data exchanged with the application provider may be measured at an application server of the core network of the service provider. As described herein, according to some embodiments, when measuring the total amount of data exchanged between the application provider and multiple UEs, the applications used by the UEs identified by the AppID in the traffic descriptor may not be required.

[0022] As described herein, when AppID is used to bill an application provider for services and / or data exchanged using one or more network slices provided to the application provider by a network service provider, the user's privacy may be at risk. In addition, selecting a network slice by AppID may affect the flexibility of network slice management. For example, two different applications that provide similar types of services may not use the same instance of a network slice because it would be difficult to bill for a specific application for each network slice. In addition, depending on the specific type of data requested by the user and / or based on the geographic location of the user requesting the service and / or data from the application provider, the application provider may use different backend services to provide the service. In addition, different versions of an application may provide different capabilities, but may still have the same AppID on all versions of the application and / or on different platforms or application stores. Therefore, using an AppID included in a traffic descriptor may not only put the user's privacy at risk, but may also bring various deployment challenges to billing the application provider by AppID.

[0023] As described herein, each data packet exchanged between the UE and the application provider may include a network slice identifier and an AppID. Therefore, the network service provider may bill the application provider using the AppID and the network slice identifier included in each data packet exchanged using the network of the network service provider. However, various embodiments as described herein may provide a technical solution for billing the application provider without using the AppID as a mandatory field in the traffic descriptor (and thereby putting the user's privacy at risk). Therefore, the AppID may not be required to properly bill the application provider, and the AppID may not be required at all.

[0024] Figure 1 Depicts an example environment in which the embodiments described herein may be practiced. Figure 1As shown, a plurality of UEs, such as UE1 102, UE2 104, and UE3 106, may be communicatively coupled to a core network 116 of a network service provider via a base station 114 (e.g., eNodeB, eNB, gNB, access point (AP)) in a radio access network (RAN) using one or more radio access technologies, such as 5G, long term evolution (LTE), etc. The network service provider may also be communicatively coupled to a plurality of application servers of one or more application providers, such as application server 1 118, application server 2 120, etc.

[0025] In some embodiments, as described herein, a network service provider may allocate one or more network slices in accordance with a service level agreement with one or more application providers to provide services and / or data from one or more application providers' application servers 1 118 and / or application servers 2 120 to UE1 102, UE2 104, and / or UE3 106. For example, a first network slice 108, a second network slice 110, and a third network slice 112 may be selected by UE1 102, UE2 104, and UE3 106, respectively, for requesting services and / or data from one or more application providers' application servers 1 118 and / or application servers 2 120. As a non-limiting example, in some embodiments, some or all of the UEs may select the same network slice to request services and / or data from application server 1 118, and some or all of the UEs may select the same network slice to request services and / or data from application server 2 120, although the network slice selected by the UE for requesting services and / or data from application server 1 118 may be different from the network slice selected by the UE for requesting services and / or data from application server 2 120. And thus, the identifier of the network slice may be used by the network service provider to determine the total amount of data exchanged between the application provider and a group of UEs, without any UE service and / or data request including the AppID traffic descriptor.

[0026] As described herein, each of UE1 102, UE2 104, and / or UE3 106 may select and use a particular network slice to send data to and / or receive data from one or more application providers. The particular network slice may be selected based on URSP rules configured at each UE, and an identification of the network slice may be included in each message, such as a request, and / or in data flowing between the UE and the one or more application providers.

[0027] However, as described herein, according to some embodiments, a network service provider may generate billing information for one or more application providers without including an AppID in a traffic descriptor according to URSP rules. The network service provider may determine, for example, the total amount of data exchanged with a particular application provider at a gateway of the network service provider. Thus, the network service provider may not rely on the AppID included in each packet sent between the particular application provider and the UE to generate billing information for the particular application provider; therefore, the UE no longer needs to include the AppID in its packets.

[0028] In addition, as described herein, according to some embodiments, a network service provider may generate billing information for each UE according to the data usage of each UE, rather than according to the data usage corresponding to the application being used by the user on the UE. The application provider may have a different service level agreement with each user of the UE, and may bill each user of the UE according to the service level agreement.

[0029] For example, a first user may have a premium account with an application provider for streaming high-definition (HD) quality video, and a second user may have a standard account with the application provider for streaming video in accordance with the available network bandwidth. However, as described herein, a network service provider may not need to consider the different service level agreements (SLAs) that each user may have with an application provider. Instead, an application provider may bill a user in accordance with the SLA between the user and the application provider.

[0030] In the present disclosure, network slicing is used to describe billing information generation performed by a network service provider corresponding to an application provider, but the various embodiments described herein may be applied to generate billing information when the network slice is not used to provide services and / or data between the UE and the application provider.

[0031] In some embodiments, and as a non-limiting example, the network service provider may generate billing information corresponding to the application provider in accordance with the SLA between the network service provider and the application provider. The SLA between the network service provider and the application provider may provide the generated billing information in accordance with the performance statistics. The performance statistics may be performance statistics of one or more network slices allocated by the network service provider to the application provider to enable it to provide services and / or data to multiple UEs. The performance statistics may include, but are not limited to, the total number of online or active users, the total number of connections, the total number of online sessions, latency, and throughput over a specific time period.

[0032] In some embodiments, and as a non-limiting example, a service level agreement between a network service provider and an application provider may provide billing information generated according to one or more attributes of one or more network slices allocated by the network service provider. The one or more attributes of one or more network slices may include, but are not limited to, a peak number of online or active users in a specific time period, a peak number of connections in a specific time period, a peak number of online sessions in a specific time period, and a type of service coverage, such as local, regional, global, and / or coverage area, etc.

[0033] In some embodiments, and as a non-limiting example, the service provider may generate billing information for each UE based on one or more of the number of PDU sessions created and / or activated by the UE, service data flows identifying a particular type of service or call flow, and QoS flows identifying the guaranteed quality of service (QoS), etc.

[0034] Figure 2 An example network interface diagram of a network in which embodiments described herein may be practiced is depicted. As described herein, a UE 202 receives services and / or data from an application provider's data network 206 using a network slice 204. Figure 2 As shown, the network slice 204 can thus create a pipeline for providing services and / or data communications between the application provider and the UE 202. The network slice 204 can extend through the radio access network (RAN) 208 and the service provider's core network, which can include various functional elements, such as a user plane function (UPF) 210. Figure 2 As shown, UPF 210 routes data from UE 202 to the application provider's data network 206 through RAN 208, and similarly routes data from the application provider's data network 206 to UE 202 through RAN 208. Figure 2 As shown, the RAN 208 and the UPF 210 may communicate using an N3 interface and the UPF 210 may communicate with the data network 206 using an N6 interface.

[0035] In addition, if Figure 2 As shown, the UE 202 and the RAN 208 (e.g., gNB, eNodeB, eNB, base station and / or access point) may communicate all connection and session related information through the 5G core access point and mobility management function (AMF) 212 using the N1 interface and the N2 interface, respectively. Thus, a connection from the UE 202 to the data network 206 may be established under the control of the AMF 212. The session management function (SMF) 214 may interact with the AMF 212 to establish, modify and / or release a PDU session through the Nsmf interface and the Namf interface.

[0036] The application provider may set the QoS requirements of the UE 202 in accordance with a service level agreement between the application provider and the UE 202 via the Naf interface with the application function (AF) 216 and via the Npcf interface with the policy charging function (PCF) 218. According to some embodiments, as described herein, the PCF 218 and the SMF 214 interact with a converged charging system (CCS) 220, which provides a charging function (CHF) 222 for generating charging or billing information.

[0037] In some embodiments, and as a non-limiting example, CCS 220 may include a charging gateway function (CGF) 224 that may generate charging records such as call detail records (CDRs) for transmission downstream, such as to a user of UE 202 and / or an application provider.

[0038] In some embodiments, services and / or data from a network service provider and / or application provider may be securely provided to the UE 202 via a network exposure function (NEF) 226 .

[0039] In some embodiments, when UE 202 requests services and / or data from an application provider, SMF 214 may select CHF 222 for generating charging information. CHF 222 may identify a charging-specific network repository function (NRF) for generating charging records and / or CDRs. SMF 214 may instruct CHF 222 to initiate charging information generation via an Nchf interface. Thus, a charging and operations support system (BOSS) may provide information such as allowed data usage limits to CHF 222 for generating charging information.

[0040] In some embodiments, as described herein, the SMF 214 that manages the establishment, modification, and / or release of PDU sessions for exchanging data with the UE 202 may provide the UPF 210 with information related to the service data flow and / or PDU session for each data packet.

[0041] like Figure 2 As shown, the UPF 210 connected to the data network 206 can monitor the total amount of data exchanged with the application provider. The UPF 210 can then report the monitored total amount of data exchanged with the application provider to the SMF 214 via the N4 interface. The SMF 214 can also report the monitored total amount of exchanged data received from the UPF 210 to the CCS 220 and / or CHF 222 for generating billing information for the application provider.

[0042] As described herein, SMF 214 can thus report the data usage of the UE independently of the total amount of data exchanged with the application provider. CHF 222 can generate charging information for UE 202 according to the data usage reported by SMF 214 for UE 202.

[0043] As described herein, for generating billing information for an application provider, an AppID is not required in the traffic descriptor to identify the application provider.

[0044] Figure 3 Depicted is an example flow diagram illustrating the exchange of events between various 5G functions according to some embodiments. Figure 3 As shown, a PDU session 318 may be established between the UE 302 and the UPF 312 for data transmission between the UE 302 and the data network of the application provider. As described herein, the PDU session 318 may be established in accordance with the QoS requirements set by the application provider at the AF 304 and the PCF 308. In addition, as described herein, the AF 304 and the SMF 310 may establish, modify and / or release PDU sessions, such as the PDU session 318, while the NEF 306 may open the UE 302 to the service provider's network for receiving services and / or data from one or more application providers.

[0045] like Figure 3 As shown, after establishing the PDU session 318, the AF 304 may send information identifying an application 320 used by the UE 302 to request services and / or data from an application provider to the NEF 306, and the NEF 306 may forward the information identifying the application 322 to the PCF 308 using the Nnef interface. The information identifying the application may include, but is not limited to, a data network access identifier (DNAI) identifying a location where one or more applications are deployed to provide services and / or data to the UE 302 via the PDU session 318.

[0046] Upon receiving the DNAI, PCF 308 may instruct SMF 310 to activate policy and charging control (PCC) rules 324. PCC rules provide instructions for processing specific data packets according to corresponding applications and / or service flows identified using the DNAI. SMF 310 may then activate rules 326 at UPF 312 to identify the amount of data exchanged with the data network of the application provider identified by the DNAI.

[0047] In some embodiments, as described herein, UPF 312 may separately monitor traffic from UE 302 and traffic to application provider 328. UPF 312, as a gateway to the data network of one or more application providers, may monitor the total amount of data exchanged with each of the one or more application providers. UPF 312 may report the monitored data usage of UE 302 and data exchanged with application provider 330 to SMF 310. SMF 310 may then separately report the monitored data usage of UE 302 and data exchanged with application provider 330 to CHF 314, as described herein. Figure 3 As shown in 332.

[0048] In some embodiments, CHF 314 may then generate billing information for the application provider and UE 302 based on the total amount of data exchanged with the application provider and as monitored at UPF 312, and may also generate billing information for UE 302 based on data usage by UE 302, as described herein. Figure 3 334 in FIG. 314. The CHF 314 may then send 336 the charging information generated for the application provider and / or UE 302 as a call detail record (CDR) to the CGF 316 for transmission to the user of the UE 302 and / or the application provider.

[0049] Figure 4 Depicted is a flow diagram of operations for generating billing information for an application provider and a plurality of user equipments (UEs) in accordance with some embodiments. Figure 4 The various operations described in the may be performed by a system such as a core network system of a service provider. The system may include at least one server that may implement various network functions, such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG, and / or CCS, etc., as described herein. The at least one server may include communication circuitry that may implement one or more interfaces corresponding to the various network functions described herein.

[0050] like Figure 4 As shown, at 402, multiple requests for receiving services and / or data from multiple application providers may be received from multiple user equipments (UEs) at at least one server via a communication circuit of at least one server. As described herein, each request from the multiple UEs may include DNAI information, which may identify a data network of one or more application providers from which services and / or information are requested. According to each of the multiple requests from the multiple UEs, data according to each request may be sent on multiple PDU sessions between the multiple UEs and one or more application providers of the multiple application providers.

[0051] As described herein, the SMF may instruct the UPF to monitor data exchanged with a data network of one or more application providers and to monitor data usage of each of the plurality of UEs. Thus, at 404, for example, at least one server implementing the UPF may determine the amount of data (e.g., service data) exchanged between an application provider among the plurality of application providers and a group of UEs among the plurality of UEs requesting service data from the one or more application providers. As described herein, a network service provider may allocate one or more network slices to one or more application providers to provide their services and / or data to the plurality of UEs.

[0052] As described herein, the UPF may then report to the SMF the data exchanged between one of the multiple application providers and a group of UEs in the multiple UEs requesting service data. The SMF may then report to the CHF the data exchanged between one of the multiple application providers and a group of UEs in the multiple UEs requesting service data from the application provider independently of data usage of each of the group of UEs.

[0053] At 406, for example, at least one server implementing CHF may generate charging information corresponding to the application provider for a group of UEs in the plurality of UEs according to a criterion including a total amount of service data exchanged with the application provider through one or more network slices. At 408, at least one server implementing CHF may also generate charging information corresponding to each UE in the group of UEs in the plurality of UEs according to data usage of each UE in the group of UEs.

[0054] As described herein, the generation of charging information for each UE is independent of the characteristics of the one or more network slices used to provide the requested service data. Thus, the charging information for each UE is generated according to its corresponding data usage, and the charging information for the application provider is generated without the AppID in the traffic descriptor of the URSP rule for the UE.

[0055] Figure 5 is a flow diagram of operations for generating billing information for an application provider as described herein, according to some embodiments. Figure 5 The various operations described in the specification may be performed by a network application server, which may be located, for example, in a core network of a network service provider. The network application server may implement various network functions, such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG, and / or CCS, as described herein. The network application server may include communication circuitry that may implement one or more interfaces corresponding to the various network functions described herein.

[0056] In some embodiments, and as a non-limiting example, the network application server as described herein can be a single instance of a network application server or multiple instances of a network application server. Multiple instances of the network application server can be co-located or geographically distributed over many locations, and each instance of the network application server can implement one or more network functions, such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG, and / or CCS, etc., as described herein.

[0057] like Figure 5 As shown, at 502, a plurality of requests to receive service data from a plurality of application providers may be received by a network application server from a plurality of user equipments (UEs). As described herein, each request from the plurality of UEs may include DNAI information that may identify a data network of each of the plurality of application providers from which services and / or information are requested. According to each of the plurality of requests from the plurality of UEs, the request data may be sent over a plurality of PDU sessions between the plurality of UEs and the plurality of application providers.

[0058] As described herein, the network application server as an SMF may instruct the UPF to monitor data exchanged with data networks of multiple application providers and monitor data usage of each of the multiple UEs. Thus, at 504, the network application server as the UPF may determine the amount of service data exchanged between an application provider among the multiple application providers and a group of UEs among the multiple UEs requesting service data from the application provider through one or more network slices.

[0059] As described herein, the UPF may then report to the SMF the data exchanged between one of the multiple application providers and a group of UEs in the multiple UEs requesting service data. The SMF may then report to the CHF the data exchanged between one of the multiple application providers and a group of UEs in the multiple UEs requesting service data from the application provider independently of data usage of each of the group of UEs. As a non-limiting example, the SMF and the CHF may be implemented by a network application server.

[0060] At 506, a network application server, such as a CHF, may generate charging information corresponding to the application provider according to a total amount of service data exchanged with the application provider through one or more network slices for a group of UEs in the plurality of UEs. As described herein, for generating the charging information corresponding to the application provider, it is not necessary to include an application identifier (AppID) in a traffic descriptor associated with a UE routing policy (URSP) for the UE.

[0061] Figure 6is a flow diagram of operations for generating billing information for an application provider as described herein, according to some embodiments. Figure 6 The various operations described in the may be performed by a converged billing system, which may be located, for example, in a core network of a network service provider. The converged billing system may implement various network functions, such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG, and / or CCS, as described herein. The converged billing system may include a processor, a memory, and a communication circuit, which is used to implement one or more interfaces corresponding to various network functions and to perform various network functions described herein.

[0062] like Figure 6 As shown, at 602, a server of a converged charging system, such as a UPF, may determine an amount of service data exchanged between an application provider among a plurality of application providers and a group of UEs among a plurality of UEs requesting service data through one or more network slices. At 604, the converged charging system, such as a UPF, may determine an amount of data usage of each UE in the group of UEs. As described herein, the UPF may determine an amount of service data exchanged between an application provider and a group of UEs according to one or more rules received from the SMF.

[0063] In some embodiments, another server of the converged charging system, such as CHF, may generate charging information corresponding to the application provider according to criteria including the amount of service data exchanged with the application provider through one or more network slices for the group of UEs in the plurality of UEs, and generate charging information corresponding to each UE in the group of UEs according to the amount of data usage of each UE in the group of UEs. As described herein, the generation of the charging information for each UE is independent of the characteristics of the one or more network slices used to provide the requested service data to the respective UE. Embodiments contemplated herein include an apparatus having a Figures 3 to 6 A component of one or more elements of a method or flow chart as shown. Figures 3 to 6 In the context of the method or flow chart shown, the apparatus may be, for example, an apparatus of a UE (such as the wireless device 802 as a UE, as described herein) or an application server or network application server (such as a wireless device 802) implementing one or more network functions (such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG and / or CCS, etc.). Figure 8 820 shown in FIG. 820 ).

[0064] Embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform Figures 3 to 6 One or more elements of a method or flow chart as shown. Figures 3 to 6 In the context of the illustrated method or flow chart, the non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 806 of a wireless device 802 that is a UE, as described herein) or a memory of an application server or a network application server (such as memory 824 of a network device that is an application server or a network application server, as described herein).

[0065] Embodiments contemplated herein include an apparatus having a Figures 3 to 6 A logic component, module, or circuit that is a component of one or more elements of the method or flowchart shown. Figures 3 to 6 In the context of the method or flow chart shown, the apparatus may be, for example, an apparatus of a UE (such as the wireless device 802 as a UE, as described herein) or an application server or network application server (such as a network application server) implementing one or more network functions (such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG, and / or CCS, etc.). Figure 8 820).

[0066] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that use or store instructions that, when executed by the one or more processors, cause the one or more processors to perform Figures 3 to 6 One or more elements of a method or flow chart as shown. Figures 3 to 6 In the context of the method or flow chart shown, the apparatus may be, for example, an apparatus of a UE (such as the wireless device 802 as a UE, as described herein) or an application server or network application server (such as a network application server) implementing one or more network functions (such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG, and / or CCS, etc.). Figure 8 820).

[0067] Embodiments contemplated herein include, for example, Figures 3 to 6 A signal described in or relating to one or more elements of a method or flowchart shown.

[0068] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein the program, when executed by a processor, causes the processor to perform Figures 3 to 6 One or more elements of a method or flow chart as shown. Figures 3 to 6In the context of the method or flow chart shown, the processor may be a processor of a UE (such as the processor 804 of the wireless device 802 as a UE, as described herein), and the instructions may be located, for example, in the processor and / or on a memory of the UE (such as the memory 806 of the wireless device 802 as a UE, as described herein), or on a memory of an application server or network application server implementing one or more network functions (such as AF, NEF, AMF, SMF, PCF, UPF, CHF, CHG, and / or CCS, etc.) (such as Figure 8 Memory 824 of an application server or network application server shown as 820).

[0069] Figure 7 An example architecture of a wireless communication system in a cellular carrier domain according to an embodiment disclosed herein is depicted. The description provided below is for an example wireless communication system operating in conjunction with an LTE system standard and / or a 5G or NR system standard, and / or a future 6G standard, etc., as provided by the 3GPP technical specifications.

[0070] like Figure 7 As shown, the wireless communication system includes UE 702 and UE 704 (although any number of UEs may be used). In this example, UE 702 and UE 704 are illustrated as smartphones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0071] UE 702 and UE 704 may be configured to be communicatively coupled to RAN 706. In an embodiment, RAN 706 may be NG-RAN, E-UTRAN, etc. UE 702 and UE 704 utilize connections (or channels) (shown as connection 708 and connection 710, respectively) with RAN 706, where each connection (or channel) includes a physical communication interface. RAN 706 may include one or more base stations, such as base station 712 and base station 714, to implement connection 708 and connection 710.

[0072] In this example, connection 708 and connection 710 are air interfaces used to achieve this communicative coupling and may conform to one or more radio access technologies (RATs) used by the RAN 706, such as, for example, LTE and / or NR.

[0073] In some embodiments, UE 702 and UE 704 may also directly exchange communication data via side link interface 716. UE 704 is shown as being configured to access an access point (shown as AP 718) via connection 720. As an example, connection 720 may include a local wireless connection, such as any connection conforming to the IEEE 802.11 protocol, wherein AP 718 may include a Wi-Fi ® In this example, AP 718 may not be connected to another network (eg, the Internet) through CN 724.

[0074] In an embodiment, UE 702 and UE 704 may be configured to communicate with each other or with base station 712 and / or base station 714 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals in accordance with various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0075] In some embodiments, all or part of the base station 712 or the base station 714 may be implemented as one or more software entities running on a server computer as part of a virtual network. In addition, or in other embodiments, the base station 712 or the base station 714 may be configured to communicate with each other via the interface 722. In an embodiment where the wireless communication system is an LTE system (e.g., when the CN 724 is an EPC), the interface 722 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In an embodiment where the wireless communication system is an NR system (e.g., when the CN 724 is a 5GC), the interface 722 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to the 5GC, between the base station 712 (e.g., gNB) and the eNB connected to the 5GC, and / or between two eNBs connected to the 5GC (e.g., CN 724).

[0076] RAN 706 is shown as being communicatively coupled to CN 724. CN 724 may include one or more network elements 726 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 702 and users of UE 704) connected to CN 724 via RAN 706. The components of CN 724 may be implemented in one physical device or separate physical devices, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0077] In an embodiment, CN 724 may be an EPC, and RAN 706 may be connected to CN 724 via an S1 interface 728. In an embodiment, S1 interface 728 may be divided into two parts: an S1 user plane (S1-U) interface, which carries traffic data between base station 712 or base station 714 and a serving gateway (S-GW); and an S1-MME interface, which is a signaling interface between base station 712 or base station 714 and a mobility management entity (MME).

[0078] In an embodiment, CN 724 may be a 5GC, and RAN 706 may be connected to CN 724 via an NG interface 728. In an embodiment, NG interface 728 may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between base station 712 or base station 714 and a user plane function (UPF); and an S1 control plane (NG-C) interface, which is a signaling interface between base station 712 or base station 714 and an access and mobility management function (AMF).

[0079] Generally speaking, the application server 730 may be an element that provides applications that use Internet Protocol (IP) bearer resources with the CN 724 (e.g., packet-switched data services). The application server 730 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 702 and the UE 704 via the CN 724. The application server 730 may communicate with the CN 724 via an IP communication interface 732.

[0080] Figure 8 A system for performing signaling between a UE and a network device according to embodiments disclosed herein is depicted. Figure 8 The system shown may be part of a wireless communication system as described herein. For example, the wireless device 802 may be a UE of the wireless communication system. The network 820 may include, for example, a base station or access point in a radio access network connected to the wireless communication system via a wired or wireless communication link, and one or more application servers or network servers located in a core network.

[0081] The wireless device 802 may include one or more processors 804. The processor 804 may execute instructions to perform various operations of the wireless device 802, as described herein. The processor 804 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0082] The wireless device 802 may include a memory 806. The memory 806 may be a non-transitory computer-readable storage medium that stores instructions 808 (which may include, for example, instructions executed by the processor 804). The instructions 808 may also be referred to as program code or a computer program. The memory 806 may also store data used by the processor 804 and results computed by the processor.

[0083] The wireless device 802 may include one or more transceivers 810, which may include radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 812 of the wireless device 802 to facilitate signaling (e.g., signaling 838) to and / or from the wireless device 802 with other devices (e.g., network 820) in accordance with a corresponding RAT.

[0084] The wireless device 802 may include one or more antennas 812 (e.g., one, two, four, or more). For implementations with multiple antennas 812, the wireless device 802 may take advantage of the spatial diversity of these multiple antennas 812 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to the multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmission by the wireless device 802 may be implemented based on precoding (or digital beamforming) applied to the wireless device 802, which multiplexes the data streams between the antennas 812 based on known or assumed channel characteristics so that each data stream is received at an appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with the data stream). Certain implementations may use a single-user MIMO (SU-MIMO) approach (in which the data streams are all directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (in which separate data streams may be directed to separate (different) receivers in different locations in the spatial domain).

[0085] In some embodiments, a wireless device 802 (e.g., a UE) may communicate with a network 820 (e.g., a base station or access point, and / or one or more application servers or network application servers). The wireless device 802 may communicate with the access point via an antenna 812, and the access point may communicate with the network 820 via a wired or wireless connection.

[0086] In certain embodiments with multiple antennas, the wireless device 802 may implement analog beamforming techniques whereby the phases of signals transmitted by the antennas 812 are relatively adjusted such that the (joint) transmissions of the antennas 812 are directional (this is sometimes referred to as beam steering).

[0087] The wireless device 802 may include one or more interfaces 814. The interface 814 may be used to provide input to the wireless device 802 or output from the wireless device. For example, a wireless device 802 that is a UE may include an interface 814, such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to input and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits (for example, in addition to the transceiver 810 / antenna 812 described above), which allow the UE to communicate with other devices and may communicate according to known protocols (for example, Wi-Fi ® ,Bluetooth ® etc.) work.

[0088] Figure 8 The base station, application server, and / or network application server shown as 820 in the figure may include one or more processors 822. The processor 822 may execute instructions to perform various operations of the network device 820 as described herein. The processor 822 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0089] Figure 8 The base station, application server, and / or network application server shown as 820 in the figure may include a memory 824. The memory 824 may be a non-transitory computer-readable storage medium that stores instructions 826 (which may include, for example, instructions executed by the processor 822). The instructions 826 may also be referred to as program code or a computer program. The memory 824 may also store data used by the processor 822 and results calculated by the processor.

[0090] Figure 8The base station, application server, and / or network application server shown as 820 may include one or more transceivers 828, which may include RF transmitter and / or receiver circuits that use antenna 830 of network device 820 to facilitate signaling (e.g., signaling 838) to and / or from network device 820 and other devices (e.g., wireless device 802) according to the corresponding RAT. In some embodiments, signaling 838 may occur via a wired or wireless network.

[0091] Figure 8 The base station, application server, and / or network application server shown as 820 in the figure may include one or more antennas 830 (e.g., one, two, four, or more). In an embodiment with multiple antennas 830, the network device 820 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc. as described above.

[0092] Figure 8 The base station, application server and / or network application server shown as 820 in the figure may include one or more interfaces 832. The interface 832 may be used to provide input to the network device 820 or provide output from the network device. For example, the network 820 as a base station may include an interface 832 composed of a transmitter, a receiver and other circuits (for example, in addition to the transceiver 828 / antenna 830 described above), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with external networks, computers, databases, etc., in order to achieve the purpose of performing operations, management and maintenance of the base station or other equipment operably connected to the base station.

[0093] Figure 8 The base station, application server, and / or network application server shown as 820 in the figure may include a network slice processing module 834 configured to execute various embodiments for billing application providers, as described herein. The network slice processing module 834 may be implemented via hardware, software, or a combination thereof. For example, the network slice processing module 834 may be implemented as a processor, circuit, and / or instruction 826 stored in the memory 824 and executed by the processor 822. In some examples, the network slice processing module 834 may be integrated within the processor 822. For example, the network slice processing module 834 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 822.

[0094] For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein. For another example, circuits associated with a UE, a base station, a network element, etc. as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein.

[0095] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0096] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic for performing operations; or may include a combination of hardware, software, and / or firmware.

[0097] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of another embodiment may be used in one embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless expressly stated herein.

[0098] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0099] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

[0100] As used herein, the phrase "at least one of" following a list of items, any of which is separated by the terms "and" or "or," modifies the list as a whole, rather than each member of the list. The phrase "at least one of" does not require selection of at least one of each of the listed items; rather, the phrase allows for a meaning that includes at least one of any of the items and / or at least one of any combination of the items and / or at least one of each of the items. For example, the phrase "at least one of A, B, and C" or "at least one of A, B, or C" each refers to only A, only B, or only C; any combination of A, B, and C; and / or one or more of each of A, B, and C. Similarly, it should be understood that the order in which the elements are presented for the combined or separated lists provided herein should not be construed to limit the disclosure to only the order provided.

Claims

1. A network application server, comprising: Communication circuits; and at least one processor, the at least one processor being configured to: receiving, from a plurality of user equipments (UEs) and via the communication circuitry, a plurality of requests to receive service data from a plurality of application providers; determining an amount of service data exchanged between an application provider among the plurality of application providers and a set of UEs among the plurality of UEs requesting service data over the one or more network slices; generating first charging information corresponding to the application provider according to criteria including an amount of the service data exchanged with the application provider over the one or more network slices for the group of UEs; as well as Second billing information corresponding to each UE in the group of UEs is generated according to data usage of each UE in the group of UEs, and the generation of the second billing information is independent of the characteristics of the one or more network slices used to provide the requested service data.

2. The network application server according to claim 1, wherein the criteria for generating the first billing information corresponding to the application provider further includes at least one of the following: performance statistics of the one or more network slices; or One or more attributes of the one or more network slices.

3. The network application server according to claim 2, wherein the performance statistics of the one or more network slices include at least one of the following: The total number of online or active users; The total number of connections; The total number of online sessions; delay; or The throughput during a specific time period.

4. The network application server according to claim 2, wherein the one or more attributes of the one or more network slices include at least one of the following: The peak number of online or active users during a specific time period; the peak number of connections during the specific time period; the peak number of online sessions during the specified time period; or The type of service coverage.

5. The network application server according to claim 1, wherein each UE in the group of UEs is further charged according to one or more of the following items: Multiple protocol data unit (PDU) sessions; service data flow; or Quality of Service (QoS) flows.

6. A network application server according to claim 1, wherein the amount of the service data exchanged with the application provider through the one or more network slices for the group of UEs is determined without an application identifier (AppID) associated with a UE routing selection policy (URSP) for each UE in the group of UEs.

7. The network application server according to claim 1, wherein each of the one or more network slices is configured to provide the requested service data according to a different quality of service or a service level agreement with a UE in the group of UEs.

8. A method comprising: receiving a plurality of requests from a plurality of user equipments (UEs) at a network application server to receive service data from a plurality of application providers; determining, by the network application server, an amount of service data exchanged between an application provider among the plurality of application providers and a group of UEs among the plurality of UEs requesting service data through one or more network slices; as well as The network application server generates billing information corresponding to the application provider according to the total amount of service data exchanged with the application provider through the one or more network slices for the group of UEs, without using an application identifier (AppID) associated with a UE routing selection policy (URSP) for each UE in the group of UEs to identify the application provider.

9. The method according to claim 8, wherein the billing information is first billing information, the method further comprising: Second billing information corresponding to each UE in the group of UEs is generated according to data usage of each UE in the group of UEs, and the generation of the second billing information is independent of the characteristics of the one or more network slices used to provide the requested service data.

10. The method according to claim 8 also includes generating the billing information corresponding to the application provider according to the performance statistics of the one or more network slices.

11. The method of claim 10, wherein the performance statistics of the one or more network slices include at least one of the following: The total number of online or active users; The total number of connections; The total number of online sessions; delay; or The throughput during a specific time period.

12. The method according to claim 8 further includes generating the billing information corresponding to the application provider according to one or more attributes of the one or more network slices.

13. The method of claim 12, wherein the one or more attributes of the one or more network slices include at least one of the following: The peak number of online or active users during a specific time period; the peak number of connections during the specific time period; the peak number of online sessions during the specified time period; or The type of service coverage.

14. The method according to claim 8, wherein the billing information is first billing information, the method further comprising: The second charging information corresponding to each UE in the group of UEs is generated according to one or more of the following items: Multiple protocol data unit (PDU) sessions; service data flow; or Quality of Service (QoS) flows.

15. The method of claim 8, wherein each of the one or more network slices is configured to provide the requested service data according to a different quality of service or a service level agreement with a UE in the group of UEs.

16. A convergent charging system (CCS), the convergent charging system (CCS) comprising: A first server, wherein the first server comprises: a first processor; and A first memory is provided, wherein the first memory stores instructions, and when the instructions are executed by the first processor, the first server performs the following operations: determining an amount of service data exchanged between an application provider among a plurality of application providers and a set of UEs among a plurality of UEs requesting service data over one or more network slices; and Data usage of each UE in the group of UEs is determined.

17. The CCS according to claim 16, further comprising: A second server, wherein the second server comprises: a second processor; and A second memory is used for storing instructions, and when the instructions are executed by the second processor, the second server performs the following operations: generating first charging information corresponding to the application provider according to criteria including an amount of the service data exchanged with the application provider over the one or more network slices for the group of UEs; and Second billing information corresponding to each UE in the group of UEs is generated according to the data usage of each UE in the group of UEs, and the generation of the second billing information is independent of the characteristics of the one or more network slices used to provide the requested service data.

18. The CCS of claim 17, wherein generating the first charging information corresponding to the application provider comprises generating the first charging information corresponding to the application provider without identifying the application provider using an application identifier (AppID) associated with a UE routing selection policy (URSP) for each UE in the set of UEs.

19. The CCS of claim 17, wherein the criteria for generating the first charging information corresponding to the application provider further comprises at least one of the following: performance statistics of the one or more network slices; or One or more attributes of the one or more network slices.

20. The CCS of claim 19, wherein: The performance statistics of the one or more network slices include at least one of a total number of online or active users, a total number of connections, a total number of online sessions, latency, or a throughput within a specific time period; and The one or more attributes of the one or more network slices include at least one of a peak number of online or active users within a specific time period, a peak number of connections within the specific time period, a peak number of online sessions within the specific time period, or a type of service coverage.