WO2012000361A1 - 一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器 - Google Patents

一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器 Download PDF

Info

Publication number
WO2012000361A1
WO2012000361A1 PCT/CN2011/074808 CN2011074808W WO2012000361A1 WO 2012000361 A1 WO2012000361 A1 WO 2012000361A1 CN 2011074808 W CN2011074808 W CN 2011074808W WO 2012000361 A1 WO2012000361 A1 WO 2012000361A1
Authority
WO
WIPO (PCT)
Prior art keywords
imei
rnc
identity
response message
user
Prior art date
Application number
PCT/CN2011/074808
Other languages
English (en)
French (fr)
Inventor
李群
赵明鹤
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to JP2013516974A priority Critical patent/JP5636100B2/ja
Priority to EP11800106.4A priority patent/EP2584814B1/en
Publication of WO2012000361A1 publication Critical patent/WO2012000361A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices

Definitions

  • the present invention relates to a wireless communication tracking method and a radio network controller (RNC) thereof, and more particularly to an international mobile device identity of an RNC tracking user equipment (UE, User Equipment) in a third generation mobile communication system (IMEI, The International Mobile) Station Equipment Identity ) method and its RNC.
  • RNC radio network controller
  • the third generation of mobile communication technology provides a platform for developing more services, and end users can enjoy data services while using traditional voice services. In this way, higher requirements are imposed on network and terminal performance, and network configuration needs to be continuously optimized to improve terminal performance.
  • the alarms and performance counters in the existing network operation and maintenance analysis methods reflect the network operation status based on the perspective of the network system equipment, but cannot reflect the specific details of each call of different terminal equipment types in the network; Type, based on the user granularity grouping, perform KPI statistics and probability distribution analysis.
  • the radio network controller acts as the intermediate link of the network side system equipment, and is responsible for the radio resources of the Uu interface and the ground transmission of the Iub, Iu, and Iur interfaces. Resource management and distribution.
  • RNC Radio Network Controller
  • IMSI International Mobile Subscriber Identification Number
  • RNC can record and track;
  • the RNC is aimed at users of different terminal types throughout the network. Therefore, the network performance and the performance of different users' IMSIs in the network, RNC can generate user call logs by collecting relevant data. Achieve statistics on both the end user and the network, and analyze the network health.
  • ⁇ is one of the UE's logos in the network, also known as the serial number. Its maximum function is to help identify the identity of the mobile phone.
  • 3GPP 25.003 is divided into two types: ⁇ and IMEISV; where ⁇ is composed of 15 digits, as shown in Figure 1, where the Type Allocation Code (TAC) occupies 6 digits; The code (FAC, Final Assembly Code) occupies 2 digits; the serial number (SNR, Serial Number) occupies 6 digits, the unique serial number in the TAC type allocation code of a certain model; and one idle digit is transmitted by the terminal, generally The situation is used for check digits. This check digit verifies the 14-digit number consisting of TAC, FAC, and SNR.
  • TAC Type Allocation Code
  • FAC Final Assembly Code
  • SNR Serial Number
  • the IMEISV consists of the IMEI and the software version number (SVN, Software Version Number).
  • the SVN indicates the software version number of the IMEI device.
  • the structure of the IMEISV is shown in Figure 2. The first 14 digits in the structure are the IMEI structure. The bit check bit, the last 2 is the number to increase the SVN.
  • SVN is assigned by the manufacturer.
  • the IMEI consists of 15 or 16 digits.
  • TAC means the manufacturer's model of the terminal;
  • FAC means the factory where the terminal is finally assembled.
  • Each factory has its own special code, which is not the code of the country. Therefore, the FAC can be considered as the code name of the terminal origin.
  • the RNC When the RNC collects the user call process information, it cannot directly obtain the IMEI information. If the RNC can record the IMEI information and refer to the user log generated during the user call, the pin can be used. Statistics are performed on the manufacturer, model, and version information of the terminal device. Thereby obtaining the performance of different terminal device types in the network. Supervise terminal version upgrades, technical improvements and troubleshooting. Summary of the invention
  • the main purpose of the present invention is to provide a method for the RNC to track the UE IMEI and its RNC, and to solve the problem that the RNC cannot directly obtain the IMEI information.
  • a method for tracking a UE IMEI including: in a process of establishing a radio resource control (RRC) connection between an RNC and a UE, when a signaling connection of a user call is successful, the RNC is The UE obtains the IMEI of the UE in the identity response message of the non-access stratum identity request message. The RNC saves the acquired IMEI to the user log generated by the UE call process.
  • RRC radio resource control
  • the signaling connection succeeds in that the Iu interface packet domain signaling connection is successful, or the Iu interface circuit domain signaling connection is successful.
  • the signaling connection succeeds in that the Iu interface packet domain signaling connection is successful; the RNC obtains the IMEI of the UE from the identity response message of the UE to the non-access stratum identity request message, and includes:
  • the RNC simulates a non-access stratum identity request message and sends it to the UE;
  • the UE After receiving the non-access stratum identity request message, the UE returns an identity response message containing the IMEI to the RNC;
  • the RNC obtains the IMEI from the identity response message.
  • the signaling connection succeeds in that the Iu interface circuit domain signaling connection is successful; the RNC obtains the IMEI of the UE from the identity response message of the UE to the non-access stratum identity request message, and includes:
  • the RNC simulates a non-access stratum identity request message and sends it to the UE;
  • the UE After receiving the non-access stratum identity request message, the UE returns an identity response message containing the IMEI to the RNC;
  • the RNC obtains the IMEI from the identity response message
  • the RNC reads the uplink sequence number filled in by the UE in the identity response message, and sends the uplink sequence number to the core network (CN, Core Network) sends a null operation compensation message of the uplink sequence number.
  • CN Core Network
  • the method further includes: before the RNC obtains the IMEI of the UE from the identity response message of the UE to the non-access stratum identity request message, the method further includes:
  • the RNC detects the cause of the user call establishment and determines that it needs to be obtained in this call.
  • the RNC obtains the IMEI of the UE from the identity response message of the UE to the non-access stratum identity request message, including:
  • the CN sends the non-access stratum identity request message to the UE;
  • the UE After receiving the non-access stratum identity request message, the UE returns an identity response message containing the IMEI to the RNC;
  • the RNC obtains the IMEI from the identity response message
  • the RNC then sends the identity response message to the core network.
  • the method further includes: after the RNC saves the acquired IMEI to the user log generated by the UE call process, the method further includes:
  • the network operation and maintenance analysis system generates an IMSI and IMEI comparison table for user system maintenance based on the IMEI information; or
  • the network operation and maintenance analysis system updates the IMSI and IMEI checklists for user system maintenance based on the IMEI information.
  • an RNC for tracking a UE IMEI includes: an obtaining module and a saving module, where
  • the obtaining module in the process of establishing an RRC connection between the RNC and the UE, is used to obtain the IMEI of the UE from the identity response message of the non-access stratum identity request message by the UE after the signaling connection of the user is successful;
  • the obtaining module further includes: a requesting module and a receiving module; wherein, the requesting module is configured to simulate a non-access stratum identity request message, and send the message to the UE;
  • a receiving module configured to receive an IMEI-containing identity response message returned by the UE
  • the RNC further includes: a reading module and a sending module, when the signaling connection of the user call is successful, the Iu interface circuit domain signaling connection is successful;
  • a reading module configured to read an uplink sequence number filled in by the UE in the identity response message; and send, by the RNC, the null operation compensation message of the uplink sequence number to the CN.
  • the RNC further includes: a detecting module, configured to detect a cause of the user call establishment, and start the acquiring module after determining that the IMEI needs to be acquired in the current call.
  • the RNC obtains the IMEI of the UE from the identity response message of the UE to the non-access stratum identity request message; and then the RNC acquires
  • the IMEI is saved to the user generated by the UE call process, so that the network operation and maintenance analysis system can track the specific details of each call of the IMEI reflecting different terminal device types according to the user call log, and perform grouping based on the terminal type.
  • Statistical analysis of key performance indicators are used to be used to the terminal device types.
  • the RNC acquires the IMEI process of the UE to initiate the process of distinguishing the call type.
  • the RNC needs to detect whether the user call establishment reason determines whether to start acquiring the IMEI, and try not to increase the call delay and the air interface load.
  • the process of the RNC acquiring the IMEI of the UE can also prevent the air interface load from being transmitted by intercepting the CN IMEI.
  • the RNC After obtaining the IMEI, the RNC saves the IMEI to the user log of the user's call process, and the user log records the user characteristic information and the behavior statistics of the call process in detail.
  • the network operation and maintenance analysis system can generate or update the maintained IMSI and IMEI comparison table based on the user identification information of the user log.
  • the network operation and maintenance analysis system associates the user ID of the user log with the comparison table.
  • Network and user equipment identity such as: manufacturer, terminal type and version, statistical analysis of angles, improve the accuracy of network analysis system, and facilitate network maintenance.
  • FIG. 2 is a structural diagram of an IMEISV in the prior art
  • FIG. 3 is a flow chart of a method for tracking UE IMEI according to the present invention.
  • FIG. 4 is a flow chart of obtaining an IMEI of a packet domain of a RNC emulation non-access stratum message in the present invention
  • FIG. 5 is a flow chart of obtaining an IMEI of a circuit domain of a RNC emulation non-access stratum message in the present invention
  • FIG. 6 is a structural block diagram of a connection between an RNC that tracks a UE IMEI and a CN and a UE according to the present invention. detailed description
  • the present invention is based on a third generation mobile wireless communication system suitable for distributed systems and centralized systems.
  • the RNC starts the acquisition of the IMEI process.
  • the RNC saves the obtained IMEI to the user log generated by the user's call process.
  • the user log records the user characteristic information and the behavior statistics of the call process in detail, and uses the network operation and maintenance analysis system to store the stored user logs from the perspective of the network and the user terminal.
  • Statistical analysis specifically, based on the cell, the base station generates a network user failure cause distribution rate; based on the IMEI-owned terminal device type, performs probability distribution statistics of failure problems, and detects whether different terminal device types are frequent transmission terminal devices with some failure problems.
  • the RNC starts to obtain the IMEI process of the UE according to the configuration of the application scenario.
  • the application scenario includes collecting all the types of call types of the user, distinguishing the call type process, and collecting the CNIMEI process.
  • Set The process of collecting all user call types means that: the UE requests the user to call the RNC to establish a connection, and the RNC starts to acquire the IMEI;
  • Differentiating the call type process Startup set refers to:
  • the RNC needs to detect whether the user call establishes the reason to decide whether to start acquiring the IMEI.
  • the RNC can specify a specific process such as the location area update process, the routing area update process, and the attach request process to start the IMEI. , try not to increase the call delay and air interface load;
  • the process of intercepting CN IMEI means that: CN initiates the process of acquiring IMEI signaling.
  • the RNC performs non-access stratum decoding, detects the UE feedback to the CN IMEI response message, reads the IMEI information, and saves it.
  • the set is not: RNC does not start the IMEI process.
  • the method for tracking UE IMEI includes:
  • the RNC saves the acquired IMEI to the user log generated by the UE call process.
  • the signaling connection in the S11 is successful, and the Iu interface packet domain signaling connection is successful, or the Iu interface circuit domain signaling connection is successful.
  • the RNC simulates the non-access stratum to obtain the IMEI signaling process to distinguish between the circuit i or the packet i or. If one i or the IMEI is successfully acquired, the other i or the triggering of the IMEI process is no longer triggered, thereby reducing the call delay and the air interface load. .
  • the scenario in which all user call type processes are collected in the packet domain is: The signaling connection in the packet domain of the Iu interface is successful. In case,
  • the RNC directly simulates the non-access stratum Identity Request message through the Uu interface to request the downlink direct transmission message of the IMEI to the UE; As shown in FIG. 4, if the CN initiates the authentication process, the RNC needs to complete the Uu interface security mode process, and then the RNC directly simulates the non-access stratum Identity Request message through the Uu interface to request the IMEI downlink direct transmission message to the UE;
  • the UE After receiving the non-access layer Identity Request message, the UE considers that it is a CN request, and directly sends an uplink direct transmission message carrying the IMEI response Identity Response message to the RNC;
  • the RNC obtains the IMEI from the uplink direct transmission message of the response Response message of the UE;
  • the RNC receives the uplink direct transmission message for non-access stratum decoding and acquires the IMEI.
  • the scenario of distinguishing the call type process initiation set is: In the case that the Iu interface packet domain signaling connection is successful, the RNC detects the cause of the user call establishment and determines that the IMEI needs to be obtained in the current call.
  • the RNC directly simulates the non-access layer Identity Request message through the Uu interface to request the downlink direct transmission message of the IMEI to the UE;
  • the RNC needs to complete the Uu interface security mode process, and then the RNC directly simulates the downlink direct transmission message of the non-access layer Identity Request message to the UE through the Uu interface;
  • the UE After receiving the non-access layer Identity Request message, the UE considers that it is a CN request, and directly sends an uplink direct transmission message carrying the IMEI response Identity Response message to the RNC;
  • the RNC obtains the IMEI from the uplink direct transmission message of the response Response message of the UE;
  • the RNC receives the uplink direct transmission message for non-access stratum decoding and acquires the IMEI.
  • the scenario of the CN IMEI collection process is as follows: In the case that the Iu interface packet domain signaling connection is successful, the RNC obtains the IMEI of the UE through the CN from the identity response message of the UE to the non-access stratum Identity Request message, including the following sub-steps:
  • the CN downlinks the non-access stratum Identity Response message to the UE; After receiving the non-access stratum Identity Response message, the UE returns an identity response message containing the IMEI to the RNC.
  • the RNC obtains the IMEI from the identity response message
  • the RNC then sends the identity response message to the CN.
  • the RNC simulates the process of the non-access stratum acquiring IMEI through the circuit domain, which is divided into the following cases:
  • the RNC directly simulates the non-access layer Identity Request message through the Uu interface to request the downlink direct transmission message of the IMEI to the UE;
  • the RNC needs to complete the Uu interface security mode process, and then the RNC directly simulates the non-access layer Identity Request message through the Uu interface to request the IMEI downlink direct transmission message to the UE;
  • the UE After receiving the non-access layer Identity Request message, the UE considers that it is a CN request, and directly sends an uplink direct transmission message carrying the IMEI response Identity Response message to the RNC;
  • the RNC obtains the IMEI from the uplink direct transmission message of the response response message of the UE; the RNC receives the uplink direct transmission message for non-access stratum decoding and acquires the IMEI;
  • the RNC reads the response of the UE.
  • the uplink sequence number filled in by the UE in the uplink direct transmission message of the Identity Response message;
  • RNC simulates the non-access stratum with the uplink serial number of the mobile management empty (MM NULL, Mobility
  • the RNC needs to compensate the uplink sequence number generated by the UE in the IMEI process, and inserts an MM NULL message to carry the uplink sequence number generated by the UE after intercepting the Identity Response message. Passed to the CN update.
  • the scenario of distinguishing the call type process startup set is:
  • the signaling connection in the III interface circuit domain is successful.
  • the RNC detects the cause of the user call establishment and determines that the IMEI needs to be acquired in the current call;
  • the RNC directly simulates the non-access layer Identity Request message through the Uu interface to request the downlink direct transmission message of the IMEI to the UE;
  • the RNC needs to complete the Uu interface security mode process, and then the RNC directly simulates the non-access layer Identity Request message through the Uu interface to request the IMEI downlink direct transmission message to the UE;
  • the UE After receiving the non-access layer Identity Request message, the UE considers that it is a CN request, and directly sends an uplink direct transmission message carrying the IMEI response Identity Response message to the RNC;
  • the RNC obtains the IMEI from the uplink direct transmission message of the response response message of the UE; the RNC receives the uplink direct transmission message for non-access stratum decoding and acquires the IMEI;
  • the RNC reads the response of the UE.
  • the uplink sequence number filled in by the UE in the uplink direct transmission message of the Identity Response message;
  • the RNC simulates the non-access stratum with the MM NULL signaling of the uplink sequence number, and sends the signaling to the CN update through the circuit domain Iu interface.
  • the scenario of the CN IMEI collection process is as follows: In the case that the signaling connection of the Iu interface circuit domain is successful, the RNC obtains the IMEI of the UE from the identity response message of the UE to the non-access stratum Identity Request message through the CN, including the following sub-steps:
  • CN forwards the non-access stratum Identity Response message to the UE directly;
  • the UE After receiving the non-access stratum Identity Response message, the UE returns an identity response message containing the IMEI to the RNC.
  • the RNC obtains the IMEI from the identity response message
  • the RNC then sends the identity response message to the CN.
  • the network operation and maintenance analysis system After the RNC saves the acquired IMEI to the user log generated by the UE call process, the network operation and maintenance analysis system generates or updates the IMSI and IMEI for user system maintenance according to the IMEI information. Corresponding table; and the associated KPI statistics and analysis are generated from the network and user device identity through the network user log.
  • the user device identity includes: a manufacturer, a terminal type, and a software version.
  • the user log contains the user identifier and signaling trace of the key behavior.
  • the user identifier may be one or more combinations of IMSI, IMEI, Packet Temperate Mobile Identity (P-TMSI), Temporary Mobile Station Identity (TMSI), and the like;
  • the signaling tracking of key behaviors includes: handover of the user's call process, radio resource reconfiguration, and Iub interface, Uu interface, and Iu interface signaling related to cell update.
  • the RNC further includes: an acquiring module and a saving module, where
  • the obtaining module is configured to: when the RNC establishes an RRC connection with the UE, the UE obtains the IMEI of the UE from the identity response message of the non-access layer Identity Request message after the user connects the signaling success message;
  • a saving module configured to save the acquired IMEI to a user log generated by the UE calling process.
  • the acquiring module may further include: a requesting module and a receiving module, where the RNC may further include: a sending module and a detecting module;
  • a requesting module configured to simulate a non-access stratum Identity Request message, and sent to the UE; and a receiving module, configured to receive an IMEI-containing identity response message returned by the UE;
  • a reading module configured to read an uplink sequence number filled in by the UE in the identity response message
  • a sending module configured to send, to the CN, the null operation compensation message of the uplink sequence number filled in by the UE in the identity response message read by the UE.
  • the detecting module is configured to detect a cause of the user call establishment, and after determining that the IMEI needs to be acquired in the current call, start the acquiring module to obtain the IMEI.
  • the RNC system After the interaction of the modules, the RNC system generates a user call log and a user equipment identity correspondence table, so that the network operation and maintenance analysis system tracks the specific details of each call of the IMEI reflecting different terminal device types according to the user call log, and Different user equipments perform network maintenance. It is to be understood that the specific implementation of the invention is not limited to the description. It will be apparent to those skilled in the art that the present invention may be made without departing from the spirit and scope of the invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器 技术领域
本发明涉及无线通信跟踪方法及其无线网络控制器 （RNC , Radio Network Control ), 特别涉及第三代移动通信系统中 RNC 跟踪用户设备 ( UE, User Equipment )国际移动设备身份 ( IMEI, The International Mobile station Equipment Identity ) 的方法及其 RNC。 背景技术
第三代移动通讯技术提供了一个发展更多业务的平台， 终端用户在使 用传统的语音业务的同时可享受数据业务。 这样， 对网络和终端性能都提 出了更高的要求， 需要不断地优化网络配置、 提升终端性能。
目前网络运维分析方法中， 常用的一些分析手段， 比如： 路测、 性能 统计等， 都是一种事后型分析手段， 这些手段的缺点是： 无法真实还原已 经发生事件的原状。 举个例子来说， 某重要客户投诉说他掉话了， 网络优 化工程师到现场进行测试， 很常见也很糟糕的情况是问题不复现， 无从下 手分析和解决； 当进一步查看操作维护中心的关键性能指标 （KPI, Key Performance Indicator ) 的统计时， 可能指标会艮好， 由于系统并不记录用 户当时通话时的详细情况， 因此， 也就无法定位问题的所在。
此外， 现有网络运维分析方法中告警和性能计数器均是基于网络系统 设备的角度反映网络运行状况， 而无法反映网络中不同终端设备类型的每 一个呼叫的具体细节； 也无法进行基于终端设备类型， 在用户粒度分组基 础上， 进行 KPI的统计以及概率分布分析。
无线网络控制器（ RNC , Radio Network Control )作为网络侧系统设备 的中间环节， 负责 Uu接口的无线资源以及 Iub、 Iu、 Iur接口的地面传输承 载资源管理和分配。 用户呼叫过程中， 用户的国际移动用户识别码（IMSI, International Mobile Subscriber Identification Number )、 信令和数据 载建 立以及传输过程， RNC都能进行记录跟踪； 况且 RNC面向的是全网不同终 端类型用户， 因此网络性能以及不同用户的 IMSI在网络中的表现， RNC 是可以通过釆集相关数据， 生成用户呼叫日志。 达到面向终端用户和网络 两个角度进行 ΚΡΙ统计， 分析网络运行状况。
ΙΜΕΙ是 UE在网内的标识之一， 也被称为串号， 它的最大功能是用来 协助辨别手机身份。
3GPP 25.003关于 ΙΜΕΙ定义分成两种： ΙΜΕΙ和 IMEISV; 其中， ΙΜΕΙ 组成结构如附图 1所示， 它由 15位数字组成， 其中， 类型分配码（ TAC, Type Allocation Code )占用 6位数字；装配码 （ FAC , Final Assembly Code) 占用 2位数字； 序列号 （SNR, Serial Number)占用 6位数字， 某种型号的 TAC 类型分配码中唯一序列号； 还有一位空闲数字位由终端传送， 一般情 况用于校验位。 该校验位对 TAC、 FAC以及 SNR组成的 14位数字进行校 验。
IMEISV由 IMEI和软件版本号（ SVN, Software Version Number )组成， 其中， SVN指示了 IMEI设备的软件版本号， IMEISV的结构如附图 2所示： 结构中的前 14位数字就是 IMEI结构，一位校验位，后 2为数字增加了 SVN。
SVN由生产商分配。
因此， IMEI由 15位或 16位数字组成。 一般地， TAC表示终端的厂家 型号； FAC 的含义是指终端最后完成装配时是在哪一家工厂， 每一家工厂 都有它特别的代号， 它并不是哪个国家制造的代号。 所以 FAC也就可以认 为是终端产地的代号。
RNC在釆集用户呼叫过程信息时， 不能直接获取 IMEI信息； 若 RNC 能将 IMEI信息记录下来， 并参照用户呼叫过程中生成的用户日志， 就可针 对终端设备对应的厂家、 型号以及版本信息进行统计。 从而获得不同终端 设备类型在网络中的表现。 督促终端版本升级、 技术改进和故障解决。 发明内容
本发明的主要目的在于提一种 RNC跟踪 UE IMEI的方法及其 RNC, 解决 RNC无法直接获取 IMEI信息的问题。
根据本发明的一个方面， 提供了一种跟踪 UE IMEI的方法， 包括： 在 RNC与 UE建立无线资源控制（ RRC, Radio Resource Control )连接过程中， 当用户呼叫的信令连接成功后， RNC从 UE对非接入层身份请求消息的身 份响应消息中获取 UE的 IMEI; RNC将获取的 IMEI保存至所述 UE呼叫 过程生成的用户日志中。
其中， 所述信令连接成功为 Iu口分组域信令连接成功、 或为 Iu接口 电路域信令连接成功。
其中， 所述信令连接成功为 Iu接口分组域信令连接成功； 所述 RNC 从 UE对非接入层身份请求消息的身份响应消息中获取 UE的 IMEI , 包括：
RNC模拟非接入层身份请求消息， 并下发给 UE;
UE收到所述非接入层身份请求消息后， 向 RNC返回含有 IMEI的身 份响应消息；
RNC从所述身份响应消息中获取所述 IMEI。
其中， 所述信令连接成功为 Iu口电路域信令连接成功； 所述 RNC从 UE对非接入层身份请求消息的身份响应消息中获取 UE的 IMEI, 包括：
RNC模拟非接入层身份请求消息， 并下发给 UE;
UE收到所述非接入层身份请求消息后， 向 RNC返回含有 IMEI的身 份响应消息；
RNC从所述身份响应消息中获取所述 IMEI;
RNC读取所述身份响应消息中 UE填写的上行序号，并向核心网（ CN, Core Network )发送该上行序号的空操作补偿消息。
其中， 在 RNC从 UE对非接入层身份请求消息的身份响应消息中获 取 UE的 IMEI之前， 该方法进一步包括：
RNC 对用户呼叫建立原因进行检测， 并确定需要在本次呼叫中获取
IMEI。
其中，所述 RNC从 UE对非接入层身份请求消息的身份响应消息中获 取 UE的 IMEI, 包括：
CN将非接入层身份请求消息下发给 UE;
UE收到所述非接入层身份请求消息后， 向 RNC返回含有 IMEI的身 份响应消息；
RNC从所述身份响应消息中获取所述 IMEI;
RNC再将所述身份响应消息上发给核心网。
其中， RNC将获取的 IMEI保存到在所述 UE呼叫过程生成的用户日 志之后， 该方法进一步包括：
网络运维分析系统根据 IMEI信息生成用户系统维护用的 IMSI 和 IMEI对照表； 或者，
网络运维分析系统根据 IMEI信息更新用户系统维护用的 IMSI 和 IMEI对照表。
根据本发明的另一方面， 提供了一种跟踪 UE IMEI的 RNC, 该 RNC 包括： 获取模块及保存模块， 其中；
获取模块，在 RNC与 UE建立 RRC连接过程中，用于当用户呼叫的信 令连接成功后， 从 UE对非接入层身份请求消息的身份响应消息中获取 UE 的 IMEI;
保存模块， 用于将获取的 IMEI保存至所述 UE呼叫过程生成的用户日 志中。 其中， 所述获取模块进一步包括： 请求模块及接收模块； 其中， 请求模块， 用于模拟非接入层身份请求消息， 并下发给 UE;
接收模块， 用于接收 UE返回的含有 IMEI的身份响应消息；
以及， 当所述用户呼叫的信令连接成功为 Iu接口电路域信令连接成功 时， 该 RNC进一步包括： 读取模块及发送模块； 其中，
读取模块， 用于读取所述身份响应消息中 UE填写的上行序号； 发送模块， RNC向 CN发送所述上行序号的空操作补偿消息。
其中， 该 RNC进一步包括： 检测模块， 用于对用户呼叫建立原因进行 检测， 并在确定需要在本次呼叫中获取 IMEI后， 启动所述获取模块。
与现有技术相比较， 本发明的有益效果在于：
1、 本发明在 RNC与 UE建立 RRC连接过程中， 当用户呼叫的信令连 接成功后， RNC从 UE对非接入层身份请求消息的身份响应消息中获取 UE 的 IMEI; 然后 RNC将获取的 IMEI保存至所述 UE呼叫过程生成的用户曰 志中， 这样， 网络运维分析系统根据用户呼叫日志， 可以跟踪 IMEI反映不 同终端设备类型的每一个呼叫的具体细节， 进行基于终端类型分组基础上 的关键性能指标统计分析。
2、 RNC获取 UE的 IMEI的过程启动区分呼叫类型的釆集过程， RNC 需要检测用户呼叫建立原因判决是否启动获取 IMEI, 尽量不额外增加呼叫 延时以及空口负荷。
3、 RNC获取 UE的 IMEI的过程还可以通过侦听 CN IMEI釆集， 防止 信令重复发送导致空口负载。
本发明 RNC获取 IMEI后， 将其保存至用户呼叫过程的用户日志中， 用户日志详细记录用户特征信息和呼叫过程的行为统计信息。 网络运维分 析系统能够基于用户日志的用户标识信息，生成或更新维护的 IMSI和 IMEI 对照表。 网络运维分析系统通过用户日志的用户标识和对照表关联， 从网 络和用户设备身份， 比如： 厂家、 终端类型和版本， 角度进行统计分析， 提高网络分析系统准确度， 便于网络维护。 附图说明
图 1是现有技术中 IMEI的结构图；
图 2是现有技术中 IMEISV的结构图；
图 3是本发明跟踪 UE IMEI方法的流程图；
图 4是本发明中 RNC模拟非接入层消息的分组域的获取 IMEI的流程 图；
图 5是本发明中 RNC模拟非接入层消息的电路域的获取 IMEI的流程 图；
图 6是本发明跟踪 UE IMEI的 RNC与 CN和 UE连接的结构框图。 具体实施方式
以下结合附图对本发明的优选实施例进行详细说明， 应当理解， 以下 所说明的优选实施例仅用于说明和解释本发明， 并不用于限定本发明。
本发明基于第三代移动无线通信系统， 适用于分布式系统和集中式系 统。 RNC启动获取 IMEI过程。 RNC将获得的 IMEI保存至用户呼叫过程 生成的用户日志中， 用户日志详细记录用户特征信息和呼叫过程的行为统 计信息， 并通过网络运维分析系统对存储的用户日志从网络和用户终端角 度进行统计分析， 具体地， 基于小区、 基站生成网络用户失败原因分布率； 基于 IMEI归属的终端设备类型进行失败问题的概率分布统计，检测不同终 端设备类型是否为某些失败问题的频发终端设备。
具体操作时， RNC 根据釆集应用场景配置开启获取 UE的 IMEI过程， 其中， 应用场景包括对所有用户呼叫类型过程都釆集、 区分呼叫类型过程 启动釆集、 侦听 CNIMEI釆集过程以及不釆集等； 对所有用户呼叫类型过程都釆集是指： UE只要请求和 RNC建立连接 的用户呼叫过程， RNC就会启动获取 IMEI;
区分呼叫类型过程启动釆集是指： RNC需要检测用户呼叫建立原因判 决是否启动获取 IMEI, 例如： RNC可指定在位置区更新过程、 路由区更新 过程和附着请求过程才启动釆集 IMEI等特定过程，尽量不额外增加呼叫延 时以及空口负荷；
侦听 CN IMEI釆集过程是指： CN启动了获取 IMEI信令过程。 RNC 进行非接入层解码，侦听到 UE反馈给 CN IMEI响应消息，读取 IMEI信息 并保存。
不釆集是指： RNC不启动釆集 IMEI过程。
下面结合附图对技术方案的优选实施例作进一步的详细描述， 如图 3 所示， 跟踪 UE IMEI的方法包括：
S11 : 在 RNC与 UE建立 RRC连接过程中， 当用户呼叫的信令连接成 功后， RNC从 UE对非接入层身份请求（ Identity Request )消息的身份响应 消息中获取 UE的 IMEI;
S12: RNC将获取的 IMEI保存至所述 UE呼叫过程生成的用户日志中。 其中， S 11中信令连接成功为 Iu接口分组域信令连接成功、 或 Iu接口 电路域信令连接成功。 RNC模拟非接入层获取 IMEI的信令过程区分电路 i或和分组 i或，如果一个 i或获取 IMEI成功后，则另一个 i或不再触发获取 IMEI 过程， 从而减少呼叫延时以及空口负载。
下面针对实际应用中 RNC模拟非接入层通过分组域获取 IMEI的过程 作详细的介绍， 在分组域中对所有用户呼叫类型过程都釆集的场景为： 在 Iu接口分组域信令连接成功的情况下，
如果 CN未启动鉴权过程， 则 RNC通过 Uu接口直接主动模拟非接入 层 Identity Request消息请求 IMEI的下行直传消息给 UE; 如图 4所示， 如果 CN启动鉴权过程， 则 RNC还需要完成 Uu接口安 全模式过程，然后 RNC通过 Uu接口直接主动模拟非接入层 Identity Request 消息请求 IMEI的下行直传消息给 UE;
UE收到所述非接入层 Identity Request消息后， 认为是 CN请求， 直接 将携带 IMEI的响应 Identity Response消息的上行直传消息发送给 RNC;
RNC从 UE的响应 Identity Response消息的上行直传消息中获取所述 IMEI;
RNC收到上行直传消息进行非接入层解码并获取 IMEI。
区分呼叫类型过程启动釆集的场景为： 在 Iu接口分组域信令连接成功 情况下， RNC在对用户呼叫建立原因进行检测并确定需要在本次呼叫中获 取 IMEI。
如果 CN未启动鉴权过程， 则 RNC通过 Uu接口直接主动模拟非接入 层 Identity Request消息请求 IMEI的下行直传消息给 UE;
如果 CN启动鉴权过程， 则 RNC还需要完成 Uu接口安全模式过程， 然后 RNC通过 Uu接口直接主动模拟非接入层 Identity Request消息的下行 直传消息给 UE;
UE收到所述非接入层 Identity Request消息后， 认为是 CN请求， 直接 将携带 IMEI的响应 Identity Response消息的上行直传消息发送给 RNC;
RNC从 UE的响应 Identity Response消息的上行直传消息中获取所述 IMEI;
RNC收到上行直传消息进行非接入层解码并获取 IMEI。
侦听 CN IMEI釆集过程的场景为：在 Iu接口分组域信令连接成功情况 下， RNC从 UE对非接入层 Identity Request消息的身份响应消息中通过 CN 获取 UE的 IMEI包括以下子步骤：
CN把非接入层 Identity Response消息下行直传给 UE; UE收到所述非接入层 Identity Response消息后 ,向 RNC返回含有 IMEI 的身份响应消息；
RNC从所述身份响应消息中获取所述 IMEI;
RNC再将所述身份响应消息上发给 CN。
实际应用中， RNC模拟非接入层通过电路域获取 IMEI的过程， 分为 以下几种情况：
在电路域中对所有用户呼叫类型过程都釆集的场景为： 在 Iu接口电路 域信令连接成功情况下，
如果 CN未启动鉴权过程， 则 RNC通过 Uu接口直接主动模拟非接入 层 Identity Request消息请求 IMEI的下行直传消息给 UE;
如图 5所示， 如果 CN启动鉴权过程， 则 RNC还需要完成 Uu接口安 全模式过程，然后 RNC通过 Uu接口直接主动模拟非接入层 Identity Request 消息请求 IMEI的下行直传消息给 UE;
UE收到所述非接入层 Identity Request消息后， 认为是 CN请求， 直接 将携带 IMEI的响应 Identity Response消息的上行直传消息发送给 RNC；
RNC从 UE的响应 Identity Response消息的上行直传消息中获取所述 IMEI; RNC收到上行直传消息进行非接入层解码并获取 IMEI;
RNC读取 UE的响应 Identity Response消息的上行直传消息中 UE填写 的上行序号；
RNC模拟非接入层带所述上行序号的移动管理空（ MM NULL, Mobility
Management NULL )信令， 并通过电路域 Iu接口将该信令发给 CN更新。
这里， RNC为了对齐 CN上行信令序号， 需要将本侧模拟获取 IMEI 流程中多让 UE生成的上行序号补偿掉，并在截获 Identity Response消息后， 插入一条 MM NULL消息， 携带 UE生成的上行序号传递给 CN更新。
区分呼叫类型过程启动釆集的场景为： 在 III接口电路域信令连接成功 情况下， RNC在对用户呼叫建立原因进行检测并确定需要在本次呼叫中获 取 IMEI;
如果 CN未启动鉴权过程， 则 RNC通过 Uu接口直接主动模拟非接入 层 Identity Request消息请求 IMEI的下行直传消息给 UE;
如果 CN启动鉴权过程， 则 RNC还需要完成 Uu接口安全模式过程， 然后 RNC再通过 Uu接口直接主动模拟非接入层 Identity Request消息请求 IMEI的下行直传消息给 UE;
UE收到所述非接入层 Identity Request消息后， 认为是 CN请求， 直接 将携带 IMEI的响应 Identity Response消息的上行直传消息发送给 RNC;
RNC从 UE的响应 Identity Response消息的上行直传消息中获取所述 IMEI; RNC收到上行直传消息进行非接入层解码并获取 IMEI;
RNC读取 UE的响应 Identity Response消息的上行直传消息中 UE填写 的上行序号；
RNC模拟非接入层带所述上行序号的 MM NULL信令， 并通过电路域 Iu接口将该信令发给 CN更新。
侦听 CN IMEI釆集过程的场景为：在 Iu接口电路域信令连接成功情况 下， RNC从 UE对非接入层 Identity Request消息的身份响应消息中通过 CN 获取 UE的 IMEI包括以下子步骤：
CN把非接入层 Identity Response消息下行直传给 UE;
UE收到所述非接入层 Identity Response消息后，向 RNC返回含有 IMEI 的身份响应消息；
RNC从所述身份响应消息中获取所述 IMEI;
RNC再将所述身份响应消息上发给 CN。
RNC将获取的 IMEI保存至所述 UE呼叫过程生成的用户日志之后，网 络运维分析系统根据 IMEI信息生成或更新用户系统维护用的 IMSI和 IMEI 对照表； 并通过全网用户日志从网络和用户设备身份角度生成关联 KPI统 计和分析， 这里， 所述用户设备身份包括： 厂家、 终端类型以及软件版本。
其中， 用户日志包含用户标识和关键行为的信令跟踪。
用户标识可以为 IMSI、 IMEI、分组临时移动用户识别码（ P-TMSI,Packet Temperate Mobile Subscription Identity )、 临时移动台标识符 （ TMSI , Temporary Mobile Station Identity )等其中之一或多个组合；
关键行为的信令跟踪包括： 用户呼叫过程的切换、 无线资源重配以及 小区更新相关的 Iub接口、 Uu接口和接 Iu口信令。
根据本发明的另一方面， 提供了一种跟踪 UE IMEI的 RNC, RNC与 CN及 UE连接的结构框图， 如图 6所示， RNC进一步包括： 获取模块及保 存模块， 其中；
获取模块，在 RNC与 UE建立 RRC连接过程中，用于当用户呼叫的信 令连接成功后， 从 UE对非接入层 Identity Request消息的身份响应消息中 获取 UE的 IMEI;
保存模块， 用于将获取的 IMEI保存至所述 UE呼叫过程生成的用户日 志中。
所述获取模块还可以进一步包括： 请求模块及接收模块， 所述 RNC还 可以进一步包括： 发送模块以及检测模块； 其中，
请求模块， 用于模拟非接入层 Identity Request消息， 并下发给 UE; 接收模块， 用于接收 UE返回的含有 IMEI的身份响应消息；
读取模块， 用于读取所述身份响应消息中 UE填写的上行序号； 发送模块，用于向 CN发送读取的所述身份响应消息中 UE填写的上行 序号的空操作补偿消息。
检测模块， 用于对用户呼叫建立原因进行检测， 并在确定需要在本次 呼叫中获取 IMEI后， 启动获取模块来获取 IMEI。 通过各模块的相互作用， 使 RNC系统生成用户呼叫日志和用户设备身 份对应表， 这样， 网络运维分析系统根据用户呼叫日志， 跟踪 IMEI反映不 同终端设备类型的每一个呼叫的具体细节， 并针对不同的用户设备进行网 络维护。 明， 不能认定本发明的具体实施只局限于这些说明。 对于本发明所属技术 领域的普通技术人员来说， 在不脱离本发明构思的前提下， 还可以做出若 干简单推演或替换， 都应当视为属于本发明的保护范围。

Claims

权利要求书
1、 一种跟踪用户设备（UE ) 国际移动设备身份（IMEI ) 的方法， 其 特征在于， 该方法包括以下步骤：
在无线网络控制器 ( RNC )与 UE建立无线资源控制 ( RRC )连接过程 中， 当用户呼叫的信令连接成功后， RNC从 UE对非接入层身份请求消息 的身份响应消息中获取 UE的 IMEI;
RNC将获取的 IMEI保存至所述 UE呼叫过程生成的用户日志中。
2、 根据权利要求 1所述的方法， 其特征在于， 所述信令连接成功为 Iu 接口分组域信令连接成功、 或为 Iu接口电路域信令连接成功。
3、 根据权利要求 1所述的方法， 其特征在于， 所述信令连接成功为 Iu 接口分组域信令连接成功； 所述 RNC从 UE对非接入层身份请求消息的身 份响应消息中获取 UE的 IMEI , 包括：
RNC模拟非接入层身份请求消息， 并下发给 UE;
UE收到所述非接入层身份请求消息后，向 RNC返回含有 IMEI的身份 响应消息；
RNC从所述身份响应消息中获取所述 IMEI。
4、 根据权利要求 1所述的方法， 其特征在于， 所述信令连接成功为 Iu 接口电路域信令连接成功； 所述 RNC从 UE对非接入层身份请求消息的身 份响应消息中获取 UE的 IMEI , 包括：
RNC模拟非接入层身份请求消息， 并下发给 UE;
UE收到所述非接入层身份请求消息后，向 RNC返回含有 IMEI的身份 响应消息；
RNC从所述身份响应消息中获取所述 IMEI;
RNC读取所述身份响应消息中 UE填写的上行序号， 并向核心网发送 所述上行序号的空操作补偿消息。
5、根据权利要求 3或 4所述的方法， 其特征在于， 在 RNC从 UE对非 接入层身份请求消息的身份响应消息中获取 UE的 IMEI之前， 该方法进一 步包括：
RNC 对用户呼叫建立原因进行检测， 并确定需要在本次呼叫中获取 IMEI。
6、根据权利要求 2所述的方法， 其特征在于， 所述 RNC从 UE对非接 入层身份请求消息的身份响应消息中获取 UE的 IMEI, 包括：
核心网将非接入层身份请求消息下发给 UE;
UE收到所述非接入层身份请求消息后，向 RNC返回含有 IMEI的身份 响应消息；
RNC从所述身份响应消息中获取所述 IMEI;
RNC将所述身份响应消息上发给核心网。
7、 根据权利要求 1所述的方法， 其特征在于， RNC将获取的 IMEI保 存至所述 UE呼叫过程生成的用户日志之后， 该方法进一步包括：
网络运维分析系统根据 IMEI信息生成用户系统维护用的国际移动用 户识别码 ( IMSI )和 IMEI对照表； 或者，
网络运维分析系统根据 IMEI信息更新用户系统维护用的 IMSI和 IMEI 对照表。
8、 一种跟踪 UE IMEI的无线网络控制器， 其特征在于， 该无线网络控 制器包括： 获取模块及保存模块， 其中；
获取模块，在 RNC与 UE建立 RRC连接过程中，用于当用户呼叫的信 令连接成功后， 从 UE对非接入层身份请求消息的身份响应消息中获取 UE 的 IMEI;
保存模块， 用于将获取的 IMEI保存至所述 UE呼叫过程生成的用户日 志中。
9、 根据权利要求 8所述的无线网络控制器， 其特征在于， 所述获取模 块进一步包括： 请求模块及接收模块； 其中，
请求模块， 用于模拟非接入层身份请求消息， 并下发给 UE;
接收模块， 用于接收 UE返回的含有 IMEI的身份响应消息； 当所述信令连接成功为 III接口电路域信令连接成功时， 该无线网络控 制器进一步包括： 读取模块及发送模块； 其中，
读取模块， 用于读取所述身份响应消息中 UE填写的上行序号； 发送模块， 用于向 CN发送所述上行序号的空操作补偿消息。
10、 根据权利要求 9所述的无线网络控制器， 其特征在于， 该无线网 络控制器进一步包括：
检测模块， 用于对用户呼叫建立原因进行检测， 并在确定需要在本次 呼叫中获取 IMEI后， 启动所述获取模块。
PCT/CN2011/074808 2010-06-28 2011-05-27 一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器 WO2012000361A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2013516974A JP5636100B2 (ja) 2010-06-28 2011-05-27 ユーザ装置の国際移動体装置アイデンティティのトラッキング方法及びトラッキング無線ネットワーク制御装置
EP11800106.4A EP2584814B1 (en) 2010-06-28 2011-05-27 Method and radio network control for tracking the international mobile station equipment identity of user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010211050.6 2010-06-28
CN201010211050.6A CN102300223B (zh) 2010-06-28 2010-06-28 一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器

Publications (1)

Publication Number Publication Date
WO2012000361A1 true WO2012000361A1 (zh) 2012-01-05

Family

ID=45360318

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/074808 WO2012000361A1 (zh) 2010-06-28 2011-05-27 一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器

Country Status (4)

Country Link
EP (1) EP2584814B1 (zh)
JP (1) JP5636100B2 (zh)
CN (1) CN102300223B (zh)
WO (1) WO2012000361A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111163456A (zh) * 2019-12-11 2020-05-15 浙江极智通信科技股份有限公司 一种信息获取方法及系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2887728A1 (en) * 2013-12-19 2015-06-24 Telefonaktiebolaget L M Ericsson (publ) Technique for performance management in a mobile communications network
CN105306213B (zh) * 2015-09-23 2019-07-09 中国联合网络通信集团有限公司 用户信息处理方法及系统
CN109660982B (zh) * 2017-10-11 2020-10-16 大唐移动通信设备有限公司 一种进行标识采集的方法和装置
CN114828060A (zh) * 2021-01-21 2022-07-29 中兴通讯股份有限公司 无线网络数据匹配方法、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101018413A (zh) * 2007-01-17 2007-08-15 上海华为技术有限公司 终端的性能统计方法、接入网设备及无线网络
CN101087465A (zh) * 2007-07-25 2007-12-12 华为技术有限公司 一种接入事件统计方法及装置
CN100417112C (zh) * 2005-01-25 2008-09-03 中兴通讯股份有限公司 一种自适应匹配信令连接的方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100381006C (zh) * 2000-02-11 2008-04-09 诺基亚公司 用于获得通信网络中被监控用户的识别信息的方法和系统
US7460862B2 (en) * 2003-01-29 2008-12-02 Nokia Corporation Solution for managing user equipment version information in a mobile communications network
US20060094478A1 (en) * 2004-11-04 2006-05-04 Lg Electronics Inc. Mobile power handling method and apparatus
EP2160049A1 (en) * 2008-08-27 2010-03-03 Nokia Siemens Networks S.p.A. Method of subscribers of mobile terminals identification managed by a controller in A 2G/3G radio access network
JP5462266B2 (ja) * 2008-09-26 2014-04-02 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 移動体通信ネットワーク

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100417112C (zh) * 2005-01-25 2008-09-03 中兴通讯股份有限公司 一种自适应匹配信令连接的方法
CN101018413A (zh) * 2007-01-17 2007-08-15 上海华为技术有限公司 终端的性能统计方法、接入网设备及无线网络
CN101087465A (zh) * 2007-07-25 2007-12-12 华为技术有限公司 一种接入事件统计方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111163456A (zh) * 2019-12-11 2020-05-15 浙江极智通信科技股份有限公司 一种信息获取方法及系统
CN111163456B (zh) * 2019-12-11 2022-07-15 浙江极智通信科技股份有限公司 一种信息获取方法及系统

Also Published As

Publication number Publication date
EP2584814A1 (en) 2013-04-24
EP2584814B1 (en) 2018-05-02
JP2013531438A (ja) 2013-08-01
CN102300223A (zh) 2011-12-28
CN102300223B (zh) 2016-06-29
EP2584814A4 (en) 2017-03-08
JP5636100B2 (ja) 2014-12-03

Similar Documents

Publication Publication Date Title
CN103026779B (zh) 用户设备休眠
US10285209B2 (en) Optimizing processing method and apparatus for D2D service
US20150023180A1 (en) Method and apparatus for obtaining terminal minimization of drive-tests data
KR101813058B1 (ko) 이동통신 시스템의 가입자의 단말들의 시그널링 처리방법
CA2509150A1 (en) A process method about the service connection between the wireless local area network and user terminal
CN105516986A (zh) 一种检测伪基站的方法、终端、数据处理器以及系统
WO2011116732A2 (zh) 移动终端接入无线网络的方法、设备及通信系统
WO2016161832A1 (zh) 一种通过托管sim卡实现移动通信的系统及相应的方法
CN104244189A (zh) 一种td-lte集群故障弱化通信系统中的寻呼方法
WO2016177106A1 (zh) 专用核心网的选择方法和装置
WO2013143228A1 (zh) 一种缩减心跳消息的方法及系统
WO2012000361A1 (zh) 一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器
US20130150008A1 (en) Method and apparatus for signaling trace
KR101291962B1 (ko) 정보 추적 제어 방법 및 코어망 망 요소
JP6884209B2 (ja) サービス注文方法および装置
CN100396135C (zh) 一种宽带码分多址系统中rab指配故障的上报方法
CN203039916U (zh) 一种客户端直接访问互联网的apn系统
US20170070867A1 (en) Method and system for triggering terminal group
US8761767B2 (en) Method, system, terminal and network side for triggering terminal response
CN102065400B (zh) 异常状态下用户的接入方法、装置和一种通信系统
KR100983653B1 (ko) 이동 통신 단말기 인증 장치 및 방법
CN103686726A (zh) 用户数据管理方法、设备和系统
WO2013067773A1 (zh) 一种终端触发消息有效时间控制方法及系统
CN101800971B (zh) 在共享网络中确定运营商的方法及装置
WO2013139073A1 (zh) 一种发送终端监控报告的方法及系统

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: 11800106

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2013516974

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2011800106

Country of ref document: EP