WO2011057438A1 - Procédé et dispositif de traitement de message pour architecture lte-a - Google Patents

Procédé et dispositif de traitement de message pour architecture lte-a Download PDF

Info

Publication number
WO2011057438A1
WO2011057438A1 PCT/CN2009/074836 CN2009074836W WO2011057438A1 WO 2011057438 A1 WO2011057438 A1 WO 2011057438A1 CN 2009074836 W CN2009074836 W CN 2009074836W WO 2011057438 A1 WO2011057438 A1 WO 2011057438A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
priority
rrc
terminal
messages
Prior art date
Application number
PCT/CN2009/074836
Other languages
English (en)
Chinese (zh)
Inventor
张亮亮
陈卓
王燕
蔺波
郭雅莉
李亚娟
常俊仁
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN2009801464566A priority Critical patent/CN102227924A/zh
Priority to PCT/CN2009/074836 priority patent/WO2011057438A1/fr
Publication of WO2011057438A1 publication Critical patent/WO2011057438A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present invention relates to the field of communications, and in particular, to a LTE-A message processing method and device.
  • FIG. 1 is a schematic diagram of an LTE-A radio access network, where the network includes a donor base station
  • DeNB Donor eNodeB
  • RN Relay Node
  • UE User Equipment
  • Each user equipment is also a terminal, and the three terminals are respectively labeled as UE1, UE2, and UE3, and the interface between them and the RN is a Uu interface; the interface between the RN and the DeNB is an Un port;
  • the interface is called an X2 interface; the interface between the base station and the Mobility Management Entity (MME) or the gateway (GW, Gateway) is an SI interface.
  • MME Mobility Management Entity
  • GW Gateway
  • an S1 message or an X2 message is carried over the RRC.
  • the RRC message is transmitted in the form of SRB (Signaling Radio Bearer).
  • the SRB can also carry NAS (Non-Access Stratum) messages.
  • the SRBs can be classified into three types, namely SRB0, SRB1, and SRB2.
  • the SRBO uses the Common Control Channel (hereinafter referred to as CCCH) logical channel to transmit RRC messages;
  • SRB1 uses a Dedicated Control Channel (hereinafter referred to as DCCH) logical channel to transmit RRC messages and NAS messages;
  • SRB2 uses DCCH logical channels. Transfer NAS messages.
  • SRB1 and SRB2 using DCCH logical channels SRB1 has higher priority than SRB1, and logical channel corresponding to SRB1
  • the priority is 1 and is the highest priority. It is usually expressed as logical channel priority 1 and the logical channel priority corresponding to SRB2 is 3, which is usually expressed as logical channel priority 3.
  • the higher the logical channel priority the higher the MAC layer scheduling priority.
  • the system schedules the infinity priority bit rate (Prireitized Bit Rate), which means how much resources the system currently has, and how much resources are provided for the corresponding SRB1 and SRB2.
  • the prior art has at least the following disadvantages: The prior art performs the same processing procedure for all S1 messages or X2 messages, and cannot perform targeted processing on different types of S1 messages or X2 messages, and the manner of message processing is not flexible enough.
  • the embodiment of the invention provides a LTE-A message processing method and device, which can flexibly process different types of S1 messages or X2 messages.
  • An embodiment of the present invention provides a LTE-A message processing method, including:
  • the radio resource control message is mapped in a signaling radio bearer corresponding to the priority.
  • An embodiment of the present invention further provides an LTE-A message processing device, including:
  • a priority determining unit configured to acquire an S1 message or an X2 message, and determine a priority of the S1 message or the X2 message
  • a bearer unit configured to carry the S1 message or the X2 message in a radio resource control message
  • the first mapping unit is configured to map the radio resource control message in a signaling radio bearer corresponding to the priority.
  • the S1 message or the X2 message of different priorities is mapped in different signaling radio bearers by using the priority of the S1 message or the X2 message, so that the S1 message or the X2 message with high priority is obtained.
  • 1 is a schematic diagram of an LTE-A radio access network
  • FIG. 2 is a schematic diagram of a LTE-A message processing method according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an SRB mapping process according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of another SRB mapping process according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of another SRB mapping process according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a message processing device of LTE-A according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of a LTE-A message processing method according to an embodiment of the present disclosure, where the method includes:
  • S21 Obtain an S1 message or an X2 message, and determine a priority of the S1 message or the X2 message.
  • S22 The S1 message or the X2 message is carried in a radio resource control message.
  • the S1 message or the X2 message of different priorities are mapped in different signaling radio bearers, so that the S1 message or the X2 message with high priority can be mapped to the high priority.
  • the signaling radio bearer and prioritized scheduling, the flexibility of message processing can be increased.
  • the mapping the radio resource control message to the priority pair The signaling radio bearer includes: when the priority of the S1 message or the X2 message is a high priority, mapping the radio resource control message in a high priority first signaling radio bearer; When the priority of the S1 message or the X2 message is low priority, the RRC message mapping is transmitted in the second signaling radio bearer of the low priority.
  • determining the priority of the S1 message or the X2 message includes: determining, when the S1 message or the X2 message is a message related to the terminal, that the S1 message or the X2 message is a high priority; When the S1 message or the X2 message is a message that is not related to the terminal, it is determined that the S1 message or the X2 message is a priority.
  • determining the priority of the S1 message or the X2 message includes: determining that the S1 message or the X2 message is a high priority when the S1 message or the X2 message is a delay sensitive message Level: When the S1 message or the X2 message is a message that is not sensitive to delay, it is determined that the S1 message or the X2 message is low priority.
  • the foregoing process classifies the S1 message or the X2 message into two categories according to whether the terminal is related or sensitive to delay. In fact, the type of the S1 message or the X2 message may be divided according to other manners.
  • the S1 message or the X2 message may be classified into a UE-specific (UE-Specific) and delay-sensitive message, a terminal-related and delay-insensitive message, and not related to the terminal (Non-UE-Specific)
  • the message class 3 where the first type of message is high priority and the low class 2 message is low priority.
  • the S1 message or the X2 message may also be classified into a terminal-related and delay-sensitive message, a terminal-related and delay-insensitive message, a terminal-insensitive and delay-sensitive message, and not related to the terminal.
  • the delay-insensitive message class 4 wherein the first two types of messages are high priority, and the latter two types of messages are low priority; the first and third types of messages in the four types of messages may also be set as high priority. Level, second and fourth type messages are low priority. How to divide messages into different priorities according to the classification of different messages and there are many ways, here no longer - enumeration, the personnel in the field can flexibly determine different types of messages according to specific application scenarios and actual needs. priority.
  • the method may further include: determining a sub-priority of the S1 message or the X2 message, and mapping the signaling radio bearer to a logical channel corresponding to the sub-priority.
  • the signaling radio bearer may also be configured to correspond to multiple logical channels of different priorities, so that different sub-priority messages are The transmission on different corresponding logical channels further divides the priority of related messages to ensure that messages of different sub-priorities of the same priority can be processed in sequence, further increasing the flexibility of processing messages.
  • an indication information element may be added to the RRC message to indicate the type or priority of the S1 message or the X2 message.
  • the indication information unit may be an IE (Information Element) or an IE Container (container;), and the S1 or X2 message may be placed in the IE or IE Container.
  • the receiver may read the indication information unit in the RRC message to obtain the S1 included in the RRC message. The type or priority of the message or X2 message, so that the S1 message is subsequently processed in the S1 protocol stack, and the X2 message is placed in the X2 protocol stack.
  • the S1 message including the high priority may be carried in the RRC message, for example, the S1 message may be included in the S1AP_priority1 IE, and the IE is carried in the RRC message; or
  • the high priority S 1 message is included in the SlAP_UE_Specific IE, and the IE is carried in a radio resource control message, and the radio resource control message is transmitted in a high priority SRB, such as SRB 1, that is,
  • the high-priority S1 message is mapped to the high-priority SRB, so that high-priority scheduling and processing can be obtained, and correspondingly, the receiver also performs high-priority scheduling and processing on the S1 message.
  • the S1 message including the low priority may be carried in the RRC message, such as the S1 message may be included in the S1AP_priority3 IE, and the IE is carried in the RRC message. Or; include the S1 message in the SlAP_Non_UE_Specific IE, and carry the IE in a certain radio resource control message, and the radio resource control message is transmitted in the low priority SRB, such as SRB3, that is, it will be low
  • the priority S1 message is mapped to the low priority SRB. For the same reason, the same is true for the X2 message, which is not specifically extended here.
  • radio resource control message may carry a particular type of message of a particular priority (such as an S1 or X2 message).
  • a particular type of message of a particular priority such as an S1 or X2 message.
  • the eNB or the IE Container is not required to be instructed by the IE or the IE Container, and the MAC layer performs scheduling according to the SRB priority corresponding to the specific radio resource control message, and the corresponding receiver controls the message according to the specific radio resource.
  • the type knows whether it is an S1 message or an X2 message.
  • the specific radio resource control message may be a newly defined radio resource control message, or may be an existing radio resource control message.
  • an RRC message may be newly defined as an S1AP_UE_Specific RRC message, and the RRC message includes a terminal-related and delay-sensitive S1 message, and then the message is mapped to a high priority.
  • SRB as in SRB 1
  • the RRC message will get a high priority scheduling.
  • the receiver can immediately know that the content included in the RRC message is an S1 message, and then the content included in the RRC message is put into the S1 protocol stack for processing. Whether IE or IE container is required in the RRC message is not limited.
  • the S1 message is included in the IE container or the IE, and may be: multiple S1 messages of the same priority of a single UE, or multiple S1 messages of a certain priority of a single UE, or equal priority of multiple UEs.
  • An IE may include a list of S1 messages, the bread containing the S1 message index Index, or the identifier of the terminal, and the number of S1 messages of each UE, and the like.
  • the SRB priority corresponding to the RRC message can be dynamically configured. Dynamic configuration means that, in some cases, a higher priority RRC message or an RRC message containing a high priority S 1/X2 message is mapped to a high priority SRB (such as SRB 1 ). The lower priority RRC message or the RRC message containing the lower priority S1/X2 message is mapped into the lower priority SRB (such as SRB2). Manner 1: Dynamically map different RRC messages to SRBs with different priorities.
  • the S1 message is divided into three priorities, which are respectively carried in three different newly defined RRC messages, such as RRC_S1AP1, RRC_S1AP2, and RRC_S1AP3 messages.
  • RRC_S1AP1 is mapped to SRB1
  • RRC_S1AP2 and RRC_S1AP3 are mapped to the transmission on SRB2.
  • the three types of RRC messages and SRBs can be dynamically configured.
  • RRC_S1AP2 is mapped to SRB1 for transmission, and other configurations are unchanged.
  • the foregoing situation can also be implemented by using an existing RRC message, and the S1 message is carried by the existing RRC message, and each type of priority S1 message is carried in an existing RRC message. No repeated description is given here.
  • the system may configure an identifier for the RRC message to indicate whether the RRC message is dynamically configured into SRB1 or SRB2.
  • the system may establish two RRC message priority sets, the RRC message in the high priority set may be mapped to the high priority SRB (such as SRB1), and the RRC message of the low priority set may be mapped to the low priority SRB ( As in SRB2), as long as the RRC message is dynamically placed in one of the sets, the purpose of dynamic configuration can be achieved.
  • the S1 message is learned to be high-priority or low-priority, or the S1 message is carried to the matched IE or IE Container by using the indicated priority information. , by placing it in a matching RRC message, mapping to a high priority or ⁇ priority SRB.
  • the S1 messages of different priorities are dynamically carried in different RRC messages, and the S1 messages of different priorities are dynamically mapped to the SRBs with different priorities by different RRC messages and different SRB static mapping relationships.
  • the three types of S1 messages are respectively carried in three IEs, namely, SlAP_Dedicated_first IE, S1 AP_Dedicated_second IE, and S1 AP_Dedicated_third IE. When the system is configured by default or the first time, the SlAP_Dedicated_first IE is placed in the RRC1 message, and the RRC1 message is mapped.
  • the S1AP_Dedicated_second IE, the SlAP_Dedicated_third IE are placed in the RRC2 message, or the corresponding SI messages of the two IEs are placed in one IE of the RRC2, and the RRC2 message is mapped into the SRB2.
  • the RRC1 message is mapped into SRB 1
  • the RRC2 message is mapped to SRB2 unchanged.
  • the mapping between the three IEs and the SRB may be dynamically configured, such as including the S lAP_Dedicated_first IE and the S 1 AP_Dedicated_second IE in the RRC1 message, or including the SI in the two IEs by using one IE in the RRC1 message.
  • the RRC2 message contains only the SlAP_Dedicated_third IE.
  • the RRC message required by the relay for its own service is more important, and needs to be mapped to the transmission in SRB 1.
  • Other RRC messages should be mapped to the transmission on SRB2, and in the process of mobile relay handover, the Un interface transmits The related RRC message transmission is more important than other messages.
  • the RRC message related to the mobile relay handover (such as the handover indication message, the RRC reconfiguration message, and the handover to the new cell, the relay and the target base station perform the S1 or X2 interface.
  • Established messages, etc. should be mapped to high priority SRBs (such as SRB 1) for transmission, while other RRC messages (such as RRC messages carrying S 1/X2 messages under mobile relay services) should be mapped to low Priority in SRB (such as SRB2).
  • the processing of the S1 message is similar to the processing of the S1 message.
  • the S1 message may be classified into the following three categories: a terminal-related and delay-sensitive message, a terminal-related and delay-insensitive message, and a message not related to the terminal, respectively named For S1A class, S 1B class, S 1C class message.
  • the S1 message can also be divided into: a message related to the terminal, a message that is not related to the terminal and is sensitive to the delay, and a message that is not related to the terminal and is not sensitive to the delay, and can also be used by those skilled in the art according to actual needs.
  • the three types of messages have different priorities, they are placed in RRC messages and mapped to different types of SRBs (such as SRB 1 and SRB2).
  • SRB 1 and SRB2 Different types of classification of related messages are performed differently, which does not affect the implementation of the embodiment.
  • the three types of messages have different priorities, they are placed in RRC messages and mapped to different types of SRBs (such as SRB 1 and SRB2).
  • SRB 1 and SRB2 Specifically, in the type 3 message, if the S1A type message needs to be processed preferentially, that is, its priority is the highest, it can be put into an existing RRC message, such as an RRC X message, the RRC.
  • the X message is mapped onto SRB 1, so the S1 Class A message is actually mapped onto SRB 1 for transmission.
  • a dedicated IE or IE Container may be added to the RRC message containing the S1A class message, and the IE or IE Container is used to indicate what message the message is.
  • an IE may be added to the RRC message that includes the S1A type message, and the IE name is S1AP_Dedicated_first. Then, when the RRC layer reads the IE in the RRC message, it knows that the RRC message includes the S1 message, and needs to be Priority is scheduled.
  • the S1A type message may be placed in an RRC message or may be transmitted in multiple RRC messages.
  • the RRC message may be an RRC message in the prior art, and may also be a newly defined RRC message.
  • the S1 messages of different priorities can be placed in the same RRC message or multiple RRC messages as long as they need to be mapped to one SRB. If different priority S1 messages need to be mapped to different SRBs, they need to be placed in different RRC messages.
  • S1 and X2 messages with the same priority, or S1 messages and X2 messages to be mapped to the same SRB may be placed in the same RRC message, or may be placed in different RRC messages. If the S1 and X2 messages are placed in an RRC message, then the S1 message and X2 need to be placed in different IE or IE containers of the message, respectively.
  • an S1B type message or an S1C type message may also be carried in an existing RRC message, such as an RRC Y message.
  • the RRC Y message may be mapped to the SRB2, and the S1B or S1C type message may be mapped to the SRB2 transmission, or a dedicated IE or IE Container may be added to the RRC message including the S1B or S1C type message.
  • a dedicated IE or IE Container may be added to the RRC message including the S1B or S1C type message.
  • an IE may be added to the RRC message including the S1B or S1C type message, and the IE name is S 1 AP_Dedicated_second.
  • the mapped data is transmitted to the receiving end, and the RRC layer of the receiving end reads the RRC message received by the receiving end, and the content of the IE or IE Container included in the RRC message can be used to know that the RRC message specifically includes the S1 message or the X2 message. And their priorities.
  • the S1 or X2 message carried in the message may be placed in the SI AP (SI Application Protocol) layer or the X2AP (X2 Application Protocol). X2 Application Protocol) layer processing.
  • the scheduling priority of the message including the IE is lower; if the IE content read by the RRC layer is the message of SlAP_Dedicated_first, the scheduling priority of the message including the IE is higher.
  • a person skilled in the art can understand that a plurality of S1 messages or X2 messages can be included in one RRC message, and another method can process multiple S1 messages or X2 messages in multiple RRC messages.
  • the scheduling priority of SRB2 is lower than SRB1, so the processing priority of S1B type messages or S1C type messages will be lower than that of S1A type messages.
  • the above process classifies SI Class A messages as high priority; and class S1B and Class C messages as low priority.
  • the S1A class and the B class message may be classified as high priority, that is, the message corresponding to the IE Container is SlAP_Dedicated_first, and the SIC class message has a low priority, corresponding to SlAP_Dedicated_second.
  • a processing method similar to the SI message can be used, so that the A and B messages of the X2 message correspond to the X2AP_Dedicated_first, and the C message of the X2 message corresponds to the X2AP_Dedicated_second.
  • the three types of S1 messages are classified into two types of priorities, which are carried in different RRC messages. It can be understood that there are only two types of RRC messages, but N types, each type of RRC message and one priority.
  • the S1 message corresponds to; the N priority S1 messages can be mapped on N kinds of RRC messages, respectively.
  • the RRC message in the previous embodiment is classified into the RRC X message and the RRC Y message.
  • a new RRC message can be generated according to the requirement to carry the S1 message.
  • three types of RRC messages which are RRC A, RRC B, and RRC C messages, can be generated to implement three different priority SI messages, which can be mapped on the corresponding priority SRB. Scheduling processing with different priorities.
  • FIG. 3 is a schematic diagram of an SRB mapping process according to an embodiment of the present invention.
  • the S1 message is divided into two priorities, which are respectively carried in an RRC message (the RRC message may be two or more RRC messages), and will be included.
  • the RRC message of the high priority S1 message is mapped on SRB1 (such as the SRB with logical channel priority 1), and the lower priority mapping is in SRB2 (such as logic On the SRB with a channel priority of 3, each SRB is mapped on its corresponding logical channel, and the corresponding logical channels of the two SRBs are represented by logical channels 1 and 3, respectively.
  • SRB1 such as the SRB with logical channel priority 1
  • SRB2 such as logic On the SRB with a channel priority of 3
  • each SRB is mapped on its corresponding logical channel
  • the corresponding logical channels of the two SRBs are represented by logical channels 1 and 3, respectively.
  • one SRB carrying an S1/X2 message may correspond to a plurality of different logical channels, and the different logical channels have different priorities.
  • FIG. 4 is a schematic diagram of another SRB mapping process according to an embodiment of the present invention. The difference from FIG. 3 is that each SRB of FIG. 4 can configure multiple logical channels of different priorities.
  • SRB1 (such as SRB with priority 1) can correspond to logical channel with priority 1 and logical channel with priority 2), priority 1 is greater than priority 2; SRB2 (priority ratio SRB1) A low SRB) corresponds to a logical channel with a priority of 3.
  • SRB2 can also configure logical channels of different priorities, and transmit S1 messages of different priorities through logical channels of different priorities, which is not deployed in this embodiment.
  • FIG. 5 is a schematic diagram of another SRB mapping process according to an embodiment of the present invention. In this mapping process, the S1 message is divided into three different priorities, which are respectively carried in the three types of SRBs, and then mapped to three logical channels.
  • SRB2 and SRB3 are mapped on logical channels 2 and 3, respectively.
  • Different types of S1 messages can be carried in SRB2 and SRB3, SRB2 is mapped to logical channel 3, and SRB3 is mapped to logical channel 2 or 4. This embodiment does not limit this.
  • the S1A type message may be classified into UE-related and delay-sensitive, non-related to the UE, and sensitive to delay, and the two sub-class S1 messages are respectively placed in the SI AP_RRC1.
  • both RRC messages are mapped into SRB1, and an identifier may be included in the S1AP_RRC2 message, indicating that it needs to be mapped to a logical channel with a logical channel priority of 2.
  • an identifier may be set in the logical channel configuration parameter in the S1AP_RRC2 message, indicating that it needs to be mapped to a logical channel with a logical channel priority of 2.
  • the S1 or X2 message may further include a NAS message of the UE, and the Uu interface between the UE and the RN is similar to the interface between the UE and the eNB in the prior art, and the RN may carry the NAS message of the UE by S1/ In the X2 message, the S1/X2 message is transmitted to the base station.
  • the base station can also have similar operations.
  • the NAS message 7 of the UE is transmitted to the RN in the S1/X2 message.
  • how the S1/X2 message is carried in the RRC message is transmitted in the previous embodiment.
  • the S1 message containing the UE NAS message may be a terminal related message or the like.
  • the S1/X2 message including the UE NAS message may be separately classified as one type, and may be mapped to SRB1 or SRB2 or an SRB3 (the priority of the SRB is 2, or 4). The example is not limited.
  • the involved messages such as RRC messages
  • RRC messages such as handover requests, handover replies/acknowledgement messages, etc.
  • the signaling priority is high. Therefore, such RRC messages can be set to have a higher priority than RRC messages containing other S1 and X2 messages.
  • the RRC message involved in the RN handover process is mapped to SRB1, and other RRC messages including the S1 and X2 messages are mapped to SRB (s) having a lower priority than SRB1, such as SRB2 or multiple different priorities.
  • Level SRBs (such as SRB2, SRB3, SRBn, etc., can specifically put different priority S1/X2 messages in different priority SRBs).
  • SRB can correspond to different priority logical channels
  • the RRC message involved in the RN handover process is mapped into SRB1, and if the SRB can be mapped to logical channels of different priorities, then the RN handover process is involved.
  • the RRC message is mapped to a high priority logical channel corresponding to SRB1, such as a logical channel with a priority of 1, to ensure that such messages are processed first.
  • the S1 message corresponding to the non-terminal related service/service may be: a reset message RESET message or a reset confirmation message RESET ACK message in the reset procedure, the error indication process (The Error indication message ERROR INDICATION message, SI setup request message SI SETUP REQUEST message or SI setup reply message SI SETUP RESPONSE message, Overload Start procedure message, overload stop procedure Overload stop message in the Overload Stop procedure OVERLOAD STOP message, Base station direct information transmission process eNB Direct Information Transfer procedure MME Direct Information TRANSFER message in the MME Direct Information Transfer procedure, MME DIRECT INFORMATION TRANSFER message in the MME Direct Information Transfer procedure, Base Station Configuration Transfer Message ENB in the eNB Configuration Transfer procedure CONFIGURATION TRANSFER message, MME configures the MME configuration transport message MME CONFIGURATION TRANSFER message in the MME Configuration Transfer procedure.
  • the error indication process The Error indication message ERROR INDICATION message, SI setup request message SI SETUP REQUEST message or SI setup reply message
  • the S1 terminal related message can be:
  • E-RAB SETUP REQUEST message or E-RAB SETUP RESPONSE message in the E-RAB Setup procedure E-RAB MODIFY REQUEST message or E-RAB MODIFY RESPONSE message
  • E-RAB Release procedure E-RAB RELEASE COMMAND message or E-RAB RELEASE RESPONSE message
  • Initial Context Setup procedure flow INITIAL CONTEXT SETUP REQUEST message or INITIAL CONTEXT SETUP RESPONSE message
  • UE Context Release Request procedure flow UE CONTEXT RELEASE REQUEST message
  • Handover HANDOVER CANCEL message or HANDOVER CANCEL ACKNOWLEDGE message in the Cancel procedure flow UE Context Release Request procedure flow
  • the X2AP Basic Mobility Procedures are all related to a single terminal.
  • the X2 message in the corresponding process is a terminal-related message, which can be:
  • HANDOVER REQUEST message or HANDOVER REQUEST ACKNOWLEDGE message or HANDOVER PREPARATION FAILURE message in the Handover Preparation process SN STATUS TRANSFER message in the SN Status Transfer procedure flow, UE CONTEXT RELEASE message in the UE Context Release procedure flow, Handover Cancel procedure flow HANDOVER CANCEL message, etc.
  • X2 Global Procedures does not involve a single terminal.
  • the corresponding X2 message is a non-terminal related message. Specifically, it can be:
  • LOAD INFORMATION message in the Load Indication procedure ERROR INDICATION message in the Error Indication procedure, X2 SETUP REQUEST message or X2 SETUP RESPONSE message in the X2 Setup procedure, RESET REQUEST message in the Reset procedure flow or RESET RESPONSE message, ENB CONFIGURATION UPDATE message or ENB CONFIGURATION UPDATE ACK message or ENB CONFIGURATION UPDATE FAILURE message in the eNB Configuration Update procedure flow, RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message in the Resource Status Reporting procedure flow, RESOURCE STATUS UPDATE message, etc.
  • the message used in the handover preparation process is a delay-sensitive X2 message
  • the load indication message is a delay-insensitive X2 message, etc., and is not classed here.
  • FIG. 6 is a schematic diagram of a LTE-A message processing device according to an embodiment of the present disclosure, where the device includes:
  • a priority determining unit 61 configured to acquire an S1 message or an X2 message, and determine a priority of the S1 message or the X2 message;
  • a bearer unit 62 configured to carry the S1 message or the X2 message in a radio resource control message
  • the first mapping unit 63 is configured to map the radio resource control message to a signaling radio bearer corresponding to the priority in.
  • the S1 message or the X2 message of different priorities are mapped in different signaling radio bearers, so that the S1 message or the X2 message with higher priority can be mapped to the high priority.
  • Level signaling radio bearers, and get priority scheduling, can increase the message Rational flexibility.
  • the mapping unit 63 may include: a first mapping module, configured to: when the priority of the S1 message or the X2 message is a high priority, map the RRC message to the first of the high priority Transmitting in the signaling radio bearer; the second mapping module is configured to: when the priority of the S1 message or the X2 message is a low priority, map the radio resource control message to the second signaling radio bearer of the low priority In transit.
  • the device may further include: a second mapping unit, configured to determine a sub-priority of the S1 message or the X2 message, and map the signaling radio bearer to a logical channel corresponding to the sub-priority.
  • the device may further include: an information acquiring unit, configured to acquire the RRC message from the bearer unit 62, and read the indication information unit in the RRC message to obtain the RRC message
  • an information acquiring unit configured to acquire the RRC message from the bearer unit 62, and read the indication information unit in the RRC message to obtain the RRC message
  • the type and priority of the S1 message or the X2 message included in the first mapping unit 63 is notified of the type and priority of the S1 message or the X2 message.
  • the device may be a base station (including various types of base stations such as a NodeB or an eNodeB) or a relay node.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Abstract

L'invention porte sur un procédé et un dispositif de traitement de message pour architecture d'évolution à long terme améliorée (LTE-A), le procédé comprenant les étapes suivantes : obtention d'un message S1 ou d'un message X2, et détermination de la priorité du message S1 ou du message X2; inclusion du message S1 ou du message X2 dans un message de gestion des ressources radio; mappage du message de gestion des ressources radio au support radio de signalisation correspondant à la priorité. A l'aide du procédé, la flexibilité de traitement de message peut être améliorée.
PCT/CN2009/074836 2009-11-11 2009-11-11 Procédé et dispositif de traitement de message pour architecture lte-a WO2011057438A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2009801464566A CN102227924A (zh) 2009-11-11 2009-11-11 一种lte-a的消息处理方法和设备
PCT/CN2009/074836 WO2011057438A1 (fr) 2009-11-11 2009-11-11 Procédé et dispositif de traitement de message pour architecture lte-a

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/074836 WO2011057438A1 (fr) 2009-11-11 2009-11-11 Procédé et dispositif de traitement de message pour architecture lte-a

Publications (1)

Publication Number Publication Date
WO2011057438A1 true WO2011057438A1 (fr) 2011-05-19

Family

ID=43991160

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/074836 WO2011057438A1 (fr) 2009-11-11 2009-11-11 Procédé et dispositif de traitement de message pour architecture lte-a

Country Status (2)

Country Link
CN (1) CN102227924A (fr)
WO (1) WO2011057438A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1863383A (zh) * 2005-09-29 2006-11-15 华为技术有限公司 通信系统中的无线资源控制消息的发送方法
WO2008078907A1 (fr) * 2006-12-22 2008-07-03 Samsung Electronics Co., Ltd. Procédé de planification de liaison montante basée sur des coupons et sélection de combinaison de format de transport
US20080212528A1 (en) * 2005-07-21 2008-09-04 Telefonaktiebolaget Lm Ericsson (Publ) Srb Enhancement on Hs-Dsch During Cell Change
CN101379866A (zh) * 2006-02-08 2009-03-04 日本电气株式会社 用于e-utra无线电资源控制的改进连接建立

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080212528A1 (en) * 2005-07-21 2008-09-04 Telefonaktiebolaget Lm Ericsson (Publ) Srb Enhancement on Hs-Dsch During Cell Change
CN1863383A (zh) * 2005-09-29 2006-11-15 华为技术有限公司 通信系统中的无线资源控制消息的发送方法
CN101379866A (zh) * 2006-02-08 2009-03-04 日本电气株式会社 用于e-utra无线电资源控制的改进连接建立
WO2008078907A1 (fr) * 2006-12-22 2008-07-03 Samsung Electronics Co., Ltd. Procédé de planification de liaison montante basée sur des coupons et sélection de combinaison de format de transport

Also Published As

Publication number Publication date
CN102227924A (zh) 2011-10-26

Similar Documents

Publication Publication Date Title
TWI601435B (zh) 處理同時通訊的方法及其通訊裝置
JP6416097B2 (ja) 複数の接続を確立するためのデバイス
US20190342148A1 (en) Method for configuring dual-connectivity by terminal, and apparatus therefor
KR101982432B1 (ko) 스몰 셀 네트워크에서의 버퍼 상태 보고
JP6387396B2 (ja) セカンダリ基地局、移動通信システム及び通信制御方法
JP6282705B2 (ja) ユーザ端末、プロセッサ及び通信制御方法
RU2656339C2 (ru) Способ конфигурации радионосителя, базовая станция и система
JP2017500794A (ja) マルチ接続性オペレーションのためのシステムおよび方法
US10425881B2 (en) User terminal, network apparatus, and processor
KR20100138759A (ko) 무선 통신 시스템에서 ｒｂ 설정 방법 및 장치
JP6829208B2 (ja) 無線端末及び基地局
US10674500B2 (en) Communication method, device, and system
EP2768267A1 (fr) Unités et procédés de communication pour communication de liaison montante par un service de relais
JP7413507B2 (ja) 通信制御方法
US20180255610A1 (en) Radio terminal, processor, and network device
WO2011057438A1 (fr) Procédé et dispositif de traitement de message pour architecture lte-a
WO2024019061A1 (fr) Dispositif et procédé de communication, et station de base
WO2024019060A1 (fr) Dispositif de communication et procédé de communication
WO2024019058A1 (fr) Dispositif de communication, station de base et procédé de communication
WO2024034475A1 (fr) Dispositif et procédé de communication, et station de base
JP7419562B2 (ja) 通信制御方法
EP4329339A1 (fr) Équipement utilisateur et procédé de commande de communication
WO2023171211A1 (fr) Terminal sans fil et procédé associé

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980146456.6

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09851194

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

Country of ref document: EP

Kind code of ref document: A1