WO2009012707A1 - Procédé, dispositif et système de statistiques d'évènements d'accès - Google Patents

Procédé, dispositif et système de statistiques d'évènements d'accès Download PDF

Info

Publication number
WO2009012707A1
WO2009012707A1 PCT/CN2008/071716 CN2008071716W WO2009012707A1 WO 2009012707 A1 WO2009012707 A1 WO 2009012707A1 CN 2008071716 W CN2008071716 W CN 2008071716W WO 2009012707 A1 WO2009012707 A1 WO 2009012707A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
core network
routing
available
event
Prior art date
Application number
PCT/CN2008/071716
Other languages
English (en)
Chinese (zh)
Inventor
Zongquan Tang
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009012707A1 publication Critical patent/WO2009012707A1/fr

Links

Classifications

    • 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
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, device and system for counting Iu-Flex network access events. Background technique
  • the 3rd Generation Partnership Project (3GPP) introduced the Intra-Domain Connection of RAN nodes to multiple CN nodes technology in the R5 version specification.
  • the radio network controller (RNC, Radio Network Controller) of the radio access network (RAN) is connected to a plurality of circuit switching domain (CS, Circuit Switch) core network (CN, Core Network) nodes, such as mobile a switching center server (MSC, Server Mobile Switch Center Server); and a plurality of packet switched domain (PS, Packet-Switched domain) CN nodes, such as a service general packet radio service support node (SGSN) Therefore, the network service capability/recovery capability is greatly enhanced, and the networking mode becomes more flexible.
  • CS circuit switching domain
  • CN Circuit Switch
  • Core Network core network
  • PS Packet-Switched domain
  • SGSN service general packet radio service support node
  • FIG. 1 it is a schematic diagram of a typical Iu-Flex network structure, where MSC1 MSC MSC7 are multiple MSC Servers (CS domains), SGSN1-SGSN6 are multiple SGSNs (PS domains), and multiple MSC Servers are used. Or the SGSN provides services for multiple RAN nodes at the same time. These RAN nodes belong to different CS pool areas and PS pool areas. In any CN domain, the CN nodes providing services at the same time are identical in status and function, with the difference that there is a difference in the capacity of different CN nodes.
  • the RNC When the RNC receives the CST initial direct transfer (IDT) of the user equipment (UE, User Equipment), it needs to select one MSC Server in the CN node to provide services.
  • This function that needs to be implemented in the RNC is called the non-access stratum node selection function (NNSF, Non Access Stratum Node Selection Function), the RNC completes the selection process according to the IDNNS (Intra Domain NAS node selector) parameter carried in the IDT message and a specific load balancing algorithm. Usually, this selection process is also called "routing.”
  • NSF Non Access Stratum Node Selection Function
  • the inventor has found that, for the different content carried in the IDNNS parameter in the IDT message sent by the UE as described above, the RNC has different processing modes when selecting a route.
  • KPI Key Performance Indicator
  • the embodiment of the invention provides a method and device for collecting network access events, which are used to provide statistics on access performance indicators in the network.
  • the radio access network node receives the initial direct transmission message sent by the user equipment; and selects the IDNNS parameter according to the non-access stratum node in the domain carried in the initial direct transmission message, and performs the non-access stratum node to select the NNSF function, and determines that the The core network node of the user equipment monthly service;
  • the radio access network node routes the initial direct transmission message to the determined core network node, and records a corresponding access event according to the routing parameter carried in the IDNNS parameter and the specific manner of determining the core network node; And count the recorded events.
  • a receiving unit configured to receive an initial direct transmission message sent by the user equipment, and parse the non-access stratum node selection IDNNS parameter element in the domain that is carried by the initial direct transmission message;
  • a determining unit configured to receive the IDNNS parameter, perform a non-access stratum node to select an NNSF function, determine a core network node serving the user equipment, and send a unit, configured to receive, according to the initial direct transmission message and the core network node Information, routing the initial direct transfer message to the core network section Point
  • An event recording unit configured to record a corresponding access event according to the received routing parameter carried in the IDNNS parameter, and determining a specific manner of the core network node; an event statistics unit, configured to send to the event recording unit Events are counted.
  • An access event statistics system provided by an embodiment of the present invention includes the foregoing access event statistics device.
  • the embodiment of the present invention receives the IDT message of the UE by using the radio access network node, and determines the first CN node corresponding to the routing parameter and determines that the UE is served according to the IDNNS parameter (route parameter) carried in the IDT message. And the second CN node is recorded as a corresponding access event according to the routing parameter, the first CN node, and the second CN node; and the recorded event is counted.
  • the embodiments of the present invention can provide various KPI indicators for Iu-Flex network access performance, which is convenient for operators to perform network performance analysis based on these KPI indicators.
  • FIG. 1 is a schematic diagram of a structure of an Iu-FLex network in the prior art
  • FIG. 2 is a schematic diagram of a function of an NNSF according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for collecting an access event according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a radio access network node according to an embodiment of the present invention. detailed description
  • the MSC Server 1, the MSC Server 2, and the MSC Server 3 connected to the radio access network can provide the service of the CS domain.
  • the RAN node receives the IDT message sent by the UE forwarded by the Node B,
  • an MSC Server for example, MSC Server1
  • MSC Server1 is selected to provide services for the UE, and the IDT message sent by the UE is forwarded to the MSC Server serving the UE (MSC Server1).
  • the IDT message mainly includes a CN domain indication ("cn-Domainldentity” indicating the CS domain or PS domain) routing parameters (“intraDomainNasNodeSelector”) and NAS messages ("nas-Message”), and its specific format is as follows:
  • IntraDomainNasNodeSelector IntraDomainNasNodeSelector, nas-Message NAS-Message, where IntraDomainNasNodeSelector (ie IDNNS parameter) is structured as follows:
  • IntraDomainNasNodeSelector :: SEQUENCE
  • Routingparameter RoutingParameter tMSIofsamePLMN SEQUENCE ⁇
  • Routingparameter RoutingParameter tMSIofdifferentPLMN SEQUENCE ⁇
  • Routingparameter RoutingParameter iMSIcauseUEinitiatedEvent SEQUENCE ⁇
  • Routingparameter RoutingParameter spare2 SEQUENCE ⁇
  • Routingparameter RoutingParameter spare 1 SEQUENCE ⁇
  • the length of each routing parameter is 10 bits.
  • the number of IDNNS carried by the UE in the IDT message may carry any routing parameter.
  • IDNNS parameters may carry any 6 legal paths One of the parameter types, derived from the three main UE identifiers, including (packet) temporary mobile subscriber identity ((p)-TMSI, (Packet) Temporary Mobile Subscriber Identity), International Mobile Subscriber Identity (IMSI, International Mobile Subscriber Identity) ), International Mobile Equipment Identity (IMEI, International Mobile Equipment Identity); and "spare2,,””sparer", which is a protocol reserved value. If the UE carries at least one of these two parameters, the IDNNS parameter is regarded as an illegal parameter. Where (p)-TMSI represents TMSI or p-TMSI.
  • the UE In an Iu-Flex network, if the UE derives routing parameters from (p)-TMSI, the "RoutingParameter" is taken from the 23 ⁇ 14 (high to low) bits in (p)-TMSI.
  • the IDNNS parameter of the IDT message When the IDNNS parameter of the IDT message is filled in, the UE will intercept the 10 bits to carry the Network Resource Identifier (NRI).
  • NRI Network Resource Identifier
  • a 10-bit NRI is usually not required. For example, in the case of identifying 30 MSC Servers, only 5 bits are needed, and more bits are used to identify users, so the actual network side RNC and CN need Configure the NRI length. The configurations on both ends must be consistent.
  • the UE can derive the routing parameters from the temporary identifier as long as the UE can obtain the temporary identity of the corresponding CN domain (the CS domain temporary identifier is "TMSI” and the PS domain temporary identifier is "p-TMSI”).
  • TMSI temporary identity of the corresponding CN domain
  • p-TMSI PS domain temporary identifier
  • RoutingParameter contains the NRI.
  • Routingbasis localPTMSI
  • TMSI TMSI
  • PS domain p-TMSI
  • LAI Location Area Identity
  • RAI Routing
  • the area identity is the same as the LAI or RAI of the current cell currently accessed by the UE, that is, the location area/routing area to which the UE belongs does not change.
  • TMSI TMSI
  • CS domain TMSI
  • -TMSI PS domain
  • the public land mobile network (PLMN) identifier (ID, IDentity) included in the stored LAI or RAI is the same as the PLMN ID of the currently selected network of the UE, that is, the UE is in the same PLMN, but the location area/route The district has changed;
  • the UE When the UE cannot obtain the temporary identifier of the corresponding CN domain, and there is an available User Identity Module (SIM, Subscriber Identity Module) or User Identifier Module (UIM) in the UE, the UE should derive the routing parameters from the IMSI.
  • SIM Subscriber Identity Module
  • UIM User Identifier Module
  • the routing parameter "RoutingParameter” is often referred to as "IMSI V value”. According to the current call as the calling or called, the routing parameter types are different, as follows:
  • Routingbasis iMSIresponsetopaging
  • IMEI V value The routing parameter "RoutingParameter” derived from IMEI is usually called "IMEI V value”, as follows:
  • the NNSF function is implemented by the radio access network node, and the radio access network node provides the statistical KPI indicator related to the NNSF function. That is, the radio access network node receives the IDNNS parameter in the IDT message from the UE, and the pre-configured core on the RNC.
  • the network node routing table and the available status of the core network node perform NNSF function, and determine a core network node (for example, the CN domain may be an MSC Server, and the PS domain may be an SGSN) to serve the UE that currently sends the initial direct transmission message.
  • the radio access network node records the corresponding access event according to the routing parameters carried in the IDNNS parameter of the initial direct transmission message and the specific manner of determining the core network node, and performs statistics on the recorded events.
  • the radio access network node uses the RNC as an example to implement the NNSF function, the event recording, and the statistics function on the RNC node.
  • a flowchart of an access event statistics method includes the following steps:
  • Step 10 In the Iu-Flex network, the radio access network node RNC receives the IDT message of the UE, and performs the NNSF function according to the IDNNS parameter carried in the IDT message to determine the CN node serving the UE.
  • the core network node serving the user equipment is a core network node available in the state; and the IDNNS parameter
  • the core network serving the user equipment is determined according to the load balancing function. node.
  • the RNC needs to perform the NNSF function according to the pre-configured routing table, the IDNNS parameter carried in the IDT message, and the available state information of the corresponding CN node.
  • the pre-configured routing table records the routing information of all CN nodes that establish a connection with the RNC.
  • the RNC can implement the load balancing function to implement routing of IDT messages according to the routing table.
  • the main principle of the load balancing function is to select one of the available CN nodes according to a certain policy (such as the current load of each CN node), which may be according to a certain ratio. For example, the selection may be as simple as random selection, or may be performed in an equal ratio.
  • Step 20 The RNC routes the IDT message to the determined CN node, and records the corresponding access event according to the different routing parameters carried in the IDNNS parameter and the specific manner of determining the CN node.
  • Step 30 Perform statistics on the recorded events.
  • the statistics function is performed after the RNC routes the received IDT message to the corresponding CN node, and the statistics can also perform separate statistics for each CN node.
  • the embodiments of the present invention record different events for the different types of routing parameters carried in the IDNNS parameters and determine the specific manners used by the CN nodes. The following describes the various events.
  • the location area of the already stored CS domain identifies the LAI or PS domain.
  • the routing area identifier RAI is the same as the LAI or RAI of the current cell, that is, the UE is from the same location area/routing area; the routing parameter "RoutingParameter” carries the network resource identifier (NRI, Network Resource Identifer), and the RNC will be based on the available status of the NRI and the CN node. Perform NNSF functions.
  • the RNC finds the corresponding CN node according to the NRI and the CN node status is available, the RNC routes the IDT message to the corresponding CN node and records it as the first event, denoted by "VS.ValidNRLLocal.Routed".
  • the RNC finds the corresponding CN node according to the NRI but the CN node status is not available, the RNC needs to perform load balancing function, determine the CN node available in the state, and route the IDT message to the determined CN node in any state. And recorded as the second event, represented by "VS.ValidNRLLocal.CNUnavailable.Balanced".
  • Routingbasis TMSIofsamePLMN
  • the RNC finds the corresponding CN node according to the NRI and the CN node status is available, the RNC routes the IDT message to the corresponding CN node and records it as the fourth event, denoted by "VS.ValidNRLSamePLMN.Routed".
  • the RNC finds the corresponding CN node according to the NRI but the CN node status is not available, the RNC needs to perform load balancing function, determine the CN node available in the state, and route the IDT message to the determined CN node in any state, and Recorded as the fifth event, represented by "VS.ValidNRLSamePLMN.CNUnavailable.Balanced".
  • the RNC needs to perform a load balancing function, determine the CN node available in the state, and route the IDT message to the determined CN node in any state, and record it as the sixth event. , expressed by "VS.InvalidNRI.SamePLMN.Balanced".
  • the RNC finds the corresponding CN node according to the NRI and the CN node status is available, the RNC will The IDT message is routed to the corresponding CN node and recorded as the seventh event, represented by "VS.ValidNRI.DifferentPLMN.Routed".
  • the RNC finds the corresponding CN node according to the NRI but the CN node status is not available, the RNC needs to perform load balancing function, determine the CN node available in the state, and route the IDT message to the determined CN node in any state, and Recorded as the eighth event, represented by "VS.ValidNRI.DifferentPLMN.CNUnavailable.Balanced".
  • the RNC needs to perform load balancing function, determine the CN node available in the state, and route the IDT message to the determined CN node in any state, and record it as the ninth.
  • the event is represented by "VS. InvalidNRLDifferentPLMN. Balanced".
  • Routingbasis iMSIcauseUEinitiatedEvent
  • the RNC finds the corresponding CN node according to the "IMSI V value" and the corresponding CN node status is available, the RNC routes the IDT message to the corresponding CN node and records it as the tenth event, using "VS.IMSI_Initiated. V-Value .Routed” means.
  • the RNC finds the corresponding CN node according to the "IMSI V value", but the corresponding CN node status is not available, the RNC needs to perform load balancing function, determine the CN node available in the state, and route the IDT message to any determined state.
  • the available CN node is recorded as the eleventh event and is represented by "VS.IMSI_Initiated.V-Value.Balanced”.
  • Routingbasis iMSIresponsetopaging
  • the RNC When the RNC receives the IMSI paging message of the CN node, it needs to temporarily store the correspondence between the global identifier "Global CN-Id" of the CN node that sends the paging message and the IMSI carried in the paging message, for the subsequent RNC. Properly route the page response.
  • the RNC receives the IDT message that the UE responds to, the RNC needs to check whether the IMSI of the user has been recorded, and whether the IMSI is obtained, whether the Global-CN ID is found, whether the corresponding CN node is available, or the like is processed. among them:
  • the RNC If the RNC obtains the IMSI and finds the corresponding Global-CN ID according to the IMSI, and the Global-CN ID corresponds to the CN node status, the RNC routes the IDT message to the corresponding CN node and records it as the thirteenth event. , expressed by "VS.IMSI-PagingResponse.CNIdBased.Routed".
  • the RNC If the RNC obtains the IMSI and finds the corresponding Global-CN ID according to the IMSI, but the Global-CN ID corresponds to the CN node status is unavailable, the RNC needs to perform a load balancing function to determine the CN node available in the state, and The IDT message is routed to the CN node that is determined to be available in any state, and is recorded as the fourteenth event, represented by "VS.IMSI-PagingResponse.Unavailable. Balanced".
  • the RNC needs to perform a load balancing function, determine the CN node available in the state, route the IDT message to any available CN node, and record For the fifteenth event, it is represented by "VS.IMSI-PagingResponse.V-Value.Routed”; or, if the RNC cannot obtain the IMSI, it can also perform load balancing function to determine the CN node available in the state, and the IDT message Route to the CN node that is available in any of the determined states, and record it as the sixteenth event, represented by "VS.IMSI-RagingResponse.V-Value.Balanced".
  • the RNC finds the corresponding CN node according to the ' ⁇ V value' and the corresponding CN node status is unavailable, the RNC needs to perform load balancing function, determine the CN node available in the state, and route the IDT message to any determined one.
  • the CN node in the state is recorded and recorded as the eighteenth event, represented by "VS.IMELV-Value.Balanced".
  • null-NRI Load Re-distribution
  • Load Re-distribution is the process of load reassignment, which refers to a process in which a CN node removes a UE from the CN node with the assistance of the RNC.
  • the load redistribution introduces a special meaning of NRI (null-NRI) and a special CN node state (unloaded state off-load).
  • NRI nucleic acid
  • CN node state unloaded state off-load
  • the state of the CN node needs to be set to the "unloaded” state on the RNC; on the other hand, the CN node performs a (p)-TMSI redistribution process on the UE that needs to be removed,
  • the triggering UE requests the location area/routing area update process again, and carries "null-NRT" in the IDNNS parameter of the IDT message sent by the UE.
  • the RNC finds that the routing parameter is "null-NRI"
  • the IDT message is routed to any A CN node that is not in the "uninstalled” state and is available.
  • the embodiment of the present invention provides the event record status in the 21st, which is recorded as a corresponding access event according to different routing parameters carried in the IDNNS parameter and different specific manners of determining the corresponding core network node.
  • the event records provided by the embodiments of the present invention are as shown in Table 1 below:
  • the sixth event VS.Inva makes RI.SamePLMN. Balanced 2. Invalid NRI
  • the ninth event VS.Inva makes RI.DifferentPLMN. Balanced 2. Invalid NRI
  • Global-CN ID is the global identifier of the CN node that routes the IDT message destination
  • CN Domain is the CN domain (PS or CS) where the CN node of the destination IDT message is located;
  • Global-CN Id unavailable indicates the global identity of the faulty CN node
  • V-value means IMSI V value or IMEI V value
  • Global-CN Id off-loading represents an array of global identifiers for the CN nodes in the "unloaded" state.
  • the embodiments of the present invention provide complete and detailed Iu-Flex network access performance statistics events, so that operators can obtain KPI data that meets the requirements based on these event records. For example, through statistics Seven events, eighth event, and ninth event, etc., can obtain the number and trend of roaming users across PLMNs in a certain period of time; by counting the third event and the sixth event, etc., the number of users moving in the pool across the pool can be obtained. trend.
  • the embodiment of the present invention further provides a radio access event statistics device, as shown in FIG. 4, including a receiving unit 100, a determining unit 200, a sending unit 300, an event recording unit 400, and an event counting unit 500, as follows: :
  • the receiving unit 100 is configured to receive an IDT message sent by the UE, and send it to the sending unit 300; and parse out the IDNNS parameter carried by the IDT message, and send it to the determining unit 200;
  • a determining unit 200 configured to receive an IDNNS parameter, perform an NNSF function, determine a CN node serving the UE, and notify the determined CN node information to the sending unit 300; and determine the received IDNNS parameter and determine the serving as the UE The specific manner of the CN node is notified to the event recording unit 400;
  • the sending unit 300 is configured to, according to the received IDT message and the CN node information served by the UE, the IDT message to the CN node serving the UE;
  • the event recording unit 400 is configured to record, according to the received routing parameter in the IDNNS parameter, the specific manner of determining the CN node as a corresponding access event, and send it to the event statistics unit 500;
  • the event statistics unit 500 is configured to perform statistics on events sent by the event recording unit 400.
  • the event recording unit 400 in the foregoing embodiment further includes a plurality of sub-units for respectively recording corresponding access events in a specific manner of the corresponding CN node when the IDT message carries different types of routing parameters.
  • the determining unit 200 may include: a module for determining a core network node corresponding to the routing parameter carried in the IDNNS parameter (for convenience of expression, referred to as a first core network node) And a module for determining that the first core network node is a core network node serving the user equipment (for convenience of expression, referred to as a second core network node) when the first core network node exists and the state is available. .
  • the determining unit 200 may include: a module for determining a first core network node corresponding to the routing parameter carried in the IDNNS parameter; and configured to exist in the first core network node but the state is unavailable or the first When a core network node does not exist, the module of the second core network node is determined according to a load balancing function.
  • the access event statistics device may be a logical entity integrated in a radio network controller (RNC) of the wireless access network.
  • RNC radio network controller
  • the embodiment of the invention further provides a system, including the foregoing access event statistics device.
  • the system can be a wireless network controller.
  • the embodiments of the present invention can provide complete and detailed statistics of KPI indicators of Iu-Flex network access performance, which is convenient for operators to obtain network performance analysis that meets the requirements based on these KPI indicators.

Landscapes

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

Abstract

La présente invention concerne un procédé et un périphérique de statistiques d'évènement d'accès. Ce procédé comprend les étapes de : réception d'un message IDT d'équipement d'utilisateur (UE) par nœud de réseau d'accès radio et implémentation de fonction NNSF pour déterminer le nœud CN qui sert l'UE basé sur le paramètre IDNNS transporté par le message IDT ; acheminement du message IDT vers le nœud CN déterminé et enregistrement de l'évènement d'accès correspondant basé sur le paramètre de routage différent transporté par le paramètre IDNNS et le mode spécifique pour déterminer le nœud CN ; la réalisation des statistiques de l'évènement enregistré. Le procédé comprend des statistiques complètes et détaillées de l'index KP de performance d'accès réseau Iu-Flex et il facilite l'obtention par un opérateur de l'analyse de performance de réseau qui satisfait à la demande selon l'index KPI.
PCT/CN2008/071716 2007-07-25 2008-07-22 Procédé, dispositif et système de statistiques d'évènements d'accès WO2009012707A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2007101297636A CN100563365C (zh) 2007-07-25 2007-07-25 一种接入事件统计方法及装置
CN200710129763.6 2007-07-25

Publications (1)

Publication Number Publication Date
WO2009012707A1 true WO2009012707A1 (fr) 2009-01-29

Family

ID=38938162

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/071716 WO2009012707A1 (fr) 2007-07-25 2008-07-22 Procédé, dispositif et système de statistiques d'évènements d'accès

Country Status (2)

Country Link
CN (1) CN100563365C (fr)
WO (1) WO2009012707A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100563365C (zh) * 2007-07-25 2009-11-25 华为技术有限公司 一种接入事件统计方法及装置
CN101267397B (zh) * 2008-04-14 2011-09-14 华为技术有限公司 接入点系统中实现核心网的网络节点共享方法、装置和系统
CN102325341A (zh) * 2008-04-14 2012-01-18 华为技术有限公司 接入点系统中实现核心网的网络节点共享方法、装置和系统
CN102026093A (zh) * 2009-09-17 2011-04-20 普天信息技术研究院有限公司 传输多媒体广播组播业务数据的方法及系统
CN102300223B (zh) * 2010-06-28 2016-06-29 中兴通讯股份有限公司 一种跟踪用户设备国际移动设备身份的方法及其无线网络控制器
CN101951623B (zh) * 2010-09-13 2014-11-05 中兴通讯股份有限公司 一种基于用户事件的用户行为统计方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1507235A (zh) * 2002-12-10 2004-06-23 ������������ʽ���� 访问中继装置
JP2004246410A (ja) * 2003-02-10 2004-09-02 Hitachi Electronics Service Co Ltd インターネットアクセスログ解析システム
CN1627707A (zh) * 2003-12-11 2005-06-15 日立通讯技术株式会社 网络统计信息服务系统及因特网接入服务器
WO2006095084A1 (fr) * 2005-03-09 2006-09-14 France Telecom Systeme hybride passerelle multi-acces/generateur de test de liens de connexion a des equipements
CN101087465A (zh) * 2007-07-25 2007-12-12 华为技术有限公司 一种接入事件统计方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1507235A (zh) * 2002-12-10 2004-06-23 ������������ʽ���� 访问中继装置
JP2004246410A (ja) * 2003-02-10 2004-09-02 Hitachi Electronics Service Co Ltd インターネットアクセスログ解析システム
CN1627707A (zh) * 2003-12-11 2005-06-15 日立通讯技术株式会社 网络统计信息服务系统及因特网接入服务器
WO2006095084A1 (fr) * 2005-03-09 2006-09-14 France Telecom Systeme hybride passerelle multi-acces/generateur de test de liens de connexion a des equipements
CN101087465A (zh) * 2007-07-25 2007-12-12 华为技术有限公司 一种接入事件统计方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes (Release 7)", 3GPP TS 23.236 V7.0.0, December 2006 (2006-12-01), Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/html-info/23236.htm> *

Also Published As

Publication number Publication date
CN100563365C (zh) 2009-11-25
CN101087465A (zh) 2007-12-12

Similar Documents

Publication Publication Date Title
JP7240689B2 (ja) 時間依存ネットワーキングのための制御プレーンに基づく設定
US11606734B2 (en) Handover method in wireless communication system and apparatus therefor
US11889471B2 (en) Paging time adjustment in a wireless network
US11330642B2 (en) Method for supporting and providing LADN service in wireless communication system and apparatus therefor
US10474522B2 (en) Providing a network access failure cause value of a user equipment
US9094839B2 (en) Evolved packet core (EPC) network error mapping
EP2348782B1 (fr) Procédé de commande d&#39;accès, dispositif et système de communication
CN109167847B (zh) 一种IPv6地址的生成方法及SMF、通信系统
CN110337150B (zh) 承载控制方法及系统
EP3740028B1 (fr) Procédé d&#39;établissement d&#39;une session d&#39;unité de données de protocole et dispositif terminal et medium de stockage lisible par ordinateur correspondant
CN107439042B (zh) 用于处理ue对网络的接入的方法和节点
US8224325B2 (en) Resource control method, relevant device, and system
US20060198347A1 (en) Accessing a communication system
CN106031105B (zh) 针对epc的受信任wlan访问的过载控制
WO2010012174A1 (fr) Procédé de gestion, dispositif et système permettant à un utilisateur d&#39;accéder à un réseau
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
WO2007022720A1 (fr) Procede d&#39;envoi d&#39;information de radiomessagerie
WO2015062098A1 (fr) Procédé de sélection de réseau et dispositif de réseau central
WO2011054300A1 (fr) Procédé et système permettant de contrôler un accès à un terminal de communication de type machine (mtc)
WO2012083809A1 (fr) Procédé de pousseur d&#39;informations et système reposant sur un système lte
WO2012051890A1 (fr) Procédé et système de limite d&#39;accès de terminal terminal access limit method and system
WO2014166089A1 (fr) Procédé et dispositif de régulation de l&#39;encombrement
WO2011153750A1 (fr) Procédé et système de synchronisation de données d&#39;utilisateur
WO2009012707A1 (fr) Procédé, dispositif et système de statistiques d&#39;évènements d&#39;accès
WO2010088817A1 (fr) Procédé et dispositif pour acquérir des informations de localisation d&#39;ue par andsf

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

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

Country of ref document: EP

Kind code of ref document: A1