WO2009059531A1 - Procédé, système et dispositif pour réduire les abandons d'appels de l'utilisateur lors de la dérive statique - Google Patents

Procédé, système et dispositif pour réduire les abandons d'appels de l'utilisateur lors de la dérive statique Download PDF

Info

Publication number
WO2009059531A1
WO2009059531A1 PCT/CN2008/072858 CN2008072858W WO2009059531A1 WO 2009059531 A1 WO2009059531 A1 WO 2009059531A1 CN 2008072858 W CN2008072858 W CN 2008072858W WO 2009059531 A1 WO2009059531 A1 WO 2009059531A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
drnc
sequence
number information
module
Prior art date
Application number
PCT/CN2008/072858
Other languages
English (en)
Chinese (zh)
Inventor
Jixian Xie
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 WO2009059531A1 publication Critical patent/WO2009059531A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H04W36/0235—Buffering or recovering information during reselection by transmitting sequence numbers, e.g. SN status transfer

Definitions

  • the present invention relates to a universal mobile communication system (Universal Mobile Telecommunication)
  • the System, UMTS field specifically related to methods, systems, and devices for reducing user dropped calls in UMTS static migration.
  • FIG. 1 The current UMTS network structure is shown in Figure 1, which mainly includes the core network (Core).
  • CN UMTS Terrestrial Radio Access Network
  • UTRAN UMTS Terrestrial Radio Access Network
  • User terminals User
  • 'CN includes grouping (Packet
  • Radio Network Controller Radio Network
  • RNC Radio Network Controller
  • UTRAN includes RNC and base station (Node B), RNC and Node B are connected through Iub interface, different RNCs are connected through Iur interface; RNC and Node
  • B constitutes a wireless network control system (Radio Network
  • the UE is connected to the Node B through the Uu interface, which is also called the air interface.
  • the wireless interface in UTRAN can be divided into physical layer, data link layer and wireless network control layer from the protocol layer.
  • the physical layer is called layer 1 (L1) and the data link layer is called layer 2 (L2).
  • the wireless network control layer is called layer 3 (L3).
  • the above L2 includes radio link control (Radio Link)
  • RLC Radio Controller
  • RLC provides service radio bearer (Traffic Radio
  • the above L3 includes radio resource control (Radio Resource
  • RRC Radio Resource Control
  • the RNC includes an RLC module corresponding to L2 and an R corresponding to L3.
  • the RC module the UE also includes an RLC module, where the RLC module performs the function corresponding to the RLC layer, and the RRC module completes the function corresponding to the RRC layer.
  • the RLC module in the UE sends control signaling to the RLC module in the RNC through the SRB, or sends a service message to the RLC module in the RNC through the TRB, where the control signaling or the service message is represented as a protocol data unit (Protocol Data).
  • Protocol Data Protocol Data
  • PDU PDU Unit
  • the PDU serial number hereinafter referred to as the RLC serial number
  • the RLC module in the RNC has a serial number check function, checks whether the UE sends the correctly transmitted PDU, and returns an RLC status report to the UE to notify the receiving situation.
  • the UE and the RNC need to perform RLC sequence number information synchronization, that is, maintain the consistent RLC sequence number information, so that the RNC may perform the sequence number check according to the consistent RLC sequence number information.
  • the 3GPP protocol stipulates that there is an RNC migration in the UMTS, and refers to a process in which the RNC serving the UE is converted from the current RNC to another RNC. According to whether the UE participates in the migration process, the RNC migration in the UMTS is classified into UE related (UE involved) and the UE does not. Related (UE not).
  • RNC Resource Control
  • Drift RNC Drift
  • the DRNC will become the UE's new service RNC.
  • Embodiments of the present invention provide a method, system, and apparatus for reducing user dropped calls in static migration.
  • a method for reducing user dropped calls in static migration comprising:
  • Drift radio network controller DRNC receive service radio network controller SRNC sends radio link control RLC serial number information
  • the DRNC uses the RLC sequence number information to process the protocol data unit PDU sequence sent by the UE.
  • a system for reducing user dropped calls in static migration includes: [16] The service radio network controller SRNC is configured to send the RLC sequence number information through the core network CN; [17] the drift radio network controller DRNC is configured to receive the RLC sequence number information sent by the SRNC, in the static migration execution process The PDU sequence sent by the user equipment UE is processed by using the RLC sequence number information sent by the SRNC.
  • a radio network controller RNC includes:
  • an RRC module configured to receive RLC serial number information sent by another RNC, and configure the RLC serial number information to an RLC module of the RNC;
  • the RLC module is configured to process, according to the RLC sequence number information configured by the RRC module, the PDU sequence received from the user terminal UE during the static migration execution.
  • a radio network controller RNC, the RNC includes:
  • the RLC module is configured to provide RLC serial number information corresponding to the radio bearer of the RNC;
  • the sending module is configured to send, by using the CN, the RLC serial number information provided by the serving RLC module to the drift radio network controller DRNC corresponding to the RNC during the static migration execution process.
  • the method, the system and the device for reducing the dropped call of the user are provided, and the SRNC provides the RLC serial number information to the DRNC, so that the DRNC and the UE maintain the same RLC serial number during the static migration execution process.
  • the information is processed by using the RLC serial number information to correctly process the PDU sequence sent by the UE, so that the PDU sequence that is correctly sent by the UE is not determined to be sent incorrectly, and the UE is prevented from performing an operation, thereby solving the problem.
  • the problem of words improve the user experience.
  • FIG. 1 is a structural diagram of a UMTS network in the prior art.
  • FIG. 2 is a schematic diagram of static migration in a UMTS according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for reducing user dropped calls in static migration according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for reducing user dropped calls in static migration according to another embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a system for reducing user dropped calls in static migration according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a radio network controller RNC according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of static migration in UMTS according to an embodiment of the present invention.
  • the left side of Figure 2 shows the status of the radio link before the RNC is migrated, that is, there is no radio link between the UE and the SRNC, and the SRNC triggers the migration to the DRNC.
  • the right side of Figure 2 shows the radio link status after the RNC migration.
  • the Old SRNC is the pre-migration SRNC and the SRNC is the pre-migration DRNC. It can be seen that during the entire static migration process, the Uu interface connection between the UE and the UTRAN does not change, that is, the UE does not perceive the migration process.
  • the following analysis process is illustrated by way of example. It is assumed that before the start of the entire static migration process, the UE has correctly sent the PDU sequence with sequence number 3 to the SR NC, and receives the RLC status report returned by the SRNC, informing the UE that the UE has correctly transmitted; during the static migration execution, the UE will sequentially The DRNC sends the PDU sequence with sequence number 4. However, since the initial number of the sequence number in the sequence number information maintained by the DRNC is 0, it is not synchronized with the UE. Therefore, after receiving the PDU sequence with the sequence number 4, the DRNC determines.
  • the PDU sequence UE whose sequence number is before 4 is not correctly transmitted, and returns an RLC status report to the UE, informing that the PDU sequence of the UE whose sequence number is before 4 is not correctly transmitted, but actually the UE has received the sequence number sent by the SRNC before the migration.
  • the RLC status report sent correctly by the previous PDU sequence if the PDU sequence 1J with the sequence number before 4 is retransmitted, it will contradict the indication of the correctly sent RLC status report that has been received before, but if the sequence is not sent.
  • the PDU sequence before the number 4 is in contradiction with the indication of the newly received RLC status report, so the internal RLC module of the UE
  • the SRB and TRB between the UE and the DRNC are reset, causing the user to drop the call.
  • FIG. 3 shows a flow of the method, where the method includes the following steps:
  • Step 401 The DRNC receives the RLC sequence number information sent by the SRNC corresponding to the UE.
  • the SRNC may carry the RL C serial number information by using a message sent to the DRNC, such as a migration request message.
  • Step 402 During the static migration execution process, the DRNC processes the PDU sequence sent by the UE by using the RLC sequence number information.
  • the DRNC After the SRNC sends a migration request to the DRNC through the CN, the DRNC returns a migration request response to the CN, and after receiving the migration request response, the CN sends a migration command to the SRNC; then the SRNC sends a migration trigger command to the DRNC, and the DRNC receives the migration. After the command is triggered, the CN is notified to detect the migration trigger, and the migration (static migration) is performed. After the migration, the SRB and TRB between the DRNC and the UE are established, and the UE is used to send the PD. U sequence.
  • the DRNC processes the PDU sequence sent by the UE by two layers.
  • the RRC layer of the DRNC can use the RLC sequence number information sent by the SRNC to configure the RNC layer of the DRNC.
  • the RLC layer processes the PD U sequence transmitted by the UE by using the RLC sequence number information configured by the RRC layer.
  • the functions of the foregoing RLC layer and the RRC layer may be respectively implemented by corresponding RLC modules and RRC modules in the DRNC.
  • the SRNC provides the RLC serial number information to the DRNC, so that the DRNC and the UE maintain the same RLC serial number information during the static migration execution process, and use the RLC sequence.
  • the number information can correctly process the PDU sequence sent by the UE, so that the PDU sequence that the UE correctly transmits is not determined to be sent incorrectly, and the UE is prevented from being unable to perform the operation, thereby solving the problem of the user dropping the call. Improve the user experience.
  • the SRNC since the SRNC sends the RLC sequence number to the DRNC, after the DRNC receives the RLC sequence number sent by the S RNC, there are two types of RLC sequence number information on the DRNC, one of which is the SRNC.
  • the transmitted RLC sequence number information synchronized with the UE, and the other is the radio bearer RB' established between the DRNC and the UE, for example, after establishing SRB' and TRB', the established SRB' and TRB'
  • the initial value of the corresponding RLC serial number After the DRNC sends the UTRAN mobility information to the UE and receives the acknowledgment message returned by the UE, the DRNC confirms that the RLC sequence number information on the UE has been synchronized with the initial values of the SRB' and TRB' established by itself, and then DRNC The synchronized PDU sequence number can be used to start processing the PDU sequence sent by the UE. Before that, the DRNC processes the PDU sequence sent by the UE by using the RLC sequence number information provided by the SRNC.
  • the DRNC receives the PDU sequence sent by the UE, if the RLC sequence number of the PDU sequence is just right. If it is 0, the DRNC will not be able to determine whether the PDU sequence is sent by the UE according to the serial number between the UE and the SRNC, or whether the UE synchronizes with the serial number information on the DRNC. Therefore, in this case, Some schemes DRNC will return a notification to the UE that the RLC status report was not correctly sent. If the PDU sequence is indeed sent by the UE according to the sequence number between the previous and the SRNC, it may cause SRB' and TRB between the UE and the DRNC. 'Reset, causing the user to drop the call.
  • the embodiment of the present invention can also take the following implementation manners: After the DRNC processes the PDU sequence sent by the UE, the DRNC does not return the RLC status report to the UE, and after the static migration is completed, resumes returning the RLC status report to the UE, thereby ensuring maximum protection during the static migration process. The user dropped the call.
  • the method includes:
  • Step 501 The SRNC sends a migration request message to the DRNC through the CN, where the RRC container of the migration request message carries the RLC serial number information.
  • the RLC sequence number information provided by the SRNC is consistent with the RLC sequence number information maintained in the UE.
  • the foregoing RLC serial number information may include: sequence number information corresponding to the radio bearer RBs of the RLC layer of the SRNC.
  • the RLC sequence number information provided by the SRNC includes the foregoing SRNC.
  • the sequence number information corresponding to SRB 1 to SRB4 and TRB in the RB of the RLC layer is as shown in Table 1.
  • the meaning of each parameter in Table 1 is common knowledge of those skilled in the art.
  • the parameters shown in Table 1 can be extended according to actual needs. It can be understood that the foregoing RLC serial number information includes the serial number information corresponding to all the SRBs and TRBs of the RLC layer of the SRNC, but is a specific implementation manner used in the present embodiment.
  • the above sequence number information may also include only the sequence number information corresponding to the SRB or TRB of the RLC layer of the SRNC.
  • Step 502 The RRC layer of the DRNC uses the RLC sequence number information sent by the SRNC to the DRNC RL.
  • the C layer adds configuration.
  • the RLC sequence number information is configured to the SRBs l' ⁇ SRB4' and TRB' of the RLC layer of the DRNC. After this step, there are two serial number information in the DRNC.
  • Step 503 The RLC layer of the DRNC receives the PDU sequence lj sent by the UE through SRB1' ⁇ SRB4' and TRB', for example, an RRC measurement report, and determines whether the RLC sequence number of the received PDU sequence is greater than or equal to R.
  • the RLC sequence number configured by the RC layer is equal to 0. If yes, go to step 504, if the received PD
  • the RLC sequence number of the U sequence is smaller than the RLC sequence number configured by the RRC module and is not equal to 0, and the PDU sequence sent by the UE is discarded, and the process goes to step 505.
  • the C layer receives the PDU sequence sent by the UE through the SRB1', and the processing of the PDU sequence can be classified into the following cases:
  • the RLC sequence number of the PDU sequence is greater than or equal to the RLC sequence number configured by SRB1', and the PDU sequence is considered to be correctly transmitted. If it is equal, it indicates that the received PDU sequence is a sequence in which the UE sequentially transmits the sequence number information between the previous and the RNC, and the received PDU sequence is stored; if the RLC sequence number of the currently received PDU sequence is greater than the SRB RL.
  • the configured RLC sequence number because the DRNC supports the sorting function, the received PDU sequence can be stored, if the RLC sequence number of the subsequently received PDU sequence is located before the RLC sequence number of the PDU sequence that has been received and stored. , then sort the received PDU sequence.
  • the sequence number of the PDU sequence is equal to 0, and the embodiment of the present invention considers that the PDU sequence is correctly transmitted. This is a special case where the sequence number of the PDU sequence is exactly the same as the initial value of the sequence number corresponding to the DRNC establishing SRB1', and the DRNC also stores the PDU sequence.
  • Step 504 The RLC layer of the DRNC, the PDU sequence sent by the UE is formed into a Service Data Unit (SDU), and then sent to the RRC layer of the DRNC.
  • SDU Service Data Unit
  • Step 505 The RLC layer of the DRNC resumes returning the RLC status report to the UE after the static migration is completed.
  • the static migration completion flag is that the RRC layer of the DRNC sends the UTRAN mobility information to the UE, and receives the acknowledgement from the UE.
  • the foregoing steps 502 to 504 describe how the DRNC processes the P DU sequence sent by the UE during the static migration execution process, which may be referred to as a special case data transmission processing process, and the data transmission processing process in the special case.
  • the PDU sequence sent by the UE is processed by using the RLC sequence number information sent by the SRNC, and after the DRNC processes the PDU sequence sent by the UE, the DRNC does not return the RLC status report to the UE.
  • the RLC module in the DRNC ends the data transmission process of the above special case, and resumes the normal processing flow.
  • the normal processing flow starts, and the initial values of the serial number information maintained on the DRNC and the UE are both 0, that is, after the normal process starts, the PDU sequence sent by the UE is processed by using the RLC sequence number information sent by the SRNC, and the PDU sequence sent by the UE is processed by using the sequence number information with the initial value of 0, and the PDU sequence sent by the UE is processed. After resuming, the RLC status report is returned to the UE.
  • the SRNC sends the sequence number information to the DRNC, and uses the messages in the existing migration process to ensure compatibility with the existing solution; all SRB's and TRBs established for the DRNC are increased.
  • the sequence number information sent by the SRNC is configured so that no matter which radio bearer the PDU sequence is sent by the UE, the occurrence of dropped calls can be prevented; and during the static migration execution, the DRNC does not return the RLC status report to the UE, thereby avoiding special In the case of possible dropped calls, the possibility of dropped calls is prevented to the utmost extent.
  • FIG. 5 shows a schematic structure of the system, where the system includes:
  • the SRNC corresponding to the UE is used to send the RLC serial number information to the DRNC through the core network CN.
  • the DRNC is configured to process the PDU sequence sent by the UE by using the RLC sequence number information sent by the SRNC during the static migration execution.
  • CN configured to connect the SRNC and the DRNC.
  • the system reduces the number of dropped calls of the user in the static migration, and the SRNC provides the RLC serial number information to the DRNC, so that the DRNC and the UE maintain the same RLC serial number information during the static migration execution process, and use the RLC sequence.
  • the number information is correctly processed by the PDU sequence sent by the UE, so that the PDU sequence that the UE correctly transmits is not determined to be sent incorrectly, and the UE is prevented from performing an operation, thereby solving the problem of the user dropping the call.
  • the SRNC in the above system may include: a first RLC module and a sending module.
  • the first RLC module is configured to provide RLC sequence number information corresponding to the RBs of the SRNC itself.
  • the sending module is configured to carry the RLC serial number information provided by the first RLC module in the migration request message, and send the information to the DRNC by using the CN.
  • the DRNC in the above system may include: an RRC module and a second RLC module.
  • the RRC module is configured to receive RLC sequence number information sent by the SRNC during the static migration execution, and configure the RLC sequence number information to the second RLC module.
  • the second RLC module is configured to process the received PDU sequence by using the RLC sequence number information configured by the RRC module during the static migration execution.
  • the foregoing second RLC module may include: a radio bearer unit, a decision processing unit, and a status reporting unit.
  • a radio bearer unit configured to receive, by using a radio bearer of the DRNC, a PDU sequence sent by the UE, where the DRN
  • the RLC sequence number information corresponding to the radio bearer of C is configured by the RRC module.
  • a determining processing unit configured to determine whether an RLC sequence number of the PDU sequence received by the radio bearer unit is greater than or equal to an RLC sequence number configured by the RRC module, or equal to 0. If yes, the PDU sequence is formed into a service data unit. The SDU sequence is sent to the RRC module; if the RLC sequence number of the received PDU sequence is smaller than the RLC sequence number configured by the RRC module and is not equal to 0, the received PDU sequence is discarded.
  • a status reporting unit configured to resume sending an RLC status report to the UE after the static migration is completed.
  • the device for reducing the dropped call of the user in the static migration of the embodiment of the present invention is introduced.
  • the device may be an RNC.
  • the RNC includes the RRC module and the RNC.
  • the RRC module is configured to receive RLC sequence number information sent by the SRNC, and configure the RLC sequence number information to the RLC module of the RNC.
  • the RLC module is configured to process the received PDU sequence sent by the UE by using the RLC sequence number information configured by the RRC module during the static migration.
  • the RNC provided by the embodiment of the present invention, after performing the DRNC function, receives the RLC sequence number information sent by the corresponding SR NC by the RRC module, and configures the information to the RLC module, and the RLC module uses the RLC serial number configured by the RRC module.
  • the information correctly processes the PDU sequence sent by the UE, so that the PDU sequence that the UE correctly transmits is not determined to be sent incorrectly, and the UE is prevented from being unable to perform the operation, thereby solving the problem that the user is dropped.
  • the RLC module in the RNC provided by the foregoing embodiment of the present invention may include: a radio bearer unit, a decision processing unit, and a status reporting unit.
  • a radio bearer unit configured to receive, by using a radio bearer of the DRNC, a PDU sequence sent by the UE, where the RLC sequence number information corresponding to the radio bearer of the DRN C is configured by the RRC module;
  • a determining processing unit configured to determine whether an RLC sequence number of the PDU sequence received by the radio bearer unit is greater than or equal to an RLC sequence number configured by the RRC module, or equal to 0. If yes, the PDU sequence is formed into a service.
  • the data unit SDU sequence is sent to the RRC module; if the RLC sequence number of the received PDU sequence is smaller than the RLC sequence number configured by the RRC module and is not equal to 0, the received PDU sequence is discarded.
  • a status reporting unit configured to resume sending an RLC status report to the UE after the static migration is completed
  • the RNC provided in the embodiment of the present invention may be used as a SRNC in another static migration execution process, and the RNC may further include: a service RLC module and a sending module.
  • Service RLC module which is used to provide RLC serial number information corresponding to the SRNC ⁇ radio bearer RB.
  • a sending module configured to carry the RLC serial number information provided by the serving RLC module in the migration request message, by using CN
  • the DRNC is sent to the other static migration execution process, and the DRNC in the other static migration execution process corresponds to the RNC as the SRNC.
  • ROM read only memory
  • RAM random access memory
  • magnetic disk magnetic disk
  • optical disk or the like.
  • ROM read only memory
  • the above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto, and any person skilled in the art can easily think of within the technical scope disclosed by the present invention. Changes or substitutions are intended to be included within the scope of the invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Landscapes

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

Abstract

L'invention concerne un procédé permettant de réduire les abandons d'appels de l'utilisateur lors de la dérive statique. Le procédé consiste notamment en ce qu'un contrôleur de réseau radio dérivé (DRNC) reçoit les informations du numéro de la séquence de commande de liaison radio (RLC) envoyées par le contrôleur de réseau radio de service (SRNC); durant la dérive statique, le DRNC utilise les informations du numéro de la séquence de commande de liaison radio RLC pour traiter la séquence de l'unité de données de protocole (PDU) envoyée par l'équipement utilisateur (UE). L'invention concerne également un système permettant de réduire les abandons d'appels de l'utilisateur lors de la dérive statique et une unité de commande de réseau radio. Le désaccord entre les informations du numéro de la séquence de commande de liaison radio RLC conservées par l'équipement utilisateur et les informations du numéro de la séquence RLC conservées par DRNC lors de la dérive statique peut être résolu par lesdits procédé, système et contrôleur
PCT/CN2008/072858 2007-10-30 2008-10-28 Procédé, système et dispositif pour réduire les abandons d'appels de l'utilisateur lors de la dérive statique WO2009059531A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710164353.5 2007-10-30
CN2007101643535A CN101426244B (zh) 2007-10-30 2007-10-30 静态迁移中防止用户掉话的方法、系统和装置

Publications (1)

Publication Number Publication Date
WO2009059531A1 true WO2009059531A1 (fr) 2009-05-14

Family

ID=40616528

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072858 WO2009059531A1 (fr) 2007-10-30 2008-10-28 Procédé, système et dispositif pour réduire les abandons d'appels de l'utilisateur lors de la dérive statique

Country Status (2)

Country Link
CN (1) CN101426244B (fr)
WO (1) WO2009059531A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998506B (zh) * 2009-08-14 2015-04-01 中兴通讯股份有限公司 无线网络控制器获取控制信息的方法及系统
CN103369560B (zh) * 2012-03-29 2018-01-26 中兴通讯股份有限公司 一种获取gsm系统异常掉话数据的方法和系统
CN102932860B (zh) * 2012-10-31 2016-06-22 华为技术有限公司 一种避免无线链路控制rlc复位的方法和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030157927A1 (en) * 2002-02-16 2003-08-21 Lg Electronics Inc. Method for relocating SRNS in a mobile communication system
CN1438809A (zh) * 2002-02-16 2003-08-27 Lg电子株式会社 上下文重定位方法
US6725040B2 (en) * 2001-07-09 2004-04-20 Asustek Computer Inc. Lossless SRNS relocation procedure in a wireless communications system
CN101018392A (zh) * 2006-02-06 2007-08-15 中兴通讯股份有限公司 一种减少srns重定位过程中数据中断时间的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6725040B2 (en) * 2001-07-09 2004-04-20 Asustek Computer Inc. Lossless SRNS relocation procedure in a wireless communications system
US20030157927A1 (en) * 2002-02-16 2003-08-21 Lg Electronics Inc. Method for relocating SRNS in a mobile communication system
CN1438809A (zh) * 2002-02-16 2003-08-27 Lg电子株式会社 上下文重定位方法
CN101018392A (zh) * 2006-02-06 2007-08-15 中兴通讯股份有限公司 一种减少srns重定位过程中数据中断时间的方法

Also Published As

Publication number Publication date
CN101426244B (zh) 2010-12-15
CN101426244A (zh) 2009-05-06

Similar Documents

Publication Publication Date Title
US20210218507A1 (en) Duplication and rlc operation in new radio access technology
JP5547341B2 (ja) 無線装置において複数の無線アクセスベアラを制御する方法
US7209747B2 (en) Handling of an unrecoverable error on a dedicated channel
US7068636B2 (en) Method for determining RLC entity re-establishment during SRNS relocation
CN109429257B (zh) 用户设备和相关方法
WO2019096281A1 (fr) Procédé de communication, dispositif de communication et système de communication s'y rapportant
EP3592097B1 (fr) Procédé de gestion de défaillance de liaison radio et produit associé
EP2802168B1 (fr) Procédé et dispositif de transmission de données
EP1408658A2 (fr) Traitement d'un erreur non recupérable sur un canal dédiée d'une liaison radio
CN110999382B (zh) 用于控制分组复制的方法及设备
US20030210714A1 (en) Method for avoiding loss of pdcp pdus in a wireless communications system
EP2058987A1 (fr) Procédé pour traiter des erreurs de n ud de support de passerelle de domaine de paquets
WO2009059531A1 (fr) Procédé, système et dispositif pour réduire les abandons d'appels de l'utilisateur lors de la dérive statique
WO2020198961A1 (fr) Procédé et dispositif de reprise sur indicent de liaison
TWI513259B (zh) 訊息處理
WO2022120744A1 (fr) Procédé de traitement de transmission de données et appareil associé
CN116762379A (zh) 用于数据传输的方法及设备
CN113141675A (zh) 一种rrc连接重配的方法及装置
KR20070047518A (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: 08846999

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

Country of ref document: EP

Kind code of ref document: A1