WO2009018777A1 - Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué - Google Patents

Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué Download PDF

Info

Publication number
WO2009018777A1
WO2009018777A1 PCT/CN2008/071911 CN2008071911W WO2009018777A1 WO 2009018777 A1 WO2009018777 A1 WO 2009018777A1 CN 2008071911 W CN2008071911 W CN 2008071911W WO 2009018777 A1 WO2009018777 A1 WO 2009018777A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
identifier
mme
message
setup request
Prior art date
Application number
PCT/CN2008/071911
Other languages
English (en)
Chinese (zh)
Inventor
Chunxia Zhi
Jinyi Zhou
Huadong Hu
Yijun Yu
Lan Liu
Zhe Chen
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009018777A1 publication Critical patent/WO2009018777A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a technology for establishing bearers in an evolved network.
  • the core network of the evolved network mainly includes three logical function modules: Mobility Management Entity (MME), Monthly Serving Gateway, and Packet Data Gateway (PDN Gateway). .
  • MME Mobility Management Entity
  • PDN Gateway Packet Data Gateway
  • the MME is a mobility management module responsible for mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, security functions, etc., which corresponds to the current Universal Mobile Telecommunications System (UMTS).
  • UMTS Universal Mobile Telecommunications System
  • the control plane part of the Serving GPRS Support Node (SGSG) is the internal service of the system.
  • the Serving Gateway is the endpoint of the evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) and the core network interface. At any point in time, any User Equipment ("UE") in the system is only connected to A Serving Gateway includes the following functions: 1. Anchor points for switching between ENodeB nodes in E-UTRAN; 2. E-UTRAN and UMTS Terrestrial Radio Access Network, referred to as "UTRAN" for the anchor point to switch; 3, lawful interception.
  • E-UTRAN evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network
  • UTRAN UMTS Terrestrial Radio Access Network
  • the PDN Gateway is the endpoint of the SGi interface that provides access to the PDN service.
  • the main functions include: 1. Policy control; 2. Service data flow filtering; 3. Billing; 4. Lawful interception.
  • the locations of the two logical functional modules of the Serving Gateway and the PDN Gateway in Figure 1 have not yet been determined. They may be combined in one physical entity or as two separate physical entities.
  • a bearer identifier is generally used to identify a bearer of the UE.
  • the inventors of the present invention have found that, at present, there is no specific method for allocating and transmitting bearer identifiers in an evolved network. If there is no assignment and transmission of bearer identifiers, the bearers cannot be successfully established and used.
  • an EPS bearer identity is defined to identify an EPS bearer of the UE. In the existing EPS standard protocol, the specific method of allocation and transmission of EPS bearer identity is lacking. If there is no allocation and transmission of EPS bearer identity, EPS bearer cannot be successfully established and used.
  • the main technical problem to be solved by the embodiments of the present invention is to provide a method and device for allocating and transmitting bearer identifiers in an evolved network, so that the bearers can be successfully established and used.
  • an embodiment of the present invention provides a method for allocating and transmitting bearer identifiers in an evolved network, including the following steps:
  • a bearer identifier is allocated for the newly created bearer; in the bearer setup process, the bearer identifier is provided to each physical device related to the bearer.
  • Embodiments of the present invention also provide a bearer identity allocation and delivery device in an evolved network, including:
  • a transmitting unit configured to provide the bearer identifier to each physical device associated with the bearer in a bearer setup process.
  • the bearer identifier is allocated by the entity device such as the MME, and the allocated bearer identifier is sent to each entity device related to the newly created bearer in the bearer establishment process, so that the established and successfully used in the evolved network can be successfully established and used. Loaded.
  • FIG. 1 is a schematic diagram of a 3GPP evolved network architecture in the prior art
  • 2 is a flowchart of a method for allocating and transmitting bearer identifiers in an evolved network according to a first embodiment of the present invention
  • 3 is a flowchart of a method for allocating and transmitting bearer identifiers in an evolved network according to a second embodiment of the present invention
  • FIG. 4 is a flow chart of a method for allocating and transmitting bearer identifiers in an evolved network according to a third embodiment of the present invention.
  • FIG. 5 is a flow chart showing a method for allocating and transmitting an identifier of an evolved network in a fourth embodiment of the present invention.
  • FIG. 6 is a flow chart of a method for allocating and transmitting bearer identifiers in an evolved network according to a fifth embodiment of the present invention.
  • FIG. 7 is a flow chart of a method for allocating and transmitting bearer identifiers in an evolved network according to a sixth embodiment of the present invention.
  • FIG. 8 is a flow chart of a method for allocating and transmitting bearer identifiers in an evolved network according to a seventh embodiment of the present invention.
  • FIG. 9 is a flow chart of a method for allocating and transmitting bearer identifiers in an evolved network according to an eighth embodiment of the present invention.
  • FIG. 10 is a flow chart showing a method for allocating and transmitting a tag in an evolved network in a ninth embodiment of the present invention.
  • FIG. 11 is a flow chart of a method for allocating and transmitting bearer identifiers in an evolved network according to a tenth embodiment of the present invention.
  • FIG. 13 is a flowchart of a method for allocating and transmitting bearer identifiers in an evolved network according to a twelfth embodiment of the present invention
  • 16 is a flowchart of a method for allocating and transmitting bearer identifiers in an evolved network according to a fifteenth embodiment of the present invention.
  • 17 is a method for allocating and transmitting bearer identifiers in an evolved network according to a sixteenth embodiment of the present invention.
  • Figure 19 is a flow chart showing a method for allocating and transmitting bearer identifiers in an evolved network in an eighteenth embodiment of the present invention.
  • An embodiment of the present invention provides a method for allocating and transmitting bearer identifiers in an evolved network, including the following steps:: assigning a bearer identifier to a newly created bearer; and providing, in a bearer setup process, the bearer identifier to the newly created bearer Individual physical devices.
  • the execution subject that allocates the bearer identifier and provides the bearer identifier to each entity device related to the newly created bearer is an MME.
  • the bearer identifier that is allocated by the MME to the newly-created bearer may be a bearer identifier that is pre-configured on the MME, or may be an unused bearer identifier that is randomly allocated by the MME.
  • a bearer is established when the UE attaches (Attach), and the flow thereof is shown in FIG. 2, and the description of each step is as follows:
  • the UE performs the process steps of the network attachment.
  • the process steps may be the same as the process steps involved in the prior art, and are not described here.
  • the MME allocates an EPS bearer identity, and sends a bearer setup request message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the PDN GW, where the message carries an EPS bearer identity, and the PDN GW saves the received EPS bearer identity.
  • the PDN GW interacts with the Policy Control and Charging Rules Function (PCRF) to obtain the related policy and charging control (PCC) policy information.
  • PCRF Policy Control and Charging Rules Function
  • PCC policy and charging control
  • the PDN GW sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the MME.
  • the MME sends an attach accept message to the eNodeB, where the message carries the assigned EPS bearer identity, and the eNodeB saves the EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries an EPS bearer identity, and the UE saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends an attach complete message to the MME.
  • the above steps 17 and 18 function to transmit the EPS bearer identity from the MME to the UE.
  • at least three specific schemes can be used:
  • the EPS bearer identity may be carried in an Information Element ("IE") of a Non-Access Stratum (“NAS”) message, sent by the MME to the eNodeB, and then transmitted by the eNodeB. Passed to the UE.
  • IE Information Element
  • NAS Non-Access Stratum
  • the EPS bearer identity may be carried in the IE of the protocol message between the MME and the eNodeB, and then transmitted to the eNodeB, and then carried in the IE of the protocol message between the eNodeB and the UE to the UE.
  • one of the above three schemes may be used if it involves transmitting an EPS bearer identity from the MME to the UE.
  • the MME initiates a bearer setup procedure by the UE.
  • the description of each step is as follows:
  • the UE sends a bearer setup request message to the MME, where the message carries a Transaction Identifier (""," and may also carry other associated identifiers (optional).
  • the MME sends a bearer setup request message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the PDN GW, where the message carries an EPS bearer identity, and the PDN GW saves the EPS bearer identity. 5.
  • the PDN GW interacts with the PCRF to obtain related PCC policy information. This step is optional.
  • the PDN GW sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the MME.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the assigned EPS bearer identity and the ⁇ or associated identifier (optional) received and saved by the MME in step 1 of the process.
  • the eNodeB saves the received EPS bearer identity
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity and the TI or association identifier (optional) received by the eNodeB in step 8.
  • the UE associates the received radio bearer setup request message with the TI or association identifier to the bearer setup request message (optional) sent to the MME in step 1, and saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer update request message to the Serving GW.
  • the Serving GW sends a bearer update response message to the MME.
  • the PDN GW is triggered by the UE to initiate a bearer setup process. As shown in FIG. 4, the description of each step is as follows:
  • the UE sends a bearer setup request message to the MME, where the message carries the TI, and may also carry other associated identifiers. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry linked TI (associated processing identifier). According to the linked TI, the related information of the built bearer can be found, which reduces the information that needs to be sent in the bearer setup request message.
  • TI associated processing identifier
  • the MME sends a bearer setup request message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity. According to the linked EPS bearer identity, the related information of the built bearer can be found, which reduces the information that needs to be sent in the bearer setup request message.
  • the linked EPS bearer identity is similar to that of Linked TI, except that it is customary to use linked EPS bearer identity between ⁇ and Serving GW, and use linked ⁇ between MME and UE.
  • the Serving GW sends a bearer setup request message to the PDN GW, where the message carries an EPS bearer identity, and the PDN GW saves the EPS bearer identity. If this process is used to establish to the same PDN The non-first bearer, the message also needs to carry the linked EPS bearer identity.
  • the PDN GW interacts with the PCRF to obtain the relevant PCC decision. This step is optional.
  • the PDN GW sends a bearer setup request message to the Serving GW, where the message carries the EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the MME, where the message carries the EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the assigned EPS bearer identity and the ⁇ or associated identifier received and saved by the MME in step 1 of the process, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity and the TI or association identifier received by the eNodeB in the step, and the UE saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the PDN GW.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • the PDN GW is triggered by the UE to initiate a bearer setup procedure. As shown in FIG. 5, the description of each step is as follows:
  • the UE sends a bearer setup request message to the MME, where the message carries the TI, and may also carry other associated identifiers.
  • the MME sends a bearer setup request message to the Serving GW.
  • the message may need to carry a correlation identifier (for example: Corr-ID), and the Serving GW saves the corresponding association identifier.
  • the Serving GW sends a bearer setup request message to the PDN GW.
  • the message may need to carry an association identifier (for example: Corr-ID), and the PDN GW saves the corresponding association identifier.
  • the PDN GW interacts with the PCRF to obtain the relevant PCC decision. This step is optional.
  • the PDN GW sends a bearer setup request message to the Serving GW. If the PDN GW receives the association identifier in step 3, the message carries the corresponding association identifier. If this process is used to build To establish a non-first bearer of the same PDN, the message also needs to carry the linked EPS bearer identity tanta
  • the Serving GW sends a bearer setup request message to the MME. If the Serving GW receives the association identifier in step 2, the message carries the corresponding association identifier. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity tanta
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the assigned EPS bearer identity and the ⁇ or associated identifier received and saved by the MME in step 1 of the process, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity and the TI or association identifier received by the eNodeB in the step, and the UE saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message may also need to carry the linked EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the EPS bearer identity. If the bearer setup request and response message binding are required, the linked EPS bearer identity saved by the MME in step 6 needs to be passed.
  • the Serving GW sends a bearer setup response message to the PDN GW, where the message carries the EPS bearer identity, and the PDN GW stores the EPS bearer identity. If you need to do bearer setup request and response message binding, you need to pass the linked EPS bearer identity saved by Serving GW in step 5.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • steps 7 and 8 may or may not be the same as the Corr-ID mentioned in steps 2 and 3.
  • the bearer establishment process is initiated by the PDN GW.
  • the description of each step is as follows: 1.
  • the PCRF sends the relevant PCC decision to the PDN GW. This step is optional.
  • the PDN GW sends a bearer setup request message to the Serving GW. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity, and the Serving GW saves the linked EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the MME. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity, and the MME saves the linked EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the assigned EPS bearer identity, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity, and the UE saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW, where the message carries the EPS bearer identity, and the Serving GW saves the received EPS bearer identity. If the bearer setup request and response message binding are required, the linked EPS bearer identity saved by the MME in step 3 needs to be passed.
  • the Serving GW sends a bearer setup response message to the PDN GW, where the message carries the EPS bearer identity, and the PDN GW saves the received EPS bearer identity. If you need to do bearer setup request and response message binding, you need to pass the linked EPS bearer identity saved by Serving GW in step 2.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • the EPS bearer identity is assigned by the MME.
  • the following describes an implementation manner in which the EPS bearer identity is allocated by the PDN GW.
  • the bearer establishment process is triggered by the UE at the time of attaching.
  • the description of each step is as follows: 1-11.
  • the process steps of the network attaching to the UE, and the process steps may be the same as the process steps involved in the prior art, and details are not described herein again.
  • the MME sends a bearer setup request message to the Serving GW, where the message may need to carry an association identifier (for example: Corr-ID), and the Serving GW saves the corresponding association identifier.
  • an association identifier for example: Corr-ID
  • the Serving GW sends a bearer setup request message to the PDN GW.
  • the message may need to carry an association identifier (for example: Corr-ID), and the PDN GW saves the corresponding association identifier.
  • the PDN GW interacts with the PCRF to obtain related PCC policy information. This step is optional.
  • the PDN GW allocates an EPS bearer identity, and sends a bearer setup response message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the received message.
  • the PDN GW receives the association identifier in step 13, the message also carries the corresponding association identifier.
  • the Serving GW sends a bearer setup response message to the MME, where the message carries the EPS bearer identity, and the MME saves the received EPS bearer identity. If the Serving GW receives the association identifier in step 12, the message also carries the corresponding association identifier.
  • the MME sends an attach accept message to the eNodeB, where the message carries the assigned EPS bearer identity, and the eNodeB saves the EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries an EPS bearer identity, and the UE saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends an attach complete message to the MME.
  • the MME initiates a bearer setup procedure by the UE. As shown in FIG. 8, the description of each step is as follows:
  • the UE sends a bearer setup request message to the MME, where the message carries the TI, and may also carry other associated identifiers.
  • the MME saves the received TI or association identifier and performs GW selection at the same time.
  • the MME sends a bearer setup request message to the Serving GW, and the message may need to carry an association identifier (for example, Corr-ID), and the Serving GW saves the corresponding association identifier.
  • the Serving GW sends a bearer setup request message to the PDN GW.
  • the message may need to carry an association identifier (for example: Corr-ID), and the PDN GW saves the corresponding association identifier.
  • the PDN GW interacts with the PCRF to obtain related PCC policy information. This step is optional.
  • the PDN GW allocates an EPS bearer identity, and sends a bearer setup response message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the received message.
  • the PDN GW receives the association identifier in step 4, the message also carries the corresponding association identifier.
  • the Serving GW sends a bearer setup response message to the MME, where the message carries the EPS bearer identity, and the MME saves the received EPS bearer identity. If the Serving GW receives the association identifier in step 3, the message also carries the corresponding association identifier.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the assigned EPS bearer identity and the ⁇ or associated identifier received and saved by the MME in step 1 of the process.
  • eNodeB saves the address: to the EPS bearer identity
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity and the TI or association identifier received by the eNodeB in step 8.
  • the UE associates the received radio bearer setup request message with the bearer setup request message sent to the MME in step 1 according to the TI or association identifier, and saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends an update request message to the Serving GW.
  • the Serving GW sends a bearer update response message to the MME.
  • the PDN GW is triggered by the UE to initiate a bearer setup process. As shown in FIG. 9, the description of each step is as follows:
  • the UE sends a bearer setup request message to the MME, where the message carries the TI, and may also carry other associated identifiers. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry linked ⁇ .
  • the MME sends a bearer setup request message to the Serving GW, where the message carries an association identifier (for example: Corr-ID), and the Serving GW saves the corresponding association identifier. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity. 3.
  • the Serving GW sends a bearer setup request message to the PDN GW, where the message carries an association identifier (for example: Corr-ID), and the PDN GW saves the corresponding association identifier. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the PDN GW interacts with the PCRF to obtain the relevant PCC decision. This step is optional.
  • the PDN GW allocates an EPS bearer identity, and sends a bearer setup request message to the Serving GW, where the message carries the assigned EPS bearer identity and the association identifier received by the PDN GW in step 3.
  • the Serving GW saves the received EPS bearer identity. .
  • the Serving GW sends a bearer setup request message to the MME, where the message carries the EPS bearer identity and the association identifier received by the Serving GW in step 2.
  • the MME stores the received EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the assigned EPS bearer identity and the ⁇ or associated identifier received and saved by the MME in step 1 of the process, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity and the TI or association identifier received by the eNodeB in the step, and the UE saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the PDN GW.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • the bearer establishment process is initiated by the PDN GW.
  • the description of each step is as follows:
  • the PCRF sends the relevant PCC decision to the PDN GW. This step is optional.
  • the PDN GW allocates an EPS bearer identity, and sends a bearer setup request message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity. 3.
  • the Serving GW sends a bearer setup request message to the MME, where the message carries an EPS bearer identity, and the MME saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the EPS bearer identity, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity, and the UE saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the PDN GW.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • the following describes various embodiments in which the Serving GW allocates an EPS bearer identity.
  • the UE initiates a bearer setup procedure when attaching, as shown in FIG. 11, the description of each step is as follows:
  • the UE performs the process steps of the network attachment.
  • the process steps may be the same as the process steps involved in the prior art, and are not described here.
  • the MME sends a bearer setup request message to the Serving GW, where the message may need to carry an association identifier (for example: Corr-ID), and the Serving GW saves the corresponding association identifier.
  • an association identifier for example: Corr-ID
  • the Serving GW allocates an EPS bearer identity, and sends a bearer setup request message to the PDN GW, where the message carries the assigned EPS bearer identity, and the PDN GW saves the received EPS bearer identity.
  • the PDN GW interacts with the PCRF to obtain related PCC policy information. This step is optional.
  • the PDN GW sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the MME, where the message carries an EPS bearer identity, and the MME saves the received EPS bearer identity. If Serving GW is in step 12 If the association identifier is received, the corresponding association identifier needs to be carried in the message.
  • the MME sends an attach accept message to the eNodeB, where the message carries the assigned EPS bearer identity, and the eNodeB saves the EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries an EPS bearer identity, and the UE saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends an attach complete message to the MME.
  • the MME initiates a bearer setup procedure by the UE. As shown in FIG. 12, the description of each step is as follows:
  • the UE sends a bearer setup request message to the MME, where the message carries the TI, and may also carry other associated identifiers.
  • the MME saves the received TI or association identifier and performs GW selection at the same time.
  • the MME sends a bearer setup request message to the Serving GW.
  • the message may need to carry a correlation identifier (for example: Corr-ID), and the Serving GW saves the corresponding association identifier.
  • the Serving GW allocates an EPS bearer identity, and sends a bearer setup request message to the PDN GW, the message carries the assigned EPS bearer identity, and the PDN GW saves the received EPS bearer identity.
  • the PDN GW interacts with the PCRF to obtain related PCC policy information. This step is optional. 6.
  • the PDN GW sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the MME, where the message carries the EPS bearer identity, and the MME saves the received EPS bearer identity. If the Serving GW receives the association identifier in step 3, the message also carries the corresponding association identifier.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the assigned EPS bearer identity and the ⁇ or associated identifier received and saved by the MME in step 1 of the process, and the eNodeB saves the EPS bearer identity cr
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity and the TI or association identifier received by the eNodeB in step 8.
  • the UE saves the received EPS bearer identity. 10.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer update request message to the Serving GW.
  • the Serving GW sends a bearer update response message to the MME.
  • the PDN GW is triggered by the UE to initiate a bearer setup process. As shown in FIG. 13, the description of each step is as follows:
  • the UE sends a bearer setup request message to the MME, where the message carries the TI, and may also carry other associated identifiers. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry linked ⁇ .
  • the message carries an association identifier (for example: Corr-ID), and the Serving GW saves the corresponding association identifier. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • an association identifier for example: Corr-ID
  • the Serving GW allocates an EPS bearer identity, and sends a bearer setup request message to the PDN GW, the message carries the assigned EPS bearer identity, and the PDN GW saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the PDN GW interacts with the PCRF to obtain the relevant PCC decision. This step is optional.
  • the PDN GW sends a bearer setup request message to the Serving GW, where the message carries the assigned EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the MME, where the message carries the EPS bearer identity and the association identifier received by the Serving GW in step 2.
  • the MME stores the received EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the EPS bearer identity and the TI or association identifier received and saved by the MME in step 1 of the process, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity and the TI or association identifier received by the eNodeB in the step, and the UE saves the received EPS bearer identity. 9.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the PDN GW.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • the bearer establishment process is initiated by the PDN GW, as shown in FIG. 14, and the steps are as follows:
  • the PCRF sends the relevant PCC decision to the PDN GW. This step is optional.
  • the PDN GW sends a bearer setup request message to the Serving GW. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity tanta
  • the Serving GW allocates the EPS bearer identity, and sends a bearer setup request message to the MME.
  • the message carries the assigned EPS bearer identity, and the MME saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the EPS bearer identity, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity, and the UE saves the received EPS bearer identity. If this process is used to build to the same
  • the message also needs to carry the linked EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the PDN GW, where the message carries the assigned EPS bearer identity, and the PDN GW saves the received EPS bearer identity. If you need to do bearer setup request and response message binding, you need to pass the linked EPS bearer identity saved by Serving GW in step 2.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • Various embodiments in which an EPS bearer identity is allocated by a UE are described below.
  • the bearer establishment process is triggered when the UE is attached, as shown in FIG. 15, the description of each step is as follows:
  • the UE performs the process steps of the network attachment.
  • the process steps may be the same as the process steps involved in the prior art, and are not described here.
  • the MME sends a bearer setup request message to the Serving GW, where the message carries the assigned EPS bearer identity, and the Serving GW saves the EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the PDN GW, where the message carries an EPS bearer identity, and the PDN GW saves the received EPS bearer identity.
  • the PDN GW interacts with the PCRF to obtain related PCC policy information. This step is optional.
  • the PDN GW sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the MME.
  • the MME sends an attach accept message to the eNodeB, where the message carries the assigned EPS bearer identity, and the eNodeB saves the received EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries an EPS bearer identity, and the UE saves the received EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends an attach complete message to the MME.
  • the MME initiates a bearer setup procedure by the UE. As shown in FIG. 16, the description of each step is as follows:
  • the UE allocates an EPS bearer identity, and sends a bearer setup request message to the MME, where the message carries the assigned EPS bearer identity, and the MME saves the received EPS bearer identity.
  • the MME performs GW selection.
  • the MME sends a bearer setup request message to the Serving GW, where the message carries the EPS bearer identity, and the Serving GW saves the EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the PDN GW, where the message carries an EPS bearer identity, and the PDN GW saves the EPS bearer identity. 5.
  • the PDN GW interacts with the PCRF to obtain related PCC policy information. This step is optional.
  • the PDN GW sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the MME.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the EPS bearer identity, and the eNodeB saves the received EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a 7-load update request message to the Serving GW.
  • the Serving GW sends a bearer update response message to the MME.
  • the PDN GW is triggered by the UE to initiate a bearer setup process. As shown in FIG. 17, the description of each step is as follows:
  • the UE allocates an EPS bearer identity, and sends a bearer setup request message to the MME, where the message carries the assigned EPS bearer identity, and the MME saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the MME sends a bearer setup request message to the Serving GW, where the message carries the EPS bearer identity, and the Serving GW saves the EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the PDN GW, where the message carries the EPS bearer identity, and the PDN GW saves the EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the PDN GW interacts with the PCRF to obtain the relevant PCC decision. This step is optional.
  • the PDN GW sends a bearer setup request message to the Serving GW, where the message carries the EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the MME, where the message carries the EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the EPS bearer.
  • Identity eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries the EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the PDN GW.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • the bearer establishment process is initiated by the PDN GW.
  • the description of each step is as follows:
  • the PCRF sends the relevant PCC decision to the PDN GW. This step is optional.
  • the PDN GW sends a bearer setup request message to the Serving GW. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity tanta
  • the Serving GW sends a bearer setup request message to the MME. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the MME sends a 7-layer setup request message to the eNodeB. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the UE allocates an EPS bearer identity, and sends a wireless bearer setup response message to the eNodeB, where the message carries the assigned EPS bearer identity, and the eNodeB saves the received EPS bearer identity. If the bearer setup request and response message binding are required, the linked EPS bearer identity saved by the UE in step 5 needs to be transmitted.
  • the eNodeB sends a bearer setup response message to the MME, where the message carries the EPS bearer identity, and the MME saves the received EPS bearer identity. If a bearer setup request and response message binding are required, the linked EPS bearer identity saved by the eNodeB in step 4 needs to be passed.
  • the MME sends a bearer setup response message to the Serving GW, where the message carries an EPS bearer.
  • Identity Serving GW saves the received EPS bearer identity. If you need to do bearer setup request and response message binding, you need to pass the linked EPS bearer identity saved by MME in step 3.
  • the Serving GW sends a bearer setup response message to the PDN GW, where the message carries the EPS bearer identity, and the PDN GW saves the received EPS bearer identity. If you need to do bearer setup request and response message binding, you need to pass the linked EPS bearer identity saved by Serving GW in step 2.
  • the PDN GW sends a PCC decision confirmation message to the PCRF. This step is optional.
  • the bearer establishment process is initiated by the PDN GW. As shown in FIG. 19, the description of each step is as follows:
  • the UE performs an application layer quality of service (QoS) negotiation between the application function and the application function (AF).
  • QoS quality of service
  • the UE sends the assigned EPS bearer identity to the control signaling message. AF.
  • the AF sends the QoS related information of the application layer to the PCRF, and the message carries the EPS bearer identity.
  • the PCRF sends the relevant PCC decision to the PDN GW, and the message carries the EPS bearer identity
  • the PDN GW sends a bearer setup request message to the Serving GW, where the message carries the EPS bearer identity, and the Serving GW saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the Serving GW sends a bearer setup request message to the MME, where the message carries the EPS bearer identity, and the MME saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the MME sends a bearer setup request message to the eNodeB, where the message carries the EPS bearer identity, and the eNodeB saves the received EPS bearer identity. If this process is used to establish a non-first bearer to the same PDN, the message also needs to carry the linked EPS bearer identity.
  • the eNodeB sends a radio bearer setup request message to the UE, where the message carries an EPS bearer identity, and the UE saves the received EPS bearer identity. If this process is used to build to the same If the PDN is not the first bearer, the message also needs to carry the linked EPS bearer identity.
  • the UE sends a radio bearer setup response message to the eNodeB.
  • the eNodeB sends a bearer setup response message to the MME.
  • the MME sends a bearer setup response message to the Serving GW.
  • the Serving GW sends a bearer setup response message to the PDN GW.
  • the PDN GW sends a PCC decision confirmation message to the PCRF.
  • the first NAS message sent by the UE to the MME carries information related to bearer establishment (for example, an Access Point Name (APN)), and carries one at the same time.
  • APN Access Point Name
  • TI for NAS messages.
  • the EPS bearer identity assigned by the network side is sent to the UE through the bearer setup request message through the eNodeB.
  • the message sent by the eNodeB to the UE is not a NAS message.
  • the MME sends the message.
  • the bearer setup request message sent to the eNodeB and the eNodeB to the UE needs to carry the relevant identifier to identify that the message is associated with the first message. For example, TI in the NAS message can be directly used as the association identifier, or a new parameter can be redefined to identify it. If the parameter is redefined, the parameter needs to be carried in the first NAS message sent by the UE to the MME.
  • the association identifier can be sent to the UE through the eNodeB, and can also be sent to the UE as an IE of the S1-AP and the air interface protocol message.
  • the bearer setup message sent by the PDN GW to the Serving GW and the Serving GW to the MME does not carry the EPS bearer identity, because the MME has not allocated yet.
  • the corresponding EPS bearer identity For how the subsequent bearer setup response message is bound to the bearer setup request message, there are different methods from different levels. If only the bearer layer is bound, the binding of a pair of request and response messages can be implemented by the sequence number in the existing GPRS Tunneling Protocol (GTP) header. If you need to do binding on the bearer layer, you need to introduce a new association parameter (for example: Corr-ID) to implement the request. Binding to the response message.
  • GTP GPRS Tunneling Protocol
  • the bearer establishment request message sent by the MME to the Serving GW and the Serving GW to the PDN GW does not carry the EPS bearer identity, because the PDN GW also The corresponding EPS bearer identity is not assigned. Therefore, there are also two levels of binding problems between request messages and response messages.
  • the bearer setup request message sent by the MME to the Serving GW and the Serving GW to the PDN GW needs to carry an association identifier (for example: Corr-ID or EPS bearer identity, etc., and the messages returned by the subsequent PDN GW and Serving GW carry the same association identifier, which is used for binding between different messages.
  • an association identifier for example: Corr-ID or EPS bearer identity, etc.
  • the messages returned by the subsequent PDN GW and Serving GW carry the same association identifier, which is used for binding between different messages.
  • the sequence number of the GTP header can no longer be used because the sequence number of the returned message may not be the same as the sequence number of the request message.
  • the bearer setup procedure initiated by the UE When the bearer setup procedure initiated by the UE is used to establish a dedicated bearer, the linked EPS bearer identity and linked TI need to be carried in the corresponding signaling message.
  • the bearer establishment process initiated by the network side is generally used to establish a dedicated bearer, so it is necessary to carry the linked EPS bearer identity in the corresponding signaling message.
  • the linked EPS bearer identity may be an EPS bearer identity carried by any one of the established bearers (the UE to the same PDN).
  • the embodiment of the present invention further provides a bearer identifier allocation and transmission device in an evolved network, including: a bearer identifier allocation unit, configured to allocate a bearer identifier for a newly created bearer; In the bearer establishment process, the bearer identifier is provided to each physical device related to the newly created bearer.
  • the bearer identity allocation and transmission device in the evolved network is set in the MME.
  • a nineteenth embodiment of the present invention relates to an MME, where the MME includes, in addition to the functional units specified by the current standard protocol, the following:
  • An identifier allocation unit for allocating a 7-load identifier for the newly created 7-load
  • the transmitting unit is configured to carry the bearer identifier in the message of the bearer establishment process, and send the information to each entity device (including the UE, the eNodeB, the Serving GW, the PDN GW, and the like) related to the bearer.
  • entity device including the UE, the eNodeB, the Serving GW, the PDN GW, and the like
  • MME For a specific interaction process between the transmission unit and the physical device such as the UE, the eNodeB, the Serving GW, and the PDN GW, refer to the related description in the first to fifth embodiments of the present invention.
  • the twentieth embodiment of the present invention relates to a Serving GW, which includes, in addition to the functional units specified by the current standard protocol, the following:
  • the transmitting unit is configured to carry the bearer identifier in the message of the bearer establishment process, and send the information to each entity device (including the UE, the eNodeB, the MME, the PDN GW, and the like) related to the bearer.
  • entity device including the UE, the eNodeB, the MME, the PDN GW, and the like
  • the specific interaction process of the Serving GW by the transmission unit with the physical device such as the UE, the eNodeB, the MME, the PDN GW, and the like, refer to the related description in the sixth to ninth embodiments of the present invention.
  • the twenty-first embodiment of the present invention relates to a PDN GW, which includes, in addition to the functional units specified by the current standard protocol, the following:
  • An identifier allocation unit for allocating a 7-load identifier for the newly created 7-load
  • the transmitting unit is configured to carry the bearer identifier in the message of the bearer establishment process, and send the information to each entity device (including the UE, the eNodeB, the MME, the Serving GW, and the like) related to the bearer.
  • entity device including the UE, the eNodeB, the MME, the Serving GW, and the like
  • the specific interaction process between the PDN GW and the physical device such as the UE, the eNodeB, the MME, and the Serving GW by the transmission unit is referred to the related description in the tenth to thirteenth embodiments of the present invention.
  • a twenty-second embodiment of the present invention relates to a UE, where the UE includes, in addition to the functional units specified by the current standard protocol, the following:
  • An identifier allocation unit for allocating a 7-load identifier for the newly created 7-load
  • a transmitting unit configured to carry the bearer identifier in a message of the bearer establishment process, and send the information to each entity device (including an eNodeB, the MME, the Serving GW, the PDN GW, and the like) related to the bearer.
  • entity device including an eNodeB, the MME, the Serving GW, the PDN GW, and the like.
  • the bearer identifier is allocated by the entity device such as the MME, and the assigned bearer identifier is sent to each entity device related to the newly created bearer in the bearer establishment process, so that the evolved network The bearer can be successfully established and used. Further, since the allocated bearer identifier can be carried in the bearer establishment process, there is no need to add a new message, and the existing EPS protocol can be better compatible.
  • association identifier is carried in the message sent and received by some entities. Binding of related messages can be achieved.
  • the carried EPS bearer identity is used to refer to some related information, which can reduce the amount of information that needs to be transmitted in the message.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Abstract

L'invention concerne un procédé de distribution et de transfert de l'identité de support dans un réseau évolué consistant à distribuer l'identité de support pour le support nouvellement créé; fournir l'identité de support au dispositif d'entité corrélé au support nouvellement créé dans la procédure de création du support. L'invention concerne aussi un appareil de distribution et de transfert de l'identité de support dans le réseau évolué.
PCT/CN2008/071911 2007-08-08 2008-08-07 Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué WO2009018777A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007100757134A CN101365159B (zh) 2007-08-08 2007-08-08 承载标识处理方法及设备
CN200710075713.4 2007-08-08

Publications (1)

Publication Number Publication Date
WO2009018777A1 true WO2009018777A1 (fr) 2009-02-12

Family

ID=40340968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/071911 WO2009018777A1 (fr) 2007-08-08 2008-08-07 Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué

Country Status (2)

Country Link
CN (1) CN101365159B (fr)
WO (1) WO2009018777A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101605353B (zh) 2008-06-13 2012-08-29 上海华为技术有限公司 一种数据通讯方法及通讯系统以及相关装置
CN101873716B (zh) * 2009-04-27 2013-02-13 电信科学技术研究院 一种家庭网络或本地网络的承载建立方法和系统
CN101730075B (zh) * 2009-06-24 2013-08-07 中兴通讯股份有限公司 一种切换过程中数据前转的方法
CN101959209B (zh) * 2009-07-16 2014-06-11 中兴通讯股份有限公司 一种部分故障处理的同步方法和系统
CN102271405B (zh) * 2010-06-04 2014-09-10 中兴通讯股份有限公司 一种承载资源分配方法及装置
CN103975642B (zh) * 2012-11-22 2018-08-21 华为技术有限公司 一种短距离通信的方法、设备和系统
WO2018081984A1 (fr) 2016-11-03 2018-05-11 Qualcomm Incorporated Supports multiples pour une application
CN108924824B (zh) * 2017-03-20 2020-10-09 电信科学技术研究院 一种eps承载标识的分配方法、装置、smf及pcf
WO2019213905A1 (fr) * 2018-05-10 2019-11-14 Oppo广东移动通信有限公司 Procédé et appareil de liaison de flux de données, et support de stockage informatique

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002030137A1 (fr) * 2000-10-06 2002-04-11 Telefonaktiebolaget Lm Ericsson (Publ) Procede et configuration dans un reseau de communication permettant de connecter un reseau d'acces radio gprs a un reseau d'infrastructure umts
CN1567775A (zh) * 2003-07-10 2005-01-19 华为技术有限公司 一种实现分组网络间呼叫承载通道建立的方法
CN1874344A (zh) * 2005-09-05 2006-12-06 华为技术有限公司 有独立承载控制层网络中识别业务流的方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI106172B (fi) * 1998-01-29 2000-11-30 Nokia Networks Oy Menetelmä uudelleenkonfiguroida solukkoradioverkossa yhteys
CN1585508A (zh) * 2003-08-19 2005-02-23 北京三星通信技术研究有限公司 为mbms建立点到点信道时引入新标识的方法
CN100420341C (zh) * 2006-02-14 2008-09-17 华为技术有限公司 一种通信系统发起业务请求时对业务承载的处理方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002030137A1 (fr) * 2000-10-06 2002-04-11 Telefonaktiebolaget Lm Ericsson (Publ) Procede et configuration dans un reseau de communication permettant de connecter un reseau d'acces radio gprs a un reseau d'infrastructure umts
CN1567775A (zh) * 2003-07-10 2005-01-19 华为技术有限公司 一种实现分组网络间呼叫承载通道建立的方法
CN1874344A (zh) * 2005-09-05 2006-12-06 华为技术有限公司 有独立承载控制层网络中识别业务流的方法

Also Published As

Publication number Publication date
CN101365159B (zh) 2011-11-16
CN101365159A (zh) 2009-02-11

Similar Documents

Publication Publication Date Title
US10938601B2 (en) Method and system for setting up a bearer
WO2009018777A1 (fr) Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué
CN113475045A (zh) 基于控制面的时间敏感网络配置
US8391210B2 (en) Radio communication system and radio transmission path control method
JP5189107B2 (ja) 移動体通信ネットワークにおいて、パケットベアラコンテクストのユーザセットを一意に識別及び統一するための仕組み
US20090016344A1 (en) Method and apparatus for controlling bearers of service data flows
WO2009097818A1 (fr) Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur
WO2007087745A1 (fr) Procédé et système pour la mise en oeuvre d'acheminement de données de l'utilisateur itinérant
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
WO2014056445A1 (fr) Procédé, système et contrôleur pour transfert de routage
WO2008089687A1 (fr) Procédé de partage de ressources de réseau, et dispositif et système à cet effet
WO2011134329A1 (fr) Procédé et système pour transmettre des paquets de données de petite taille
WO2009059532A1 (fr) Procédé et dispositif pour exploitation de support
WO2014086280A1 (fr) Procédé, dispositif et système pour traiter un accès d'utilisateur à un réseau sans fil
WO2011026392A1 (fr) Procédé et système d'acquisition de stratégies d’itinéraire
WO2012041073A1 (fr) Procédé et système adaptés pour exécuter un transfert de flux
WO2014166294A1 (fr) Méthode et appareil de sélection de serveur de service de proximité, et méthode et appareil d'inscription d'utilisateur
WO2012126302A1 (fr) Procédé et système prenant en charge la communication simultanée pour un terminal à double mode, à double veille
WO2013174190A1 (fr) Procédé de sélection de routage et élément de réseau fonctionnel
KR20150001251A (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
WO2010051696A1 (fr) Procédé et système de libération d’une ressource radio
WO2007147344A1 (fr) Procédé de restauration de transmission de données de plan d'utilisateur et entité de réseau évolué
WO2011063543A1 (fr) Prévention de surfacturation par enregistrement de volume de données de liaison descendante non envoyées
WO2009097779A1 (fr) Procédé, système et appareil d'accès au réseau fédérateur sae
EP2071778A2 (fr) Procédé d'échange de données pour garantir la qualité de service entre une entité évoluée de noeud-B et de réseau

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

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

Country of ref document: EP

Kind code of ref document: A1