US20130130704A1 - Method and apparatus for validating radio resource control messages - Google Patents
Method and apparatus for validating radio resource control messages Download PDFInfo
- Publication number
- US20130130704A1 US20130130704A1 US13/686,373 US201213686373A US2013130704A1 US 20130130704 A1 US20130130704 A1 US 20130130704A1 US 201213686373 A US201213686373 A US 201213686373A US 2013130704 A1 US2013130704 A1 US 2013130704A1
- Authority
- US
- United States
- Prior art keywords
- wtru
- rrc message
- message
- cell
- valid
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/10—Integrity
- H04W12/106—Packet or message integrity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/22—Manipulation of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
Definitions
- the present invention generally relates to wireless communication systems, and more particularly, to a method and apparatus for validating radio resource control messages.
- the 3GPP standard 25.331 specifies the radio resource control (RRC) protocol for the radio interface between a wireless transmit/receive unit (WTRU) and a UMTS terrestrial radio access network (UTRAN).
- RRC radio resource control
- Section 8.6 of standard 25.331 describes the rules that the WTRU must follow for validating downlink peer messages received from the UTRAN. Included in this section are rules regarding transport channel information elements (IEs).
- IEs transport channel information elements
- the standard states in Section 8.6.5.2 that if the IE “Transport format combination set” is not included and either (1) if no transport format combination set is stored in the WTRU; or (2) if transport channels are added or removed in the message; or (3) if any transport channel is reconfigured in the message such that the size of the transport format set is changed, then the WTRU shall set the variable INVALID CONFIGURATION to TRUE.
- the WTRU should reject the peer message.
- the rule does not take additional information into account, such as the type of transport channel being modified, the configured RRC state of the WTRU, etc.
- the two basic operational modes of a WTRU are “Idle” and “Connected” modes.
- the Connected mode is further divided into several RRC states (i.e., a CELL_DCH state, a CELL_FACH state, a CELL_PCH state, and a URA_PCH state), which define the kind of channels that the WTRU is using.
- a CELL_DCH state dedicated channels are allocated to the WTRU.
- the CELL_FACH state no dedicated channel is allocated for the WTRU but the WTRU uses common channels which are shared by all WTRUs.
- the WTRU may receive (and must retain) certain information regarding dedicated channels. This information may then be used by the WTRU if the WTRU is directed by UTRAN to transition into the CELL_DCH state.
- a WTRU under test failed several connection attempts. Analysis showed that the WTRU was rejecting the network's RRC connection setup message because it broke the validation rule. Specifically, the message was directing the WTRU to the CELL_FACH state and was adding a dedicated transport channel, but was not including a transport format combination set (TFCS). The problem was that the validation rule was indeed broken as written. Based on this test result, the implementation of the validation rule could benefit from being more flexible.
- TFCS transport format combination set
- a UTRAN sends a message to the WTRU directing it to a CELL_FACH state and removing a transport channel, but not including a new TFCS.
- the WTRU accepts this message because the transport channels will not be used in the CELL_FACH state.
- a UTRAN sends a message to the WTRU directing it to a CELL_DCH state, including neither new transport channel information nor a new TFCS.
- the WTRU accepts this message because it does not break the validation rule.
- the WTRU will not be able to operate in the CELL_DCH state because it lacks the appropriate transport channel information or TFCS.
- a method for validating radio resource control (RRC) messages includes determining whether an RRC message received by a wireless transmit-receive unit (WTRU) is valid based on: an RRC state for which the WTRU is configured, whether or not the WTRU needs a new transport format combination set, and whether or not the RRC message will configure the WTRU for a CELL_DCH state.
- RRC radio resource control
- a WTRU includes a rule application device configured to implement the method.
- FIG. 1 is a flowchart of a method for applying a validation rule to an incoming RRC message
- FIG. 2 is a block diagram of a device configured to apply a validation rule to an incoming RRC message.
- wireless transmit/receive unit includes, but is not limited to, a user equipment, a mobile station, a fixed or mobile subscriber unit, a pager, or any other type of device capable of operating in a wireless environment.
- base station includes, but is not limited to, a Node B, a site controller, an access point, or any other type of interfacing device in a wireless environment.
- a WTRU wants to allow for a liberal interpretation of the validation rule as defined in the standard (and therefore operate in the most networks possible) and still protect itself against invalid configurations, the WTRU must perform transport channel validation in a manner not described in the standard.
- FIG. 1 is a flowchart of a method 100 for applying the standard validation rule to an incoming message.
- the method 100 begins by receiving a peer message at a WTRU (step 102 ).
- the WTRU applies the validation rule to the received message (step 104 ).
- a determination is made whether the WTRU needs a new TFCS based on the received peer message (step 106 ). If the WTRU needs a new TFCS, then a TFCS indicator (e.g., a TFCS_NEEDED flag) is set to true (step 108 ).
- the TFCS indicator is maintained in the WTRU. If the WTRU does not need a new TFCS, then the TFCS indicator is left unchanged.
- the TFCS indicator e.g., the TFCS_NEEDED flag
- the WTRU Since the WTRU needs a new TFCS and the network has not supplied the new TFCS during configuration for the CELL_DCH state, the message is properly rejected. If the TFCS indicator is set to false, then the message is accepted (step 116 ) and the method terminates (step 118 ). Since the network has supplied the WTRU with a new TFCS prior to or during configuration into the CELL_DCH state, the WTRU correctly accepts the message. In all cases, the WTRU continues operating error-free in the data plane.
- the present invention allows the WTRU to operate on networks that interpret the validation rule liberally.
- the present invention also allows the WTRU to still protect itself against invalid configurations and, therefore, continue operating without self-induced errors in the data plane (leading to less retry and/or fallback handling, and ultimately fewer dropped calls).
- the WTRU may not apply the TFCS validation rule, but the WTRU risks accepting invalid configurations or dropping calls.
- the WTRU may delay applying the cited TFCS validation rule until the WTRU is configured for the CELL_DCH state. In this case, the WTRU also risks accepting invalid configurations or dropping calls.
- FIG. 2 is a block diagram of a device 200 configured to apply a validation rule to an incoming RRC message.
- the device 200 is a WTRU.
- the device 200 includes a receiver 202 , a rule application device 204 in communication with the receiver 202 , a message accepting device 206 in communication with the rule application device 204 , and a message rejecting device 208 in communication with the rule application device 204 .
- the receiver 202 receives an incoming RRC message for the device 200 .
- the rule application device 204 applies a message validation rule to the received message and checks the configured state of the WTRU. If the message passes the validation rule or is not configured for the CELL_DCH state, then the message accepting device 206 takes the message and processes it accordingly. If the message fails the validation rule and is configured for the CELL_DCH state, then the message is passed to the message rejecting device 208 and is discarded.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
A method for validating radio resource control (RRC) messages includes determining whether an RRC message received by a wireless transmit-receive unit (WTRU) is valid based on: an RRC state for which the WTRU is configured, whether or not the WTRU needs a new transport format combination set, and whether or not the RRC message will configure the WTRU for a CELL_DCH state. A WTRU includes a rule application device configured to implement the method.
Description
- This application is a continuation of U.S. patent application Ser. No. 11/312,006, filed Dec. 20, 2005, which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/667,449 filed on Apr. 1, 2005, which are incorporated by reference as if fully set forth.
- The present invention generally relates to wireless communication systems, and more particularly, to a method and apparatus for validating radio resource control messages.
- The 3GPP standard 25.331 specifies the radio resource control (RRC) protocol for the radio interface between a wireless transmit/receive unit (WTRU) and a UMTS terrestrial radio access network (UTRAN). Section 8.6 of standard 25.331 describes the rules that the WTRU must follow for validating downlink peer messages received from the UTRAN. Included in this section are rules regarding transport channel information elements (IEs).
- Specifically, the standard states in Section 8.6.5.2 that if the IE “Transport format combination set” is not included and either (1) if no transport format combination set is stored in the WTRU; or (2) if transport channels are added or removed in the message; or (3) if any transport channel is reconfigured in the message such that the size of the transport format set is changed, then the WTRU shall set the variable INVALID CONFIGURATION to TRUE.
- This means that if the any of the above conditions are met, the WTRU should reject the peer message. The rule does not take additional information into account, such as the type of transport channel being modified, the configured RRC state of the WTRU, etc.
- The two basic operational modes of a WTRU are “Idle” and “Connected” modes. The Connected mode is further divided into several RRC states (i.e., a CELL_DCH state, a CELL_FACH state, a CELL_PCH state, and a URA_PCH state), which define the kind of channels that the WTRU is using. In the CELL_DCH state, dedicated channels are allocated to the WTRU. In the CELL_FACH state, no dedicated channel is allocated for the WTRU but the WTRU uses common channels which are shared by all WTRUs. While in the CELL_FACH state, the WTRU may receive (and must retain) certain information regarding dedicated channels. This information may then be used by the WTRU if the WTRU is directed by UTRAN to transition into the CELL_DCH state.
- During an interoperability test session, a WTRU under test failed several connection attempts. Analysis showed that the WTRU was rejecting the network's RRC connection setup message because it broke the validation rule. Specifically, the message was directing the WTRU to the CELL_FACH state and was adding a dedicated transport channel, but was not including a transport format combination set (TFCS). The problem was that the validation rule was indeed broken as written. Based on this test result, the implementation of the validation rule could benefit from being more flexible.
- Network operators may be tempted to read this rule liberally, thinking that the rule should only apply to transport channel elements that the WTRU will use in its immediately configured RRC state. The temptation (and perhaps confusion) is reinforced by the current ASN.1 message syntax which requires networks to add dedicated transport channels to all WTRUs upon RRC connection setup, even those being configured for the CELL_FACH state. However, simply delaying an application of the rule until such time as the channels will be used (i.e., when the WTRU is configured for CELL_DCH) will not suffice since the rule is transaction-based. By applying the rule as it is written, the WTRU may reject an operable configuration (such as in the case described above). But by delaying the application of the rule, as the following example shows, the WTRU may accept an inoperable configuration, which is arguably worse.
- For example, consider a WTRU that is operating in a CELL_DCH state. A UTRAN sends a message to the WTRU directing it to a CELL_FACH state and removing a transport channel, but not including a new TFCS. The WTRU accepts this message because the transport channels will not be used in the CELL_FACH state. A UTRAN sends a message to the WTRU directing it to a CELL_DCH state, including neither new transport channel information nor a new TFCS. The WTRU accepts this message because it does not break the validation rule. However, the WTRU will not be able to operate in the CELL_DCH state because it lacks the appropriate transport channel information or TFCS.
- A method for validating radio resource control (RRC) messages includes determining whether an RRC message received by a wireless transmit-receive unit (WTRU) is valid based on: an RRC state for which the WTRU is configured, whether or not the WTRU needs a new transport format combination set, and whether or not the RRC message will configure the WTRU for a CELL_DCH state.
- A WTRU includes a rule application device configured to implement the method.
- A more detailed understanding of the invention may be had from the following description of a preferred embodiment, given by way of example, and to be understood in conjunction with the accompanying drawings, wherein:
-
FIG. 1 is a flowchart of a method for applying a validation rule to an incoming RRC message; and -
FIG. 2 is a block diagram of a device configured to apply a validation rule to an incoming RRC message. - Hereafter, the term “wireless transmit/receive unit” (WTRU) includes, but is not limited to, a user equipment, a mobile station, a fixed or mobile subscriber unit, a pager, or any other type of device capable of operating in a wireless environment. When referred to hereafter, the term “base station” includes, but is not limited to, a Node B, a site controller, an access point, or any other type of interfacing device in a wireless environment.
- If a WTRU wants to allow for a liberal interpretation of the validation rule as defined in the standard (and therefore operate in the most networks possible) and still protect itself against invalid configurations, the WTRU must perform transport channel validation in a manner not described in the standard.
-
FIG. 1 is a flowchart of amethod 100 for applying the standard validation rule to an incoming message. Themethod 100 begins by receiving a peer message at a WTRU (step 102). The WTRU applies the validation rule to the received message (step 104). A determination is made whether the WTRU needs a new TFCS based on the received peer message (step 106). If the WTRU needs a new TFCS, then a TFCS indicator (e.g., a TFCS_NEEDED flag) is set to true (step 108). The TFCS indicator is maintained in the WTRU. If the WTRU does not need a new TFCS, then the TFCS indicator is left unchanged. - Next, a determination is made whether the WTRU received a new TFCS in the received peer message (step 110). If the WTRU received a new TFCS, then the TFCS indicator (e.g., the TFCS_NEEDED flag) is set to false (step 112). If the WTRU did not receive a new TFCS, then the TFCS indicator is left unchanged.
- A determination is then made whether the WTRU is configuring itself for the CELL_DCH state based on the received peer message (step 114). If the WTRU is not configuring itself for the CELL_DCH state, then the message is accepted (step 116) and the method terminates (step 118). If the WTRU is configuring itself for the CELL_DCH state (step 114), then the TFCS indicator is evaluated to determine if it is set to true or false (step 120). If the TFCS indicator is set to true, then the WTRU rejects the message (step 122) and the method terminates (step 118). Since the WTRU needs a new TFCS and the network has not supplied the new TFCS during configuration for the CELL_DCH state, the message is properly rejected. If the TFCS indicator is set to false, then the message is accepted (step 116) and the method terminates (step 118). Since the network has supplied the WTRU with a new TFCS prior to or during configuration into the CELL_DCH state, the WTRU correctly accepts the message. In all cases, the WTRU continues operating error-free in the data plane.
- The present invention allows the WTRU to operate on networks that interpret the validation rule liberally. The present invention also allows the WTRU to still protect itself against invalid configurations and, therefore, continue operating without self-induced errors in the data plane (leading to less retry and/or fallback handling, and ultimately fewer dropped calls).
- Alternatively, the WTRU may not apply the TFCS validation rule, but the WTRU risks accepting invalid configurations or dropping calls. Another alternative is that the WTRU may delay applying the cited TFCS validation rule until the WTRU is configured for the CELL_DCH state. In this case, the WTRU also risks accepting invalid configurations or dropping calls.
-
FIG. 2 is a block diagram of adevice 200 configured to apply a validation rule to an incoming RRC message. In a preferred embodiment, thedevice 200 is a WTRU. Thedevice 200 includes areceiver 202, arule application device 204 in communication with thereceiver 202, amessage accepting device 206 in communication with therule application device 204, and amessage rejecting device 208 in communication with therule application device 204. In operation, thereceiver 202 receives an incoming RRC message for thedevice 200. Therule application device 204 applies a message validation rule to the received message and checks the configured state of the WTRU. If the message passes the validation rule or is not configured for the CELL_DCH state, then themessage accepting device 206 takes the message and processes it accordingly. If the message fails the validation rule and is configured for the CELL_DCH state, then the message is passed to themessage rejecting device 208 and is discarded. - Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention.
Claims (11)
1. A method for validating radio resource control (RRC) messages, comprising:
determining whether an RRC message received by a wireless transmit-receive unit (WTRU) is valid based on:
an RRC state for which the WTRU is configured;
whether or not the WTRU needs a new transport format combination set (TFCS); and
whether or not the RRC message will configure the WTRU for a CELL_DCH state.
2. The method of claim 1 further comprising:
accepting the RRC message on a condition that the RRC message is valid; and
rejecting the RRC message on a condition that the RRC message is not valid.
3. The method according to claim 1 , wherein the RRC message is valid on a condition that the WTRU receives a new TFCS.
4. The method according to claim 1 , wherein the RRC message is valid on a condition that the RRC message will not configure the WTRU for the CELL_DCH state.
5. The method according to claim 1 , wherein the RRC message is valid on a condition that:
the RRC message will configure the WTRU for the CELL_DCH state; and
the WTRU does not need a new TFCS.
6. A wireless transmit/receive unit (WTRU), comprising:
a rule application device, configured to determine whether an RRC message received by the WTRU is valid based on:
an RRC state for which the WTRU is configured;
whether or not the WTRU needs a new transport format combination set (TFCS); and
whether or not the RRC message will configure the WTRU for a CELL_DCH state.
7. The WTRU of claim 6 , further comprising:
a message accepting device, configured to accept the RRC message on a condition that the RRC message is valid; and
a message rejecting device, configured to reject the RRC message on a condition that the RRC message is not valid.
8. The WTRU according to claim 6 , wherein the rule application device is configured to determine that the RRC message is valid on a condition that the WTRU receives a new TFCS.
9. The WTRU according to claim 6 , wherein the rule application device is configured to determine that the RRC message is valid on a condition that the RRC message will not configure the WTRU for the CELL_DCH state.
10. The WTRU according to claim 6 , wherein the rule application device is configured to determine that the RRC message is valid on a condition that:
the RRC message will configure the WTRU for the CELL_DCH state; and
the WTRU does not need a new TFCS.
11. The WTRU according to claim 6 , wherein the rule application device is further configured to:
determine whether the RRC message will configure the WTRU for a CELL_DCH state; and
determine whether the WTRU needs a new TFCS based on the RRC message.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/686,373 US20130130704A1 (en) | 2005-04-01 | 2012-11-27 | Method and apparatus for validating radio resource control messages |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US66744905P | 2005-04-01 | 2005-04-01 | |
US11/312,006 US8320923B2 (en) | 2005-04-01 | 2005-12-20 | Method and apparatus for validating radio resource control messages |
US13/686,373 US20130130704A1 (en) | 2005-04-01 | 2012-11-27 | Method and apparatus for validating radio resource control messages |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/312,006 Continuation US8320923B2 (en) | 2005-04-01 | 2005-12-20 | Method and apparatus for validating radio resource control messages |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130130704A1 true US20130130704A1 (en) | 2013-05-23 |
Family
ID=37071254
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/312,006 Expired - Fee Related US8320923B2 (en) | 2005-04-01 | 2005-12-20 | Method and apparatus for validating radio resource control messages |
US13/686,373 Abandoned US20130130704A1 (en) | 2005-04-01 | 2012-11-27 | Method and apparatus for validating radio resource control messages |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/312,006 Expired - Fee Related US8320923B2 (en) | 2005-04-01 | 2005-12-20 | Method and apparatus for validating radio resource control messages |
Country Status (9)
Country | Link |
---|---|
US (2) | US8320923B2 (en) |
EP (1) | EP1867180A4 (en) |
JP (1) | JP2008535399A (en) |
KR (2) | KR20070122226A (en) |
CA (1) | CA2615985A1 (en) |
MX (1) | MX2007012138A (en) |
NO (1) | NO20075401L (en) |
TW (3) | TWI419523B (en) |
WO (1) | WO2006107699A2 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2140631B1 (en) * | 2007-05-02 | 2018-06-20 | Nokia Technologies Oy | System and method for improving reordering functionality in radio communications |
KR101428093B1 (en) * | 2008-09-08 | 2014-08-08 | 현대자동차주식회사 | Validity diagnostic apparatus of data on network for a vehicle |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100602024B1 (en) | 1999-11-01 | 2006-07-20 | 유티스타콤코리아 유한회사 | Method for transmitting radio resource control message in asynchronous mobile communication system |
GB2355890B (en) | 1999-10-28 | 2003-10-08 | Ericsson Telefon Ab L M | Data transmission in a telecommunications network |
US7046992B2 (en) * | 2001-05-11 | 2006-05-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Authentication of termination messages in telecommunications system |
CN1173500C (en) * | 2001-12-05 | 2004-10-27 | 华为技术有限公司 | High-speed down data packet accessing system support method to different service quality business |
GB2382956B (en) | 2001-12-05 | 2006-03-01 | Ipwireless Inc | Method and arrangement for power control |
US20040266461A1 (en) * | 2002-05-24 | 2004-12-30 | Mark Beckmann | Method and system for transmitting data |
CA2486995A1 (en) | 2002-05-29 | 2003-12-11 | Interdigital Technology Corporation | Packet switched connections using dedicated channels |
WO2004034680A1 (en) | 2002-10-07 | 2004-04-22 | Interdigital Technology Corporation | System and method for simulation of performance of measurement-based algorithms for slotted wireless communications |
US20040224669A1 (en) | 2003-05-08 | 2004-11-11 | Pedlar David W. | Apparatus and method of handling universal terrestrial radio access network radio resource control connecting messages in universal mobile telecommunications system user equipment |
KR100947741B1 (en) | 2003-05-09 | 2010-03-17 | 엘지전자 주식회사 | Rrc connection setup method in a mobile communication system |
KR100548344B1 (en) | 2003-05-13 | 2006-02-02 | 엘지전자 주식회사 | Rrc connection method in mobile communication system |
WO2004114574A2 (en) | 2003-06-17 | 2004-12-29 | Knowmotion, Llc | Group network methods and systems |
US7406314B2 (en) * | 2003-07-11 | 2008-07-29 | Interdigital Technology Corporation | Wireless transmit receive unit having a transition state for transitioning from monitoring to duplex connected states and method |
TWI268724B (en) * | 2003-07-17 | 2006-12-11 | Interdigital Tech Corp | Method and system for delivery of assistance data |
ATE398875T1 (en) * | 2003-09-09 | 2008-07-15 | Interdigital Tech Corp | TRANSPORT FORMAT COMBINATION LOOKUP AND RESELECTION |
EP1530393B1 (en) * | 2003-11-07 | 2008-07-02 | Research in Motion Limited | Processing configuration and mobility management messages with missing Ciphering Activation Time for DPCH information in a universal mobile telecommunications system (UMTS) |
FI20031671A (en) * | 2003-11-17 | 2005-05-18 | Nokia Corp | A method and apparatus for correctly reporting received transport blocks on a wireless system |
WO2005112500A1 (en) * | 2004-05-13 | 2005-11-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Reestablishing wireless communication between a radio access network and a mobile station |
US7580388B2 (en) * | 2004-06-01 | 2009-08-25 | Lg Electronics Inc. | Method and apparatus for providing enhanced messages on common control channel in wireless communication system |
KR101059876B1 (en) | 2004-06-16 | 2011-08-29 | 엘지전자 주식회사 | Data Transmission Volume Selection Method for Guaranteeing Service Quality of Mobile Communication System |
-
2005
- 2005-12-20 US US11/312,006 patent/US8320923B2/en not_active Expired - Fee Related
-
2006
- 2006-03-28 TW TW095137441A patent/TWI419523B/en not_active IP Right Cessation
- 2006-03-28 TW TW095110820A patent/TWI300313B/en not_active IP Right Cessation
- 2006-03-28 TW TW098111582A patent/TWI403189B/en not_active IP Right Cessation
- 2006-03-30 JP JP2008504355A patent/JP2008535399A/en active Pending
- 2006-03-30 KR KR1020077024976A patent/KR20070122226A/en not_active IP Right Cessation
- 2006-03-30 CA CA002615985A patent/CA2615985A1/en not_active Abandoned
- 2006-03-30 EP EP06740038A patent/EP1867180A4/en not_active Withdrawn
- 2006-03-30 KR KR1020087005794A patent/KR20080031512A/en not_active Application Discontinuation
- 2006-03-30 MX MX2007012138A patent/MX2007012138A/en not_active Application Discontinuation
- 2006-03-30 WO PCT/US2006/011635 patent/WO2006107699A2/en active Search and Examination
-
2007
- 2007-10-24 NO NO20075401A patent/NO20075401L/en not_active Application Discontinuation
-
2012
- 2012-11-27 US US13/686,373 patent/US20130130704A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
KR20080031512A (en) | 2008-04-08 |
WO2006107699A3 (en) | 2008-01-24 |
EP1867180A2 (en) | 2007-12-19 |
MX2007012138A (en) | 2008-04-04 |
TW200733766A (en) | 2007-09-01 |
TWI419523B (en) | 2013-12-11 |
WO2006107699A2 (en) | 2006-10-12 |
US20060223551A1 (en) | 2006-10-05 |
TWI300313B (en) | 2008-08-21 |
CA2615985A1 (en) | 2006-10-12 |
TW200640270A (en) | 2006-11-16 |
TW201014373A (en) | 2010-04-01 |
JP2008535399A (en) | 2008-08-28 |
EP1867180A4 (en) | 2008-07-23 |
TWI403189B (en) | 2013-07-21 |
NO20075401L (en) | 2007-10-24 |
US8320923B2 (en) | 2012-11-27 |
KR20070122226A (en) | 2007-12-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1969737B1 (en) | Method for reading dynamic system information blocks | |
US8971790B2 (en) | Method and apparatus for broadcast services in a communication system | |
KR20200064135A (en) | Data transmission channel processing method, apparatus, and system | |
US8116282B2 (en) | Method and apparatus for mapping 3GPP service primitives to media independent handover event services | |
EP2422561A1 (en) | Access control with partial support for communications | |
USRE43630E1 (en) | Data transmission method with a lower probability of erroneous rejection of data | |
US11438806B2 (en) | Terminal apparatus, base station apparatus, and method | |
US20200280886A1 (en) | Terminal apparatus and method | |
EP1389400B1 (en) | Synchronization of stored service parameters in a communication system | |
US11115896B2 (en) | Handling QoS rules on QoS operation errors | |
US20130130704A1 (en) | Method and apparatus for validating radio resource control messages | |
US11265771B2 (en) | AT commands for supporting session and service continuity modes of 5G protocol data unitsession operations | |
CN116614172A (en) | Satellite communication method, nonvolatile storage medium, and electronic device | |
US11228943B2 (en) | Signaling transmission method and apparatus, base station, and terminal | |
MXPA06003854A (en) | A method and a device for reconfiguration in a wireless system. | |
US7961655B2 (en) | Method and apparatus for performing radio bearer mapping in a wireless communications system | |
US20120087243A1 (en) | Message Processing Method and System | |
CN116762467A (en) | Session management method and apparatus in mobile communication system | |
WO2023139852A1 (en) | Terminal, base station, and communication method | |
US20230136984A1 (en) | Method and apparatus for verifying compliance with ue route selection policy | |
CN117880794A (en) | Communication method and device | |
CN117413616A (en) | Method and apparatus for managing backhaul information-based sessions in a wireless communication system | |
CN115843029A (en) | Network authentication method and device | |
KR100782591B1 (en) | A method and a device for reconfiguration in a wireless system | |
CN117560737A (en) | Communication method and communication device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |