WO2019214384A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2019214384A1
WO2019214384A1 PCT/CN2019/081948 CN2019081948W WO2019214384A1 WO 2019214384 A1 WO2019214384 A1 WO 2019214384A1 CN 2019081948 W CN2019081948 W CN 2019081948W WO 2019214384 A1 WO2019214384 A1 WO 2019214384A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
ran
terminal device
bearer
ran device
Prior art date
Application number
PCT/CN2019/081948
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 WO2019214384A1 publication Critical patent/WO2019214384A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.
  • V2X vehicle to everything
  • a communication link needs to be established first.
  • the communication link includes not only a communication link between the two terminal devices and a radio access network (RAN) device, but also a communication link between the radio access network device and the core network device. And a communication link between the core network device and the V2X service server.
  • RAN radio access network
  • the sender can send the data packet to the first RAN device serving the sender, and then the first RAN device sends the data packet to the V2X service server via the core network device, and then the V2X.
  • the service server sends the data packet to the second RAN device serving the receiving end via the core network device, and finally the second RAN device sends the data packet to the receiving end.
  • the present application provides a communication method and apparatus for solving the problem that the existing solution has a large delay in realizing data transmission between terminal devices.
  • the present application provides a communication method, in which a first terminal device may send a service identifier and a service quality requirement of a service corresponding to the service identifier to the first RAN device, and the first RAN device may be based on the The service identity and/or the quality of service requirement establishes a first bearer with the first terminal device and establishes a second bearer with the second RAN device based on the service identity and/or the quality of service requirement.
  • the first bearer and/or the second bearer are used to transmit a data packet of a service corresponding to the service identifier performed between the first terminal device and the second terminal device, where the second RAN device refers to the The second terminal device provides a serving RAN device.
  • the RAN device can establish a bearer between the RAN device and the terminal device and a bearer between the RAN device based on the service identifier and the corresponding quality of service requirement, triggered by the terminal device.
  • the data packet can be directly transmitted to the terminal device of the peer end through the bearer between the RAN device and the terminal device, and the bearer between the RAN device, so that the data packet can be forwarded without going through the core network device, and the data packet does not need to be established.
  • a communication link for transmitting data packets is established between the RAN device and the core network device. Not only can the time for establishing a communication link for transmitting data packets be saved, but also the delay in the transmission of data packets can be reduced.
  • the service identifier may include a destination address, and the destination address may be used by at least one terminal device to participate in a service corresponding to the service identifier.
  • the quality of service requirements of the service corresponding to the service identifier may include a first indicator for characterizing the delay requirement of the service, a second indicator for characterizing the reliability requirement of the service, and the like.
  • the service quality requirement may include a prose per-packet priority (PPPP) and a prose per-packet reliability (PPPR) when the service corresponding to the service identifier is a V2X service.
  • the service identifier and/or the quality of service requirement may be carried in a control indication sent by the first terminal device to the first RAN device, where the control indication is used to indicate that the first RAN device is the service Identifying that the corresponding service establishes a first bearer with the first terminal device.
  • the first bearer and/or the terminal device is established according to the foregoing method.
  • Second bearer For example, if the quality of service requirement is represented by PPPP and PPPR, the first RAN device may determine the service of the service corresponding to the service identifier when the received PPPP is lower than the first threshold and the PPPR is higher than the second threshold. The quality requirement is low latency and high reliability requirement, and then the first bearer and/or the second bearer are established for the terminal device according to the above method.
  • the first RAN device may receive the authorization information of the first terminal device from the core network device, where the authorization information includes an authorized service identifier of the service that the first terminal device has been authorized, And a quality of service requirement when the first terminal device executes the authorized service.
  • the first RAN device may be configured to include the service identifier in the authorized service identifier, and the service quality requirement corresponding to the service identifier matches the quality of service requirement from the first terminal device, The first bearer between a terminal device.
  • the RAN device may obtain and store the authorization information about the terminal device from the core network device in advance, after the subsequent RAN device receives the service identifier from the terminal device and the service quality requirement of the service corresponding to the service identifier,
  • the authorization information of the locally stored terminal device can be directly matched with the received related service information from the terminal device to determine whether to establish a radio bearer for the terminal device, and the process of establishing the radio bearer can be avoided without the core network device participating, thereby avoiding The core network controls the delay effect when establishing a radio bearer.
  • the first endpoint corresponding to the destination address may be configured. And identifying, after determining that the second RAN device records the destination address, acquiring a second endpoint identifier corresponding to the destination address configured by the second RAN device.
  • the first RAN device may use the first endpoint identifier and/or the second endpoint identifier to identify the second bearer after establishing the second bearer with the second RAN device.
  • the RAN device stores the destination address, and the destination address can identify the services supported by the terminal device within the jurisdiction of the RAN device, and the RAN devices can exchange the respective stored destination addresses, and when it is determined that the same destination address exists,
  • the bearers between the RAN devices can be established based on the destination address.
  • the bearer between the established RANs may be identified by the endpoint identifier corresponding to the destination address, and the subsequent RAN device only needs to identify the endpoint identifier when forwarding the data packet, and then the data may be transmitted through the bearer corresponding to the endpoint identifier. package.
  • the second RAN device is also based on the second terminal
  • the service identifier and the quality of service requirement of the device establish a radio bearer with the second terminal device, and the bearer between the first terminal device and the second terminal device can be established between the terminal device and the RAN device, and the RAN device
  • the bearer between the packets is transmitted. Subsequently, as the first terminal device moves, handover between the RAN devices may occur, and as the RAN device switches, the bearer for transmitting the data packet needs to be updated.
  • An implementation for updating a bearer for transmitting a data packet is:
  • the first terminal device may send a measurement report to the first RAN device, where the measurement report carries a handover indication, where the handover indication includes the service identifier, where the handover indication is used to indicate that the first RAN device performs the terminal device
  • the service corresponding to the service identifier performs switching between RAN devices.
  • the first RAN device determines, after the first terminal device performs the service corresponding to the service identifier, that the first RAN device needs to be switched to the third RAN device by using the service identifier that is carried in the measurement report, to the third RAN.
  • the device sends a first handover request, where the first handover request includes the service identifier and/or the quality of service requirement, and the service identifier and/or the quality of service requirement is used to indicate that the third RAN device is established with the first And a third bearer between the terminal devices, where the third bearer is used to transmit the data packet sent by the first terminal device to the third RAN device.
  • the first handover request may further include a second endpoint identifier of the second RAN device, and a first communication address of the second RAN device, where the first communication address is the first RAN device Obtained when the second bearer is established.
  • the second endpoint identifier and/or the first communication address is used to indicate that the third RAN device establishes a fourth bearer with the second RAN device, where the fourth bearer is used to transmit the third RAN device to The data packet sent by the second RAN device from the first terminal device.
  • the first terminal device may send a measurement report to the first RAN device, where the measurement report carries a handover indication, where the handover indication includes the service identifier, where the handover indication is used to indicate that the first RAN device performs the terminal device
  • the service corresponding to the service identifier performs switching between RAN devices.
  • the first RAN device determines, after the first terminal device performs the service corresponding to the service identifier, that the first RAN device needs to be handed over to the fourth RAN device by using the service identifier that is carried in the measurement report, to the fourth RAN.
  • the device sends a second handover request.
  • the second handover request includes the service identifier and/or the quality of service requirement, where the service identifier and/or the quality of service requirement is used to indicate that the fourth RAN device establishes a fifth relationship with the first terminal device.
  • the fifth bearer is configured to transmit the data packet sent by the fourth RAN device to the first terminal device from the second terminal device.
  • the first RAN device may further receive a second communication address of the fourth RAN device from the fourth RAN device, and a third endpoint corresponding to the destination address of the fourth RAN device configuration. And the first RAN device sends the second communication address and the third endpoint identifier to the second RAN device.
  • the second communication address and the third endpoint identifier are used to indicate that the second RAN device establishes a sixth bearer with the fourth RAN device, where the sixth bearer is used to transmit the second RAN device to the first The data packet sent by the fourth RAN device from the second terminal device.
  • the first RAN device may further establish, according to the received second communication address and the third endpoint identifier, a seventh bearer with the fourth RAN device, where the seventh bearer is used for transmitting The data packet that the first RAN device has sent to the fourth RAN device that has been received from the second terminal device but has not been sent yet.
  • an implementation manner of updating the bearer for transmitting the data packet is:
  • the first terminal device sends a measurement report to the first RAN device, where the measurement report carries a handover indication, where the handover indication includes the service identifier, where the handover indication is used to indicate that the first RAN device is configured for the terminal device
  • the service corresponding to the service identifier performs switching between RAN devices.
  • the first RAN device determines, after the first terminal device performs the service corresponding to the service identifier, that the first RAN device needs to be handed over to the fifth RAN device by using the service identifier that is carried in the measurement report, to the fifth RAN.
  • the device sends a third handover request.
  • the third handover request includes the service identifier and/or the service quality requirement, where the service identifier and/or the service quality requirement is used to indicate that the fifth RAN device establishes an eighth relationship with the first terminal device.
  • the eighth bearer is configured to transmit the data packet sent by the first terminal device to the fifth RAN device, and the data packet sent by the fifth RAN device to the first terminal device from the second terminal device .
  • the third handover instruction further includes a second endpoint identifier of the second RAN device, and a first communication address of the second RAN device, where the first communication address is that the first RAN device is Obtained when the second bearer is established.
  • the second endpoint identifier and the first communication address are used to indicate that the fifth RAN device establishes a ninth bearer with the second RAN device, where the ninth bearer is used to transmit the fifth RAN device to the second RAN
  • the first RAN device may further receive a third communication address of the fifth RAN device sent by the fifth RAN device, and a fourth endpoint identifier corresponding to the destination address configured by the fifth RAN device. .
  • the first RAN device may send the third communication address and the fourth endpoint identifier to the second RAN device, where the third communication address and the fourth endpoint identifier are used to indicate the second RAN
  • the device establishes a tenth bearer with the fifth RAN device, where the tenth bearer is used to transmit the data packet sent by the second RAN device from the second terminal device to the fifth RAN device.
  • the present application provides a communication device, the communication device having the function of implementing the first RAN device involved in the foregoing first aspect, for example, the communication device includes the first RAN device performing the above first aspect
  • the functions or modules or units or means can be implemented by software, or by hardware, or by corresponding software implementation by hardware.
  • the communication device comprises a processing unit, a transmitting unit and a receiving unit, and the functions performed by the processing unit, the transmitting unit and the receiving unit may correspond to the steps performed by the first RAN device involved in the first aspect above. I will not repeat them here.
  • the communication device includes a processor, and may further include a transceiver for transmitting and receiving signals, and the processor executes program instructions to perform the above first aspect and the first aspect.
  • the communication device includes a processor, and may further include a transceiver for transmitting and receiving signals, and the processor executes program instructions to perform the above first aspect and the first aspect.
  • the communication device may further comprise one or more memories for coupling with the processor, which hold necessary computer program instructions and/or data for implementing the functions of the first RAN device involved in the first aspect above.
  • the one or more memories may be integrated with the processor or may be separate from the processor. This application is not limited.
  • the processor may execute the computer program instructions stored by the memory to perform the first aspect and the method performed by the first RAN device in any of the possible designs or implementations of the first aspect.
  • the present application provides a communication device, where the communication device is provided with a function of implementing the first terminal device related to the first aspect, for example, the communication device includes the first terminal device performing the foregoing first aspect.
  • the modules or units or means corresponding to the steps may be implemented by software, or by hardware, or by corresponding software implementation by hardware.
  • the communication device comprises a processing unit, a transmitting unit and a receiving unit, and the functions performed by the processing unit, the transmitting unit and the receiving unit may correspond to the steps performed by the first terminal device involved in the first aspect above. I will not repeat them here.
  • the communication device includes a processor, and may further include a transceiver for transmitting and receiving signals, and the processor executes program instructions to perform the above first aspect and the first aspect.
  • the communication device may further comprise one or more memories for coupling with the processor, which hold necessary computer program instructions and/or data for implementing the functions of the first terminal device involved in the first aspect above.
  • the one or more memories may be integrated with the processor or may be separate from the processor. This application is not limited.
  • the processor may execute the computer program instructions stored by the memory to perform the first aspect and the method performed by the first terminal device in any of the possible designs or implementations of the first aspect.
  • the present application provides a chip, the chip may be in communication with a memory, or the chip includes a memory, and the chip executes program instructions stored in the memory to implement the above-mentioned first aspect The corresponding function of the first RAN device or the first terminal device.
  • the present application provides a computer storage medium storing computer readable instructions, when the computer readable instructions are executed, such that the first RAN involved in the first aspect described above is implemented The corresponding function of the device or the first terminal device.
  • the present application further provides a computer program product comprising a software program, when run on a computer, to implement the first RAN device or the first terminal device involved in the above first aspect The corresponding function.
  • the present application further provides a communication system, including the first RAN device involved in the above first aspect, and/or the second RAN device, and/or Terminal Equipment.
  • the terminal device may include the first terminal device and the second terminal device involved in the foregoing first aspect.
  • FIG. 1 is a network architecture diagram of a possible communication system provided by the present application.
  • FIG. 2 is a schematic flowchart of a communication method according to an embodiment of the present application.
  • 3A is a schematic flowchart 1 of establishing a first bearer according to an embodiment of the present application
  • 3B is a schematic flowchart 2 of establishing a first bearer according to an embodiment of the present application
  • 4A is a schematic diagram 1 of a second bearer according to an embodiment of the present application.
  • FIG. 4B is a second schematic diagram of a second bearer according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart of establishing a second bearer according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram 1 of an application scenario of data packet transmission according to an embodiment of the present application.
  • FIG. 6B is a schematic diagram 2 of an application scenario of data packet transmission according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of a switching scenario 1 according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of updating a communication link for transmitting a data packet in a handover scenario 1 according to an embodiment of the present disclosure
  • FIG. 9 is a schematic diagram of a handover scenario 2 according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic flowchart of updating a communication link for transmitting a data packet in a handover scenario 2 according to an embodiment of the present disclosure
  • FIG. 11 is a schematic diagram of a handover scenario 3 according to an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of updating a communication link for transmitting a data packet in a handover scenario 3 according to an embodiment of the present disclosure
  • FIG. 13 is a schematic diagram 1 of a communication device according to an embodiment of the present disclosure.
  • FIG. 14 is a second schematic diagram of a communication device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram 1 of another communication device according to an embodiment of the present disclosure.
  • FIG. 16 is a second schematic diagram of another communication apparatus according to an embodiment of the present disclosure.
  • LTE long term evolution
  • 5th generation 5th generation
  • 5G fifth generation
  • Figure 1 exemplarily shows a network architecture diagram of one possible communication system.
  • the network architecture includes a terminal device, a RAN device, and a core network device.
  • the core network device in the network architecture may also be connected to an external data network.
  • the terminal device can be used to access the RAN device deployed by the operator through the wireless air interface, and then access the external data network through the core network device.
  • the terminal device may also be referred to as a user equipment (UE), such as a mobile phone, a car network terminal, a computer, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (wireless local Loop, WLL) station, personal digital assistant (PDA), laptop computer, handheld communication device, handheld computing device, satellite wireless device, wireless modem card, set top box (STB), Any device such as customer premise equipment (CPE) that can be used for communication on the above communication system.
  • UE user equipment
  • PDA personal digital assistant
  • STB set top box
  • CPE customer premise equipment
  • the RAN device can be used to implement functions such as wireless physical layer functions, radio resource management, radio access control, and mobility management.
  • the RAN device may be a base station in an LTE system or an evolved LTE system, such as a Node B (NB), an evolved Node B (eNB), or an access node in a 5G system (access) Point, AP), next generation Node B (gNB), next generation evolved Node B (ng-eNB, gNB), transmission and reception point (TRP), transmission point (TP) Or some other access node, etc.
  • NB Node B
  • eNB evolved Node B
  • AP next generation Node B
  • ng-eNB next generation evolved Node B
  • TRP transmission and reception point
  • TP transmission point Or some other access node, etc.
  • the core network device may include, but is not limited to, a management device and a gateway device, wherein the management device may be used for registration, security authentication, mobility management, and location management of the terminal device, and the gateway device may be used to establish, maintain, release, and terminate the terminal device.
  • the transmission channel between the two can also forward the data packet when the communication between the terminal device and the external data network is performed on the transmission channel.
  • the data network may include network devices (eg, servers, routers, etc.), and the data network may be used to provide a variety of data service services, such as V2X services, for the terminal devices.
  • network devices eg, servers, routers, etc.
  • V2X services a variety of data service services, such as V2X services
  • FIG. 1 is only an exemplary network architecture diagram.
  • the network architecture may also include other network element devices or functional units, which is not limited in this application.
  • the terminal device when data transmission needs to be performed between terminal devices, in the existing solution, the terminal device first initiates a registration process to the core network device, and the core network is The terminal device establishes and maintains a communication link for transmitting data packets.
  • the communication link specifically includes a communication link between the RAN device and the terminal device established by the RAN device, a communication link established between the core network device and the RAN device, and a server in the core network device and the data network. Communication links, etc.
  • the data packet sent by the terminal device as the transmitting end needs to pass through the RAN device serving the transmitting end, the core network device, the server in the data network, the core network device, and the RAN serving the receiving end.
  • the device can be received by the terminal device as the receiving end.
  • a terminal device can transmit a data packet through a directly connected communication link, that is, device-to-device (D2D) communication
  • D2D device-to-device
  • the terminal device can be made
  • the transmission delay of the data packets between the two devices is low, but in the communication mode, the terminal devices need to compete for the radio resources for transmitting the data packets, so that the communication between the terminal devices is easy to cause packet loss.
  • the reliability lower. Therefore, according to the data transmission manner between the terminal devices proposed in the prior art, it is difficult to balance the performance requirements of low latency and high reliability in some service scenarios.
  • the present application proposes a communication method and device, and establishes a communication link between terminal devices for transmitting data packets through the RAN device, and the data packets can be forwarded without passing through the core network device, thereby shortening the data packet.
  • the transmission process on the network side not only saves the time for establishing a communication link, but also reduces the transmission delay during the transmission of subsequent data packets.
  • the data packet is transmitted through the radio access network side, and the RAN device can provide the function of managing the radio resource, and allocate the radio resource for transmitting the data packet to the terminal device, so as to avoid preempting the radio resource between the terminal devices in the existing D2D solution. In this case, it is also possible to balance the reliability of data packets transmitted between terminal devices.
  • the communication link involved in the present application includes a communication link between the terminal device and the RAN device, and a communication link between the RAN device and the RAN device. It should be understood that the communication link in the following description may also be referred to as a bearer.
  • the words "first”, “second”, and the like, which are referred to hereinafter, are used to distinguish between the purpose of the description, and are not to be construed as indicating or implying relative importance, nor to indicate or suggest a sequence or the like.
  • the first terminal device and the second terminal device are respectively used as both ends of the transmission data packet.
  • the first terminal device can serve as both a transmitting end and a receiving end.
  • the second terminal device is the receiving end, and when the first terminal device is the receiving end, the first terminal device is the receiving end.
  • the second terminal device is the transmitting end.
  • the first terminal device and the second terminal device are not limited to one-way communication, and two-way communication is also possible.
  • the first RAN device establishes the first terminal device and the second terminal device under the trigger of the first terminal device by using the first terminal device and the first RAN device serving the first terminal device as an example.
  • the process of transmitting a communication link between packets Specifically, the following steps are included:
  • Step 201 The first terminal device sends a service identifier and a service quality requirement of the service corresponding to the service identifier to the first RAN device.
  • the service identifier includes at least a destination address
  • the destination address may be used by at least one terminal device to participate in a service corresponding to the service identifier.
  • the destination address can be used to identify a service, and at least one terminal device capable of performing the same service can be configured with the same destination address, so that at least one terminal device using the same destination address can participate in the same service. For example, if the service identifier sent by the first terminal device to the first RAN device is the destination address #1, the second terminal device configured with the destination address #1 and the first terminal device may be based on the established communication link. The packet of the service identified by the destination address #1 is transmitted.
  • the destination address configured in the at least one terminal device, including the first terminal device may be at least one, and the number of specifically configured destination addresses may be determined according to the number of services actually supported by the at least one terminal device.
  • the number of service identifiers reported by the first terminal device to the first RAN device may also be at least one.
  • the first terminal device may report the at least one destination address to the first RAN device.
  • at least one destination address may take the form of a destination address list.
  • the service identifier may further include a service type.
  • the service type supported by the first terminal device as the car network terminal may include, for example, an accident service for characterizing a traffic accident on a certain road segment, and is used to represent a certain service. Congestion-type business with congestion in one section.
  • the destination address can be in one-to-one correspondence with the service type, and the destination address can also be associated with multiple service types.
  • the service quality requirement of the service corresponding to the service identifier may include a first indicator for characterizing the delay requirement of the service, and may further include a second indicator for characterizing the reliability requirement of the service.
  • the first indicator is, for example, PPPP
  • the second indicator is, for example, PPPR.
  • a third indicator capable of simultaneously characterizing the delay requirement of the service and the reliability requirement such as a quality of service (QoS) parameter, may be used, which is not limited in this application.
  • QoS quality of service
  • the first terminal device may report the service identifier and the service quality requirement to the first RAN device in the process of attaching the network, or report the service identifier and the service to the first RAN device when the service is initiated after the network is successfully attached to the network. Quality requirements, etc.
  • the specific reporting method will be exemplified in the following.
  • Step 202 The first RAN device establishes a first bearer with the first terminal device based on the service identifier and the quality of service requirement from the first terminal device.
  • Step 203 The first RAN device establishes a second bearer with the second RAN device based on the service identity and the quality of service requirement from the first terminal device.
  • the second RAN device refers to a RAN device that provides a service for the second terminal device
  • the second terminal device refers to a terminal device that can perform services corresponding to the service identifier except the first terminal device.
  • the established first bearer and/or the second bearer may be used to transmit a data packet of a service corresponding to the service identifier performed between the first terminal device and the second terminal device.
  • the second RAN device may also receive the service identifier from the second terminal device and store it locally.
  • the service identifier from the second terminal device received by the second RAN device is received by the first RAN device.
  • the service identifiers from the first terminal device may be the same, such that the first RAN device may establish a second bearer with the second terminal device for the same service identifier.
  • the first RAN device may first determine whether the service quality requirement is characterized by low delay and high reliability. If yes, the first bearer and/or the second bearer may be established for the first terminal device according to the steps of step 202 and step 203. If not, the first terminal device and the second terminal may be established according to the existing scheme.
  • the transmission path of packets between devices For example, when the quality of service is represented by PPPP or PPPR, you can configure the first threshold for PPPP and the second threshold for PPPR. When PPPP is lower than the first threshold, PPPR is higher than the second threshold.
  • the embodiment of the present application may be applicable to a scenario in which a low-latency demand is required, or in a scenario where a high-reliability requirement is required. Similar scenarios for business needs.
  • the data packet in the present application may be generally referred to as a type of data packet, and the data packets that are exchanged between the first terminal device and the second terminal device when performing the service corresponding to the service identifier may be classified into one. Class data package.
  • the process of establishing the first bearer and the second bearer by the first RAN device may be a process independent of each other, so the foregoing steps 202 and 203 may be in the order of execution.
  • the first RAN device establishes a first bearer with the first terminal device based on the service identity and the quality of service requirement from the first terminal device.
  • the first bearer between the first RAN device and the first terminal device can be understood as a radio bearer between the first RAN device and the first terminal device.
  • the first terminal device can serve as both the transmitting end of the transmitting data packet and the receiving end of the receiving data packet
  • the first RAN device when the first terminal device is the transmitting end, the first RAN device is the RAN device serving the transmitting end.
  • the first RAN device When the first terminal device is the receiving end, the first RAN device is a RAN device that provides a service for the receiving end. The following two cases are introduced separately.
  • the first terminal device is a transmitting end
  • the first RAN device is a RAN device that provides a service for the transmitting end.
  • the first terminal device is a Tx UE
  • the first RAN device is gNB#1
  • the first bearer is a radio bearer #1 as an example.
  • the process of establishing the radio bearer #1 can be as shown in FIG. 3A, and includes the following steps:
  • Step 301A The Tx UE sends a control indication to gNB#1.
  • the Tx UE sending a control indication to the gNB#1 may be implemented in the process of requesting the attached network. In another implementation manner, the Tx UE sending the control indication to the gNB#1 may also be implemented in the process of requesting to initiate the service after successfully attaching the network.
  • the control indication may include a service identifier and a quality of service requirement of a service corresponding to the service identifier.
  • the control indication sent by the Tx UE may be carried in a non-access stratum (NAS) message.
  • NAS non-access stratum
  • the gNB#1 does not parse the control indication after receiving the NAS message, and transparently forwards the packet to the core network device.
  • the control indication sent by the Tx UE may also be carried in an access stratum (AS) message.
  • AS access stratum
  • the gNB#1 may parse the control indication after receiving the AS message, and send the parsed control indication to the Core network equipment.
  • Step 302A gNB#1 sends a control indication from the Tx UE to the core network device.
  • Step 303A The core network device sends a bearer setup request to gNB#1.
  • the core network device After receiving the control indication, the core network device obtains the service quality requirement corresponding to the service identifier by identifying the service identifier, and carries the service identifier and the corresponding service quality requirement in the bearer setup request and sends the request to the gNB#1.
  • Step 304A gNB#1 configures radio bearer #1 for the Tx UE.
  • the gNB#1 may configure a parameter for establishing the radio bearer #1 for the Tx UE and indicate by radio resource control (RRC) signaling, based on the quality of service requirement carried in the bearer setup request.
  • RRC radio resource control
  • Step 305A The Tx UE sends a bearer setup completion indication to gNB#1.
  • the Tx UE may complete the configuration of the radio bearer #1 based on the received parameters for establishing the radio bearer #1, and after the configuration is successful, send a bearer setup completion indication to the gNB#1, and the bearer setup completion indication may also be carried in the RRC signaling. in.
  • the above step 305A may also be an optional step.
  • Step 306A gNB#1 sends a bearer setup completion response to the core network device.
  • the bearer setup completion response may instruct the core network device to perform a control policy operation, such as charging, on the data packet transmitted by the Tx UE based on the radio bearer #1.
  • the bearer setup completion response may also instruct the core network device to retain the configuration parameters of the radio bearer #1 when the radio bearer #1 is released.
  • the radio bearer #1 between the Tx UE and the gNB#1 is established, and the established radio bearer #1 is used to transmit the data packet sent to the gNB#1 when the Tx UE performs the service corresponding to the service identifier.
  • the core network device participates in the process of establishing the radio bearer #1 between the Tx UE and the gNB#1, and takes into account the participation of the core network device, which brings a long delay to the establishment of the radio bearer #1, so in the example In the second, it is designed that the radio bearer #1 can be established directly by gNB#1 in order to minimize the delay in establishing the radio bearer #1.
  • the process of establishing the radio bearer #1 can be as shown in FIG. 3B, and includes the following steps:
  • Step 301B The Tx UE sends a control indication to the gNB#1, where the control indication carries the service identifier of the Tx UE and the service quality requirement of the service corresponding to the service identifier.
  • the control indication may be sent to gNB#1 in the process of requesting the attached network, or may be sent to gNB#1 in the process of requesting the initiation of the service, as described in step 301A above.
  • the control indication is used to indicate that gNB#1 establishes a radio bearer #1 between the service corresponding to the service identifier and the Tx UE.
  • Step 302B After determining that the service identifier and the quality of service requirement from the Tx UE meet the preset condition, the gNB#1 configures the radio bearer #1 for the Tx UE.
  • the gNB#1 pre-stores the authorization information about the Tx UE from the core network device, where the authorization information includes the authorized service identifier of the service that the Tx UE has been authorized, and the Tx UE performs the authorized operation. Quality of service requirements during business.
  • the gNB#1 After receiving the service identifier and the quality of service requirement from the Tx UE, the gNB#1 determines that the authorized service identifier includes the service identifier from the Tx UE, and optionally, the pre-stored service identifier corresponds to the service quality requirement and When the quality of service requirements from the Tx UEs are matched, it is confirmed that the preset condition is met, and the radio bearer #1 is configured for the service corresponding to the service identifier of the Tx UE. Wherein, if the pre-stored service identifier corresponding service quality requirement is the same as or similar to the service quality requirement from the Tx UE, the two can be regarded as matching. Similarity can be understood as the difference between the two does not exceed the set threshold.
  • gNB#1 can unify the format of the two before performing the above analysis process.
  • the gNB#1 may indicate the configured parameters for establishing the radio bearer #1 to the Tx UE through RRC signaling.
  • Step 303B The Tx UE sends a bearer setup completion indication to gNB#1.
  • the Tx UE may complete the configuration of the radio bearer #1 based on the received parameters for establishing the radio bearer #1, and after the configuration is successful, send a bearer setup completion indication to the gNB#1, and the bearer setup complete indication may also be carried in the RRC signaling. in.
  • the foregoing step 303B may also be an optional step.
  • Step 304B gNB#1 sends a bearer setup completion response to the core network device.
  • the bearer setup completion response may carry the terminal identifier of the Tx UE, the quality of service requirement of the radio bearer #1, and the time-frequency resource, etc., so as to be subsequently transmitted by the Tx UE through the radio bearer #1.
  • the network device completes the policy control operation, such as charging for the Tx UE.
  • the bearer setup completion response may further instruct the core network device to retain the configuration parameter of the radio bearer #1 when the radio bearer #1 is released.
  • the radio bearer #1 between the Tx UE and the gNB#1 is established, and the established radio bearer #1 is used to transmit the data packet to the gNB#1 when the Tx UE performs the service corresponding to the service identifier.
  • the first terminal device is a receiving end, and the first RAN device is a RAN device that provides a service to the receiving end.
  • the first terminal device is the Rx UE, the first RAN device is gNB#2, and the first bearer is the radio bearer #2.
  • Example 1 and/or Example 2 can accomplish the establishment of a radio bearer by controlling the interaction of plane signaling.
  • the embodiment of the present application further provides an example 3 of establishing the radio bearer #2.
  • the manner given in Example 3 is implemented in the case where a communication link has been established between the transmitting end and gNB#2.
  • the gNB#2 can receive the data packet from the sending end based on the established communication link with the transmitting end, where the packet header of the data packet can include the service identifier and the service quality requirement of the service corresponding to the service identifier. Since the quality of service requirements when the sender and the receiver perform the same service are basically the same, gNB#2 can establish a relationship between the gNB#2 and the Rx UE according to the service identifier and the quality of service requirement of the packet header from the sender. Wireless bearer #2.
  • gNB#2 may send the data packet from the sending end to the Rx UE through the radio bearer #2.
  • gNB#2 can complete the establishment of the radio bearer #2 with the Rx UE in the process of forwarding the data packet.
  • the first RAN device is configured to establish a first bearer with the first terminal device, and the first RAN device may establish, for the service corresponding to the service identifier performed by the first terminal device, a data packet.
  • the first bearer may be established during the process of establishing the first bearer by the first RAN device, so that the delay for establishing the first bearer may be reduced.
  • the radio bearer may also be established between the second terminal device and the second RAN device by referring to the foregoing example, and details are not described herein again.
  • the first RAN device establishes a second bearer with the second RAN device based on the service identity and the quality of service requirement from the first terminal device.
  • the second bearer between the first RAN device and the second RAN device may be referred to as a tunnel between the RANs, and may be a direct link based on the X2 interface (FIG. 4A). As shown, it may also be a bridge link (shown in FIG. 4B) or the like established by the first RAN device and the second RAN device based on a bridge function module. In the case that there is no X2 interface between the RAN devices, the RAN devices can perform control plane signaling and user plane data interaction between the RAN devices through the bridge function module.
  • the bridge function module can be deployed together with the RAN device or separately from the RAN device.
  • the bridge function module functions as a transparent forwarding, which can be regarded as directly interacting between the RAN devices.
  • the first terminal device is a Tx UE
  • the first RAN device is gNB#1
  • the second RAN device is gNB#2.
  • the bearer between the RAN devices is represented by a tunnel.
  • Step 501 The Tx UE sends a control indication to gNB#1.
  • the control indication may include a service identifier, where the service identifier is exemplified by a destination address.
  • control indication For a detailed description of the control indication, refer to the description in the foregoing example 1 of the present application, and details are not described herein again.
  • Step 502 gNB#1 records the destination address, and determines gNB#2 that also records the destination address.
  • Step 503 The first endpoint identifier corresponding to the destination address is configured by gNB#1, and the second endpoint identifier corresponding to the destination address configured by gNB#2 is obtained.
  • Step 504 gNB#1 establishes a tunnel with gNB#2 and identifies the established tunnel by using the first endpoint identifier and/or the second endpoint identifier.
  • the gNB#1 can receive the destination address sent by the terminal device in the service range of the gNB#1, and record the first mapping relationship between the identifier of the terminal device and the destination address.
  • the identifier of the terminal device is an identifier that can uniquely identify the terminal device, and may be, for example, an International Mobile Subscriber Identification Number (IMSI), a Subscriber Identity Module (SIM) number, or an Internet protocol (Internet Protocol). Protocol, IP) address, L2 layer address (for example, Media Access Control (MAC) address, etc.), or other identifier that can determine the terminal device, such as the temporary identifier of the terminal device, or the location information of the terminal device.
  • IMSI International Mobile Subscriber Identification Number
  • SIM Subscriber Identity Module
  • IP Internet Protocol
  • L2 layer address for example, Media Access Control (MAC) address, etc.
  • MAC Media Access Control
  • the destination address sent by the terminal device in the service range of gNB#2 can also be received, and the first mapping relationship between the identifier of the terminal device and the destination address is recorded.
  • the first mapping relationship between the identifier of the recorded terminal device and the destination address may be, for example, in the form of a list, as described in Table 1:
  • Terminal equipment #1 Destination address #1 Terminal equipment #2 Destination address #2 > (7) Terminal equipment#n Destination address #n
  • Table 1 is only for illustrative purposes, and does not limit the destination address to have a one-to-one correspondence with the terminal device.
  • one destination address may correspond to the identifier of multiple terminal devices, and the identifier of one terminal device also Can correspond to multiple destination addresses. This is because the destination address is used to identify the services supported by the terminal device, and one terminal device can support multiple services. Therefore, the identifier of one terminal device can correspond to multiple destination addresses, and multiple terminal devices can support the same service, so one The destination address can correspond to the identifier of multiple terminal devices.
  • the gNB#1 and gNB#2 can exchange the destination address of the RAN device with the destination address of the RAN device and the second mapping relationship between the RAN device and the destination address.
  • the identifier of the RAN device is an identifier that can uniquely identify the RAN device, and may be, for example, an IP address of the RAN device, an L2 layer address (for example, a MAC address, etc.), or other identifiers that can determine the RAN device. For example, supposing that destination address #1, destination address #2, destination address #3, and gNB#2 are recorded in gNB#1, destination address #1 and destination address #2 are recorded, then gNB#1 and gNB#2 will be recorded. After the destination address of the record is interacted, the generated list of the second mapping relationship is as shown in Table 2:
  • gNB#1 can determine that gNB#2 also records destination address #1 and destination address #2 according to the second mapping relationship. Furthermore, gNB#1 can determine that a tunnel can be established based on destination address #1 with gNB#2, or a tunnel can be established based on destination address #2. Optionally, in order to identify which destination address the established tunnel corresponds to, gNB#1 may configure endpoint identifier #1A corresponding to destination address #1 and endpoint identifier #2A corresponding to destination address #2. The endpoint identifier can also be understood as a tunnel interface.
  • gNB#2 it can also be determined that a tunnel can be established between the destination address #1 and/or the destination address #2 with gNB#1. Therefore, gNB#2 can also be configured with the destination address #1. Endpoint ID #1B, Endpoint ID #2B corresponding to destination address #2.
  • gNB#1 may interact with gNB#2 to configure an endpoint identifier corresponding to the destination address, so that gNB#1 may use endpoint identifier #1A and endpoint identifier #1B to identify the establishment based on destination address #1.
  • the tunnel uses endpoint identifier #2A, endpoint identifier #2B to identify the tunnel established based on destination address #2.
  • the establishment of a tunnel between gNB#1 and gNB#2 can be completed. Subsequently, the data packets from the terminal device can be forwarded based on the established tunnel.
  • the application scenario shown in FIG. 6A after gNB#1 receives the data packet from the Tx UE, if gNB#1 determines that the packet header carries the destination address #1, it can match the destination address #1. Go to endpoint ID #1B and forward the packet directly to gNB#2 through the tunnel identified by endpoint ID #1B.
  • the gNB#2 may determine that the first mapping relationship exists between the at least one Rx UE and the destination address #1 in the service range according to the first mapping relationship between the identifier of the recorded terminal device and the destination address.
  • At least one Rx UE supports the service identified by the destination address #1, and then the gNB#2 can directly forward the data packet from the Tx UE to at least one Rx UE in the service range of the gNB#2.
  • the gNB#1 after the gNB#1 receives the data packet from the Tx UE, it can perform not only the forwarding between the RAN devices shown in FIG. 6A but also the forwarding in the RAN.
  • gNB#1 determines at least one Rx UE that is in the service range of gNB#1 according to the first mapping relationship between the identifier of the recorded terminal device and the destination address.
  • a first mapping relationship exists between the destination address and the destination address #1, so that at least one Rx UE supports the service identified by the destination address #1, and the gNB#1 can directly forward the data packet from the Tx UE to the gNB#1. At least one Rx UE within the scope of service.
  • the data packet when data packet transmission is performed between the first terminal device and the second terminal device, the data packet may be directly transmitted between the RAN or the RAN without being forwarded by the core network device. Reduce the transmission delay of packets.
  • the data packet is forwarded via the RAN, and the RAN device manages the radio resource for transmitting the data packet, etc., and the packet loss rate can be reduced compared to the D2D communication, thereby making it possible to balance the reliability of the data packet transmission.
  • the communication link for transmitting the data packet needs to be updated to ensure that the data packet can be normally transmitted between the Tx UE and the Rx UE.
  • the first terminal device is a Tx UE
  • the second terminal device is an Rx UE
  • the first RAN device serving the first terminal device is gNB#1
  • the second terminal device is the second serving device.
  • the RAN device is gNB#2
  • one-way communication is performed between the first terminal device and the second terminal device.
  • the communication link of the data packet between the Tx UE and the Rx UE that has been established for transmission includes the radio bearer #1 between the Tx UE and the gNB#1, and the tunnel #1 between gNB#1 and gNB#2, Radio bearer #2 between Rx UE and gNB#2.
  • the data packet sent by the Tx UE is sent to gNB#1 through radio bearer #1, and then sent to gNB#2 by gNB#1 through tunnel #1, and then the data packet is sent by gNB#2 through radio bearer #2.
  • the Rx UE is sent to gNB#1 through radio bearer #1, and then sent to gNB#2 by gNB#1 through tunnel #1, and then the data packet is sent by gNB#2 through radio bearer #2.
  • the process of updating the communication link for transmitting the data packet may be as shown in FIG. 8, and specifically includes the following steps:
  • Step 801 The Tx UE sends a first measurement report (measurement report #1) to the gNB #1 during the service range of the gNB#1 to the service range of the gNB#1-N.
  • the first measurement report may include a handover indication, including a service indicator, and a handover indication, in addition to the existing parameters such as the signal strength of the target gNB and the physical cell identifier (PCI) information.
  • the indication is used to indicate that the gNB#1 performs handover between the RAN devices for the service corresponding to the service identifier performed by the Tx UE.
  • the handover indication may further include a service quality requirement of the service corresponding to the service identifier. Whether it is required to carry the quality of service requirement may be determined according to the configuration of gNB#1.
  • Tx The quality of service requirement may not be carried in the first measurement report sent by the UE.
  • Step 802 The gNB#1 determines, according to the received first measurement report, that the Tx UE performs the service corresponding to the service identifier, and needs to be switched by gNB#1 to gNB#1-N, and then sends the first handover request to the gNB#1-N (handover Request#1).
  • the first handover request includes a terminal identifier of the Tx UE, a service identifier, and a service quality requirement of the service corresponding to the service identifier.
  • the service identifier is the destination address #1 as an example.
  • the destination address #1 included in the first handover request and the quality of service requirement are used to indicate that the gNB#1-N establishes the radio bearer #3 between the Tx UE and the Tx UE.
  • gNB#1 can also carry the gNB#2 configuration in the first handover request.
  • the destination address #1B corresponding to the destination address #1, and the communication address of the gNB#2, etc., the communication addresses of the endpoint identifiers #1B and gNB#2 are used to indicate that the gNB#1-N establishes a tunnel with the gNB#2# 2.
  • the communication address of gNB#2 may be acquired by gNB#1 in the process of establishing tunnel #1 between gNB#2, and the communication address of gNB#2 may be an L2 protocol layer address, such as a MAC address.
  • gNB#1 can obtain the communication address of gNB#2 when the destination address of each record is exchanged with gNB#2 by means of route update.
  • Step 803 The gNB#1-N parses the content carried in the first handover request, configures parameters for establishing the radio bearer #3 for the Tx UE according to the parsed destination address #1, and the quality of service requirement, and further, to gNB# 1 Send a first handover response (handover request ack#1).
  • the first handover response includes a first handover command (handover command #1), where the first handover command includes a terminal identifier of the Tx UE, a parameter for establishing the radio bearer #3, a security algorithm, and the like.
  • handover command #1 includes a terminal identifier of the Tx UE, a parameter for establishing the radio bearer #3, a security algorithm, and the like.
  • Step 804 gNB#1-N parses the content carried in the first handover request, and completes the tunnel between gNB#1-N and gNB#2 according to the parsed endpoint identifier #1B and the communication address of gNB#2# 2 configuration.
  • Step 805 The gNB#1 parses the first handover command from the received first handover response, and sends the first handover command to the Tx UE by using RRC signaling.
  • Step 806 After receiving the first handover command, the Tx UE completes the configuration of the radio bearer #3 based on the content carried in the first handover command, and detaches from the gNB#1.
  • the Tx UE may send the data packet to the gNB#1-N through the radio bearer #3, and then send it to the gNB#2 through the tunnel #2 by the gNB#1-N, and then send it to the gNB#2 through the radio bearer #2.
  • Rx UE may send the data packet to the gNB#1-N through the radio bearer #3, and then send it to the gNB#2 through the tunnel #2 by the gNB#1-N, and then send it to the gNB#2 through the radio bearer #2.
  • the data packet that has been received from the Tx UE but has not been sent to gNB#2 may be buffered in gNB#1.
  • gNB#1 can continue to use the tunnel #1 to send a data packet to the gNB#2, and after the buffered data packet is sent, the tunnel #1 is invalidated.
  • the gNB#1 may also delete related information of the Tx UE, for example, parameters for establishing the radio bearer #1, and the like.
  • the Tx UE may also move from the service range of gNB#1 to the service range of gNB#2 during the mobile process.
  • gNB#1 may indicate that gNB#2 is established between the Tx UE and the Tx UE.
  • For the specific procedure of the radio bearer refer to the process of establishing the radio bearer #3 shown in FIG. 8 above, which is not repeatedly described in this application.
  • the first terminal device is an Rx UE
  • the second terminal device is a Tx UE
  • the first RAN device serving the first terminal device is gNB#2
  • the second terminal device is the second serving device.
  • the RAN device is gNB#1
  • one-way communication is performed between the first terminal device and the second terminal device.
  • the communication link of the data packet between the Tx UE and the Rx UE that has been established for transmission includes the radio bearer #1 between the Tx UE and the gNB#1, and the tunnel #1 between gNB#1 and gNB#2, Radio bearer #2 between Rx UE and gNB#2.
  • the data packet sent by the Tx UE is sent to gNB#1 through radio bearer #1, and then sent to gNB#2 by gNB#1 through tunnel #1, and then the data packet is sent by gNB#2 through radio bearer #2.
  • the Rx UE is sent to gNB#1 through radio bearer #1, and then sent to gNB#2 by gNB#1 through tunnel #1, and then the data packet is sent by gNB#2 through radio bearer #2.
  • the process of updating the communication link for transmitting the data packet may be as shown in FIG. 10, and specifically includes the following steps:
  • Step 1001 The Rx UE sends a second measurement report (measurement report #2) to the gNB#2 during the mobile range of the service range of the gNB#2 to the gNB#2-N.
  • the second measurement report carries a handover indication, where the handover indication includes a service identifier, and the handover indication is used to indicate that the gNB#2 performs handover between the RAN devices for the service corresponding to the service identifier performed by the Rx UE.
  • the handover indication includes a service identifier
  • the handover indication is used to indicate that the gNB#2 performs handover between the RAN devices for the service corresponding to the service identifier performed by the Rx UE.
  • Step 1002 The gNB#2 determines, according to the received second measurement report, that the Rx UE performs the service corresponding to the service identifier, and needs to be switched by gNB#2 to gNB#2-N, and then sends a second handover request to the gNB#2-N. Request#2).
  • the second handover request includes the terminal identifier of the Rx UE, the service identifier, and the service quality requirement of the service corresponding to the service identifier.
  • the service identifier is the destination address #1 as an example.
  • the destination address #1 included in the first handover request and the quality of service requirement are used to indicate that the gNB#2-N establishes the radio bearer #4 between the Rx UE and the Rx UE.
  • Step 1003 The gNB#2-N parses the content carried in the first handover request, configures parameters for establishing the radio bearer #4 for the Rx UE according to the parsed destination address #1, the quality of service requirement, and the like, and addresses the destination address. #1 performs tunnel interface configuration, and then sends a second handover response (handover request ack#2) to gNB#2.
  • the third endpoint identifier corresponding to the destination address #1 that is, the endpoint identifier #1C is configured as the tunnel interface.
  • the second handover response includes a second handover command (handover command #2), where the second handover command includes a terminal identifier of the Rx UE, a parameter for establishing the radio bearer #4, a security algorithm, and the like.
  • the second handover response further includes an endpoint identifier #1C of the gNB#2-N configuration, and a communication address of the gNB#2-N.
  • the communication address of gNB#2-N may be an L2 protocol layer address, such as a MAC address.
  • Step 1004 gNB#2 parses the communication addresses of the endpoint identifier #1C and the gNB#2-N from the received second handover response, and completes the configuration of the tunnel #3 between the gNB#2 and the gNB#2-N.
  • step 1004 may be an optional step. That is, when the packet from the Tx UE that has been received from gNB#1 but has not been transmitted to the Rx UE is buffered in gNB#2, gNB#2 may be based on endpoint identifier #1C, and gNB#2-N Establishing tunnel #3 between gNB#2 and gNB#2-N to send the buffered data packet from the Tx UE to gNB#2-N, and then the established radio bearer by gNB#2-N# 4 is sent to the Rx UE.
  • Step 1005 gNB#2 sends a first bearer update request (bearer update request #1) to gNB#1, where the first bearer update request carries the endpoint address #1C and the communication address of gNB#2-N.
  • the first bearer update request is used to instruct gNB#1 to establish tunnel #4 with gNB#2-N.
  • Step 1006 gNB#1 completes the configuration of tunnel #4 between gNB#1 and gNB#2-N according to the communication addresses of endpoint identifier #1C and gNB#2-N parsed from the first bearer update request. .
  • the tunnel #4 can be used to transmit the data packet sent by the gNB#1 to the gNB#2-N from the Tx UE.
  • Step 1007 gNB#1 sends a first bearer update response (bearer update request ack#1) to gNB#2, indicating that gNB#2 has completed the configuration of tunnel #4.
  • step 1007 may also be an optional step.
  • Step 1008 gNB#2 sends the second handover command parsed from the second handover response to the Rx UE through RRC signaling.
  • Step 1009 After receiving the second handover command, the Rx UE completes the configuration of the radio bearer #4 based on the content carried in the second handover command, and detaches from the gNB#2.
  • the Tx UE may send the data packet to gNB#1 through radio bearer #1, and then send it to gNB#2-N through gNB#1 through tunnel #4, and then send it to gNB#2-N through radio bearer #4.
  • Rx UE for the data packet from the Tx UE that has been buffered in gNB#2 that has been received from gNB#1 but has not been sent to the Rx UE, gNB#2 can be sent to gNB#2-N through the established tunnel #3. And then transmitted by gNB#2-N to the Rx UE through the radio bearer #4.
  • gNB#2 may also delete related information of the Rx UE, for example, parameters for establishing the radio bearer #2.
  • the Rx UE may also move from the service range of gNB#2 to the service range of gNB#1 during the mobile process.
  • gNB#2 may indicate that gNB#1 is established between the Rx UE and the Rx UE.
  • For the specific procedure of the radio bearer refer to the process of establishing the radio bearer #4 shown in FIG. 10 above, which is not repeatedly described in this application.
  • the first terminal device is UE#1
  • the second terminal device is UE#2
  • the first RAN device that provides service for the first terminal device is gNB#1, and provides services for the second terminal device.
  • the second RAN device is gNB#2, and the two-way communication is performed between the first terminal device and the second terminal device.
  • the communication link of the data packet between UE#1 and UE#2 that has been established for transmission includes the tunnel between the radio bearer #1, gNB#1 and gNB#2 between UE#1 and gNB#1. #1A, tunnel #1B between gNB#1 and gNB#2, radio bearer #2 between UE#1 and gNB#2.
  • tunnel #1A is an uplink tunnel and tunnel #1B is a downlink tunnel. It is assumed here that UE#1 transmits a data packet to UE#2 in the uplink direction, and UE#2 transmits a data packet to UE#1 in the downlink direction.
  • the data packet sent by UE#1 is sent to gNB#1 through radio bearer #1, and then sent to gNB#2 through gNB#1 through tunnel #1A, and then transmitted by gNB#2 through radio bearer.
  • #2 sends the packet to UE#2.
  • the data packet sent by UE#2 is sent to gNB#1 through radio bearer #1, and then sent to gNB#2 by gNB#1 through tunnel #1B, and then the packet is transmitted by gNB#2 through radio bearer #2. Send to UE#1.
  • the flow of updating the communication link for transmitting a data packet is exemplified as an example in which UE#1 is moved within the service range of gNB#1 to the service range of gNB#1-N. It should be understood that the process of updating the communication link shown in FIG. 12 is also applicable to the scenario in which UE#2 is moved within the service range of gNB#2 to the service range of gNB#2-N.
  • Step 1201 UE#1 sends a third measurement report (measurement report#3) to gNB#1 during the service range from gNB#1 to the service range of gNB#1-N.
  • measurement report#3 a third measurement report
  • the third measurement report carries a handover indication, where the handover indication includes a service identifier, and the handover indication is used to indicate that the gNB#1 performs handover between the RAN devices for the service corresponding to the service identifier performed by the UE#1.
  • the handover indication includes a service identifier
  • the handover indication is used to indicate that the gNB#1 performs handover between the RAN devices for the service corresponding to the service identifier performed by the UE#1.
  • Step 1202 The gNB#1 determines that the UE#1 performs the service corresponding to the service identifier based on the received third measurement report, and needs to be switched by gNB#1 to gNB#1-N, and then sends a third handover request to gNB#1-N ( Handover request#3).
  • the third handover request includes the terminal identifier of the UE#1, the service identifier, and the service quality requirement of the service corresponding to the service identifier.
  • the service identifier is the destination address #1 as an example.
  • the destination address #1 included in the first handover request and the quality of service requirement are used to indicate that the gNB#1-N establishes the radio bearer #5 between the UE and the UE#1.
  • gNB# 1 may also carry the endpoint identifier #1B corresponding to the destination address #1 configured by gNB#2 and the communication address of gNB#2 in the third handover request, and the communication addresses of the endpoint identifiers #1B and gNB#2 are used to indicate gNB#1-N establishes tunnel #5A with gNB#2.
  • tunnel #5A is an uplink tunnel.
  • Step 1203 gNB#1-N parses the content carried in the third handover request, configures parameters for establishing the radio bearer #5 for the UE#1 according to the parsed destination address #1, and the quality of service requirement, etc., and aims for Address #1 performs tunnel interface configuration, and then sends a third handover response (handover request ack#3) to gNB#1.
  • the gNB#1-N can configure the fourth endpoint identifier corresponding to the destination address #1, that is, the endpoint identifier #1D as the tunnel interface, when the tunnel interface is configured for the destination address #1.
  • the third handover response includes a third handover command (handover command #3), where the third handover command includes a terminal identifier of the UE#1, a parameter for establishing the radio bearer #5, a security algorithm, and the like.
  • the third handover response further includes an endpoint identifier #1D configured by the gNB#1-N, and a communication address of the gNB#1-N.
  • the communication address of gNB#1-N may be an L2 protocol layer address, such as a MAC address.
  • Step 1204 gNB#1-N completes the tunnel #5A in the uplink direction between gNB#1-N and gNB#2 according to the address identifiers of the endpoint identifiers #1B and gNB#2 carried in the third handover request. Configuration.
  • Step 1205 gNB#1 sends a second bearer update request (bearer update request #2) to gNB#2, where the second bearer update request carries the endpoint address #1D and the communication address of gNB#1-N.
  • the bearer update request is used to instruct gNB#2 to establish tunnel #5B with gNB#1-N.
  • tunnel #5B is a downlink tunnel.
  • Step 1206 gNB#2 completes the tunnel in the downlink direction between gNB#2 and gNB#1-N according to the endpoint ID #1D and the communication address of gNB#1-N parsed from the second bearer update request# 5B configuration.
  • the tunnel #5B can be used to transmit the data packet from the UE#2 sent by the gNB#2 to the gNB#1-N.
  • Step 1207 gNB#2 sends a second bearer update response (bearer update request ack#2) to gNB#1, indicating that gNB#1 has completed the configuration of tunnel #5B.
  • step 1207 can also be an optional step.
  • Step 1208 gNB#1 sends the third handover command parsed from the third handover response to UE#1 through RRC signaling.
  • Step 1209 After receiving the third handover command, the UE #1 completes the configuration of the radio bearer #5 based on the content carried in the second handover command, and detaches from the gNB#1.
  • UE#1 can send the data packet to gNB#1 through radio bearer #5, and then send it to gNB#1-N through gNB#1 through tunnel #5A, and then pass gNB#1-N Radio bearer #2 is sent to UE#2.
  • UE#2 can send the data packet to gNB#2 through radio bearer #2, and then send it to gNB#1-N through gNB#2 through tunnel #5B, and then pass the radio bearer by gNB#1-N# 5 is sent to UE#1.
  • gNB#1 can still be sent to gNB#2 through the previously established tunnel #1A, in the cached After the data packet is sent, the tunnel #1A is invalidated.
  • gNB#1 may also delete related information of UE#1, for example, parameters for establishing radio bearer #1, and the like.
  • the process of transmitting a communication link for transmitting a data packet is performed, and the RAN device can perform handover between the RAN devices and update of the communication link directly under the trigger of the terminal device.
  • the core network device does not participate in the handover process, which can reduce the delay of the handover process, so that the terminal device has no perception of the handover process as much as possible, and achieves the purpose of seamless handover.
  • the RAN device is a process of initiating updating a communication link for transmitting a data packet for a service corresponding to the service identifier in the received handover indication.
  • the services corresponding to the service identifiers in this application mainly include services with low latency requirements and high reliability requirements.
  • the handover between the RANs and the update of the communication link may still be performed according to the existing scheme.
  • the embodiment of the present application further provides a communication device, which is used to implement the functions performed by the first RAN device in the foregoing method embodiment.
  • FIG. 13 is a schematic structural diagram 1 of the communication device provided by the embodiment of the present application.
  • the communication device 1300 may include a receiving unit 1301 and a processing unit 1302.
  • the receiving unit 1301 is configured to receive a service identifier sent by the first terminal device, and a service quality requirement of the service corresponding to the service identifier.
  • the processing unit 1302 may be configured to establish a first bearer with the first terminal device based on the service identifier and the quality of service requirement, and establish and second based on the service identifier and the quality of service requirement. The second bearer between the RAN devices of the radio access network.
  • the first bearer and the second bearer are used to transmit a data packet corresponding to the service identifier performed by the first terminal device and the second terminal device, where the second RAN device is used.
  • the service identifier may include a destination address, where the destination address is used by at least one terminal device to participate in a service corresponding to the service identifier.
  • the quality of service requirements include a first indicator for characterizing the latency requirement of the service and a second indicator for characterizing the reliability requirement of the service.
  • the receiving unit 1301 may be further configured to receive authorization information of the first terminal device from the core network device, where the authorization information includes authorization of the service that the first terminal device has been authorized. a service identifier, and a quality of service requirement when the first terminal device executes the authorized service.
  • the processing unit 1302 may be specifically configured to include the service identifier in the authorized service identifier, and the service quality requirement corresponding to the service identifier Establishing the first bearer with the first terminal device if the quality of service requirement from the first terminal device matches.
  • the processing unit 1302 may be configured to configure a first endpoint identifier corresponding to the destination address, and determine the second RAN, when establishing a second bearer with the second RAN device. After the device records the destination address, the second endpoint identifier corresponding to the destination address configured by the second RAN device is obtained, and optionally, the second bearer is established with the second RAN device, and The second bearer is identified by the first endpoint identifier and the second endpoint identifier.
  • the communication device 1300 After the communication device 1300 completes the process of establishing the first bearer with the first terminal device and the second bearer with the second RAN device, the data packet transmitted between the first terminal device and the second terminal device may be Forwarding is performed by the communication device 1300. Subsequently, the handover between the RAN devices may be performed as the first terminal device moves, and the specific functions performed by the communication device 1300 are also different in different handover scenarios.
  • the receiving unit 1301 is further configured to receive a measurement report from the first terminal device, where the measurement report carries a handover indication, where the handover indication includes the service identifier, The handover indication is used to instruct the communication device 1300 to perform handover between the RAN devices for the service corresponding to the service identifier performed by the first terminal device.
  • the processing unit 1302 is further configured to: when the first terminal device performs the service corresponding to the service identifier, according to the service identifier carried in the measurement report, the communication device 1300 needs to be handed over to the third RAN device. .
  • the communication device 1300 may further include a sending unit 1303, where the sending unit 1303 is configured to send a first handover request to the third RAN device.
  • the first handover request includes the service identifier and the quality of service requirement, where the service identifier and the quality of service requirement are used to indicate that the third RAN device is established between the first terminal device and the first terminal device.
  • a third bearer where the third bearer is used to transmit the data packet sent by the first terminal device to the third RAN device.
  • the first handover request may further include a second endpoint identifier of the second RAN device, and a first communication address of the second RAN device, where the first communication address is The communication device 1300 is acquired when the second bearer is established.
  • the second endpoint identifier and the first communication address may be used to indicate that the third RAN device establishes a fourth bearer with the second RAN device, where the fourth bearer is used to transmit the fourth bearer.
  • the receiving unit 1301 is further configured to receive the measurement report sent by the first terminal device, where the measurement report carries a handover indication, where the handover indication includes the service identifier, The handover indication is used to instruct the communication device 1300 to perform handover between the RAN devices for the service corresponding to the service identifier performed by the first terminal device.
  • the processing unit 1302 may be further configured to: when the first terminal device performs the service corresponding to the service identifier, according to the service identifier carried in the measurement report, the communication device 1300 needs to be handed over to the fourth RAN device. .
  • the sending unit 1303 is further configured to send a second handover request to the fourth RAN device.
  • the second handover request includes the service identifier and the quality of service requirement, where the service identifier and the quality of service requirement are used to indicate that the fourth RAN device is established between the first terminal device and the first terminal device.
  • a fifth bearer where the fifth bearer is used to transmit the data packet sent by the fourth RAN device from the second terminal device to the first terminal device.
  • the receiving unit 1301 is further configured to receive a second communication address of the fourth RAN device from the fourth RAN device, and the destination address of the fourth RAN device configuration. Corresponding third endpoint identifier.
  • the sending unit 1303 is further configured to send the second communication address and the third endpoint identifier to the second RAN device. The second communication address and the third endpoint identifier are used to indicate that the second RAN device establishes a sixth bearer with the fourth RAN device, where the sixth bearer is used to transmit the The data packet sent by the second RAN device from the second terminal device to the fourth RAN device.
  • the processing unit 1302 is further configured to establish, according to the received second communication address and the third endpoint identifier, a seventh bearer with the fourth RAN device, where The seventh bearer is configured to transmit the data packet that the communication device 1300 sends to the fourth RAN device that has been received from the second terminal device but has not been sent yet.
  • the receiving unit 1301 is further configured to receive a measurement report from the first terminal device, where the measurement The report carries a handover indication, where the handover indication includes the service identifier, and the handover indication is used to instruct the communication device 1300 to perform handover between the RAN devices for the service corresponding to the service identifier performed by the terminal device.
  • the processing unit 1302 is further configured to: when the first terminal device performs the service corresponding to the service identifier, according to the service identifier carried in the measurement report, the communication device 1300 needs to be handed over to the fifth RAN device. Thereafter, a third handover request is sent to the fifth RAN device.
  • the third handover request includes the service identifier and the quality of service requirement, where the service identifier and the quality of service requirement are used to indicate that the fifth RAN device is established between the first terminal device and the first terminal device.
  • An eighth bearer where the eighth bearer is used to transmit the data packet sent by the first terminal device to the fifth RAN device, and the data sent by the fifth RAN device to the first terminal device The data packet of the second terminal device.
  • the third switching instruction further includes a second endpoint identifier of the second RAN device, and a first communication address of the second RAN device, where the first communication address is the communication
  • the device 1300 is acquired when the second bearer is established.
  • the second endpoint identifier and the first communication address are used to indicate that the fifth RAN device establishes a ninth bearer with the second RAN device, and the ninth bearer is used to transmit the fifth RAN The data packet sent by the device from the first terminal device to the second RAN device.
  • the receiving unit 1301 is further configured to receive a third communication address of the fifth RAN device sent by the fifth RAN device, and the destination address configured by the fifth RAN device Corresponding fourth endpoint identifier.
  • the sending unit 1303 is further configured to send the third communications address and the fourth endpoint identifier to the second RAN device, where the third communications address and the fourth endpoint are The identifier is used to indicate that the second RAN device establishes a tenth bearer with the fifth RAN device, where the tenth bearer is used to transmit the source that is sent by the second RAN device to the fifth RAN device Said data packet of the second terminal device.
  • FIG. 14 shows a schematic structural diagram 2 of the communication apparatus provided by the embodiment of the present application.
  • the communication apparatus 1400 may include a processor 1401 and a transceiver 1402.
  • the processor 1401 may be a central processing unit (CPU) or a network processor (NP).
  • the processor 1401 can also be other types of chips, such as a baseband circuit, a radio frequency circuit, an application specific integrated circuit (ASIC), a programmable logic device (PLD), or any combination thereof.
  • the transceiver 1402 can include an antenna.
  • the communication device 1400 may further include a memory 1403 for storing a program executed by the processor 1401 and data required to be processed.
  • the memory 1403 may be integrated in the processor 1401 or may be separately disposed from the processor 1401.
  • the processor 1401 is configured to receive, by the transceiver 1402, a service identifier sent by the first terminal device and a service quality requirement of the service corresponding to the service identifier, and establish, based on the service identifier and the service quality requirement, And a first bearer between the first terminal device and a second bearer between the second radio access network RAN device based on the service identity and the quality of service requirement.
  • the first bearer and the second bearer are used to transmit a data packet corresponding to the service identifier performed by the first terminal device and the second terminal device, where the second RAN device is used. Refers to the RAN device that provides the second terminal device with a service.
  • the processor 1401 may correspond to the processing unit 1302 described in the communication device 1300
  • the transceiver 1402 may correspond to the receiving unit 1301 and the sending unit 1303 described in the communication device 1300.
  • For the specific interaction process of the foregoing processor 1401 and the transceiver 1402 refer to the interaction process between the foregoing receiving unit 1301, the processing unit 1302, and the sending unit 1303, and details are not described herein again.
  • the embodiment of the present application further provides another communication device, which is used to implement the functions performed by the first terminal device in the foregoing method embodiment.
  • FIG. 15 is a first schematic structural diagram of the communication device provided by the embodiment of the present application.
  • the communication device 1500 may include a sending unit 1501 and a processing unit 1502.
  • the sending unit 1501 is configured to send, to the first RAN device, a service identifier, and a service quality requirement of the service corresponding to the service identifier.
  • the processing unit 1502 is configured to establish a first bearer with the first RAN device under the indication of the first RAN device, where the first bearer is used to transmit the communication device 1500 to perform the service identifier corresponding to The data packet transmitted between the first RAN device and the first RAN device.
  • the service identifier includes at least a destination address, where the destination address is used by at least one communication device to participate in a service corresponding to the service identifier.
  • the quality of service requirements include a first indicator for characterizing the latency requirement of the service and a second indicator for characterizing the reliability requirement of the service.
  • the service identifier and the quality of service requirement are carried in a control indication sent by the communication device 1500 to the first RAN device by using the sending unit 1501, where the control indication is used to indicate
  • the first RAN device establishes the first bearer between the service corresponding to the service identifier and the communication device.
  • the sending unit 1501 may be further configured to send a measurement report to the first RAN device, where the measurement report carries a handover indication, where the handover indication includes the service identifier, and the handover And indicating, by the first RAN device, a handover between the RAN devices for the service corresponding to the service identifier performed by the communication device 1500.
  • the communication device 1500 may further include a receiving unit 1503.
  • the receiving unit 1503 may receive related configuration parameters sent by the first RAN device for establishing the first bearer, related information for performing handover between the RANs, and the like.
  • FIG. 16 shows a schematic structural diagram 2 of the communication apparatus provided by the embodiment of the present application.
  • the communication apparatus 1600 may include a processor 1601 and a transceiver 1602.
  • the processor 1601 may be a central processing unit (CPU) or a network processor (NP).
  • the processor 1601 can also be other types of chips, such as a baseband circuit, a radio frequency circuit, an application specific integrated circuit (ASIC), a programmable logic device (PLD), or any combination thereof.
  • the transceiver 1602 can include an antenna.
  • the communication device 1600 may further include a memory 1603 for storing a program executed by the processor 1601 and data required to be processed.
  • the memory 1603 may be integrated in the processor 1601 or may be separately disposed from the processor 1601.
  • the processor 1601 is configured to send, by using the transceiver 1602, a service identifier, and a service quality requirement of a service corresponding to the service identifier, to the first RAN device, where the a first bearer between the first RAN device, where the first bearer is used to transmit a data packet transmitted between the first RAN device when the communication device 1600 performs a service corresponding to the service identifier.
  • the processor 1601 may correspond to the processing unit 1502 described in the communication device 1500
  • the transceiver 1602 may correspond to the sending unit 1501 and the receiving unit 1503 described in the communication device 1500.
  • the present application further provides a chip, the chip may be in communication with a memory, or the chip includes a memory, and the chip executes program instructions stored in the memory to implement the foregoing method embodiment.
  • the chip executes program instructions stored in the memory to implement the foregoing method embodiment.
  • the present application also provides a computer storage medium storing computer readable instructions, when the computer readable instructions are executed, such that the methods involved in the foregoing method embodiments are implemented
  • the present application further provides a computer program product comprising a software program, when it is run on a computer, to implement the first RAN device or the first terminal involved in the foregoing method embodiment The corresponding function of the device.
  • the present application further provides a communication system, which may include the first RAN device involved in the foregoing method embodiments, and/or the second RAN device, and/or the terminal device .
  • the terminal device may include the first terminal device and the second terminal device involved in the foregoing method embodiments.
  • the communication system can be a communication system comprised of a first RAN device, a second RAN device, and other network devices capable of interacting with the first RAN device or the second RAN device.
  • the communication system can also be a communication system comprised of a terminal device, a first RAN device, a second RAN device, and other network devices capable of interacting with the first RAN device or the second RAN device.
  • the communication system may also be a communication system composed of a terminal device, a first RAN device, or the like.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种通信方法及装置，该方法中第一RAN设备接收第一终端设备发送的业务标识、以及业务标识对应的业务的服务质量需求，进而第一RAN设备基于业务标识和服务质量需求，建立与第一终端设备之间的第一承载，以及，第一RAN设备基于业务标识和服务质量需求建立与第二RAN设备之间的第二承载。其中，第一承载和第二承载用于传输第一终端设备与第二终端设备之间执行的业务标识对应的业务的数据包，第二RAN设备是指为第二终端设备提供服务的RAN设备。上述方法中，终端设备之间传输的数据包可以不经过核心网设备进行转发，可以缩短数据包在网络侧的传输过程，不仅可以节省建立通信链路的时间，也可以降低数据包的传输过程中的时延。

Description

一种通信方法及装置
本申请要求在2018年05月11日提交中国专利局、申请号为201810450360.X、发明名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
现有移动通信网络中，在一些业务场景下，例如车与外界的信息交换(vehicle to everything，V2X)业务场景下，当两个终端设备之间进行数据传输时，首先需要建立起通信链路，该通信链路不仅包括两个终端设备分别与无线接入网(radio access network，RAN)设备之间的通信链路，还包括无线接入网设备与核心网设备之间的通信链路、以及核心网设备与V2X业务服务器之间的通信链路。
在建立好通信链路后，发送端可以将数据包发送给为发送端服务的第一RAN设备，进而由第一RAN设备经由核心网设备将数据包发送给V2X业务服务器，之后，再由V2X业务服务器将该数据包经由核心网设备发送给为接收端服务的第二RAN设备，最终由第二RAN设备将数据包发送给接收端。
上述现有方案，为实现终端设备之间的数据传输，需要建立用于传输数据包的多级通信链路，而多级通信链路的建立过程、以及数据包经过多级通信链路进行传输的过程存在着较大的时延，这很难满足一些业务场景中对低时延的性能需求。
发明内容
本申请提供一种通信方法及装置，用以解决现有方案在实现终端设备之间的数据传输时存在较大的时延的问题。
本申请提供的技术方案包括：
第一方面，本申请提供一种通信方法，该方法中，第一终端设备可以向第一RAN设备发送业务标识、以及该业务标识对应的业务的服务质量需求，进而第一RAN设备可以基于该业务标识和/或该服务质量需求，建立与该第一终端设备之间的第一承载，以及，基于该业务标识和/或该服务质量需求建立与第二RAN设备之间的第二承载。其中，该第一承载和/或该第二承载用于传输该第一终端设备与该第二终端设备之间执行的该业务标识对应的业务的数据包，该第二RAN设备是指为该第二终端设备提供服务的RAN设备。
通过上述方法，RAN设备可以在终端设备的触发下，基于业务标识以及对应的服务质量需求，建立起RAN设备与终端设备之间的承载、以及RAN设备之间的承载。当终端设备发起业务时，数据包可以直接经由RAN设备与终端设备之间的承载、以及RAN设备之间的承载传输至对端的终端设备，从而可以无需经过核心网设备进行转发，也可以不必建立RAN设备与核心网设备之间建立用于传输数据包的通信链路。不仅可以节省建立用于传输数据包的通信链路的时间，还可以降低数据包的传输过程中的时延。
其中，业务标识可以包括目的地址，目的地址可以被用于至少一个终端设备参与该业务标识对应的业务。与业务标识对应的业务的服务质量需求可以包括用于表征业务的时延需求的第一指标、用于表征业务的可靠性需求的第二指标等。其中，当与业务标识对应的业务为V2X业务时，服务质量需求可以包括近距离包优先级(prose per-packet priority，PPPP)、以及近距离包可靠性(prose per-packet reliability，PPPR)。
在一种实现方式中，该业务标识和/或该服务质量需求可以携带在第一终端设备向该第一RAN设备发送的控制指示中，该控制指示用于指示该第一RAN设备为该业务标识对应的业务建立与该第一终端设备之间的第一承载。
在一种实现方式中，第一RAN设备可以在识别到与业务标识对应的业务的服务质量需求为低时延、或高可靠性需求后，按照上述方法为终端设备建立第一承载和/或第二承载。例如，假设服务质量需求用PPPP、以及PPPR表示，第一RAN设备可以在确认接收的PPPP低于第一门限值、PPPR高于第二门限值时，确定与业务标识对应的业务的服务质量需求为低时延、高可靠性需求，进而按照上述方法为终端设备建立第一承载和/或第二承载。
在一种可能的设计中，该第一RAN设备可以接收来自于核心网设备的该第一终端设备的授权信息，该授权信息中包括该第一终端设备已被授权的业务的授权业务标识、以及该第一终端设备执行该已被授权的业务时的服务质量需求。这样，第一RAN设备可以在该授权业务标识中包括该业务标识、且该业务标识对应的服务质量需求与来自于该第一终端设备的该服务质量需求相匹配的情况下，建立与该第一终端设备之间的该第一承载。
上述设计中，RAN设备中可以预先从核心网设备中获取并存储有关终端设备的授权信息，后续RAN设备在接收到来自终端设备的业务标识、以及与业务标识对应的业务的服务质量需求后，可以直接将本地存储的终端设备的授权信息与接收的来自于终端设备的相关业务信息进行匹配，进而确定是否为终端设备建立无线承载，建立无线承载的过程可以无需核心网设备参与，从而尽量避免核心网控制面对建立无线承载时的时延影响。
在一种可能的设计中，该第一RAN设备在基于该业务标识和/或该服务质量需求建立与第二RAN设备之间的第二承载时，可以配置该目的地址对应的第一端点标识，以及，在确定该第二RAN设备记录有该目的地址后，获取该第二RAN设备配置的该目的地址对应的第二端点标识。可选的，该第一RAN设备在建立起与该第二RAN设备之间的第二承载后，可以利用该第一端点标识和/或该第二端点标识来标识建立该第二承载。
上述设计中，RAN设备中存储有目的地址，目的地址可以标识在RAN设备管辖范围内的终端设备支持的业务，RAN设备之间可以交互各自存储的目的地址，在确定存在相同的目的地址时，可以基于目的地址建立起RAN设备之间的承载。可选的，建立的RAN之间的承载可以通过与目的地址对应的端点标识来标识，后续RAN设备在转发数据包时，只需识别出端点标识，便可以通过该端点标识对应的承载传输数据包。
在建立起第一终端设备与第一RAN设备之间的第一承载、以及第一RAN设备与第二RAN设备之间的第二承载后，这里，假设第二RAN设备也基于来自第二终端设备的业务标识以及服务质量需求建立起了与第二终端设备之间的无线承载，第一终端设备与第二终端设备之间可以通过建立的终端设备与RAN设备之间的承载、以及RAN设备之间的承载来传输数据包。后续，随着第一终端设备的移动，可能会进行RAN设备之间的切换，随着RAN设备之间的切换，也需要更新用于传输数据包的承载。
当该第一终端设备和该第二终端设备之间单向传输该数据包，且该第一终端设备为发 送该数据包的发送端、该第二终端设备为接收该数据包的接收端时，一种更新用于传输数据包的承载的实现方式为：
第一终端设备可以向第一RAN设备可以发送测量报告，其中，该测量报告中携带切换指示，该切换指示包括该业务标识，该切换指示用于指示该第一RAN设备为该终端设备执行的该业务标识对应的业务进行RAN设备之间的切换。
该第一RAN设备在基于该测量报告中携带的该业务标识确定该第一终端设备执行该业务标识对应的业务时需要由该第一RAN设备切换至第三RAN设备后，向该第三RAN设备发送第一切换请求，其中，该第一切换请求中包括该业务标识和/或该服务质量需求，该业务标识和/或该服务质量需求用于指示该第三RAN设备建立与该第一终端设备之间的第三承载，该第三承载用于传输该第一终端设备向该第三RAN设备发送的所述数据包。
在一种实现方式中，该第一切换请求中还可以包括该第二RAN设备的第二端点标识、以及该第二RAN设备的第一通信地址，该第一通信地址为该第一RAN设备在建立该第二承载时获取的。这里，该第二端点标识和/或该第一通信地址用于指示该第三RAN设备建立与该第二RAN设备之间的第四承载，该第四承载用于传输该第三RAN设备向该第二RAN设备发送的来自于该第一终端设备的该数据包。
当该第一终端设备和该第二终端设备之间单向传输该数据包，且该第一终端设备为接收该数据包的接收端、该第二终端设备为发送该数据包的发送端时，一种更新用于传输数据包的承载的实现方式为：
第一终端设备可以向第一RAN设备发送测量报告，其中，该测量报告中携带切换指示，该切换指示包括该业务标识，该切换指示用于指示该第一RAN设备为该终端设备执行的该业务标识对应的业务进行RAN设备之间的切换。
该第一RAN设备在基于该测量报告中携带的该业务标识确定该第一终端设备执行该业务标识对应的业务时需要由该第一RAN设备切换至第四RAN设备后，向该第四RAN设备发送第二切换请求。其中，该第二切换请求中包括该业务标识和/或该服务质量需求，该业务标识和/或该服务质量需求用于指示该第四RAN设备建立与该第一终端设备之间的第五承载，该第五承载用于传输该第四RAN设备向该第一终端设备发送的来自于该第二终端设备的该数据包。
在一种实现方式中，该第一RAN设备还可以接收来自于该第四RAN设备的该第四RAN设备的第二通信地址、以及该第四RAN设备配置的该目的地址对应的第三端点标识，进而该第一RAN设备向该第二RAN设备发送该第二通信地址、以及该第三端点标识。其中，该第二通信地址以及该第三端点标识用于指示该第二RAN设备建立与该第四RAN设备之间的第六承载，该第六承载用于传输该第二RAN设备向该第四RAN设备发送的来自于该第二终端设备的该数据包。
在一种实现方式中，该第一RAN设备还可以基于接收的该第二通信地址以及该第三端点标识，建立与该第四RAN设备之间的第七承载，该第七承载用于传输该第一RAN设备向该第四RAN设备发送的已从该第二终端设备接收到但还未发送的该数据包。
当该第一终端设备与该第二终端设备之间双向传输该数据包时，一种更新用于传输数据包的承载的实现方式为：
该第一终端设备向该第一RAN设备发送测量报告，其中，该测量报告中携带切换指示，该切换指示包括该业务标识，该切换指示用于指示该第一RAN设备为该终端设备执 行的该业务标识对应的业务进行RAN设备之间的切换。
该第一RAN设备在基于该测量报告中携带的该业务标识确定该第一终端设备执行该业务标识对应的业务时需要由该第一RAN设备切换至第五RAN设备后，向该第五RAN设备发送第三切换请求。其中，该第三切换请求中包括该业务标识和/或该服务质量需求，该业务标识和/或该服务质量需求用于指示该第五RAN设备建立与该第一终端设备之间的第八承载，该第八承载用于传输该第一终端设备向该第五RAN设备发送的该数据包、以及该第五RAN设备向该第一终端设备发送的来自该第二终端设备的该数据包。
在一种实现方式中，该第三切换指令中还包括该第二RAN设备的第二端点标识、以及该第二RAN设备的第一通信地址，该第一通信地址为该第一RAN设备在建立该第二承载的时获取的。该第二端点标识以及该第一通信地址用于指示该第五RAN设备建立与该第二RAN设备之间的第九承载，该第九承载用于传输该第五RAN设备向该第二RAN设备发送的来自该第一终端设备的所述数据包。
在一种实现方式中，该第一RAN设备还可以接收该第五RAN设备发送的该第五RAN设备的第三通信地址、以及该第五RAN设备配置的该目的地址对应的第四端点标识。可选的，该第一RAN设备可以向该第二RAN设备发送该第三通信地址、以及该第四端点标识，其中，该第三通信地址以及该第四端点标识用于指示该第二RAN设备建立与该第五RAN设备之间的第十承载，该第十承载用于传输该第二RAN设备向该第五RAN设备发送的来自所述第二终端设备的所述数据包。
第二方面，本申请提供一种通信装置，所述通信装置具备实现上述第一方面涉及的第一RAN设备的功能，比如，所述通信装置包括所述第一RAN设备执行以上第一方面中涉及步骤所对应的模块或单元或手段(means)，所述功能或模块或单元或手段(means)可以通过软件实现，或者通过硬件实现，也可通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、发送单元以及接收单元，处理单元、发送单元以及接收单元执行的功能可以和上述第一方面涉及的第一RAN设备执行的步骤相对应，在此不予赘述。
在另一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面以及第一方面任意可能的设计或实现方式中第一RAN设备执行的方法。
其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，其保存实现上述第一方面涉及的第一RAN设备的功能的必要计算机程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置。本申请并不限定。所述处理器可执行所述存储器存储的计算机程序指令，完成上述第一方面以及第一方面任意可能的设计或实现方式中第一RAN设备执行的方法。
第三方面，本申请提供一种通信装置，所述通信装置具备实现上述第一方面涉及的第一终端设备的功能，比如，所述通信装置包括所述第一终端设备执行上述第一方面中涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段(means)可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、发送单元以及接收单元，处理单元、发送单元以及接收单元执行的功能可以和上述第一方面涉及的第一终端设备执行的步骤相对应，在此不予赘述。
在另一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面以及第一方面任意可能的设计或实现方式中第一终端设备执行的方法。
其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，其保存实现上述第一方面涉及的第一终端设备的功能的必要计算机程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置。本申请并不限定。所述处理器可执行所述存储器存储的计算机程序指令，完成上述第一方面以及第一方面任意可能的设计或实现方式中第一终端设备执行的方法。
第四方面，本申请提供一种芯片，所述芯片可以与存储器相通信，或者所述芯片中包括存储器，所述芯片执行所述存储器中存储的程序指令，以实现上述第一方面中所涉及的所述第一RAN设备或者所述第一终端设备的相应功能。
第五方面，本申请提供一种计算机存储介质，所述计算机存储介质存储有计算机可读指令，所述计算机可读指令被执行时，使得实现上述第一方面中所涉及的所述第一RAN设备或者所述第一终端设备的相应功能。
第六方面，本申请还提供一种包含软件程序的计算机程序产品，当其在计算机上运行时，使得实现上述第一方面中所涉及的所述第一RAN设备或者所述第一终端设备的相应功能。
第七方面，本申请还提供一种通信系统，在所述通信系统中包括上述第一方面中所涉及的所述第一RAN设备，和/或，所述第二RAN设备，和/或，终端设备。其中，终端设备可以包括上述第一方面中所涉及的所述第一终端设备和所述第二终端设备。
附图说明
图1为本申请提供的一种可能的通信系统的网络架构图；
图2为本申请实施例提供的通信方法的流程示意图；
图3A为本申请实施例提供的建立第一承载的流程示意图一；
图3B为本申请实施例提供的建立第一承载的流程示意图二；
图4A为本申请实施例提供的第二承载的场景示意图一；
图4B为本申请实施例提供的第二承载的场景示意图二；
图5为本申请实施例提供的建立第二承载的流程示意图；
图6A为本申请实施例提供的数据包传输的应用场景示意图一；
图6B为本申请实施例提供的数据包传输的应用场景示意图二；
图7为本申请实施例提供的切换场景一的示意图；
图8为本申请实施例提供的切换场景一中更新用于传输数据包的通信链路的流程示意图；
图9为本申请实施例提供的切换场景二的示意图；
图10为本申请实施例提供的切换场景二中更新用于传输数据包的通信链路的流程示意图；
图11为本申请实施例提供的切换场景三的示意图；
图12为本申请实施例提供的切换场景三中更新用于传输数据包的通信链路的流程示意图；
图13为本申请实施例提供的一种通信装置的示意图一；
图14为本申请实施例提供的一种通信装置的示意图二；
图15为本申请实施例提供的另一种通信装置的示意图一；
图16为本申请实施例提供的另一种通信装置的示意图二。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
首先，对本申请提供的技术方案可适用的通信系统进行说明。
本申请提供的技术方案可适用在各种通信系统中，例如长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)通信系统、以及其它类似的通信系统。
图1示例性示出了一种可能的通信系统的网络架构图。该网络架构包括终端设备、RAN设备、核心网设备。可选的，在一种实现方式中，该网络架构下的核心网设备还可以连接到外部的数据网络。
其中，终端设备可以用于通过无线空口接入到运营商部署的RAN设备，继而通过核心网设备访问外部的数据网络。终端设备也可称为用户设备(user equipment，UE)，例如为手机、车联网终端、电脑、蜂窝电话、无绳电话、会话发起协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、膝上型计算机、手持式通信设备、手持式计算设备、卫星无线设备、无线调制解调器卡、电视机顶盒(set top box，STB)、用户驻地设备(customer premise equipment，CPE)等任意可以用于在上述通信系统上进行通信的设备。
RAN设备可以用于实现无线物理层功能、无线资源管理、无线接入控制以及移动性管理等功能。RAN设备可以为LTE系统或演进的LTE系统中的基站，例如节点B(Node B，NB)、演进型节点B(evolved Node B，eNB)，或者也可以为5G系统中的接入节点(access point，AP)、下一代节点B(next generation Node B，gNB)、下一代演进型节点B(ng-eNB，gNB)、收发点(transmission receive point，TRP)、传输点(transmission point，TP)或某种其它接入节点等。
核心网设备可以包含但不限于管理设备和网关设备，其中，管理设备可以用于终端设备的注册、安全认证、移动性管理和位置管理等，网关设备可以用于建立、维护、释放与终端设备之间的传输通道，还可以在该传输通道上转发终端设备和外部的数据网络之间通信时的数据包。
数据网络可以包含网络设备(例如，服务器、路由器等)，数据网络可以用于为终端设备提供多种数据业务服务，例如V2X业务等。
应理解，图1仅为示例性网络架构图，除图1中所示的网元设备之外，该网络架构还可以包括其他网元设备或功能单元，本申请对此并不限定。
基于上述示出的通信系统，在一些业务场景下，例如V2X业务场景下，当终端设备之间需要进行数据传输时，现有方案中终端设备首先向核心网设备发起注册过程，由核心网为终端设备建立和维护用于传输数据包的通信链路。通信链路具体包括核心网设备指示RAN设备建立的RAN设备与终端设备之间的通信链路、核心网设备与RAN设备之间建立的通信链路、以及核心网设备与数据网络中的服务器之间的通信链路等。基于建立起的 通信链路，作为发送端的终端设备发送的数据包需要经过为发送端提供服务的RAN设备、核心网设备、数据网络中的服务器、核心网设备、以及为接收端提供服务的RAN设备才能被作为接收端的终端设备接收。
由此可见，终端设备之间进行数据传输时，建立用于传输数据包的多级通信链路的过程存在着较大的时延，数据包经过建立的多级通信链路在网络侧传输的过程也存在着较大的时延。示例性的，尽管另一现有方案中提出终端设备之间可以通过直连的通信链路进行数据包的传输，即设备到设备(device-to-device，D2D)通信，可以使终端设备之间的数据包的传输时延较低，但是这种通信方式下终端设备之间需要经过竞争机制来抢占用于传输数据包的无线资源等，使得终端设备之间通信时很容易造成丢包现象，使得可靠性较低。故此，按照现有技术中提出的终端设备之间的数据传输方式，在一些业务场景下很难兼顾低时延、以及高可靠性的性能需求。
为解决上述问题，本申请提出了一种通信方法及设备，建立了终端设备之间通过RAN设备来传输数据包的通信链路，数据包可以不经过核心网设备进行转发，缩短了数据包在网络侧的传输过程，不仅可以节省建立通信链路的时间，后续数据包的传输过程中也可以降低传输时延。数据包通过无线接入网侧进行传输，RAN设备可以提供管理无线资源的功能，为终端设备分配用于传输数据包的无线资源，从而可以尽量避免现有D2D方案中终端设备之间抢占无线资源的情况，因此也可以兼顾终端设备之间传输数据包的可靠性。
下面，首先对本申请实施例提供的建立通信链路的方式进行详细说明。其中，本申请中涉及的通信链路包括终端设备与RAN设备之间的通信链路、以及RAN设备与RAN设备之间的通信链路。需要理解的是，下文的描述中通信链路也可以被称为承载。示例性的，下文中涉及的“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序等。例如，下文的描述中采用第一终端设备和第二终端设备分别作为传输数据包的两端。其中，第一终端设备既可以作为发送端，也可以作为接收端，相应地，当第一终端设备为发送端时，第二终端设备为接收端，当第一终端设备为接收端时，第二终端设备为发送端。此外，第一终端设备和第二终端设备之间并不限定于单向通信，还可以进行双向通信。
参照图2所示，为本申请实施例提供的通信方法的流程示意图。该实施例中以第一终端设备、以及为第一终端设备提供服务的第一RAN设备为例，描述了第一RAN设备在第一终端设备的触发下建立第一终端设备与第二终端设备之间传输数据包的通信链路的过程。具体包括以下步骤：
步骤201：第一终端设备向第一RAN设备发送业务标识、以及所述业务标识对应的业务的服务质量需求。
具体的，所述业务标识至少包括目的地址，所述目的地址可以被用于至少一个终端设备参与所述业务标识对应的业务。也可以理解为，所述目的地址可以用于标识业务，能够执行同一业务的至少一个终端设备可以配置有同一目的地址，这样，使用同一目的地址的至少一个终端设备可以参与同一业务。例如，假设第一终端设备向第一RAN设备发送的业务标识为目的地址#1，那么同样配置了目的地址#1的第二终端设备与第一终端设备之间可以基于建立好的通信链路传输执行目的地址#1标识的业务的数据包。此外，包含第一终端设备在内的至少一个终端设备中配置的目的地址可以有至少一个，具体配置的目的地址的数目可以根据至少一个终端设备实际支持的业务的个数来确定。可选的，第一终端设备 向第一RAN设备上报的业务标识的数目也可以为至少一个。例如，若业务标识用目的地址来表示时，那么，第一终端设备可以向第一RAN设备上报至少一个目的地址。在一个示例中，至少一个目的地址可以采用目的地址列表的形式。
所述业务标识还可以包括业务类型，在V2X业务场景下，作为车联网终端的第一终端设备支持的业务类型例如可以包括用于表征某一路段出现交通事故的事故类业务、用于表征某一路段出现拥堵的拥堵类业务等。这里目的地址可以与业务类型一一对应，一个目的地址还可以与多种业务类型对应等，本申请对此并不限定。
所述业务标识对应的业务的服务质量需求可以包括用于表征业务的时延需求的第一指标，还可以包括用于表征业务的可靠性需求的第二指标等。其中，第一指标例如为PPPP、第二指标例如为PPPR。当然，还可以采用能够同时表征业务的时延需求、以及可靠性需求的第三指标，例如服务质量(quality of service，QoS)参数等，本申请对此并不限定。
具体实施时，第一终端设备可以在附着网络的过程中向第一RAN设备上报业务标识以及服务质量需求，也可以在成功附着到网络后请求发起业务时向第一RAN设备上报业务标识以及服务质量需求等。具体上报方式将在后文中进行示例性说明。
步骤202：第一RAN设备基于来自于第一终端设备的业务标识以及服务质量需求，建立与第一终端设备之间的第一承载。
步骤203：第一RAN设备基于来自于第一终端设备的业务标识以及服务质量需求，建立与第二RAN设备之间的第二承载。
其中，第二RAN设备是指为第二终端设备提供服务的RAN设备，第二终端设备指除第一终端设备以外能够执行所述业务标识对应的业务的终端设备。建立的第一承载和/或第二承载可以用于传输第一终端设备与第二终端设备之间执行的所述业务标识对应的业务的数据包。这里，第二RAN设备也可以接收到来自于第二终端设备的业务标识并存储在本地，可选的，第二RAN设备接收的来自于第二终端设备的业务标识与第一RAN设备接收的来自于第一终端设备的业务标识可以相同，这样，第一RAN设备可以针对相同的业务标识建立与第二终端设备之间的第二承载。
一种实现方式中，第一RAN设备接收到来自第一终端设备的业务标识以及所述业务标识对应的业务的服务质量需求后，可以首先判断服务质量需求是否表征为低时延、高可靠性需求，若是，则可以按照步骤202和步骤203的方式为第一终端设备建立起第一承载和/或第二承载，若否，则可以依据现有方案来建立第一终端设备与第二终端设备之间数据包的传输路径。例如，当服务质量需求用PPPP、PPPR来表示时，可以为PPPP配置第一门限值，为PPPR配置第二门限值，当PPPP低于第一门限值、PPPR高于第二门限值时，确定为低时延、高可靠性需求，进而采用本实施例一提供的方案建立第一承载和/或第二承载。当然，实际应用时，本申请实施例也可以适用于存在低时延需求的场景下、或者存在高可靠性需求的场景下，随着业务需求的不断丰富，本申请实施例还可以适用于其他类似的业务需求的场景下。
需要说明的是，本申请中所述数据包可以泛指一类数据包，第一终端设备和第二终端设备之间执行所述业务标识对应的业务时交互的数据包均可以被归为一类数据包。可选的，第一RAN设备建立第一承载以及第二承载的过程可以为彼此独立的过程，故上述步骤202和步骤203在执行顺序上可以不分先后顺序。
下面，分别针对上述步骤202所述的建立第一承载的过程，以及上述步骤203所述的 建立第二承载的过程进行具体介绍。
(一)第一RAN设备基于来自于第一终端设备的业务标识以及服务质量需求，建立与第一终端设备之间的第一承载。
其中，第一RAN设备与第一终端设备之间的第一承载可以理解为第一RAN设备与第一终端设备之间的无线承载。
鉴于第一终端设备既可以作为发送数据包的发送端，也可以作为接收数据包的接收端，那么，当第一终端设备为发送端时，第一RAN设备为为发送端提供服务的RAN设备，当第一终端设备为接收端时，第一RAN设备为为接收端提供服务的RAN设备。下面对这两种情况进行分别介绍。
情况A1：第一终端设备为发送端，第一RAN设备为为发送端提供服务的RAN设备。为便于描述，以第一终端设备为Tx UE，第一RAN设备为gNB#1，第一承载为无线承载#1为例进行说明。
在示例一中，建立无线承载#1的过程可参照图3A所示，包括以下步骤：
步骤301A：Tx UE向gNB#1发送控制指示。
一种实现方式中，Tx UE向gNB#1发送控制指示可以在请求附着网络的过程中实现。另一种实现方式中，Tx UE向gNB#1发送控制指示也可以在成功附着网络后请求发起业务的过程中实现。所述控制指示可以包括业务标识、以及与所述业务标识对应的业务的服务质量需求。
其中，Tx UE发送的控制指示可以携带在非接入层(non-access stratum，NAS)消息中，这种情况下，gNB#1接收NAS消息后不解析控制指示，透明转发至核心网设备。或者，Tx UE发送的控制指示还可以携带在接入层(access stratum，AS)消息中，这种情况下，gNB#1接收AS消息后可以解析控制指示，并将解析出的控制指示发送给核心网设备。
步骤302A：gNB#1向核心网设备发送来自于Tx UE的控制指示。
步骤303A：核心网设备向gNB#1发送承载建立请求。
核心网设备接收到控制指示后，通过识别业务标识获取与业务标识对应的服务质量需求，并将业务标识、以及对应的服务质量需求携带在承载建立请求中发送给gNB#1。
步骤304A：gNB#1为Tx UE配置无线承载#1。
gNB#1接收到承载建立请求后，可以基于承载建立请求中携带的服务质量需求，为Tx UE配置用于建立无线承载#1的参数并通过无线资源控制(radio resource control，RRC)信令指示给Tx UE。
步骤305A：Tx UE向gNB#1发送承载建立完成指示。
Tx UE可基于接收的用于建立无线承载#1的参数完成无线承载#1的配置，并在配置成功后，向gNB#1发送承载建立完成指示，承载建立完成指示也可以携带在RRC信令中。具体实施时，上述步骤305A也可以为可选步骤。
步骤306A：gNB#1向核心网设备发送承载建立完成响应。
该承载建立完成响应可以指示核心网设备对Tx UE基于无线承载#1传输的数据包进行计费等控制策略操作。另外，该承载建立完成响应还可以指示核心网设备在无线承载#1被释放时保留该无线承载#1的配置参数。
至此，Tx UE与gNB#1之间的无线承载#1建立完成、建立的无线承载#1用于传输Tx UE执行所述业务标识对应的业务时向gNB#1发送的数据包。
上述示例一，核心网设备参与了Tx UE与gNB#1之间建立无线承载#1的过程，考虑到核心网设备的参与，对建立无线承载#1带来较长的时延，故在示例二中，设计了可以直接由gNB#1建立无线承载#1，以便尽可能减少建立无线承载#1的时延。
在示例二中，建立无线承载#1的过程可参照图3B所示，包括以下步骤：
步骤301B：Tx UE向gNB#1发送控制指示，控制指示中携带有Tx UE的业务标识、以及业务标识对应的业务的服务质量需求。
其中，同上述步骤301A所述，控制指示既可以在请求附着网络的过程中发送给gNB#1，也可以在请求发起业务的过程中发送给gNB#1。控制指示用于指示gNB#1为业务标识对应的业务建立与Tx UE之间的无线承载#1。
步骤302B：gNB#1在确定来自于Tx UE的业务标识、服务质量需求满足预设条件后，为Tx UE配置无线承载#1。
一种实现方式中，gNB#1中预先存储有来自于核心网设备的有关Tx UE的授权信息，授权信息中包括Tx UE已被授权的业务的授权业务标识、以及Tx UE执行已被授权的业务时的服务质量需求。gNB#1在接收到来自于Tx UE的业务标识、服务质量需求后，在判断出授权业务标识中包含来自于Tx UE的业务标识，可选的，在预先存储的业务标识对应服务质量需求与来自于Tx UE的服务质量需求相匹配的情况下，确认满足预设条件，进而为Tx UE的该业务标识对应的业务配置无线承载#1。其中，在预先存储的业务标识对应服务质量需求与来自于Tx UE的服务质量需求相同或相近的情况下，可以视为两者相匹配。相近可以理解为两者之间的差距不超出设定阈值。另外，在gNB#1接收的来自于Tx UE的业务标识、服务质量需求的格式与预先存储的来自于核心网设备的授权业务标识、授权业务标识对应的服务质量需求的格式不一致的情况下，gNB#1可以先将两者的格式统一后，再进行上述分析过程。
gNB#1在为Tx UE配置无线承载#1时，可以通过RRC信令将配置的用于建立无线承载#1的参数指示给Tx UE。
步骤303B：Tx UE向gNB#1发送承载建立完成指示。
Tx UE可以基于接收的用于建立无线承载#1的参数完成无线承载#1的配置，并在配置成功后，向gNB#1发送承载建立完成指示，承载建立完成指示也可以携带在RRC信令中。具体实施时，上述步骤303B也可以为可选步骤。
步骤304B：gNB#1向核心网设备发送承载建立完成响应。
其中，承载建立完成响应中可以携带Tx UE的终端标识、无线承载#1的服务质量需求、以及时频资源等信息，以便后续在Tx UE通过无线承载#1传输数据包的过程中，由核心网设备完成对Tx UE的计费等策略控制操作，另外，该承载建立完成响应还可以指示核心网设备在无线承载#1被释放时保留该无线承载#1的配置参数。
至此，Tx UE与gNB#1之间的无线承载#1建立完成、且建立的无线承载#1用于传输Tx UE执行所述业务标识对应的业务时，向gNB#1发送数据包。
情况A2：第一终端设备为接收端，第一RAN设备为接收端提供服务的RAN设备。为便于描述，以第一终端设备为Rx UE，第一RAN设备为gNB#2，第一承载为无线承载#2为例进行说明。
其中，上述示例一和/或示例二中记载的方案可以同样适用于gNB#2与Rx UE之间建立无线承载#2的过程。示例一和/或示例二给出的方案可以通过控制面信令的交互来完成 无线承载的建立。
针对情况A2，本申请实施例还提供了建立无线承载#2的示例三。示例三给出的方式，是在发送端与gNB#2之间已经建立好通信链路的情况下实现的。具体的，gNB#2可以基于与发送端之间建立好的通信链路接收到来自于发送端的数据包，其中，数据包的包头可以包括业务标识以及业务标识对应的业务的服务质量需求等。由于发送端和接收端执行同一业务时的服务质量需求基本相同，故gNB#2可以根据来自于发送端的数据包的包头的业务标识以及服务质量需求，建立起gNB#2与Rx UE之间的无线承载#2。可选的，gNB#2可以将来自于发送端的数据包通过无线承载#2发送给Rx UE。示例三给出的方案中gNB#2可以在转发数据包的过程中完成与Rx UE之间的无线承载#2的建立。
以上三个示例中列举出第一RAN设备建立与第一终端设备之间的第一承载的方式，第一RAN设备可以为第一终端设备执行的业务标识对应的业务建立起用于传输数据包的第一承载。可选的，示例二和示例三中，第一RAN设备建立第一承载的过程中，可以不需要核心网设备的参与，从而可以减少建立第一承载的时延。另外，关于第二终端设备与第二RAN设备之间也可以参照上述示例建立起无线承载，这里不再一一赘述。
(二)第一RAN设备基于来自于第一终端设备的业务标识以及服务质量需求，建立与第二RAN设备之间的第二承载。
在介绍第二承载的建立过程之前，首先对第二承载的概念做出进一步说明。参照图4A和图4B所示的场景示意图，第一RAN设备与第二RAN设备之间的第二承载，又可称为RAN间的隧道，可以是基于X2接口的直连链路(图4A所示)，也可以是第一RAN设备与第二RAN设备基于桥接(bridge)功能模块而建立起的桥接链路(图4B所示)等。其中，在RAN设备之间不存在X2接口的情况下，RAN设备之间可以通过bridge功能模块完成RAN设备之间的控制面信令以及用户面数据的交互。具体的，bridge功能模块可以和RAN设备共部署，也可以和RAN设备分离部署。可选的，RAN设备之间当通过bridge功能模块交互控制面信令或用户面数据时，bridge功能模块起到透明转发的作用，实际可以看做是RAN设备之间直接进行交互。
下面，结合图5所示的示例四，对第二承载的建立过程进行说明。为便于描述，以第一终端设备为Tx UE，第一RAN设备为gNB#1，第二RAN设备为gNB#2为例进行说明，并且下文中RAN设备之间的承载用隧道来表示。
步骤501：Tx UE向gNB#1发送控制指示。所述控制指示可以包括业务标识，这里，业务标识以目的地址为例。
关于控制指示的具体说明，可参见本申请上述示例一中的描述，不再一一赘述。
步骤502：gNB#1记录所述目的地址，并确定同样记录有所述目的地址的gNB#2。
步骤503：gNB#1配置所述目的地址对应的第一端点标识，以及，获取gNB#2配置的所述目的地址对应的第二端点标识。
步骤504：gNB#1建立与gNB#2之间的隧道，并利用第一端点标识和/或第二端点标识来标识建立的隧道。
一种实现方式中，gNB#1可以接收处于gNB#1服务范围内的终端设备发送的目的地址，并记录终端设备的标识与目的地址之间的第一映射关系。其中，终端设备的标识是可以唯一标识该终端设备的标识，例如可以是国际移动用户识别码(International Mobile Subscriber Identification Number，IMSI)、客户识别模块(Subscriber Identity Module，SIM) 号、互联网协议(Internet Protocol，IP)地址、L2层地址(例如为媒体访问控制(Media Access Control，MAC)地址等)、或其他可以确定终端设备的标识，如终端设备的临时标识、或终端设备的位置信息等。
相应地，对于其它RAN设备，例如gNB#2来说，也可以接收到处于gNB#2服务范围内的终端设备发送的目的地址，并记录终端设备的标识与目的地址之间的第一映射关系。其中，记录的终端设备的标识与目的地址之间的第一映射关系例如可以采用列表的形式，如表1所述：
表1
终端设备#1 目的地址#1
终端设备#2 目的地址#2
...... ......
终端设备#n 目的地址#n
需要理解的是，上述表1仅作为示例性说明，并不限定目的地址与终端设备具备一一对应的关系，实际上，一个目的地址可以对应多个终端设备的标识，一个终端设备的标识也可以对应多个目的地址。这是因为，目的地址用于标识终端设备支持的业务，一个终端设备可以支持多种业务，因此一个终端设备的标识可以对应多个目的地址，而多个终端设备可以支持同一个业务，因此一个目的地址可以对应多个终端设备的标识。
gNB#1与gNB#2之间可以通过路由更新等通信方式交互自身记录的目的地址，并根据交互的目的地址，建立RAN设备的标识与目的地址之间的第二映射关系。其中，RAN设备的标识是可以唯一标识RAN设备的标识，例如可以是RAN设备的IP地址、L2层地址(例如为MAC地址等)、或其他可以确定RAN设备的标识等。例如，假设gNB#1中记录了目的地址#1、目的地址#2、目的地址#3，gNB#2中记录了目的地址#1、目的地址#2，那么，gNB#1与gNB#2将自身记录的目的地址进行交互之后，生成的第二映射关系的列表如表2所示：
表2
gNB#1 目的地址#1
gNB#1 目的地址#2
gNB#1 目的地址#3
gNB#2 目的地址#1
gNB#2 目的地址#2
gNB#1可以根据第二映射关系，确定gNB#2同样记录有目的地址#1、目的地址#2。进而gNB#1可以确定与gNB#2之间可以基于目的地址#1建立隧道，也可以基于目的地址#2建立隧道。可选的，为了标识建立的隧道对应哪一个目的地址，gNB#1可以配置目的地址#1对应的端点标识#1A，目的地址#2对应的端点标识#2A。其中，端点标识也可以理解为是隧道接口。
相应地，对于gNB#2来说，也可以确定与gNB#1之间可以基于目的地址#1和/或目的地址#2分别建立隧道，因此，gNB#2也可以配置目的地址#1对应的端点标识#1B，目的地 址#2对应的端点标识#2B。
可选的，gNB#1可以与gNB#2之间交互各自配置的与目的地址对应的端点标识，这样，gNB#1可以利用端点标识#1A、端点标识#1B来标识基于目的地址#1建立的隧道，利用端点标识#2A、端点标识#2B来标识基于目的地址#2建立的隧道。
至此，可以完成gNB#1与gNB#2之间的隧道的建立。后续，可以基于建立的隧道转发来自于终端设备的数据包。
上述示例一至示例四对建立第一承载、第二承载的过程进行了介绍。下面将结合具体应用场景，示例性说明基于第一承载和第二承载进行数据包的传输的过程。应理解的是，以下应用场景中，已假设接收端Rx UE与gNB#2之间已建立起无线承载。
参照图6A所示的应用场景示意图一，当gNB#1接收到来自于Tx UE的数据包后，若gNB#1确定数据包的包头中携带有目的地址#1，可以通过目的地址#1匹配到端点标识#1B，进而直接将该数据包通过端点标识#1B标识的隧道转发至gNB#2处。可选的，gNB#2可以根据记录的终端设备的标识与目的地址之间的第一映射关系，确定出处于其服务范围内的至少一个Rx UE与目的地址#1之间存在第一映射关系，那么可以间接说明至少一个Rx UE支持目的地址#1标识的业务，进而gNB#2可以直接将来自于Tx UE的数据包转发给处于gNB#2的服务范围内的至少一个Rx UE。
此外，gNB#1接收到来自于Tx UE的数据包后，不仅可以进行上述图6A所示的RAN设备之间的转发，还可以进行RAN内的转发。继续参照图6B所示的应用场景示意图二，若gNB#1根据记录的终端设备的标识与目的地址之间的第一映射关系，还确定出处于gNB#1的服务范围内的至少一个Rx UE与目的地址#1之间存在第一映射关系，那么可以间接说明至少一个Rx UE支持目的地址#1标识的业务，进而gNB#1可以直接将来自于Tx UE的数据包转发给处于gNB#1的服务范围内的至少一个Rx UE。
由此可见，本申请提供的上述方案中，第一终端设备和第二终端设备之间进行数据包传输时，可以不经过核心网设备的转发，直接在RAN内或RAN间传输数据包，能够减少数据包的传输时延。示例性，数据包经由RAN转发，由RAN设备管理用于传输数据包的无线资源等，相比D2D通信，也可以降低丢包率，从而能够兼顾数据包传输的可靠性。
考虑到在建立好用于传输数据包的通信链路后，当Tx UE或者Rx UE发生移动时，可能会进行RAN设备之间的切换，而进行RAN设备之间的切换会使得之前已建立的通信链路中部分通信链路失效，这种情况下需要对用于传输数据包的通信链路进行更新，以保证Tx UE与Rx UE之间能够正常传输数据包。
下面列举几种切换场景，分别对更新用于传输数据包的通信链路的过程进行说明。
切换场景一：
参照图7所示，假设第一终端设备为Tx UE，第二终端设备为Rx UE，为第一终端设备提供服务的第一RAN设备为gNB#1，为第二终端设备提供服务的第二RAN设备为gNB#2，第一终端设备和第二终端设备之间进行单向通信。已建立好用于传输的Tx UE与Rx UE之间的数据包的通信链路包括Tx UE与gNB#1之间的无线承载#1、gNB#1与gNB#2之间的隧道#1，Rx UE与gNB#2之间的无线承载#2。初始状态下，Tx UE发送的数据包通过无线承载#1发送给gNB#1，进而由gNB#1通过隧道#1发送给gNB#2，然后由gNB#2通过无线承载#2将数据包发送给Rx UE。
当Tx UE由gNB#1的服务范围内移动至gNB#1-N的服务范围内时，更新用于传输数 据包的通信链路的流程可参照图8所示，具体包括以下步骤：
步骤801：Tx UE由gNB#1的服务范围内向gNB#1-N的服务范围内移动过程中，向gNB#1发送第一测量报告(measurement report#1)。
其中，第一测量报告中除了携带目标gNB的信号强度、物理小区标识(physical cell identifier，PCI)信息等现有的参数外，还可以携带有切换指示，所述切换指示中包括业务标识，切换指示用于指示gNB#1为Tx UE执行的业务标识对应的业务进行RAN设备之间的切换。此外，切换指示中还可以包括业务标识对应的业务的服务质量需求。具体是否需要携带服务质量需求，可根据gNB#1的配置情况来确定，例如，若gNB#1的配置方式为在建立无线承载#1时存储了业务标识对应的业务的服务质量需求，那么Tx UE发送的第一测量报告中可以不携带该服务质量需求。
步骤802：gNB#1基于接收的第一测量报告确定Tx UE执行业务标识对应的业务时需要由gNB#1切换至gNB#1-N，进而向gNB#1-N发送第一切换请求(handover request#1)。
其中，第一切换请求中包括Tx UE的终端标识、业务标识、以及与业务标识对应的业务的服务质量需求。这里以业务标识为目的地址#1为例。第一切换请求中包括的目的地址#1、以及服务质量需求用于指示gNB#1-N建立与Tx UE之间的无线承载#3。
另外，由于Tx UE切换到gNB#1-N时，后续数据包的传输需要由gNB#1-N发送给gNB#2，故gNB#1也可以在第一切换请求中携带gNB#2配置的目的地址#1对应的端点标识#1B、以及gNB#2的通信地址等，端点标识#1B、以及gNB#2的通信地址用于指示gNB#1-N建立与gNB#2之间的隧道#2。其中，gNB#2的通信地址可以是gNB#1在建立与gNB#2之间的隧道#1的过程中获取的，gNB#2的通信地址可以为L2协议层地址，如MAC地址等。在一个例子中能够，gNB#1可以在通过路由更新的方式与gNB#2交互各自记录的目的地址时获取的gNB#2的通信地址。
步骤803：gNB#1-N解析第一切换请求中携带的内容，根据解析出的目的地址#1、以及服务质量需求等为Tx UE配置用于建立无线承载#3的参数，进而向gNB#1发送第一切换响应(handover request ack#1)。
第一切换响应中包括第一切换命令(handover command#1)，第一切换命令中包括Tx UE的终端标识、用于建立无线承载#3的参数、安全算法等。
步骤804：gNB#1-N解析第一切换请求中携带的内容，根据解析出的端点标识#1B、以及gNB#2的通信地址，完成gNB#1-N与gNB#2之间的隧道#2的配置。
步骤805：gNB#1从接收的第一切换响应中解析出第一切换命令，并通过RRC信令将第一切换命令发送给Tx UE。
步骤806：Tx UE接收到第一切换命令后，基于第一切换命令中携带的内容完成无线承载#3的配置，并从gNB#1上去附着。
后续，Tx UE可以将数据包通过无线承载#3发送至gNB#1-N，进而由gNB#1-N通过隧道#2发送至gNB#2，然后由gNB#2通过无线承载#2发送给Rx UE。
需要说明的是，考虑到Tx UE由gNB#1切换至gNB#1-N的过程中，gNB#1中可能缓存了已从Tx UE处接收到但还未发送至gNB#2的数据包，这种情况下，gNB#1可以继续沿用隧道#1向gNB#2之间发送数据包，在缓存的数据包发送完成后，再使得隧道#1失效。可选的，Tx UE在成功由gNB#1切换至gNB#1-N之后，gNB#1也可以删除Tx UE的相关信息，例如用于建立无线承载#1的参数等。
此外，Tx UE在移动过程中还可以出现由gNB#1的服务范围内移动至gNB#2的服务范围内的情况，这种情况下，gNB#1可以指示gNB#2建立与Tx UE之间的无线承载，具体流程可以参照上述图8所示的建立无线承载#3的过程，本申请不再一一赘述。
切换场景二：
参照图9所示，假设第一终端设备为Rx UE，第二终端设备为Tx UE，为第一终端设备提供服务的第一RAN设备为gNB#2，为第二终端设备提供服务的第二RAN设备为gNB#1，第一终端设备和第二终端设备之间进行单向通信。已建立好用于传输的Tx UE与Rx UE之间的数据包的通信链路包括Tx UE与gNB#1之间的无线承载#1、gNB#1与gNB#2之间的隧道#1，Rx UE与gNB#2之间的无线承载#2。初始状态下，Tx UE发送的数据包通过无线承载#1发送给gNB#1，进而由gNB#1通过隧道#1发送给gNB#2，然后由gNB#2通过无线承载#2将数据包发送给Rx UE。
当Rx UE由gNB#2的服务范围内移动至gNB#2-N的服务范围内时，更新用于传输数据包的通信链路的流程可参照图10所示，具体包括以下步骤：
步骤1001：Rx UE由gNB#2的服务范围内向gNB#2-N的服务范围内移动过程中，向gNB#2发送第二测量报告(measurement report#2)。
其中，第二测量报告中携带有切换指示，所述切换指示中包括业务标识，切换指示用于指示gNB#2为Rx UE执行的业务标识对应的业务进行RAN设备之间的切换。有关第二测量报告的其它解释说明可参见步骤801中对第一测量报告的介绍，这里不再赘述。
步骤1002：gNB#2基于接收的第二测量报告确定Rx UE执行业务标识对应的业务时需要由gNB#2切换至gNB#2-N，进而向gNB#2-N发送第二切换请求(handover request#2)。
其中，第二切换请求中包括Rx UE的终端标识、业务标识、以及与业务标识对应的业务的服务质量需求。这里以业务标识为目的地址#1为例。第一切换请求中包括的目的地址#1、以及服务质量需求用于指示gNB#2-N建立与Rx UE之间的无线承载#4。
步骤1003：gNB#2-N解析第一切换请求中携带的内容，根据解析出的目的地址#1、以及服务质量需求等为Rx UE配置用于建立无线承载#4的参数，并针对目的地址#1进行隧道接口配置，进而向gNB#2发送第二切换响应(handover request ack#2)。
其中，gNB#2-N在针对目的地址#1进行隧道接口配置时，可以配置目的地址#1对应的第三端点标识，即端点标识#1C作为隧道接口。
所述第二切换响应中包括第二切换命令(handover command#2)，第二切换命令中包括Rx UE的终端标识、用于建立无线承载#4的参数、安全算法等。所述第二切换响应中还包括gNB#2-N配置的端点标识#1C、以及gNB#2-N的通信地址。其中，gNB#2-N的通信地址可以为L2协议层地址，如MAC地址等。
步骤1004：gNB#2从接收的第二切换响应中解析出端点标识#1C、以及gNB#2-N的通信地址，完成gNB#2与gNB#2-N之间的隧道#3的配置。
其中，需要理解的是，步骤1004可以为可选步骤。即，当gNB#2中缓存了已从gNB#1处接收到但还未发送至Rx UE的来自于Tx UE的数据包时，gNB#2可以基于端点标识#1C、以及gNB#2-N，建立gNB#2与gNB#2-N之间的隧道#3，以便将缓存的来自于Tx UE的数据包发送给gNB#2-N，进而由gNB#2-N通过建立的无线承载#4发送给Rx UE。
步骤1005：gNB#2向gNB#1发送第一承载更新请求(bearer update request#1)，第一承载更新请求中携带有端点标识#1C、以及gNB#2-N的通信地址。第一承载更新请求用于 指示gNB#1建立与gNB#2-N之间的隧道#4。
步骤1006：gNB#1根据从第一承载更新请求中解析出的端点标识#1C、以及gNB#2-N的通信地址，完成gNB#1与gNB#2-N之间的隧道#4的配置。
其中，隧道#4可以用于传输gNB#1向gNB#2-N发送的来自于Tx UE的数据包。
步骤1007：gNB#1向gNB#2发送第一承载更新响应(bearer update request ack#1)，指示gNB#2已经完成隧道#4的配置。
其中，需要理解的是，步骤1007也可以为可选步骤。
步骤1008：gNB#2将从第二切换响应中解析出的第二切换命令通过RRC信令发送给Rx UE。
步骤1009：Rx UE接收到第二切换命令后，基于第二切换命令中携带的内容完成无线承载#4的配置，并从gNB#2上去附着。
后续，Tx UE可以将数据包通过无线承载#1发送至gNB#1，进而由gNB#1通过隧道#4发送至gNB#2-N，然后由gNB#2-N通过无线承载#4发送给Rx UE。另外，对于gNB#2中缓存的已从gNB#1处接收到但还未发送至Rx UE的来自于Tx UE的数据包，gNB#2可以通过建立的隧道#3发送给gNB#2-N，进而由gNB#2-N通过无线承载#4发送给Rx UE。可选的，Rx UE在成功由gNB#2切换至gNB#2-N之后，gNB#2也可以删除Rx UE的相关信息，例如用于建立无线承载#2的参数等。
此外，Rx UE在移动过程中还可以出现由gNB#2的服务范围内移动至gNB#1的服务范围内的情况，这种情况下，gNB#2可以指示gNB#1建立与Rx UE之间的无线承载，具体流程可以参照上述图10所示的建立无线承载#4的过程，本申请不再一一赘述。
切换场景三：
参照图11所示，假设第一终端设备为UE#1，第二终端设备为UE#2，为第一终端设备提供服务的第一RAN设备为gNB#1，为第二终端设备提供服务的第二RAN设备为gNB#2，第一终端设备和第二终端设备之间进行双向通信。已建立好用于传输的UE#1与UE#2之间的数据包的通信链路包括UE#1与gNB#1之间的无线承载#1、gNB#1与gNB#2之间的隧道#1A、gNB#1与gNB#2之间的隧道#1B，UE#1与gNB#2之间的无线承载#2。其中，隧道#1A为上行隧道、隧道#1B为下行隧道。这里假设UE#1向UE#2发送数据包为上行方向，UE#2向UE#1发送数据包为下行方向。
初始状态下，在上行方向上，UE#1发送的数据包通过无线承载#1发送给gNB#1，进而由gNB#1通过隧道#1A发送给gNB#2，然后由gNB#2通过无线承载#2将数据包发送给UE#2。在下行方向上，UE#2发送的数据包通过无线承载#1发送给gNB#1，进而由gNB#1通过隧道#1B发送给gNB#2，然后由gNB#2通过无线承载#2将数据包发送给UE#1。
参照图12所示，以UE#1由gNB#1的服务范围内移动至gNB#1-N的服务范围内为例，对更新用于传输数据包的通信链路的流程进行示例性说明。应理解，图12所示的更新通信链路的过程同样适用在UE#2由gNB#2的服务范围内移动至gNB#2-N的服务范围内的场景下。
步骤1201：UE#1由gNB#1的服务范围内向gNB#1-N的服务范围内移动过程中，向gNB#1发送第三测量报告(measurement report#3)。
其中，第三测量报告中携带有切换指示，所述切换指示中包括业务标识，切换指示用于指示gNB#1为UE#1执行的业务标识对应的业务进行RAN设备之间的切换。有关第三 测量报告的其它解释说明可参见步骤801中对第一测量报告的介绍，这里不再赘述。
步骤1202：gNB#1基于接收的第三测量报告确定UE#1执行业务标识对应的业务时需要由gNB#1切换至gNB#1-N，进而向gNB#1-N发送第三切换请求(handover request#3)。
其中，第三切换请求中包括UE#1的终端标识、业务标识、以及与业务标识对应的业务的服务质量需求。这里以业务标识为目的地址#1为例。第一切换请求中包括的目的地址#1、以及服务质量需求用于指示gNB#1-N建立与UE#1之间的无线承载#5。
另外，考虑到UE#1切换到gNB#1-N时，后续在上行方向上，UE#1发送的数据包需要经由gNB#1-N、gNB#2才能被UE#2接收，故gNB#1也可以在第三切换请求中携带gNB#2配置的目的地址#1对应的端点标识#1B、以及gNB#2的通信地址等，端点标识#1B、以及gNB#2的通信地址用于指示gNB#1-N建立与gNB#2之间的隧道#5A。这里，隧道#5A为上行隧道。
步骤1203：gNB#1-N解析第三切换请求中携带的内容，根据解析出的目的地址#1、以及服务质量需求等为UE#1配置用于建立无线承载#5的参数，并针对目的地址#1进行隧道接口配置，进而向gNB#1发送第三切换响应(handover request ack#3)。
其中，gNB#1-N在针对目的地址#1进行隧道接口配置时，可以配置目的地址#1对应的第四端点标识，即端点标识#1D作为隧道接口。
所述第三切换响应中包括第三切换命令(handover command#3)，第三切换命令中包括UE#1的终端标识、用于建立无线承载#5的参数、安全算法等。所述第三切换响应中还包括gNB#1-N配置的端点标识#1D、以及gNB#1-N的通信地址。其中，gNB#1-N的通信地址可以为L2协议层地址，如MAC地址等。
步骤1204：gNB#1-N根据第三切换请求中携带的端点标识#1B、以及gNB#2的通信地址，完成gNB#1-N与gNB#2之间在上行方向上的隧道#5A的配置。
步骤1205：gNB#1向gNB#2发送第二承载更新请求(bearer update request#2)，第二承载更新请求中携带有端点标识#1D、以及gNB#1-N的通信地址。承载更新请求用于指示gNB#2建立与gNB#1-N之间的隧道#5B。这里，隧道#5B为下行隧道。
步骤1206：gNB#2根据从第二承载更新请求中解析出的端点标识#1D、以及gNB#1-N的通信地址，完成gNB#2与gNB#1-N之间在下行方向上的隧道#5B的配置。
其中，隧道#5B可以用于传输gNB#2向gNB#1-N发送的来自于UE#2的数据包。
步骤1207：gNB#2向gNB#1发送第二承载更新响应(bearer update request ack#2)，指示gNB#1已经完成隧道#5B的配置。
其中，需要理解的是，步骤1207也可以为可选步骤。
步骤1208：gNB#1将从第三切换响应中解析出的第三切换命令通过RRC信令发送给UE#1。
步骤1209：UE#1接收到第三切换命令后基于第二切换命令中携带的内容完成无线承载#5的配置，并从gNB#1上去附着。
后续，在上行方向上，UE#1可以将数据包通过无线承载#5发送至gNB#1，进而由gNB#1通过隧道#5A发送至gNB#1-N，然后由gNB#1-N通过无线承载#2发送给UE#2。在下行方向上，UE#2可以将数据包通过无线承载#2发送至gNB#2，进而由gNB#2通过隧道#5B发送至gNB#1-N，然后由gNB#1-N通过无线承载#5发送给UE#1。另外，对于gNB#1中缓存的已从UE#1处接收到但还未发送至gNB#2的数据包，gNB#1仍可以通过原先建立 的隧道#1A发送给gNB#2，在缓存的数据包发送完成后，再使得隧道#1A失效。可选的，UE#1在成功由gNB#1切换至gNB#1-N之后，gNB#1也可以删除UE#1的相关信息，例如用于建立无线承载#1的参数等。
本申请实施例提供的上述切换场景一至三中，更新用于传输数据包的通信链路的过程，RAN设备可以直接在终端设备的触发下，进行RAN设备之间的切换以及通信链路的更新，核心网设备不参与切换过程，可以降低切换过程的时延，从而使终端设备尽可能的对切换过程无感知，达到无缝切换的目的。
需要理解的是，本申请实施例中，RAN设备是针对接收的切换指示中业务标识所对应的业务而发起更新用于传输数据包的通信链路的过程。本申请中业务标识对应的业务主要包括低时延需求、高可靠性需求的业务等。对于除业务标识对应的业务之外的其它业务，可以仍按照现有方案进行RAN之间的切换以及通信链路的更新。
基于相同的技术构思，本申请实施例还提供了一种通信装置，用于实现上述方法实施例中第一RAN设备所执行的功能。
图13示出了本申请实施例提供的该通信装置的结构示意图一，通信装置1300可以包括接收单元1301、处理单元1302。具体的，接收单元1301可以用于接收第一终端设备发送的业务标识、以及所述业务标识对应的业务的服务质量需求。处理单元1302可以用于基于所述业务标识和所述服务质量需求，建立与所述第一终端设备之间的第一承载，以及，基于所述业务标识和所述服务质量需求建立与第二无线接入网RAN设备之间的第二承载。其中，所述第一承载和所述第二承载用于传输所述第一终端设备与所述第二终端设备之间执行的所述业务标识对应的业务的数据包，所述第二RAN设备是指为所述第二终端设备提供服务的RAN设备。所述业务标识可以包括目的地址，所述目的地址被用于至少一个终端设备参与所述业务标识对应的业务。所述服务质量需求包括用于表征业务的时延需求的第一指标、用于表征业务的可靠性需求的第二指标。
本申请的一示例中，接收单元1301还可以用于接收来自于核心网设备的所述第一终端设备的授权信息，所述授权信息中包括所述第一终端设备已被授权的业务的授权业务标识、以及所述第一终端设备执行所述已被授权的业务时的服务质量需求。
相应地，处理单元1302在建立与所述第一终端设备之间的第一承载时，具体可以用于在所述授权业务标识中包括所述业务标识、且所述业务标识对应的服务质量需求与来自于所述第一终端设备的所述服务质量需求相匹配的情况下，建立与所述第一终端设备之间的所述第一承载。
本申请的又一示例中，处理单元1302在建立与第二RAN设备之间的第二承载时，具体可以用于配置所述目的地址对应的第一端点标识，以及确定所述第二RAN设备记录有所述目的地址后获取所述第二RAN设备配置的所述目的地址对应的第二端点标识，可选的，建立与所述第二RAN设备之间的所述第二承载，并利用所述第一端点标识和所述第二端点标识来标识所述第二承载。
在通信装置1300完成与第一终端设备之间的第一承载、以及与第二RAN设备之间的第二承载的建立过程后，第一终端设备与第二终端设备之间传输的数据包可以通过通信装置1300进行转发。后续，随着第一终端设备的移动，可能会进行RAN设备之间的切换，在不同的切换场景下，通信装置1300所执行的具体功能也有所区别。
当所述第一终端设备和所述第二终端设备之间单向传输所述数据包，且所述第一终端 设备为发送所述数据包的发送端、所述第二终端设备为接收所述数据包的接收端时，所述接收单元1301还用于接收来自于所述第一终端设备的测量报告，其中，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述通信装置1300为所述第一终端设备执行的所述业务标识对应的业务进行RAN设备之间的切换。所述处理单元1302还用于：基于所述测量报告中携带的所述业务标识确定所述第一终端设备执行所述业务标识对应的业务时需要由所述通信装置1300切换至第三RAN设备。所述通信装置1300还可以包括发送单元1303，发送单元1303用于向所述第三RAN设备发送第一切换请求。其中，所述第一切换请求中包括所述业务标识和所述服务质量需求，所述业务标识和所述服务质量需求用于指示所述第三RAN设备建立与所述第一终端设备之间的第三承载，所述第三承载用于传输所述第一终端设备向所述第三RAN设备发送的所述数据包。
一种实现方式中，所述第一切换请求中还可以包括所述第二RAN设备的第二端点标识、以及所述第二RAN设备的第一通信地址，所述第一通信地址为所述通信装置1300在建立所述第二承载时获取的。其中，所述第二端点标识和所述第一通信地址可以用于指示所述第三RAN设备建立与所述第二RAN设备之间的第四承载，所述第四承载用于传输所述第三RAN设备向所述第二RAN设备发送的来自于所述第一终端设备的所述数据包。
当所述第一终端设备和所述第二终端设备之间单向传输所述数据包，且所述第一终端设备为接收所述数据包的接收端、所述第二终端设备为发送所述数据包的发送端时，所述接收单元1301还可以用于接收所述第一终端设备发送的测量报告，其中，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述通信装置1300为所述第一终端设备执行的所述业务标识对应的业务进行RAN设备之间的切换。所述处理单元1302还可以用于基于所述测量报告中携带的所述业务标识确定所述第一终端设备执行所述业务标识对应的业务时需要由所述通信装置1300切换至第四RAN设备。所述发送单元1303还用于向所述第四RAN设备发送第二切换请求。其中，所述第二切换请求中包括所述业务标识和所述服务质量需求，所述业务标识和所述服务质量需求用于指示所述第四RAN设备建立与所述第一终端设备之间的第五承载，所述第五承载用于传输所述第四RAN设备向所述第一终端设备发送的来自于所述第二终端设备的所述数据包。
一种实现方式中，所述接收单元1301还可以用于接收来自于所述第四RAN设备的所述第四RAN设备的第二通信地址、以及所述第四RAN设备配置的所述目的地址对应的第三端点标识。可选的，所述发送单元1303还用于向所述第二RAN设备发送所述第二通信地址、以及所述第三端点标识。其中，所述第二通信地址以及所述第三端点标识用于指示所述第二RAN设备建立与所述第四RAN设备之间的第六承载，所述第六承载用于传输所述第二RAN设备向所述第四RAN设备发送的来自于所述第二终端设备的所述数据包。
又一种实现方式中，所述处理单元1302还可以用于基于接收的所述第二通信地址以及所述第三端点标识，建立与所述第四RAN设备之间的第七承载，其中，所述第七承载用于传输所述通信装置1300向所述第四RAN设备发送的已从所述第二终端设备接收到但还未发送的所述数据包。
当所述第一终端设备与所述第二终端设备之间双向传输所述数据包时，所述接收单元1301还用于接收来自于所述第一终端设备的测量报告，其中，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述通信装置1300为所述 终端设备执行的所述业务标识对应的业务进行RAN设备之间的切换。
所述处理单元1302还用于在基于所述测量报告中携带的所述业务标识确定所述第一终端设备执行所述业务标识对应的业务时需要由所述通信装置1300切换至第五RAN设备后，向所述第五RAN设备发送第三切换请求。其中，所述第三切换请求中包括所述业务标识和所述服务质量需求，所述业务标识和所述服务质量需求用于指示所述第五RAN设备建立与所述第一终端设备之间的第八承载，所述第八承载用于传输所述第一终端设备向所述第五RAN设备发送的所述数据包、以及所述第五RAN设备向所述第一终端设备发送的来自所述第二终端设备的所述数据包。
一种实现方式中，所述第三切换指令中还包括所述第二RAN设备的第二端点标识、以及所述第二RAN设备的第一通信地址，所述第一通信地址为所述通信装置1300在建立所述第二承载的时获取的。所述第二端点标识以及所述第一通信地址用于指示所述第五RAN设备建立与所述第二RAN设备之间的第九承载，所述第九承载用于传输所述第五RAN设备向所述第二RAN设备发送的来自所述第一终端设备的所述数据包。
又一种实现方式中，所述接收单元1301还可以用于接收所述第五RAN设备发送的所述第五RAN设备的第三通信地址、以及所述第五RAN设备配置的所述目的地址对应的第四端点标识。可选的，所述发送单元1303还可以用于向所述第二RAN设备发送所述第三通信地址、以及所述第四端点标识，其中，所述第三通信地址以及所述第四端点标识用于指示所述第二RAN设备建立与所述第五RAN设备之间的第十承载，所述第十承载用于传输所述第二RAN设备向所述第五RAN设备发送的来自所述第二终端设备的所述数据包。
图14示出了本申请实施例提供的该通信装置的结构示意图二，通信装置1400可以包括处理器1401和收发器1402。其中，处理器1401可以是中央处理器(central processing unit，CPU)或网络处理器(network processor，NP)。处理器1401还可以是其他类型芯片，例如基带电路，射频电路，专用集成电路(application specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其任意组合。收发器1402可以包括天线。可选的，通信装置1400中还可以包括存储器1403，用于存储处理器1401所执行的程序以及所需处理的数据。所述存储器1403可以集成在所述处理器1401中，也可以与所述处理器1401分离设置。
所述处理器1401，用于用所述收发器1402接收第一终端设备发送的业务标识、以及所述业务标识对应的业务的服务质量需求；基于所述业务标识和所述服务质量需求，建立与所述第一终端设备之间的第一承载，以及，基于所述业务标识和所述服务质量需求建立与第二无线接入网RAN设备之间的第二承载。其中，所述第一承载和所述第二承载用于传输所述第一终端设备与所述第二终端设备之间执行的所述业务标识对应的业务的数据包，所述第二RAN设备是指为所述第二终端设备提供服务的RAN设备。
其中，上述处理器1401可以对应于通信装置1300中所述的处理单元1302，上述收发器1402可以对应于通信装置1300中所述的接收单元1301以及发送单元1303。关于上述处理器1401和收发器1402的具体交互过程，可参见上述接收单元1301、处理单元1302、以及发送单元1303之间的交互过程，在此不再赘述。
基于相同的技术构思，本申请实施例还提供了另一种通信装置，用于实现上述方法实施例中第一终端设备所执行的功能。
图15示出了本申请实施例提供的该通信装置的结构示意图一，通信装置1500可以包括发送单元1501、处理单元1502。具体的，发送单元1501可以用于向第一RAN设备发送业务标识、以及所述业务标识对应的业务的服务质量需求。处理单元1502可以用于在所述第一RAN设备的指示下建立与所述第一RAN设备之间的第一承载，所述第一承载用于传输所述通信装置1500执行所述业务标识对应的业务时与所述第一RAN设备之间传输的数据包。其中，所述业务标识至少包括目的地址，所述目的地址被用于至少一个通信装置参与所述业务标识对应的业务。所述服务质量需求包括用于表征业务的时延需求的第一指标、用于表征业务的可靠性需求的第二指标。
本申请的一示例中，所述业务标识和所述服务质量需求携带在所述通信装置1500通过所述发送单元1501向所述第一RAN设备发送的控制指示中，所述控制指示用于指示所述第一RAN设备为所述业务标识对应的业务建立与所述通信装置之间的所述第一承载。
本申请的另一示例中，所述发送单元1501还可以用于向所述第一RAN设备发送测量报告，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述第一RAN设备为所述通信装置1500执行的所述业务标识对应的业务进行RAN设备之间的切换。
此外，通信装置1500还可以包括接收单元1503。具体的，接收单元1503可以接收第一RAN设备发送的用于建立第一承载的相关配置参数、以及用于进行RAN之间的切换的相关信息等。
图16示出了本申请实施例提供的该通信装置的结构示意图二，通信装置1600可以包括处理器1601和收发器1602。其中，处理器1601可以是中央处理器(central processing unit，CPU)或网络处理器(network processor，NP)。处理器1601还可以是其他类型芯片，例如基带电路，射频电路，专用集成电路(application specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其任意组合。收发器1602可以包括天线。可选的，通信装置1600中还可以包括存储器1603，用于存储处理器1601所执行的程序以及所需处理的数据。所述存储器1603可以集成在所述处理器1601中，也可以与所述处理器1601分离设置。
所述处理器1601，用于用所述收发器1602向第一RAN设备发送业务标识、以及所述业务标识对应的业务的服务质量需求，在所述第一RAN设备的指示下建立与所述第一RAN设备之间的第一承载，所述第一承载用于传输所述通信装置1600执行所述业务标识对应的业务时与所述第一RAN设备之间传输的数据包。
其中，上述处理器1601可以对应于通信装置1500中所述的处理单元1502，上述收发器1602可以对应于通信装置1500中所述的发送单元1501、以及接收单元1503。具体的，处理器1601和收发器1602的具体交互过程，可参见上述发送单元1501、处理单元1502、以及接收单元1503之间的交互过程，在此不再赘述。
基于相同的技术构思，本申请还提供一种芯片，所述芯片可以与存储器相通信，或者所述芯片中包括存储器，所述芯片执行所述存储器中存储的程序指令，以实现上述方法实施例中所涉及的所述第一RAN设备或者所述第一终端设备的相应功能。
基于相同的技术构思，本申请还提供一种计算机存储介质，所述计算机存储介质存储有计算机可读指令，当所述计算机可读指令被执行时，使得实现上述方法实施例中所涉及的所述第一RAN设备或者所述第一终端设备的相应功能。
基于相同的技术构思，本申请还提供一种包含软件程序的计算机程序产品，当其在计算机上运行时，使得实现上述方法实施例中所涉及的所述第一RAN设备或者所述第一终端设备的相应功能。
此外，本申请还提供一种通信系统，在该通信系统中可以包括上述方法实施例中所涉及的所述第一RAN设备，和/或，所述第二RAN设备，和/或，终端设备。其中，终端设备可以包括上述方法实施例中涉及的所述第一终端设备和所述第二终端设备。比如，该通信系统可以为由第一RAN设备、第二RAN设备、以及其它能够与第一RAN设备或第二RAN设备进行交互的网络设备构成的通信系统。再比如，该通信系统也可以为由终端设备、第一RAN设备、第二RAN设备、以及其它能够与第一RAN设备或第二RAN设备进行交互的网络设备构成的通信系统。再比如，该通信系统还可以为由终端设备、第一RAN设备构成的通信系统等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。可选的，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种通信方法，其特征在于，包括：
    第一无线接入网RAN设备接收第一终端设备发送的业务标识、以及所述业务标识对应的业务的服务质量需求；
    所述第一RAN设备基于所述业务标识和所述服务质量需求，建立与所述第一终端设备之间的第一承载；以及，
    所述第一RAN设备基于所述业务标识和所述服务质量需求建立与第二RAN设备之间的第二承载；
    其中，所述第一承载和所述第二承载用于传输所述第一终端设备与所述第二终端设备之间执行的与所述业务标识对应的业务的数据包，所述第二RAN设备是指为所述第二终端设备提供服务的RAN设备。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一RAN设备接收来自于核心网设备的所述第一终端设备的授权信息，所述授权信息中包括所述第一终端设备已被授权的业务的授权业务标识、以及所述第一终端设备执行所述已被授权的业务时的服务质量需求；
    所述第一RAN设备基于所述业务标识和所述服务质量需求，建立与所述第一终端设备之间的第一承载，包括：
    在所述授权业务标识中包括所述业务标识、且所述业务标识对应的服务质量需求与来自于所述第一终端设备的所述服务质量需求相匹配的情况下，所述第一RAN设备建立与所述第一终端设备之间的所述第一承载。
  3. 如权利要求1或2所述的方法，其特征在于，所述业务标识包括目的地址，所述目的地址被用于至少一个终端设备参与所述业务标识对应的业务；
    所述第一RAN设备基于所述业务标识和所述服务质量需求建立与第二RAN设备之间的第二承载，包括：
    所述第一RAN设备配置所述目的地址对应的第一端点标识；以及，所述第一RAN设备确定所述第二RAN设备记录有所述目的地址后，获取所述第二RAN设备配置的所述目的地址对应的第二端点标识；
    所述第一RAN设备建立与所述第二RAN设备之间的所述第二承载，并利用所述第一端点标识和所述第二端点标识来标识所述第二承载。
  4. 如权利要求3所述的方法，其特征在于，当所述第一终端设备和所述第二终端设备之间单向传输所述数据包，且所述第一终端设备为发送所述数据包的发送端、所述第二终端设备为接收所述数据包的接收端时，所述方法还包括：
    所述第一RAN设备接收来自于所述第一终端设备的测量报告，其中，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述第一RAN设备为所述终端设备执行的与所述业务标识对应的业务进行RAN设备之间的切换；
    所述第一RAN设备基于所述测量报告中携带的所述业务标识确定所述第一终端设备执行与所述业务标识对应的业务时需要由所述第一RAN设备切换至第三RAN设备；
    所述第一RAN设备向所述第三RAN设备发送第一切换请求；
    其中，所述第一切换请求中包括所述业务标识和所述服务质量需求，所述业务标识和 所述服务质量需求用于指示所述第三RAN设备建立与所述第一终端设备之间的第三承载，所述第三承载用于传输所述第一终端设备向所述第三RAN设备发送的所述数据包。
  5. 如权利要求4所述的方法，其特征在于，所述第一切换请求中还包括所述第二RAN设备的第二端点标识、以及所述第二RAN设备的第一通信地址，所述第一通信地址为所述第一RAN设备在建立所述第二承载时获取的；
    所述第二端点标识和所述第一通信地址用于指示所述第三RAN设备建立与所述第二RAN设备之间的第四承载，所述第四承载用于传输所述第三RAN设备向所述第二RAN设备发送的来自于所述第一终端设备的所述数据包。
  6. 如权利要求3所述的方法，其特征在于，当所述第一终端设备和所述第二终端设备之间单向传输所述数据包，且所述第一终端设备为接收所述数据包的接收端、所述第二终端设备为发送所述数据包的发送端时，所述方法还包括：
    所述第一RAN设备接收所述第一终端设备发送的测量报告，其中，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述第一RAN设备为所述终端设备执行的与所述业务标识对应的业务进行RAN设备之间的切换；
    所述第一RAN设备基于所述测量报告中携带的所述业务标识，确定所述第一终端设备执行与所述业务标识对应的业务时，需要由所述第一RAN设备切换至第四RAN设备；
    所述第一RAN设备向所述第四RAN设备发送第二切换请求；
    其中，所述第二切换请求中包括所述业务标识和所述服务质量需求，所述业务标识和所述服务质量需求用于指示所述第四RAN设备建立与所述第一终端设备之间的第五承载，所述第五承载用于传输所述第四RAN设备向所述第一终端设备发送的来自于所述第二终端设备的所述数据包。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一RAN设备接收来自于所述第四RAN设备的所述第四RAN设备的第二通信地址、以及所述第四RAN设备配置的所述目的地址对应的第三端点标识；
    所述第一RAN设备向所述第二RAN设备发送所述第二通信地址、以及所述第三端点标识；
    其中，所述第二通信地址以及所述第三端点标识用于指示所述第二RAN设备建立与所述第四RAN设备之间的第六承载，所述第六承载用于传输所述第二RAN设备向所述第四RAN设备发送的来自于所述第二终端设备的所述数据包。
  8. 如权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述第一RAN设备基于接收的所述第二通信地址以及所述第三端点标识，建立与所述第四RAN设备之间的第七承载；
    所述第七承载用于传输所述第一RAN设备向所述第四RAN设备发送的已从所述第二终端设备接收到但还未发送的所述数据包。
  9. 如权利要求1至8任一所述的方法，其特征在于，所述服务质量需求包括用于表征业务的时延需求的第一指标、用于表征业务的可靠性需求的第二指标。
  10. 一种通信方法，其特征在于，包括：
    终端设备向第一无线接入网RAN设备发送业务标识、以及与所述业务标识对应的业务的服务质量需求；
    所述终端设备在所述第一RAN设备的指示下建立与所述第一RAN设备之间的第一承 载，所述第一承载用于传输所述终端设备执行与所述业务标识对应的业务时与所述第一RAN设备之间传输的数据包。
  11. 如权利要求10所述的方法，其特征在于，所述业务标识和所述服务质量需求携带在所述终端设备向所述第一RAN设备发送的控制指示中，所述控制指示用于指示所述第一RAN设备为与所述业务标识对应的业务建立与所述终端设备之间的所述第一承载。
  12. 如权利要求10或11所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述第一RAN设备发送测量报告，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述第一RAN设备为所述终端设备执行的与所述业务标识对应的业务进行RAN设备之间的切换。
  13. 如权利要求10至12任一所述的方法，其特征在于，所述业务标识至少包括目的地址，所述目的地址被用于至少一个终端设备参与所述业务标识对应的业务；
    所述服务质量需求包括用于表征业务的时延需求的第一指标、用于表征业务的可靠性需求的第二指标。
  14. 一种通信装置，其特征在于，包括：
    接收单元，用于接收第一终端设备发送的业务标识、以及与所述业务标识对应的业务的服务质量需求；
    处理单元，用于基于所述业务标识和所述服务质量需求，建立与所述第一终端设备之间的第一承载；以及，基于所述业务标识和所述服务质量需求建立与第二无线接入网RAN设备之间的第二承载；
    其中，所述第一承载和所述第二承载用于传输所述第一终端设备与所述第二终端设备之间执行的与所述业务标识对应的业务的数据包，所述第二RAN设备是指为所述第二终端设备提供服务的RAN设备。
  15. 如权利要求14所述的装置，其特征在于，所述接收单元还用于：
    接收来自于核心网设备的所述第一终端设备的授权信息，所述授权信息中包括所述第一终端设备已被授权的业务的授权业务标识、以及所述第一终端设备执行所述已被授权的业务时的服务质量需求；
    所述处理单元具体用于：
    在所述授权业务标识中包括所述业务标识、且所述业务标识对应的服务质量需求与来自于所述第一终端设备的所述服务质量需求相匹配的情况下，建立与所述第一终端设备之间的所述第一承载。
  16. 如权利要求14或15所述的装置，其特征在于，所述业务标识包括目的地址，所述目的地址被用于至少一个终端设备参与所述业务标识对应的业务；
    所述处理单元具体用于：
    配置所述目的地址对应的第一端点标识；以及，确定所述第二RAN设备记录有所述目的地址后，获取所述第二RAN设备配置的所述目的地址对应的第二端点标识；
    建立与所述第二RAN设备之间的所述第二承载，并利用所述第一端点标识和所述第二端点标识来标识所述第二承载。
  17. 如权利要求16所述的装置，其特征在于，当所述第一终端设备和所述第二终端设备之间单向传输所述数据包，且所述第一终端设备为发送所述数据包的发送端、所述第二终端设备为接收所述数据包的接收端时，所述接收单元还用于：
    接收来自于所述第一终端设备的测量报告，其中，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述通信装置为所述第一终端设备执行的与所述业务标识对应的业务进行RAN设备之间的切换；
    所述处理单元还用于：
    基于所述测量报告中携带的所述业务标识，确定所述第一终端设备执行与所述业务标识对应的业务时，需要由所述通信装置切换至第三RAN设备；
    所述装置还包括：
    发送单元，用于向所述第三RAN设备发送第一切换请求；
    其中，所述第一切换请求中包括所述业务标识和所述服务质量需求，所述业务标识和所述服务质量需求用于指示所述第三RAN设备建立与所述第一终端设备之间的第三承载，所述第三承载用于传输所述第一终端设备向所述第三RAN设备发送的所述数据包。
  18. 如权利要求17所述的装置，其特征在于，所述第一切换请求中还包括所述第二RAN设备的第二端点标识、以及所述第二RAN设备的第一通信地址，所述第一通信地址为所述通信装置在建立所述第二承载时获取的；
    所述第二端点标识和所述第一通信地址用于指示所述第三RAN设备建立与所述第二RAN设备之间的第四承载，所述第四承载用于传输所述第三RAN设备向所述第二RAN设备发送的来自于所述第一终端设备的所述数据包。
  19. 如权利要求16所述的装置，其特征在于，当所述第一终端设备和所述第二终端设备之间单向传输所述数据包，且所述第一终端设备为接收所述数据包的接收端、所述第二终端设备为发送所述数据包的发送端时，所述接收单元还用于：
    接收所述第一终端设备发送的测量报告，其中，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述通信装置为所述第一终端设备执行的与所述业务标识对应的业务进行RAN设备之间的切换；
    所述处理单元还用于：
    基于所述测量报告中携带的所述业务标识确定所述第一终端设备执行与所述业务标识对应的业务时需要由所述通信装置切换至第四RAN设备；
    所述发送单元还用于：向所述第四RAN设备发送第二切换请求；
    其中，所述第二切换请求中包括所述业务标识和所述服务质量需求，所述业务标识和所述服务质量需求用于指示所述第四RAN设备建立与所述第一终端设备之间的第五承载，所述第五承载用于传输所述第四RAN设备向所述第一终端设备发送的来自于所述第二终端设备的所述数据包。
  20. 如权利要求19所述的装置，其特征在于，所述接收单元还用于：
    接收来自于所述第四RAN设备的所述第四RAN设备的第二通信地址、以及所述第四RAN设备配置的所述目的地址对应的第三端点标识；
    所述发送单元还用于：向所述第二RAN设备发送所述第二通信地址、以及所述第三端点标识；
    其中，所述第二通信地址以及所述第三端点标识用于指示所述第二RAN设备建立与所述第四RAN设备之间的第六承载，所述第六承载用于传输所述第二RAN设备向所述第四RAN设备发送的来自于所述第二终端设备的所述数据包。
  21. 如权利要求16或19所述的装置，其特征在于，所述处理单元还用于：
    基于接收的所述第二通信地址以及所述第三端点标识，建立与所述第四RAN设备之间的第七承载；
    所述第七承载用于传输所述通信装置向所述第四RAN设备发送的已从所述第二终端设备接收到但还未发送的所述数据包。
  22. 如权利要求14至21任一所述的装置，其特征在于，所述服务质量需求包括用于表征业务的时延需求的第一指标、用于表征业务的可靠性需求的第二指标。
  23. 一种通信装置，其特征在于，包括：
    发送单元，用于向第一无线接入网RAN设备发送业务标识、以及与所述业务标识对应的业务的服务质量需求；
    处理单元，用于在所述第一RAN设备的指示下建立与所述第一RAN设备之间的第一承载，所述第一承载用于传输所述通信装置执行与所述业务标识对应的业务时与所述第一RAN设备之间传输的数据包。
  24. 如权利要求23所述的装置，其特征在于，所述业务标识和所述服务质量需求携带在所述通信装置通过所述发送单元向所述第一RAN设备发送的控制指示中，所述控制指示用于指示所述第一RAN设备为与所述业务标识对应的业务建立与所述通信装置之间的所述第一承载。
  25. 如权利要求23或24所述的装置，其特征在于，所述发送单元还用于：
    向所述第一RAN设备发送测量报告，所述测量报告中携带切换指示，所述切换指示包括所述业务标识，所述切换指示用于指示所述第一RAN设备为所述通信装置执行的与所述业务标识对应的业务进行RAN设备之间的切换。
  26. 如权利要求23至25任一所述的装置，其特征在于，所述业务标识至少包括目的地址，所述目的地址被用于至少一个通信装置参与所述业务标识对应的业务；
    所述服务质量需求包括用于表征业务的时延需求的第一指标、用于表征业务的可靠性需求的第二指标。
  27. 一种通信装置，其特征在于，包括：处理器和存储器；
    所述存储器用于存储计算机执行指令；
    所述处理器用于执行所述存储器所存储的计算机执行指令，以使所述通信装置实现如所述权利要求1至9任一项所述的方法中所述第一无线接入网RAN设备或所述第二RAN设备的功能，或者，如所述权利要求10至13任一项所述的方法中所述终端设备的功能。
  28. 一种通信系统，其特征在于，包括：如权利要求1至9任一项所述的方法中的所述第一无线接入网RAN设备，和/或，如权利要求1至9任一项所述的方法中的所述第二RAN设备，和/或，如权利要求10至13任一项所述的方法中的所述终端设备。
  29. 一种计算机存储介质，其特征在于，包括计算机可读指令，当所述计算机可读指令被执行时，实现如权利要求1至9任一项所述的方法中的所述第一RAN设备或第二RAN设备的功能，或者，实现如权利要求10至13任一项所述的方法中的所述终端设备的功能。
PCT/CN2019/081948 2018-05-11 2019-04-09 一种通信方法及装置 WO2019214384A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810450360.XA CN110475384B (zh) 2018-05-11 2018-05-11 一种通信方法及装置
CN201810450360.X 2018-05-11

Publications (1)

Publication Number Publication Date
WO2019214384A1 true WO2019214384A1 (zh) 2019-11-14

Family

ID=68467265

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/081948 WO2019214384A1 (zh) 2018-05-11 2019-04-09 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN110475384B (zh)
WO (1) WO2019214384A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113381920B (zh) * 2020-03-09 2022-11-22 中国移动通信有限公司研究院 一种数据传输方法、节点和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101193117A (zh) * 2006-11-28 2008-06-04 华为技术有限公司 终端之间互通的方法、接入网及无线网络
CN101800938A (zh) * 2009-02-05 2010-08-11 华为技术有限公司 为mbms承载业务建立无线承载的方法、装置和系统
WO2016159841A1 (en) * 2015-03-31 2016-10-06 Telefonaktiebolaget Lm Ericsson (Publ) Service continuity
CN106304271A (zh) * 2015-06-10 2017-01-04 电信科学技术研究院 一种多无线接入网络下提供业务与接受业务的方法及设备
CN107548127A (zh) * 2016-06-23 2018-01-05 北京三星通信技术研究有限公司 支持数据传输的方法和设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102421145B (zh) * 2011-11-24 2015-02-04 中国联合网络通信集团有限公司 基站间数据直通方法及系统
CN103731513A (zh) * 2012-10-15 2014-04-16 中国联合网络通信集团有限公司 基站转发方法、基站和基站转发系统
US20190132717A1 (en) * 2016-05-09 2019-05-02 Nokia Solutions And Networks Oy Enhancing Communication Services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101193117A (zh) * 2006-11-28 2008-06-04 华为技术有限公司 终端之间互通的方法、接入网及无线网络
CN101800938A (zh) * 2009-02-05 2010-08-11 华为技术有限公司 为mbms承载业务建立无线承载的方法、装置和系统
WO2016159841A1 (en) * 2015-03-31 2016-10-06 Telefonaktiebolaget Lm Ericsson (Publ) Service continuity
CN106304271A (zh) * 2015-06-10 2017-01-04 电信科学技术研究院 一种多无线接入网络下提供业务与接受业务的方法及设备
CN107548127A (zh) * 2016-06-23 2018-01-05 北京三星通信技术研究有限公司 支持数据传输的方法和设备

Also Published As

Publication number Publication date
CN110475384B (zh) 2021-12-03
CN110475384A (zh) 2019-11-19

Similar Documents

Publication Publication Date Title
US11477703B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US11553365B2 (en) Method for reporting measurement result by user equipment transceiving data by first radio access technology and second radio access technology, and device therefor
TWI804992B (zh) 層2使用者設備透過網路中繼進行信令傳輸的方法
US9532395B2 (en) System and method for device to device (D2D) communication
CN109428818B (zh) 处理分组路由的装置及方法
WO2013075635A1 (zh) 连接建立方法和用户设备
WO2013075602A1 (zh) 实现载波聚合的方法、基站和用户设备
CN108282833B (zh) 处理系统间移动中的分组数据流的装置及方法
WO2011100894A1 (zh) 切换方法和中继节点
WO2015062287A1 (zh) 终端的本地交换方法及系统
US20150163837A1 (en) Method, apparatus, and system for establishing radio bearer
US10499445B2 (en) Method and apparatus for providing next generation network service in heterogeneous network environment
WO2019214384A1 (zh) 一种通信方法及装置
CN110495244B (zh) 控制用户设备的网络接入
US10455472B2 (en) Device and method of handling data transmissions in a wireless communication system
US20220377541A1 (en) Key Management Method and Communication Apparatus
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2022236644A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2014000611A1 (zh) 传输数据的方法和装置
WO2023286783A1 (ja) 通信制御方法
WO2024093719A1 (zh) 一种数据传输的方法和装置
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
US20240179611A1 (en) Method and device for wireless communication
WO2023286690A1 (ja) 通信制御方法
WO2023130362A1 (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: 19799643

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

Country of ref document: EP

Kind code of ref document: A1