WO2010043095A1 - Procédé de traitement d’échec d’inscription d’un utilisateur et unité de gestion de mobilité associée - Google Patents
Procédé de traitement d’échec d’inscription d’un utilisateur et unité de gestion de mobilité associée Download PDFInfo
- Publication number
- WO2010043095A1 WO2010043095A1 PCT/CN2008/073761 CN2008073761W WO2010043095A1 WO 2010043095 A1 WO2010043095 A1 WO 2010043095A1 CN 2008073761 W CN2008073761 W CN 2008073761W WO 2010043095 A1 WO2010043095 A1 WO 2010043095A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- failure
- user
- registration
- network
- reason
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
Definitions
- the present invention belongs to the field of packet domain evolution in a mobile communication system, and in particular, to a method for user registration failure processing and a mobility management entity.
- SAE System Architecture Evolution
- E-RAN Evolved RAN
- the network element included in the E-RAN is an eNodeB (Evolved NodeB) that provides radio resources for terminal access.
- eNodeB Evolved NodeB
- HSS Home Subscriber Server
- a home subscriber server that permanently stores user subscription data.
- PDN Packet Data Network
- E-Packet Core Evolved packet network, which improves lower latency and allows more wireless access systems to access, including the following network elements:
- MME Mobility Management Entity: A control plane function entity that temporarily stores user data. It is responsible for managing and storing the terminal UE context (such as UE/user ID, mobility management status, user security parameters, etc.) for the user. Assigning a temporary identity, when the UE is camped on the tracking area or the network is responsible for authenticating the user; processing all non-access stratum messages between the MME and the UE; triggering paging at the SAE.
- the terminal UE context such as UE/user ID, mobility management status, user security parameters, etc.
- the gateway is a user plane entity responsible for user plane data routing processing and terminating downlink data of the UE in idle state. Manage and store the SAE bearer context of the UE, such as IP bearer service parameters and network internal routing information. It is the anchor point of the internal user plane of the 3GPP system.
- a user can only have one Serving GW at a time;
- PDN GW Packet data network gateway, responsible for the UE accessing the PDN gateway, assigning the user IP address, and being the mobility anchor of 3GPP and non-3GPP access systems. Users can access multiple PDN GWs at the same time.
- the Policy and Charging Rule Functionality (PCRF) function entity which generates Qos (Quality of Service) rules for controlling user data transmission based on service information, user subscription information, and operator configuration information. And billing rules.
- the functional entity can also control the establishment and release of bearers in the access network.
- Serving GW and PDN GW may be one.
- the user's packet domain operation can be selected in two steps, that is, the service is activated after registration.
- the service is activated after registration.
- the user can be attached only in the packet domain without being activated. Since the user's registration process does not involve the interaction of user service information, the reason for the user registration failure may not involve the user service information.
- the process of activating a bearer is added to the attaching process, that is, once the user registers, a bearer must be activated for subsequent services, and it is specified that if the activation of the bearer process fails, the entire user will be caused.
- the process of activating a bearer necessarily involves interaction with the business information that will be used, including business usage rights. In particular, there is a process of refusing registration due to business reasons. Possible business reasons include non-bearing network failures such as user arrears and user service usage restrictions.
- the network can only set all the failure reasons to network failure, such as network failure, network busy, etc., which will cause users to timely and accurately understand the true failure reason of registration, and the user cannot The reason for the failure of the network return is to make the correct follow-up decision.
- the failure information obtained by the user is related to the bearer network provided by the operator, the user may incorrectly attribute the failure of the registration to the bearer network, thereby increasing the probability of the user complaining about the network.
- the technical problem to be solved by the present invention is to provide a method for user registration failure processing and a mobility management entity, so that in the SAE network, the user cannot solve the note in time and accurately.
- the present invention discloses a method for user registration failure processing, including:
- the terminal determines that if the registration fails due to the non-bearer network, the mobility management entity sends a reject message to the terminal through the evolved base station, where the reject message carries a field indicating the reason for the failure.
- the registration failure of the non-bearing network causes that the packet data network gateway or the serving gateway finds that the user owes a fee to refuse registration in the charging;
- the policy and charging rule function entity After the mobility management entity interacts with the policy and charging rule function entity, the policy and charging rule function entity refuses to register; or
- the circuit switched domain refuses to register.
- the mobility management entity When the packet data network gateway or the service gateway finds that the user owes a fee for registration in the charging, the mobility management entity carries a field indicating that the reason for the failure is a user's arrears in the refusal message.
- the mobility management entity After the mobility management entity interacts with the policy and charging rule function entity, when the policy and charging rule function entity refuses to register, the mobility management entity carries a field indicating that the failure reason is the user service usage permission restriction in the rejection message.
- the mobility management entity After the mobility management entity interacts with the traditional circuit switched domain, when the circuit switched domain refuses to register, the mobility management entity carries a field indicating that the reason for the failure is the user service usage restriction in the reject message.
- the field indicating the reason for the failure carried in the rejection message is a new dedicated field.
- the new dedicated field is a protocol configuration option.
- the present invention also discloses a mobility management entity MME for user registration failure processing.
- the MME determines to send a reject message to the evolved base station if the registration fails due to the non-bearer network.
- the reject message carries a field indicating the reason for the failure.
- the MME and the system architecture play If the packet data network gateway or the service gateway interacts with the network, if the user is found to be in arrears in the charging, it is determined that the registration fails due to the non-bearing network, and the rejection message carries the failure reason for the user's arrears. Field; or
- the MME interacts with the policy and charging rule function entity in the system architecture evolution network, if the user service usage permission limit is found, it is determined that the registration fails due to the non-bearer network, and the failure is carried in the rejection message. The reason is that the user service uses the restricted field; or
- the MME interacts with the circuit switching domain in the system architecture evolution network, if the user service usage permission restriction is found, it is determined that the registration failure occurs due to the non-bearer network, and the failure message is carried in the rejection message as the user service.
- the field indicating the reason for failure carried in the reject message is a new dedicated field.
- the invention solves the problem that the non-bearing network failure information is carried in the registration failure notification message, thereby solving the problem that the SAE network cannot make a correct subsequent decision because the user cannot timely and accurately understand the true cause of the registration failure.
- FIG. 1 is a schematic diagram of a SAE architecture in the prior art
- FIG. 2 is a flow chart showing a failure of a user registration process in an embodiment of the present invention. Preferred embodiment of the invention
- the registration rejection message carries a field indicating the reason for the failure, thereby solving the problem that the SAE network cannot make a correct subsequent decision because the user cannot timely and accurately understand the true cause of the registration failure.
- the problem is further described in detail below with reference to the accompanying drawings and specific embodiments.
- Step 200 when the UE needs to register in the SAE network, the UE sends an attach request to the eNodeB;
- Step 201 the eNodeB sends an attach request message to the MME;
- Step 202 The MME, the SGW, the PGW, the eNodeB, the PDN, the PCRF, and the UE perform message interaction on an intermediate process in the registration process.
- Step 203 If the registration fails during the registration process, the MME determines that the current registration failure reason is a non-bearing network cause.
- the registration failure caused by the non-bearing network causes the registration to fail due to reasons other than the bearer network itself, that is, the registration fails due to reasons other than the MME, the SGW, the PGW, and the HSS itself.
- the non-bearing network causes the registration failure to occur.
- the PGW or the SGW rejects the user after the user owes the fee, or the PCRF rejects the MME and the PCRF, or the CS domain rejects after the MME interacts with the traditional circuit-switched CS domain.
- the registration failure message is sent according to the existing process.
- Step 204 The MME sends a reject message to the eNodeB, where the reject message carries a field indicating the reason for the failure, and the field indicating the reason for the failure is used to indicate the real reason for the registration failure, such as the user arrears, the user service usage permission limit, and the like.
- the user service usage permission limit includes multiple failure reasons returned by the service layer;
- the field carried in the refusal message indicates that the reason for the failure is the user's arrears. If the PCRF rejects the MME and the PCRF, the field carried in the refusal message indicates the failure. The reason is that the user service usage permission is restricted. If the traditional circuit switched CS domain is rejected after the MME interacts with the PGW, the field carried in the reject message indicates that the failure reason is the user service usage permission restriction.
- the PCRF rejects the field, and the field carried in the reject message indicates that the cause of the failure may be the specific failure reason returned by the RCRF, for example, "user authorization failure” or "illegal authorized user", etc., if the MME interacts with the traditional circuit-switched CS domain. If the post-CS domain is rejected, the field carried in the reject message indicates that the reason for the failure may be the specific failure reason returned by the CS domain.
- the field indicating the reason for the failure is a newly added field, and the newly added field may be an existing field, and the protocol configuration option (PCO) is set.
- An MME for user registration failure processing is applied to a SAE network.
- the MME when communicating with the network element such as the SGW, the PGW, and the PCRF in the SAE network, performs a message exchange with the intermediate process in the registration process, and determines that the user registration fails due to the non-bearer network, that is, the MME, the SGW, the PGW, the HSS, and the like.
- the MME sends a reject message to the eNodeB.
- the message carries a new field indicating the reason for the failure.
- the field indicating the reason for the failure is used to indicate the real cause of the registration failure, such as the user.
- the arrears, user service usage rights restrictions, etc. Further, the user service usage rights restriction may also include multiple failure reasons returned by the business layer.
- the registration failure caused by the non-bearer network includes: the PGW or the SGW rejects the user's arrears after charging, or the PCRF rejects after the MME interacts with the PCRF, or the traditional circuit switched CS domain refuses when the MME interacts with the PGW. .
- the reject message carries a field indicating that the reason for the failure is the user's arrears
- the refusal message carries a field indicating that the failure reason is the user service usage restriction.
- the refusal message carries a field indicating that the failure reason is the user service usage restriction.
- the present invention carries the field indicating the reason for the failure in the registration failure notification message, thereby solving the failure reason that the non-bearing network fails to be carried when the non-bearing network fails to register in the SAE network.
- the user cannot timely and accurately understand the reason for the true failure of the registration, and the user cannot make a correct follow-up decision based on the failure reason returned by the network.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
L’invention relève du domaine de paquets dans un système évolué de communication mobile et concerne un procédé et une unité de gestion de mobilité de traitement d’échec d’inscription d’un utilisateur. Selon ledit procédé, au cours de l’inscription d’un réseau d’évolution d’architecture de système (SAE), si un terminal juge que l’inscription a échoué faute d'un réseau de prise en charge, l’entité de gestion de mobilité envoie, via une station de base évoluée, un message de refus à un terminal, ledit message de refus portant un champ exprimant les causes de l’échec. L’invention permet de résoudre, dans un réseau SAE, le problème posé par l’incapacité de l’utilisateur à trouver à temps et de manière précise les véritables causes d'échec d’une inscription, l'empêchant de prendre les bonnes décisions.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNA2008101672890A CN101577963A (zh) | 2008-10-17 | 2008-10-17 | 一种用户注册失败后的处理方法 |
CN200810167289.0 | 2008-10-17 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010043095A1 true WO2010043095A1 (fr) | 2010-04-22 |
Family
ID=41272706
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2008/073761 WO2010043095A1 (fr) | 2008-10-17 | 2008-12-26 | Procédé de traitement d’échec d’inscription d’un utilisateur et unité de gestion de mobilité associée |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101577963A (fr) |
WO (1) | WO2010043095A1 (fr) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102811448B (zh) * | 2012-07-31 | 2017-12-15 | 中兴通讯股份有限公司 | 一种错误码识别方法及移动终端 |
CN102833782A (zh) * | 2012-08-23 | 2012-12-19 | 中兴通讯股份有限公司 | 一种错误码信息获取方法、装置及系统 |
CN109257712A (zh) * | 2018-11-02 | 2019-01-22 | Oppo广东移动通信有限公司 | 信息识别方法、电子装置及计算机可读存储介质 |
CN111885515A (zh) * | 2020-07-03 | 2020-11-03 | 麦腾物联网技术有限公司 | 短信欠费的判断方法、装置和系统 |
CN114513844B (zh) * | 2022-01-20 | 2023-11-14 | Tcl通讯科技(成都)有限公司 | 网络注册方法、装置、存储介质及电子设备 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1960565A (zh) * | 2005-11-01 | 2007-05-09 | 华为技术有限公司 | 演进的移动通信网络及终端向演进的3g接入网络注册方法 |
CN1997207A (zh) * | 2006-01-06 | 2007-07-11 | 上海原动力通信科技有限公司 | 移动通信系统中用户设备开机注册接入的方法 |
CN101102607A (zh) * | 2007-08-08 | 2008-01-09 | 中兴通讯股份有限公司 | 一种ip多媒体子系统ims中处理用户订阅的方法 |
US20080014930A1 (en) * | 2006-05-31 | 2008-01-17 | Nokia Corporation | Managing user profile information |
CN201057653Y (zh) * | 2006-04-19 | 2008-05-07 | 美商内数位科技公司 | 用于支持路由区域更新的设备 |
CN101227352A (zh) * | 2007-01-15 | 2008-07-23 | 华为技术有限公司 | 用户终端紧急注册到ip连接接入网络的方法及系统 |
-
2008
- 2008-10-17 CN CNA2008101672890A patent/CN101577963A/zh active Pending
- 2008-12-26 WO PCT/CN2008/073761 patent/WO2010043095A1/fr active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1960565A (zh) * | 2005-11-01 | 2007-05-09 | 华为技术有限公司 | 演进的移动通信网络及终端向演进的3g接入网络注册方法 |
CN1997207A (zh) * | 2006-01-06 | 2007-07-11 | 上海原动力通信科技有限公司 | 移动通信系统中用户设备开机注册接入的方法 |
CN201057653Y (zh) * | 2006-04-19 | 2008-05-07 | 美商内数位科技公司 | 用于支持路由区域更新的设备 |
US20080014930A1 (en) * | 2006-05-31 | 2008-01-17 | Nokia Corporation | Managing user profile information |
CN101227352A (zh) * | 2007-01-15 | 2008-07-23 | 华为技术有限公司 | 用户终端紧急注册到ip连接接入网络的方法及系统 |
CN101102607A (zh) * | 2007-08-08 | 2008-01-09 | 中兴通讯股份有限公司 | 一种ip多媒体子系统ims中处理用户订阅的方法 |
Also Published As
Publication number | Publication date |
---|---|
CN101577963A (zh) | 2009-11-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA3145304C (fr) | Reselection de reseau lors d'un sinistre | |
CA3132854C (fr) | Radiomessagerie de dispositif sans fil par le biais d'un reseau sans fil | |
US11533401B2 (en) | Charging policy information for a packet data unit session in a wireless network | |
US11039018B2 (en) | Charging control with SMF and PCF | |
US8949950B2 (en) | Selection of successive authentication methods | |
US20100048161A1 (en) | Method, system and apparatuses thereof for realizing emergency communication service | |
US20110021196A1 (en) | Access class based picocell policy enforcement | |
WO2011054299A1 (fr) | Procédé et système pour obtenir des informations de terminal de communication de type machine | |
WO2009086734A1 (fr) | Procédé pour sélectionner une entité à fonction de règles de politique et de facturation dans le scénario sans itinérance | |
US20110182244A1 (en) | Method for supporting context management by home node-b | |
US8582553B2 (en) | Policy management in a roaming or handover scenario in an IP network | |
WO2011023091A1 (fr) | Procédé et système de gestion du repli vers une transmission vocale à commutation de circuits dans un réseau | |
TW201513701A (zh) | 在通信網路中用於緊急處理的方法及裝置 | |
US9629179B2 (en) | Method and device for processing local access connection | |
WO2010105462A1 (fr) | Procédé de traitement du rattachement d'un équipement d'utilisateur, entité de gestion de la mobilité et équipement d'utilisateur associé | |
WO2010043095A1 (fr) | Procédé de traitement d’échec d’inscription d’un utilisateur et unité de gestion de mobilité associée | |
WO2010051696A1 (fr) | Procédé et système de libération d’une ressource radio | |
WO2011018020A1 (fr) | Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection | |
WO2012146093A1 (fr) | Procédé et système destinés à réaliser un traitement de service | |
WO2014071790A1 (fr) | Procédé, dispositif et système destinés à un contrôle de politique d'une convergence fixe-mobile | |
WO2007085196A1 (fr) | Procédé et système d'enregistrement dans un sous-système multimédia ip | |
EP4195864A1 (fr) | Équipement utilisateur (ue) | |
WO2010091632A1 (fr) | Procédé de gestion d'informations de passerelle de réseau de données par paquets (pdn gw), et équipement et système correspondants | |
WO2010037287A1 (fr) | Procédé, système et élément de réseau, serveur pour notifier des informations d'activité d'équipement utilisateur | |
WO2012129997A1 (fr) | Procédé et dispositif pour traiter une connexion d'accès à un réseau local |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08877372 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 08877372 Country of ref document: EP Kind code of ref document: A1 |