WO2015062287A1 - Procédé et système d'échange local de terminal - Google Patents

Procédé et système d'échange local de terminal Download PDF

Info

Publication number
WO2015062287A1
WO2015062287A1 PCT/CN2014/080344 CN2014080344W WO2015062287A1 WO 2015062287 A1 WO2015062287 A1 WO 2015062287A1 CN 2014080344 W CN2014080344 W CN 2014080344W WO 2015062287 A1 WO2015062287 A1 WO 2015062287A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
enb
message
local
rrc connection
Prior art date
Application number
PCT/CN2014/080344
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 中兴通讯股份有限公司
Publication of WO2015062287A1 publication Critical patent/WO2015062287A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup

Definitions

  • the present invention relates to the field of communications, and in particular to a local switching method and system for a terminal.
  • BACKGROUND OF THE INVENTION With the development of wireless multimedia services, the demand for high data rates and user experiences is increasing, and higher requirements are placed on the system capacity and coverage of traditional cellular networks. Moreover, the popularity of applications such as social networking, near-field data sharing, and local advertising has led to an increasing demand for PS (Proximity Services) that understands and communicates with people or things of interest nearby.
  • PS Proximity Services
  • the traditional base station-centric cellular network has obvious limitations in supporting high data rates and proximity services.
  • D2D Device-to-Device, device to the new direction of future communication technology development
  • Equipment came into being.
  • the application of D2D technology can reduce the burden on the cellular network, reduce the battery power consumption of the user equipment, increase the data rate, and improve the robustness of the network infrastructure, which satisfies the requirements of the above high data rate services and proximity services.
  • the local switching technology belongs to a branch of the D2D technology.
  • the two terminals communicate, the user data does not need to go through the complete core network process, but the base station directly forwards the user data.
  • the two terminals performing the local exchange may perform data forwarding by the base station under the coverage of the same base station, or may be jointly performed by the two base stations under the coverage of two adjacent base stations.
  • LTE Long Term Evolution
  • SGW Serving Gateway
  • P PGW Packet Data
  • SGW Serving Gateway
  • P PGW Packet Data Gateway
  • This data exchange method increases the load on the SGW and the PGW gateway and the transmission network.
  • the data needs to undergo complicated processing at the base station, and the delay of the user data transmission is large, and the transmission speed is affected.
  • the method of data forwarding by the LTE technology in the related art increases the load of the network equipment of the core network and the transmission delay of the user data.
  • no effective solution has been proposed.
  • a method for local switching of a terminal including: the evolved base station e B cooperates with the first terminal and the second terminal to establish a local bearer, where the local bearer refers to a dedicated need to be used in the local exchange process.
  • the bearer of the device to the device D2D; the eNB forwards the service data between the first terminal and the second terminal through the local bearer to implement local exchange.
  • the evolved base station eNB cooperates with the first terminal and the second terminal to establish a local bearer, including: after the packet data gateway PGW initiates a local bearer setup procedure, the eNB initiates a first radio resource control RRC to the first terminal and the second terminal respectively.
  • the connection reconfiguration process the second radio resource control RRC connection reconfiguration procedure; in the case that both the first RRC connection reconfiguration and the second RRC connection reconfiguration are successful, the eNB determines that the establishment of the local bearer has been completed, otherwise, according to the first
  • the establishment failure message fed back by the terminal and/or the second terminal re-initiates the RRC connection reconfiguration process to the first terminal and/or the second terminal until the establishment of the local bearer is completed.
  • the packet data gateway PGW initiates a local bearer setup procedure, including: after receiving the local bearer setup request message sent by the first terminal, the PGW generates a first transport stream template TFT for the first terminal, and adds a local to the first TFT.
  • the exchanged address type and the IP address of the second terminal where the local bearer setup request message includes: an IP address of the first terminal and an IP address of the second terminal; and the PGW generates a second second terminal according to the IP address of the second terminal a TFT, and adding a locally exchanged address type and an IP address of the first terminal in the second TFT; the PGW generates a first local bearer setup message, where the first local bearer setup message is a message from the PGW to the mobility management entity MME,
  • the local bearer setup message includes: an IP address of the first terminal, a local switching TFT pair composed of the first TFT and the second TFT, and a quality of service QoS parameter;
  • the PGW sends a first local bearer setup message to the MME through the serving gateway SGW, Generating, by the MME, a second local bearer setup message according to the first local bearer setup message, where
  • the local bearer setup message is a message from the MME to the eNB, and the second local bear
  • the eNB initiates a first radio resource control RRC connection reconfiguration procedure and a second radio resource control RRC connection reconfiguration procedure to the first terminal and the second terminal, respectively, including: the eNB initiating the first radio resource control RRC to the first terminal
  • the connection reconfiguration process includes: the eNB generates a first data radio bearer DRB of the first terminal to the eNB according to the first E-RAB ID, and generates a first DRB ID, a first logical channel, and the first corresponding to the first DRB.
  • An LC ID where the reserved value of the first LC ID is used to identify the first logical channel in the process of performing local switching; the eNB generates a first RRC connection reconfiguration message corresponding to the first terminal, where the first RRC connection is heavy
  • the configuration message includes: a first DRB ID, a first LC ID, and a first NAS message corresponding to the first terminal, where the first NAS message carries the first TFT; the eNB sends a first RRC connection reconfiguration message to the first terminal, and initiates The first RRC connection reconfiguration process; And the eNB sends a second radio resource control RRC connection reconfiguration procedure to the second terminal, where: the eNB generates a second data radio bearer DRB of the second terminal to the eNB according to the second E-RAB ID, and generates a second DRB corresponding to the second DRB.
  • the eNB generates a second RRC corresponding to the second terminal
  • the second RRC connection reconfiguration message includes: a second DRB ID, a second LC ID, and a second NAS message corresponding to the second terminal, where the second NAS message carries the second TFT;
  • the second terminal sends a second RRC connection reconfiguration message, and initiates a second RRC connection reconfiguration process.
  • the first DRB and the second DRB have a fixed binding relationship, and the first DRB ID and the second DRB ID are fixedly bound.
  • the method includes: the first terminal binding the first TFT to the first terminal The first DRB, and performing other operations of the first RRC connection reconfiguration; the second terminal binding the second TFT to the second DRB, and performing other operations of the second RRC connection reconfiguration.
  • the method includes: the first terminal sends a first RRC connection reconfiguration complete message to the eNB; and the second terminal sends the second RRC connection to the eNB.
  • Rematch complete message when the eNB receives the first RRC connection reconfiguration complete message and the second RRC connection reconfiguration complete message, the method includes: the eNB sends a first RRC configuration end message to the first terminal, and sends a second message to the second terminal. RRC configuration end message.
  • the eNB forwards the service data between the first terminal and the second terminal by using the local bearer to implement the local exchange, including: after receiving the call request SR signaling sent by the first terminal, the eNB sends the UL grant message to the first terminal.
  • the UL grant signaling carries the uplink resource used when the first terminal sends the service data; the eNB receives the service data from the first terminal through the air interface, and processes the service data by the PHY layer, the MAC layer, and the RLC layer, The service data is sent to the PDCP layer; the eNB allocates a buffer for using the second terminal to receive the service data; and the eNB sends the service data to the second terminal by using the cache.
  • the eNB sends the service data to the second terminal by using the buffer, in one of the following manners: In the first mode, after the eNB service data is placed in the PDCP layer, the eNB is sent to the second terminal by using the buffer; After being above the PDCP layer, it will be sent to the second terminal through the cache;
  • the method of performing encryption on the service data when the data is sent by using the mode 1 includes: when the uplink data packet count value of the first data radio bearer DRB of the first terminal to the eNB reaches a first counting threshold, the eNB sends the first terminal to the first terminal.
  • the method further includes: the eNB or the packet data gateway PGW determining whether local switching is possible.
  • the eNB determines whether the local exchange is possible, the method includes: in the process of attaching by the first terminal, the eNB receives the IP address of the first terminal sent by the mobility management entity MME, and saves the IP address of the first terminal; During the process of attaching the terminal, the eNB receives the IP address of the second terminal sent by the MME, and saves the IP address of the second terminal; when receiving the local exchange request message that is sent by the first terminal and carries the IP address of the second terminal, The eNB determines whether the IP address of the second terminal has been saved locally. If the determination result is yes, it is determined that the first terminal and the second terminal can perform local exchange; if the determination result is negative, the eNB approaches the neighbor.
  • the eNB queries whether the neighboring eNB has saved the IP address of the second terminal. If the query result is yes, it is determined that the first terminal and the second terminal can perform local exchange. If the query result is no, the first terminal and the second terminal cannot be determined. Perform local exchange.
  • the method includes: the eNB sends a local exchange request response message to the first terminal, where the local exchange request response message is used to indicate that the first terminal can The two terminals perform local exchange and initiate the establishment process of the local bearer.
  • the PGW determines whether the local terminal can be exchanged, the method includes: after the first terminal succeeds and the second terminal successfully attaches, the PGW establishes an LTE bearer between the first terminal and the second terminal; and the PGW receives the service sent by the first terminal.
  • Data where the service data includes: an IP address of the first terminal and an IP address of the second terminal; and the PGW determines, according to the IP address of the first terminal and the IP address of the second terminal, whether the first terminal and the second terminal are located.
  • the eNB and the eNB support the local switching function, or whether the first terminal and the second terminal are respectively located under the eNB and the neighboring eNB, and the eNB and the neighboring eNB support the local switching function.
  • a local switching system of a terminal including: an evolved base station e B, a first terminal, a second terminal, a packet data gateway PGW, a serving gateway SGW, and a mobility management entity MME, where
  • the eNB includes: an establishing module, configured to establish a local bearer in cooperation with the first terminal and the second terminal, where The local bearer refers to a bearer dedicated to the device to the device D2D that needs to be used in the local switching process.
  • the forwarding module is configured to forward the service data between the first terminal and the second terminal through the local bearer to implement local exchange.
  • the establishing module includes: an initiating module, configured to: after the PGW initiates the local bearer setup process, initiate a first radio resource control RRC connection reconfiguration process to the first terminal and the second terminal, and the second radio resource control RRC connection weight a processing module, configured to determine that the establishment of the local bearer has been completed if the first RRC connection reconfiguration and the second RRC connection reconfiguration are successful, otherwise, according to the feedback of the first terminal and/or the second terminal A failure message is established, and the RRC connection reconfiguration process is re-initiated to the first terminal and/or the second terminal until the establishment of the local bearer is completed.
  • the PGW is configured to initiate a local bearer setup process
  • the PGW includes: a first receiving module, configured to receive a local bearer setup request message sent by the first terminal; and a first generating module, configured to generate a first transport stream for the first terminal a template TFT, and adding a locally exchanged address type and an IP address of the second terminal in the first TFT, where the local bearer setup request message includes: an IP address of the first terminal and an IP address of the second terminal; And generating, according to the IP address of the second terminal, a second TFT for the second terminal, and adding a locally exchanged address type and an IP address of the first terminal in the second TFT; and a third generation module, configured to generate the first local a bearer setup message, where the first local bearer setup message is a message from the PGW to the MME, and the local bearer setup message includes: an IP address of the first terminal, a local exchange TFT pair composed of the first TFT and the second TFT, and a service a quality Q
  • the initiating module includes: a first generating unit, configured to generate a first data radio bearer DRB of the first terminal to the eNB according to the first E-RAB ID, and generate a first DRB ID corresponding to the first DRB, first a logical channel, and a first LC ID, where the reserved value of the first LC ID is used to identify the first logical channel in a process of performing local switching; and the second generating unit is configured to generate a first RRC corresponding to the first terminal a first RRC connection reconfiguration message, where the first RRC connection reconfiguration message includes: a first DRB ID, a first LC ID, and a first NAS message corresponding to the first terminal, where the first NAS message carries the first TFT; a unit, configured to send a first RRC connection reconfiguration message to the first terminal, to initiate a first RRC connection reconfiguration process, and a third generating unit, configured to generate second data from the second terminal to the eNB according to the second E-RAB ID Radio
  • the first terminal includes: a first binding module, configured to bind the first TFT to the first DRB and perform the first RRC connection after the initiating module initiates the first RRC connection reconfiguration process to the first terminal
  • the second terminal includes: a second binding module, configured to bind the second TFT to the second DRB after the initiating module initiates the second RRC connection reconfiguration process to the second terminal, and perform the Two other operations of RRC connection reconfiguration.
  • the first terminal further includes: a second sending module, configured to: when the first RRC connection reconfiguration succeeds, send a first RRC connection reconfiguration complete message to the e B; the second terminal further includes: the third sending And a module, configured to send a second RRC connection reconfiguration complete message to the eNB if the second RRC connection reconfiguration succeeds.
  • the establishing module further includes: a fourth sending module, configured to send the first RRC configuration end message to the first terminal, when the first RRC connection reconfiguration complete message and the second RRC connection reconfiguration complete message are received Sending a second RRC configuration end message to the second terminal.
  • the forwarding module includes: a second receiving module, configured to receive the call request SR signaling sent by the first terminal; and a fifth sending module, configured to send the UL grant signaling to the first terminal, where the UL grant signaling is Carrying the uplink resource used when the first terminal sends the service data;
  • the third receiving module is configured to receive the service data from the first terminal by using the air interface, and perform processing on the PHY layer, the MAC layer, and the RLC layer of the service data to enable the service data Arriving at the PDCP layer; an allocation module, configured to allocate a buffer for use in receiving the service data to the second terminal; and a sixth sending module, configured to send the service data to the second terminal by using the cache.
  • the sixth sending module sends the service data to the second terminal by using a buffer, in one of the following manners: mode 1, the sixth sending module sends the service data to the PDCP layer, and then sends the data to the second terminal by using the buffer; After the service module is placed on the PDCP layer, the sixth sending module sends the data to the second terminal by using the cache.
  • the data is sent by the sixth sending module to encrypt the service data, including: When the uplink data packet count value of the first data radio bearer DRB of the first terminal to the eNB reaches the first counting threshold, the sixth sending module sends a first Countercheck message to the first terminal to make the first terminal according to the LTE. The process performs a check on the service data.
  • the sixth sending module sends a second Countercheck message to the second terminal.
  • the second terminal performs counting check on the service data according to the LTE process.
  • the e B further includes: a first determining module, configured to determine whether the local exchange can be performed before the establishing module establishes the local bearer; or the PGW further includes: a second determining module, configured to: before the establishing module establishes the local bearer , to determine whether local exchange is possible.
  • the first determining module includes: a first receiving unit, configured to receive an IP address of the first terminal sent by the MME and save the IP address of the first terminal in the process of attaching the first terminal; In the process of attaching the second terminal, receiving the IP address of the second terminal sent by the MME, and saving the IP address of the second terminal; the first determining unit is configured to receive when the first terminal sends the When the local exchange request message of the IP address of the second terminal is used, it is determined whether the IP address of the second terminal has been saved locally; the first determining unit is configured to determine the first terminal and the second terminal if the determination result is yes The local exchange can be performed; the query unit is configured to, if the judgment result is negative, query the neighboring eNB whether the neighboring eNB has saved the IP address of the second terminal; the second determining unit is set to be when the query result is Determining that the first terminal and the second terminal can perform local exchange, and when the query result is no, determining the first terminal and the first Terminal can be locally switched.
  • the eNB further includes: a seventh sending module, configured to send a local exchange request response message to the first terminal, where the first determining module determines that the first terminal and the second terminal can perform local exchange, where the local exchange The request response message is used to indicate that the first terminal can perform local exchange with the second terminal, and initiates a setup process of the local bearer.
  • a seventh sending module configured to send a local exchange request response message to the first terminal, where the first determining module determines that the first terminal and the second terminal can perform local exchange, where the local exchange The request response message is used to indicate that the first terminal can perform local exchange with the second terminal, and initiates a setup process of the local bearer.
  • the second determining module includes: an establishing unit, configured to: after the first terminal succeeds and the second terminal successfully attaches, establish an LTE bearer between the first terminal and the second terminal; and the third receiving unit is configured to receive The service data sent by the first terminal, where the service data includes: an IP address of the first terminal and an IP address of the second terminal; and a second determining unit, configured to be based on the IP address of the first terminal and the IP address of the second terminal Determining whether the first terminal and the second terminal are both located under the eNB and the eNB supports the local switching function, or whether the first terminal and the second terminal are respectively located under the eNB and the neighboring eNB, and the eNB and the neighboring eNB support the local switching function, If the determination result is yes, it is determined that the first terminal and the second terminal can perform local exchange, and if the determination result is no, it is determined that the first terminal and the second terminal cannot perform local exchange.
  • the eNB when the eNB or the PGW determines that the first terminal and the second terminal are capable of local switching, the eNB may establish a local device in cooperation with the first terminal and the second terminal of the eNB or one of the neighboring eNBs. Carrying, and then forwarding the service data between the first terminal and the second terminal by using the local bearer.
  • the method solves the problem that the data forwarding by the LTE technology in the related art increases the load of the network equipment of the core network and the transmission delay of the user data, thereby reducing the load of the network equipment of the core network and shortening the data transmission. Delay, the effect of increasing the speed of data transmission.
  • FIG. 1 is a flow chart of a local switching method of a terminal according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a local switching system of a terminal according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a local switching system of a terminal according to an embodiment of the present invention
  • FIG. 4 is a flow chart of a local exchange according to a preferred embodiment of the present invention
  • FIG. 5 is a flow chart of local bearer establishment according to a preferred embodiment of the present invention
  • FIG. 6 is a preferred embodiment of the present invention.
  • the e B of the example determines whether a message flow chart of the local exchange can be performed
  • FIG. 7 is a message block diagram of the local bearer setup message of the MME to the e B according to a preferred embodiment of the present invention
  • FIG. 8 is a local bearer according to a preferred embodiment of the present invention.
  • FIG. 9 is a block diagram of a locally switched MAC header in accordance with a preferred embodiment of the present invention
  • Figure 10 is a flowchart of an RRC Connection Reconfiguration message in accordance with a preferred embodiment of the present invention
  • Figure 11 is a preferred embodiment in accordance with the present invention.
  • Figure 12 is a flow diagram of a local exchange message in accordance with a preferred embodiment of the present invention
  • 3 is a flow chart of local exchange data processing (PDCP layer forwarding) according to a preferred embodiment of the present invention
  • FIG. 14 is a flow chart of a ConterCheck base station message for preventing illegal intrusion according to a preferred embodiment of the present invention
  • FIG. 15 is a preferred embodiment of the present invention.
  • FIG. 16 is a flow diagram of local exchange data processing (for forwarding over the PDCP layer) in accordance with a preferred embodiment of the present invention.
  • BEST MODE FOR CARRYING OUT THE INVENTION will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • the embodiment of the present invention mainly provides a method for implementing local exchange of a terminal, and the method can also be used to implement local exchange of a wireless device having similar functions to the terminal in the embodiment of the present invention.
  • the SGW Serving Gateway
  • the PGW Packet Data Gateway
  • the problem of increasing the load of the network equipment of the core network and the transmission delay of the user data may reduce the load of the network equipment of the core network, shorten the transmission delay of the data, and increase the speed of data transmission.
  • the embodiment of the invention provides a local exchange method of a terminal. 1 is a flowchart of a local switching method of a terminal according to an embodiment of the present invention. As shown in FIG.
  • the method mainly includes the following steps (step S102 to step S104): Step S102, an evolved base station (e B ) cooperates with A terminal and a second terminal establish a local bearer, where the local bearer refers to a device-to-device (D2D)-specific bearer that needs to be used in the local switching process; and in step S104, the e B forwards the first terminal and the second terminal by using the local bearer. Business data between to achieve local exchange.
  • the eNB can establish a local bearer in cooperation with the first terminal and the second terminal located in the eNB or one of the neighboring eNBs, and then use the local bearer to forward the service data between the first terminal and the second terminal, which can be reduced.
  • step S102 may be implemented in the following manner: After the packet data gateway PGW initiates a local bearer setup process, the eNB initiates a first radio resource control RRC connection reconfiguration process to the first terminal and the second terminal, respectively.
  • the second radio resource control RC connection reconfiguration process in the case that both the first RC connection reconfiguration and the second RRC connection reconfiguration are successful, the eNB determines that the establishment of the local bearer has been completed, otherwise, according to the first terminal and/or the second The establishment failure message sent by the terminal re-initiates the RRC connection reconfiguration process to the first terminal and/or the second terminal until the establishment of the local bearer is completed.
  • the packet data gateway PGW initiates a local bearer setup process, which may include: after receiving the local bearer setup request message sent by the first terminal, the PGW generates a first transport stream template TFT for the first terminal, And adding the locally exchanged address type and the IP address of the second terminal to the first TFT, where the local bearer setup request message includes: an IP address of the first terminal and an IP address of the second terminal; and the PGW is configured according to the IP address of the second terminal.
  • the second terminal generates a second TFT, and adds a locally exchanged address type and an IP address of the first terminal in the second TFT.
  • the PGW generates a first local bearer setup message, where the first local bearer setup message is from the PGW.
  • the message to the mobility management entity MME includes: an IP address of the first terminal, a local switching TFT pair composed of the first TFT and the second TFT, and a quality of service QoS parameter; the PGW will first through the serving gateway SGW
  • the local bearer setup message is sent to the MME, and the MME generates a second local bearer setup message according to the first local bearer setup message, where the second local bearer setup message is a message from the MME to the eNB, and the second local bearer setup message includes: a first UE ID of a terminal, a second UE ID of the second terminal, a first E-RAB ID of the first terminal, and a second terminal A second E-RAB ID, and QoS parameters.
  • the eNB initiates a first radio resource control RRC connection reconfiguration process and a second radio resource control RRC connection reconfiguration process to the first terminal and the second terminal, which may be implemented in the following manner: Initiating the first radio resource control RRC connection reconfiguration procedure, the method includes: the eNB generates a first data radio bearer DRB of the first terminal to the eNB according to the first E-RAB ID, and generates a first DRB ID corresponding to the first DRB, a logical channel, and a first LC ID, where the reserved value of the first LC ID is used to identify the first logical channel in the process of performing local switching; the eNB generates a first RRC connection reconfiguration message corresponding to the first terminal, The first RRC connection reconfiguration message includes: a first DRB ID, a first LC ID, and a first NAS message corresponding to the first terminal, where the first NAS message carries the first TFT; the eNB sends the first to the first terminal
  • the first DRB ID and the second DRB ID have a fixed binding relationship.
  • the first DRB ID and the second DRB ID form a DRB ID pair.
  • the first terminal may use the first TFT. Binding to the first DRB, and performing other operations of the first RRC connection reconfiguration; the second terminal may bind the second TFT to the second DRB and perform other operations of the second RRC connection reconfiguration.
  • the first terminal may send a first RRC connection reconfiguration complete message to the eNB; the second terminal may send the first eNB to the eNB.
  • the second RRC connection reconfiguration complete message when the eNB receives the first RRC connection reconfiguration complete message and the second RRC connection reconfiguration complete message, the eNB may send a first RRC configuration end message to the first terminal, and send the message to the second terminal.
  • the second RRC configuration end message when both the first RRC connection reconfiguration and the second RRC connection reconfiguration are successful, the first terminal may send a first RRC connection reconfiguration complete message to the eNB; the second terminal may send the first eNB to the eNB.
  • the second RRC connection reconfiguration complete message when the eNB receives the first RRC connection reconfiguration complete message and the second RRC connection reconfiguration complete message, the eNB may send a first RRC configuration end message to the first terminal, and send the message to the second terminal.
  • the second RRC configuration end message when the eNB receives the first R
  • the step S104 may be implemented by: after receiving the call request SR signaling sent by the first terminal, the eNB sends the UL grant signaling to the first terminal, where the UL grant signaling carries the first The uplink resource used by the terminal to send the service data; the eNB receives the service data from the first terminal through the air interface, and processes the service data by the PHY layer, the MAC layer, and the RLC layer, so that the service data reaches the PDCP layer; the eNB is the second terminal. Allocating a buffer for use in receiving service data; the eNB transmits the service data to the second terminal through the cache.
  • the eNB sends the service data to the second terminal by using the buffer, in one of the following manners:
  • the eNB In the first mode, after the eNB service data is placed in the PDCP layer, the eNB sends the data to the second terminal through the buffer. After the data is placed on the PDCP layer, the data is sent to the second terminal by using the buffer. The data is sent to the eNB by the first method.
  • the eNB sends a first Countercheck message to the first terminal to enable the first terminal to check the service data according to the LTE process; when the second terminal sends the second data radio bearer to the eNB.
  • the eNB When the downlink packet count value of the DRB reaches the second technical threshold, the eNB sends a second Countercheck message to the second terminal, so that the second terminal performs the check check on the service data according to the LTE process.
  • the method before the evolved base station eNB cooperates with the first terminal and the second terminal to establish a local bearer, the method further includes: determining, by the eNB or the packet data gateway PGW, whether local exchange is possible.
  • the eNB determines whether the local exchange can be performed, and may be implemented in the following manner: In the process of attaching by the first terminal, the eNB receives the IP address of the first terminal sent by the mobility management entity MME, and saves the first The IP address of the terminal; in the process of attaching the second terminal, the eNB receives the IP address of the second terminal sent by the MME, and saves the IP address of the second terminal; When the local exchange request message of the IP address of the terminal is used, the eNB determines whether the IP address of the second terminal has been saved locally.
  • the method includes: the eNB sends a local exchange request response message to the first terminal, where the local exchange request response message is used to indicate the first terminal.
  • the local terminal can be exchanged with the second terminal, and the establishment process of the local bearer is started.
  • the PGW determines whether the local bearer can be established, and can be implemented in the following manner: After the first terminal succeeds and the second terminal successfully attaches, the PGW establishes an LTE bearer between the first terminal and the second terminal; The PGW receives the service data sent by the first terminal, where the service data includes: an IP address of the first terminal and an IP address of the second terminal; and the PGW determines the first according to the IP address of the first terminal and the IP address of the second terminal.
  • the embodiment of the present invention provides a local switching system for a terminal, which is used to implement the local switching method of the terminal provided by the foregoing embodiment.
  • 2 is a schematic structural diagram of a local switching system of a terminal according to an embodiment of the present invention. As shown in FIG.
  • the system mainly includes: an evolved base station (e B), a first terminal, a second terminal, and a packet data gateway (PGW). ), the Serving Gateway (SGW) and the Mobility Management Entity (MME).
  • the eNB may include: an establishing module 12, configured to establish a local bearer in cooperation with the first terminal and the second terminal, where the local bearer refers to a bearer dedicated to the device to the device D2D that needs to be used in the local switching process; and the forwarding module 14 It is configured to forward the service data between the first terminal and the second terminal by using the local bearer to implement local exchange.
  • the system can be further optimized to obtain a preferred embodiment. This preferred embodiment is further described below in conjunction with FIG.
  • the establishing module 12 may include: an initiating module 122, which is configured. After the local bearer establishment process is initiated on the PGW, the first radio resource control RRC connection reconfiguration process and the second radio resource control RRC connection reconfiguration process are respectively initiated to the first terminal and the second terminal; and the processing module 124 is set to be in the first When both the RRC connection reconfiguration and the second RRC connection reconfiguration are successful, determining the local bearer The establishment has been completed.
  • the PGW is configured to initiate a local bearer setup process, and the PGW includes: a first receiving module 21, configured to receive a local bearer setup request message sent by the first terminal; 22, the first transport stream template TFT is configured to be generated for the first terminal, and the locally exchanged address type and the IP address of the second terminal are added to the first TFT, where the local bearer setup request message includes: the IP of the first terminal The address and the IP address of the second terminal; the second generating module 23 is configured to generate a second TFT for the second terminal according to the IP address of the second terminal, and add the locally exchanged address type and the first terminal in the second TFT
  • the third generation module 24 is configured to generate a first local bearer setup message, where the first local bearer setup message
  • the initiating module 122 includes: a first generating unit 1221, configured to generate a first data radio bearer DRB of the first terminal to the eNB according to the first E-RAB ID, and generate Corresponding to the first DRB ID of the first DRB, the first logical channel, and the first LC ID, where the reserved value of the first LC ID is used to identify the first logical channel in the process of performing local switching; 1222.
  • the first RRC connection reconfiguration message is configured to generate a first RRC connection reconfiguration message, where the first RRC connection reconfiguration message includes: a first DRB ID, a first LC ID, and a first NAS message corresponding to the first terminal.
  • the first NAS message carries the first TFT.
  • the first sending unit 1223 is configured to send a first RRC connection reconfiguration message to the first terminal, and initiate a first RRC connection reconfiguration process.
  • the third generating unit 1224 is configured to Generating, by the second E-RAB ID, a second data radio bearer DRB of the second terminal to the eNB, and generating a second DRB ID, a second logical channel, and a second LC I corresponding to the second DRB D, wherein the reserved value of the second LC ID is used to identify the second logical channel in the process of performing local exchange;
  • the fourth generating unit 1225 is configured to generate a second RRC connection reconfiguration message corresponding to the second terminal, where
  • the second RRC connection reconfiguration message includes: a second DRB ID, a second LC ID, and a second NAS message corresponding to the second terminal, where the second NAS message carries the second TFT;
  • the second sending unit 1226 is configured to Sending a second
  • the first terminal includes: a first binding module 32, configured to: after the initiating module 122 initiates a first RRC connection reconfiguration process to the first terminal, Binding to the first DRB, and performing other operations of the first RRC connection reconfiguration;
  • the second terminal includes: a second binding module 42, configured to: after the initiating module 122 initiates the second RRC connection reconfiguration procedure to the second terminal Binding the second TFT to the second DRB, and performing other operations of the second RRC connection reconfiguration.
  • the first terminal further includes: a second sending module 34, configured to send the first RRC connection reconfiguration to the e B if the first RRC connection reconfiguration succeeds
  • the second terminal further includes: a third sending module 44, configured to send a second RRC connection reconfiguration complete message to the eNB if the second RRC connection reconfiguration succeeds.
  • the establishing module 12 further includes: a fourth sending module 126, configured to receive the first RRC connection reconfiguration complete message and the second RRC connection reconfiguration complete message And sending a first RRC configuration end message to the first terminal, and sending a second RRC configuration end message to the second terminal.
  • the forwarding module 14 includes: a second receiving module 141, configured to receive the call request SR signaling sent by the first terminal; and a fifth sending module 142, configured to be the first The terminal sends the UL grant signaling, where the UL grant signaling carries the uplink resource used by the first terminal to send the service data.
  • the third receiving module 143 is configured to receive the service data from the first terminal through the air interface, and the service data is received.
  • the sixth sending module 145 performs processing on the PHY layer, the MAC layer, and the RLC layer to enable service data to reach the PDCP layer; 44 And being configured to allocate, to the second terminal, a buffer used for receiving the service data; and the sixth sending module 145 is configured to send the service data to the second terminal by using the cache.
  • the sixth sending module 145 sends the service data to the second terminal by using the cache, in one of the following manners: In the first mode, the sixth sending module 145 places the service data in the PDCP. After the layer is sent to the second terminal by using the buffer, the second sending module 145 sends the service data to the second terminal by using the buffer, and then sends the data to the second terminal by using the buffer.
  • the sixth sending module 145 performs the encryption processing on the service data, including: when the uplink data packet count value of the first data radio bearer DRB of the first terminal to the eNB reaches the first counting threshold, the sixth sending module 145 sends the first sending module 145 to the first terminal. a first Countercheck message to enable the first terminal to check the service data according to the LTE process; when the second terminal to the eNB's second data radio bearer DRB When the downlink packet count value reaches the second technical threshold, the sixth sending module 145 sends a second Countercheck message to the second terminal, so that the second terminal performs the check check on the service data according to the LTE process.
  • the e B further includes: a first judging module 16, configured to determine whether the local exchange can be performed before the establishing module 12 establishes the local bearer; or the PGW further includes: The second determining module 26 is configured to determine whether local switching is possible before the establishing module 12 establishes a local bearer.
  • the first determining module 16 includes: a first receiving unit 161, configured to receive an IP address of the first terminal sent by the MME in the process of attaching the first terminal, And storing the IP address of the first terminal; the second receiving unit 162 is configured to receive the IP address of the second terminal sent by the MME and save the IP address of the second terminal in the process of attaching the second terminal;
  • the unit 163 is configured to: when receiving the local exchange request message that is sent by the first terminal and carrying the IP address of the second terminal, determine whether the IP address of the second terminal has been saved locally;
  • the first determining unit 164 is configured to be If the determination result is yes, it is determined that the first terminal and the second terminal can perform local exchange;
  • the query unit 165 is configured to, if the determination result is negative, query the neighboring eNB whether the neighboring eNB has saved the second The IP address of the terminal;
  • the second determining unit 166 is configured to: when the query result is yes, determine that the first terminal and the second terminal
  • the eNB further includes: a seventh sending module 18, configured to: when the first determining module 16 determines that the first terminal and the second terminal are capable of local switching, A terminal sends a local exchange request response message, where the local exchange request response message is used to indicate that the first terminal can perform local exchange with the second terminal, and initiates a local bearer establishment process.
  • the second determining module 26 includes: an establishing unit 262, configured to establish the first terminal and the second terminal after the first terminal succeeds and the second terminal successfully attaches
  • the third receiving unit 264 is configured to receive the service data sent by the first terminal, where the service data includes: an IP address of the first terminal and an IP address of the second terminal; and a second determining unit 266, setting In order to determine whether the first terminal and the second terminal are both located under the eNB according to the IP address of the first terminal and the IP address of the second terminal, and whether the eNB supports the local switching function, or whether the first terminal and the second terminal are respectively located in the eNB and The neighboring eNB and the eNB and the neighboring eNB support the local switching function.
  • the eNB can cooperate with the eNB or one of the first terminals located in the neighboring eNB. Establishing a local bearer with the second terminal, and then using the local bearer to forward the service data between the first terminal and the second terminal, thereby reducing the load on the network device of the core network, shortening the data transmission delay, and improving the data. The effect of the transmission speed.
  • Step 1 A local bearer is established between the first terminal and the second terminal.
  • Step 2 The eNB completes a local exchange process between the first terminal and the second terminal by using a local bearer. Step 1 may further subdivide the following three steps.
  • FIG. 4 A local bearer is established between the first terminal and the second terminal.
  • Step 2 The eNB completes a local exchange process between the first terminal and the second terminal by using a local bearer. Step 1 may further subdivide the following three steps.
  • Step 11 The eNB or the PGW determines whether it is OK. Establish a local bearer.
  • Step 12 The PGW initiates a process of establishing a local bearer.
  • Step 13 The eNB completes the RRC connection reconfiguration and completes the establishment of the local bearer.
  • the eNB or the PGW can first determine whether the local exchange can be performed.
  • data exchange at the PDCP layer and data exchange on the PDCP layer can be adopted.
  • the preferred embodiment of the present invention provides a specific embodiment in which the first terminal and the second terminal establish a local bearer and perform local exchange.
  • the eNB determines whether the local bearer can be established.
  • the first terminal and the second terminal serve the same e B.
  • the locally exchanged data is exchanged at the PDCP layer. Step 1: The eNB determines whether a local bearer can be established.
  • FIG. 6 is a message flow diagram of an eNB determining whether a local exchange can be performed according to a preferred embodiment of the present invention.
  • the specific process of the eNB determining whether a bearer can be established is as follows: The first terminal performs attaching. In the process of attaching, the MME transmits the IP address of the first terminal to the e B through the initial context setup request message, and after receiving the message, the eNB records the IP address of the first terminal, and the second terminal attaches, and is attached. In the process, the MME transmits the IP address of the second terminal to the eNB through the initial context setup request message, and after receiving the message, the eNB records the IP address of the second terminal.
  • the first terminal When the first terminal has data to send to the second terminal, the first terminal sends a local exchange request message to the eNB.
  • the message carries the IP address of the second terminal.
  • the eNB obtains the IP address of the second terminal from the message, and determines whether the local terminal can be exchanged.
  • the determining method is as follows: The eNB determines whether the eNB records the IP address of the second terminal, and if the judgment result is that the eNB records the second terminal. The eNB considers that the first terminal and the second terminal can perform local exchange. If the eNB determines that the eNB does not record the IP address of the second terminal, the eNB sends an IP address query to the neighboring eNB through the X2 interface.
  • the message carries the IP address of the second terminal, and the neighboring eNB determines whether the IP address of the second terminal is recorded after receiving the message. If the neighboring eNB supports the local exchange and records the IP address of the second terminal, and then returns an IP address query response message, indicating that the IP address is queried, the eNB considers that the first terminal and the second terminal can perform localization after receiving the message. Exchange, otherwise the neighboring eNB returns an IP address query response message, indicating that the IP address is not queried. After receiving the message, the eNB considers that the first terminal and the second terminal cannot perform the exchange.
  • the eNB records the IP address of the second terminal, and after obtaining the IP address of the second terminal, the eNB determines the IP address of the second terminal recorded by the local eNB, and the eNB considers that A terminal and a second terminal can perform local exchange.
  • the eNB returns a local exchange request response message to the first terminal, indicating that the first terminal and the second terminal can perform local exchange.
  • the first terminal sends a local exchange bearer setup request message to the PGW, where the message carries the IP address of the first terminal and the IP address of the second terminal.
  • Step 2 The PGW initiates a process of establishing a local bearer.
  • the PGW After receiving the local exchange bearer setup request message of the first terminal, the PGW generates a TFT of the first terminal for local exchange, and first generates a TFT of the first terminal (that is, the first TFT) according to a normal process, and then A new type (ie, a locally exchanged address type) is added to the packet filter content unit of the packet filter of the TFT of the first terminal.
  • a new type ie, a locally exchanged address type
  • the address type exchanged locally is followed by the IP address of the target UE, that is, the IP address of the second terminal, and can only contain the IP address of the second terminal.
  • the PGW also generates a TFT for the second terminal for local exchange (ie, the second TFT described above), first generates a TFT of the second terminal according to a normal flow, and then performs a packet filter content unit of the packet filter of the second terminal TFT.
  • a new type has been added (that is, the address type of the local exchange).
  • the address type exchanged locally is followed by the IP address of the target UE, that is, the IP address of the first terminal, and can only contain the IP address of the first terminal.
  • the local switching TFT of the first terminal and the local switching TFT of the second terminal form a TFT pair.
  • the PGW generates a local bearer setup message, which contains the parameters contained in the normal bearer setup message. It also includes the local exchange TFT pair and the IP address of the second terminal.
  • the PGW generates a local bearer setup message from the PGW to the MME, and the message is sent to the MME through the SGW.
  • the MME determines, according to the IP address of the second terminal, the second terminal, and obtains the MME UE SIAP ID value and the eNB UE SIAP ID value of the second terminal according to the context information of the second terminal, and the UE Aggregate Maximum Bit Rate of the second terminal. value.
  • the MME generates an E-RAB ID of the first terminal (ie, the first E-RAB ID) and an E-RAB ID of the second terminal (ie, the second E-RAB ID) according to the message.
  • the MME also generates a NAS message and packs it into the NAS PDU and the NAS PDU2 parameters, and includes the first terminal NAS message in the NAS PDU parameter, which includes the local switching TFT corresponding to the first terminal, and is included in the NAS PDU2 parameter.
  • the second terminal NAS message includes a local switching TFT corresponding to the second terminal.
  • the MME generates a local bearer setup message from the MME to the eNB.
  • 7 is a message block diagram of a local bearer setup message of an MME to an eNB according to a preferred embodiment of the present invention. As shown in FIG.
  • the message includes the following parameters: MME UE S1AP ID, eNB UE SIAP ID, UE Aggregate Maximum Bit Rate, E-RAB ID, NAS-PDU, E-RAB Level QoS Parameters, MME UE S1AP ID2, eNB UE S1AP ID2, UE Aggregate Maximum Bit Rate2, E-RAB ID2, NAS-PDU2 where MME UE SIAP ID, eNB UE SIAP ID , UE Aggregate Maximum Bit Rate, E-RAB ID is a parameter related to the first terminal, MME UE SIAP ID2, eNB UE S1AP ID2, UE Aggregate Maximum Bit Rate2, E-RAB ID2, NAS-PDU2 is a second terminal related parameter .
  • FIG. 8 is a flow chart of establishing a local bearer according to a preferred embodiment of the present invention. As shown in FIG. 8, the PGW is generated to
  • the local bearer setup message of the MME includes the TFT pair, the IP address of the second terminal, and parameters such as Qos.
  • the message is sent to the MME via the SGW.
  • the MME After receiving the message, the MME generates a local bearer setup message of the MME to the eNB, where the message includes the UE ID of the first terminal and the second terminal, and the E-RAB ID and Qos parameters of the first terminal and the second terminal.
  • the MME sends the message to e B.
  • Step 3 The eNB completes the RRC connection reconfiguration and completes the establishment of the local bearer.
  • the eNB After receiving the local bearer setup message sent by the MME, the eNB generates a DRB pair and generates a corresponding DRB ID pair and an LCID pair according to the E-RAB ID pair of the message.
  • the eNB generates a data radio bearer (DRB) of the first terminal to the eNB according to the E-RAB ID parameter corresponding to the first terminal in the message, and generates a data radio bearer identifier DRB ID.
  • DRB data radio bearer
  • the eNB generates a data radio bearer (DRB) of the second terminal to the eNB according to the E-RAB ID2 parameter corresponding to the second terminal in the message, and generates a data radio bearer identifier DRB ID2, where the two DRBs have a fixed binding relationship, and the same
  • the DRB ID and DRB ID2 also have a fixed binding relationship.
  • the DRB ID and DRB ID2 form a DRB ID pair.
  • the eNB generates a logical channel corresponding to the DRB of the first terminal to the eNB, and generates an LCID
  • the eNB generates a logical channel corresponding to the DRB of the second terminal to the eNB, and generates an LCID2.
  • FIG. 9 is a block diagram of a locally exchanged MAC header according to a preferred embodiment of the present invention. As shown in FIG. 9, when generating a MAC subheader, the eNB may use the original R bit, that is, a reserved bit, to indicate that it is a locally switched Mac. Sub-header format, you can change the R bit to the T bit, that is, the type bit.
  • the eNB adds an LSdrb-ToAddModList field in the RadioResourceConfigDedicated field in the RRC Connection Reconfiguration message, which field contains the DRB ID used by the local exchange. After generating the locally exchanged DRB pair and the logical channel and generating the DRB ID pair and the LCID, the eNB separately generates an RRC connection reconfiguration message from the eNB to the first terminal and an RRC connection reconfiguration message from the eNB to the second terminal.
  • the RRC connection reconfiguration message of the eNB to the first terminal includes parameters such as a DRB ID and an LCID corresponding to the DRB of the eNB to the first terminal, and the eNB obtains the NAS message included in the NAS PDU parameter of the bearer setup message of the MME to the eNB, and The NAS message is carried by the RRC connection reconfiguration message, and the NAS message includes the locally exchanged TFT corresponding to the first terminal.
  • the RRC connection reconfiguration message of the eNB to the second terminal includes parameters such as DRB ID2 and LCID2 corresponding to the DRB of the second terminal to the eNB, and the eNB obtains the NAS message included in the NAS PDU parameter of the bearer setup message from the MME to the eNB, and The NAS message is carried by the connection reconfiguration message, where the NAS message includes a local switching TFT corresponding to the second terminal.
  • the eNB After the eNB generates an RRC connection reconfiguration message, the RRC connection reconfiguration is initiated.
  • FIG. 10 is a flowchart of an RRC connection reconfiguration message according to a preferred embodiment of the present invention. As shown in FIG.
  • the eNB sends an RRC connection reconfiguration message from the eNB to the first terminal to the first terminal, and sends the eNB to the second terminal.
  • the RRC connection reconfiguration message of the second terminal After receiving the connection reconfiguration message, the first terminal will generate a local exchange DRB of the first terminal to the eNB, and the DRB will be identified by the DRB ID, and the local switching TFT will be bound to the local exchange DRB, and the first terminal will be first.
  • the local switching TFT of the terminal is bound to the local exchange DRB of the first terminal to the eNB.
  • complete other operations of RRC connection reconfiguration After completing the RRC connection reconfiguration, the first terminal returns an RRC connection reconfiguration complete message to the eNB.
  • the second terminal After receiving the RRC connection reconfiguration message, the second terminal performs TFT bonding, and generates a local switching DRB of the second terminal to the eNB, where the DRB is identified by DRB ID2, and the local switching TFT is switched to the local switching DRB. Binding, binding the local switching TFT of the second terminal to the second terminal to the local exchange DRB of the eNB. And complete other operations of RRC connection reconfiguration.
  • the first terminal After completing the RRC connection reconfiguration, the first terminal returns an RRC connection reconfiguration complete message to the eNB.
  • the eNB After receiving the RRC connection reconfiguration complete message of the first terminal and the RRC connection reconfiguration complete message of the second terminal, the eNB. And sending an RRC configuration end message to the first terminal and the second terminal respectively.
  • the first terminal After receiving the RRC configuration end message, the first terminal starts local data exchange with the second terminal, and after receiving the RRC configuration end message, the second terminal starts local data exchange with the first terminal.
  • the above is the normal flow of the RRC connection reconfiguration and the configuration is successful. If the RRC connection reconfiguration fails, the RRC connection reconfiguration exception procedure is entered.
  • 11 is a flowchart of an RRC connection reconfiguration failure message according to a preferred embodiment of the present invention. As shown in FIG. 11, after the eNB sends an RRC connection reconfiguration message to the first terminal, if the first terminal is performing RRC connection reconfiguration, The reconfiguration failure fails.
  • an RRCConnectionConfigurationFailure message is added in the RRC connection reconfiguration exception procedure of the local exchange, and the message indicates that the RRC connection configuration of the local exchange fails.
  • the first terminal sends the message to e B, and the first terminal may carry an RRCConnectionConfigurationFigurationCause unit in the message, the unit indicating the reason for the failure.
  • the eNB may re-allocate the RRC connection reconfiguration related parameter for the local exchange communication according to the failure reason, and resend the RRCConnectionReconfiguration message.
  • the first terminal returns the RRCConnectionReconfigurationComplete message, and the eNB performs the following process, after receiving the first terminal and The RRCConnectionReconfigurationComplete message of the second terminal sends a bearer setup response to the MME, indicating that the local bearer is successfully established. If the configuration is successful, the first terminal will return the RRCConnectionConfigurationFailure message a second time, and the eNB sends a bearer setup response to the MME, where the message is E. In the -RAB Failed to Setup List unit, it indicates that the local bearer setup failed due to the RRC connection reconfiguration failure with the first terminal.
  • the eNB further sends an RRC connection reconfiguration recovery message to the second terminal, and restores the second terminal to the state before the connection reconfiguration.
  • Step four the local exchange process. After the local exchange bearer is established, local data exchange will take place.
  • 12 is a flow chart of a local exchange message according to a preferred embodiment of the present invention. As shown in FIG. 12, when the first terminal has data to transmit, the first terminal sends scheduling request signaling, that is, SR signaling, and the eNB receives the SR. After the signaling, the UL grant signaling is sent, where the signaling includes the uplink transmission resource allocated for the first terminal, but the uplink resource allocated by the UL grant is very limited.
  • the first terminal after receiving the UL grant signaling, the first terminal sends a BSR message to the eNB for the uplink resource allocated by the eNB, where the message carries the buffer (ie, cache) of the data to be sent by the first terminal. size.
  • eNB After the message, the buffer size of the data to be sent by the first terminal will be obtained.
  • the eNB checks the size of the space left by the forwarding buffer used for the local exchange. If the remaining space of the forwarding buffer is greater than the buffers of the data to be sent by the first terminal, the eNB allocates uplink resources to the first terminal and sends UL grant signaling. After receiving the uplink signaling, the first terminal sends the service data on the uplink resource allocated by the eNB.
  • FIG. 13 is a flowchart of local exchange data processing (PDCP layer forwarding) according to a preferred embodiment of the present invention.
  • the first terminal sends service data to the second terminal.
  • the switching TFT is mapped to the locally switched DRB of the first terminal, and after being processed by the PDCP layer, the RLC layer, the MAC layer, and the PHY layer, is sent out through the air interface.
  • the eNB After receiving the data sent by the first terminal, the eNB passes through the PHY layer, the MAC layer, and the RLC layer to reach the PDCP layer.
  • locally exchanged data is forwarded at the PDCP layer.
  • the eNB After the data passes through the RLC layer, among the DRBs corresponding to the DRB ID exchanged locally by the eNB, the eNB reads data from the DRB, writes it into the forwarding buffer, and records the packet read from the DRB. Number, record it as countMSB-Uplink.
  • the eNB allocates downlink resources to the second terminal, and reads data from the forwarding buffer, and writes the data into the DRB corresponding to the local exchange DRB ID2 of the eNB. And record the number of packets written to the DRB, and record it as countMSB-Downlink.
  • the data After the data is written into the DRB corresponding to the DRB ID2 of the eNB, it is processed by the RLC layer, the MAC layer, and the PHY layer, and is sent to the second terminal. After receiving the data, the second terminal passes the PHY layer and the MAC layer. After the RLC layer and the PDCP layer are processed, the data is written into the DRB corresponding to the second terminal local exchange DRB ID2, and the data is mapped to the service layer through the mapping of the second terminal local switching TFT. Forwarding at the PDCP layer, data encryption and decryption processing is performed between the first terminal and the second terminal. However, in order to prevent the data between the first terminal and the eNB from being attacked by the intruder.
  • the local exchange countercheck mechanism is adopted between the eNB and the first terminal, and the local exchange countercheck mechanism is also adopted between the eNB and the second terminal.
  • 14 is a message flow diagram of a ConterCheck base station for preventing illegal intrusion according to a preferred embodiment of the present invention.
  • the eNB A Countercheck message is sent to the first terminal, and the drb-CountMSB-InfoList field of the message will contain the value of countMSB-Uplink.
  • the first terminal performs a Countercheck check according to the normal LTE procedure. And return the CounterCheckResponse message.
  • the eNB When the value of the countMSB-Downlink of the DRB corresponding to the DRB ID2 of the eNB reaches a certain value, the eNB sends a Countercheck message to the second terminal, and the drb-CountMSB-InfoList field of the message will contain the value of countMSB-Uplink.
  • the second terminal performs a CountCheck check according to a normal LTE process. And return the CounterCheckResponse message. Only when the eNB and the first terminal and the eNB and the second terminal are both correct, it is considered that the local switching link between the first terminal and the second terminal passes the Countercheck check.
  • the preferred embodiment of the present invention provides a specific embodiment in which the first terminal and the second terminal establish a local bearer and perform local exchange.
  • the PGW determines whether the local bearer can be established.
  • the first terminal and the second terminal are served by the same eNB, and are also under the management of the same PGW.
  • the locally exchanged data is exchanged over the PDCP layer.
  • Step 1 The PGW determines whether a local bearer can be established.
  • FIG. 15 is a message flow diagram of a PGW determining whether a local exchange can be performed according to a preferred embodiment of the present invention. As shown in FIG. 15, the specific process of the PGW determining whether a bearer can be established is as follows: The first terminal performs attaching. The second terminal performs the attaching.
  • the PGW When the first terminal has data to be sent to the second terminal, the PGW is requested to establish a normal bearer. After the normal LTE bearer is established, the first terminal sends data to the second terminal through the bearer. The data packet sent by the first terminal to the second terminal will pass through the PGW, and the PGW obtains the destination address of the data packet from the data packet sent by the first terminal. In this embodiment, the destination address of the first terminal data packet is the IP address of the second terminal. The PGW can obtain, according to the IP address of the second terminal, that the destination of the data packet sent by the first terminal is the second terminal. The PGW determines whether the first terminal and the second terminal are in the same eNB.
  • the PGW considers that the first terminal and the second terminal can perform the If the first terminal and the second terminal are not in the same eNB, the first terminal and the second terminal are determined to be in the neighboring eNB, and the two neighboring eNBs support the local switching function. Condition, the first terminal and the second terminal can perform local exchange. If the above two conditions are not met, the first terminal and the second terminal cannot perform local exchange. In this embodiment, the first terminal and the second terminal serve the same e B, so that local exchange can be performed, and the PGW will initiate a local bearer establishment process. Step 2: The PGW initiates a process of establishing a local bearer.
  • the PGW initiates a process of establishing a local bearer, and the PGW generates a TFT for the first terminal for local exchange (ie, the first TFT), first generates a TFT of the first terminal according to a normal process, and then filters the packet of the TFT in the first terminal.
  • a new type ie, the locally exchanged address type
  • the locally exchanged address type is followed by the IP address of the target UE (ie, the IP address of the second terminal), and Contains the IP address of the second terminal.
  • the PGW also generates a TFT for the second terminal for local exchange (ie, the above second TFT), first generates a TFT of the second terminal according to a normal flow, and then a packet filter content unit of the packet filter of the second terminal TFT , A new type (ie, the locally exchanged address type) is added, and the locally exchanged address type is followed by the IP address of the target UE (ie, the IP address of the first terminal), and can only contain the IP address of the first terminal.
  • the local switching TFT of the first terminal and the local switching TFT of the second terminal constitute a TFT pair.
  • the PGW generates a local bearer setup message, which contains the parameters contained in the normal bearer setup message. It also includes the local exchange TFT pair and the IP address of the second terminal.
  • the PGW generates a local bearer setup message from the PGW to the MME, and the message is sent to the MME through the SGW.
  • the MME determines, according to the IP address of the second terminal, the second terminal, and obtains the MME UE SIAP ID value and the eNB UE SIAP ⁇ ) value of the second terminal according to the context information of the second terminal. And the value of the UE Aggregate Maximum Bit Rate of the second terminal.
  • the MME generates an E-RAB ID (ie, the first E-RAB ID) of the first terminal and a second terminal E-RAB ID (ie, the second E-RAB ID) according to the message.
  • the MME also generates a NAS message and packs it into the NAS PDU and NAS PDU2 parameters, and includes the first terminal NAS message in the NAS PDU parameter, which includes the local switching TFT corresponding to the first terminal, and is included in the NAS PDU2 parameter.
  • the second terminal NAS message includes a local switching TFT corresponding to the second terminal.
  • the MME generates a local bearer setup message of the MME to the eNB.
  • 7 is a message block diagram of a local bearer setup message of an MME to an eNB according to a preferred embodiment of the present invention. As shown in FIG.
  • the message includes the following parameters: MME UE S1AP ID, eNB UE SIAP ID, UE Aggregate Maximum Bit Rate, E-RAB ID, NAS-PDU, E-RAB Level QoS Parameters, MME UE S1AP ID2, eNB UE S1AP ID2, UE Aggregate Maximum Bit Rate2, E-RAB ID2, NAS-PDU2 where MME UE SIAP ID, eNB UE SIAP ID , UE Aggregate Maximum Bit Rate, E-RAB ID is a parameter related to the first terminal, MME UE SIAP ID2, eNB UE S1AP ID2, UE Aggregate Maximum Bit Rate2, E-RAB ID2, NAS-PDU2 is a second terminal related parameter .
  • FIG. 8 is a flowchart of a local bearer setup according to a preferred embodiment of the present invention.
  • the PGW initiates a local bearer setup process.
  • the PGW generates a local bearer setup message to the MME, where the message includes a TFT pair, and the second terminal. IP address, and parameters such as Qos.
  • the message is sent to the MME via the SGW.
  • the MME After receiving the message, the MME generates a local bearer setup message of the MME to the eNB, where the message includes the UE ID of the first terminal and the second terminal, and the E-RAB ID and Qos parameters of the first terminal and the second terminal.
  • the MME sends the message to the eNB.
  • Step 3 The eNB completes the RRC connection reconfiguration and completes the establishment of the local bearer.
  • the eNB After receiving the local bearer setup message sent by the MME, the eNB generates a DRB pair and generates a corresponding DRB ID pair and an LCID pair according to the E-RAB ID pair of the message.
  • the eNB generates a data radio bearer (DRB) of the first terminal to the eNB according to the E-RAB ID parameter corresponding to the first terminal in the message, and generates a data radio bearer identifier DRB. ID.
  • the eNB generates a data radio bearer (DRB) of the second terminal to the eNB according to the E-RAB ID2 parameter corresponding to the second terminal in the message, and generates a data radio bearer identifier DRB ID2, where the two DRBs have a fixed binding relationship.
  • the DRB ID and the DRB ID2 also have a fixed binding relationship, and the DRB ID and the DRB ID2 form a DRB ID pair.
  • the eNB generates a logical channel corresponding to the DRB of the first terminal to the eNB, and generates an LCID
  • the eNB generates a logical channel corresponding to the DRB of the second terminal to the eNB, and generates an LCID2.
  • e B can break the limit of the number of radio bearer identifiers specified in the current protocol.
  • the eNB can also break the limit of the number of logical channel identifiers specified by the current protocol.
  • 9 is a block diagram of a locally exchanged MAC header according to a preferred embodiment of the present invention. As shown in FIG.
  • the eNB when generating a MAC subheader, the eNB may use the original R bit, that is, a reserved bit, to indicate that it is a locally switched Mac. Sub-header format, you can change the R bit to the T bit, that is, the type bit. You can use 1 to indicate the MAC sub-header of the local exchange, and 0 to indicate the normal MAC header. And when performing local exchange, the reserved value of the LCID can be used to identify the logical channel of the local exchange to reach the extension of the number of LCIDs.
  • the eNB adds an LSdrb-ToAddModList field in the RadioResourceConfigDedicated field in the RRC Connection Reconfiguration message, which field contains the DRB ID used by the local exchange.
  • an RRC connection reconfiguration message from the eNB to the first terminal and an RRC connection reconfiguration message from the eNB to the second terminal are generated.
  • the RRC connection reconfiguration message of the eNB to the first terminal includes parameters such as a DRB ID and an LCID corresponding to the DRB of the eNB to the first terminal, and the eNB obtains the NAS message included in the NAS PDU parameter of the bearer setup message of the MME to the eNB, and
  • the NAS message is carried by the RRC connection reconfiguration message, and the NAS message includes the locally exchanged TFT corresponding to the first terminal.
  • the RRC connection reconfiguration message of the eNB to the second terminal includes parameters such as DRB ID2 and LCID2 corresponding to the DRB of the second terminal to the lj eNB, and the eNB obtains the NAS message included in the NAS PDU parameter of the bearer setup message of the MME to the eNB, And the NAS message is carried by the connection reconfiguration message, where the NAS message includes the local switching TFT corresponding to the second terminal.
  • the RRC connection reconfiguration is initiated.
  • FIG. 10 is a flowchart of the RRC connection reconfiguration message according to the preferred embodiment of the present invention. As shown in FIG.
  • the RRC connection reconfiguration process includes: A terminal sends an RRC connection reconfiguration message of the eNB to the first terminal, and sends an RRC connection reconfiguration message of the eNB to the second terminal to the second terminal.
  • the first terminal After receiving the connection reconfiguration message, the first terminal generates a local exchange DRB of the first terminal to the eNB, and the DRB identifies the DRB ID, and performs binding of the local switching TFT to the local exchange DRB, and the first The local switching TFT of the terminal is bound to the local exchange DRB of the first terminal to the eNB. And complete other operations of RRC connection reconfiguration. After completing the RRC connection reconfiguration, the first terminal returns an RRC connection reconfiguration complete message to the eNB.
  • the second terminal After receiving the RRC connection reconfiguration message, the second terminal will perform TFT binding, and will generate a local exchange DRB of the second terminal to the eNB, the DRB will be identified by DRB ID2, and the local switching TFT will be performed to the local exchange DRB. Binding, binding the local switching TFT of the second terminal to the second terminal Go to the local exchange DRB of the eNB. And complete other operations of RRC connection reconfiguration.
  • the first terminal After completing the RRC connection reconfiguration, the first terminal returns an RRC connection reconfiguration complete message to the eNB.
  • the eNB After receiving the RRC connection reconfiguration complete message of the first terminal and the RRC connection reconfiguration complete message of the second terminal, the eNB. And sending an RRC configuration end message to the first terminal and the second terminal respectively.
  • the first terminal After receiving the RRC configuration end message, the first terminal starts to perform local data exchange with the second terminal, and after receiving the RRC configuration end message, the second terminal starts to perform local data exchange with the first terminal, where the RRC connection reconfiguration is configured. If the RRC connection reconfiguration configuration fails, the RRC connection reconfiguration exception procedure is entered.
  • 11 is a flowchart of an RRC connection reconfiguration failure message according to a preferred embodiment of the present invention. As shown in FIG. 11, after the eNB sends an RRC connection reconfiguration message to the first terminal, if the first terminal is performing RRC connection reconfiguration, The reconfiguration failure fails.
  • an RRCConnectionConfigurationFailure message is added in the RRC connection reconfiguration exception procedure of the local exchange, and the message indicates that the RRC connection configuration of the local exchange fails.
  • the first terminal sends the message to e B, and the first terminal may carry an RRCConnectionConfigurationFigurationCause unit in the message, the unit indicating the reason for the failure.
  • the eNB may re-allocate the RRC connection reconfiguration related parameter for the local exchange communication according to the failure reason, and resend the RRCConnectionReconfiguration message.
  • the first terminal returns the RRCConnectionReconfigurationComplete message, and the eNB performs the following process, after receiving the first terminal and The RRCConnectionReconfigurationComplete message of the second terminal sends a bearer setup response to the MME, indicating that the local bearer is successfully established. If the configuration is successful, the first terminal will return the RRCConnectionConfigurationFailure message a second time, and the eNB sends a bearer setup response to the MME, where the message is E. In the -RAB Failed to Setup List unit, it indicates that the local bearer setup failed due to the RRC connection reconfiguration failure with the first terminal.
  • FIG. 12 is a flow chart of a local exchange message according to a preferred embodiment of the present invention. As shown in FIG.
  • the message flow of the local data exchange includes: when the first terminal has data to send, the first terminal sends a scheduling request signaling, that is, The SR signaling, after receiving the SR signaling, the eNB sends the UL grant signaling, where the signaling includes the uplink transmission resource allocated for the first terminal, but the uplink resource allocated by the UL grant is very limited.
  • the first terminal after receiving the UL grant signaling, the first terminal sends a BSR message to the eNB for the uplink resource allocated by the eNB, where the message carries the size of the buffer of the data to be sent by the first terminal. After receiving the message, the eNB obtains the buffer size of the data to be sent by the first terminal.
  • FIG. 16 is a flowchart of local exchange data processing (for forwarding on the PDCP layer) according to a preferred embodiment of the present invention. As shown in FIG. 16, in the preferred embodiment, the service data of the first terminal to the second terminal is shown in FIG.
  • the local switching TFT is mapped to the DRB corresponding to the DRB ID of the local exchange of the first terminal, and then sent out through the air interface.
  • the eNB After receiving the data sent by the first terminal, the eNB passes through the PHY layer, the MAC layer, and the RLC layer to reach the PDCP layer.
  • the eNB After the data passes through the PDCP layer, it is already in the DRB corresponding to the DRB ID exchanged locally by the eNB, and the data of the first terminal to the eNB has been protected by the encryption and decryption processing of the PDCP layer and countercheck, and the eNB processes the data security. It can be processed according to the current agreement.
  • the eNB reads data from the DRB and writes it into the forwarding buffer.
  • the eNB allocates downlink resources to the second terminal, and reads data from the forwarding buffer, and writes the data to the local exchange DRB ID2 corresponding to the eNB. DRB.
  • the data After the data is written into the DRB corresponding to the DRB ID2, it is processed by the PDCP layer, the RLC layer, the MAC layer, and the PHY layer, and is sent to the second terminal.
  • the data between the eNB and the second terminal has been encrypted and decrypted by the PDCP layer and counterchecked by the PDCP layer.
  • the eNB can process the data security according to the current protocol.
  • the data is processed by the PHY layer, the MAC layer, the RLC layer, and the PDCP layer, and the data is written into the DRB corresponding to the local exchange DRB ID2 of the second terminal, and is locally exchanged by the second terminal. TFT mapping, data reaches the business layer.
  • each of the above modules can be implemented by hardware.
  • a processor including the above modules, or each of the above modules is located in one processor.
  • software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments.
  • a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like. From the above description, it can be seen that the present invention achieves the following technical effects: When the eNB or the PGW determines that the first terminal and the second terminal can perform local exchange, the eNB can cooperate with the eNB or one of the neighboring eNBs.
  • the first terminal and the second terminal establish a local bearer, and then use the local bearer to forward the service data between the first terminal and the second terminal, and solve the related art to perform data forwarding by using the LTE technology.
  • the method increases the load of the network equipment of the core network and the transmission delay of the user data, and achieves the effect of reducing the load of the network equipment of the core network, shortening the transmission delay of the data, and improving the data transmission speed.
  • the computing device may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

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

Abstract

La présente invention concerne un procédé et un système permettant l'échange local d'un terminal. Le procédé comprend les étapes suivantes : une station de base évoluée eNB se coordonne avec un premier terminal et un second terminal pour établir une onde porteuse locale, l'onde porteuse locale faisant référence à une onde porteuse dédiée à un système dispositif à dispositif (D2D) qu'on doit utiliser dans un processus d'échange local ; et l'eNB transmet des données de service entre le premier terminal et le second terminal à l'aide de l'onde porteuse locale afin de mettre en œuvre l'échange local. Grâce à la présente invention, on obtient des effets de réduction de charges d'un dispositif de réseau dans un réseau central, de raccourcissement d'un délai de transmission des données, et d'amélioration d'une vitesse de transmission des données.
PCT/CN2014/080344 2013-11-01 2014-06-19 Procédé et système d'échange local de terminal WO2015062287A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310538380.XA CN104618849A (zh) 2013-11-01 2013-11-01 终端的本地交换方法及系统
CN201310538380.X 2013-11-01

Publications (1)

Publication Number Publication Date
WO2015062287A1 true WO2015062287A1 (fr) 2015-05-07

Family

ID=53003262

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/080344 WO2015062287A1 (fr) 2013-11-01 2014-06-19 Procédé et système d'échange local de terminal

Country Status (2)

Country Link
CN (1) CN104618849A (fr)
WO (1) WO2015062287A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4207828A4 (fr) * 2020-09-27 2023-09-20 Huawei Technologies Co., Ltd. Procédé de communication de données et appareil de communication

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107926065B (zh) 2015-08-14 2020-04-28 华为技术有限公司 一种设备对设备d2d的数据传输方法、装置及系统
KR20190002431A (ko) * 2016-05-11 2019-01-08 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 통신 방법, 단말 기기 및 네트워크 기기
CN109644384B (zh) * 2016-08-26 2021-02-05 华为技术有限公司 一种网络管理方法和控制器
CN109996306B (zh) 2017-12-29 2022-02-25 华为技术有限公司 通信方法和通信设备
WO2020077574A1 (fr) * 2018-10-17 2020-04-23 北京小米移动软件有限公司 Procédé et dispositif de transmission à base de liaison latérale
WO2020191741A1 (fr) 2019-03-28 2020-10-01 Oppo广东移动通信有限公司 Procédé et appareil de gestion de connexion, dispositif informatique et support de stockage

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159905A (zh) * 2007-11-07 2008-04-09 华为技术有限公司 基站控制器内实现本地交换方法、核心网设备及网络系统
CN101754412A (zh) * 2008-12-08 2010-06-23 中兴通讯股份有限公司 Gsm系统中实现基站群本地交换的方法、设备及系统
CN101815358A (zh) * 2009-02-24 2010-08-25 鼎桥通信技术有限公司 一种用户设备之间的数据传输方法
WO2012106932A1 (fr) * 2011-07-26 2012-08-16 华为技术有限公司 Procédé et dispositif d'établissement d'échange de données, procédé et dispositif d'échange de données et noeud de support

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101835131B (zh) * 2009-03-10 2012-12-12 华为技术有限公司 一种数据本地交换方法、装置和系统
CN102088688B (zh) * 2009-12-07 2014-01-22 华为技术有限公司 信息交互的控制方法
CN102843779B (zh) * 2011-06-22 2017-03-22 中兴通讯股份有限公司 连接的建立处理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159905A (zh) * 2007-11-07 2008-04-09 华为技术有限公司 基站控制器内实现本地交换方法、核心网设备及网络系统
CN101754412A (zh) * 2008-12-08 2010-06-23 中兴通讯股份有限公司 Gsm系统中实现基站群本地交换的方法、设备及系统
CN101815358A (zh) * 2009-02-24 2010-08-25 鼎桥通信技术有限公司 一种用户设备之间的数据传输方法
WO2012106932A1 (fr) * 2011-07-26 2012-08-16 华为技术有限公司 Procédé et dispositif d'établissement d'échange de données, procédé et dispositif d'échange de données et noeud de support

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4207828A4 (fr) * 2020-09-27 2023-09-20 Huawei Technologies Co., Ltd. Procédé de communication de données et appareil de communication

Also Published As

Publication number Publication date
CN104618849A (zh) 2015-05-13

Similar Documents

Publication Publication Date Title
WO2021159906A1 (fr) Procédé et appareil de communication de relais de liaison latérale, dispositif et support
JP6718103B2 (ja) 通信方法
WO2018141284A1 (fr) Procédé, dispositif et système de communication pour traitement de flux qos
WO2018028694A1 (fr) Procédé et dispositif de communication destinés au système de communication directe de dispositif et système de communication
WO2018028504A1 (fr) Procédé et dispositif de routage
WO2015062287A1 (fr) Procédé et système d'échange local de terminal
TWI804992B (zh) 層2使用者設備透過網路中繼進行信令傳輸的方法
JP5088091B2 (ja) 基地局装置、通信方法及び移動通信システム
WO2013010420A1 (fr) Procédé, dispositif et système de communication à très large bande sans fil
JP2014511168A (ja) 移動体通信ネットワークおよび方法
WO2013064104A1 (fr) Procédé de transmission de données, entité de gestion de mobilité et terminal mobile
WO2013010418A1 (fr) Procédé, appareil et système pour une communication à très large bande sans fil
WO2013097586A1 (fr) Procédé de transfert de communication, équipement utilisateur et station de base
WO2014048224A1 (fr) Procédé, dispositif et système permettant de transmettre des données par signalisation de plan de commande
WO2012167743A1 (fr) Procédé, équipement d'utilisateur et station de base pour une interaction entre un réseau wlan et un réseau wwan
WO2013075602A1 (fr) Procédé, station de base et équipement d'utilisateur pour obtenir une agrégation de porteuses
WO2013117128A1 (fr) Procédé de transmission et de réception de données, équipement utilisateur, station de base et passerelle
WO2022001761A1 (fr) Procédé et appareil de communication
TW201735715A (zh) 用於中繼傳輸的方法和裝置以及中繼終端設備
CN110999382B (zh) 用于控制分组复制的方法及设备
WO2022001928A1 (fr) Procédé et appareil de communication
WO2014153721A1 (fr) Procédé et système de transmission de paquet de données, dispositif terminal et dispositif de réseau
WO2019192492A1 (fr) Procédé d'indication pour demander des informations de système, et dispositif et système associés
WO2014032311A1 (fr) Procédé et système d'émission d'informations pour liaison terrestre, dispositif mandataire et dispositif d'accès
WO2015018232A1 (fr) Procédé et appareil de gestion de connexion de dispositif à dispositif et station de base

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

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

Country of ref document: EP

Kind code of ref document: A1