TWI737633B - Method, apparatus and system for sponsored data connectivity related information control and transmission in a wireless network - Google Patents

Abstract

Machine-readable media, methods, apparatus and system for sponsored data connectivity related information (SDCRI) control and transmission in a wireless network. In some embodiments, an apparatus to be implemented as a sponsored data connectivity function (SDCF) may comprise a control module to configure sponsored data connectivity related information (SDCRI); and an interface module to transmit a request associated with the SDCRI to a policy and charging enforcement function (PCEF) or a traffic detection function (TDF), based at least in part on a network operator's policy.

Description

Method, device and system for controlling and transmitting information related to the connectivity of sponsored data in wireless network

The embodiments of this application generally relate to the field of wireless communications, and more particularly relate to methods, devices, and systems for controlling and transmitting Sponsored Data Connectivity Related Information (SDCRI) in wireless networks.

In wireless networks (for example, in compliance with the Long Term Evolution (LTE) standard of the third-generation mobile communications cooperation program with any changes, updates and/or amendments), the Policy and Charging Rules Function (PCRF) can be configured for sponsored data connectivity Related information (SDCRI), and during the establishment or modification process of the IP-CAN communication period, it is sent on the basis of each user and/or each Internet Protocol Connectivity Access Network (IP-CAN) communication period SDCRI to Policy and Charging Enforcement Function (PCEF).

100: wireless system

101: Application Service

102: Sponsored data connectivity function

103: Policy and charging rules function

104: Policy and billing enforcement function

105: Flow detection function

106: Gateway

107: Radio Access Network

108: user equipment

110: control module

112: Interface Module

113: Control Module

114: Interface Module

115: control module

116: Interface Module

601: Block

602: Block

603: Block

604: Block

700: System

704: processor

708: System Control Logic

712: system memory

716: Non-volatile memory/storage

720: network interface

724: instruction

732: input/output device

800: user equipment device

802: Application Circuit

804: Baseband Circuit

804a: Second-generation baseband processor

804b: third-generation baseband processor

804c: The fourth generation baseband processor

804d: other baseband processors

804e: Central Processing Unit

804f: Audio digital signal processor

806: RF circuit

806a: Mixer circuit

806b: amplifier circuit

806c: filter circuit

806d: synthesizer circuit

808: Front-end module circuit

1010: Antenna

The embodiments of this application are by way of example rather than by way of limitation It is shown that in the figures of the accompanying drawings, the same reference numbers refer to the same elements.

Figure 1 schematically illustrates a wireless system for Sponsored Data Connectivity Related Information (SDCRI) control according to various embodiments.

FIG. 2 schematically illustrates an example of an initial provisioning procedure for SDCRI control in a wireless network according to various embodiments.

FIG. 3 schematically shows an example of a modification procedure for SDCRI control in a wireless network according to various embodiments.

FIG. 4 schematically illustrates an example of a removal procedure for SDCRI control in a wireless network according to various embodiments.

FIG. 5 schematically illustrates a method of SDCRI control implemented by the Sponsored Data Connectivity Function (SDCF) in the wireless system according to various embodiments.

Fig. 6 schematically illustrates a method of SDCRI control implemented by a policy and charging enforcement function (PCEF) in a wireless system according to various embodiments.

Figure 7 schematically illustrates an example system according to various embodiments.

Fig. 8 schematically illustrates an example of a UE device according to various embodiments.

[Content and Implementation of the Invention]

Illustrative embodiments of the present disclosure include, but are not limited to, the use of sponsored data connectivity in wireless networks (e.g., in compliance with the Long Term Evolution (LTE) standard of the third-generation mobile communications cooperation project together with any changes, updates, and/or amendments) Related information control and transmission methods, systems and equipment.

Various aspects of the illustrative embodiments will be described using terms commonly used by persons with ordinary knowledge in the relevant technical field, so as to convey the essence of their work to persons with ordinary knowledge in other technical fields. However, the technology Those with general knowledge in the field will understand that some of the explanations can be used to implement some alternative embodiments. For the purpose of explanation, specific numbers, materials, and configurations are presented in order to provide a complete understanding of the illustrative embodiments. However, those with ordinary knowledge in the technical field will understand that alternative embodiments can be implemented without the specific details. In other cases, well-known features may be omitted or simplified so as not to confuse the illustrative embodiments.

Furthermore, multiple operations will be described in several separate operations, followed by the most useful way to understand the illustrative embodiments; however, the order of the embodiments should not be construed to mean that these operations should be related to the order. In particular, these operations need not be performed in the order of presentation.

The term "in one embodiment" is used repeatedly. The term generally does not mean the same embodiment; however, the term may mean the same embodiment. The terms "include", "have", and "include" are synonymous, unless the context dictates otherwise. The word "A/B" means "A or B". The term "A and/or B" means "(A), (B), or (A and B)". The term "at least one of A, B, and C" means "(A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C)". The word "(A)B" means "(B) or (AB)", that is, A is optional.

Although the specific examples have been illustrated and described herein, those skilled in the art will understand that various alternative and/or equivalent implementations can be substituted for the specific examples shown and described without departing from the present invention. The scope of the disclosed embodiments. This application is intended to cover any adaptations or changes of the embodiments discussed herein. Therefore, the obvious intention is Therefore, the embodiments of the present disclosure are only limited by the scope of the patent application and its equivalents.

As used herein, the term "module" can mean, can be a part of, or can include application-specific integrated circuits (ASIC), electronic circuits, processors (shared, dedicated, or group), and /Or memory (shared, dedicated, or group), which executes one or more software or firmware programs, combinational logic circuits, and/or other appropriate components that provide the described functions.

Fig. 1 schematically illustrates a wireless system 100 for controlling and transmitting Sponsored Data Connectivity Related Information (SDCRI) according to various embodiments. In some embodiments, the wireless system 100 may include application services 101, sponsored data connectivity function (SDCF) 102, policy and charging rules function (PCRF) 103, packet data network gateway (PDW)/policy and accounting Charge execution function (PCEF) 104, traffic detection function (TDF) 105, other gateways 106 (such as service gateway (S-GW)), radio access network (RAN) 107, user equipment (UE) 108. And/or others that can use many wireless access technologies to operate in a wireless network, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time sharing Multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and/or compliant with the Institute of Electrical and Electronics Engineers (IEEE) 802 system, third-generation mobile communications Cooperation Project (3GPP) system, 3GPP Long Term Evolution (LTE) system, and/or 3GPP2 system others.

The AS101 may be owned by a wireless network operator and/or a third-party application service provider, and provide application services to the UE108. In some embodiments , The sponsor can compensate the network connectivity of the UE to the operator of the wireless network associated with the sponsor, so as to prompt the UE 108 to access the associated application service.

In some embodiments, the SDCF 102 may include a control module 110, an interface module 112, and/or other modules. The control module 110 can configure the SDCRI based at least in part on the operator's policy. If the operator decides to open the interface to a third-party application service provider or respond to requests from other functional entities (such as AS101), it may be unsafe. Examples of "configuration" may include, but are not limited to, addition, modification, and removal. Examples of "SDCRI" may include, but are not limited to, the identification of sponsors, the identification of application service providers and their applications, sponsored data rules (such as usage thresholds) to limit the amount or time of data that can be sponsored for user connectivity, and billing Key, and/or others. The interface module 112 can receive a request from the AS101, and send a response to the request to the AS101 via the interface Sr3. The request may include a request to add an SDCRI, a request to modify an SDCRI, a request to remove an SDCRI, and/or others. The response may include adding SDCRI response, modifying SDCRI response, removing SDCRI response, and/or other.

Based at least in part on an operator's strategy, the interface module 112 may further transmit a request associated with the SDCRI to the PCEF 104 via the interface Sr1 or to a traffic detection function (TDF) 105 via the interface Sr2. For example, the interface module 112 may periodically send the request associated with the SDCRI to PCEF104/TDF105, and/or respond to other functional entities (such as AS101, PDRF103, Service Performance Exposure Function (SCEF) (in Figure 1). Is not shown in), etc.) and Send the request associated with the SDCRI to PCEF104/TDF105. In addition, the interface module 112 can receive a response to the request from the PCEF 104 via the interface Sr1 or from the TDF 105 via the interface Sr2. The request may include a request to add an SDCRI, a request to modify an SDCRI, a request to remove an SDCRI, and/or others. The response may include adding SDCRI response, modifying SDCRI response, removing SDCRI response, and/or other.

The PCEF 104 may include a control module 113, an interface module 114, and/or others. The control module 113 can configure the SDCRI in response at least in part to the request received from the SDCF 102 via the interface Sr1. Examples of "configuration" may include, but are not limited to, addition, modification, and removal. Based at least in part on the SDCRI provided by the SDCF, the control module 113 can further calculate and record the service unit used by the UE 108 for sponsoring data connectivity for billing purposes.

The interface module 114 can receive a request from the SDCF 102, and send a response to the request to the SDCF 102 via the interface Sr1. The request may include a request to add an SDCRI, a request to modify an SDCRI, a request to remove an SDCRI, and/or others. The response may include adding SDCRI response, modifying SDCRI response, removing SDCRI response, and/or other.

The TDF 105 may include a control module 115, an interface module 116, and/or others. The control module 115 can configure the SDCRI in response at least in part to the request received from the SDCF 102 via the interface Sr2. Examples of "configuration" may include, but are not limited to, addition, modification, and removal. Based at least in part or optionally based on the SDCRI provided by the SDCF, the control module 115 may further calculate and record the used service units for sponsoring data connectivity for billing purposes.

The interface module 116 can receive the request from the SDCF 102, and through The interface Sr2 sends the response to the request to SDCF102. The request may include a request to add an SDCRI, a request to modify an SDCRI, a request to remove an SDCRI, and/or others. The response may include adding SDCRI response, modifying SDCRI response, removing SDCRI response, and/or other.

In some embodiments, PCRF103 can configure SDCRI based at least in part on the Internet Protocol Connectivity Access Network (IP-CAN) communication period-related information received from AS101 via interface Rx, and configure SDCRI based on interface Gx. A user and/or every IP-CAN communication period provides SDCRI to PCEF104. Examples of "configuration" may include, but are not limited to, addition, modification, and removal. Examples of "SDCRI" may include, but are not limited to, the identification of sponsors, the identification of application service providers and their applications (optionally using thresholds), and whether PCRF103 reports connectivity with sponsored data, billing keys, and/ Or other related events. In some embodiments, the PCRF 103 may further send an instruction to the PCEF 104 or the TDF 105, and the instruction starts the SDCRI supplied by the PCRF or the SDCRI supplied by the SDCF for this IP-CAN communication period.

Based on the wireless system 100, the SDCF 102 can be implemented as a central node to maintain all SDCRI interfaces with third-party application program interfaces for PCEFs/TDFs within its coverage area. Furthermore, the communication between AS101 and SDCF102 may exceed data layer 3.

It should be understood that other technologies may be implemented for other embodiments of SDCF 102. For example, SDCF102 can be paired with PCRF103, which can result in requests and responses associated with SDCRI between AS101 and PCRF103 that want to communicate via interface Rx, as well as those that want to communicate via interface Gx. SDCRI related request and response between PCRF103 and PCEF104. For example, SDCF102 can be paired with SCEF (not shown in Figure 1), which can result in requests and responses associated with the SDCRI between SCEF and PCEF104 to be communicated via PCRF103, for example, via the interface Rx between SCEF and PCRF103 , And through the interface Gx between PCRF103 and PCEF104.

FIG. 2 schematically illustrates an example of an initial provisioning procedure for SDCRI control in a wireless network according to various embodiments. The procedure shown in the upper part of FIG. 2 can correspond to the situation where SDCF102 receives SDCRI from AS101. In some embodiments, AS101 may transmit an add SDCRI request to SDCF102 (S201), where the SDCRI request may include SDCRI. Examples of "SDCRI" may include, but are not limited to, sponsored data connectivity information (SDCI). The sponsored data connectivity information has the identification of the sponsor, the identification of the application service provider and its application, and the information used to limit the connectivity of sponsored users. Sponsored data rules for the amount or time of the data (such as using thresholds), and/or others. The SDCF102 can store the SDCRI and send an add SDCRI response to the AS101 (S202).

Based at least in part on the operator's policy, the SDCF 102 may send the SDCRI addition request to the PCEF 104 (S203) or TDF 105 (S204). For example, the SDCF 102 may periodically transmit the SDCRI addition request to the PCEF 104 or TDF 105, or transmit the SDCRI addition request to the PCEF 104 or TDF 105 in response to a request from another entity (such as AS101, PDRF103, SCEF, etc.). The add SDCRI request may include SDCRI. Examples of "SDCRI" may include, but are not limited to, SDCI, Service data flow template and charging key that can be allocated by SDCF102.

The PCEF 104 or TDF 105 can store the SDCRI and start calculating and recording the service units used, and start communication with the offline charging system (OFCS) for offline charging based at least in part on the SDCRI. Furthermore, in S205 and S206, PCEF104 or TDF105 can send the SDCRI response to SDCF102 respectively.

The program shown in the lower part of FIG. 2 can correspond to the situation where SDCF102 supplies SDCRI on the operator's configuration. For example, if the operator decides to open the interface to a third-party application service provider, it may be unsafe. Based at least in part on the operator's policy, the SDCF 102 may send the SDCRI addition request to the PCEF 104 (S207) or to the TDF 105 (S208). For example, the SDCF 102 may periodically transmit the SDCRI addition request to the PCEF 104 or TDF 105, or transmit the SDCRI addition request to the PCEF 104 or TDF 105 in response to a request from another entity (such as AS101, PDRF103, SCEF, etc.). The add SDCRI request may include SDCRI. Examples of "SDCRI" may include, but are not limited to, the identification of sponsors, the identification of application service providers and their applications, sponsored data rules (such as usage thresholds) that limit the amount or time of data that can be sponsored for user connectivity, services Data flow template, billing key, and/or others.

The PCEF 104 or TDF 105 can store the SDCRI and start calculating and recording the service units used, and start communication with the offline charging system (OFCS) based at least in part on the SDCRI. Furthermore, in S209 and S210, PCEF104 or TDF105 can send the SDCRI response to SDCF102 separately.

FIG. 3 schematically shows an example of a modification procedure for SDCRI control in a wireless network according to various embodiments. The procedure shown in the upper half of FIG. 3 can correspond to a situation where SDCF102 responds at least partially to a request from AS101 to modify the SDCRI. In some embodiments, AS101 may send a request to modify SDCRI to SDCF 102 (S301), where the request to modify SDCRI may include SDCRI modification related information. Examples of "SDCRI" may include, but are not limited to, sponsored data connectivity information (SDCI). The sponsored data connectivity information has the identification of the sponsor, the identification of the application service provider and its application, and the information used to limit the connectivity of sponsored users. Sponsored data rules for the amount or time of the data (such as using thresholds), and/or others. SDCF102 can modify SDCRI and send a modified SDCRI response to AS101 (S302).

Based at least in part on the operator's policy, the SDCF 102 may send a request to modify the SDCRI to the PCEF 104 (S303) or TDF 105 (S304). For example, SDCF 102 may periodically transmit the modified SDCRI request to PCEF 104 or TDF 105, or transmit the modified SDCRI request to PCEF 104 or TDF 105 in response to a request from another entity (such as AS101, PDRF 103, SCEF, etc.). The SDCRI modification request may include SDCRI modification related information. Examples of "SDCRI" may include, but are not limited to, SDCI, service data flow templates, and charging keys that can be allocated by SDCF 102.

The PCEF 104 or TDF 105 can modify the SDCRI and start calculating and recording the service unit used, and start communication with the offline charging system (OFCS) based at least in part on the modified SDCRI. Even more, in In S205 and S206, PCEF104 or TDF105 can respectively send the modified SDCRI response to SDCF102.

The program shown in the lower part of Figure 3 can correspond to the situation where SDCF102 modifies SDCRI on the operator's configuration. For example, if the operator decides to open the interface to a third-party application service provider, it may be unsafe. Based at least in part on the operator's policy, the SDCF 102 may send the modified SDCRI request to the PCEF 104 (S307) or to the TDF 105 (S308). For example, SDCF 102 may periodically transmit the modified SDCRI request to PCEF 104 or TDF 105, or transmit the modified SDCRI request to PCEF 104 or TDF 105 in response to a request from another entity (such as AS101, PDRF 103, SCEF, etc.). The SDCRI modification request may include SDCRI modification related information. Examples of "SDCRI" may include, but are not limited to, the identification of sponsors, the identification of application service providers and their applications, sponsored data rules (such as usage thresholds) that limit the amount or time of data that can be sponsored for user connectivity, services Data flow template, billing key, and/or others.

The PCEF 104 or TDF 105 can modify the SDCRI and start calculating and recording the service unit used, and start communication with the offline charging system (OFCS) based at least in part on the modified SDCRI. Furthermore, in S309 and S310, PCEF104 or TDF105 can respectively send the modified SDCRI response to SDCF102.

FIG. 4 schematically illustrates an example of a removal procedure for SDCRI control in a wireless network according to various embodiments. As shown in the upper half of Figure 4, the corresponding SDCF102 can at least partially respond to the response from AS101 Request to remove SDCRI. In some embodiments, the AS101 may send a SDCRI removal request to the SDCF 102 (S401), where the SDCRI removal request may include SDCRI removal related information, such as the identification of the sponsor and the application service provider corresponding to the SDCRI to be removed. Examples of "SDCRI" may include, but are not limited to, sponsored data connectivity information (SDCI), which has the identification of the sponsor, the identification of the application service provider, and/or other. The SDCF 102 can remove the SDCRI and send a remove SDCRI response to the AS 101 (S402).

Based at least in part on the operator's policy, the SDCF 102 may send the SDCRI removal request to the PCEF 104 (S403) or TDF 105 (S404). For example, the SDCF 102 may periodically transmit the SDCRI removal request to the PCEF 104 or TDF 105, or transmit the SDCRI removal request to the PCEF 104 or TDF 105 in response to a request from another entity (such as AS101, PDRF103, SCEF, etc.). The SDCRI request may include SDCRI removal related information, such as the sponsor identification and application service provider identification corresponding to the SDCRI to be removed. Examples of "SDCRI" may include, but are not limited to, SDCI, service data flow templates, and charging keys that can be allocated by SDCF 102.

PCEF104 or TDF105 can remove SDCRI and stop calculating and recording the used service unit, and stop offline charging communication with the offline charging system (OFCS). Moreover, in S405 and S406, PCEF104 or TDF105 can respectively send the SDCRI removal response to SDCF102.

The procedure shown in the lower part of Figure 4 can correspond to the situation where SDCF102 removes SDCRI on the operator’s configuration, for example, if the operator decides to open The interface to third-party application service providers may be insecure. Based at least in part on the operator's policy, the SDCF 102 may send the SDCRI removal request to the PCEF 104 (S407) or TDF 105 (S408). For example, the SDCF 102 may periodically transmit the SDCRI removal request to the PCEF 104 or TDF 105 or transmit the SDCRI removal request to the PCEF 104 or TDF 105 in response to a request from another entity (such as AS101, PDRF103, SCEF, etc.). The SDCRI removal request may include SDCRI removal related information. Examples of "SDCRI" may include, but are not limited to, the identification of sponsors, the identification of application service providers, and/or others.

PCEF104 or TDF105 can remove SDCRI and stop calculating and recording the used service unit, and stop offline charging communication with the offline charging system (OFCS). Furthermore, in S409 and S410, PCEF104 or TDF105 can respectively send the SDCRI removal response to SDCF102.

FIG. 5 schematically illustrates a method of SDCRI control implemented by the Sponsored Data Connectivity Function (SDCF) in the wireless system 100 according to various embodiments. In some embodiments, in block 501, SDCF 102 may receive an add/modify/remove SDCRI request from AS101. The add SDCRI request may include SDCRI. The SDCRI modification request may include SDCRI modification related information. The SDCRI removal request may include SDCRI removal related information, such as the identification of the sponsor and the application service provider corresponding to the SDCRI to be removed. In block 502, based at least in part on the add/modify/remove SDCRI request, the SDCF 102 may add/modify/remove the SDCRI. In block 503, SDCF 102 may send an add/modify/remove SDCRI response to AS101.

In block 504, based at least in part on the operator's policy, SDCF 102 may transmit the add/modify/remove request to PCEF 104 or TDF 105. For example, SDCF102 may periodically send a request to add/modify/remove SDCRI to PCEF104 or TDF105, or send a request to add/modify/remove SDCRI to PCEF104 or TDF105 in response to requests from other entities (such as AS101, PDRF103, SCEF, etc.) PCEF104 or TDF105. The add SDCRI request may include SDCRI. The SDCRI modification request may include SDCRI modification related information. The SDCRI removal request may include SDCRI removal related information. In block 505, SDCF 102 may receive the add/modify/remove SDCRI response from PCEF 104 or TDF 105.

It should be understood that other embodiments may implement other techniques used in the method of FIG. 5. For example, the SDCF 102 can add/modify/remove the SDCRI itself, such as based on the operator's policy, not based on the request from AS101. In view of this, blocks 501 to 503 can be omitted.

Fig. 6 schematically illustrates a method of SDCRI control implemented by a policy and charging enforcement function (PCEF) in a wireless system according to various embodiments. In block 601, PCEF 104 or TDF 105 may receive an add/modify/remove SDCRI request from SDCF 102, which may be transmitted based at least in part on the operator's policy 601. For example, it can periodically send add/modify/remove SDCRI requests to PCEF104 or TDF105, or send add/modify/remove SDCRI requests to PCEF104 in response to requests from other entities (such as AS101, PDRF103, SCEF, etc.) Or TDF105. The add SDCRI request may include SDCRI. The SDCRI modification request may include SDCRI modification related information. SDCRI removal request may include SDCRI move In addition to related information.

In block 602, PCEF 104 or TDF 105 may add/modify/remove SDCRI at least in part in response to the add/modify/remove request. In block 603, PCEF 104 or TDF 105 may send an add/modify/remove SDCRI response to SDCF 102. In block 604, start to calculate and record the service units used, and start at least partly in response to adding or modifying the SDCRI request to start offline charging communication with the offline charging system (OFCS); or, at least partly in response to removing The SDCRI requested to stop calculating and recording the service units used, and stop the offline charging communication with the offline charging system (OFCS).

Figure 7 schematically illustrates an example system 700 according to various embodiments. In an embodiment, the system 700 may include one or more processors 704, a system control logic 708 coupled with at least one processor 704, a system memory 712 coupled with the system control logic 708, and a system memory 712 coupled with the system control logic 708. Non-volatile memory (NVM)/storage 716, and network interface 720 coupled with system control logic 708.

The processor 704 may include one or more single-core or multi-core processors. The processor 704 may include any combination of a general-purpose processor and a dedicated processor (for example, a graphics processor, an application processor, a baseband processor, etc.). In an embodiment where the system 700 implements AS101, SDCF102, PCRF103, PCEF104, or TDF105, the processor 704 may be configured to perform one or more embodiments as shown in FIGS. 1 to 6 according to various embodiments. .

The system control logic 708 for an embodiment may include any suitable interface controller to provide any suitable interface to at least one processor 704 and/or to any appropriate device or component that communicates with the system control logic 708.

The system control logic 708 for an embodiment may include one or more memory controllers to provide an interface to the system memory 712. The system memory 712 can be used to load and store data and/or commands used in the system 700, for example. The system memory 712 used in an embodiment may include any suitable volatile memory, such as, for example, a suitable dynamic random access memory (DRAM).

The NVM/storage 716 may include, for example, one or more tangible, non-transitory computer-readable media for storing data and/or instructions. The NVM/storage 716 may include any suitable non-volatile memory, such as, for example, flash memory, and/or may include any suitable non-volatile storage device, such as, for example, one or more hard disk drives (HDD), One or more compact disc (CD) drives, and/or one or more digital versatile disc (DVD) drives.

The NVM/storage 716 may include storage resources that are essentially part of the device on which the system 700 is installed, or it may be accessed by the device (but not necessarily a part of the device). For example, through the network interface 720, the NVM/storage 716 can be accessed through the network.

The system memory 712 and the NVM/storage 716 can each include, in particular, the temporary and persistent copy of the instruction 724. The instructions 724 may include instructions that, when executed by the at least one processor 704, cause the system 700 to implement the methods described with reference to FIGS. 5-6. In various embodiments, the instruction 724 or its hardware, firmware, and/or software components may additionally/alternatively be located in the system control logic 708, the network interface 720, and/or the processor 704.

The network interface 720 may include the interface module 112 of the SDCF 102 shown in FIG. 1, or the interface module 114 of the PCEF 104 and/or others, to provide a radio interface to the system 700 to communicate through one or more networks and/ Or communicate with any other appropriate device. In various embodiments, the network interface 720 can be integrated with other components of the system 700. For example, the network interface may include the processor in the processor 704, the memory in the system memory 712, the NVM/storage in the NVM/storage 716, and/or a firmware device with instructions (not shown) These instructions, when executed by at least one processor 704, cause the system 700 to implement the method described with reference to FIGS. 5-6.

The network interface 720 may further include any appropriate hardware and/or firmware for providing a multi-input and multi-output radio interface. The network interface 720 used in an embodiment may be, for example, a network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.

For one embodiment, at least one processor 704 may be packaged with logic for one or more controllers of the system control logic 708. For one embodiment, at least one processor 704 may be packaged with logic for one or more controllers of the system control logic 708 to form a system-in-package (SiP). For one embodiment, at least one processor 704 may be integrated on the same chip with the logic for one or more controllers of the system control logic 708. For one embodiment, the at least one processor 704 may be integrated with the logic of one or more controllers for the system control logic 708 on the same chip to form a system-on-chip (SoC).

The system 700 may further include an input/output (I/O) device 732. The I/O device 732 may include a user interface designed to enable a user to interact with the system 700. A user interface, a peripheral component interface designed to enable peripheral components to interact with the system 700, and/or a sensor designed to determine environmental conditions and/or location information related to the system 700.

In various embodiments, the user interface may include, but is not limited to, a display (e.g., liquid crystal display, touch screen display, etc.), speakers, microphones, one or more cameras (e.g., still cameras and/or cameras), Flash (for example, LED flash), and keyboard.

In various embodiments, the peripheral component interfaces may include, but are not limited to, non-volatile memory ports, audio jacks, and power supply interfaces.

In various embodiments, the sensor may include, but is not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be a part of the network interface 720 or interact with the network interface to communicate with components of a positioning network (such as a global positioning system (GPS) satellite).

In various embodiments, the system 700 may be AS101, SDCF102, PCRF103, PCEF104, or TDF105. In various embodiments, the system 700 may have more or fewer components, and/or have different architectures.

For one embodiment, FIG. 8 illustrates example components of a UE device 800 according to some embodiments. In some embodiments, the UE device 800 may include an application circuit 802, a baseband circuit 804, a radio frequency (RF) circuit 806, a front-end module (FEM) circuit 808, and one or more antennas 1010, which are coupled at least as shown Together. In some embodiments, the UE device 800 may include additional elements such as, for example, memory/storage, display, camera Machine, sensor, and/or input/output (I/O) interface.

The application circuit 802 may include one or more application processors. For example, the application circuit 802 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of a general-purpose processor and a dedicated processor (eg, graphics processor, application processor, etc.). The processor may be coupled and/or may include memory/storage, and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

The baseband circuit 804 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 804 may include one or more baseband processors and/or control logic to process the baseband signal received from the receive signal path of the RF circuit 806 and generate the baseband for the transmit signal path of the RF circuit 806 Signal. The baseband processing circuit 804 can interface with the application circuit 802 for generating and processing baseband signals, and for controlling the operation of the RF circuit 806. For example, in some embodiments, the baseband circuit 804 may include a second-generation (2G) baseband processor 804a, a third-generation (3G) baseband processor 804b, a fourth-generation (4G) baseband processor 804c, And/or other baseband processors 804d used in other current generations, under development, or generations to be developed in the future (for example, fifth generation (5G), 6G, etc.). The baseband circuit 804 (for example, one or more of the baseband processors 804a to 804d) can handle many radio control functions that enable communication with one or more radio networks via the RF circuit 806. Radio control functions may include but are not limited to signal modulation/demodulation, encoding/decoding, radio frequency shifting, and so on. In some embodiments, the modulation/demodulation circuit of the baseband circuit 804 may include fast Fourier transform (FFT), precoding, and/or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuit of the baseband circuit 804 may include convolution, tail-convolution, turbo, Viterbi, and/or low-density parity check (LDPC) encoder/decoder functions. The embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, the baseband circuit 804 may include protocol stacking components, such as, for example, EUTRAN protocol components, such as physical (PHY), medium access control (MAC), radio link control (RLC), and packet data convergence. Protocol (PDCP), and/or RRC components. The central processing unit (CPU) 804e of the baseband circuit 804 can be configured to run protocol stacking components for PHY, MAC, RLC, PDCP, and/or RRC layer signal transmission. In some embodiments, the baseband circuit may include one or more audio digital signal processors (DSP) 804f. The sound DSP 804f may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. The components of the baseband circuit can be appropriately combined in a single chip, in a single chip group, or in some embodiments can be configured on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuit 804 and the application circuit 802 may be implemented together, such as, for example, on a system-on-chip (SOC).

In some embodiments, the baseband circuit 804 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 804 can support and evolve the universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), wireless bureau Local area network (WLAN), wireless personal area network (WPAN) communications. Embodiments in which the baseband circuit 804 is configured to support radio communications of more than one wireless protocol may be referred to as a multi-mode baseband circuit.

The radio frequency circuit 806 can use modulated electromagnetic radiation through non-solid media to initiate communication with the wireless network. In various embodiments, the RF circuit 806 may include switches, filters, amplifiers, etc., to facilitate communication with wireless networks. The radio frequency circuit 806 may include a receiving signal path, which may include a circuit for down-converting the radio frequency signal received from the FEM circuit 808 and providing a baseband signal to the baseband circuit 804. The radio frequency circuit 806 may also include a transmission signal path, and the transmission signal path may include a circuit for up-converting the baseband signal provided by the baseband circuit 804 and providing a radio frequency output signal to the FEM circuit 808 for transmission.

In some embodiments, the radio frequency circuit 806 may include a receiving signal path and a transmitting signal path. The receiving signal path of the radio frequency circuit 806 may include a mixer circuit 806a, an amplifier circuit 806b, and a filter circuit 806c. The transmission signal path of the radio frequency circuit 806 may include a filter circuit 806c and a mixer circuit 806a. The radio frequency circuit 806 may also include a synthesizer circuit 806d for synthesizing the used frequency by the mixer circuit 806a of the receiving signal path and the transmitting signal path. In some embodiments, the mixer circuit 806a of the receiving signal path can be configured to down-convert the RF signal received from the FEM circuit 808 based on the synthesized frequency provided by the synthesizer circuit 806d. The amplifier circuit 806b can be configured to amplify the down-converted signal, and the filter circuit 806c can be a low-pass filter (LPF) or a band-pass filter (BPF), which is configured to remove unwanted signals from the down-converted signal. Important news Signal to generate the output baseband signal. The output baseband signal can be provided to the baseband circuit 804 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, although this is not necessary. In some embodiments, the mixer circuit 806a of the receiving signal path may include a passive mixer, although the scope of the embodiment is not limited to this aspect.

In some embodiments, the mixer circuit 806a of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 806d to generate the RF output for the FEM circuit 808 Signal. The baseband signal can be provided by the baseband circuit 804 and can be filtered by the filter circuit 806c. The filter circuit 806c may include a low-pass filter (LPF), although the scope of the embodiment is not limited to this aspect.

In some embodiments, the mixer circuit 806a of the receiving signal path and the mixer circuit 806a of the transmitting signal path may include two or more mixers, and may be arranged to be used for quadrature reduction. Frequency conversion and/or up-conversion. In some embodiments, the mixer circuit 806a of the receiving signal path and the mixer circuit 806a of the transmitting signal path may include two or more mixers, and may be arranged for image cancellation (e.g., Hartley image elimination). In some embodiments, the mixer circuit 806a and the mixer circuit 806a of the receive signal path can be arranged to be used for direct down conversion and/or direct up conversion, respectively. In some embodiments, the mixer circuit 806a of the receiving signal path and the mixer circuit 806a of the transmitting signal path can be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited to this aspect. In a In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the radio frequency circuit 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 804 may include a digital baseband interface for communicating with the radio frequency circuit 806 .

In some dual-mode embodiments, separate radio IC circuits may be provided for processing signals for each frequency spectrum, although the scope of the embodiments is not limited to this aspect.

In some embodiments, the synthesizer circuit 806d may be a fractional N-synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiment is not limited to this aspect (because other types of frequency synthesizers may be suitable) . For example, the synthesizer circuit 806d may be a sigma delta synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

The synthesizer circuit 806d can be configured to synthesize the output frequency used by the mixer circuit 806a of the radio frequency circuit 806 based on the frequency input and the divider control input. In some embodiments, the synthesizer circuit 806d may be a fractional N/N+1 synthesizer.

In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not necessary. Depending on the desired output frequency, the frequency divider control input can be provided by the baseband circuit 804 or the application processor 802. In some embodiments, based on the channel indicated by the application processor 802, the divider control input (eg, N) can be determined from the lookup table.

The synthesizer circuit 806d of the radio frequency circuit 806 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some implementation In an example, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by N or N+1 (for example, based on the carry output) to provide a fractional frequency division ratio. In some example embodiments, the DLL may include a set of serial, adjustable, delay elements, phase detectors, charge pumps, and D-type flip-flops. In these embodiments, the delay elements can be configured to split the VCO cycle into Nd equal packet phases, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help confirm that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuit 806d may be configured to generate the carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, Quadruple) and can be used in conjunction with a quadrature generator and frequency divider circuit to generate several signals at carrier frequencies having several different phases relative to each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the radio frequency circuit 806 may include an IQ/polarity converter.

The FEM circuit 808 may include a receive signal path, which may include configured to operate on the radio frequency signal received from one or more antennas 1010, amplify the receive signal, and provide an amplified version of the receive signal to the radio frequency circuit 806 for further processing Processing circuit. The FEM circuit 808 may also include a transmission signal path, which may include a circuit configured to amplify the transmission provided by the radio frequency circuit 806 and the signal transmitted by one or more of the one or more antennas 1010.

In some embodiments, the FEM circuit 808 may include a TX/RX switch to switch between transmission mode and reception mode operation. The FEM circuit may include a receiving signal path and a transmitting signal path. The receiving signal path of the FEM circuit may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (for example, to the RF circuit 806). The transmission signal path of the FEM circuit 808 may include a power amplifier (PA) used to amplify the input radio frequency signal (for example, provided by the radio frequency circuit 806) and a power amplifier (PA) used to generate a radio frequency signal for subsequent transmission (for example, by one or more antennas). One or more of 1010) one or more filters.

In some embodiments, UE 800 includes a plurality of power saving mechanisms. If the UE 800 is in the RRC_CONNECTED state, where it is still connected to the eNB (because it expects to receive traffic soon), after a period of inactivity, it can enter a state called discontinuous reception mode (DRX). During this state, the device can be powered off within a short time interval, thus saving power.

If there is no data traffic activity for an extended period of time, the UE 800 can transition to stop to the RRC_idle state, where it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. UE800 enters a very low power state, and it implements paging, where it wakes up periodically to listen to the network, and then powers off again. The device cannot receive data in this state; in order to receive data, it switches back to the RRC_connected state.

During periods longer than the paging interval (ranging from a few seconds to a few hours), an additional power saving mode can make a device unavailable for the network. currently In time, the device cannot reach the network at all and can be completely powered off. Any data sent during this time will experience a large delay, and it is assumed that the delay is acceptable.

The present disclosure may include various exemplary embodiments disclosed below.

Example 1 includes a device implemented with a sponsored data connectivity function (SDCF), which includes: a control module for configuring sponsored data connectivity related information (SDCRI); and an interface module for Based at least in part on a network operator's policy, a request associated with the SDCRI is sent to a policy and charging enforcement function (PCEF) or a traffic detection function (TDF).

Example 2 includes the device of Example 1, wherein the network operator's policy further instructs to periodically transmit the request to the PCEF or TDF or to transmit the request to the PCEF or TDF in response to another request from another entity.

Example 3 includes the device of example 1 or example 2, wherein the other entity includes an application service (AS), a service performance disclosure function (SCEF), and/or a policy and charging rules function (PCRF).

Example 4 includes the device of any one of Examples 1 to 3, wherein the interface module is further used to receive a response to the request from the PCEF or the TDF.

Example 5 includes the device of Example 4, where the request includes an add SDCRI request, a modify SDCRI request, and/or a remove SDCRI request, and the response includes an add SDCRI response, a modified SDCRI response, and/or a remove SDCRI Response.

Example 6 includes the device of any one of Examples 1 to 5, wherein configuring the SDCRI includes at least partly based on another received from an application service (AS) associated with a service provider and/or the network operator A request to add, modify or remove the SDCRI.

Example 7 includes the device of any one of Examples 1 to 6, wherein configuring the SDCRI includes adding, modifying, or removing the SDCRI based at least in part on the network operator's policy.

Example 8 includes the device of any one of Examples 1 to 7, wherein the device is further matched with a policy and charging rules function (PCRF).

Example 9 includes the device of any one of Examples 1 to 8, wherein the device is further matched with a Service Performance Exposure Function (SCEF).

Example 10 includes the device of any one of Examples 1 to 9, wherein the SDCRI includes a sponsor identifier, an application service provider and application identifier, and/or the amount of data used to limit the sponsorship of a user’s connectivity or A threshold of time is used.

Example 11 includes the device of any one of Example 1 to Example 10, wherein the SDCRI further includes a charging key allocated by the SDCF.

Example 12 includes a device implemented with a policy and charging enforcement function (PCEF) or a traffic detection function (TDF), which includes: an interface module for at least partly based on a network operator’s policy, from a The Sponsored Data Connectivity Function (SDCF) receives a request associated with Sponsored Data Connectivity Related Information (SDCRI); and a control module for configuring the SDCRI in response to at least part of the request; wherein, the interface The module further sends a response to the request to the SDCF.

Example 13 includes the device of Example 12, wherein the network operator's policy further instructs to transmit the request to the device periodically or to transmit the request to the device in response to another request from another entity.

Example 14 includes the device of example 12 or example 13, wherein when the SDCF is paired with the PCRF, the interface module receives the request from the SDCF in the PCRF.

Example 15 includes the device of any one of Examples 12 to 14, wherein when the SDCF is paired with a service performance disclosure function (SCEF), the interface module receives the request from the SDCF in the SCEF.

Example 16 includes the device of any one of Examples 12 to 15, wherein the SDCRI includes a sponsor identifier, an application service provider, and an application identifier, and/or the amount of data used to limit the connectivity of a user Or a use threshold of time.

Example 17 includes the device of any one of Example 12 to Example 16, wherein the SDCRI further includes a charging key allocated by the SDCF.

Example 18 includes the device of any one of Examples 12 to 17, wherein the request includes an add SDCRI request, a modify SDCRI request, and/or a remove SDCRI request, and the response includes an add SDCRI response, a modified SDCRI response, and / Or a response to the removal of SDCRI.

Example 19 includes the device of Example 18, wherein configuring the SDCRI includes adding, modifying, or removing the SDCRI.

Example 20 includes the equipment of any one of Examples 12 to 19, wherein the interface module is further used to use an Internet Protocol Connectivity Access Network (IP-CAN) communication period as a basis to change from a policy and billing Rule function (PCRF) receiving the SDCRI and enabling the SDRF to provide the SDCRI or the PCRF to provide an indication of the SDCRI; and, the control module is further configured to be based at least in part on the SDCRI provided by the SDRF or the PCRF (if the SDCRI is provided by the PCRF) (Indicated by the instructions) to record and charge for the use of connectivity of a sponsored profile.

Example 21 may include a computer-readable storage medium that stores instructions for execution by a processor to perform SDRF or PCEF operations. When the operations are executed by the processor, they are used to perform the above-mentioned operations. The discussion is any combination of operations.

Example 22 may include equipment for SDRF or PCEF that includes means for performing any of the operations discussed above in any combination.

Although for the purpose of illustration, specific embodiments have been shown and described herein, many alternative and/or equivalent embodiments or implementations calculated for the same purpose can be substituted for those shown and described. The embodiments do not depart from the scope of the disclosure. This application is intended to cover any adaptations or changes of the embodiments discussed herein. Therefore, it is obviously intended that the embodiments described herein are only limited by the scope of the patent application and its equivalents.

100: wireless system

101: Application Service

102: Sponsored data connectivity function

103: Policy and charging rules function

104: Policy and billing enforcement function

105: Flow detection function

106: Gateway

107: Radio Access Network

108: user equipment

110: control module

112: Interface Module

113: Control Module

114: Interface Module

115: control module

116: Interface Module

Claims (23)

A device implemented with a sponsored data connectivity function (SDCF), comprising: a control circuit for configuring sponsored data connectivity related information (SDCRI); and an interface circuit for operating at least partly based on a network The provider’s policy transmits a request associated with the SDCRI to a policy and charging enforcement function (PCEF) or a traffic detection function (TDF), where the device is further matched with a service performance disclosure function (SCEF). For example, the device of the first item of the patent application, wherein the network operator's policy further instructs to send the request to the PCEF or TDF periodically or in response to another request from another entity. For example, the device of item 2 of the scope of patent application, where the other entity includes an application service (AS), the SCEF, and/or a policy and charging rules function (PCRF). For example, the device of the first item in the scope of patent application, wherein the interface circuit is further used to receive a response to the request from the PCEF or the TDF. For example, the device of item 4 of the scope of patent application, where the request includes a request to add SDCRI, a request to modify SDCRI, and/or a request to remove SDCRI, and the response includes a response to add SDCRI, a response to modify SDCRI, and/or a move Except SDCRI responded. For example, the device of the first item of the scope of patent application, where the configuration of the SDCRI includes at least partly based on the relationship with a service provider and/or the network operator An associated application service (AS) receives another request to add, modify or remove the SDCRI. For example, in the device of the first item of the patent application, configuring the SDCRI includes adding, modifying, or removing the SDCRI based at least in part on the network operator's strategy. For example, the device of item 1 in the scope of patent application, wherein the device is further matched with a policy and charging rules function (PCRF). For example, the device in the scope of the patent application, where the SDCRI includes a sponsor identifier, an application service provider and application identifier, and/or a use of data to limit the amount or time of sponsoring a user’s connectivity Critical value. For example, the device of item 1 in the scope of patent application, wherein the SDCRI further includes a charging key allocated by the SDCF. A device implemented with a policy and charging enforcement function (PCEF) or a traffic detection function (TDF), which includes: an interface circuit, which is used at least partly based on a network operator’s strategy to support data connectivity The function (SDCF) receives a request associated with Sponsored Data Connectivity Related Information (SDCRI); and a control circuit for configuring the SDCRI in response at least in part to the request; wherein the interface circuit further responds to the request A response to the request is sent to the SDCF, where the interface circuit is further used to use an Internet Protocol Connectivity Access Network (IP-CAN) communication period as a basis, from a policy and charging rules function (PCRF) Receive the SDCRI and enable the SDCRI provided by the SDRF or an indication of the SDCRI provided by the PCRF; and the control The control circuit is further used to record and charge based at least in part on the use of a sponsored data connectivity by the SDCRI provided by the SDRF or provided by the PCRF as indicated by the instruction. For example, the device in the scope of patent application, where the network operator’s policy further instructs to send the request to the device periodically or in response to another request from another entity. For example, the device of item 11 in the scope of patent application, wherein when the SDCF is matched with the PCRF, the interface circuit receives the request from the SDCF in the PCRF. For example, the device of item 11 in the scope of patent application, wherein when the SDCF is paired with a service performance disclosure function (SCEF), the interface circuit receives the request from the SDCF in the SCEF. For example, the device of item 11 of the scope of patent application, where the SDCRI includes a sponsor identifier, an application service provider and an application identifier, and/or a data amount or time used to limit the amount or time of sponsoring a user’s connectivity Use critical values. For example, the device of item 11 in the scope of patent application, wherein the SDCRI further includes a charging key allocated by the SDCF. For example, the device of item 11 of the scope of patent application, where the request includes a request to add SDCRI, a request to modify SDCRI, and/or a request to remove SDCRI, and the response includes a response to add SDCRI, a response to modify SDCRI, and/or a move Except SDCRI responded. For example, the device of item 17 in the scope of patent application, where configuring the SDCRI includes adding, modifying or removing the SDCRI. A non-transitory computer-readable medium with commands on it. When the commands are executed, a sponsored data connectivity function (SDCF) is used to: configure sponsored data connectivity related information (SDCRI) for Based at least in part on the strategy of a network operator, a request associated with the SDCRI is sent to a policy and charging enforcement function (PCEF) or a traffic detection function (TDF), and further related to a service performance disclosure function ( SCEF) match. For example, the non-transitory computer-readable medium of item 19 of the scope of the patent application, wherein the network operator’s strategy is further used to instruct to send the request to that request periodically or in response to another request from another entity PCEF or TDF, and the other entity includes an application service (AS), the SCEF, and/or a policy and charging rules function (PCRF). For example, the non-transitory computer-readable medium of item 19 of the scope of patent application, when the instructions are executed, further cause the SDCF to receive a response to the request from the PCEF or the TDF. For example, the non-transitory computer-readable media of item 19 of the scope of patent application, where the request includes a request to add SDCRI, a request to modify SDCRI, and/or a request to remove SDCRI, and the response includes a response to add SDCRI, and a modification SDCRI response and/or a SDCRI removal response. For example, the non-transitory computer-readable media of item 19 of the scope of patent application, where configuring the SDCRI includes adding, modifying, or removing the SDCRI, which is based at least in part on operating from a service provider and/or the network Another request received by an application service (AS) associated with the provider; or based on the network operator’s strategy.

Images