WO2007147344A1 - Procédé de restauration de transmission de données de plan d'utilisateur et entité de réseau évolué - Google Patents

Procédé de restauration de transmission de données de plan d'utilisateur et entité de réseau évolué Download PDF

Info

Publication number
WO2007147344A1
WO2007147344A1 PCT/CN2007/001885 CN2007001885W WO2007147344A1 WO 2007147344 A1 WO2007147344 A1 WO 2007147344A1 CN 2007001885 W CN2007001885 W CN 2007001885W WO 2007147344 A1 WO2007147344 A1 WO 2007147344A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
data channel
downlink data
evolved
network
Prior art date
Application number
PCT/CN2007/001885
Other languages
English (en)
Chinese (zh)
Inventor
Weihua Hu
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 WO2007147344A1 publication Critical patent/WO2007147344A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to an evolved mobile communication network system architecture in a third generation mobile communication system, and a method for quickly recovering user plane number transmission under the network system architecture, and an evolved access network entity and an evolved network core Network entity.
  • Background technique
  • the core network of the wireless evolution network mainly includes a Mobility Management Entity (MME), a User Plane Entity (UPE), and an Inter Access System Anchor (Inter AS Anchor,).
  • MME Mobility Management Entity
  • UPE User Plane Entity
  • Inter AS Anchor Inter Access System Anchor
  • the control plane part of the Serving GPRS Support Node SGSN
  • the UPE is a user plane entity, responsible for initiating paging for downlink data in idle state, management
  • the IP bearer parameters and intra-network routing information are saved, which corresponds to the data plane part of the current SGSN of the current UMTS system
  • Inter AS Anchor acts as a user plane anchor between different access systems.
  • the attachment process and the activation process of the Packet Data Protocol (PDP) context are two separate processes.
  • the terminal After booting up, the terminal first performs a GPRS attach procedure, which mainly includes security procedures and location updates. Attachment completed After that, the terminal does not obtain an IP connection at the same time. Only when the terminal initiates a PDP context activation process, the terminal is provided with an IP address and corresponding configuration parameters. As a result, the delay of the user initiating the service becomes longer, and the process is obviously inconsistent with the requirements of the evolved network.
  • the specification proposes that the System Architecture Evolution (SAE)/long-term evolution (LTE) system combines the network registration with the default IP bearer.
  • SAE System Architecture Evolution
  • LTE long-term evolution
  • the network allocates an IP and a part of the corresponding bearer resources to the terminal, and whether the air interface resources are allocated remains to be determined.
  • the mobile terminal is always online, so that when the terminal needs to perform data service, the network can provide services faster and more quickly.
  • users in an evolved network need to establish a default IP bearer when they attach to the network.
  • Figure 2 depicts a network attach process that includes the following steps:
  • the mobile user's terminal discovers the SAE/LTE access system, and then selects the access system and network.
  • the terminal initiates an attach request to the MME/UPE, and the request includes information previously registered by the user (for example, a temporary identity). If the terminal does not report the user's previous registration information, the request contains the user's permanent identity.
  • the attach request may include information of the default IP access bearer (e.g., user selected IP address or access point name APN).
  • the MME UPE will use the previous registration information of the user to derive the address of the old MME/UPE that the user last registered, and send the registration information of the user to the old MME UPE to request the user. Information.
  • the old MME/UPE sends the context of the user to the new MME/UPE, including the permanent identity of the user, security context parameters, and the like.
  • the new MME/UPE performs security authentication on the mobile user or device according to the system configuration. This step is optional.
  • the MME/UPE initiates a registration update to the Home Subscriber Server (HSS), and registers as the MME UPE currently serving the mobile subscriber.
  • HSS Home Subscriber Server
  • the HSS instructs the old MME UPE to delete the context of the mobile user. 7.
  • the HSS confirms the registration of the new MME/UPE.
  • the subscription information of the default IP access bearer, the related QoS policy, and the charging control information are also transmitted to the MME UPE.
  • An Inter AS Anchor is selected.
  • the selection mechanism is not determined.
  • the IP address configuration is determined by the user's preferences or subscription data, or the policy of the HPLMN or VPLMN.
  • Inter AS Anchor performs IP layer configuration based on the determined user IP address.
  • User planes are established and default policy and charging rules are applied.
  • the establishment of the user plane may be initiated by the terminal or initiated by the MME/UPE.
  • the MME/UPE provides the QoS configuration of the default IP bearer to the evolved radio access network (Evolved RAN).
  • the MME UPE sends an attach message of the accepting terminal and allocates a temporary identifier to the terminal, and the default IP bearer related information such as the user IP address is also sent to the terminal.
  • the roaming limit is checked and if it is violated the attachment will be rejected.
  • the terminal confirms that the attachment is successful.
  • the default IP bearer established by the user attach procedure in the evolved network may carry IP-based protocol signaling, such as the SIP protocol registered by the IP Multimedia Subsystem (IMS), and may also carry other default QoS. Control the potential business of policies and billing strategies.
  • IP-based protocol signaling such as the SIP protocol registered by the IP Multimedia Subsystem (IMS)
  • IMS IP Multimedia Subsystem
  • the QoS difference required by the upper-layer application service data flow is relatively large.
  • the network side or the terminal initiates the establishment of a new dedicated bearer, so as to be the corresponding service data flow.
  • Provide hosting services are examples of hosting services.
  • the default IP bearer is composed of multiple channels or bearers, including between the user terminal and the evolved access network.
  • the air interface carries, the data channel between the evolved access network and the core network user plane entity UPE, the data channel between the core network user plane entity UPE and the mobility anchor Inter AS Anchor.
  • the default IP bearer in order to reduce the occupation of air interface resources, when the mobile user enters the idle state, the corresponding context of the mobile user in the evolved access network entity will be released, that is, when the user is in an idle state, the default IP bearer
  • the occupied air interface bearer resources and the access network side resources of the data channel between the evolved access network and the core network user plane entity UPE are released.
  • the user's default IP bearer needs to be restored as soon as possible. This requires restoring the air interface bearer of the default IP bearer and the evolved access network and the core network user plane entity as soon as possible. Data transmission channel between UPEs.
  • the user terminal needs to restore the default IP bearer availability from the idle state, and the user terminal needs to first interact with the evolved access network to complete the establishment of the air interface resource bearer. Then, the evolved access network needs to be reconstructed.
  • the user terminal After the radio bearer is established, the user terminal sends an uplink data packet.
  • the protocol encapsulation of the outer layer of the data packet carries the uplink data channel identification information of the default IP bearer between the evolved access network and the core network user entity UPE, with the GPRS tunnel.
  • the GPRS Tunneling Protocol (GTP) tunnel is used as an example.
  • the IP address of the uplink tunnel on the UPE side and the tunnel end identifier information assigned by the UPE to the uplink tunnel are sent from the received core network when the user terminal attaches to the network.
  • the attachment is obtained and saved in the message.
  • the evolved access network uses the above information to encapsulate the received user data packet, and transmits the user uplink data to the core network user plane entity UPE through the corresponding uplink data channel between the evolved access network and the core network user plane entity UPE.
  • the UPE forwards the data to the mobility anchor based on the routing information in the user context. Click Inter AS Anchor.
  • the user terminal initiates a service request, and requires the network to restore the default IP bearer for the user, and the message carries the user identity.
  • the evolved access network forwards the service request of the user to the control plane entity MME of the core network according to the user identity information.
  • the control plane entity MME notifies the evolved access network to create a context for the user, and the message carries the default IP bearer related information, such as QoS information, the identifier information of the uplink data channel between the evolved access network and the core network user plane entity UPE.
  • the GTP tunnel is used as an example, including the IP address of the UPE side of the core network user plane entity used by the uplink tunnel, and the tunnel end identifier assigned by the core network user plane entity UPE for the uplink tunnel, and the security parameters required by the access network. Permanent identity (IMSI), etc.
  • IMSI Permanent identity
  • the evolved access network creates a context for the user according to the information received from the MME, and allocates resources required for the default IP bearer, that is, downlink data channel resources between the evolved access network and the core network user plane entity UPE,
  • the GTP tunnel is used as an example, including the IP address of the downlink tunnel access network and the tunnel end identifier, and returns a notification to the MME.
  • the MME saves the received information, and sets the downlink data channel identification information allocated by the access network to take the GTP tunnel as an example, including the IP address and the tunnel end identifier of the downlink tunnel access network side, and notifies the user plane entity UPE.
  • the downlink direction of the data transmission channel between the evolved access network and the core network user plane entity UPE is penetrated.
  • the downlink data arrives at the UPE, it can be sent to the evolved access network through the downlink data channel between the UPE and the evolved access network, and then forwarded to the user terminal by the access network.
  • FIG. 4 is a second process of the IP bearer for reestablishing a user terminal from an idle state to a data receiving and receiving state in the prior art, and specifically includes the following steps:
  • the user terminal Before the user terminal wants to transmit data, it initiates a wireless access request and negotiates with the access network for wireless bearer establishment.
  • the user terminal After the radio bearer is established, the user terminal sends an uplink data packet.
  • the protocol encapsulation of the outer layer of the data packet carries the default IP bearer in the evolved access network.
  • the GTP tunnel is used as an example.
  • the IP address of the uplink tunnel on the UPE side and the tunnel end identifier information assigned by the UPE to the uplink tunnel are user terminals.
  • the evolved access network uses the above information to encapsulate the received user data packet, and transmits the user uplink data to the core network user plane entity UPE through the corresponding uplink data channel between the evolved access network and the core network user plane entity UPE.
  • the UPE forwards the data to the mobility anchor Inter AS Anchor based on the routing information in the user context.
  • the mobile anchor Inter AS Anchor can forward the user's downlink data to the core network user plane entity UPE, and the UPE receives the downlink data.
  • the packet is located in the context of the user, and it is found that the downlink data channel between the UPE and the evolved access network has not been restored, so the data can only be cached in the UPE first.
  • the UPE notifies the MME to re-establish the default IP bearer, and the message carries the identity of the user.
  • the control plane entity MME notifies the evolved access network to create a context for the user, and the message carries the default IP bearer related information, such as QoS information, the identifier information of the uplink data channel between the evolved access network and the core network user plane entity UPE.
  • the GTP tunnel is used as an example, including the IP address of the UPE side of the core network user plane entity used by the uplink tunnel, and the tunnel end identifier assigned by the core network user plane entity UPE for the uplink tunnel, and the security parameters required by the access network. Permanent identity (IMSI), etc.
  • IMSI Permanent identity
  • the evolved access network creates a context for the user according to the information received from the MME, and allocates resources required for the default IP bearer, that is, downlink data channel resources between the evolved access network and the core network user plane entity UPE,
  • the GTP tunnel is used as an example, including the IP address of the downlink tunnel access network and the tunnel end identifier, and returns a notification to the MME.
  • the MME saves the received information, and sets the downlink data channel identification information allocated by the access network to take the GTP tunnel as an example, including the IP address and the tunnel end identifier of the downlink tunnel access network side, and notifies the user plane entity UPE.
  • the downlink direction of the data transmission channel between the evolved access network and the core network user plane entity UPE is penetrated.
  • the UPE sends the buffered data and the subsequent downlink data to the evolved access network through the downlink data channel between the UPE and the evolved access network, and then forwards the data to the user terminal.
  • the context of the user in the UPE of the core network user plane is not released. Therefore, the data channel resources allocated by the UPE for the default IP bearer of the user do not change during the next user access. Reuse. For this reason, the user terminal is required to save the uplink data channel identification information between the UPEs of the core entity after entering the idle state.
  • the GTP tunnel is used as an example, including the IP address and the tunnel end identifier of the core network side of the uplink tunnel, so that the user needs to When the data transmission is performed, the information may be notified to the evolved access network, so that the evolved access network can forward the uplink data of the user normally, and no additional signaling procedure is needed for reconstructing the default IP bearer of the user in the evolved access network and The upstream data channel between the core network user plane entity UPE.
  • the above two methods have applied this idea to achieve the purpose of speeding up the user's uplink data transmission. The difference between the two methods is only the timing of reconstructing the downlink data channel.
  • the process shown in Figure 3 is to initiate the reconstruction of the downlink data channel through the user terminal.
  • the process shown in Figure 4 is the downlink data triggering reconstruction of the downlink data channel.
  • the key needs the core network user plane UPE to know that the evolved access network is the channel identifier information allocated by the user's default IP bearer downlink data, to GTP.
  • the tunnel includes the IP address of the downlink tunnel access network and the tunnel end identifier, so that the core network user plane entity UPE can correctly encapsulate and forward the downlink data to the correct downlink data channel.
  • the evolved access network releases the user's context, and the corresponding resources are released, and may be occupied by other users, so even if the information is still stored in the user of the core network user plane UPE In the context, it is also not reusable.
  • the embodiment of the invention provides a method for restoring the number of user planes and an evolved network entity, which is used to solve the problem that the recovery delay of the downlink data transmission of the user existing in the prior art is long.
  • a method for restoring the number of user planes including:
  • the evolved access network When receiving the uplink data packet sent by the idle state user, the evolved access network allocates a downlink data channel to the user, and sends the allocated downlink data channel information together with the received user uplink data packet to the evolved network core network through the uplink data channel. ;
  • the evolved network core network obtains the downlink data channel information that is allocated to the user, and the downlink data that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel, and is sent by the evolved access network to the user terminal.
  • An evolved access network entity including:
  • a downlink data channel allocation unit configured to allocate a downlink data channel to the user and send the uplink data packet when the idle state user sends the uplink data packet;
  • the encapsulating unit is configured to receive the downlink data channel information sent by the downlink data channel allocation unit, and send the downlink data channel information together with the uplink data packet sent by the user to the evolved network core network through the uplink data channel.
  • An evolved network core network entity including:
  • a downlink data channel information acquiring unit configured to acquire, from the uplink data packet, downlink data channel information that is allocated to the user by the evolved access network, and send the information;
  • a sending unit configured to receive downlink data channel information sent by the downlink data channel information acquiring unit, and send downlink data that needs to be forwarded to the user to the progress access network by using the downlink data channel.
  • the evolved access network when the evolved access network receives the uplink data packet sent by the idle state user, the downlink data channel is allocated to the user, and the allocated downlink data channel information and the received user uplink data packet are used together through the uplink data channel.
  • the egress network core network obtains the downlink data channel information allocated to the user, and the downlink data that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel, and is sent by the evolved access network. Give the user terminal. In this way, there is no need to establish a downlink data channel through additional signaling, which shortens the downlink data recovery. The delay speeds up the recovery of the user's face number.
  • FIG. 1 is a schematic diagram of a prior art wireless evolution network architecture
  • FIG. 2 is a flow chart of a network attachment of a terminal in the prior art
  • FIG. 3 is a signaling flow chart of a prior art user terminal from an idle state to a data transceiving state
  • FIG. 4 is a second flow chart of signaling of a prior art user terminal from an idle state to a data transceiving state
  • Embodiments of the present invention are a signaling flow chart of a user terminal from an idle state to a data transceiving state
  • FIG. 6 is a schematic structural diagram of an evolved access network entity according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of an evolved network core network entity according to an embodiment of the present invention. detailed description
  • the evolved access network When receiving the uplink data packet sent by the idle state user, the evolved access network allocates a downlink data channel to the user, and sends the allocated downlink data channel information together with the received user uplink data packet to the evolved network core network through the uplink data channel. ;
  • the evolved network core network obtains the downlink data channel information allocated to the user, and the downlink data that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel, and is sent by the evolved access network to the user terminal.
  • the downlink data channel information may be encapsulated into a data channel protocol header of the outer layer of the user data packet.
  • the extended cell domain may be used to encapsulate the downlink data.
  • Channel information if the protocol used in the data channel does not include an extended cell domain, the protocol extension is used to add a new cell field to carry the downlink data channel information, and the encapsulated downlink data channel information and the user's
  • the uplink data packets are sent together to the user plane entity in the evolved network core network.
  • the user terminal sends an uplink data packet.
  • the protocol encapsulation of the outer layer of the data packet carries the uplink data channel identification information of the default IP bearer between the evolved access network and the core network user entity UPE, and the GTP tunnel is used.
  • the IP address of the uplink tunnel on the UPE side and the tunnel end identifier information allocated by the UPE for the uplink tunnel are obtained and saved from the received attachment message sent by the core network when the user terminal attaches to the network. of.
  • the evolved access network saves the identifier information of the received uplink data channel, and according to the above information, encapsulates the received user data packet and forwards it to the corresponding uplink data channel.
  • the upstream direction of the user's default IP bearer has been penetrated.
  • the evolved access network allocates channel resources of the downlink data channel between the evolved access network and the core network user plane entity UPE for the default IP bearer of the user, and encapsulates the allocated downlink data channel information into a protocol header used by the data channel.
  • the encapsulated data is transferred to the UPE through the upstream data channel.
  • the following upper/downlink data channel is a GTP tunnel as an example to specify how to carry the downlink data channel information allocated to the user through the user uplink data packet.
  • the extended data field included in the GTP header can be used to encapsulate the downlink data channel information.
  • GTP V1 As shown in Table 1 below, the GTP header format is GTP V1:
  • Tunnel Endpoint Ident if ier ( ⁇ Octet) (the first byte of the tunnel end identification field from low to high)
  • Tunnel Endpoint Ident if ier (2 nd Octet) (the second byte of the tunnel end identification field from low to high)
  • Tunnel Endpoint Ident if ier (3 rd Octet) (the third byte of the tunnel end identification field from low to high)
  • Tunnel Endpoint Ident if ier (4 ,h Octet) (the fourth byte of the tunnel end identification field from low to high)
  • the tail of the GTP header can contain an extended header field.
  • the fields of the extended header are as shown in Table 2, where the length is 4 bytes, that is, the extended header length must be an integer multiple of 4 bytes:
  • a GTP header can contain multiple extension fields.
  • the extension fields allowed in the current GTP header are shown in the table.
  • Table 5 is a specific example of the new GTP extension header format of the present invention.
  • the UPU After the UPE receives the data packet, the UPU decapsulates the data channel protocol of the outer layer of the user data packet, and parses the downlink data channel information allocated by the evolved access network for the default IP bearer of the user from the data channel protocol header, and saves the information to the downlink data channel.
  • the parsed data payload is then re-encapsulated according to the data channel format between the core network user plane entity UPE and the mobility anchor Inter AS Anchor, and the data is forwarded to the mobility anchor according to the routing information of the user context.
  • Point Inter AS Anchor Point Inter AS Anchor
  • the downlink data is sent from the mobility anchor Inter AS Anchor to the core network user plane entity UPE UPE, and the downlink data is forwarded to the evolved access network according to the downlink data channel information between the evolved access network and the UPE saved in the user context.
  • the evolved access network forwards the data to the user terminal.
  • the core network user plane entity UPE receives the uplink data of the user forwarded by the evolved access network and performs the forwarding process, and notifies the control plane entity of the core network to recover the data transmission of the MME user plane, and initiates a bearer establishment indication to the control plane entity MME. .
  • the control plane entity MME learns from the notification of the user plane entity UPE that the user plane number is restored, and initiates a process of reestablishing the user context to the evolved access network, requesting the evolved access network to create a context for the user, and the message carries the default IP bearer. Relevant information, such as QoS information, security parameters required by the access network, permanent identity of the user (IMSI), etc. When the user is in an idle state, the information is still stored in the context of the user on the MME.
  • the evolved access network creates a context for the user according to the information received from the control plane entity MME, and feeds back the result to the control plane entity MME.
  • Steps 6 to 8 in the above embodiment can be performed in synchronization with steps 4 to 5, without a sequential relationship.
  • the control plane entity MME and the user plane entity UPE in the core network are independent network nodes, but the present invention is also applicable to the case where the MME and the UPE are located in the same network node.
  • the external interface is connected; when the user plane entity UPE and the control plane entity MME are located in the same network node, the two interact through the internal interface.
  • the network location of the mobile anchor Inter AS Anchor does not affect the applicability of the present invention, If the mobile anchor Inter AS Anchor and the user plane entity UPE coexist in the same network node are not excluded.
  • the user plane entity UPE and the mobility anchor Inter AS Anchor are mutually independent network nodes, they are connected through an external interface; when the user plane entity UPE and the mobility anchor Inter AS Anchor are located in the same network node, the two are internally Interface interaction.
  • An embodiment of an evolved access network entity structure includes:
  • the downlink data channel allocating unit 101 is configured to allocate a downlink data channel and send the uplink data channel to the user when receiving the uplink data packet sent by the idle state user;
  • the encapsulating unit 102 is configured to receive the downlink data channel information sent by the downlink data channel allocating unit 101, and send the downlink data channel information together with the uplink data packet sent by the user to the evolved network core network through the uplink data channel.
  • An embodiment of an evolved network core network entity includes:
  • the downlink data channel information obtaining unit 201 is configured to obtain, from the uplink data packet, downlink data channel information that is allocated to the user by the evolved access network, and send the information;
  • the sending unit 202 is configured to receive the downlink data channel information sent by the downlink data channel information acquiring unit 201, and send the downlink data that needs to be forwarded to the user to the evolved access network through the downlink data channel.
  • the evolved access network when the evolved access network receives the uplink data packet sent by the idle state user, the downlink data channel is allocated to the user, and the allocated downlink data channel information and the received user uplink data packet are obtained.
  • the uplink data channel is sent to the evolved access network through the uplink data channel, and the downlink data channel that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel.
  • the evolved access network is sent to the user terminal.
  • the downlink data channel is not newly established by using additional signaling, which shortens the delay of downlink data transmission recovery, and speeds up the recovery of the user plane number transmission.

Landscapes

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

Abstract

L'invention concerne un procédé pour restaurer une transmission de données de plan d'utilisateur, ledit procédé comportant les étapes suivantes : lorsque le réseau d'accès évolué reçoit des paquets de données de liaison montante envoyés par l'utilisateur d'un état inactif, il attribue un tunnel de données de liaison descendante à l'utilisateur, et envoie les informations de tunnel de données de liaison descendante attribuées conjointement aux paquets de données de liaison montante de l'utilisateur reçus au réseau de cœur évolué, par l'intermédiaire du tunnel de données de liaison montante; ledit réseau de cœur évolué acquiert les informations de tunnel de données de liaison descendante attribuées à l'utilisateur, et envoie les données de liaison montante qui doivent être envoyées à l'utilisateur au réseau d'accès évolué par l'intermédiaire d'un tunnel de données de liaison descendante attribué; les données sont ensuite envoyées au terminal d'utilisateur par le réseau d'accès évolué. La présente invention permet d'obtenir une augmentation de la vitesse d'établissement d'un tunnel de données de liaison descendante, la réduction du retard pour restaurer une transmission de données de liaison descendante et l'amélioration de la vitesse de restauration de transmission de données à plan d'utilisateur.
PCT/CN2007/001885 2006-06-15 2007-06-15 Procédé de restauration de transmission de données de plan d'utilisateur et entité de réseau évolué WO2007147344A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610082876.0 2006-06-15
CN2006100828760A CN101090358B (zh) 2006-06-15 2006-06-15 一种恢复用户面数传的方法

Publications (1)

Publication Number Publication Date
WO2007147344A1 true WO2007147344A1 (fr) 2007-12-27

Family

ID=38833073

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/001885 WO2007147344A1 (fr) 2006-06-15 2007-06-15 Procédé de restauration de transmission de données de plan d'utilisateur et entité de réseau évolué

Country Status (2)

Country Link
CN (1) CN101090358B (fr)
WO (1) WO2007147344A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110944331A (zh) * 2017-04-28 2020-03-31 Oppo广东移动通信有限公司 获取上下文配置信息的方法、终端设备和接入网设备
CN113056038A (zh) * 2016-11-04 2021-06-29 华为技术有限公司 删除用户面隧道的方法、网元及***

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101499966B (zh) * 2008-01-28 2012-04-04 华为技术有限公司 一种信息处理方法以及服务网关
CN103945560B (zh) * 2013-01-17 2018-04-20 中兴通讯股份有限公司 小数据传输路径的建立方法及***、基站、服务网关
CN103458438B (zh) * 2013-08-21 2016-06-01 中国联合网络通信集团有限公司 业务无线侧行为分析的处理方法与装置
CN109548010B (zh) 2017-07-31 2021-02-12 华为技术有限公司 获取终端设备的身份标识的方法及装置
CN109803453B (zh) * 2017-11-17 2023-07-07 华为技术有限公司 一种通信方法，通信设备及其通信***

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020150084A1 (en) * 2000-08-23 2002-10-17 Samsung Electronics Co., Ltd. Core network separation structure and signal processing method thereof in mobile communication system
CN1463085A (zh) * 2002-05-29 2003-12-24 华为技术有限公司 无线接入网络中的数据传输方法
KR20050118597A (ko) * 2004-06-14 2005-12-19 삼성전자주식회사 Ｕｍｔｓ 네트워크에서의 ｇｔｐ 터널 관리 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020150084A1 (en) * 2000-08-23 2002-10-17 Samsung Electronics Co., Ltd. Core network separation structure and signal processing method thereof in mobile communication system
CN1463085A (zh) * 2002-05-29 2003-12-24 华为技术有限公司 无线接入网络中的数据传输方法
KR20050118597A (ko) * 2004-06-14 2005-12-19 삼성전자주식회사 Ｕｍｔｓ 네트워크에서의 ｇｔｐ 터널 관리 방법

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113056038A (zh) * 2016-11-04 2021-06-29 华为技术有限公司 删除用户面隧道的方法、网元及***
CN113056038B (zh) * 2016-11-04 2023-05-16 华为技术有限公司 删除用户面隧道的方法、网元及***
CN110944331A (zh) * 2017-04-28 2020-03-31 Oppo广东移动通信有限公司 获取上下文配置信息的方法、终端设备和接入网设备
CN110944331B (zh) * 2017-04-28 2023-08-01 Oppo广东移动通信有限公司 获取上下文配置信息的方法、终端设备和接入网设备

Also Published As

Publication number Publication date
CN101090358A (zh) 2007-12-19
CN101090358B (zh) 2011-02-02

Similar Documents

Publication Publication Date Title
EP3834384B1 (fr) Configuration basée sur un plan de commande pour mise en réseau sensible au temps
US11848744B2 (en) Non-access stratum connection handling for wireless devices
EP3881635B1 (fr) Déclenchement d'application pour un dispositif sans fil
JP4230106B2 (ja) Ｇｐｒｓ加入者による多数のインタネットサービスプロバイダの選択
US8027309B2 (en) Low latency handover between wireless communication networks using different radio access technologies
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
WO2009097818A1 (fr) Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur
US20100309881A1 (en) Mobile communication system and tunnel management method thereof
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
WO2009049529A1 (fr) Procédé d'établissement de support de charge et dispositif associé
WO2013097641A1 (fr) Procédé, entité et système de réalisation d'un service en grappe
WO2013064104A1 (fr) Procédé de transmission de données, entité de gestion de mobilité et terminal mobile
KR100755981B1 (ko) 콘텍스트 링크 방식
WO2020173137A1 (fr) Procédé de transmission de données, dispositif associé, produit informatique, et support de stockage
WO2007147344A1 (fr) Procédé de restauration de transmission de données de plan d'utilisateur et entité de réseau évolué
TWI792415B (zh) Ue和網路之間的多存取pdu會話狀態同步
WO2011109938A1 (fr) Procédé, dispositif et système destinés à remettre un compte rendu contenant des informations d'élément de réseau d'accès sans fil
WO2009018777A1 (fr) Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué
US7954002B2 (en) Systems and methods for bulk release of resources associated with node failure
WO2012024989A1 (fr) Procédé et système pour une libération de porteuse
US20220248370A1 (en) Signaling Delivery in a Wireless Network
WO2010051696A1 (fr) Procédé et système de libération d’une ressource radio
US8418228B2 (en) Converged access control method using network access device at penetration node of IP network of convergence ALL-IP network
WO2009127120A1 (fr) Procédé, dispositif et système permettant de suivre un utilisateur au cours du processus de commutation
KR100901206B1 (ko) 기지국과 네트워크 개체간의 서비스 품질 보장이 가능한데이터 교환방법

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

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

Country of ref document: EP

Kind code of ref document: A1