WO2019062794A1 - 一种建立承载的方法及设备 - Google Patents

一种建立承载的方法及设备 Download PDF

Info

Publication number
WO2019062794A1
WO2019062794A1 PCT/CN2018/107833 CN2018107833W WO2019062794A1 WO 2019062794 A1 WO2019062794 A1 WO 2019062794A1 CN 2018107833 W CN2018107833 W CN 2018107833W WO 2019062794 A1 WO2019062794 A1 WO 2019062794A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
bearer
address
request message
plane device
Prior art date
Application number
PCT/CN2018/107833
Other languages
English (en)
French (fr)
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 WO2019062794A1 publication Critical patent/WO2019062794A1/zh

Links

Images

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 application relates to the field of wireless communications technologies, and in particular, to a method and device for establishing a bearer.
  • a new network architecture is proposed.
  • the functions of the base station are divided into two units: a central unit (CU) and a distributed unit (DU).
  • the CU processes the wireless high-layer protocol stack function, for example, a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, and a packet data convergence protocol (PDCP). Layer; etc.;
  • DU handles the physical layer of baseband processing and part of protocol stack functions of layer 2, such as radio link control (RLC) layer, media access control (MAC) layer and physical layer (physical layer, PHY) and so on.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the functions of the CU can be further divided into two parts: a control plane (CU-CP) and a user plane (CU-UP).
  • the CU-CP is used to control the data radio bearer (DRB) establishment, release, and data forwarding operations of the DU and the CU-UP.
  • the protocol layer involved includes the RRC layer and the PDCP layer.
  • the CU-UP is used to perform data service transmission according to the configuration of the CU-CP.
  • the protocol layer involved includes the SDAP layer and the PDCP layer.
  • the CU-CP is responsible for the establishment and release of the DRB. When the DRB corresponding to the data is not successfully established, there is no related solution for how to establish the DRB corresponding to the downlink service data.
  • the embodiment of the present application provides a method and a device for establishing a bearer to establish a data radio bearer corresponding to downlink service data.
  • the embodiment of the present application discloses a method for establishing a bearer, including: when an access network control plane device responds to a first trigger message, sending a first request message to an access network distribution unit device, where the first The request message is used to request the access network distribution unit to establish a first bearer; the access network control plane device receives a first response message sent by the access network distribution unit, and the first response message is responsive to The first request message, the first response message carries a first address, the first address is a first transport layer address corresponding to the first bearer, and the access network control plane device is connected
  • the inbound network user plane device sends a second request message, where the second request message is used to request the access network user plane device to establish the first bearer, where the second request message carries the first address,
  • the first address is used by the access network user plane device to send downlink data to the access network distribution unit device by using the first bearer.
  • the access control device can obtain the address corresponding to the first bearer, so that the downlink data can be sent to the access network distribution unit by using the first bearer.
  • the first trigger message carries a second address
  • the second address is a second transport layer address corresponding to the first bearer
  • the second address is used for the
  • the access network distribution unit device sends uplink data to the access network user plane device by using the first bearer, where the first request message carries the second address.
  • the second address is directly carried in the first trigger message, thereby avoiding obtaining the second address by using other interaction information, thereby saving signaling overhead.
  • the method further includes: the access network control plane device receives a second response message sent by the access network user plane device, and the second response message is responsive to the second Request message.
  • the method further includes: the access network control plane device receives a second response message sent by the access network user plane device, and the second response message is responsive to the second a request message, where the second response message carries a second address, where the second address is a second transport layer address corresponding to the first bearer; and the access network control plane device is connected to the access network
  • the distribution unit device sends a third response message, where the third response message carries the second address, where the second address is used by the access network distribution unit to access the access by using the first bearer
  • the network user plane device sends uplink data.
  • the present application provides a method for establishing a bearer, including: an access network distribution unit device receiving a first request message sent by an access network control plane device; and the access network distribution unit device according to the first request a first bearer, where the first bearer is a bearer between the access network distribution unit device and the access network user plane device; the access network distribution unit device sends the access network control plane device to the access network control plane device a first response message, the first response message is responsive to the first request message, the first response message carries a first address, and the first address is a first transmission corresponding to the first bearer a layer address, where the first address is used by the access network user plane device to send downlink data to the access network distribution unit device by using the first bearer.
  • the first request message carries a second address
  • the second address is a second transport layer address corresponding to the first bearer
  • the second address is used for the
  • the access network distribution unit device sends uplink data to the access network user plane device by using the first bearer.
  • the method further includes: the access network distribution unit device receives a third response message sent by the access network control plane device, where the third response message carries a second address, where The second address is a second transport layer address corresponding to the first bearer, and the second address is used by the access network distribution unit to send the user equipment to the access network through the first bearer. Upstream data.
  • the present application provides a method for establishing a bearer, including: receiving, by a user equipment of an access network, a second request message sent by an access control device, where the second request message carries a first address, where The first address is a first transport layer address corresponding to the first bearer, and the first address is used by the access network user plane device to send downlink data to the access network distribution unit device by using the first bearer.
  • the access network user plane device establishes a first bearer according to the second request message, where the first bearer is a bearer between the access network distribution unit device and the access network user plane device.
  • the method further includes: the access network user plane device sends a first trigger message to the access network control plane device, where the first trigger message carries a second address, The second address is a second transport layer address corresponding to the first bearer, and the second address is used by the access network distribution unit device to the access network user plane device by using the first bearer Sending uplink data; the access network user plane device sends a second response message to the access network control plane device, and the second response message is responsive to the second request message.
  • the method further includes: the access network user plane device sends a second response message to the access network control plane device, and the second response message is responsive to the second request a message, the second response message carries a second address, the second address is a second transport layer address corresponding to the first bearer, and the second address is used by the access network distribution unit device And transmitting uplink data to the access network user plane device by using the first bearer.
  • the present application further provides a method for releasing a bearer, including: when receiving a second trigger message, the access network control plane device sends a first request message to the access network distribution unit device, where the first request is sent.
  • the message is used to request the access network distribution unit to release the first bearer, where the first bearer is used for data exchange between the access network distribution unit device and the access network user plane device, the first request message And carrying the identifier of the first bearer;
  • the access network control plane device sends a second request message to the user equipment of the access network, where the second request message is used to request release of the user plane device of the access network
  • the first bearer, where the second request message carries the identifier of the first bearer.
  • the method further includes: the access network control plane device receiving a first response message sent by the access network distribution unit device, where the first response message is responsive to the first request message
  • the access network control plane device receives a second response message sent by the access network user plane device, and the second response message is responsive to the second request message.
  • the application further provides a method for releasing a bearer, comprising: an access network distribution unit device receiving a first request message sent by an access network control plane device, where the first request message carries a first bearer The first bearer is used for data exchange between the access network distribution unit device and the access network user plane device; the access network distribution unit device releases the first according to the identifier of the first bearer One bearer.
  • the method further includes: the access network distribution unit device transmitting a first response message to the access network control plane device, where the first response message is responsive to the first request Message.
  • the present application further provides a method for releasing a bearer, comprising: receiving, by an access network user plane device, a second request message sent by an access network control plane device, where the second request message carries a first bearer
  • the first bearer is used for data exchange between the access network distribution unit device and the access network user plane device; the access network user plane device releases the first according to the identifier of the first bearer One bearer.
  • the method further includes: the access network user plane device sends a second response message to the access network control plane device, and the second response message is responsive to the second request Message.
  • the application provides a method for switching a bearer, including: a destination access network control plane device sends a first message to a destination access network user plane device; and the destination access network control plane device receives the destination interface a first response message sent by the network access user plane device, where the first response message is in response to the first message, the first response message carries a first address, and the first address is used in a source access network.
  • the user plane device sends forward data to the destination access network user plane device; the destination access network control plane device sends a second message to the source access network control plane device, where the second message carries the first message address.
  • the application provides a method for switching bearers, including:
  • the source access network control plane device receives the second message sent by the destination access network control plane device, where the second message carries a first address, where the first address is used by the source access network user plane device
  • the destination access network control plane device sends forward data
  • the source access network control plane device sends a third message to the source access network user plane device, where the third message carries the first address.
  • the method further includes:
  • the source access network control plane device receives a second response message sent by the source access network user plane device, and the second response message is responsive to the third message.
  • the ninth aspect the application further provides a method for switching bearers, including:
  • the source access network user plane device receives a third message sent by the source access network control plane device, where the third message carries a first address, where the first address is used by the source user plane device to the destination user plane.
  • the device sends forward data;
  • the source user plane device sends forwarding data to the destination user plane device according to the first address, where the forwarding data carries downlink service data to be transferred by the terminal device and processing information of the downlink service data.
  • an embodiment of the present application provides an access network device, which may include a controller/processor, a memory, and a communication unit.
  • the controller/processor may be configured to perform the foregoing method for establishing a bearer, a method for releasing a bearer, or a method for modifying a bearer.
  • the memory can be used to store program code and data for the access network device.
  • the communication unit is configured to support communication between access network devices, for example, the access network device may include an access network control plane device, an access network user plane device, and an access network distribution device, where the communication unit can support Communication between the incoming control plane device and the access network user plane device.
  • the embodiment of the present application provides a communication system, where the system includes the access network device of the foregoing aspect, and may specifically include an access network control plane device, an access network user plane device, and an access network distribution. Equipment, etc.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the access network device, which includes a program designed to perform the above aspects.
  • the embodiment of the present application further provides an apparatus, where the apparatus is connected to a memory, for reading and executing a software program stored in the memory, to implement the method designed by the foregoing method.
  • the first bearer between the CU-UP and the DU can be established, and the second address that is sent by the CU-CP to the CU-UP carries the first address, where the first address
  • the CU-UP sends downlink data to the DU through the first bearer. Therefore, the CU-UP can use the first address to send downlink service data to the DU through the first bearer to implement downlink service data transmission.
  • FIG. 1 to FIG. 3 are schematic diagrams of a network architecture provided by an embodiment of the present application.
  • FIG. 9 are flowcharts of establishing a bearer according to an embodiment of the present application.
  • FIG. 10 to FIG. 12 are flowcharts of releasing a bearer according to an embodiment of the present application.
  • FIG. 13 and FIG. 14 are flowcharts of a handover bearer according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of an access network device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of an access network control plane device according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of an access network distribution unit device according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of a user plane device of an access network according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic block diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 20 is another schematic block diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 21 is still another schematic block diagram of a communication apparatus according to an embodiment of the present application.
  • the communication system can be a variety of radio access technology (RAT) systems, such as, for example, code division multiple access (CDMA), time division multiple access (TDMA), and frequency division. Frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division (SC-FDMA), and other systems.
  • RAT radio access technology
  • CDMA code division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division
  • the term "system” can be replaced with "network”.
  • a CDMA system can implement wireless technologies such as universal terrestrial radio access (UTRA), CDMA2000, and the like. UTRA may include wideband CDMA (WCDMA) technology and other CDMA variant technologies.
  • CDMA2000 can cover the interim standard (IS) 2000 (IS-2000), IS-95 and IS-856 standards.
  • the TDMA system can implement a wireless technology such as a global system for mobile communication (GSM).
  • GSM global
  • An OFDMA system can implement such as evolved universal radio land access (evolved UTRA, E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA And other wireless technologies.
  • UTRA and E-UTRA are UMTS and UMTS evolved versions.
  • the various versions of 3GPP in long term evolution (LTE) and LTE-based evolution are new versions of UMTS that use E-UTRA.
  • the communication system can also be applied to the future-oriented communication technology, and the technical solution provided by the embodiment of the present application is applicable to the communication system including the new communication technology, including the establishment of the bearer.
  • a base station is a device deployed in a radio access network to provide wireless communication functions for a UE.
  • the base station may include various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.
  • the name of a device having a base station function may be different, for example, in an LTE system, an evolved Node B (evolved NodeB, eNB or eNodeB), in the third In a 3rd generation (3G) system, it is called a Node B or the like.
  • a base station for example, in an LTE system, an evolved Node B (evolved NodeB, eNB or eNodeB), in the third In a 3rd generation (3G) system, it is called a Node B or the like.
  • the foregoing apparatus for providing a wireless communication function to a UE is collectively referred to as a base station.
  • the UE may include various handheld devices having wireless communication capabilities, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem.
  • the UE may also be referred to as a mobile station (MS), a terminal, a terminal equipment, and may also include a subscriber unit, a cellular phone, and a smart phone.
  • Phone personal digital assistant
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • a core network (CN) node which is connected to one or more base stations, can control the base station to establish a service bearer.
  • the control node can control the CU-CP to establish a bearer between the CU-UP and the DU, and establish a relationship between the DU and the UE. Hosted.
  • the base station may be a Node B in a UMTS system
  • the core network node may be a network controller.
  • the base station may be a small station
  • the control node may be a macro base station that covers the small station.
  • control node may be a wireless network cross-system cooperative controller or the like
  • base station is a base station in the wireless network, which is not limited in the embodiment of the present application.
  • the device that implements the foregoing function control to establish a bearer is collectively referred to as a CN.
  • CU Central unit
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • CU and CN respectively DU is connected.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • CU and CN respectively DU is connected.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • CU and CN respectively DU is connected.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the CU In the downlink communication link, it is used to receive data from the CN and send it to the DU.
  • the CU has a centralized control function for the DU.
  • devices with CU capabilities may have different names. For convenience of description, devices having CU functions are collectively referred to as access network centralized unit devices.
  • the DU is connected to the CU and the user equipment (UE).
  • the downlink communication link is used to receive data from the CU and send the data to the UE.
  • the data is received from the UE and sent to the CU.
  • devices with DU capabilities may have different names. For convenience of description, devices having DU functions are collectively referred to as access network distribution unit devices.
  • a control plane (CU-CP) is used to control CU-UP and DU for service establishment, release, and data forwarding.
  • the protocols involved include the RRC layer and the PDCP layer.
  • devices with CU-CP functionality may have different names.
  • devices having a CU-CP function are collectively referred to as an access network control plane device.
  • the user plane (CU-UP) is used to transmit service data according to the configuration of the CU-CP. Also, in systems employing different wireless access technologies, devices with CU-UP functionality may have different names. For convenience of description, devices having a CU-UP function are collectively referred to as an access network user plane device.
  • FIG. 3 illustrates a possible communication system of an embodiment of the present application.
  • communication system 300 can include at least base station 30 and UE 31.
  • the functions of the base station 30 can be divided into two units: a central unit (CU) and a distributed unit (DU). As shown in FIG. 4, when the function of the base station 30 is divided into two units, CU and DU, the process of downlink service data transmission is as follows:
  • Step S41 The core network node CN sends the downlink service data to the CU, where the downlink service data carries the quality of service flow (Qos Flow) indication information.
  • Qos Flow quality of service flow
  • Step S42 After receiving the downlink service data, the CU determines whether the data radio bearer (DRB) corresponding to the downlink service data is successful according to the Qos Flow indication information carried in the downlink service data. Established, if successful establishment, step S43 is performed; if not successfully established, step S44 is performed.
  • DRB data radio bearer
  • Step S43 The CU transmits the downlink service data to the DU through the corresponding DRB.
  • Step S44 The CU sends a first bearer setup request to the DU, and sends a DRB setup request to the UE.
  • the first bearer setup request carries the address of the first transport layer of the first bearer allocated by the CU, and the DRB setup request carries the identifier information of the DRB corresponding to the downlink service data.
  • the first bearer setup request message may further carry an RLC layer configuration parameter of the DRB corresponding to the first bearer.
  • the first bearer setup request message may further carry at least one of a MAC layer configuration parameter and a physical layer configuration parameter.
  • the DRB establishment request may further carry at least one of a PDCP layer configuration parameter of the DRB and an RLC layer configuration parameter;
  • At least one of a MAC layer configuration parameter and a physical layer configuration parameter may also be included in the DRB establishment request.
  • the PDCP layer configuration parameter, the RLC layer configuration parameter, the MAC layer configuration parameter, and the physical layer configuration parameter are determined according to the Qos Flow indication information.
  • the first bearer is a bearer corresponding to a DR to a CU, and the first bearer may also be a tunnel.
  • the DRB is a bearer established by the network side (including the CU and the DU) and the UE for transmitting service data.
  • the protocol layer of one DRB may include a physical layer, a MAC layer, an RLC layer, a PDCP layer, a SDAP layer, and the like.
  • a DRB corresponds to one PDCP entity, one RLC entity, a physical layer entity, a MAC entity, and a SDAP entity may be shared by multiple DRBs.
  • Step S45 The DU establishes a first bearer between the CU and the DU according to the first bearer setup request, and sends a first response to the CU, where the first response carries the first bearer allocated by the DU.
  • the first bearer is a part between the CU and the DU corresponding to the DRB.
  • the DU establishes a new RLC layer entity for the DRB, and applies the RLC layer configuration parameter, the MAC layer configuration parameter, and the physical layer configuration parameter.
  • Step S46 The UE establishes the DRB according to the DRB establishment request, and after the DRB is successfully established, sends a second response.
  • the UE establishes a new PDCP layer entity for the DRB, and the RLC layer entity applies the PDCP layer configuration parameter, the RLC layer configuration parameter, the MAC layer configuration parameter, and the physical layer configuration parameter.
  • Step S47 The CU transmits the downlink service data to the UE by using the DRB.
  • the CU may transmit the downlink service data to the DU by using the first bearer, and then transmit the downlink service data to the UE by using the air interface.
  • the functions of the CU can be further divided into two nodes, CU-CP and CU-UP.
  • the downlink service data sent by the core network will first reach the CU-UP, and the CU-CP is responsible for the establishment and release of the service bearer.
  • how to establish and release the bearer is the technical problem to be solved by the present application.
  • the first bearer specifically refers to a bearer between the CU-UP and the DU.
  • the solid line indicates signaling transmission, and the broken line indicates data transmission.
  • the number and types of UEs included in the communication system 300 shown in FIG. 3 are merely exemplary, and the embodiments of the present application are not limited thereto. For example, more UEs that communicate with the base station may be included. For the sake of brevity, they are not described in the drawings. Further, in the communication system 300 shown in FIG. 3, although the base station 30 and the UE 31 are shown, the communication system 300 may not be limited to include the base station 30 and the UE 31, and may also include the CN 32 or for management. The devices that carry the setup, etc., will be apparent to those of ordinary skill in the art and will not be described in detail herein.
  • the application provides a process for establishing a bearer method. As shown in FIG. 5, the process is specifically as follows:
  • Step S51 The CU-CP sends a first request message to the DU in response to the first trigger message, where the first request message is used to request the DU to establish the first bearer.
  • the CU-CP may specifically refer to the first trigger message, and the CU-CP receives the first trigger message, and then sends the first request message to the DU.
  • the first bearer is a bearer corresponding to a radio to data carrier (DRB) corresponding to a DU to a CU-UP, and the first bearer may also be a tunnel.
  • the DRB is a bearer established by the network side (including the CU and the DU) and the UE for transmitting service data.
  • the request for establishing a bearer sent by the CU-CP to the DU may be referred to as a first request message
  • the bearer between the DU and the CU-UP may be referred to as a first bearer
  • the response of the DU to the first request message may be referred to.
  • the message is referred to as a first response message
  • the request sent by the CU-CP to the CU-UP is referred to as a second request message
  • the response message of the CU-UP for the second request message is referred to as a second response message.
  • the first request message may further carry an RLC layer configuration parameter of the DRB corresponding to the first bearer. Further, the first request message may further carry at least one of a MAC layer configuration parameter and a physical layer configuration parameter.
  • Step S52 The DU establishes a first bearer according to the first request message.
  • the process of establishing the first bearer by the DU may be specifically: assigning a transport layer address of the DU side to the first bearer.
  • the transport layer address of the DU side corresponding to the first bearer may be referred to as a first address.
  • the first address is used by the CU-UP to send downlink data to the DU through the first bearer.
  • the DU processes the physical layer and part of the protocol stack functions of the layer 2, such as a radio link control (RLC) layer, a media access control (MAC) layer, and a physical layer. (physical layer, PHY) and so on.
  • the process of establishing the first bearer by the DU further includes: configuring a parameter of the DU side protocol stack corresponding to the DRB corresponding to the first bearer, for example, establishing a new RLC layer entity for the DRB, and applying the RLC layer configuration parameter, MAC layer configuration parameters, as well as physical layer configuration parameters.
  • Step S53 The DU sends a first response message to the CU-CP, where the first response message is in response to the first request message, and the first response message carries the first address.
  • Step S54 The CU-CP sends a second request message to the CU-UP, where the second request message is used to request the CU-UP to establish the first bearer, where the second request message carries the first address.
  • the second request may further carry a PDCP layer configuration parameter of the DRB.
  • Step S55 The CU-UP establishes a first bearer according to the second request.
  • the process of establishing the first bearer by the CU-UP may be specifically: assigning a transport layer address of the CU-UP side to the first bearer.
  • the transport layer address of the CU-UP side corresponding to the first bearer may be referred to as a second address, and the second address is used by the DU to send uplink data to the CU-UP through the first bearer.
  • the CU-UP processes the wireless high-layer protocol stack functions, such as an IP layer, an SDAP layer, and a packet data convergence protocol (PDCP) layer.
  • the process of the CU-UP establishing the first bearer may further include: configuring parameters of the CU-UP side protocol stack corresponding to the DRB corresponding to the first bearer, such as establishing a new PDCP layer entity for the DRB, The PDCP layer configuration parameters, etc.
  • the CU-UP may also first allocate a second address to the first bearer, and when receiving the second request, configure the CU corresponding to the DRB corresponding to the first bearer.
  • the first bearer between the CU-UP and the DU can be established, and the first request is sent by the second request sent by the CU-CP to the CU-UP, the first The address is used by the CU-UP to send downlink data to the DU through the first bearer. Therefore, the CU-UP can use the first address to send downlink service data to the DU through the first bearer to implement downlink service data transmission.
  • the method may further include the step S56: the CU-UP sends a second response to the CU-CP, and the second response is responsive to the second Request message.
  • FIG. 6 is a flowchart of a method for establishing a bearer according to an embodiment of the present disclosure.
  • the process is mainly used by a CU-UP to send a first trigger message to a CU-CP, and the CU-UP is carried in the first trigger message.
  • a bearer is assigned the second address. As shown in Figure 6, the process is specifically as follows:
  • Step S61 The CU-UP sends a first trigger message to the CU-CP, where the first trigger message carries the second address corresponding to the first bearer.
  • the first bearer is a bearer corresponding to a radio to data carrier (DRB) corresponding to a DU to a CU-UP, and the first bearer may also be a tunnel.
  • the DRB is a bearer established by the network side (including the CU and the DU) and the UE for transmitting service data.
  • the CU-UP may allocate a second address to the first bearer in advance.
  • the first trigger message may be specifically a bearer setup request message, such as a DRB setup request message, and the specific name is not limited in the present invention.
  • Step S62 The CU-CP sends a first request message to the DU.
  • Step S63 The DU establishes a first bearer according to the first request message.
  • Step S64 The DU sends a first response message to the CU-CP, where the first response message carries a first address, and the first response message is responsive to the first request message.
  • Step S65 The CU-CP sends a second request message to the CU-UP, where the second request message carries the first address.
  • Step S66 The CU-UP establishes a first bearer according to the second request message.
  • step S67 may further be included, specifically:
  • Step S67 The CU-UP sends a second response message to the CU-CP, and the second response message is responsive to the second request message.
  • the first bearer between the CU-UP and the DU can be established by using the foregoing method, and the DU side obtains the second address that transmits the uplink data by using the first bearer, and the CU-UP side obtains the pass.
  • the first transmission of the first address of the downlink data, the DU and the CU-UP may perform the uplink/downlink data transmission by using the first bearer, and the CU-UP carries the address for the uplink data transmission in the first trigger message, thereby saving Signaling overhead.
  • FIG. 7 is a flowchart of a method for establishing a bearer according to an embodiment of the present disclosure. As shown in FIG. 7, the process may be specifically:
  • Step S71 The CU-CP receives the first trigger message.
  • the first trigger message may be sent by the core network node CN, for example, the first trigger message may be sent by an access and mobility management function (AMF) node.
  • the first trigger message may be a protocol data unit session control resource setup request message, for example, the first touch message may be sent by the CU-UP, for example, the first trigger message may be a radio bearer setup request message, etc.
  • the first trigger message may be sent by another CU-CP.
  • the first trigger message may be a radio resource control recovery request message.
  • Step S72 The CU-CP sends a first request message to the DU.
  • Step S73 The DU establishes a first bearer according to the first request message.
  • Step S74 The DU sends a first response message to the CU-CP, where the first response message carries a first address, and the first response is responsive to the first request message.
  • Step S75 The CU-CP sends a second request message to the CU-UP, where the second request message carries the first address.
  • Step S76 The CU-UP establishes a first bearer according to the second request message.
  • Step S77 The CU-UP sends a second response message to the CU-CP, where the second response message carries the second address in response to the second request message.
  • Step S78 The CU-CP sends a third response message to the DU, where the third response message carries the second address.
  • the first bearer between the CU-UP and the DU can be established by using the foregoing method, and the DU side obtains the second address that transmits the uplink data by using the first bearer, and the CU-UP side obtains the pass.
  • the first transmission of the first address of the downlink data, then the DU and CU-UP sides can perform data communication.
  • the CU-CP first sends a first request message to the DU, and obtains the first request message.
  • the second request message is sent to the CU-UP, and the first response message and the second request message both carry the DU for the first bearer for transmission.
  • the transport layer address of the downlink data also known as the first address.
  • the CU-CP does not send the first request message to the DU first, and then obtains the first address carried in the first response message, and then sends the second request message to the CU-UP.
  • the CU-CP may first send a second request message to the CU-UP, and after obtaining the second address in the second response message for the second request message, the second address is used for the DU.
  • the first bearer sends the uplink data to the CU-UP, and the CU-CP sends the first request message to the CU-UP.
  • the first request message carries the second address.
  • the solution provided by the embodiment of the present application can be applied to the modification of the bearer in addition to the bearer establishment.
  • the function of the foregoing first request message may be specifically: the requesting the DU to modify the current first bearer to the second bearer, where the first address may be specifically allocated by the DU as the second bearer for transmission.
  • the transport layer address of the downlink data, and correspondingly, the function of the second request message may be specifically that the requesting CU-UP modifies the current first bearer to the second bearer, and the second address may be specifically that the CU-UP is the second bearer.
  • the assigned transport layer address used to transmit upstream data is not limited to the specific application scenarios of the present solution, and those skilled in the art can understand that the solutions similar to the technical solutions of the present application are within the protection scope of the present application.
  • the first request message is used to request the DU to establish the first bearer, and the first response.
  • the message is used to respond to the first request message
  • the second request message is used to request the CU-UP to establish a second bearer
  • the second response message is used to respond to the second request message
  • the first address is used by the CU-UP to pass the A bearer sends downlink data to the DU
  • the second address is used by the DU to send uplink data to the CU-UP by using the first bearer.
  • the names of the first request message, the second request message, the first response message, the second response message, the first address, and the second address are not defined.
  • the first request message, the second request message, the first response message, the second response message, the first address, and the second address may have different names, for example, in an application.
  • the first request message may be referred to as an F1 bearer setup message
  • the second request message may be referred to as an E1 bearer setup message
  • the first response message may be referred to as an F1 bearer setup complete message
  • the second response message may be referred to as an E1 bearer setup. Complete the message, etc. Therefore, those skilled in the art may know that the names of the above messages may be different in different scenarios and wireless communication systems, and the present application does not limit the name of the message.
  • the embodiment of the present application provides a process for establishing a bearer, and a protocol data unit session control resource establishment request (PDU SESSION RESOURCE SETCU-UP REQUEST) message may be specifically shown in FIG. 5 and FIG. 6 above.
  • PDU SESSION RESOURCE SETCU-UP REQUEST protocol data unit session control resource establishment request
  • the first bearer corresponds to the DRB between the CU-UP and the DU.
  • the process includes:
  • Step S81 The core network node CN sends a protocol data unit session control resource establishment request (PDU SESSION RESOURCE SETCU-UP REQUEST) message to the CU-CP.
  • PDU SESSION RESOURCE SETCU-UP REQUEST protocol data unit session control resource establishment request
  • the core network device may be specifically a device that implements a session control function, for example, may be specifically an AMF in a fifth generation communication system.
  • the PDU SESSION RESOURCE SETCU-UP REQUEST message may carry a protocol data unit PDU (Storage Resource Setup List IE).
  • the PDU Session Resource Setup List IE further includes a protocol data unit (PDU Session ID IE), and the PDU Session ID IE further includes a protocol data unit session establishment request conversion cell (PDU Session).
  • the PDU Session Setup Request Transfer IE further includes a maximum bit rate corresponding to the PDU Session, a transport layer information, a PDU Session type, and one or more QoS Flow information to be established, where QoS Flow
  • the information includes QoS Flow indication information, QoS Flow level QoS parameters, and Reflective QoS Activation parameters.
  • Step S82 The CU-CP sends a first F1 bearer setup message to the DU.
  • the CU-UP may set parameters that meet the Qos requirements of each QOS Flow based on the QoS Flow related information of the PDU Session carried in the PDU SESSION RESOURCE SETCU-UP REQUEST message, for example, logical channel configuration parameters. , RLC layer configuration parameters, MAC layer configuration parameters, PHY layer configuration parameters, and so on.
  • the first F1 bearer setup message carries a list including a first bearer that needs to be established, and an RLC layer configuration parameter of the DRB corresponding to the first bearer, and at least one of logical channel configuration parameters.
  • An item may also include L1, MAC layer configuration parameters, and UE identification information.
  • the UE identification information may be specifically an identifier of the UE, or may be an application layer identifier (AP ID) for identifying the UE.
  • AP ID application layer identifier
  • Step S83 The DU establishes a first bearer according to the first F1 bearer setup message.
  • Step S84 The DU sends a first response message to the CU-CP, where the first response message is responsive to the first F1 bearer setup message.
  • the first response message carries at least a transport network layer address of the data allocated by the DU and the CU-UP, where the transport network layer address is used by the CU-UP to send downlink data to the DU, where
  • the transport network layer address may be in units of UEs, or may be in units of bearers.
  • the transport layer address assigned by the DU may be referred to as a first address.
  • Step S85 The CU-CP sends a first E1 bearer setup message to the CU-UP.
  • the first E1 bearer setup message includes a list of bearers to be established, and a SDAP layer configuration parameter, a PDCP layer configuration parameter, a first address, and a transport layer between the CU-UP and the core network.
  • An address such as at least one of a transport layer address with the UPF, UE identification information, and the like.
  • the identifier information of the UE may be an identifier of the UE, or may be an application layer identifier (AP ID) used to identify the UE.
  • AP ID application layer identifier
  • the SDAP layer configuration parameter may include a mapping relationship between the QoS Flow and the DRB of the data protocol session (PDU Session). For example, if the PDU Session includes six QoS flows, namely QoS Flow1, QoS Flow2, QoS Flow3, QoS Flow4, QoS Flow5, and QoS Flow6, the mapping relationship between each QoS Flow and DRB can be as follows:
  • QoS Flow1 is mapped to DRB1;
  • QoS Flow2 is mapped to DRB2;
  • QoS Flow3 is mapped to DRB3;
  • QoS Flow4 is mapped to DRB1;
  • QoS Flow6 is mapped to the default DRB
  • the QoS Flow5 does not map any DRB. If the data corresponding to the QoS Flow5 is reached, the SDAP layer of the CU-UP directly triggers the process of sending an E1 bearer setup request to the CU-CP, and establishes the corresponding QoS Flow5. The data of the DRB.
  • the meaning of QoS Flow6 mapping to the default DRB is: If the data corresponding to QoS Flow6 is reached, the SDAP layer of CU-UP directly triggers the process of sending an E1 bearer setup request to the CU-CP, and establishes the data corresponding to QoS Flow6. DRB; or if the data corresponding to QoS Flow6 arrives, the SDAP layer of CU-UP will hand over the new data to the PDCP layer of the default DRB, and on the other hand trigger the process of sending an E1 bearer setup request to the CU-CP; Or if the data corresponding to QoS Flow6 arrives, the SDAP layer of CU-UP will deliver the new data to the PDCP layer of the default DRB.
  • the role of the SDAP layer configuration parameter is when the data is transmitted from the core network, such as the UPF.
  • the SDAP layer of the CU-UP submits the data to the PDCP entity of the corresponding DRB for processing according to the QoS Flow information carried in the data.
  • QoS Flow establishes a DRB.
  • the PDU Session includes six QoS flows, namely QoS Flow1, QoS Flow2, QoS Flow3, QoS Flow4, QoS Flow5, and QoS Flow6.
  • QoS Flow5 and QoS Flow6 start with no data, Then, QoS Flow5 can be configured as "QoS Flow5 does not map any DRB temporarily", and QoS Flow6 is configured as "QoS Flow6 is mapped to the default DRB".
  • QoS Flow included in the CU-CP does not need to establish a corresponding DRB, the corresponding PDCP entity of the DRB will not be established, and the L1 and L2 parameters of the corresponding DRB will not be configured to the DU.
  • Step S86 The CU-UP establishes a bearer between the DU and the CU-UP according to the configuration parameter.
  • Step S87 The CU-UP sends a second response message to the CU-CP.
  • the second response message carries at least a transport network layer address that is transmitted between the CU and the PU and is transmitted by the DU.
  • the transport network layer address may be based on the UE or may be The DRB is in units.
  • the transport network layer address is used by the DU to send data to the CU CU-UP.
  • the transport layer address assigned by the CU-UP is referred to as a second address.
  • Step S88 The CU-CP sends a third response message to the DU.
  • the third response message carries the second address.
  • the method may further include:
  • Step S89 The CU-CP sends a DRB setup message to the UE, and configures a radio parameter for the UE.
  • the DRB setup message includes at least one of a PDCP layer configuration parameter, an RLC layer configuration parameter, a Mac layer configuration parameter, and a physical layer configuration parameter corresponding to the DRB.
  • Step S810 The UE establishes a DRB between the DU and the UE according to the DRB setup message, and after establishing the DRB, sends a fourth response message to the CU-UP, where the fourth response message is in response to the DRB setup message.
  • the DRB of the data corresponding to the QoS Flow in the PDU Session can be established, and the CU-UP can obtain the transport layer address allocated by the DU as the bearer corresponding to the DRB, and the DU can obtain the CU-UP as the The bearer allocates a transport layer address, so that the CU-UP and the DU can transmit data corresponding to the QoS Flow through the bearer.
  • the embodiment of the present application provides a process for establishing a bearer, where the E1 bearer setup request message may be specifically the first trigger message in FIG. 5, FIG. 6, and FIG. 7; the first F1.
  • the bearer setup message may be specifically the first request message in the foregoing FIG. 5, FIG. 6 and FIG. 7; the first E1 bearer setup message may be specifically the second request message in FIG. 5, FIG. 6 and FIG.
  • a bearer corresponds to a bearer between the CU-UP and the DU.
  • the process specifically includes:
  • Step S91 The CN sends downlink data to the CU-UP, where the downlink data carries QoS Flow indication information.
  • the CN may be specifically a UPF.
  • Step S92 The CU-UP determines, according to the QoS Flow indication information carried in the downlink data, whether the downlink data can be mapped to the established DRB, and if it can be mapped to the established DRB, step S93 is performed. If it cannot be mapped to the established DRB, or can only be mapped to the default DRB, step S94 is performed.
  • Step S93 The CU-UP transmits the downlink data to the DU through the established DRB, and the DU transmits the downlink data to the UE through the established DRB.
  • Step S94 The CU-UP sends an E1 bearer setup request message to the CU-CP, requesting the CU-CP to establish a new DRB for transmitting the downlink data.
  • the CU-UP needs to carry the PDU Session ID information in the bearer setup request message, so that the CU-CP can obtain the PDU session ID information according to the PDU. Determine which DRB needs to be established for the QoS Session of the PDU Session.
  • Step S95 The CU-CP receives the E1 bearer setup request message, and sends a first F1 bearer setup message to the DU.
  • the first F1 bearer setup message carries the L1 and L2 parameters corresponding to the DRB, and the specific parameters may be the same as the parameters carried in the first F1 bearer in the foregoing process 8, but each parameter is The value of the first F1DRB corresponds to the Qos Flow parameter corresponding to the DRB to be established.
  • Step S96 The DU determines the bearer to be established and the required configuration parameters according to the QoS Flow information carried in the first F1 bearer setup request message.
  • Step S97 The DU establishes a corresponding bearer according to the configuration parameter, and sends a first response message to the CU-CP.
  • the first response message carries at least a transport network layer address of the data allocated by the DU and the CU-UP, where the transport network layer address is used by the CU-UP to send downlink data to the DU, where
  • the transport network layer address may be in units of UEs, or may be in units of bearers.
  • the transport layer address may be referred to as a first address.
  • Step S98 The CU-CP receives the first response message sent by the DU, and sends a first E1 bearer setup message to the CU-UP.
  • the first E1 bearer setup message carries at least the transport layer address, that is, the first address, of the data allocated between the DU and the CU-UP.
  • Step S99 The CU-UP establishes a bearer between the CU-UP and the DU, and sends a second response message to the CU-CP.
  • the flow method shown in FIG. 6 may be used, and the transport layer for transmitting uplink data allocated between the DU and the CU-UP may be carried in the E1 bearer setup request message.
  • the address, that is, the second address, and the second address is carried in the first F1 bearer setup message.
  • the second address may be carried in the second response message by using the method shown in FIG. 7.
  • the process shown in FIG. 9 may further include step S910: CU.
  • the CP sends a third response message to the DU, where the second response message carries the second address.
  • Step S911 The CU-CP sends a DRB setup message to the UE, and configures radio bearer related parameters for the UE.
  • Step S912 The UE sends a fourth response message to the CU CU-CP, where the fourth response message is responsive to the DRB setup message.
  • the sequence of the step S91 to the step S912 is not limited.
  • the CU-CP may send the first E1 bearer to the first CU-UP. And sending the first F1 bearer setup message to the DU, and sending the first F1 bearer setup message to the TU, and then sending the first E1 bearer setup message to the CU-UP.
  • the DU and the CU-CP may be located at the same node, and in the flow shown in FIG. 9 of the present application, the flow between the DU and the CU CU-CP may be omitted.
  • the flow between CU-UP and CN can be omitted.
  • the flow between the CU-CP and the CU-UP and the DU can be merged.
  • the CU-UP may also trigger the process based on the received uplink data.
  • the UE may use the default bearer to send data of a certain QoS Flow to the CU- UP, the SDAP layer of the CU UE performs an operation similar to when the downlink data is received. I will not repeat them here.
  • the application provides a process for releasing a bearer method. As shown in FIG. 10, the process is specifically as follows:
  • Step S101 The CU-CP sends a first request message to the DU when receiving the second trigger message.
  • the first request message is used to request the DU to release the first bearer, where the first bearer is a bearer between the DU and the CU-UP, and the first bearer is used for the DU and the CU-UP.
  • the first request message carries the identifier of the first bearer.
  • Step S102 The DU releases the first bearer according to the first request message.
  • Step S104 The CU-CP sends a second request message to the CU-UP, where the second request message is used to request the CU-UP to release the first bearer, where the second request message carries the identifier of the first bearer.
  • Step S105 The CU-UP releases the first bearer according to the second request message.
  • the request message may be specifically sent to the DU and the CU-UP to request the DU and the CU-UP to release the corresponding bearer.
  • the method further includes: Step S103: the DU sends a first response message to the CU-CP, where the first response message is responsive to the first Request message.
  • the method may further include: step S106: the CU-UP sends a second response message to the CU-CP, where the second response message is responsive to the second request message.
  • step S102 may be performed first, and the first request is sent.
  • the message is sent to the step S104, and the second request message is sent.
  • the step S104 is performed first, and the second request message is sent, and then the step S102 is sent to send the first request message, and details are not described herein.
  • the E1 bearer release request may correspond to the second trigger message in FIG. 10, where the first F1 bearer release message may correspond to the first request message in FIG. 10, and the first F1 bearer release response
  • the first E1 bearer release message may correspond to the second request message in FIG. 10
  • the first E1 bearer release response may correspond to the second response message in FIG.
  • the process may specifically be:
  • Step S110 The CU-UP sends an E1 bearer release request message to the CU-CP when it is determined that a certain DRB needs to be released.
  • the CU-UP can monitor the data arrival status of each DRB, such as starting or restarting a timer reflecting the DRB data activity level according to whether data is received or not, such as Inactivity. Timer. After the timer expires, CU-UP can determine that the DRB corresponding to the service needs to be released.
  • the E1 bearer release request message carries the identifier information that needs to release the DRB.
  • Step S111 The CU-CP receives the E1 bearer release request, and sends a first F1 bearer release message to the DU.
  • the first F1 bearer release message may carry identifier information of the first bearer that needs to be released or suspended.
  • Step S112 The DU releases the corresponding first bearer according to the first F1 bearer release message.
  • Step S113 The DU sends a first F1 bearer release response to the CU-CP.
  • Step S114 The CU-CP sends a first E1 bearer release message to the CU-UP.
  • Step S115 The CU-UP releases the corresponding first bearer according to the first E1 bearer release message.
  • Step S116 The CU-UP sends a first E1 bearer release response to the CU-CP.
  • Step S117 The CU-CP sends a DRB release or RRC release command to the UE.
  • the RRC release command may be sent, otherwise, the DRB release command is sent.
  • Step S118 The UE sends a DRB release completion or RRC release complete message to the CU-CP.
  • the method for releasing a bearer shown in FIG. 10 can be applied to a process of suspending a bearer.
  • the following describes the method of suspending the bearer in combination with a specific scenario.
  • the embodiment of the present application provides a method for suspending a bearer.
  • the DRB in the flow may correspond to the first bearer in FIG. 10
  • the suspend request may correspond to the second in FIG.
  • the trigger message, the first request message or the second request message, the Suspend response message may correspond to the first response message or the second response message in FIG. 10
  • the SN Transfer message may correspond to the forwarding data in FIG.
  • the process may be specifically as follows:
  • Step S120 The CU-UP sends an E1 bearer Suspend request message to the CU-CP when it is determined that a certain DRB needs to be released.
  • the CU-UP can monitor the data arrival status of each DRB, such as starting or restarting a timer reflecting the DRB data activity level according to whether data is received or not, such as Inactivity. Timer. After the timer expires, CU-UP can determine that the DRB corresponding to the service needs to be released.
  • the E1 bearer release request message or the Suspend request message carries the identifier information of the DRB that needs to be released or suspended.
  • Step S121 The CU-CP receives the Suspend request and sends a Suspend request to the DU.
  • the Suspend request message carries the identifier information of the DRB that needs to be suspended.
  • Step S122 The DU suspends the corresponding DBR according to the Suspend request.
  • Step S123 The DU sends a Suspend response to the CU-CP.
  • Step S124 The CU-CP sends a Suspend request to the CU-UP.
  • the Suspend request message carries the identifier information of the DRB that needs to be suspended.
  • Step S125 The CU-UP suspends the corresponding DRB according to the Suspend request.
  • Step S126 The CU-UP sends a Suspend response message to the CU-CP.
  • Step S127 The CU-CP sends a Suspend command or an RRC release command or a DRB release command to the UE.
  • the Suspend command or the RRC release command may be sent; otherwise, the DRB release command is sent.
  • Step S128 The UE sends a DRB release response message or a Suspend response message or an RRC response message to the CU CP.
  • step S120 to step S128 is not limited.
  • the embodiment of the present application further provides a procedure for switching a bearer. As shown in FIG. 13, the process specifically includes:
  • Step S131 The destination CU-CP sends a first message to the destination CU-UP.
  • Step S132 The destination CU-UP sends a first response message to the destination CU-CP, where the first response message is in response to the first message, where the first response message carries a first address, the first address Used by the source CU-UP to send forward data to the destination CU-UP.
  • Step S133 The destination CU-CP sends a second message to the source CU-CP, where the second message carries the first address.
  • Step S134 The source CU-CP sends a third message to the source CU-UP, where the third message carries the first address.
  • step S134 the method further includes: step S135: the source CU-UP sends a second response message to the source CU-CP, where the second response message is responsive to the second message,
  • Step S136 The source CU-UP sends forward data to the destination CU-UP according to the first address.
  • the method of the embodiment of the present application can successfully implement data forwarding.
  • CU-UP1 corresponds to source CU-UP in FIG. 13
  • CU-CP1 corresponds to source CU-CP in FIG. 13
  • CU-UP2 corresponds to FIG.
  • the destination CU-UP, CU-CP2 corresponds to the destination CU-CP in FIG. 13
  • the first message may correspond to a HandoverIn request message
  • the first response message may correspond to a HandoverIn response message
  • the second message may correspond to a Context Retrieval Complete message.
  • the third message may correspond to a HandoverOut request message
  • the second response message may correspond to a HandoverOut response message.
  • the process specifically includes:
  • Step S141 CU-UP1 receives downlink data from the core network node CN, generates an E1 bearer setup request message, and requests the CU CP1 to recover the DRB for transmitting the data.
  • the core network node CN may be specifically a UPF.
  • the core network node CN may be specifically a UPF.
  • Step S142 The CU-CP1 determines that the UE is in the Suspend or Inactive state, and then initiates RAN paging in the RAN paging area of the UE.
  • the RAN paging area of the UE may be configured for the UE when the UE enters the Suspend or Inactive state, and may be a TA area, or a cell list, or a RAN area identifier, where the UE is in the state.
  • a TA area or a cell list, or a RAN area identifier, where the UE is in the state.
  • the RAN paging area of the UE may include one CU-CP, and may also include multiple CU-CPs.
  • the last CU-CP serving the UE is called an Anchor CU-CP.
  • the Anchor CU-CP sends a RAN paging message to other CPs in the RAN paging area.
  • the Anchor CU-CP may be referred to as CU-CP2.
  • each CU-CP in the RAN paging area After receiving the RAN paging message, each CU-CP in the RAN paging area initiates paging in the respective controlled area. Specifically, the RRC paging message is sent through the respective DU, or when the CU-CP and the DU are located in the same At the time of the node, the RRC paging message is directly sent.
  • the UE after receiving the paging message, the UE sends an RRC Resume Request message to the network side.
  • RRC Resume Request message In the embodiment of the present application, taking the UE in the CU-CP2 as an example, the following process is described in detail:
  • Step S143 The UE sends the RRC Resume Request message to the Cu-CP2 through the DU2.
  • Step S144 The CU-CP2 sends a Context Retrieval Request message to the CU-CP1 according to the RRC Resume Request message sent by the UE.
  • the RRC Resume Request message includes the Resume ID of the UE, and the CU-CP2 determines the Anchor CU-CP of the UE, that is, CU-CP2, CU according to the Resume ID in the RRC Resume Request message sent by the UE.
  • Step S145 The CU-CP1 sends a Context Retrieval Response message to the CU CP2, which mainly carries the context information of the UE.
  • the context of the UE may include information such as PDU Session information, DRB information, and transport layer address information of the CU UP.
  • Step S146 CU-CP2 establishes a bearer between CU-UP2 and DU2.
  • the process of the CU-CP2 to establish the bearer between the CU-CP2 and the DU2 refer to the methods described in the foregoing FIG. 4 to FIG. 9, and details are not described herein again.
  • Step S147 A bearer is established between CU-CP2 and CU-UP2.
  • the CU CP2 may send a HandoverIn request message to the CU UP2, where the message carries relevant configuration parameters of the UE, such as configuration parameters of the RB; in step 9, the CU UP2 sends a HandoverIn response message to the CU CP2, the message Carry Cu UP2 as information such as the transport layer address of each RB.
  • Step S148 The CU-CP2 sends a Context Retrieval Complete message to the CU-CP1, which carries Cu UP2 as the transport layer address and other information configured for each RB.
  • Step S149 The CU-CP1 sends a HandoverOut request message to the CU-UP1, which carries Cu UP2 as the transport layer address and other information configured for each RB.
  • step S149 the method further includes: step S1410: CU-UP1 may reply the CU-CP1 with a HandoverOut response message.
  • Step S1411 CU-UP1 sends a SN Transfer (Transfer) message to CU-UP2.
  • the SN Transfer message may carry the PDCP status information of each RB in the CU-UP1, such as an uplink counter value, a downlink counter value, and a status of the received uplink SDU.
  • the SN Status Transfer message may be directly sent. If there is no interface between CU-UP1 and CU-UP2, the SN Status Transfer message is sent through CU-CP1 and CU-CP2. Through the above step S140, the downlink data of CU-UP1 can be forwarded to CU-UP2.
  • Step S1412 CU-CP2 sends an RRC Resume (RRC Resume) message to the UE through the DU2.
  • Step S1413 The UE sends an RRC Resume Complete (RRC Resume Complete) message to the CU CP2.
  • Step S1414 CU-UP1 releases the connection with the UE between CU-CP1; CU-CP1 releases the connection with the UE for DU1
  • the signaling flow triggered by the CU-UP1 implements data forwarding.
  • the method for establishing a bearer, the method for releasing a bearer, and the method for switching a bearer are respectively introduced from the perspective of the interaction between the network elements and the respective network elements.
  • each network element such as UE, CU-UP, CU-CP, etc.
  • each network element includes hardware structures and/or software modules corresponding to each function.
  • UE such as UE, CU-UP, CU-CP, etc.
  • present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • FIG. 15 is a schematic diagram of a possible structure of an access network device according to the foregoing embodiment, and the access network device may be a CU-UP, a CU-CP, a DU, or the like involved in the foregoing embodiment.
  • the illustrated access network device 1500 can include a transceiver 1501, a controller/processor 1502.
  • the transceiver 1501 can be used to support the transmission and reception of information between the network and the UE in the foregoing embodiment, and to support radio communication between network devices, such as supporting CU-UP and radio communication between CU-CP.
  • the controller/processor 1502 can be configured to perform various functions for communicating with a UE or other network device. On the uplink, the uplink signal from the UE is received via the antenna, coordinated by the transceiver 1501, and further processed by the controller/processor 1502 to recover the traffic data and signaling information transmitted by the UE.
  • the controller/processor 1502 On the downlink, traffic data and signaling messages from the core network node are received and processed by the controller/processor 1502 and mediated by the transceiver 1501 to generate a downlink signal and transmitted to the UE via the antenna. .
  • the controller/processor 1502 is further configured to perform a method for establishing a bearer, a method for releasing a bearer, or a method for modifying a bearer, as described in the foregoing embodiment.
  • the method may be specifically executed in response to the first And triggering a message, sending a first request message to the access network distribution unit, where the first request message is used to request the access network distribution unit to establish a first bearer, and receive the first sent by the access network distribution unit a response message, the first response message is responsive to the first request message, the first response message carries a first address, and the first address is a first transport layer corresponding to the first bearer
  • Sending a second request message to the access network user plane device where the second request message is used to request the access network user plane device to establish the first bearer, where the second request message carries the a first address, where the first address is used by the access network user plane device to send downlink data or the like to the access network distribution unit device by using the first bearer.
  • the controller/processor 1502 may also be used to perform the processes involved in the network device of FIGS. 4-14 and/or other processes for the techniques described herein.
  • the access network device 1500 can also include a memory 1503 that can be used to store program codes and data of the access network device.
  • the access network device 1500 can also include a communication unit 1504 for supporting the access network device to communicate with other network entities.
  • Figure 15 only shows a simplified design of the base station.
  • the access network device may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all access network devices that can implement the present application are in the embodiments of the present application. Within the scope of protection.
  • the controller/processor for performing the foregoing access network device in the embodiment of the present application may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and field programmable. Gate array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • FIG. 16 shows an access network control plane device 1600.
  • the access network control plane device 1600 can be the CU-CP in the foregoing embodiment, including:
  • the transceiver unit 1601 is configured to send, according to the first trigger message, a first request message to the access network distribution unit, receive the first response message sent by the access network distribution unit, and send the message to the access network user plane device.
  • a second request message where the first request message is used to request the access network distribution unit to establish a first bearer, where the first response message is carried in the first response message in response to the first request message
  • the first address is the first transport layer address corresponding to the first bearer
  • the second request message is used to request the access network user plane device to establish the first bearer.
  • the second request message carries the first address, where the first address is used by the user equipment of the access network to send downlink data to the access network distribution unit device by using the first bearer;
  • the processing unit 1602 is configured to generate the first request message and the second request message.
  • the first trigger message carries a second address, where the second address is a second transport layer address corresponding to the first bearer, and the second address is used for the
  • the network distribution unit sends the uplink data to the access network user plane device by using the first bearer, where the first request message carries the second address.
  • the transceiver unit 1601 is further configured to: receive a second response message sent by the access network user plane device, where the second response message is responsive to the second request message.
  • the transceiver unit 1601 is further configured to: receive a second response message sent by the access network user plane device, where the second response message is responsive to the second request message,
  • the second response message carries a second address, where the second address is a second transport layer address corresponding to the first bearer, and a third response message is sent to the access network distribution unit device, where the third response
  • the message carries the second address, where the second address is used by the access network distribution unit to send uplink data to the access network user plane device by using the first bearer.
  • the processing unit 1602 is configured to generate a first request message and a second request message when receiving the second trigger message;
  • the transceiver unit 1601 is configured to send the first request message to the access network distribution unit device, and send a second request message to the access network user plane device, where the first request message is used to request the access network distribution unit
  • the device releases the first bearer, where the first bearer is used for data exchange between the access network distribution unit device and the access network user plane device, and the first request message carries the identifier of the first bearer.
  • the second request message is used to request the user equipment of the access network to release the first bearer, and the second request message carries the identifier of the first bearer.
  • the transceiver unit 1601 is further configured to: receive a first response message sent by the access network distribution unit, where the first response message is responsive to the first request message; and the access network user is received. a second response message sent by the device, the second response message being responsive to the second request message.
  • the processing unit 1602 is configured to generate a first message and a second message.
  • the transceiver unit 1601 is configured to send the first message to the target access network user plane device, receive the first response message sent by the target access network user plane device, and send the second message to the source access network control plane device.
  • the first response message is responsive to the first message, the first response message carries a first address, and the first address is used by the source access network user plane device to the destination access network user plane device Forwarding data is sent, and the third message carries the first address.
  • the transceiver unit 1601 is configured to receive a second message sent by the control device of the destination access network, where the second message carries a first address, where the first address is used by the user equipment of the source access network Describe the destination access network control plane device to send forward data;
  • the processing unit 1602 is configured to generate a third message, where the third message carries the first address
  • the transceiver unit 1602 is further configured to send a third message to the source access network user plane device.
  • the transceiver unit 1601 is further configured to: receive a second response message sent by the source access network user plane device, where the second response message is responsive to the third message.
  • FIG. 17 shows an access network distribution unit device 1700.
  • the access network distribution unit 1700 may be specifically the DU in the above-mentioned identification, and includes:
  • the transceiver unit 1701 is configured to receive a first request message sent by the access network control plane device;
  • the processing unit 1702 is configured to establish, according to the first request message, a first bearer, where the first bearer is a bearer between the access network distribution unit device and the access network user plane device;
  • the transceiver unit 1701 is further configured to send a first response message to the access network control plane device, where the first response message is responsive to the first request message, the first response message
  • the first address is the first transport layer address corresponding to the first bearer, and the first address is used by the user equipment of the access network to pass through the first bearer
  • the access network distribution unit device transmits downlink data.
  • the first request message carries a second address, where the second address is a second transport layer address corresponding to the first bearer, and the second address is used for the
  • the network distribution unit device sends uplink data to the access network user plane device by using the first bearer.
  • the transceiver unit 1701 is further configured to: receive a third response message sent by the control device of the access network, where the third response message carries a second address, where the second address is The second transport layer address corresponding to the first bearer, where the second address is used by the access network distribution unit to send uplink data to the access network user plane device by using the first bearer.
  • the transceiver unit 1701 is configured to receive a first request message sent by the access network control plane device, where the first request message carries an identifier of the first bearer, where the first bearer is used by the access network distribution unit device Data exchange with the access network user plane device;
  • the processing unit 1702 is configured to release the first bearer according to the identifier of the first bearer.
  • the transceiver unit 1701 is further configured to: send a first response message to the access network control plane device, where the first response message is responsive to the first request message.
  • FIG. 18 shows an access network user plane device 1800.
  • the access network user plane device 1800 may be specifically the CU-UP in the foregoing embodiment, and includes:
  • the transceiver unit 1801 is configured to receive a second request message sent by the access network control plane device, where the second request message carries a first address, where the first address is a first transport layer address corresponding to the first bearer
  • the first address is used by the access network user plane device to send downlink data to the access network distribution unit device by using the first bearer;
  • the processing unit 1802 is configured to establish, according to the second request message, a first bearer, where the first bearer is a bearer between the access network distribution unit device and the access network user plane device.
  • the transceiver unit 1801 is further configured to: send a first trigger message to the access network control plane device, where the first trigger message carries a second address, where the second address is a second transport layer address corresponding to the first bearer, where the second address is used by the access network distribution unit to send uplink data to the access network user plane device by using the first bearer;
  • the access network control plane device sends a second response message, and the second response message is responsive to the second request message.
  • the transceiver unit 1801 is further configured to: send a second response message to the access network control plane device, where the second response message is responsive to the second request message, the second The response message carries a second address, where the second address is a second transport layer address corresponding to the first bearer, and the second address is used by the access network distribution unit device to pass the first bearer Sending uplink data to the access network user plane device.
  • the transceiver unit 1801 is configured to receive a second request message sent by the access network control plane device, where the second request message carries an identifier of the first bearer, where the first bearer is used by the access network distribution unit device Data exchange with the access network user plane device;
  • the processing unit 1802 is configured to release the first bearer according to the identifier of the first bearer.
  • the transceiver unit 1801 is further configured to: send a second response message to the access network control plane device, where the second response message is responsive to the second request message.
  • the transceiver unit 1801 is configured to receive a third message sent by the source access network control plane device, where the third message carries a first address, where the first address is used by the source user plane device to the destination user plane device Send forward data;
  • the processing unit 1802 is configured to obtain forwarding data, where the forwarding data carries downlink service data to be transferred by the terminal device and processing information of the downlink service data.
  • the transceiver unit 1801 is further configured to send forwarding data to the destination user plane device according to the first address.
  • a computer readable storage medium comprising instructions, when operating on a communication device, such that the access network devices (such as CU-UP, CU-CP, and DU) in the foregoing embodiments.
  • the access network devices such as CU-UP, CU-CP, and DU
  • the method for establishing a bearer, the method for releasing a bearer, or the method for modifying a bearer in the foregoing embodiment is performed.
  • the embodiment of the present application further provides a device, where the device is connected to a memory, and is configured to read and execute a software program stored in the memory, to implement a method for establishing a bearer, a method for releasing a bearer, or a modification in the foregoing embodiment.
  • the device can be a chip.
  • the embodiment of the present application further provides a communication device, which may be a terminal device or a circuit.
  • the communication device can be used to perform the actions performed by the terminal device in the above method embodiments.
  • FIG. 19 shows a schematic structural diagram of a simplified terminal device.
  • the terminal device uses a mobile phone as an example.
  • the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input/output device.
  • the processor is mainly used for processing communication protocols and communication data, and controlling terminal devices, executing software programs, processing data of software programs, and the like.
  • Memory is primarily used to store software programs and data.
  • the RF circuit is mainly used for the conversion of the baseband signal and the RF signal and the processing of the RF signal.
  • the antenna is mainly used to transmit and receive RF signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are primarily used to receive user input data and output data to the user. It should be noted that some types of terminal devices may not have input and output devices.
  • the processor When the data needs to be sent, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal, and then sends the radio frequency signal to the outside through the antenna in the form of electromagnetic waves.
  • the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.
  • the memory may also be referred to as a storage medium or a storage device or the like.
  • the memory may be independent of the processor, or may be integrated with the processor, which is not limited in this embodiment of the present application.
  • the antenna and the radio frequency circuit having the transceiving function can be regarded as the transceiving unit of the terminal device, and the processor having the processing function is regarded as the processing unit of the terminal device.
  • the terminal device includes a transceiver unit 1910 and a processing unit 1920.
  • the transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver, and the like.
  • the processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, and the like.
  • the device for implementing the receiving function in the transceiver unit 1910 can be regarded as a receiving unit, and the device for implementing the sending function in the transceiver unit 1910 is regarded as a sending unit, that is, the transceiver unit 1910 includes a receiving unit and a sending unit.
  • the transceiver unit may also be referred to as a transceiver, a transceiver, or a transceiver circuit.
  • the receiving unit may also be referred to as a receiver, a receiver, or a receiving circuit or the like.
  • the transmitting unit may also be referred to as a transmitter, a transmitter, or a transmitting circuit, and the like.
  • transceiver unit 1910 is configured to perform the sending operation and the receiving operation on the terminal device side in the foregoing method embodiment
  • the processing unit 1920 is configured to perform other operations on the terminal device except the transmitting and receiving operations in the foregoing method embodiments.
  • the transceiver unit 1910 is configured to perform the operation of sending the second response in S46 in FIG. 4, and/or the transceiver unit 1910 is further configured to perform other transceiver steps on the terminal device side in the embodiment of the present application.
  • the processing unit 1920 is configured to perform the operation of establishing the DRB in S46 in FIG. 4, and/or the processing unit 1920 is further configured to perform other processing steps on the terminal device side in the embodiment of the present application.
  • the transceiver unit 1910 is configured to perform the operation of sending the fourth response message by the S810 terminal device side in FIG. 8, and/or the transceiver unit 1910 is further configured to perform the terminal device side in the embodiment of the present application.
  • the processing unit 1920 is configured to perform the operation of establishing the DRB between the DU and the UE in S810 in FIG. 8 , and/or the processing unit 1920 is further configured to perform other processing steps on the terminal device side in the embodiment of the present application.
  • the transceiver unit 1910 is configured to perform an operation of receiving downlink data by using the established DRB by the terminal device side in S93 in FIG. 9, and receiving an operation of receiving the DRB setup message in S911, and sending in S912.
  • the operation of the fourth response message, and/or the transceiver unit 1910 is also used to perform other transceiving steps on the terminal device side in the embodiment of the present application.
  • the transceiver unit 1910 is configured to perform an operation of receiving a DRB release or an RRC release command by the terminal device side in S117 in FIG. 11 , and an operation of sending a DRB release completion or an RRC release complete message in S118, And/or the transceiver unit 1910 is further configured to perform other transceiver steps on the terminal device side in the embodiment of the present application.
  • the transceiver unit 1910 is configured to perform a receiving operation on the terminal device side in S127 in FIG. 12, or a sending operation in S128, and/or the transceiver unit 1910 is further configured to execute the embodiment of the present application. Other transceiver steps on the terminal device side.
  • the chip When the communication device is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input/output circuit and a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the device shown in FIG. 20 can be referred to.
  • the device can perform functions similar to controller/processor 1502 of FIG.
  • the device includes a processor 2010, a transmit data processor 2020, and a receive data processor 2030.
  • the processing unit 1602 / processing unit 1702 / processing unit 1802 in the above embodiment may be the processor 2010 in FIG. 20 and perform the corresponding functions.
  • the transceiver unit 1610/transceiver unit 1701/transceiver unit 1801 in the above embodiment may be the transmission data processor 2020 in FIG. 20, and/or the reception data processor 2030.
  • a channel coder and a channel decoder are shown in FIG. 20, it is to be understood that these modules are not intended to be limiting, and are merely illustrative.
  • Fig. 21 shows another form of this embodiment.
  • the processing device 2100 includes modules such as a modulation subsystem, a central processing subsystem, and a peripheral subsystem.
  • the communication device in this embodiment can be used as a modulation subsystem therein.
  • the modulation subsystem may include a processor 2103, an interface 2104.
  • the processor 2103 performs the functions of the processing unit 1602/processing unit 1702/processing unit 1802, and the interface 2104 performs the functions of the transceiver unit 1610/transceiving unit 1701/transceiving unit 18010.
  • the modulation subsystem includes a memory 2106, a processor 2103, and a program stored on the memory 2106 and executable on the processor, and the processor 2103 executes the program to implement the terminal device side in the above method embodiment.
  • the memory 2106 may be non-volatile or volatile, and its location may be located inside the modulation subsystem or in the processing device 2100 as long as the memory 2106 can be connected to the The processor 2103 is sufficient.
  • a computer readable storage medium having stored thereon an instruction for executing a method on a terminal device side in the above method embodiment when the instruction is executed.
  • a computer program product comprising instructions which, when executed, perform the method on the terminal device side in the above method embodiment.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the user equipment.
  • the processor and the storage medium may also reside as discrete components in the user equipment.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

一种建立承载的方法及设备，用于解决在接入网控制面网元和接入网用户面网元分离的架构下，建立承载传输数据。该方法包括：接入网控制面设备响应于第一触发消息时，向接入网分布单元设备发送第一请求消息；所述接入网控制面设备接收所述接入网分布单元设备发送的第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址；所述接入网控制面设备向接入网用户面设备发送第二请求消息，所述第二请求消息中携带有所述第一地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据。

Description

一种建立承载的方法及设备
本申请要求于2017年09月28日提交中国专利局、申请号为201710900044.3、申请名称为“一种建立承载的方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种建立承载的方法及设备。
背景技术
目前，在LTE REL15以及5G NR的演进中，如图1所示，提出了一种新的网络架构。在该网络架构下，基站的功能被划分为中心单元(central unit，CU)和分布单元(distributed unit，DU)两个单元。其中，CU处理无线高层协议栈功能，比如，无线资源控制(radio resource control，RRC)层、服务数据适配协议(service data adaptation protocol，SDAP)层和分组数据汇聚协议(packet data convergence protocol，PDCP)层等；DU处理基带处理的物理层以及层2的部分协议栈功能，比如，无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层(physical layer，PHY)等。其中，CU和DU间的接口为F1接口。
进一步的，如图2所示，CU的功能又可被划分为控制面(control plane，CU-CP)和用户面(user plane,CU-UP)两个节点。其中，CU-CP用于控制DU和CU-UP进行数据无线承载(data radio bearer，DRB)建立、释放和数据前转等操作，涉及的协议层包括RRC层和PDCP层。而CU-UP用于根据CU-CP的配置，进行数据业务的传输，涉及的协议层包括SDAP层和PDCP层。通过图2可以看出，在CU-CP和CU-UP分离后，核心网发送的下行业务数据首先到达CU-UP，而CU-CP负责DRB的建立和释放等操作，此时，在下行业务数据所对应的DRB未成功建立时，如何建立下行业务数据所对应的DRB并没有相关解决方案。
发明内容
本申请实施例提供一种建立承载的方法及设备，以建立下行业务数据所对应的数据无线承载。
第一方面，本申请实施例公开了一种建立承载的方法，包括：接入网控制面设备响应于第一触发消息时，向接入网分布单元设备发送第一请求消息，所述第一请求消息用于请求所述接入网分布单元设备建立第一承载；所述接入网控制面设备接收所述接入网分布单元设备发送的第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址；所述接入网控制面设备向接入网用户面设备发送第二请求消息，所述第二请求消息用于请求所述接入网用户面设备建立所述第一承载，所述第二请求消息中携带有所述第一地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下 行数据。
应当指出，采用本申请实施例中的建立承载的方法，接入网控制面设备可获取第一承载所对应的地址，从而可通过第一承载向接入网分布单元发送下行数据。
在一种可能的设计中，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据，所述第一请求消息中携带有所述第二地址。
应当指出，在该可能的设计中，在第一触发消息中直接携带第二地址，从而避免利用其它交互信息获得第二地址，节省信令开销。
在一种可能的设计中，所述方法还包括：所述接入网控制面设备接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息。
在一种可能的设计中，所述方法还包括：所述接入网控制面设备接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址；所述接入网控制面设备向所述接入网分布单元设备发送第三响应消息，所述第三响应消息中携带有所述第二地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
第二方面，本申请提供一种建立承载的方法，包括：接入网分布单元设备接收接入网控制面设备发送的第一请求消息；所述接入网分布单元设备根据所述第一请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载；所述接入网分布单元设备向所述接入网控制面设备发送第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据。
在一种可能的设计中，所述第一请求消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
在一种可能的设计中，所述方法还包括：所述接入网分布单元设备接收接入网控制面设备发送的第三响应消息，所述第三响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
第三方面，本申请提供一种建立承载的方法，包括：接入网用户面设备接收接入网控制面设备发送的第二请求消息，所述第二请求消息中携带有第一地址，所述第一地址为第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；所述接入网用户面设备根据所述第二请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载。
在一种可能的设计中，所述方法还包括：所述接入网用户面设备向所述接入网控制面设备发送第一触发消息，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一 承载向所述接入网用户面设备发送上行数据；所述接入网用户面设备向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
在一种可能的设计中，所述方法还包括：所述接入网用户面设备向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
第四方面，本申请还提供一种释放承载的方法，包括：接入网控制面设备在接收到第二触发消息时，向接入网分布单元设备发送第一请求消息，所述第一请求消息用于请求所述接入网分布单元设备释放第一承载，所述第一承载用于所述接入网分布单元设备与接入网用户面设备之间数据交换，所述第一请求消息中携带有所述第一承载的标识；所述接入网控制面设备向接入网用户面设备发送第二请求消息，所述第二请求消息用于请求所述接入网用户面设备释放所述第一承载，所述第二请求消息中携带有所述第一承载的标识。
在一种可能的设计中，所述方法还包括：所述接入网控制面设备接收接入网分布单元设备发送的第一响应消息，所述第一响应消息响应于所述第一请求消息；所述接入网控制面设备接收接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息。
第五方面，本申请还提供一种释放承载的方法，包括：接入网分布单元设备接收接入网控制面设备发送的第一请求消息，所述第一请求消息中携带有第一承载的标识，所述第一承载用于所述接入网分布单元设备与接入网用户面设备之间数据交换；所述接入网分布单元设备根据所述第一承载的标识，释放所述第一承载。
在一种可能的设计中，所述方法还包括：所述接入网分布单元设备向所述接入网控制面设备发送第一响应消息，所述第一响应消息响应于所述第一请求消息。
第六方面，本申请还提供一种释放承载的方法，包括：接入网用户面设备接收接入网控制面设备发送的第二请求消息，所述第二请求消息中携带有第一承载的标识，所述第一承载用于所述接入网分布单元设备与接入网用户面设备之间数据交换；所述接入网用户面设备根据所述第一承载的标识，释放所述第一承载。
在一种可能的设计中，所述方法还包括：所述接入网用户面设备向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
第七方面，本申请提供一种切换承载的方法，包括：目的接入网控制面设备向目的接入网用户面设备发送第一消息；所述目的接入网控制面设备接收所述目的接入网用户面设备发送的第一响应消息，所述第一响应消息响应于所述第一消息，所述第一响应消息中携带有第一地址，所述第一地址用于源接入网用户面设备向目的接入网用户面设备发送前转数据；所述目的接入网控制面设备向源接入网控制面设备发送第二消息，所述第二消息中携带有所述第一地址。
第八方面，本申请提供一种切换承载的方法，包括：
源接入网控制面设备接收目的接入网控制面设备发送的第二消息，所述第二消息中携带有第一地址，所述第一地址用于所述源接入网用户面设备向所述目的接入网控制面设备发送前转数据；
所述源接入网控制面设备向源接入网用户面设备发送第三消息，所述第三消息中携带 有所述第一地址。
在一种可能的设计中，所述方法还包括：
所述源接入网控制面设备接收所述源接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第三消息。
第九方面，本申请还提供一种切换承载的方法，包括：
源接入网用户面设备接收源接入网控制面设备发送的第三消息，所述第三消息中携带有第一地址，所述第一地址用于所述源用户面设备向目的用户面设备发送前转数据；
所述源用户面设备根据所述第一地址，向目的用户面设备发送前转数据，所述前转数据中携带有终端设备待转移的下行业务数据以及所述下行业务数据的处理信息。
第十方面，本申请实施例提供了一种接入网设备，可以包括控制器/处理器，存储器以及通信单元。所述控制器/处理器可以用于执行上述建立承载的方法、释放承载的方法，或修改承载的方法。存储器可以用于存储接入网设备的程序代码和数据。所述通信单元，用于支持接入网设备间的通信，譬如接入网设备可以包括接入网控制面设备、接入网用户面设备和接入网分布设备，所述通信单元可支持接入网控制面设备与接入网用户面设备间的通信。
第十一方面，本申请实施例提供了一种通信系统，该系统包括上述方面的接入网设备，比如可具体为包括接入网控制面设备、接入网用户面设备以及接入网分布设备等。
第十二方面，本申请实施例提供了一种计算机存储介质，用于储存为上述接入网设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第十三方面，本申请实施例还提供一种装置，所述装置与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现上述方法所设计的方法。由上可见，在本申请实施例中，可建立CU-UP与DU间的第一承载，且由于CU-CP向CU-UP发送的第二请求中携带有第一地址，所述第一地址用于CU-UP通过第一承载向DU发送下行数据，因此CU-UP可利用该第一地址，通过第一承载向DU发送下行业务数据，实现下行业务数据的传输。
附图说明
图1至图3为本申请实施例所提供的一网络架构；
图4为本申请实施例提供的下行数据传输的流程；
图5至图9为本申请实施例提供的建立承载的流程；
图10至图12为本申请实施例提供的释放承载的流程；
图13和图14为本申请实施例提供的切换承载的流程；
图15为本申请实施例提供的接入网设备的一结构示意图；
图16为本申请实施例提供的接入网控制面设备的一结构示意图；
图17为本申请实施例提供的接入网分布单元设备的一结构示意图；
图18为本申请实施例提供的接入网用户面设备的一结构示意图；
图19为本申请实施例提供的通信装置的示意性框图；
图20为本申请实施例提供的通信装置的另一示意性框图；
图21为本申请实施例提供的通信装置的再一示意性框图。
具体实施方式
为了便于理解，示例的给出了与本申请的实施例相关概念的说明以供参考，如下所示：
通信系统，可以为各种无线接入技术(radio access technology，RAT)系统，譬如例如码分多址(code division multiple access，CDMA)、时分多址(time division multiple access，TDMA)、频分多址(frequency division multiple access，FDMA)、正交频分多址(orthogonal frequency-division multiple access，OFDMA)、单载波频分多址(single carrier FDMA，SC-FDMA)和其它系统等。术语“系统”可以和“网络”相互替换。CDMA系统可以实现例如通用无线陆地接入(universal terrestrial radio access，UTRA)，CDMA2000等无线技术。UTRA可以包括宽带CDMA(wideband CDMA，WCDMA)技术和其它CDMA变形的技术。CDMA2000可以覆盖过渡标准(interim standard，IS)2000(IS-2000)，IS-95和IS-856标准。TDMA系统可以实现例如全球移动通信系统(global system for mobile communication，GSM)等无线技术。OFDMA系统可以实现诸如演进通用无线陆地接入(evolved UTRA，E-UTRA)、超级移动宽带(ultra mobile broadband，UMB)、IEEE 802.11(Wi-Fi)，IEEE 802.16(WiMAX)，IEEE 802.20，Flash OFDMA等无线技术。UTRA和E-UTRA是UMTS以及UMTS演进版本。3GPP在长期演进(long term evolution，LTE)和基于LTE演进的各种版本是使用E-UTRA的UMTS的新版本。此外，所述通信系统还可以适用于面向未来的通信技术，只要采用新通信技术的通信系统包括承载的建立，都适用本申请实施例提供的技术方案。本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
基站，是一种部署在无线接入网中用以为UE提供无线通信功能的装置。所述基站可以包括各种形式的宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在LTE系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB),在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。为方便描述，本申请所有实施例中，上述为UE提供无线通信功能的装置统称为基站。
UE，可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备。所述UE也可以称为移动台(mobile station,简称MS)，终端(terminal)，终端设备(terminal equipment)，还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端等。为方便描述，本申请所有实施例中，上面提到的设备统称为UE。
核心网(core network，CN)节点，连接一个或多个基站，可以控制基站建立业务承载，比如，控制节点可控制CU-CP建立CU-UP与DU间的承载，以及建立DU与UE间的承载。在本申请实施例中，例如，所述基站可以为UMTS系统中的Node B，所述核心网节点可以为网络控制器。又例如，所述基站可以为小站，则所述控制节点可以为覆盖所述小站的宏基站。再例如，所述控制节点可以为无线网络跨制式协同控制器等，基站为无线网络中的 基站，在本申请实施例中不作限定说明。为方便描述，在本申请实施例中，将实现上述功能控制建立承载的设备，统一称为CN。
集中单元(central unit，CU)，处理无线高层协议栈功能，比如，无线资源控制(radio resource control，RRC)层和分组数据汇聚协议(packet data convergence protocol，PDCP)层等；CU分别与CN和DU相连。在下行通信链路中，用于从CN接收数据，并发送给DU。在上行通信链路中，用于从DU接收数据，并发送给CN。同时，CU具有对DU的集中控制功能。在采用不同的无线接入技术的系统中，具有CU功能的设备可能有不同的名称。为了方便描述，将具有CU功能的设备统称为接入网集中单元设备。
分布单元(distributed unit，DU)，处理基带处理的物理层以及层2的部分协议栈功能，比如，无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层(physical layer，PHY)等。DU分别与CU和用户设备(user equipment，UE)相连，在下行通信链路中，用于从CU接收数据，发送给UE，在上行通信链路中，用于从UE接收数据，发送给CU。在采用不同的无线接入技术的系统中，具有DU功能的设备可能有不同的名称。为了方便描述，将具有DU功能的设备统称为接入网分布单元设备。
控制面(control plane，CU-CP)，用于控制CU-UP和DU进行业务建立、释放和数据转转等操作，涉及的协议包括RRC层和PDCP层。在采用不同的无线接入技术的系统中，具有CU-CP功能的设备可能有不同的名称。为了方便描述，将具有CU-CP功能的设备统称为接入网控制面设备。
用户面(user plane，CU-UP)用于根据CU-CP的配置，进行业务数据的传输。同样，在采用不同的无线接入技术的系统中，具有CU-UP功能的设备可能有不同的名称。为了方便描述，将具有CU-UP功能的设备统称为接入网用户面设备。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整的描述。
图3示出了本申请实施例一种可能的通信系统。如图3所示，通信系统300至少可包括基站30和UE31。
在LTE REL15以及5G NR的演进中，基站30的功能可被划分为集中单元(central unit，CU)和分布单元(distributed unit，DU)两个单元。如图4所示，当基站30的功能被划分为CU和DU两个单元时，下行业务数据传输的过程，如下：
步骤S41：核心网节点CN向CU发送下行业务数据，其中，所述下行业务数据中携带有服务质量流(quality of service flow，Qos Flow)指示信息。
步骤S42：CU在接收到所述下行业务数据后，根据所述下行业务数据中携带的Qos Flow指示信息，判断所述下行业务数据所对应的数据无线承载(data radio bearer，DRB)是否已成功建立，如果成功建立，则执行步骤S43；如果没有成功建立，则执行步骤S44。
步骤S43：CU通过所对应的DRB将下行业务数据传输至DU。
步骤S44：CU则向DU发送第一承载建立请求，向UE发送DRB建立请求。
其中，所述第一承载建立请求中携带有CU分配的第一承载的第一传输层的地址，所述DRB建立请求中携带有所述下行业务数据所对应所述DRB的标识信息；
进一步的，所述第一承载建立请求消息中还可以携带所述第一承载对应的DRB的RLC层配置参数。
进一步的，所述第一承载建立请求消息中还可以携带MAC层配置参数，以及物理层 配置参数中的至少一项。
进一步的，所述DRB建立请求中还可以携带有所述DRB的PDCP层配置参数，RLC层配置参数中的至少一项；
进一步的，所述DRB建立请求中还可以MAC层配置参数，以及物理层配置参数中的至少一项。
进一步的，所述PDCP层配置参数，RLC层配置参数，MAC层配置参数，以及物理层配置参数是根据所述Qos Flow指示信息确定的。在本申请实施例中，所述第一承载为DRB对应DU至CU间的承载，所述第一承载也可为隧道。所述DRB为网络侧(包括CU及DU)与UE建立的用于传输业务数据的承载，通常一个DRB的协议层可以包括物理层，MAC层，RLC层，PDCP层，SDAP层等，其中一个DRB对应一个PDCP实体，一个RLC实体，物理层实体，MAC实体，SDAP实体可以由多个DRB共享。
步骤S45：DU根据所述第一承载建立请求，建立CU与DU间的第一承载，且向CU发送第一响应，所述第一响应中携带有所述DU分配的所述第一承载所对应传输层的地址。其中，所述第一承载为所述DRB对应的CU与DU间的部分。
进一步的，所述DU为所述DRB建立新的RLC层实体，应用所述RLC层配置参数，MAC层配置参数，以及物理层配置参数。
步骤S46：UE根据所述DRB建立请求，建立所述DRB，且在所述DRB建立成功后，发送第二响应。
进一步的，所述UE为所述DRB建立新的PDCP层实体，RLC层实体，应用所述PDCP层配置参数，RLC层配置参数，MAC层配置参数，以及物理层配置参数。
步骤S47：CU通过所述DRB将下行业务数据传输至UE。
具体的，在本申请实施例中，所述CU可通过所述第一承载将下行业务数据传输至DU，然后再通过空口将下行业务数据传输至UE。
需要说明的是，上述各步骤中涉及的消息名称，仅作为示例性描述，不构成对本发明的限制。任何其它名称但所实现的功能和/或携带的消息与上述各步骤中涉及的消息相同或相似时，均在本发明保护范围之内。
进一步的，仍可参见图3，CU的功能又可被划分为CU-CP和CU-UP两个节点。通过图3可以看出，在CU-CP和CU-UP相分离后，核心网发送的下行业务数据将首先到达CU-UP，而CU-CP负责业务承载的建立和释放等操作。此时，如何建立和释放承载，正是本申请所要解决的技术问题。
需要说明的是，在图3所示的CU-CP和CU-UP相分离的架构下，所述第一承载具体是指CU-UP至DU间的承载。且在图3所示的网络架构下，实线表示信令传输，虚线表示数据传输。
还需要说明的是，图3所示的通信系统300中所包含的UE的数量和类型仅仅是一种例举，本申请实施例也并不限制于此。譬如，还可以包括更多与基站进行通信的UE，为简明描述，不在附图中一一描述。此外，在如图3所示的通信系统300中，尽管示出了基站30和UE31，但所述通信系统300可以并不限于包括所述基站30和UE31，譬如还可以包括CN32或者用于管理承载建立的设备等，这些对于本领域普通技术人员而言是显而易见的，在此不再详述。
基于图3所示的通信系统300，本申请提供一种建立承载方法的流程，如图5所示，该流程具体为：
步骤S51：CU-CP响应于第一触发消息，向DU发送第一请求消息，所述第一请求消息用于请求DU建立第一承载。
在本申请实施例中，所述CU-CP响应于第一触发消息具体可指，CU-CP接收第一触发消息，然后向DU发送第一请求消息。
在本申请实施例中及本申请各实施例中，，所述第一承载为无线数据承载(data radio bearer，DRB)对应DU至CU-UP间的承载，所述第一承载也可为隧道。所述DRB为网络侧(包括CU及DU)与UE建立的用于传输业务数据的承载。为了便于描述，可将CU-CP向DU所发送的建立承载的请求，称为第一请求消息，将DU至CU-UP间的承载称为第一承载，将DU针对第一请求消息的响应消息称为第一响应消息，CU-CP向CU-UP所发送的请求，称为第二请求消息，将CU-UP针对第二请求消息的响应消息称为第二响应消息。
进一步的，所述第一请求消息中还可以携带所述第一承载对应的DRB的RLC层配置参数。进一步的，所述第一请求消息中还可以携带MAC层配置参数，以及物理层配置参数中的至少一项。
步骤S52：DU根据所述第一请求消息，建立第一承载。
所述DU建立第一承载的过程可具体为为第一承载分配DU侧的传输层地址，为了方便描述，可将第一承载所对应的DU侧的传输层地址，称为第一地址，所述第一地址用于CU-UP通过第一承载向DU发送下行数据。
在本申请实施例中，DU处理物理层以及层2的部分协议栈功能，比如，无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层(physical layer，PHY)等。所述DU建立第一承载的过程还包括，配置第一承载对应的所述DRB对应的DU侧协议栈的参数，如为所述DRB建立新的RLC层实体，应用所述RLC层配置参数，MAC层配置参数，以及物理层配置参数等。
步骤S53：DU向CU-CP发送第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有所述第一地址。
步骤S54：CU-CP向CU-UP发送第二请求消息，所述第二请求消息用于请求CU-UP建立所述第一承载，所述第二请求消息中携带有所述第一地址。
进一步的，所述第二请求中还可以携带所述DRB的PDCP层配置参数。
步骤S55：CU-UP根据所述第二请求，建立第一承载。
CU-UP建立第一承载的过程可具体为：为第一承载分配CU-UP侧的传输层地址。为了方便描述，可将第一承载所对应的CU-UP侧的传输层地址，称为第二地址，所述第二地址用于DU通过第一承载向CU-UP发送上行数据。
在本申请实施例中，CU-UP处理无线高层协议栈功能，比如IP层、SDAP层以及分组数据汇聚协议(packet data convergence protocol，PDCP)层等。CU-UP建立第一承载的过程还可包括：配置所述第一承载对应的所述第DRB对应的CU-UP侧协议栈的参数，如为所述DRB建立新的PDCP层实体，应用所述PDCP层配置参数等。
或者，在本申请实施例中，CU-UP也可预先先为第一承载分配第二地址，而在接收到第二请求中时，配置所述第一承载对应的所述第DRB对应的CU-UP侧协议栈的参数。
可以看出，通过上述步骤S51至步骤S55，可建立CU-UP与DU间的第一承载，且由 于CU-CP向CU-UP发送的第二请求中携带有第一地址，所述第一地址用于CU-UP通过第一承载向DU发送下行数据，因此CU-UP可利用该第一地址，通过第一承载向DU发送下行业务数据，实现下行业务数据的传输。
需要说明的是，在本申请实施例中，所述步骤S51至步骤S55之后，还可包括步骤S56：CU-UP向CU-CP发送第二响应，所述第二响应响应于所述第二请求消息。
图6为本申请实施例提供的一种建立承载的方法流程，该流程主要用于CU-UP向CU-CP发送第一触发消息，且在第一触发消息中携带CU-UP为所述第一承载所分配的第二地址。如图6所示，该流程具体为：
步骤S61：CU-UP向CU-CP发送第一触发消息，所述第一触发消息中携带有所述第一承载所对应的第二地址。
在本申请实施例中，所述第一承载为无线数据承载(data radio bearer，DRB)对应DU至CU-UP间的承载，所述第一承载也可为隧道。所述DRB为网络侧(包括CU及DU)与UE建立的用于传输业务数据的承载。在本申请实施例中，CU-UP可预先为第一承载分配第二地址。
可选的，所述第一触发消息可具体为承载建立请求消息，比如DRB建立请求消息等，具体名称本发明不作限制。
步骤S62：CU-CP向DU发送第一请求消息。
步骤S63：DU根据所述第一请求消息，建立第一承载。
步骤S64：DU向CU-CP发送第一响应消息，所述第一响应消息中携带有第一地址，所述第一响应消息响应于所述第一请求消息。
步骤S65：CU-CP向CU-UP发送第二请求消息，所述第二请求消息中携带有第一地址。
步骤S66：CU-UP根据所述第二请求消息，建立第一承载。
可选的，在本申请实施例中，在步骤S61至步骤S66之后，还可包括步骤S67，具体为：
步骤S67：CU-UP向CU-CP发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
由上可见，在本申请实施例中，通过上述方法，可建立CU-UP和DU间的第一承载，且DU侧获得通过第一承载传输上行数据的第二地址，CU-UP侧获得通过第一传输下行数据的第一地址，那么DU和CU-UP可通过第一承载进行上/下行数据传输，且CU-UP在第一触发消息中携带用于上行数据传输的地址，从而可节省信令开销。
图7为本申请实施例提供的一种建立承载的方法流程，如图7所示，该流程可具体为：
步骤S71：CU-CP接收第一触发消息。
在本申请实施例中，所述第一触发消息可以为核心网节点CN发送的，比如所述第一触发消息可为接入与移动管理功能(access and mobility management function，AMF)节点发送的，所述第一触发消息可以为协议数据单元会话控制资源建立请求消息，再比如，所述第一触消息可为CU-UP发送的，比如，所述第一触发消息可以无线承载建立请求消息等，再比如，所述第一触发消息可以是其它CU-CP发送的，比如，所述第一触发消息可以为无线资源控制恢复请求消息。
步骤S72：CU-CP向DU发送第一请求消息。
步骤S73：DU根据所述第一请求消息，建立第一承载。
步骤S74：DU向CU-CP发送第一响应消息，所述第一响应消息中携带有第一地址，所述第一响应响应于所述第一请求消息。
步骤S75：CU-CP向CU-UP发送第二请求消息，所述第二请求消息中携带有第一地址。
步骤S76：CU-UP根据所述第二请求消息，建立第一承载。
步骤S77：CU-UP向CU-CP发送第二响应消息，所述第二响应消息中响应于第二请求消息，所述第二响应消息中携带有第二地址。
步骤S78：CU-CP向DU发送第三响应消息，所述第三响应消息中携带有第二地址。
由上可见，在本申请实施例中，通过上述方法，可建立CU-UP和DU间的第一承载，且DU侧获得通过第一承载传输上行数据的第二地址，CU-UP侧获得通过第一传输下行数据的第一地址，那么DU和CU-UP侧可进行数据通信。
需要说明的是，在本申请实施例中(比如，上述图5、图6以及图7所示的流程中)，均为CU-CP先向DU发送第一请求消息，且在获得针对第一请求消息的第一响应消息时，再向CU-UP发送第二请求消息，当然所述第一响应消息和所述第二请求消息中均携带有DU为所述第一承载分配的用于传输下行数据的传输层地址，也称为第一地址。而在本申请实施例中，并不限定于CU-CP先向DU发送第一请求消息，再获得第一响应消息中携带的第一地址后，再向CU-UP发送第二请求消息。在本申请的一示例中，CU-CP可先向CU-UP发送第二请求消息，再获得针对第二请求消息的第二响应消息中的第二地址后，所述第二地址用于DU利用第一承载向CU-UP发送上行数据，CU-CP再向CU-UP发送第一请求消息，当然所述第一请求消息中携带有所述第二地址。
进一步，需要说明的是，本申请实施例所提供的方案(比如图5、图6以及图7所示的流程中)，除了可适用于承载建立，也可适用于承载的修改。当适用于承载的修改时，上述第一请求消息的功能可具体为请求DU将当前第一承载修改为第二承载，所述第一地址可具体为DU为第二承载所分配的用于传输下行数据的传输层地址，相应的，第二请求消息的功能可具体为请求CU-UP将当前第一承载修改为第二承载，所述第二地址可具体为CU-UP为第二承载所分配的用于传输上行数据的传输层地址。本申请并不限定对本方案具体应用场景的限定，本领域普通技术人员可知，在不同场景下，与本申请技术方案构思相类似的方案，均在本申请的保护范围内。
更进一步，需要说明的是，在本申请实施例所提供的方案(比如图5、图6以及图7所示的流程中)，第一请求消息用于请求DU建立第一承载，第一响应消息用于响应于第一请求消息，第二请求消息用于请求CU-UP建立第二承载，第二响应消息用于响应于第二请求消息，第一地址用于CU-UP通过所述第一承载向DU发送下行数据，所述第二地址用于所述DU通过所述第一承载向CU-UP发送上行数据。在本申请实施例中，并不对第一请求消息、第二请求消息、第一响应消息、第二响应消息、第一地址以及第二地址的名称进行限定。在不同的无线通信系统和/应用场景中，第一请求消息、第二请求消息、第一响应消息、第二响应消息、第一地址和第二地址可能有不同的名称，比如，在一应用场景中，第一请求消息可称为F1承载建立消息，第二请求消息可称为E1承载建立消息，第一响应消息可称为F1承载建立完成消息，第二响应消息可称为E1承载建立完成消息等。因此，本领域普通技术人员可知，在不同场景和无线通信系统中，上述消息的名称可能不同， 本申请并不限定消息的名称。
下面结合具体的场景，对本申请实施例提供的建立承载的方法，进行详细的介绍。如图8所示，本申请实施例提供一种建立承载的流程，该流程中的协议数据单元会话控制资源建立请求(PDU SESSION RESOURCE SETCU-UP REQUEST)消息，可具体为上述图5、图6以及图7中的第一触发消息；第一F1承载建立消息，可具体为上述图5、图6以及图7中的第一请求消息；第一E1承载建立消息，可具体为上述图5、图6以及图7中的第二请求消息，第一承载对应于CU-UP至DU间的DRB。如图8所示，该流程包括：
步骤S81：核心网节点CN向CU-CP发送协议数据单元会话控制资源建立请求(PDU SESSION RESOURCE SETCU-UP REQUEST)消息。
在本申请实施例中，所述核心网设备可具体为实现会话控制功能的设备，比如，可具体为第五代通信系统中的AMF。
可选的，所述PDU SESSION RESOURCE SETCU-UP REQUEST消息中可携带有协议数据单元会话资源建立列表信元(PDU Session Resource Setup List IE)。所述PDU Session Resource Setup List IE中还进一步包括携带有协议数据单元会话标识信元(PDU Session ID IE)，所述PDU Session ID IE中还进一步包括协议数据单元会话建立请求转换信元(PDU Session Setup Request Transfer IE)，而PDU Session Setup Request Transfer IE进一步包括PDU Session对应的最大比特率，传输层信息，PDU Session类型，要建立的一个或多个服务质量流(QoS Flow)信息，其中QoS Flow信息中包括QoS Flow指示信息，QoS Flow级的QoS参数，Reflective QoS Activation参数等。
步骤S82：CU-CP向DU发送第一F1承载建立消息。
在本申请实施例中，CU-UP可基于PDU SESSION RESOURCE SETCU-UP REQUEST消息中携带的PDU Session的各个QoS Flow相关信息，设置的满足各个QOS Flow的Qos需求的参数，比如，逻辑信道配置参数，RLC层配置参数，MAC层配置参数，PHY层配置参数等。
在本申请实施例中，所述第一F1承载建立消息中携带有包括需要建立的第一承载的列表，以及所述第一承载对应的DRB的RLC层配置参数，逻辑信道配置参数中的至少一项，还可以包括L1、MAC层配置参数和UE标识信息等。所述UE标识信息可具体为UE的标识，也可以为用于标识UE的应用层标识(AP ID)等。
步骤S83：DU根据第一F1承载建立消息，建立第一承载。
步骤S84：DU向CU-CP发送第一响应消息，所述第一响应消息响应于第一F1承载建立消息。
在本申请实施例中，所述第一响应消息中至少携带DU分配的与CU-UP之间传输数据的传输网络层地址，该传输网络层地址用于CU-UP向DU发送下行数据，该传输网络层地址可以是以UE为单位的，也可以是以承载为单位的。为了方便描述，可将该DU分配的传输层地址称为第一地址。
步骤S85：CU-CP向CU-UP发送第一E1承载建立消息。
在本申请实施例中，所述第一E1承载建立消息中包括需要建立的承载的列表，以及SDAP层配置参数，PDCP层配置参数，第一地址，CU-UP与核心网之间的传输层地址，比如与UPF之间的传输层地址，UE标识信息等中的至少一项。可选的，所述UE的标识信息可为UE的标识，也可以为用于标识UE的应用层标识(AP ID)等。
在本申请实施例中，所述SDAP层配置参数可包括所述数据协议会话(PDU Session)的QoS Flow与DRB的映射关系。比如，PDU Session中包括6个QoS Flow，分别为QoS Flow1、QoS Flow2、QoS Flow3、QoS Flow4、QoS Flow5以及QoS Flow6，那么各QoS Flow与DRB的映射关系，可如下所示：
QoS Flow1映射到DRB1；
QoS Flow2映射到DRB2；
QoS Flow3映射到DRB3；
QoS Flow4映射到DRB1；
QoS Flow5暂不映射任何DRB；
QoS Flow6映射到缺省DRB；
其中，QoS Flow5暂不映射任何DRB的含义为：如果QoS Flow5所对应的的数据到了，CU-UP的SDAP层会直接触发向CU-CP发送E1承载建立请求的过程，建立QoS Flow5所对应的的数据的DRB。
QoS Flow6映射到缺省DRB的含义是：如果QoS Flow6所对应的的数据到了，CU-UP的SDAP层会直接触发向CU-CP发送E1承载建立请求的过程，建立QoS Flow6所对应的的数据的DRB；或者如果QoS Flow6所对应的数据到了，CU-UP的SDAP层一方面会将新数据递交给缺省DRB的PDCP层，另一方面触发向CU-CP发送E1承载建立请求的过程；或者如果QoS Flow6所对应的数据到了，CU-UP的SDAP层会将新数据递交给缺省DRB的PDCP层。
在本申请实施例中，由于在图3所示的网络架构下，核心网络节点CN将下行业务数据首先发送至CU-UP，因此SDAP层配置参数的作用为当数据从核心网如UPF传输CU-UP后，CU-UP的SDAP层根据数据中携带的QoS Flow信息，将数据递交给对应的DRB的PDCP实体进行处理。
由于在实际应用中，一个PDU Session包括的各个QoS Flow,并不是总是有数据，有些QoS Flow可能一开始没有数据，因此，在本申请实施例中，并不为PDU Session所包括的所有的QoS Flow均建立DRB，比如，PDU Session中包括6个QoS Flow，分别为QoS Flow1、QoS Flow2、QoS Flow3、QoS Flow4、QoS Flow5以及QoS Flow6，如果QoS Flow5与QoS Flow6开始时并没能数据，那么，可将QoS Flow5配置为“QoS Flow5暂不映射任何DRB”，将QoS Flow6配置为“QoS Flow6映射到缺省DRB”。当然，如果CU-CP中所包括的QoS Flow不需要建立对应的DRB，那么相应的，也不会建立该DRB的PDCP实体，也不会向DU配置对应DRB的L1、L2参数。
步骤S86：CU-UP根据配置参数，建立DU与CU-UP间的承载。
步骤S87：CU-UP向CU-CP发送第二响应消息。
在本申请实施例中，所述第二响应消息中中至少携带CU-UP分配的与DU之间传输数据的传输网络层地址，该传输网络层地址可以是以UE为单位的也可以是以DRB为单位的。该传输网络层地址用于DU向CU CU-UP发送数据。为了方便描述，将CU-UP分配的传输层地址，称为第二地址。
步骤S88：CU-CP向DU发送第三响应消息。
在本申请实施例中，所述第三响应消息中携带有上述第二地址。
可选的，在本申请实施例中，在步骤S81至步骤S88之后，所述方法还可以包括：
步骤S89：CU-CP向UE发送DRB建立消息，为UE配置无线参数。
具体的，所述DRB建立消息包括所述DRB对应的PDCP层配置参数，RLC层配置参数，Mac层配置参数，物理层配置参数中的至少一项。
步骤S810：UE根据所述DRB建立消息，建立DU与UE间的DRB，且在建立所述DRB后，向CU-UP发送第四响应消息，所述第四响应消息响应于所述DRB建立消息。
由上可见，在本申请实施例中，可建立PDU Session中QoS Flow所对应数据的DRB，且CU-UP可获得DU为该DRB对应的承载分配的传输层地址，DU可获得CU-UP为该承载分配的传输层地址，从而使得CU-UP和DU可通过该承载传输QoS Flow所对应的数据。
下面结合具体的应用场景，对对本申请实施例提供的建立承载的方法进行详细介绍。如图9所示，本申请实施例提供一种建立承载的流程，该流程中的E1承载建立请求消息，可具体为上述图5、图6以及图7中的第一触发消息；第一F1承载建立消息，可具体为上述图5、图6以及图7中的第一请求消息；第一E1承载建立消息，可具体为上述图5、图6以及图7中的第二请求消息，第一承载对应于CU-UP至DU间的承载。如图9所示，该流程具体包括：
步骤S91：CN向CU-UP发送下行数据，所述下行数据中携带有QoS Flow指示信息。
可选的，所述CN可具体为UPF。
步骤S92：CU-UP根据所述下行数据中携带的QoS Flow指示信息，判断所述下行数据是否可映射到已建立好的DRB中，如果可以映射到已建立好的DRB中，则执行步骤S93；如果无法映射到已建立好的DRB中，或者只能映射到缺省DRB中，则执行步骤S94。
步骤S93：CU-UP通过已建立的DRB，将下行数据传输至DU，DU通过已建立的DRB，将下行数据传输至UE。
步骤S94：CU-UP向CU-CP发送E1承载建立请求消息，请求CU-CP建立新的DRB用于传输所述下行数据。
需要说明的是，如果同一个UE有多个PDU Session分别有相同的QoS Flow信息，则CU-UP需要在所述承载建立请求消息中携带PDU Session ID信息，以便CU-CP根据PDU Session ID信息确定需要为哪个PDU Session的Qos Flow建立对应的DRB。
步骤S95：CU-CP在接收到所述E1承载建立请求消息，向DU发送第一F1承载建立消息。
在本申请实施例中，所述第一F1承载建立消息中携带有需建立DRB对应的L1、L2参数，具体的参数可上述流程8中的第一F1承载中携带的参数相同，只是各个参数的取值可能有所不同，所述第一F1DRB中携带的参数与需建立DRB对应的Qos Flow参数相对应。
步骤S96：DU根据所述第一F1承载建立请求消息中携带的QoS Flow信息，确定要建立的承载，以及所需要的配置参数。
步骤S97：DU根据所述配置参数，建立对应的承载，并向CU-CP发送第一响应消息。
在本申请实施例中，所述第一响应消息中至少携带DU分配的与CU-UP之间传输数据的传输网络层地址，该传输网络层地址用于CU-UP向DU发送下行数据，该传输网络层地址可以是以UE为单位的，也可以是以承载为单位的，为了方便描述，可将该传输层地址称为第一地址。
步骤S98：CU-CP接收到DU发送的第一响应消息，向CU-UP发送第一E1承载建立 消息。
在本申请实施例中，所述第一E1承载建立消息中至少携带有DU分配的与CU-UP之间传输数据的传输层地址，即第一地址。
步骤S99：CU-UP建立CU-UP与DU间的承载，且向CU-CP发送第二响应消息。
需要说明的，在本申请实施例中，可沿用图6所示的流程方法，可在E1承载建立请求消息中携带CU-UP为DU与CU-UP间分配的用于传输上行数据的传输层地址，即第二地址，且在第一F1承载建立消息中携带所述第二地址。或者，在本申请实施例中，也可沿用图7所示的流程的方法，在第二响应消息中携带所述第二地址，那么整个图9所示的流程，还可包括步骤S910:CU-CP向DU发送第三响应消息，所述第三响应消息中携带有所述第二地址。
步骤S911：CU-CP向UE发送DRB建立消息，为UE配置无线承载相关参数；
步骤S912：UE向CU CU-CP发送第四响应消息，所述第四响应消息响应于所述DRB建立消息。
需要说明的是，在本申请实施例，并不限定步骤S91至步骤S912的先后顺序，如前所述，在本申请实施例中，CU-CP可向先CU-UP发送第一E1承载建立消息，再向DU发送第一F1承载建立消息，也可先向DU发送第一F1承载建立消息，再向CU-UP发送第一E1承载建立消息。
进一步，需要说明的是，在本申请实施例中，DU和CU-CP可位于同一节点，那么在本申请图9所示的流程中，DU和CU CU-CP之间的流程可以省略。同理，当CU-UP与CU-CN位于同一节点时，CU-UP与CN之间的流程可以省略。当CU-UP与DU位于同一节点时，CU-CP与CU-UP和DU之间的流程可以合并。
再进一步，需要说明的是，在本申请实施例中，CU-UP也可能基于接收到的上行数据触发该过程，具体的，UE可能会使用缺省承载将某QoS Flow的数据发送到CU-UP，CU UE的SDAP层会执行类似于接收到下行数据时的操作。在此不作赘述。
基于图3所示的通信系统300，本申请提供一种释放承载方法的流程，如图10所示，该流程具体为：
步骤S101：CU-CP在接收到第二触发消息时，向DU发送第一请求消息。
在本申请实施例中，所述第一请求消息用于请求DU释放第一承载，所述第一承载为DU与CU-UP间的承载，所述第一承载用于DU与CU-UP之间数据交换，所述第一请求消息中携带有所述第一承载的标识。
步骤S102：DU根据所述第一请求消息，释放第一承载。
步骤S104：CU-CP向CU-UP发送第二请求消息，所述第二请求消息用于请求CU-UP释放第一承载，所述第二请求消息中携带有所述第一承载的标识。
步骤S105：CU-UP根据所述第二请求消息，释放第一承载。
由上可见，在本申请实施例中，当CU-CP需求释放一承载时，可具体向DU和CU-UP发送请求消息，以请求DU和CU-UP释放相应的承载即可。
可选的，在本申请图10所示的流程中，在步骤S102之后，还可包括：步骤S103：DU向CU-CP发送第一响应消息，所述第一响应消息响应于所述第一请求消息。在步骤S105之后，还可包括：步骤S106：CU-UP向CU-CP发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
需要说明的是，在本申请图10所示的流程中，并不限定步骤S101至步骤S105执行的先后顺序，比如，在图10所示的流程中，可先执行步骤S102，发送第一请求消息，再执行步骤S104，发送第二请求消息，也可以先执行步骤S104，发送第二请求消息，再执行步骤S102，发送第一请求消息，在此不再赘述。
下面结合具体的应用场景，对本申请实施例提供的释放承载的方法进行详细介绍。如图11所示，所述E1承载释放请求可对应于图10中的第二触发消息，所述第一F1承载释放消息可对应于图10中的第一请求消息，第一F1承载释放响应可对应于图10中的第一响应消息，所述第一E1承载释放消息可对应于图10中的第二请求消息，第一E1承载释放响应可对应于图10中的第二响应消息。如图11所示，该流程具体可为：
步骤S110：CU-UP在确定需要释放某个DRB时，向CU-CP发送E1承载释放请求消息。
在本申请实施例中，在业务进行过程中，CU-UP可监测各DRB的数据到达情况，如根据是否有数据接收过发送，来启动或者重新启动反映DRB数据活跃程度的定时器，比如Inactivity Timer。而当定时器超时后，CU–UP可确定该业务对应的DRB需要释放。所述E1承载释放请求消息中，携带需要释放DRB的标识信息。
步骤S111：CU-CP接收到E1承载释放请求，向DU发送第一F1承载释放消息。
具体的，该第一F1承载释放消息中，可携带需要释放或挂起的第一承载的标识信息。
步骤S112：DU根据所述第一F1承载释放消息，将对应的第一承载释放。
步骤S113：DU向CU-CP发送第一F1承载释放响应。
步骤S114：CU-CP向CU-UP发送第一E1承载释放消息。
步骤S115：CU-UP根据所述第一E1承载释放消息，释放对应的第一承载。
步骤S116：CU-UP向CU-CP发送第一E1承载释放响应。
步骤S117：CU-CP向UE发送DRB释放或RRC释放命令。
在本申请实施例中，如果当前释放的DRB时最后一个DRB时，可以发送RRC释放命令，否则，发送DRB释放命令。
步骤S118：UE向CU-CP发送DRB释放完成或RRC释放完成消息。
需要说明的是，在本申请实施例中，并不限定步骤S111至步骤S117执行的前后顺序。
在本申请实施例中，图10所示的释放承载的方法，可应用于挂起承载的过程中。下面结合具体的场景，对挂起承载的方法进行介绍。如图12所示，本申请实施例提供了一种挂起承载的方法流程，该流程中的DRB可对应于图10中的第一承载，挂起Suspend请求可对应于图10中的第二触发消息，第一请求消息或第二请求消息，Suspend响应消息可对应于图10中的第一响应消息或第二响应消息，SN Transfer消息可对应于图10中的前转数据。如图12所示，该流程可具体为：
步骤S120：CU-UP在确定需要释放某个DRB时，向CU-CP发送E1承载Suspend请求消息。
在本申请实施例中，在业务进行过程中，CU-UP可监测各DRB的数据到达情况，如根据是否有数据接收过发送，来启动或者重新启动反映DRB数据活跃程度的定时器，比如Inactivity Timer。而当定时器超时后，CU–UP可确定该业务对应的DRB需要释放。所述E1承载释放请求消息或Suspend请求消息中，携带需要释放或挂起的DRB的标识信息。
步骤S121：CU-CP接收到Suspend请求，向DU发送Suspend请求。
具体的，该Suspend请求消息中，携带需要挂起的DRB的标识信息。
步骤S122：DU根据所述Suspend请求，将对应的DBR挂起。
步骤S123：DU向CU-CP发送Suspend响应。
步骤S124：CU-CP向CU-UP发送Suspend请求。
具体的，该Suspend请求消息中，携带有需要挂起的DRB的标识信息。
步骤S125：CU-UP根据所述Suspend请求，将对应的DRB挂起。
步骤S126：：CU-UP向CU-CP发送Suspend响应消息。
步骤S127：CU-CP向UE发送Suspend命令或RRC释放命令或DRB释放命令。
在本申请实施例中，如果当前释放的DRB时最后一个DRB时，可以发送Suspend命令或RRC释放命令，否则，发送DRB释放命令。
步骤S128：UE向CU CP发送DRB释放响应消息或Suspend响应消息或RRC响应消息。
可以理解的，在本申请实施例中，并不限定步骤S120至步骤S128的先后执行顺序。
基于图3所示的通信系统300，当UE31处于挂起(Suspend)或无效(Inactive)状态时，本申请实施例还提供一种切换承载的流程。如图13所示，该流程具体包括：
步骤S131：目的CU-CP向目的CU-UP发送第一消息。
步骤S132：目的CU-UP向目的CU-CP发送第一响应消息，所述第一响应消息响应于所述第一消息，所述第一响应消息中携带有第一地址，所述第一地址用于源CU-UP向目的CU-UP发送前转数据。
步骤S133：目的CU-CP向源CU-CP发送第二消息，所述第二消息中携带有第一地址。
步骤S134：源CU-CP向源CU-UP发送第三消息，所述第三消息中携带有所述第一地址。
可选的，在步骤S134之后，还可包括：步骤S135：源CU-UP向源CU-CP发送第二响应消息，所述第二响应消息响应于所述第二消息，
步骤S136：源CU-UP根据所述第一地址向目的CU-UP发送前转数据。
由上可见，在本申请实施例中，当UE处于Suspend或无效Inactive状态时，采用本申请实施例的方法，可成功实现数据的前转。
下面结合具体的应用场景，假设UE进入Suspend或Inactive状态，对本申请实施例提供的切换承载的方法进行详细介绍。如图14所示，提供了一种切换承载的流程，CU-UP1对应于图13中源CU-UP，CU-CP1对应于图13中源CU-CP，CU-UP2对应于图13中的目的CU-UP，CU-CP2对应于图13中的目的CU-CP，第一消息可对应于HandoverIn请求消息，第一响应消息可对应于HandoverIn响应消息，第二消息可对应于Context Retrieval Complete消息，第三消息可对应于HandoverOut请求消息，第二响应消息可对应于HandoverOut响应消息。如图14所示，该流程具体包括：
步骤S141：CU-UP1从核心网节点CN接收下行数据，生成E1承载建立请求消息，请求CU CP1恢复DRB用于传输所述数据。
在本申请实施例中，所述核心网节点CN可具体为UPF。关于上述步骤S141可具体参见上述图9的介绍，在此不再赘述。
步骤S142：CU-CP1确定UE处于Suspend或Inactive状态，则在该UE的RAN寻呼区域内发起RAN寻呼。
具体的，该UE的RAN寻呼区域可以在UE进入该Suspend或Inactive状态时，为UE配置，可以是一个TA区，或者一个小区列表，或者一个RAN区域标识，UE在该状态下，在该RAN寻呼区域内移动时，不需要作切换，不需要通知网络侧，只需要作小区重选即可。
在本申请实施例中，上述UE的RAN寻呼区域可以包括一个CU-CP，也可以包括多个CU-CP。当包括多个CU-CP时，最后为UE服务的CU-CP称为Anchor CU-CP。且当包括多个CU-CP时，Anchor CU-CP向RAN寻呼区域内其它CP发送RAN寻呼消息。在本申请实施例中，为了方便描述，可将Anchor CU-CP称为CU-CP2
RAN寻呼区内各CU-CP接收到RAN寻呼消息后，在各自控制的区域内发起寻呼，具体的，通过各自的DU发送RRC寻呼消息，或者当CU-CP与DU位于相同的节点时，直接发送RRC寻呼消息。
在本申请实施例中，当UE接收到寻呼消息后，向网络侧发送RRC恢复请求(RRC Resume Request)消息。在本申请实施例中，以UE在CU-CP2接入为例，详细说明下述过程：
步骤S143：UE将RRC Resume Request消息通过DU2发送给Cu-CP2。
步骤S144：CU-CP2根据UE发送的RRC Resume Request消息向CU-CP1发送上下文检索请求(Context Retrieval Request)消息。
在本申请实施例中，所述RRC Resume Request消息中包括UE的Resume ID，CU-CP2根据UE发送的RRC Resume Request消息中的Resume ID确定UE的Anchor CU-CP，即CU-CP2，CU并发送Context Retrieval Request消息。
步骤S145：CU-CP1向CU CP2发送Context Retrieval Response消息，主要携带UE的上下文信息。
在本申请实施例中，所述UE的上下文中可包括PDU Session信息，DRB信息，CU UP的传输层地址信息等信息。
步骤S146：CU-CP2建立CU-UP2与DU2间的承载。
在本申请实施例中，CU-CP2建立CU-CP2与DU2间承载的过程，可参见上述图4至图9所记载的方法，在此不再赘述。
步骤S147：CU-CP2与CU-UP2间建立承载。
在本申请的一示例中，CU CP2可向CU UP2发送HandoverIn请求消息，消息中携带UE的相关配置参数，如RB的配置参数；在步骤9中，CU UP2向CU CP2发送HandoverIn响应消息，消息携带Cu UP2为各RB配置的传输层地址等信息。
步骤S148：CU-CP2向CU-CP1发送上下文检索完成(Context Retrieval Complete)消息，里面携带Cu UP2为各RB配置的传输层地址等信息。
步骤S149：CU-CP1向CU-UP1发送越区切换(HandoverOut)请求消息，里面携带Cu UP2为各RB配置的传输层地址等信息。
可选的，在步骤S149之后，还可包括：步骤S1410:CU-UP1可以向CU-CP1回复HandoverOut响应消息。
步骤S1411：CU-UP1向CU-UP2发送SN传输(Transfer)消息。
在本申请实施例中，所述SN Transfer消息里面可携带CU-UP1中各RB的PDCP状态信息，比如上行Counter值，下行Counter值，接收的上行SDU的状态等信息。
具体的，如果CU-UP1与CU-UP2间有接口，则可以直接发送所述SN Status Transfer消息。如果CU-UP1与CU-UP2间没有接口，则通过CU–CP1和CU-CP2发送所述SN Status Transfer消息。通过上述步骤S140，可将CU-UP1的下行数据可以前转给CU-UP2.
步骤S1412：CU-CP2通过DU2向UE发送RRC恢复(RRC Resume)消息。
步骤S1413：UE向CU CP2发送RRC恢复完成(RRC Resume Complete)消息。
步骤S1414：CU-UP1释放与CU-CP1之间的针对此UE的连接；CU-CP1释放与DU1之间针对此UE的连接
由上可见，在本申请实施例中，当UE处于在Suspend及Inactive状态时，且有下行数据时，由CU-UP1触发的信令流程，实现数据前转。
上述本申请提供的实施例中，分别从各个网元本身、以及从各个网元之间交互的角度对本申请实施例提供的建立承载的方法，释放承载的方法以及切换承载的方法进行了介绍。
可以理解的是，各个网元，例如UE、CU-UP，CU-CP等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图15示出了上述实施例所涉及的接入网设备的一种可能的结构示意图，该接入网设备可以是上述实施例所涉及的CU-UP、CU-CP或DU等。
所示接入网设备1500可包括收发器1501,控制器/处理器1502。所述收发器1501可以用于支持网络与上述实施例中的所述的UE之间收发信息，以及支持网络设备之间进行无线电通信，比如支持CU-UP以及CU-CP间的无线电通信等。所述控制器/处理器1502可以用于执行各种用于与UE或其他网络设备通信的功能。在上行链路，来自所述UE的上行链路信号经由天线接收，由收发器1501进行调解，并进一步由控制器/处理器1502进行处理来恢复UE所发送到业务数据和信令信息。在下行链路上，接收来自核心网节点的业务数据和信令消息，且由控制器/处理器1502进行处理，并由收发器1501进行调解来产生下行链路信号，并经由天线发射给UE。所述控制器/处理器1502还用于执行如上述实施例描述的建立承载方法、释放承载的方法，或修改承载的方法，比如，在执行建立承载的方法时，可具体执行响应于第一触发消息，向接入网分布单元设备发送第一请求消息，所述第一请求消息用于请求所述接入网分布单元设备建立第一承载；接收所述接入网分布单元设备发送的第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址；向接入网用户面设备发送第二请求消息，所述第二请求消息用于请求所述接入网用户面设备建立所述第一承载，所述第二请求消息中携带有所述第一地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据等。所述控制器/处理器1502还可以用于执行图4至图14中涉及网络设备的处理过程和/或用于本申请所描述的技术的其他过程。所述接入网设备1500还可以包括存储器1503，可以用于存储接入网设备的程序代码和数据。所述接入网设备1500还可以包括通信单元1504，用于支持接入网设备与其他网络实体进行通信。
可以理解的是，图15仅仅示出了基站的简化设计。在实际应用中，接入网设备可以包含任意数量的发射器，接收器，处理器，控制器，存储器，通信单元等，而所有可以实现本申请的接入网设备都在本申请实施例的保护范围之内。
用于执行本申请实施例中上述接入网设备的控制器/处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
图16示出了一种接入网控制面设备1600，该接入网控制面设备1600可以上述实施例中的CU-CP，包括：
收发单元1601，用于响应于第一触发消息，向接入网分布单元设备发送第一请求消息、接收所述接入网分布单元设备发送的第一响应消息以及向接入网用户面设备发送第二请求消息，所述第一请求消息用于请求所述接入网分布单元设备建立第一承载，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址，所述第二请求消息用于请求所述接入网用户面设备建立所述第一承载，所述第二请求消息中携带有所述第一地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；
处理单元1602，用于生成所述第一请求消息以及所述第二请求消息。
在本申请实施例中，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据，所述第一请求消息中携带有所述第二地址。
在本申请实施例中，所述收发单元1601还用于：接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息。
在本申请实施例中，所述收发单元1601还用于：接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址；向所述接入网分布单元设备发送第三响应消息，所述第三响应消息中携带有所述第二地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
或者，
处理单元1602，用于在接收到第二触发消息时，生成第一请求消息以及第二请求消息；
收发单元1601，用于向接入网分布单元设备发送所述第一请求消息，向接入网用户面设备发送第二请求消息，所述第一请求消息用于请求所述接入网分布单元设备释放第一承载，所述第一承载用于所述接入网分布单元设备与接入网用户面设备之间数据交换，所述第一请求消息中携带有所述第一承载的标识，所述第二请求消息用于请求所述接入网用户面设备释放所述第一承载，所述第二请求消息中携带有所述第一承载的标识。
在本申请实施例中，所述收发单元1601还用于：接收接入网分布单元设备发送的第一响应消息，所述第一响应消息响应于所述第一请求消息；接收接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息。
或者，
处理单元1602，用于生成第一消息和第二消息；
收发单元1601，用于向目的接入网用户面设备发送所述第一消息，接收所述目的接入网用户面设备发送的第一响应消息，向源接入网控制面设备发送第二消息；所述第一响应消息响应于所述第一消息，所述第一响应消息中携带有第一地址，所述第一地址用于源接入网用户面设备向目的接入网用户面设备发送前转数据，所述第三消息中携带有所述第一地址。
或者，
收发单元1601，用于接收目的接入网控制面设备发送的第二消息，所述第二消息中携带有第一地址，所述第一地址用于所述源接入网用户面设备向所述目的接入网控制面设备发送前转数据；
处理单元1602，用于生成第三消息，所述第三消息中携带有所述第一地址；
在本申请实施例中，所述收发单元1602，还用于向源接入网用户面设备发送第三消息。所述收发单元1601还用于：接收所述源接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第三消息。
图17示出了一种接入网分布单元设备1700，该接入网分布单元1700可具体为上述辨例中的DU，包括：
收发单元1701，用于接收接入网控制面设备发送的第一请求消息；
处理单元1702，用于根据所述第一请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载；
在本申请实施例中，收发单元1701，还用于向所述接入网控制面设备发送第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据。
在本申请实施例中，所述第一请求消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
在本申请实施例中，所述收发单元1701还用于：接收接入网控制面设备发送的第三响应消息，所述第三响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
或者，
收发单元1701，用于接收接入网控制面设备发送的第一请求消息，所述第一请求消息中携带有第一承载的标识，所述第一承载用于所述接入网分布单元设备与接入网用户面设备之间数据交换；
处理单元1702，用于根据所述第一承载的标识，释放所述第一承载。
在本申请实施例中，所述收发单元1701还用于：向所述接入网控制面设备发送第一响应消息，所述第一响应消息响应于所述第一请求消息。
图18示出了一种接入网用户面设备1800，该接入网用户面设备1800可具体为上述实施例中的CU-UP，包括：
收发单元1801，用于接收接入网控制面设备发送的第二请求消息，所述第二请求消息中携带有第一地址，所述第一地址为第一承载所对应的第一传输层地址，所述第一地址用 于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；
处理单元1802，用于根据所述第二请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载。
在本申请实施例中，所述收发单元1801还用于：向所述接入网控制面设备发送第一触发消息，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据；向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
在本申请实施例中，所述收发单元1801还用于：向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
或者，
收发单元1801，用于接收接入网控制面设备发送的第二请求消息，所述第二请求消息中携带有第一承载的标识，所述第一承载用于所述接入网分布单元设备与接入网用户面设备之间数据交换；
处理单元1802，用于根据所述第一承载的标识，释放所述第一承载。
在本申请实施例中，所述收发单元1801还用于：向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
或者，
收发单元1801，用于接收源接入网控制面设备发送的第三消息，所述第三消息中携带有第一地址，所述第一地址用于所述源用户面设备向目的用户面设备发送前转数据；
处理单元1802，用于获取前转数据，所述前转数据中携带有终端设备待转移的下行业务数据以及所述下行业务数据的处理信息。
在本申请实施例中，所述收发单元1801，还用于根据所述第一地址，向目的用户面设备发送前转数据。
在本申请实施例中，还提供一种计算机可读存储介质，包括指令，当其在通信设备上运行时，使得上述实施例中的接入网设备(比如CU-UP、CU-CP以及DU等)执行上述实施例中的建立承载的方法、释放承载的方法或修改承载的方法。
本申请实施例还提供一种装置，所述装置与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现上述实施例中的建立承载的方法、释放承载的方法或修改承载的方法。可选的，所述装置可为芯片。
本申请实施例还提供一种通信装置，该通信装置可以是终端设备也可以是电路。该通信装置可以用于执行上述方法实施例中由终端设备所执行的动作。
当该通信装置为终端设备时，图19示出了一种简化的终端设备的结构示意图。便于理解和图示方便，图19中，终端设备以手机作为例子。如图19所示，终端设备包括处理器、存储器、射频电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对终端设备进行控制，执行软件程序，处理软件程序的数据等。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显 示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。需要说明的是，有些种类的终端设备可以不具有输入输出装置。
当需要发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。为便于说明，图19中仅示出了一个存储器和处理器。在实际的终端设备产品中，可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置，也可以是与处理器集成在一起，本申请实施例对此不做限制。
在本申请实施例中，可以将具有收发功能的天线和射频电路视为终端设备的收发单元，将具有处理功能的处理器视为终端设备的处理单元。如图19所示，终端设备包括收发单元1910和处理单元1920。收发单元也可以称为收发器、收发机、收发装置等。处理单元也可以称为处理器，处理单板，处理模块、处理装置等。可选的，可以将收发单元1910中用于实现接收功能的器件视为接收单元，将收发单元1910中用于实现发送功能的器件视为发送单元，即收发单元1910包括接收单元和发送单元。收发单元有时也可以称为收发机、收发器、或收发电路等。接收单元有时也可以称为接收机、接收器、或接收电路等。发送单元有时也可以称为发射机、发射器或者发射电路等。
应理解，收发单元1910用于执行上述方法实施例中终端设备侧的发送操作和接收操作，处理单元1920用于执行上述方法实施例中终端设备上除了收发操作之外的其他操作。
例如，在一种实现方式中，收发单元1910用于执行图4中的S46中发送第二响应的操作，和/或收发单元1910还用于执行本申请实施例中终端设备侧的其他收发步骤。处理单元1920，用于执行图4中的S46中建立DRB的操作，和/或处理单元1920还用于执行本申请实施例中终端设备侧的其他处理步骤。
再例如，在另一种实现方式中，收发单元1910用于执行图8中S810终端设备侧发送第四响应消息的操作，和/或收发单元1910还用于执行本申请实施例中终端设备侧的其他收发步骤。处理单元1920用于执行图8中的S810中建立DU与UE间的DRB的操作，和/或处理单元1920还用于执行本申请实施例中终端设备侧的其他处理步骤。
又例如，在再一种实现方式中，收发单元1910用于执行图9中S93终端设备侧通过已建立的DRB，接收下行数据的操作，以及S911中接收DRB建立消息的操作，以及S912中发送第四响应消息的操作，和/或收发单元1910还用于执行本申请实施例中终端设备侧的其他收发步骤。
又例如，在再一种实现方式中，收发单元1910用于执行图11中S117中终端设备侧接收DRB释放或RRC释放命令的操作，以及S118中发送DRB释放完成或RRC释放完成消息的操作，和/或收发单元1910还用于执行本申请实施例中终端设备侧的其他收发步骤。
又例如，在再一种实现方式中，收发单元1910用于执行图12中S127中终端设备侧的接收操作，或S128中的发送操作，和/或收发单元1910还用于执行本申请实施例中终端设备侧的其他收发步骤。
当该通信装置为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输 入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。
本实施例中的通信装置为终端设备时，可以参照图20所示的设备。作为一个例子，该设备可以完成类似于图15中控制器/处理器1502的功能。在图20中，该设备包括处理器2010，发送数据处理器2020，接收数据处理器2030。上述实施例中的处理单元1602/处理单元1702/处理单元1802可以是图20中的该处理器2010，并完成相应的功能。上述实施例中的收发单元1610/收发单元1701/收发单元1801可以是图20中的发送数据处理器2020，和/或接收数据处理器2030。虽然图20中示出了信道编码器、信道解码器，但是可以理解这些模块并不对本实施例构成限制性说明，仅是示意性的。
图21示出本实施例的另一种形式。处理装置2100中包括调制子系统、中央处理子系统、周边子系统等模块。本实施例中的通信装置可以作为其中的调制子系统。具体的，该调制子系统可以包括处理器2103，接口2104。其中处理器2103完成上述处理单元1602/处理单元1702/处理单元1802的功能，接口2104完成上述收发单元1610/收发单元1701/收发单元18010的功能。作为另一种变形，该调制子系统包括存储器2106、处理器2103及存储在存储器2106上并可在处理器上运行的程序，该处理器2103执行该程序时实现上述方法实施例中终端设备侧的方法。需要注意的是，所述存储器2106可以是非易失性的，也可以是易失性的，其位置可以位于调制子系统内部，也可以位于处理装置2100中，只要该存储器2106可以连接到所述处理器2103即可。
作为本实施例的另一种形式，提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行上述方法实施例中终端设备侧的方法。
作为本实施例的另一种形式，提供一种包含指令的计算机程序产品，该指令被执行时执行上述方法实施例中终端设备侧的方法。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (33)

  1. 一种建立承载的方法，其特征在于，包括：
    接入网控制面设备响应于第一触发消息，向接入网分布单元设备发送第一请求消息，所述第一请求消息用于请求所述接入网分布单元设备建立第一承载；
    所述接入网控制面设备接收所述接入网分布单元设备发送的第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址；
    所述接入网控制面设备向接入网用户面设备发送第二请求消息，所述第二请求消息用于请求所述接入网用户面设备建立所述第一承载，所述第二请求消息中携带有所述第一地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据，所述第一请求消息中携带有所述第二地址。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述接入网控制面设备接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述接入网控制面设备接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址；
    所述接入网控制面设备向所述接入网分布单元设备发送第三响应消息，所述第三响应消息中携带有所述第二地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  5. 一种建立承载的方法，其特征在于，包括：
    接入网分布单元设备接收接入网控制面设备发送的第一请求消息；
    所述接入网分布单元设备根据所述第一请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载；
    所述接入网分布单元设备向所述接入网控制面设备发送第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据。
  6. 根据权利要求5所述的方法，其特征在于，所述第一请求消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  7. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述接入网分布单元设备接收接入网控制面设备发送的第三响应消息，所述第三响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第 二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  8. 一种建立承载的方法，其特征在于，包括：
    接入网用户面设备接收接入网控制面设备发送的第二请求消息，所述第二请求消息中携带有第一地址，所述第一地址为第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；
    所述接入网用户面设备根据所述第二请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述接入网用户面设备向所述接入网控制面设备发送第一触发消息，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据；
    所述接入网用户面设备向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
  10. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述接入网用户面设备向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  11. 一种接入网控制面设备，其特征在于，包括：
    收发器，用于响应于第一触发消息，向接入网分布单元设备发送第一请求消息、接收所述接入网分布单元设备发送的第一响应消息以及向接入网用户面设备发送第二请求消息，所述第一请求消息用于请求所述接入网分布单元设备建立第一承载，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址，所述第二请求消息用于请求所述接入网用户面设备建立所述第一承载，所述第二请求消息中携带有所述第一地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；
    处理器，用于生成所述第一请求消息以及所述第二请求消息。
  12. 根据权利要求11所述的设备，其特征在于，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据，所述第一请求消息中携带有所述第二地址。
  13. 根据权利要求12所述的设备，其特征在于，所述收发器还用于：
    接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息。
  14. 根据权利要求11所述的设备，其特征在于，所述收发器还用于：
    接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址；
    向所述接入网分布单元设备发送第三响应消息，所述第三响应消息中携带有所述第二地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  15. 一种接入网分布单元设备，其特征在于，包括：
    收发器，用于接收接入网控制面设备发送的第一请求消息；
    处理器，用于根据所述第一请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载；
    所述收发器，还用于向所述接入网控制面设备发送第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据。
  16. 根据权利要求15所述的设备，其特征在于，所述第一请求消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  17. 根据权利要求15所述的设备，其特征在于，所述收发器还用于：
    接收接入网控制面设备发送的第三响应消息，所述第三响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  18. 一种接入网用户面设备，其特征在于，包括：
    收发器，用于接收接入网控制面设备发送的第二请求消息，所述第二请求消息中携带有第一地址，所述第一地址为第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；
    处理器，用于根据所述第二请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载。
  19. 根据权利要求18所述的设备，其特征在于，所述收发器还用于：
    向所述接入网控制面设备发送第一触发消息，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据；
    向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
  20. 根据权利要求18所述的设备，其特征在于，所述收发器还用于：
    向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  21. 一种接入网控制面设备，其特征在于，包括：
    收发单元，用于响应于第一触发消息，向接入网分布单元设备发送第一请求消息、接收所述接入网分布单元设备发送的第一响应消息以及向接入网用户面设备发送第二请求消息，所述第一请求消息用于请求所述接入网分布单元设备建立第一承载，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所 述第一承载所对应的第一传输层地址，所述第二请求消息用于请求所述接入网用户面设备建立所述第一承载，所述第二请求消息中携带有所述第一地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；
    处理单元，用于生成所述第一请求消息以及所述第二请求消息。
  22. 根据权利要求21所述的设备，其特征在于，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据，所述第一请求消息中携带有所述第二地址。
  23. 根据权利要求22所述的设备，其特征在于，所述收发单元还用于：
    接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息。
  24. 根据权利要求21所述的设备，其特征在于，所述收发单元还用于：
    接收所述接入网用户面设备发送的第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址；
    向所述接入网分布单元设备发送第三响应消息，所述第三响应消息中携带有所述第二地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  25. 一种接入网分布单元设备，其特征在于，包括：
    收发单元，用于接收接入网控制面设备发送的第一请求消息；
    处理单元，用于根据所述第一请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载；
    所述收发单元，还用于向所述接入网控制面设备发送第一响应消息，所述第一响应消息响应于所述第一请求消息，所述第一响应消息中携带有第一地址，所述第一地址为所述第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据。
  26. 根据权利要求25所述的设备，其特征在于，所述第一请求消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  27. 根据权利要求25所述的设备，其特征在于，所述收发单元还用于：
    接收接入网控制面设备发送的第三响应消息，所述第三响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  28. 一种接入网用户面设备，其特征在于，包括：
    收发单元，用于接收接入网控制面设备发送的第二请求消息，所述第二请求消息中携带有第一地址，所述第一地址为第一承载所对应的第一传输层地址，所述第一地址用于所述接入网用户面设备通过所述第一承载向所述接入网分布单元设备发送下行数据；
    处理单元，用于根据所述第二请求消息，建立第一承载，所述第一承载为所述接入网分布单元设备与接入网用户面设备间的承载。
  29. 根据权利要求28所述的设备，其特征在于，所述收发单元还用于：
    向所述接入网控制面设备发送第一触发消息，所述第一触发消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据；
    向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息。
  30. 根据权利要求28所述的设备，其特征在于，所述收发单元还用于：
    向所述接入网控制面设备发送第二响应消息，所述第二响应消息响应于所述第二请求消息，所述第二响应消息中携带有第二地址，所述第二地址为所述第一承载所对应的第二传输层地址，所述第二地址用于所述接入网分布单元设备通过所述第一承载向所述接入网用户面设备发送上行数据。
  31. 一种计算机可读存储介质，其特征在于，包括指令，当其在通信设备上运行时，使得所述通信设备执行如权利要求1至10任一项所述的方法。
  32. 一种装置，其特征在于，所述装置与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现如权利要求1至10任一项所述的方法。
  33. 一种通信装置，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序，其特征在于，所述处理器执行所述程序时实现权利要求1至10中任一项所述的通信方法。
PCT/CN2018/107833 2017-09-28 2018-09-27 一种建立承载的方法及设备 WO2019062794A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710900044.3 2017-09-28
CN201710900044.3A CN109587824A (zh) 2017-09-28 2017-09-28 一种建立承载的方法及设备

Publications (1)

Publication Number Publication Date
WO2019062794A1 true WO2019062794A1 (zh) 2019-04-04

Family

ID=65900662

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107833 WO2019062794A1 (zh) 2017-09-28 2018-09-27 一种建立承载的方法及设备

Country Status (2)

Country Link
CN (1) CN109587824A (zh)
WO (1) WO2019062794A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021179245A1 (en) * 2020-03-12 2021-09-16 Qualcomm Incorporated Small data transmissions in an inactive state to disaggregated base stations

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114258151A (zh) * 2020-09-21 2022-03-29 华为技术有限公司 一种计算数据传输方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541109A (zh) * 2008-03-19 2009-09-23 大唐移动通信设备有限公司 服务网关的s1接口用户面地址信息获取方法及通信设备
CN101835131A (zh) * 2009-03-10 2010-09-15 华为技术有限公司 一种数据本地交换方法、装置和系统
CN105338655A (zh) * 2014-06-19 2016-02-17 北京三星通信技术研究有限公司 一种用户平面承载建立的方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102547848B (zh) * 2011-01-04 2015-08-05 华为技术有限公司 一种处理业务数据流的方法和装置
CN106162730B (zh) * 2016-07-12 2019-11-15 上海华为技术有限公司 一种通信的方法、设备及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541109A (zh) * 2008-03-19 2009-09-23 大唐移动通信设备有限公司 服务网关的s1接口用户面地址信息获取方法及通信设备
CN101835131A (zh) * 2009-03-10 2010-09-15 华为技术有限公司 一种数据本地交换方法、装置和系统
CN105338655A (zh) * 2014-06-19 2016-02-17 北京三星通信技术研究有限公司 一种用户平面承载建立的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "TP for Bearer Management over F1 to 38.473", 3GPP TSG RAN WG3 NR ADHOC R3-172192, 29 June 2017 (2017-06-29), XP051302138 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021179245A1 (en) * 2020-03-12 2021-09-16 Qualcomm Incorporated Small data transmissions in an inactive state to disaggregated base stations

Also Published As

Publication number Publication date
CN109587824A (zh) 2019-04-05

Similar Documents

Publication Publication Date Title
TWI754140B (zh) 處理qos 流的方法及使用者設備
TWI665929B (zh) 處理在長期演進網路端及第五代網路端間的移動性的裝置及方法
WO2021026906A1 (zh) 通信方法、通信装置、计算机存储介质及通信系统
WO2018006253A1 (zh) 一种无线链路失败处理方法、相关设备及通信系统
CN111149419B (zh) 用于rrc恢复/暂停时的nr pdcp保留的方法和设备
US11284468B2 (en) Suspending/resuming measurements in RRC inactive state
CN108282906B (zh) 处理移动性中的分组数据网络连接的装置及方法
US11115880B2 (en) Path switch method between LTE and 5G node
US20200120572A1 (en) Methods and Units in a Network Node for Handling Communication with a Wireless Device
CN108289314B (zh) 处理移动性中的协议数据单元连线的装置及方法
TWI682682B (zh) 處理完全組態的裝置及方法
CN107113535B (zh) 用于pros直接发现的承载管理
TWI699985B (zh) 處理協定資料單元會議及網路切片的裝置及方法
CN111345074A (zh) 与ue非活动有关的方法、装置和系统
WO2019196833A1 (zh) 一种通信方法、装置、系统及存储介质
WO2018014154A1 (zh) 一种rrc连接重建方法和装置
WO2021215979A1 (en) Methods and nodes in integrated access backhaul networks
JP2022544501A (ja) サイドリンクｒｒｃ手順
US20230403623A1 (en) Managing sidelink information, configuration, and communication
WO2019062794A1 (zh) 一种建立承载的方法及设备
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2022198597A1 (zh) 小区重选场景下的数据传输方法、装置、设备及存储介质
US20230133792A1 (en) Handling of collision between pdu session establishment and modification procedure
WO2024065137A1 (zh) 配置信息获取方法, 配置信息转发方法以及终端设备

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

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

Country of ref document: EP

Kind code of ref document: A1