3gpp Charging characteristics

本文详细介绍了移动网络中SGSN、MME、S-GW和P-GW等组件如何处理和应用计费特性,包括计费特性的选择、配置及在网络元素间的传递规则,并给出了具体的计费行为示例。

Charging Characteristics can be supplied by the HLR/HSS to the SGSN/MME as part of the subscription information. A subscriber may have charging characteristics assigned to his subscription and/or his subscribed APNs. The SGSN applies a pre‑configured default if no charging characteristics are supplied by the HLR/HSS. The SGSN shall support three different charging characteristics default configurations:

Charging characteristics in SGSN

·       the home default behaviour for subscribers of the SGSN's PLMN;

·       the visiting default behaviour for visitors using a P-GW belonging to the same PLMN as the SGSN;

·       the roaming default behaviour for visitors using a P-GW belonging to their home PLMN.

The SGSN can determine the P-GW PLMN from the operator identifier part of the APN. Optionally the SGSN may support several visiting and roaming default behaviours based on the MNC/MCC combination of the subscriber.

In the case of a home subscriber, the charging characteristics are selected by the SGSN according to the following procedures. For IP CAN bearer specific charging characteristics (i.e. those used for the S-CDRs that are generated for this IP CAN bearer):

·      If the MS requests a particular APN then:

*    If the SGSN accepts this request (i.e. it has been verified against the subscription) then:

§       If it has been matched against the wildcard APN then:

-     If charging characteristics for the wildcard APN are present in the subscription information then they shall be used;

-     If no charging characteristics are present for the wildcard APN but subscription related charging characteristics are present, then they shall be chosen;

-     If neither of the two are present then the SGSN home default shall be applied.

§       If it has been matched against a specific subscribed APN then:

-     If charging characteristics for this APN are present in the subscription information then they shall be used;

-     If no charging characteristics are present for the APN but subscription related charging characteristics are present, then they shall be chosen;

-     If neither of the two are present then the SGSN home default shall be applied.

*    If the SGSN rejects the request then charging characteristics selection does not apply.

·       If the MS does not request an APN then:

*    If the SGSN chooses a subscribed APN then:

§       If charging characteristics for this APN are present in the subscription information then they shall be used;

§       If no charging characteristics are present for the APN but subscription related charging characteristics are present, then they shall be chosen;

§       If neither of the two are present then the SGSN home default shall be applied.

*    If only the wildcard APN is present in the subscription, i.e. the SGSN applies its configured default APN then:

§       If charging characteristics for the wildcard APN are present in the subscription information then they shall be used;

§       If no charging characteristics are present for the wildcard APN but subscription related charging characteristics are present, then they shall be chosen;

§       If neither of the two are present then the SGSN home default shall be applied.

For the non-IP CAN bearer specific CDR types, i.e. the M-CDRs and the SMS CDRs, the SGSN applies the subscription specific charging characteristics, or, if not supplied, it shall choose the home default behaviour as defined above.

In case of subscribers from other PLMNs, the SGSN may be configured to either apply the "home subscriber case" charging characteristics selection procedure defined above, or to ignore charging characteristics provided by the subscriber's HLR, and apply a default configuration instead. If default charging characteristics are selected for the foreign subscriber, then the SGSN shall choose either the visiting or roaming default behaviour for the IP CAN bearer specific charging characteristics, according to the roaming or visiting scenario, as described above. For M-CDRs and SMS CDRs, the operator can configure if the roaming or the visiting behaviour shall be applied, since no P-GW is involved.

Upon activation of a IP CAN bearer, the SGSN forwards the charging characteristics to the P-GW according to the following rules:

·       if charging characteristics were received from the HLR/HSS, then they shall be sent as provided by the HLR/HSS, regardless of the home, visiting, or roaming case, and regardless of whether the SGSN applies the HLR/HSS supplied charging characteristics or chooses to ignore them;

·       if no charging characteristics were received from the HLR/HSS, then the SGSN does not forward any charging characteristics to the P-GW.

Upon activation of a IP CAN bearer, the S4-SGSN forwards the charging characteristics to the S-GW according to the following rules:

·       if charging characteristics were received from the HLR/HSS, then they shall be sent as provided by the HLR/HSS, regardless of the home, visiting, or roaming case, according to the following rules:

o        if charging characteristics for APN are present in the subscription information they shall be forwarded;

o        if no charging characteristics are present for the APN but subscription related charging characteristics is present, they shall be forwarded.

·       if no charging characteristics were received from the HLR/HSS, then the S4-SGSN does not forward any charging characteristics to the S-GW.

Charging characteristics in MME

The MME does not utilize charging characteristics as it does not generate charging information.

Upon activation of a IP CAN  session, the MME forwards the charging characteristics to the S-GW according to the following rules:

·       if charging characteristics were received from the HLR/HSS, then they shall be sent as provided by the HLR/HSS, regardless of the home, visiting, or roaming case according to the following rules:

§         if charging characteristics for the PDN connection (e.g APN) is present in the subscription information it shall be forwarded;

§         if no charging characteristics is present for the PDN connection (e.g APN) but subscription related charging characteristics is present, it shall be forwarded.

·       if no charging characteristics were received from the HLR/HSS, then the MME does not forward any charging characteristics to the S-GW.

 

 

 

 

Charging characteristics in S-GW

The S-GW shall apply charging characteristics to its IP CAN bearers. It shall either apply the S4-SGSN/MME supplied parameters, or it may be configured to ignore the S4-SGSN/MME supplied charging characteristics in any combination of the following cases:

·       visiting case, i.e. the P-GW belongs to same PLMN the subscriber belongs to a different PLMN;

·       roaming case, i.e. the P-GW belongs to a different PLMN;

·       home case, i.e. the subscriber belongs to the same PLMN as the S-GW and P-GW; or

·       unconditionally, i.e. it always ignores the S4-SGSN/MME supplied parameters.

If the S-GW ignores the parameters supplied by the S4-SGSN/MME, it shall nevertheless accept the IP CAN session request. It shall then apply its own pre‑configured charging characteristics as appropriate, i.e. the home, visiting or roamingbehaviour. The S-GW shall support the configuration of one set of default charging characteristics (i.e. home, visiting, roaming).

Upon activation of a IP CAN session, the S-GW forwards the charging characteristics to the P-GW according to the following rules:

·       if charging characteristics were received from the S4-SGSN/MME, then they shall be sent as provided by the S4-SGSN/MME, regardless of the home or visiting case;

·       if no charging characteristics were received from the S4-SGSN/MME, then the S-GW does not forward any charging characteristics to the P-GW.

Charging characteristics in P-GW

The P-GW shall apply charging characteristics to its IP CAN bearers. It shall either apply the SGSN/S-GW supplied parameters, or it may be configured to ignore the SGSN/S-GW supplied charging characteristics in any combination of the following cases:

·       visiting case, i.e. the subscriber belongs to a different PLMN;

·       roaming case, i.e. the subscriber belongs to same PLMN and the SGSN/S-GW belongs to a different PLMN;

·       home case, i.e. the subscriber belongs to the same PLMN as the SGSN/S-GW and P-GW; or

·       unconditionally, i.e. it always ignores the SGSN/S-GW supplied parameters.

If the P-GW ignores the parameters supplied by the SGSN/S-GW, it shall nevertheless accept the IP CAN session request. It shall then apply its own pre‑configured charging characteristics as appropriate, i.e. the home, visiting or roaming behaviour. The P-GW shall support the configuration of one set of default charging characteristics (i.e. home, visiting, roaming) for each of its supported APNs.

Charging characteristics generally

Charging Characteristics consists of a string of 16 bits designated as Behaviours (B), freely defined by Operators, as shown in 3GPP TS 32.298 [41].

For example, one way to define a behaviour, could be to associate it to a specific usage designed according to following guidances:

One usage may consist of a set of trigger profiles associated to CDR types, with following trigger sets, e.g.:

·       S-CDR: activate/deactivate CDRs, time limit, volume limit, maximum number of charging conditions, tariff times;

·       SGW-CDR: same as S-CDR, plus maximum number of SGSN/MME changes;

·       PGW-CDR: same as S-CDR, plus maximum number of S-GW changes;

·       M-CDR: activate/deactivate CDRs, time limit, and maximum number of mobility changes;

·       SMS-MO-CDR: activate/deactivate CDRs;

·       SMS-MT-CDR: active/deactivate CDRs.

·       LCS-MO-CDR.

·       LCS-MT-CDR.

·       LCS-NI-CDR.

In addition to these trigger sets, an optional charging gateway address may also be specified:

-     If the CGF address is configured in the P-GW’s selected charging characteristics behaviour, the P-GW shall apply it for the PGW-CDRs. P-GW applied CGF address is sent to SGSN/S-GW during IP CAN bearer activation.

  • - In the home or visiting case, the S-GW shall apply from P-GW received CGF address to the SGW-CDRs pertaining to this IP CAN bearer. In the roaming case, or if no CGF address is received from the P-GW, the S-GW shall use the CGF address from its own applied charging characteristics behaviour, or, if it does not exist, it uses the default CGF address. There is no need to send CGF address to S4-SGSN/MME as it does not generate charging data.

-     In the home or visiting case, the SGSN shall apply the received CGF address to the S-CDRs pertaining to this IP-CAN bearer. In the roaming case, or if no CGF address is received from the P-GW, then the SGSN shall use the CGF address from its own selected charging characteristics behaviour, or, if it does not exist, use the default CGF address. For M-CDRs and SMS CDRs, the SGSN shall use the CGF address configured in the charging characteristics behaviour that it applies to the respective CDRs, or if no such address is configured then the default CGF shall be used.

Table A.1, A.2 and A.3 are informative examples intended for clarification.

Table A.1: Example of charging characteristics behaviours for SGSN

 

 

S-CDR

M-CDR

Behaviour Index bits

0 - 3

CGF Address

Active

Time limit

Volume limit

Change cond

Tariff times

Active

0

-

Yes

30 min

100 K

2

0-7, 7-12, …

Yes

..

1

100.128.35.20

No

-

-

-

-

No

..

2

-

Yes

10 min

50 K

1

0-24

Yes

..

..

..

..

..

..

..

..

..

..

 

Charging characteristics behaviour in S-GW is used for SGW-CDR generation

Table A.2: Example of charging characteristics behaviours for S-GW

 

 

SGW-CDR

 

 

Behaviour

Index

Bits

0-15

Primary and Secondary CGF

Addresses

Active

Time

Limit

Vol

Limit

Change

Cond.

Tariff times

 

0

100.128.35.20

100.128.35.21

Yes

30 min

100K

2

0-7,

7-12

...

 

1

100.128.35.21

100.128.35.20

No

-

-

-

-

 

2

100.128.35.21

100.128.35.20

Yes

10 min

50K

1

0-24

...

 

           

 

Charging characteristics behaviour in P-GW is used for PGW-CDR generation / and for online charging.

FBC is always active in P-GW. PCRF may provide default charging method to PCEF (P-GW) per IP CAN bearer session. If received by the PCEF, it supersedes the ‘Default charging method’ in charging characteristics behaviour, see TS 23.203 [72] for more information about default charging method. PCRF may also provide CGF/OCS addresses to P-GW per IP CAN bearer session. If received by the P-GW it supersedes the ‘Primary CGF/OCS address’ and ‘Secondary CGF/OCS address’ in charging characteristics behaviour, see TS 23.203 [72] for more information. 

Table A.2: Example of charging characteristics behaviours for P-GW

 

Offline charging (PGW-CDR)

Online charging

Behaviour

Index

Bits

0-15

Default charging method

 

Primary and Secondary CGF

addresses

Active

Time

Limit

Vol

Limit

Change

Cond.

Tariff times

Primary and Secondary OCS

addresses

Active

0

Online

100.128.35.20

100.128.35.21

Yes

30 min

100K

2

0-7,

7-12

...

100.128.35.30

100.128.35.31

Yes

1

Offline

100.128.35.21

100.128.35.20

No

-

-

-

-

-

No

2

Online

/Offline

100.128.35.21

100.128.35.20

Yes

10 min

50K

1

0-24

...

100.128.35.31

100.128.35.30

Yes

 

Other examples for behaviours are:

·       Selection of the applicable idle context purge timer, i.e. use global value or use special value. This feature could be used to distinguish between customers and/or APNs whose IP CAN bearers should be purged after short (e.g. 30 minutes) or long (e.g. 12 hours) periods of inactivity.

·       Use specific charging gateway address (override all other configured/selected CG addresses).

·       Deactivate SMS-MO-CDRs for customers of the own PLMN using pre-configured SMSC addresses.

·       Disable PGW-CDRs for roamers that use the HPLMN P-GW.

·       Allow or inhibit the use of own P-GWs by visitors.

·       Allow or inhibit network triggered QoS change (upgrade and/or downgrade).

The SGSN selects the charging characteristics behaviour for M-CDR generation upon the creation of a MM context. SGSN, S-GW and P-GW select the charging characteristics behaviour upon creation of a IP CAN bearer. Once selected, the charging characteristics behaviour shall be maintained throughout the lifetime of the MM or IP CAN bearer. If the SGSN receives modified subscriber information from the HLR/HSS (e.g. execution of a stand-alone Insert Subscriber Data procedure) which includes changes the charging characteristics, the new charging characteristics shall be applied only to new IP CAN bearers. This implies the following:

-     the S4-SGSN/MME shall not send IP CAN bearer modifications for the existing IP CAN bearer to the S-GW because of charging characteristics change;

-     the SGSN shall not send IP CAN bearer modifications for the existing IP CAN bearer to the P-GW because of charging characteristics change.

代码转载自:https://pan.quark.cn/s/8ce4326d996e 对于在 CentOS 7 系统中修改网卡配置文件后无法使设置生效的情况,经过实践验证,可以通过使用 nmcli 命令来进行调整。完成修改之后,需要重新启动虚拟机以使更改生效,这样操作流程即告完成。如果设置仍然无法生效,则表明虚拟机在启动过程中所获取的 IP 地址配置并非针对 eth0,此时可以对其它网卡的配置文件进行修改或将其移除。在 CentOS 7 系统中,网络配置的管理机制与早期版本存在差异,主要体现为采用了 Network Manager 服务来负责网络接口的管理。在某些情形下,尽管修改了 `/etc/sysconfig/network-scripts` 目录下的 `ifcfg-eth0` 文件,但网络配置却未能即时生效。此类问题的发生通常源于 CentOS 7 采用了不同于以往的配置读取方法。接下来将具体阐述如何借助 nmcli 命令来处理这一挑战。 以 root 用户身份登录系统并打开终端界面。nmcli 是 Network Manager 提供的命令行界面工具,它支持在命令行环境下执行网络连接的建立、编辑、查询及管理任务。针对修改 eth0 网卡配置的需求,可以遵循以下步骤进行操作: 1. 导航至 `/etc/sysconfig/network-scripts` 目录: ``` cd /etc/sysconfig/network-scripts ``` 2. 检查该目录内是否存在 `ifcfg-eth0.bak` 文件,该备份文件可能是先前调整配置时遗留下来的,若存在可能造成冲突。若发现该文件,可以选择将其删除: ``` [root@localhost netw...
代码转载自:https://pan.quark.cn/s/46fd08fb879c 网管教程 从入门到精通软件篇 ★一。★详尽的xp修复控制台指令及其应用!!! 放入xp(2000)的光盘,安装时选择R,执行修复! Windows XP(涵盖 Windows 2000)的控制台指令是在系统遭遇某些意外状况时的一种极具效用的诊断、检测以及恢复系统功能的工具。笔者确实一直期望能够将这方面的指令进行归纳,此次由老范辛苦整理了这份极具价值的秘籍。 Bootcfg bootcfg 命令用于启动配置与故障恢复(对大多数计算机而言,即 boot.ini 文件)。 带有特定参数的 bootcfg 命令仅在运用故障恢复控制台时方可使用。能够在命令行界面下运用带有不同参数的 bootcfg 命令。 用法: bootcfg /default 设定默认引导选项。 bootcfg /add 向引导清单中增添 Windows 安装。 bootcfg /rebuild 重复整个 Windows 安装流程并让用户选择需添加的项目。 注意:运用 bootcfg /rebuild 之前,应先借助 bootcfg /copy 命令备份 boot.ini 文件。 bootcfg /scan 探查用于 Windows 安装的全部磁盘并展示结果。 注意:这些结果被静态存储,并用于当前会话。若在当前会话期间磁盘配置发生变动,为获取更新的探查结果,必须先重启计算机,然后再次探查磁盘。 bootcfg /list 列示引导清单中已有的项目。 bootcfg /disableredirect 在启动引导程序中禁用重定向。 bootcfg /redirect [ PortBaudRrate] |[ useBio...
代码下载链接: https://pan.quark.cn/s/fc524f791b68 AA制程,即Active Alignment,被理解为主动对准,是一种用于确定零部件装配中相对位置的方法。在摄像头封装阶段,涉及图像传感器、镜座、马达、镜头、线路板等多个部件的重复组装,而传统的封装设备如CSP及COB等,均是依据设备设定的参数进行零部件的移动装配,因而零部件的叠加误差会逐渐增大,最终在摄像头上表现为拍照最清晰的位置可能偏离画面中心、四边清晰度不均等现象。伴随智能手机和其他高端电子产品的普及,摄像头模组的性能正日益受到重视。高分辨率、卓越的低光表现以及稳定视频输出是现代用户所期望的。在摄像头模组的制造环节,各部件的精准定位对成像质量具有决定性作用。因此,一种名为“AA制程”(Active Alignment)的前沿技术被开发出来,成为摄像头精密对准的核心技术。 AA制程,即Active Alignment,是一种在摄像头封装过程中应用的主动对准方法。该方法在多个组件装配阶段发挥作用,涵盖图像传感器、镜座、马达、镜头和线路板等部件。传统的封装方式,例如CSP(Chip Scale Package)和COB(Chip On Board),依赖于设备预设的参数进行组装,但随着组件数量的增加,误差也会累积,最终影响摄像头的表现。例如在成像质量上可能出现中心位置偏移、四角清晰度不一致等问题。 AA制程技术的核心在于实时监测与主动调整。在组装过程中,它借助先进的检测设备持续监控半成品的状态,并根据实时信息对组装部件进行精确修正,从而显著降低装配误差。通过这种技术,能够确保摄像头模组中各组件的相对位置准确无误,从而使得最终的成像效果更加稳定,特别是在中心区域和四角的清晰度上...
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值