WO2019084725A1 - 提升业务可靠性的方法、设备及系统 - Google Patents

提升业务可靠性的方法、设备及系统 Download PDF

Info

Publication number
WO2019084725A1
WO2019084725A1 PCT/CN2017/108396 CN2017108396W WO2019084725A1 WO 2019084725 A1 WO2019084725 A1 WO 2019084725A1 CN 2017108396 W CN2017108396 W CN 2017108396W WO 2019084725 A1 WO2019084725 A1 WO 2019084725A1
Authority
WO
WIPO (PCT)
Prior art keywords
function entity
transmission path
terminal
user plane
transmission
Prior art date
Application number
PCT/CN2017/108396
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 华为技术有限公司
Priority to KR1020207014662A priority Critical patent/KR102413507B1/ko
Priority to JP2020524129A priority patent/JP7175977B2/ja
Priority to CN202111056184.XA priority patent/CN113891496A/zh
Priority to BR112020008149-3A priority patent/BR112020008149A2/pt
Priority to PCT/CN2017/108396 priority patent/WO2019084725A1/zh
Priority to EP17930784.8A priority patent/EP3703466B1/en
Priority to CN201780096080.7A priority patent/CN111247869B/zh
Publication of WO2019084725A1 publication Critical patent/WO2019084725A1/zh
Priority to US16/862,001 priority patent/US11432297B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
    • H04W40/14—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality based on stability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1845—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast broadcast or multicast in a specific location, e.g. geocast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/806—Broadcast or multicast traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00692—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, device, and system for improving service reliability.
  • next generation mobile communication system next generation system
  • 5G fifth generation
  • the 5G network architecture defines an ultra-reliable low latency communication (URLLC) scenario, which mainly includes services such as driverless, industrial automation, etc. that require low latency and high reliability.
  • URLLC ultra-reliable low latency communication
  • the advanced air interface technology of 5G network and the optimized core network architecture make the requirements of the above scenarios possible.
  • the mobile network itself has some instability, whether it is the underlying link or the upper layer routing protocol, and the above scenarios are mostly life safety or production security related services, so there is no error. Therefore, we need to give an optimized network solution, so that the network can meet the above requirements as much as possible even if the link quality is not good.
  • the present application provides a network for improving service reliability, the network including a session function entity and a user plane function entity, the session function entity is used for decision making and initiating establishment of a terminal and At least two transmission paths between the user plane function entities, and instructing the terminal or the user plane function entity to transmit the same data on the at least two paths; the user plane function entity is used according to the Notifying the session function entity that the user plane resource is allocated to the at least two transmission paths, and transmitting the same data to the terminal on the at least two transmission paths, and at least two to the terminal are initiated by the network
  • the transmission path is very reliable for the reliability of data transmission for high reliability services.
  • the triggering network determines to establish multiple transmission paths, including:
  • the session function entity acquires service QoS information according to the service request sent by the terminal or the policy function entity, and determines, according to the QoS information, that the first and second transmission paths between the terminal and the user plane function entity need to be established; Or the session function entity requests authorization from the policy function entity according to the master/slave transmission path establishment indication or the dual-play indication carried in the service request sent by the terminal, and determines that the terminal and the user plane function entity need to be established according to the authorization result. First and second transmission paths between.
  • the session function entity instructs the terminal or the user plane function entity to transmit the same data on the first and second transmission paths, including: the session function entity to the terminal or the user plane function entity user plane
  • the functional entity sends an association identifier (or backup identifier, etc.) indicating that the terminal or user plane function entity transmits the same data on the first and second transmission paths.
  • the multiple transmission paths are established, and the notification terminal or the user plane function entity starts to use the established multiple transmission paths for data transmission, which may be completed sequentially or simultaneously.
  • the session function entity may notify the user plane function entity and/or the terminal to start transmission through the established first and second transmission paths when initiating the establishment of the first and second transmission paths.
  • the same data; or the session function entity may notify the user plane function entity and according to the network condition or service requirement after the first and second transmission paths are established.
  • the terminal starts transmitting the same data on the first and second transmission paths, and such a processing manner can enhance the flexibility of using multiple transmission paths.
  • the network may establish multiple transmission paths, one is established separately, and the access devices carrying the transmission paths may be unrelated, that is, the session function entity notifies the mobility management entity to indicate the first
  • the access device and the second access device negotiate with the terminal to establish the first and second transmission paths; or the session function entity initiates through an access device (ie, with the first access device as an anchor)
  • Establishing a plurality of transmission paths for example, the first and second transmission path establishment requests are sent by the session function entity to the mobility management entity, and the mobility management entity instructs the first access device to establish the location according to the indication of the session function entity Describe the first transmission path, and instruct the first access device to notify the second access device to establish the second transmission path.
  • the first access device may acquire resource information of the second access device, and then notify the terminal. And establishing, by the terminal, establishing a connection with the second access device to complete establishment of the second transmission path.
  • the terminal or the user plane function entity transmitting the same data on the first and second transmission paths, including: the user plane function entity or the terminal sending on the first and second transmission paths The same data; or the user plane function entity or terminal receives the same data from the first and second transmission paths and deduplicates the received data.
  • the terminal or the user plane function entity may also select one of the two established transmission paths for data reception according to data transmission quality and/or link quality, without performing a deduplication operation. Although the work of path quality detection is added, the burden of data deduplication can be alleviated.
  • the session function entity is a session management function entity SMF
  • the user plane function entity is UPF or the network function entity is a packet data gateway PGW.
  • the user plane function entity is the gateway user plane function GW-U.
  • the network provided by the present application may also be applied to the case where the first transmission path exists between the terminal and the user plane functional entity user plane functional entity, and then the second transmission path is initiated.
  • the session function entity determines to establish the terminal and a second transmission path between the user plane function entities; the session function entity initiates establishing the second transmission path, and may indicate, in the second transmission path establishment request, the terminal or user plane function entity in the The same data is transmitted on the first and second transmission paths.
  • the session function entity determines a manner of establishing a second transmission path between the terminal and the user plane function entity, including: the session function entity receiving a request message sent by the terminal or the policy function entity, according to the request
  • the message determines that the second transmission path between the terminal and the user plane function entity needs to be established, and may further include: the session function entity receiving a notification message (such as a failure notification message) sent by the user plane function entity about the first transmission path. It is determined that the second transmission path needs to be established.
  • a notification message such as a failure notification message
  • the present application also provides a method for improving service reliability.
  • the process implemented by the method is basically consistent with the network system description process provided above, and the description is not repeated.
  • the application also provides a terminal device, which may be a terminal or a chip in the terminal.
  • the device has the function of implementing the various embodiments described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the terminal when the device is a terminal, the terminal includes: an interaction module and a processing module, the interaction module is configured to receive a message sent by the session function entity, where the message is used to indicate that the processing module is in the user Transmitting the same data on the first transmission path and the second transmission path between the surface functional entity and the terminal; the processing module is configured to transmit the same data on the first and second transmission paths.
  • the present application also provides a session function entity, such as an SMF, including a decision module and a processing module, where the decision module is configured to determine a first transmission path and a second transmission path between the establishment terminal and the user plane functional entity, or Determining to establish a second transmission path if the first transmission path already exists; the processing module, configured to initiate establishment of the first and second transmission paths, or where the first transmission path already exists In the case that the second transmission path is initiated, the processing module is further configured to instruct the terminal or the user plane function entity to transmit the same data on the first and second transmission paths.
  • a session function entity such as an SMF
  • the decision module is configured to determine a first transmission path and a second transmission path between the establishment terminal and the user plane functional entity, or Determining to establish a second transmission path if the first transmission path already exists
  • the processing module configured to initiate establishment of the first and second transmission paths, or where the first transmission path already exists
  • the processing module is further configured to instruct the terminal or the user plane function entity to transmit the same data on the
  • the present application also provides a computer program product for performing the methods performed by the terminal and network described above when the computer product is executed.
  • the present application also provides a computer readable storage medium having stored therein instructions for performing the methods performed by the terminal and network described above.
  • FIG. 1 is a schematic structural diagram of a system 10 for improving service reliability according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a communication device 200 according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method S300 for improving service reliability according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of data transmission between a terminal and a user plane functional entity through two transmission paths according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a dual-issue and dual-receiving mechanism on a transmitting and receiving side according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a method 600 for simultaneously initiating two transmission paths according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a method 700 for initiating a new transmission path according to an embodiment of the present invention.
  • 8A and 8B are schematic diagrams showing the architecture of a 5G system according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of a signaling method 900 for simultaneously initiating two transmission paths in a scenario of a 5G according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of signaling method 1000 for simultaneously establishing two transmission paths in a scenario of a 5G according to an embodiment of the present invention
  • FIG. 11 is a flowchart of a method for establishing a new transmission path method 1100 in a scenario of a 5G according to an embodiment of the present invention
  • FIG. 12 is a flowchart of a method for establishing a new transmission path method 1200 in a scenario of a 5G according to an embodiment of the present invention
  • FIG. 13 is a schematic structural diagram of a system according to an embodiment of the present invention.
  • FIG. 14 is a schematic diagram of a session function entity 1400 according to an embodiment of the present invention.
  • FIG. 15 is a schematic diagram of an apparatus 1500 according to an embodiment of the present invention.
  • the words “first” and “second” are used. Distinguish between the same or similar items that have essentially the same effect. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the number and execution order, and the words “first”, “second” and the like are not necessarily limited.
  • FIG. 1 is a schematic structural diagram of a system 10 for improving service reliability according to an embodiment of the present application.
  • the system 10 for improving service reliability includes a terminal 101, a first access device 102, a second access device 103 or more access devices, and a functional network element in the core network, including a session function entity 104 and
  • the user plane function entity 105 may also include a policy function entity 106.
  • the user terminal 101 accesses the core network through the first access device 102 and/or the second access device 103, and performs service data transmission with the core network.
  • the first access device 102 and the second access device 103 are both connected to the core network, and the core network establishes a transmission path with the terminal 101 through the access device.
  • the terminal 101 is configured to interact with the access device (102, 103) to establish at least two transmission paths (for example, a first transmission path and a second transmission path) with the core network user plane function entity 105; and the terminal 101 receives the session function entity.
  • 104 a message transmitted via the access device (102, 103) indicating that the terminal can transmit the same data on the first transmission path and the second transmission path.
  • the first access device 102 and the second access device 103 are configured to establish a data transmission path between the user terminal 101 and the user plane function entity 105 according to the indication of the session function entity 104, the user terminal 101 or other access devices;
  • the session function entity 104 is configured to determine and initiate at least two transmission paths between the terminal 101 and the user plane function entity 105; and simultaneously indicate that the terminal 101 or the user plane function entity 105 is on the at least two paths Transfer the same data.
  • the user plane function entity 105 is configured to allocate user plane resources to at least two transmission paths and transmit the same data on the at least two transmission paths.
  • the policy function entity 106 is configured to instruct or authorize the session function entity 104 to initiate establishment of at least two transmission paths between the terminal 101 and the core network, and the at least two transmission paths are used to transmit the same data to the same user terminal.
  • the first and the second of the first access device 102 and the second access device 103 are only logically different.
  • the specific implementation may be different physical entities or the same physical entity, for example, The same base station.
  • the transmission path in the embodiment of the present invention refers to a logical channel or a data path capable of carrying service data transmission.
  • the specific implementation manner or the establishment method of the transmission path may be, for example, a user plane path between the UE and the UPF in the 5G network. .
  • the system 10 can be applied to a 4G, a 5G network, and other networks in the future.
  • the system 10 for improving service reliability provided by the embodiment of the present invention establishes at least two transmission paths for the same terminal by the core network, and transmits at least two transmission paths.
  • the same service data is transmitted on the path and the terminal respectively, so that the transmission quality of the service is better ensured and the service reliability is improved.
  • the session function entity 104, the terminal 101 or other functional entities in FIG. 1 can all be implemented by the communication device 200 in FIG.
  • the communication device 200 includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.
  • the processor 201 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
  • Communication bus 202 can include a path for communicating information between the components described above.
  • Communication interface 204 using any type of transceiver, for communicating with other devices Network communication, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), and the like.
  • the memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 203 is used to store application code for executing the method of the following embodiment of the present application, and is controlled by the processor 201 for execution.
  • the processor 201 is configured to execute the application code stored in the memory 203, thereby implementing the method for improving service reliability provided by the following embodiments of the present application.
  • processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 200 can include multiple processors, such as processor 201 and processor 208 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the communication device 200 can also include an output device 205 and an input device 206. Output device 205 is in communication with processor 401 and can display information in a variety of ways.
  • the output device 405 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 206 is in communication with processor 201 and can accept user input in a variety of ways.
  • input device 206 can be a mouse, keyboard, touch screen device or sensing device, and the like.
  • the embodiment of the present application provides a method S300 for improving service reliability, by establishing at least two transmission paths for the same terminal, and respectively transmitting the same for the terminal on at least two transmission paths.
  • the business data so as to better ensure the transmission quality of the business and improve the reliability of the business.
  • the core network determines and initiates establishing at least two transmission paths with the user terminal, where the at least two transmission paths can simultaneously transmit the same service data for the user terminal.
  • the session function entity in the core network may initiate establishment by itself, or initiate a transmission path between at least two terminals and a core network user plane functional entity according to the request of the terminal or the policy function entity.
  • the terminal needs to configure according to its own configuration and service requirements.
  • the network environment sends a request to establish a primary and secondary transmission path to the session function entity; or the policy function entity and/or the session function entity initiates establishment of at least two transmission paths according to the network condition or the service attribute, or according to the enhanced QoS request sent by the terminal;
  • the terminal and the network element of the core network cooperate with each other to initiate the negotiation, which is not limited in the embodiment of the present invention.
  • the order of establishing the at least two transmission paths may be established at the same time, or may be established one after another, as long as at least two transmission paths can simultaneously perform the same data transmission for the same user terminal; at least two transmission paths can be mutually Active/standby relationship. At this time, at least two transmission paths can simultaneously transmit the same service data, or part of the transmission path is transmitting service data. Other transmission paths are not in ongoing data transmission, but are in an established and ready state. Can be triggered according to the core network, terminal configuration or business environment, and the current transmission path The same path, simultaneous transmission of the same business data;
  • the at least two transmission paths may be established by the core network via different access devices and the terminal, or the core network may use the same access device to establish multiple transmission paths with the terminal, or anchored by one access device. Point, initiate the establishment of multiple transmission paths. Since the session function entity in the core network stores the access type information of the terminal, the session function entity can know whether the terminal has a control plane connection on the two access devices according to the access information of the terminal. The transmission path is established with different access devices. If there is only one, the other access devices are instructed by one access device, and multiple transmission paths are initiated.
  • the core network performs data transmission by using the at least two transmission paths and the terminal.
  • the data transmission may be that at least two transmission paths are simultaneously transmitting the same data, or some of the transmission paths are actually transmitting service data, and other transmission paths are in a state that has been established but does not actually transmit data, and is not actually
  • the transmission path of the transmission data may start to transmit the same service data according to the configuration of the core network and/or the terminal or the trigger of the service environment;
  • the core network can simultaneously deliver the same service data (dual or dual) to the terminal through the at least two transmission paths; or can simultaneously send the terminal through the at least two transmission paths.
  • the same business data and de-reprocessing double-receipt
  • the terminal receives the service data sent by the core network through the at least two transmission paths and performs deduplication processing (double reception); or sends the same service to the core network through the at least two transmission paths at the same time.
  • Data (dual or dual).
  • the mechanism for transmitting and receiving data on the core network side and the terminal side is as follows:
  • the embodiment of the present invention can implement the dual-issue and dual-receive functions described in the method S300 by adding a protocol stack to the user equipment (UE) and the user plane function entity of the core network.
  • UE user equipment
  • the user plane and the user plane function entity of the core network realize data transmission through two transmission paths, and respectively perform double-issue and dual-receipt processing through the protocol stack.
  • the NCP is a Network Control Protocol, that is, the network control protocol, and the first transmission path (Path1) and the second transmission path (Path2) may be the same as the 3GPP path, or may be the 3GPP and the Non-3GPP channel.
  • Figure 4 shows the data flow direction, and the dual-issue and dual-receiving mechanisms on the transmitting and receiving side.
  • the baseband chip receives the upper layer service packet, performs the packet copying, and adds the serial number and the NCP ID to the packet, and then sends it through Path1 and Path2.
  • the user plane function entity removes the protocol headers related to path1 and path2, deduplicates according to the NCP ID and sequence number, and then sends the data packet to the data network (DN).
  • DN data network
  • the first transmission path loses the data packet with sequence number 2, and the system can be used from the second when the data is received due to the adoption of the primary and secondary transmission path mechanisms.
  • the lost data packet with sequence number 2 is obtained in the transmission path, which improves the quality and reliability of data reception.
  • one of the data transmission quality and/or the link quality may be selected for reception (alternative mode) without performing execution.
  • Re-operation For example, the network side or the terminal periodically samples and monitors the data transmission quality of the two transmission paths, and according to the dynamic change of the quality, timely selects the transmission path with higher transmission quality or more conforming to the current service requirement (the most stable or the fastest) to receive. Data, compared to the way of deduplication, the alternative way can reduce the burden of deduplication on the receiving side.
  • the method for improving service reliability in the embodiment of the present invention can simultaneously transmit the same service data on two transmission paths by establishing at least two transmission paths to the core network for the same terminal, and further adopting the same service data on the transmitting and receiving side. Dual-issue and dual-receiving mechanisms enable highly reliable data transmission.
  • the two transmission paths are taken as an example for description.
  • the two transmission paths are referred to as a first transmission path and a second transmission path, or are referred to as a primary transmission path and a backup transmission path (active and standby paths).
  • the present embodiment does not limit the correspondence between the primary and secondary paths and the first and second transmission paths, that is, the first or second transmission paths may be mutually active transmission paths.
  • the session function entity determines that two transmission paths between the terminal and the user plane functional entity, that is, the first transmission path and the second transmission path, need to be established;
  • the session function entity initiates establishment of the first transmission path and the second transmission path, and notifies the identification of the two transmission paths and the association relationship to the access device and the user terminal, so as to implement establishment of two transmission paths.
  • the first type the session function entity establishes the first transmission path and the second transmission path by using the first access device and the second access device, respectively, and specifically includes:
  • the first access device is notified to establish a first transmission path, and the establishment of the first transmission path is a prior art, and details are not described herein.
  • the notification content includes: a first transmission path identifier, a second transmission path identifier, and an association identifier; establishing a second transmission path;
  • the notification content includes: a first second transmission path resource, a first second transmission path identifier information, and an association identifier, and completing establishment of two transmission paths.
  • the core network separately initiates the establishment of two transmission paths, and the access devices that are responsible for carrying the two transmission paths may have no interaction.
  • This manner can implement the 3GPP access devices to respectively carry two transmission paths, and can also implement The 3GPP and non-3GPP access devices respectively carry two transmission paths.
  • the first access device and the second access device may be the same access device (like a base station), but from the perspective of increasing reliability, the two access devices are respectively connected by different connections. Incoming device implementation, even implemented by 3GPP and non-3GPP access devices, can better improve the reliability or robustness of data transmission.
  • the second type the core network notifies the second access device to establish a second transmission path by using the first access device;
  • the session function entity notifies the first access device to establish a first transmission path with the terminal (this is a prior art, and is not described again); further, the session function entity further notifies the first access device by the first
  • the access device notifies the second access device and the terminal to interact (the interaction information includes the first transmission path identifier, the second transmission path identifier, and the backup identifier), and establishes a second transmission path.
  • the notification content includes: a first second transmission path resource, a first second transmission path identification information, and an association identifier, and completing establishment of the two transmission paths.
  • the first access device after receiving the request for establishing the second transmission path, the first access device triggers the second access device and the terminal to establish the second transmission path, and the implementation manner has less changes to the network and is easier. Compatible with existing networks.
  • the session function entity notifies the terminal or the user plane function entity to associate the first and second transmission paths by using the association identifier, where the association includes: the user plane function entity or the terminal in the first and second transmission paths Sending the same data respectively; or the user plane function entity or terminal pair from the first and second transmission paths
  • the received data is deduplicated, or the terminal selects a transmission path from the first and second transmission paths to receive data.
  • the session function entity generally includes an association tag in the setup request of the second transmission path, and the association tag (or backup tag) instructs the terminal to associate (or bind) the two transmission paths.
  • the session function entity may notify the user plane function entity to associate (or bind) the two transmission paths after receiving the response message of the completion of the second transmission path.
  • the identifier may be carried in the notification message (or the backup label) and the identifier of the first and second transmission paths.
  • step 603 when the session function entity initiates the establishment of the two transmission paths, the user may further notify the user function entity or the terminal to enable the dual-issue and/or dual-receive function, and specifically, the session function entity sends the first and/or Or, the second transmission path setup notification message carries the foregoing indication that the dual-issue and/or dual-receive function is enabled, which is not limited in the embodiment of the present invention.
  • the session function entity may separately transmit the same data by using the already associated first and second transmission paths.
  • the session function entity may notify the user function entity or the terminal to perform dual-issue and/or dual-receipt when the first and second transmission paths are initiated, or may be based on the network or service after the two transmission paths are established.
  • the situation informs the user that the function entity or the terminal actually performs dual-issue and/or dual-receiving using the established two transmission paths.
  • Method S700 Referring to FIG. 7, a transmission path exists between the current terminal and the core network user plane functional entity user plane functional entity, and a new transmission path still needs to be established;
  • the terminal already has a transmission path with the network side at this time, or alternatively, the service data has been transmitted through the first transmission path, but the transmission quality needs to be improved due to changes in service requirements or changes in network conditions. The quality of the transmission is not degraded, so the session function entity needs to be requested to increase the QoS.
  • the terminal or network side network element such as a policy function entity or a username function entity, may also directly send a request to the session function entity to request to establish a second transmission path (backup path).
  • the session function entity determines that a second transmission path between the terminal and the user plane functional entity needs to be established
  • the session function entity may establish a second transmission path according to the QoS requirement of the service and/or the local network load condition, and the session function entity may further request authorization from the policy function entity, and the policy function entity decision may establish a second transmission path for the service. Send a response to the session function entity.
  • the session function entity may directly initiate the establishment of the second transmission path according to the received second transmission path establishment request.
  • the session function entity initiates the establishment of the second transmission path.
  • the second transmission path is established by the access device, and there are two ways:
  • the first type the first transmission path has been established by the core network through the first access device, and the core network establishes a second transmission path by using the second access device;
  • Notifying the second access device, the notification content includes: a first transmission path identifier, a second transmission path identifier, and an association identifier, and establishing a second transmission path.
  • the core network initiates the establishment of a new transmission path (the second transmission path), and the access devices that are responsible for carrying the two transmission paths may have no interaction between each other.
  • the 3GPP access device can respectively carry two transmission paths.
  • the 3GPP and non-3GPP access devices can respectively implement two transmission paths. It should be noted that the first access device and the second access device may be the same access device (like a base station).
  • the second type the core network notifies the second access device to establish a second transmission path by using the first access device;
  • S703a Notifying the first access device, including the first transmission path identifier, the second transmission path identifier, and the association identifier.
  • the first access device notifies the terminal and the second access device to establish a second transmission path (backup path);
  • the first access device After receiving the request for establishing the second transmission path, the first access device notifies the terminal and the second access device to establish a second transmission path, which has less modification to the network and is more compatible with the existing network.
  • the session function entity may notify the terminal or the user plane function entity to associate the first and second transmission paths when initiating the establishment of the second transmission path, where the association includes: the user plane function entity or the terminal is in the Transmitting the same data on the first and second transmission paths respectively; or the user plane function entity or terminal deduplicating data received from the first and second transmission paths, or from the first sum A transmission path is selected in the second transmission path to receive data.
  • the session function entity includes an association label in the setup request of the second transmission path, and the association label instructs the terminal to associate (or bind) the two transmission paths.
  • the session function entity may notify the user plane function entity to associate (or bind) the two transmission paths after receiving the response message that the second transmission path is established.
  • the session function entity may further notify the user plane function entity or the terminal to start dual-issue and/or dual-receive when the active/standby transmission path is established. Specifically, the session function entity sends the second transmission path.
  • the notification message is established, the above-mentioned dual-issue and/or dual-receive indication is carried out, which is not limited in the embodiment of the present invention.
  • the session function entity may separately transmit the same data by using the already associated first and second transmission paths.
  • the terminal or the network side when the first transmission path already exists, or the first transmission path is already performing data transmission, the terminal or the network side initiates the establishment of the second transmission according to the service requirement or the network condition change.
  • the path can transmit the same service data together with the first transmission path, thereby improving the reliability and flexibility of the data transmission. Since the two transmission paths do not need to be established at the same time from the beginning, the processing load on the terminal and the network side is saved. Network resources add flexibility.
  • the session function entity may be an SMF (Session Management Function) in 5G or a PGW (PDN Gataway) in 4G: the policy function entity may be in 5G.
  • the PCF Policy Control Function
  • the PCRF Policy and Charging Rules Function
  • the user plane function entity can be a User Plane Function (UPF) in the 5G. Or GW-U (Gateway User plane function) in 4G.
  • FIG. 8A the UE accesses the network only through the 3GPP access device.
  • FIG. 8B the UE accesses the network through the 3GPP access device and the Non-3GPP access device at the same time, and the two types shown in FIG. 8A and FIG. 8B are required to be described.
  • the access device that connects the UE to the network and the AMF have a control plane connection.
  • the QoS flow is the minimum granularity of QoS differentiation in 5G.
  • all service flows use the same forwarding process, including scheduling policy, queue management, traffic shaping, and resource configuration.
  • different QoS flows are required, one transmission path corresponding to one QoS flow.
  • the first and second transmission paths are established based on the architectures of FIG. 8A and 8B.
  • the active and standby paths are established in the initial stage, services with high reliability requirements can be ensured. (For example, URLLC service)
  • URLLC service In addition to the main path, there can be a backup path available.
  • the steps of Embodiment 900 are specifically described as follows:
  • the UE sends a service request to the SMF, including QoS parameters, an active/standby path establishment indication (optional), etc.; the SMF is based on the type of the UE (for example, the UE is a URLLC terminal), QoS requirements, etc., and refers to the network load situation, and the main The backup path indication label (optional) determines that the active and standby QoS flows are established for the service requirement of the UE.
  • the SMF may further request authorization from the PCF, that is, send the active/standby path establishment request to the PCF, and the request message carries QoS parameters, such as 5QI (5G QoS indicator, 5G QoS label, or specific QoS requirement).
  • the PCF determines that the SMF can establish an active/standby path for the UE according to the UE subscription information and the QoS parameters, and the PCF sends an active/standby path setup response message to the SMF, where the message indicates that the SMF can establish a primary and backup path for the service request of the UE.
  • the PCF sends a service request to the SMF, including the QoS parameter and the active/standby path indication.
  • the PCF needs to establish an active/standby path for the service according to the QoS parameter and the UE subscription information decision.
  • the SMF may carry the active/standby path indication label and the like; the SMF establishes the service requirement of the UE according to the UE type (URLLC terminal), QoS requirement, etc., and refers to the network load condition and the active/standby path indication label (optional).
  • the active/standby QoS flow is set up (or the primary and backup paths are established for the UE according to the establishment of the active/standby path of the PCF).
  • the SMF initiates the establishment of the active/standby path, including: the SMF allocates the primary and secondary QoS flow user plane resources, and the primary package
  • the QFI QoS flow identity
  • the details are as follows: QoS flow-related resources such as QFIs corresponding to the primary and secondary QoS flows are allocated, for example, PCC (Policy Charging Control) rules.
  • the charging or QoS policies of the two QoS flows may be the same or different (for example, the second QoS flow may not be charged), which is not limited in this embodiment.
  • the SMF may also decide whether to notify the UPF and/or the UE to enable dual transmission (double-issue and/or dual-receiving) according to the URLLC service type and/or the terminal type.
  • the SMF carries the dual-transmission indication notification when the active/standby path establishment notification message is sent. Instruct the UPF and the UE to perform dual transmission.
  • the URLLC terminal is a low-end mobile terminal, it indicates that the network path is relatively stable. Only the active/standby path is established for it. Then, dual-transmission is enabled when needed.
  • the SMF sends a primary and secondary QoS flow creation request to the AMF, where the request message carries: the primary and secondary QoS flows QFI, the PDU Session ID (the primary and secondary QoS flows need to carry two PDU Session IDs if they are in different PDU sessions), TFT, QoS, backup label, dual transmission indication (optional), etc.;
  • the backup label is used to indicate the relationship between the two QoS flows.
  • the relationship between the two QoS flows can be called the active/standby relationship, the associated relationship, or the binding relationship.
  • the UE or the UPF can determine that the two QoS flows can be transmitted separately according to the backup label. The same data.
  • the AMF receives the primary and secondary QoS flow establishment request sent by the SMF, and sends a QoS flow establishment request to the first access device, where the request message carries the PDU Session ID, and the QoS rule, etc.;
  • the QoS flow establishment request is made, the QoS rule is mapped to the radio QoS rule, the wireless reconfiguration information is sent to the UE, and the first QoS flow is established;
  • the first access device sends a QoS flow setup response message to the AMF, and notifies the AMF, first.
  • the QoS flow radio side is established;
  • AMF initiates a backup QoS establishment process.
  • the AMF sends a QoS flow creation request message to the second access device, where the request message carries: a first QoS flow QFI, a PDU Session ID, a second QoS flow QFI, and a PDU Session ID (a PDU Session that can be associated with the first QoS flow) ID is the same, can also be different, no restrictions), backup label, dual transmission indication (optional), QoS, etc.
  • the second access device receives the backup QoS flow creation request, maps the QoS rule to the radio QoS rule, sends the wireless reconfiguration information to the UE, and completes the second QoS flow establishment.
  • the UE side performs binding (or association) of two QoS flows according to the backup label and the first QoS flow identifier (QFI, PDU Session ID) and the second QoS flow identifier (QFI). Specifically, the The established first QoS flow is bound to the existing first QoS flow, and the association between the active and standby paths is completed.
  • the reconfiguration message includes a dual transmission indication, the UE enables dual transmission.
  • the UE performs the data packet replication, and copies the first QoS flow data locally, and sends the original data packet to the first access device by using the radio bearer corresponding to the first QoS flow. And transmitting the copied data packet to the second access device by using the radio bearer where the second QoS flow is located.
  • the UE adds a dual transport protocol header to the data packets of the first QoS flow and the second QoS flow, and the protocol header carries the packet sequence number, identifier, and the like.
  • UPF can implement deduplication by parsing the dual transport protocol header.
  • the second access device sends a QoS flow setup response message to the AMF, notifying the AMF that the wireless side of the second QoS flow is established.
  • the AMF sends a primary and secondary QoS flow setup response message to the SMF.
  • the message includes: a first QoS flow identifier and a second QoS flow identifier, and the like.
  • the S911.SMF notifies the UPF to establish the first and second QoS flow UPF side user plane resources.
  • the SMF allocates resources (the tunnel, and the charging QoS rules obtained by the SMF from elsewhere), and sends them to the UPF.
  • the UPF stores/installs these rules to implement the establishment of user plane resources.
  • the SMF sends an N4 session modification message to the UPF, which carries the following content:
  • the UPF side is based on the backup label and the first QoS flow identifier (QFI, PDU Session ID) and the second QoS Flow ID (QFI).
  • QFI first QoS flow identifier
  • PDU Session ID PDU Session ID
  • QFI second QoS Flow ID
  • the UPF performs the following actions:
  • the UPF When receiving the data packet corresponding to the first QoS flow sent by the DN, the UPF performs data packet replication, and sends the original data packet to the first access device through the N3 tunnel where the first QoS flow is located. The copied data packet is sent to the second access device through the N3 tunnel where the second QoS flow is located.
  • the UPF adds a dual transport protocol header to the data packets of the first QoS flow and the second QoS flow, and the protocol header carries the packet sequence number, identifier, and the like.
  • the UE can implement the deduplication operation by parsing the dual transmission protocol header;
  • the UPF establishes a policy charging rule related to the second QoS flow, and the like.
  • the UPF sends an N4 session modification response message to the SMF to complete the creation of the user plane resources of the active and standby QoS flows on the UPF side.
  • the URL LC service is identified by the network side, and the active and standby paths are established for the service to improve the quality of the service transmission and the reliability of the error, and in the embodiment, there is no communication between the two access devices.
  • the requirement can realize the scenario that the UE simultaneously accesses the hybrid access through 3GPP and Non-3GPP to maximize the transmission efficiency.
  • FIG. 8A and FIG. 10 a schematic flowchart of another embodiment 1000 for establishing an active/standby path (ie, a first transmission path and a second transmission path) in an initial stage, in this embodiment, a first access device and a first
  • the second access device has a communication interface, and the UE can establish the same PDU session by using the first access device and the second access device, where the control plane context of the UE is located in the first access device, that is, the AMF and the first access.
  • the device has a signaling plane connection.
  • the primary and secondary transmission path establishment decision specifically refer to the foregoing embodiment step S901;
  • the SMF initiates the establishment of the active and standby paths. For details, refer to step S902 in the foregoing embodiment.
  • the SMF sends a primary and secondary QoS flow creation request to the AMF, where the request message carries:
  • the AMF receives the primary and secondary QoS flow establishment request sent by the SMF, and sends a primary and secondary QoS flow establishment request to the first access device, where the request message carries the PDU Session ID, the first QoS flow QFI, and the second QoS flow QFI. , QoS rules Then, backup label, dual transmission indication (optional), etc.;
  • the first access device initiates a second access device adding process (refer to the process of adding a secondary base station by the primary base station in the prior art, and may refer to the 3GPP standard TS36.300 for details);
  • the first access device sends a QoS flow setup request message to the second access device, where the request message carries the second QoS flow QFI, the first tunnel information on the UPF side, the PDU Session ID, the QoS rule, and the like.
  • the second access device allocates radio resource information for the second QoS flow, and sends the allocated radio resource information to the first access device.
  • the first access device notifies the UE to establish the first QoS flow and the second QoS flow, where the notification message includes:
  • First QoS flow identifier First QoS flow identifier, second QoS flow identifier, PDU Session ID, backup label.
  • the UE implements an active/standby relationship between the first QoS flow and the second QoS flow according to the information, and completes the association between the active and standby paths.
  • Dual transmission indication instructing the UE to perform dual-receive dual-issue.
  • the radio resource information allocated by the first access device is the first QoS flow
  • the UE initiates a radio reconfiguration message to the first access device according to the radio resource information, and completes the establishment of the first QoS flow.
  • the radio resource information allocated by the second access device for the second QoS flow the UE initiates a radio reconfiguration message to the second access device according to the radio resource information, and completes the establishment of the second QoS flow.
  • the UE initiates radio reconfiguration information to the first access device, and completes establishment of the first QoS flow.
  • the UE initiates wireless reconfiguration information to the second access device, and completes establishment of the second QoS flow.
  • the first access device sends a QoS flow setup response message to the AMF, where the response message carries a QFI, a PDU Session ID, and the like of the first QoS flow and the second QoS flow.
  • the AMF sends a primary and secondary QoS flow setup response message to the SMF.
  • the message includes: a first QoS flow identifier and a second QoS flow identifier, and the like.
  • the SMF notifies the UPF to establish a first and second QoS flow UPF side user plane resource
  • the SMF allocates resources (the tunnel, and the charging QoS rules obtained by the SMF from elsewhere), and sends them to the UPF.
  • the UPF stores/installs these rules to implement the establishment of user plane resources.
  • the SMF sends an N4 session modification message to the UPF, which carries the following content:
  • the UPF side is based on the backup label and the first QoS flow identifier (QFI, PDU Session ID) and the second QoS Flow ID (QFI).
  • QFI first QoS flow identifier
  • PDU Session ID PDU Session ID
  • QFI second QoS Flow ID
  • the UPF performs the following actions:
  • the UPF When receiving the data packet corresponding to the first QoS flow sent by the DN, the UPF performs data packet replication, and sends the original data packet to the first access device through the N3 tunnel where the first QoS flow is located. The copied data packet is sent to the second access device through the N3 tunnel where the second QoS flow is located.
  • the UPF adds a dual transport protocol header to the data packets of the first QoS flow and the second QoS flow, and the protocol header carries the packet sequence number, identifier, and the like.
  • the UE can implement the deduplication operation by parsing the dual transmission protocol header.
  • the UPF establishes a policy charging rule related to the second QoS flow, and the like.
  • the UPF sends an N4 session modification response message to the SMF to complete the creation of the user plane resources of the active and standby QoS flows on the UPF side.
  • two access devices establish interaction between two access devices through interaction, and the core network can only give one The establishment of the primary and secondary transmission paths can be established by the access device sending the primary and secondary transmission path establishment requests.
  • the existing core network generally only allows one of the access devices to have a control plane connection with the AMF (such as the primary base station and the secondary base station mechanism), and the solution of this embodiment has less changes to the network and is easier to The current network is compatible.
  • Embodiment 1100 based on the architecture of FIG. 8A, 8B, the core network initiates the establishment process of establishing the second transmission path on the basis that the first transmission path already exists.
  • the steps of Embodiment 1100 are specifically described as follows:
  • the UE sends a QoS promotion request or a link failure notification to the SMF, including QoS parameters, link failure notification, backup path establishment indication (optional, very unlikely), etc.; SMF according to UE type (URLLC terminal), QoS Raising the requirements, etc., and referring to the network load condition and the backup path indication label (optional), the decision is made to establish a backup QoS flow for the request of the UE;
  • the SMF may further request authorization from the PCF, that is, send a backup path establishment request to the PCF, and the request message carries QoS parameters (such as 5QI or specific QoS requirements), and the PCF is based on the PCF.
  • the UE may sign the information and the QoS parameters, and the decision may authorize the SMF to establish a backup path for the UE, and send an active/standby path setup response message to the SMF, where the message indicates that the SMF may establish a backup QoS flow for the request of the UE;
  • the PCF sends a service request to the SMF, including the QoS parameter and the backup label. (Optional, after the PCF receives the service request from the DN, the PCF needs to establish an active/standby path for the service according to the QoS parameter and the UE subscription information decision.
  • the PCF can also carry the QFI and PDU Session ID of the original QoS flow in the service request; the SMF according to the type of the UE (URLLC terminal), QoS requirements, etc., and refer to the network load condition, and the backup label (optional) And the original QoS flow identifier, the decision to establish a backup QoS flow (or according to the PCF's active and standby establishment instructions, the level of the foregoing backup label, establish a primary and backup path for the UE);
  • the UPF senses that the link quality deteriorates, for example, lower than the preset value, notifies the SMF, carries the PDU Session ID, QFI, etc.; the SMF according to the type of the UE (URLLC terminal), QoS enhancement requirements, etc., and refers to the network load situation, And a backup path indication label (optional), the decision is to establish a backup QoS flow for the request of the UE;
  • the UPF senses that the link quality is deteriorated, and notifies the SMF; the SMF needs to be the UE according to the type of the UE (URLLC terminal), the QoS requirement, and the network load condition, and the backup path indication label (optional).
  • the request establishes a backup QoS flow; the SMF sends a backup path setup request to the PCF, and the request message carries a QoS parameter (such as 5QI or specific QoS requirement); the PCF determines that the SMF can establish a backup path for the UE according to the UE subscription information and the QoS parameter.
  • the PCF sends a primary and secondary path setup response message to the SMF, the message indicating that the SMF can establish a backup QoS flow for the request of the UE.
  • the SMF initiates the establishment of the backup path, including: the SMF allocates the backup QoS flow user plane resources, mainly including the QFI of the active and standby QoS flows, the packet detection and charging rules, and the like.
  • QoS flow related resources such as QFI corresponding to the backup QoS flow are allocated, for example, a PCC (Policy Charging Control) rule.
  • the charging or QoS policy of the backup QoS flow may be the same as or different from the primary QoS flow (for example, the backup QoS flow may not be charged), which is not limited in this embodiment.
  • the SMF may also decide whether to notify the UPF and/or the UE to enable dual transmission (double-issue and/or dual-receiving) according to the URLLC service type and/or the terminal type.
  • the SMF carries a dual transmission indication notification when the backup path establishment notification message is sent, indicating that the UPF and the UE perform dual transmission.
  • the URLLC terminal is a low-end mobile terminal, it indicates that the network path is relatively stable. You can set up a backup path for it only, and then enable dual-transmission when needed.
  • the SMF sends a backup QoS flow creation request to the AMF, where the request message carries: the primary and secondary QoS flows QFI, the PDU Session ID (if the primary and secondary QoS flows are in different PDU sessions, the two PDU Session IDs are required), TFT , QoS, backup label, dual transmission indication (optional), etc.;
  • the backup label is used to indicate the relationship between the two QoS flows.
  • the relationship between the two QoS flows can be called the active/standby relationship, the associated relationship, or the binding relationship.
  • the UE or the UPF can determine that the two QoS flows can be transmitted separately according to the backup label. The same data.
  • AMF initiates a backup QoS establishment process.
  • the AMF sends a QoS flow creation request message to the second access device, where the request message carries: a first QoS flow QFI, a PDU Session ID, a second QoS flow QFI, and a PDU Session ID (a PDU Session that can be associated with the first QoS flow) ID is the same, can also be different, no restrictions), backup label, dual transmission indication (optional), QoS, etc.
  • the second access device receives the backup QoS flow creation request, maps the QoS rule to the radio QoS rule, sends the wireless reconfiguration information to the UE, and completes the second QoS flow establishment.
  • the UE side performs binding (or association) of two QoS flows according to the backup label and the first QoS flow identifier (QFI, PDU Session ID) and the second QoS flow identifier (QFI). Specifically, the The established first QoS flow is bound to the existing first QoS flow, and the association between the active and standby paths is completed. Optionally, if the reconfiguration message includes a dual transmission indication, the UE enables dual transmission. Referring to FIG. 4 and FIG. 5, the specific implementation is as follows:
  • the UE performs the data packet replication, and copies the first QoS flow data locally, and sends the original data packet to the first access device by using the radio bearer corresponding to the first QoS flow. And transmitting the copied data packet to the second access device by using the radio bearer where the second QoS flow is located.
  • the UE adds a dual transport protocol header to the data packets of the first QoS flow and the second QoS flow, and the protocol header carries the packet sequence number, identifier, and the like.
  • UPF can implement deduplication by parsing the dual transport protocol header.
  • the second access device sends a QoS flow setup response message to the AMF, notifying the AMF that the wireless side of the second QoS flow is established.
  • the AMF sends a primary and secondary QoS flow setup response message to the SMF.
  • the message includes: a first QoS flow identifier and a second QoS flow identifier, and the like.
  • the SMF notifies the UPF to establish a second QoS flow UPF side user plane resource.
  • the SMF sends an N4 session modification message to the UPF, which carries the following content:
  • the UPF side is based on the backup label and the first QoS flow identifier (QFI, PDU Session ID) and the second QoS Flow ID (QFI).
  • QFI first QoS flow identifier
  • PDU Session ID PDU Session ID
  • QFI second QoS Flow ID
  • the UPF performs the following actions:
  • the UPF When receiving the data packet corresponding to the first QoS flow sent by the DN, the UPF performs data packet replication, and sends the original data packet to the first access device through the N3 tunnel where the first QoS flow is located. The copied data packet is sent to the second access device through the N3 tunnel where the second QoS flow is located.
  • the UPF adds a dual transport protocol header to the data packets of the first QoS flow and the second QoS flow, and the protocol header carries the packet sequence number, identifier, and the like.
  • the UE can implement the deduplication operation by parsing the dual transmission protocol header;
  • the UPF establishes a policy charging rule related to the second QoS flow, and the like.
  • the UPF sends an N4 session modification response message to the SMF to complete the creation of the QoS flow user plane resource on the UPF side.
  • the core network initiates the establishment of a new transmission path (the second transmission path), and the access devices that are responsible for carrying the two transmission paths may have no interaction.
  • the strip transmission path can also implement 3GPP and non-3GPP access devices to respectively carry two transmission paths.
  • the first access device and the second access device may be the same access device (like a base station).
  • Embodiment 1200 based on the architecture of FIG. 8A, the core network initiates an establishment process of establishing a second transmission path on the basis that the first transmission path already exists.
  • the steps of Embodiment 1200 are specifically described as follows:
  • the SMF initiates the establishment of the backup path. For details, refer to step S1102 in the foregoing embodiment.
  • the SMF sends a second QoS flow creation request to the AMF, where the request message carries: a first QoS flow QFI, a second QoS flow QFI, a PDU Session ID (the primary and secondary QoS flows are in the same PDU session), TFT, QoS, Backup label, dual transmission indication (optional), etc.
  • the AMF receives the second (backup) QoS flow setup request sent by the SMF, and sends a backup QoS flow setup request to the first access device, where the request message carries the PDU Session ID, the first QoS flow QFI, and the second QoS. Flow QFI, QoS rules, backup label, dual transmission indication (optional), etc.
  • the request message is used to indicate the first access device to establish a backup QoS flow between the second access device and the UE.
  • the first access device initiates a second access device adding process (refer to the prior art, the primary base station initiates a supplementary base station adding process, and may refer to TS36.300 for details);
  • the first access device sends a QoS establishment request message to the second access device, where the request message carries a second QoS flow QFI, a PDU Session ID, a QoS rule, and the like.
  • the second access device allocates radio resource information for the second QoS flow, and sends the allocated radio resource information to the first access device.
  • the first access device notifies the UE to establish a second QoS flow, where the notification message includes:
  • First QoS flow identifier First QoS flow identifier, second QoS flow identifier, PDU Session ID, backup label.
  • the UE implements an active/standby relationship between the first QoS flow and the second QoS flow according to the information, and completes the association between the active and standby paths.
  • Dual transmission indication instructing the UE to perform dual-receive dual-issue.
  • the second access device allocates radio resource information for the second QoS flow, and the UE can complete the establishment of the second QoS flow according to the radio resource information.
  • the UE initiates radio reconfiguration information to the second access device, and completes establishment of the second QoS flow.
  • the first access device sends a QoS flow setup response message to the AMF.
  • the AMF sends a primary and secondary QoS flow setup response message to the SMF.
  • the SMF notifies the UPF to establish a second QoS flow UPF side user plane resource
  • the SMF allocates resources (the tunnel, and the charging QoS rules obtained by the SMF from elsewhere), and sends them to the UPF.
  • the UPF stores/installs these rules to implement the establishment of user plane resources.
  • the SMF sends an N4 session modification message to the UPF, which carries the following content:
  • the UPF side is based on the backup label and the first QoS flow identifier (QFI, PDU Session ID) and the second QoS Flow ID (QFI). Bind the two QoS flows to complete the association between the active and standby paths.
  • the UPF performs the following actions:
  • the UPF When receiving the data packet corresponding to the first QoS flow sent by the DN, the UPF performs data packet replication, and sends the original data packet to the first access device through the N3 tunnel where the first QoS flow is located. The copied data packet is sent to the second access device through the N3 tunnel where the second QoS flow is located.
  • the UPF adds a dual transport protocol header to the data packets of the first QoS flow and the second QoS flow, and the protocol header carries the packet sequence number, identifier, and the like.
  • the UE can implement the deduplication operation by parsing the dual transmission protocol header.
  • the UPF establishes a policy charging rule related to the second QoS flow, and the like.
  • the UPF sends an N4 session modification response message to the SMF to complete the creation of the user plane resources of the active and standby QoS flows on the UPF side.
  • the core network notifies the second access device and the UE to establish the second transmission path by using the first access device.
  • the existing core network generally only allows one of the access devices to have a control plane connection with the AMF (such as the primary base station and the secondary base station mechanism), and the solution of this embodiment has less changes to the network and is easier to The current network is compatible.
  • the method in the foregoing embodiment of the present invention can also be applied to the current 4G network.
  • One possible applicable architecture is the architecture shown in FIG. 13.
  • the UE accesses the core network through the 3GPP access device (E-UTRAN).
  • the UE can also access the network through the 3GPP access device and the Non-3GPP access device in the 4G, as long as the control plane is connected between the access device that accesses the UE and the MME.
  • the name and function description of the network element involved in Figure 13 are as follows:
  • the corresponding functions of the SMF in the foregoing embodiments of the present invention are performed by the PGW network element; the MME network element performs AMF in the present invention.
  • the PGW network element performs AMF in the present invention.
  • PCRF performs PCF corresponding functions in the foregoing embodiments of the present invention, and other related
  • the network element can also be similarly implemented with reference to the foregoing embodiment, and details are not described herein again.
  • the bearer is the minimum granularity for distinguishing QoS. Within one bearer, all service flows use the same forwarding process, including scheduling policy, queue management, traffic shaping, resource configuration, etc.; different QoS processing is required. Different bearers need to be used, so in 4G, one transmission path corresponds to one bearer.
  • the terminal in all of the foregoing embodiments may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; and may also include a subscriber unit , cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handheld, laptop Laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (UE), mobile station ( Mobile station, MS), terminal device, etc.
  • PDA personal digital assistant
  • WLL cordless phone or wireless local loop (WLL) station
  • MTC machine type communication
  • UE user equipment
  • MS Mobile station
  • terminal device etc.
  • the access device refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (BNG), an aggregation switch, a non-3GPP access device, or the like.
  • the base station may include various forms of base stations, such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.
  • the action of the PGW may be performed by the processor 201 in the communication device 200 shown in FIG. 2, and the application code stored in the memory 203 is used to perform the implementation.
  • the embodiment of the present application does not impose any limitation.
  • the action involving the terminal can also be performed by the processor 201 in the communication device 200 shown in FIG. 2 by calling the application code stored in the memory 203. This embodiment of the present application does not impose any limitation.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements.
  • the above-mentioned session function entity or terminal device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may perform a function module division on a session function entity or a terminal device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 14 shows a possible structural diagram of the session function entity 1400 involved in all of the foregoing embodiments.
  • the session functional entity includes a decision module 1401 and a processing module 1402.
  • the decision module 1401 is configured to determine a first transmission path and a second transmission path between the establishment terminal and the user plane functional entity, or determine to establish the second transmission path if the first transmission path already exists;
  • the processing module 1402 And initiating establishing the first and second transmission paths, or initiating establishment of the second transmission path if the first transmission path already exists;
  • the processing module 1402 is further configured to indicate the terminal Or the user plane function entity transmits the same data on the first and second transmission paths.
  • the session function entity further includes a notification module 1403, where the notification module 1403 is configured to When the processing module 1402 initiates the establishment of the second transmission path, notifying the user plane function entity and/or the terminal to start transmitting the same data in the first and second transmission paths; or after the second transmission path is established After the completion, according to the terminal or the network side request, the user plane function entity and/or the terminal is notified to start transmitting the same data on the first and second transmission paths.
  • the notification module 1403 is configured to When the processing module 1402 initiates the establishment of the second transmission path, notifying the user plane function entity and/or the terminal to start transmitting the same data in the first and second transmission paths; or after the second transmission path is established After the completion, according to the terminal or the network side request, the user plane function entity and/or the terminal is notified to start transmitting the same data on the first and second transmission paths.
  • the determining module 1401 obtains service QoS information according to the service request sent by the terminal or the policy function entity, and determines, according to the QoS information, that the first and second transmissions between the terminal and the user plane functional entity need to be established. Or the decision module 1401 requests authorization from the policy function entity according to the active/standby transmission path establishment indication or the bidirectional indication carried in the service request sent by the terminal, and determines that the terminal and the user plane need to be established according to the authorization result.
  • the determining module 1401 receives the request message sent by the terminal or the policy function entity, and determines, according to the request message, that a second transmission path between the terminal and the user plane functional entity needs to be established; or the determining module 1401 receives The notification message about the first transmission path sent by the user plane function entity determines that the second transmission path needs to be established according to the notification message.
  • the notification message may be a first transmission path failure notification message.
  • the processing module 1402 sends the first and second transmission path establishment requests to the mobility management entity, and notifies the mobility management entity to respectively indicate the first connection according to the first and second transmission path establishment requests.
  • the ingress device and the second access device negotiate with the terminal to establish the first and second transmission paths.
  • the session function entity may be an SMF or a PGW. All the related content in the foregoing embodiments may be referred to the function description of the corresponding function module, and details are not described herein.
  • FIG. 15 is a schematic diagram of a possible device structure of the terminal involved in all the foregoing embodiments.
  • the device 1500 may be a terminal or a chip in the terminal, which is not specifically limited in this embodiment of the present application.
  • the device 1500 includes an interaction module 1501 and a processing module 1502.
  • the interaction module 1501 is configured to receive a message sent by the session function entity, where the message indicates that the terminal device transmits the same data on the first transmission path and the second transmission path between the user plane function entity and the terminal; the processing module 1502 For transmitting the same data on the first and second transmission paths.
  • the interaction module 1501 is further configured to send a service request to the session function entity, where the service request carries an indication that at least two transmission paths are established, or a second transmission path is established.
  • the interaction module 1501 negotiates with the first access device and the second access device to establish the first transmission path and the second transmission path, respectively.
  • the processing module 1502 transmits the same data on the first and second transmission paths.
  • the processing module 1502 is in the first Sending the same data to the user plane function entity user plane function entity on the second transmission path; or the processing module 1502 receives the user plane function entity user plane function entity from the first and second transmission paths
  • the same data is transmitted and the received data is deduplicated, or the processing module 1502 selects a transmission path from the first and second transmission paths to receive data.
  • the function/implementation process of the interaction module 1501 can also be implemented by using a pin or a circuit or the like.
  • the session function entity 1400 and the device 1500 provided by the embodiment of the present application are used to perform all the foregoing methods for improving the reliability of the service. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.

Landscapes

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

Abstract

提升业务可靠性的方法，网络中的会话功能实体决策并发起建立终端与所述用户面功能实体之间的至少两条传输路径，并指示所述终端或所述用户面功能实体在所述至少两条路径上传输相同的数据；所述用户面功能实体用于根据所述会话功能实体的通知，给所述至少两条传输路径分配用户面资源，并在所述至少两条传输路径上与所述终端传输相同的数据，由核心网发起建立了到终端的至少两条传输路径，可以分别由两个接入设备单独建立，也可以以一个接入设备为锚点，触发其他接入设备和终端建立其他传输路径，，终端和网络侧进行相应的进行双发和双收，对收到的数据进行去重，本发明使得高可靠性业务的数据传输的可靠性得到了很好的保证。

Description

提升业务可靠性的方法、设备及系统 技术领域
本申请涉及通信技术领域，尤其涉及提升业务可靠性的方法、设备及系统。
背景技术
为了应对无线宽带技术的挑战，保持第三代合作伙伴计划(3rd generation partnership project，3GPP)网络的领先优势，3GPP标准组在2016年底制定了下一代移动通信系统(next generation system)网络架构，称为第五代(5rd generation，5G)网络架构。
5G网络架构中定义了极高可靠性低时延通信(ultra-reliable low latency communication，URLLC)场景，主要包括如无人驾驶、工业自动化等需要低时延、高可靠连接的业务。5G网络的先进空口技术和优化的核心网络架构，使得上述场景的要求成为可能。但是移动网络自身不管是底层链路还是上层路由协议等均存在一定的不稳定性，而上述场景多为生命安全或生产安全相关的业务，因此容不得差错。因此我们需要给出优化的网络方案，使得网络即便在链路质量不好的情况下，仍能够尽可能的满足上述要求。
发明内容
为了满足对高度可靠性的应用的需求，本申请提供了一种提升业务可靠性的网络，所述网络包括会话功能实体和用户面功能实体，所述会话功能实体用于决策并发起建立终端与所述用户面功能实体之间的至少两条传输路径，并指示所述终端或所述用户面功能实体在所述至少两条路径上传输相同的数据；所述用户面功能实体用于根据所述会话功能实体的通知，给所述至少两条传输路径分配用户面资源，并在所述至少两条传输路径上与所述终端传输相同的数据，由网络发起建立了到终端的至少两条传输路径，对于高可靠性业务的数据传输的可靠性得到了很好的保证。
其中，触发网络确定建立多条传输路径的情况有很多种，包括：
所述会话功能实体根据所述终端或者策略功能实体发送的业务请求，获取业务QoS信息，根据所述QoS信息确定需要建立终端与用户面功能实体之间的所述第一和第二传输路径；或者所述会话功能实体根据所述终端发送的业务请求中携带的主备传输路径建立指示或者双播指示，向策略功能实体请求授权，根据所述授权结果确定需要建立终端与用户面功能实体之间的第一和第二传输路径。
其中，所述会话功能实体指示所述终端或用户面功能实体在所述第一和第二传输路径上传输相同的数据，包括：所述会话功能实体给所述终端或者用户面功能实体用户面功能实体发送关联标识(或称备份标识等)，所述关联标识指示所述终端或用户面功能实体在所述第一和第二传输路径上传输相同的数据。
其中，建立多条传输路径，和通知终端或者用户面功能实体开始利用建立的多条传输路径进行数据传输，可以先后完成，也可以同时完成。例如，可以是会话功能实体在发起建立所述第一和第二传输路径时，即一并通知所述用户面功能实体和/或终端通过所述建立好的第一和第二传输路径开始传输相同的数据；也可以是会话功能实体在所述第一和第二传输路径建立后完成后，根据网络情况或者业务要求，再去通知所述用户面功能实体和 /或终端在所述第一和第二传输路径上开始传输相同的数据，这样的处理方式，可以增强多传输路径使用的灵活性。
其中，网络建立多传输路径的方式可以有很多种，一种是分别建立，承载各传输路径的接入设备之间可以没有关联，即会话功能实体通知所述移动性管理实体，分别指示第一接入设备和第二接入设备与所述终端协商建立所述第一和第二传输路径；还可以是会话功能实体通过一个接入设备(即以第一接入设备为锚点)来发起建立多条传输路径，例如由会话功能实体给移动性管理实体发送所述第一和第二传输路径建立请求，所述移动性管理实体根据会话功能实体的指示，指示第一接入设备建立所述第一传输路径，并指示所述第一接入设备通知第二接入设备建立所述第二传输路径，例如可以是第一接入设备获取第二接入设备的资源信息，然后通知终端，由终端发起建立和第二接入设备的连接，完成第二传输路径的建立。
其中，所述终端或所述用户面功能实体在所述第一和第二传输路径上传输相同的数据，包括：所述用户面功能实体或者终端在所述第一和第二传输路径上发送相同的数据；或者，所述用户面功能实体或者终端从所述第一和第二传输路径上接收相同的数据并对所述接收的数据去重。另外，从接收侧来说，终端或所述用户面功能实体也可以根据数据传输质量和/或者链路质量，从建立的两条传输路径中选择一条进行数据接收，而不必执行去重操作，虽然增加了路径质量检测的工作，但是可以减轻数据去重的负担。
其中，在5G的网络下，所述会话功能实体为会话管理功能实体SMF，所述用户面功能实体为UPF或者；在4G网络下，所述所述会话功能实体为分组数据网关PGW,所述用户面功能实体为网关用户面功能GW-U。
本申请提供的网络还可以应用于终端和用户面功能实体用户面功能实体之间已存在第一传输路径的情况下，再发起建立第二传输路径的情形，此时会话功能实体确定建立终端与用户面功能实体之间的第二传输路径；所述会话功能实体发起建立所述第二传输路径，并可以在第二传输路径建立请求中，指示所述终端或用户面功能实体在所述第一和第二传输路径上传输相同的数据。
其中，所述会话功能实体确定需要建立终端与用户面功能实体之间的第二传输路径的方式，包括：所述会话功能实体接收所述终端或者策略功能实体发送的请求消息，根据所述请求消息确定需要建立终端与用户面功能实体之间的第二传输路径，还可以包括：所述会话功能实体接收用户面功能实体发送的关于所述第一传输路径的通知消息(例如故障通知消息)确定需要建立所述第二传输路径。在已存在第一传输路径的情况下建立第二传输路径的情况，与连接发起时即建立第二传输路径的情况类似，在此不再赘述。
相应的，本申请也提供了提升业务可靠性的方法，因方法实现的流程与以上提供的网络系统描述过程基本一致，不再重复描述。
本申请还提供了一种终端装置，该装置可以是终端，也可以是终端内的芯片。该装置具有实现上述各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一种可能的设计中，当该装置为终端时，终端包括：交互模块和处理模块，所述交互模块用于接收会话功能实体发送的消息，所述消息用于指示所述处理模块在用户面功能实体和终端之间的第一传输路径和第二传输路径上传输相同的数据；所述处理模块用于在所述第一和第二传输路径上传输相同的数据。
本申请还提供了一种会话功能实体，例如SMF，包括决策模块和处理模块，所述决策模块，用于确定建立终端与用户面功能实体之间的第一传输路径和第二传输路径，或者在所述第一传输路径已经存在的情况下，确定建立第二传输路径；所述处理模块，用于发起建立所述第一和第二传输路径，或者在所述第一传输路径已经存在的情况下，发起建立所述第二传输路径；所述处理模块进一步用于指示所述终端或所述用户面功能实体在所述第一和第二传输路径上传输相同的数据。
以上终端和会话功能实体的各功能单元更进一步的功能，可参考方法和系统实施例中的描述，不再展开详细说明，本领域技术人员有能力根据本发明实施例提供的方法和系统描述，灵活的实现上述功能单元的具体功能。
本申请还提供了一种计算机程序产品，当该计算机产品被执行时，其用于执行上述所介绍的终端和网络所执行的方法。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，所述指令用于执行上述所介绍的终端和网络所执行的方法。
附图说明
图1为本发明实施例提升业务可靠性的系统10的架构示意图；
图2为本发明实施例通信设备200的架构示意图；
图3为本发明实施例提高业务可靠性的方法S300流程示意图；
图4为本发明实施例终端和用户面功能实体通过两条传输路径实现数据传输示意图；
图5为本发明实施例收发侧的双发和双收机制示意图；
图6为本发明实施例同时发起建立两条传输路径方法600示意图；
图7为本发明实施例发起建立新的传输路径方法700示意图；
图8A,8B为本发明实施例5G系统架构示意图；
图9为本发明实施例5G场景下同时发起建立两条传输路径方法900信令流程图；
图10为本发明实施例5G场景下同时发起建立两条传输路径方法1000信令流程图；
图11为本发明实施例5G场景下建立新的传输路径方法1100信令流程图；
图12为本发明实施例5G场景下建立新的传输路径方法1200信令流程图；
图13为本发明实施例4G系统架构示意图；
图14为本发明实施例一种会话功能实体1400示意图；
图15为本发明实施例一种装置1500示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能 和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
如图1所示，为本申请实施例提供的提升业务可靠性的系统10的架构示意图。该提升业务可靠性的系统10包括终端101,第一接入设备102，第二接入设备103或者更多的接入设备,还包括核心网中的功能网元,其中包括会话功能实体104和用户面功能实体105，还可以包括策略功能实体106。用户终端101通过第一接入设备102和/或第二接入设备103接入核心网，与核心网进行业务数据传输。第一接入设备102和第二接入设备103都和核心网相连接，核心网通过接入设备，建立和终端101的传输路径。
终端101，用于与接入设备(102,103)交互，建立与核心网用户面功能实体105之间的至少两条传输路径(例如第一传输路径和第二传输路径)；终端101接收会话功能实体104经由所述接入设备(102,103)发送的消息，所述消息指示所述终端可以在第一传输路径和第二传输路径上传输相同的数据。
第一接入设备102和第二接入设备103，用于根据会话功能实体104，用户终端101或者其他接入设备的指示，建立用户终端101和用户面功能实体105之间的数据传输路径；
会话功能实体104，用于决策并发起建立终端101与用户面功能实体105之间的至少两条传输路径；同时指示所述终端101或所述用户面功能实体105在所述至少两条路径上传输相同的数据。
用户面功能实体105，用于给至少两条传输路径分配用户面资源，并在所述至少两条传输路径上传输相同的数据。
策略功能实体106，用于指示或者授权会话功能实体104发起建立终端101和核心网之间的至少两条传输路径，所述至少两条传输路径用于给同一个用户终端传输相同的数据。
其中，第一接入设备102和第二接入设备103中的第一和第二只是逻辑上的区分，具体实现中可以是不同的物理实体,也可以是同一个物理实体,例如,可以是同一个基站。第一接入设备102和第二接入设备103之间，根据不同的实施方式，可以有通信连接，也可以没有通信连接；可以进行信息交互也可以不需要进行信息交互，本发明实施例不做限定。本发明实施例所述的传输路径，是指能够承载业务数据传输的逻辑信道或者数据通路，传输路径的具体实现方式或者建立方法可以有很多种比如5G网络中UE与UPF之间的用户面路径。
系统10可以应用于4G，5G网络以及未来其它的网络，本发明实施例提供的提升业务可靠性的系统10，通过由核心网为同一个终端建立至少两条传输路径,并在至少两条传输路径上分别和终端传输相同的业务数据，从而更好的保证了业务的传输质量，提高了业务可靠性。
图1中的会话功能实体104，终端101或者其他功能实体，均可以通过图2中的通信设备200来实现。通信设备200包括至少一个处理器201，通信总线202，存储器203以及至少一个通信接口204。处理器201可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。通信总线202可包括一通路，在上述组件之间传送信息。通信接口204，使用任何收发器一类的装置，用于与其他设备或通信 网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。存储器203可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。其中，存储器203用于存储执行本申请下述实施例方法的应用程序代码，并由处理器201来控制执行。处理器201用于执行存储器203中存储的应用程序代码，从而实现本申请下述实施例提供的提高业务可靠性的方法。
在具体实现中，作为一种实施例，处理器201可以包括一个或多个CPU，例如图2中的CPU0和CPU1。在具体实现中，作为一种实施例，通信设备200可以包括多个处理器，例如图2中的处理器201和处理器208。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。在具体实现中，作为一种实施例，通信设备200还可以包括输出设备205和输入设备206。输出设备205和处理器401通信，可以以多种方式来显示信息。例如，输出设备405可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备206和处理器201通信，可以以多种方式接受用户的输入。例如，输入设备206可以是鼠标、键盘、触摸屏设备或传感设备等。
基于上述系统10和通信设备200,本申请实施例提供了一种提高业务可靠性的方法S300,通过为同一个终端建立至少两条传输路径,并在至少两条传输路径上分别为终端传输相同的业务数据，从而更好的保证了业务的传输质量，提高了业务可靠性。
S301、核心网确定并发起建立与用户终端之间的至少两条传输路径，所述至少两条传输路径能够同时为所述用户终端传输相同的业务数据；
核心网中的会话功能实体可以自主发起建立，或者根据终端或者策略功能实体的请求，发起建立至少两条终端和核心网用户面功能实体之间的传输路径，例如，终端根据自身配置，业务需求或者网络环境向会话功能实体发送建立主备传输路径请求；或者策略功能实体和/或会话功能实体根据网络状况或者业务属性，或者根据终端发送的提升QoS请求，主动发起建立至少两条传输路径；当然也可以是由终端和核心网各网元配合协商发起，本发明实施例不做限定。
所述至少两条传输路径的建立顺序可以是同时建立，也可以是先后建立，只要实现至少两条传输路径能够同时为同一个用户终端进行相同数据传输即可；至少两条传输路径可以互为主备关系，此时至少两条传输路径可以同时进行相同的业务数据的传输，也可以部分传输路径正在传输业务数据，其他传输路径虽然没有正在进行数据传输，但是处于已经建立并准备好的状态，可以根据核心网、终端的配置或者业务环境的触发，和当前传输路 径一起，同时进行相同业务数据的传输；
所述至少两条传输路径，可以由核心网分别经由不同的接入设备与终端建立，也可以由核心网利用同一个接入设备与终端建立多条传输路径，或者以一个接入设备为锚点，发起建立多个传输路径。由于核心网中的会话功能实体存储有终端的接入类型信息，会话功能实体根据终端的接入信息，可以知道终端在两个接入设备上是否都有控制面连接，如果都有，就是分别和不同的接入设备建立传输路径，如果只有一个有，则通过一个接入设备指示其他接入设备，发起建立多个传输路径。
S302、核心网通过所述至少两条传输路径和终端进行数据传输。
这里的数据传输，可以是至少两条传输路径上同时在进行相同数据的传输，也可以是部分传输路径正在实际传输业务数据，其他传输路径处于已经建立但是并没有实际传输数据的状态，未实际传输数据的传输路径，可以根据核心网和/或终端的配置或者业务环境的触发，开始进行相同业务数据的传输；
从核心网侧来说，核心网可以同时通过所述至少两条传输路径向终端下发相同的业务数据(双发或双播)；也可以同时通过所述至少两条传输路径接收终端发送的相同的业务数据并进行去重处理(双收)；
从终端侧来说，终端通过所述至少两条传输路径接收核心网发送的业务数据并进行去重处理(双收)；也可以同时通过所述至少两条传输路径向核心网发送相同的业务数据(双发或双播)。
下面以两条传输路径为例，对核心网侧和终端侧对数据的发送和接收机制说明如下：
本发明实施例可以通过在用户终端(user equipment,UE)和核心网的用户面功能实体上增加一个协议栈来实现方法S300中描述的双发和双收功能，参考图4所示，可以看到，用户终端和核心网的用户面功能实体通过两条传输路径实现了数据传输，并各自通过协议栈进行了双发和双收处理。其中，NCP为Network Control Protocol，即网络控制协议，第一传输路径(Path1)和第二传输路径(Path2)可以同是3GPP通路，也可以是3GPP和Non-3GPP通路。
图4示意了数据流走向，而收发侧的双发和双收机制，还可以参考图5，可以看到，在用户终端UE处，APP需要发送的报文会通过本地总线等方式发往手机的基带芯片，基带芯片收到上层的业务报文，执行报文复制，并给报文打上序列号和NCP ID，然后通过Path1和Path2发送出去。用户面功能实体侧接收到报文后，去除path1和path2相关的协议头，根据NCP ID和序列号进行去重，然后将数据包发送至数据网络(Data Network,DN)。
从图5的收侧可以看到，第一传输路径(path1)在传输过程中，序号为2的数据包丢失，由于采用了主备传输路径机制，在数据接收的时候，系统可以从第二传输路径中获得丢失的序号为2的数据包，提高了数据接收的质量和可靠性。
对于已经建立好的两条传输路径，例如图5所示，从接收侧来说，也可以根据数据传输质量和/或者链路质量，选择其中一条进行接收(择一方式)，而不必执行去重操作。例如，网络侧或者终端周期性采样监测两条传输路径的数据传输质量，根据质量的动态变化，及时选择传输质量较高或者更加符合当前业务需求(最稳定或者速度最快)的传输路径来接收数据，相比去重的方式，择一的方式可以减轻接收侧的去重处理负担。
本发明实施例的提升业务可靠性的方法，通过为同一个终端建立到核心网的至少两条传输路径，在两条传输路径上能够同时传输相同的业务数据，并进一步通过在收发侧采用 双发和双收机制，实现了高可靠性的数据传输。
下面结合具体的应用场景，以两条传输路径为例进行说明，实施例中两条传输路径称为第一传输路径和第二传输路径，或者称为主传输路径和备份传输路径(主备路径)，本实施例并不限定主备路径和第一第二传输路径的对应关系，即第一或第二传输路径可以互为主备传输路径。
方法S600，参考附图6，同时发起建立两条传输路径步骤介绍如下：
S601.当终端或者核心网的策略功能实体要保证高可靠业务的数据传输时，给会话功能实体发送高可靠性传输路径建立请求；
S602.会话功能实体确定需要建立终端与用户面功能实体之间两条传输路径，即第一传输路径和第二传输路径；
S603.会话功能实体发起第一传输路径和第二传输路径的建立，将两条传输路径的标识以及关联关系通知到接入设备以及用户终端，实现两条传输路径的建立；
具体的，通过接入设备实现两条传输路径的建立，可有两种方式：
第一种：会话功能实体分别通过第一接入设备和第二接入设备，建立第一传输路径和第二传输路径；具体可以包括：
S6031.通知第一接入设备，建立第一传输路径，第一传输路径的建立为现有技术，在此不再赘述；
S6032.通知第二接入设备，通知内容包括：第一传输路径标识，第二传输路径标识，关联标识；建立第二传输路径；
S6033.通知核心网的用户面功能实体，通知内容包括：第一第二传输路径资源，第一第二传输路径标识信息，关联标识，完成两条传输路径的建立。
本实施例由核心网分别发起建立两条传输路径，负责承载两条传输路径的接入设备之间可以没有交互，这种方式既可以实现3GPP接入设备分别承载两条传输路径，也可以实现3GPP和非3GPP接入设备分别承载两条传输路径。需要说明的是，第一接入设备和第二接入设备在实现上可以是同一个接入设备(如同一个基站)，但是从增加可靠性的角度考虑，两个接入设备分别由不同接入设备实现，甚至由3GPP和非3GPP接入设备分别实现，能更好的提升数据传输的可靠性或者鲁棒性。
第二种：核心网通过第一接入设备，通知第二接入设备建立第二传输路径；
S603a.会话功能实体通知第一接入设备与终端交互建立的第一传输路径(此为现有技术，不再赘述)；进一步的，会话功能实体还通知第一接入设备，由该第一接入设备通知第二接入设备和终端交互(交互信息包括第一传输路径标识，第二传输路径标识，备份标识)，建立第二传输路径。
S603b.通知用户面功能实体，通知内容包括：第一第二传输路径资源，第一第二传输路径标识信息，关联标识，完成两条传输路径的建立。
本实施例中，第一接入设备在收到建立第二传输路径的请求后，触发第二接入设备和终端建立所述第二传输路径，这种实施方式对网络改动较小，更容易与现存网络兼容。
会话功能实体通过关联标识，通知所述终端或用户面功能实体将第一和第二传输路径进行关联，所述关联包括：所述用户面功能实体或者终端在所述第一和第二传输路径上分别发送相同的数据；或者，所述用户面功能实体或者终端对从所述第一和第二传输路径上 收到的数据进行去重，或者所述终端从所述第一和第二传输路径中选择一条传输路径来接收数据。
对于终端来说，会话功能实体一般在第二传输路径的建立请求中包含关联标签，通过关联标签(或者备份标签)指示终端将两个传输路径进行关联(或绑定)。
对于核心网侧的用户面功能实体来说，会话功能实体可以在收到第二个传输路径建立完成的响应消息后，通知用户面功能实体将两个传输路径进行关联(或绑定)，具体可以是在通知消息中携带关联标签(或者备份标签)和第一，第二传输路径的标识。
另外，步骤603中，会话功能实体在发起两条传输路径建立时，还可以进一步通知用户面功能实体或者终端开启双发和/或双收功能，具体可以是在会话功能实体发送第一和/或第二传输路径建立通知消息时携带上述开启双发和/或双收功能的指示，本发明实施例不做限定。
S604.如果会话功能实体通知用户面功能实体或者终端进行双发和/或双收，则用户面功能实体或者终端即可以利用已经关联了的第一和第二传输路径分别传输相同的数据。
会话功能实体可以在发起建立第一和第二传输路径的时候即通知用户面功能实体或者终端进行双发和/或双收；也可以在两条传输路径建立好了以后，再根据网络或者业务情况通知用户面功能实体或者终端利用建立好的两条传输路径实际进行双发和/或双收。
通过本发明实施例S600的方法，在初始阶段即在终端和网络侧之间建立两条传输路径用来传输相同的业务数据，提高了数据传输的可靠性。
方法S700：参考附图7，当前终端和核心网用户面功能实体用户面功能实体之间已存在一条传输路径，仍需要建立新的传输路径；
S701.当终端或者网络侧需要提升传输的QoS需求时，给会话功能实体发送QoS提升请求；
具体的，终端此时和网络侧已经存在一条传输路径，或者可选的，已经通过第一传输路径进行业务数据传输了，但由于业务需求变更或者网络状况的变化等情况，需要提升传输质量或者保持传输的质量不下降，因此，需要请求会话功能实体提升QoS。另外，终端或者网络侧网元，如策略功能实体或者用户名功能实体，也可以直接给会话功能实体发送请求，请求建立第二传输路径(备份路径)。
S702.会话功能实体确定需要建立终端与用户面功能实体之间的第二传输路径；
会话功能实体可以根据业务的QoS要求和/或本地网络负载情况决策建立第二传输路径，会话功能实体还可以进一步向策略功能实体请求授权，策略功能实体决策可以为该业务建立第二传输路径，发送响应给会话功能实体。另外，会话功能实体也可以根据收到的第二传输路径建立请求，直接发起建立第二传输路径。
S703.会话功能实体发起第二传输路径的建立，具体的，通过接入设备实现第二传输路径的建立，可以有两种方式：
第一种：第一传输路径已经由核心网通过第一接入设备建立好了，此时核心网通过第二接入设备，建立第二传输路径；
S7031.通知第二接入设备，通知内容包括：第一传输路径标识，第二传输路径标识，关联标识，建立第二传输路径。
S7032.通知用户面功能实体，包括第二传输路径资源，第一路径标识信息，关联 标识，完成用户面功能实体侧第二传输路径建立。
核心网发起建立一条新的传输路径(第二传输路径)，负责承载两条传输路径的接入设备之间可以没有交互，这种方式既可以实现3GPP接入设备分别承载两条传输路径，也可以实现3GPP和非3GPP接入设备分别承载两条传输路径。需要说明的是，第一接入设备和第二接入设备在实现上可以是同一个接入设备(如同一个基站)。
第二种：核心网通过第一接入设备，通知第二接入设备建立第二传输路径；
S703a.通知第一接入设备，包括第一传输路径标识，第二传输路径标识，关联标识。第一接入设备通知终端和第二接入设备，建立第二传输路径(备份路径)；
S703b.通知用户面功能实体UPF，包括第二传输路径资源，第一传输路径标识信息，关联标识，完成用户面功能实体侧第二传输路径的建立；
由第一接入设备在收到建立第二传输路径的请求后，通知终端和第二接入设备建立第二传输路径，对网络改动较小，更容易与现存网络兼容。
会话功能实体可以在发起建立第二传输路径时，通知所述终端或用户面功能实体将第一和第二传输路径进行关联，所述关联包括：所述用户面功能实体或者终端在所述第一和第二传输路径上分别发送相同的数据；或者，所述用户面功能实体或者终端对从所述第一和第二传输路径上收到的数据进行去重，或者从所述第一和第二传输路径中选择一条传输路径来接收数据。
对于终端来说，会话功能实体在第二传输路径的建立请求中包含关联标签，通过关联标签指示终端将两个传输路径进行关联(或绑定)。对于核心网侧的用户面功能实体来说，会话功能实体可以在收到第二传输路径建立完成的响应消息后，通知用户面功能实体将两个传输路径进行关联(或绑定)。
另外，步骤703中，会话功能实体在发起主备传输路径建立时，还可以进一步通知用户面功能实体或者终端开始进行双发和/或双收，具体可以是在会话功能实体发送第二传输路径建立通知消息时携带上述双发和/或双收的指示，本发明实施例不做限定。
S704.如果会话功能实体通知用户面功能实体或者终端进行双发和/或双收，则用户面功能实体或者终端即可以利用已经关联了的第一和第二传输路径分别传输相同的数据。
通过本发明实施例S700的方法，在当前已经存在第一传输路径，或者第一传输路径已经在进行数据传输的情况下，终端或者网络侧根据业务需要或者网络情况变化等，发起建立第二传输路径，可以与第一传输路径一起传输同样的业务数据，从而提高了数据传输的可靠性和灵活性，由于两条传输路径并不需要一开始就同时建立，节省终端和网络侧的处理负担和网络资源，增加了灵活性。
前述提高业务可靠性的系统10,通信装置200，方法S300，图4，图5示意的收发侧的双发和双收机制，方法S600和S700，都可以应用于当前的4G，4.5G或者5G网络以及未来其它的网络中，例如上述的会话功能实体可以是5G中的SMF(Session Management Function,会话管理功能)或者4G中的PGW(PDN Gataway，分组数据网关)：策略功能实体可以是5G中的PCF(Policy Control Function，策略控制功能)或者4G中的PCRF(Policy and Charging Rules Function，策略与计费规则功能)：用户面功能实体可以是5G中的UPF(User Plane Function，用户面功能)或者4G中的GW-U(Gateway User plane function，网关用户面功能)。
前述的系统，通信装置和方法应用于5G网络，可能的适用架构包括图8A和图8B所示的架构。图8A中，UE仅通过3GPP接入设备接入网络，图8B中UE通过3GPP接入设备和Non-3GPP接入设备同时接入网络，需要说明的是图8A和图8B所示的两种架构中，将UE接入网络的接入设备和AMF均有控制面连接存在。
对图8A,8B中涉及的主要网元名称和功能描述简要介绍如下表一所示：
Figure PCTCN2017108396-appb-000001
表一
需要说明的是，QoS流是5G中区分QoS的最小粒度，一个QoS流内，所有的业务流使用相同的转发处理，包括调度策略，队列管理，流量整形，资源配置。要提供不同的QoS处理，需使用不同的QoS流，一条传输路径和一个QoS流对应。
参考图9，是基于图8A,8B的架构基础上的第一和第二传输路径(主备路径)的建立流程，通过在初始阶段即分别建立主备路径，可以确保高可靠性要求的业务(如URLLC业务)除了主路径之外，还可以有一条备份路径可用。实施例900步骤具体说明如下：
S901.主备传输路径建立决策。可以分为以下几种情况：
a.UE发送业务请求至SMF，包含QoS参数，主备路径建立指示(可选)等；SMF根据UE的类型(例如，UE是URLLC终端)，QoS需求等，并参考网络负荷情况，以及主备路径指示标签(可选)，决策为UE的所述业务需求建立主备QoS流。
b.SMF收到UE的业务请求后，还可以进一步向PCF请求授权，即向PCF发送主备路径建立请求，请求消息携带QoS参数，如5QI(5G QoS indicator，5G QoS标签，或者具体QoS需求；PCF根据UE签约信息和QoS参数，决策可以授权SMF为UE建立主备路径，PCF向SMF发送主备路径建立应答消息，所述消息指示SMF可以为UE的所述业务请求建立主备路径。
c.PCF向SMF发送业务请求，包括QoS参数和主备路径指示(可选，PCF收到DN的业务请求后，根据QoS参数和UE签约信息决策需要为该业务建立主备路径，此种情况可以携带主备路径指示标签)等；SMF根据UE的类型(URLLC终端)，QoS需求等，并参考网络负荷情况，以及主备路径指示标签(可选)，决策为UE的所述业务需求建立主备QoS流(或者直接按照PCF的主备路径建立指示为UE建立主备路径)。
S902.SMF发起建立所述主备路径，包括：SMF分配主备QoS流用户面资源，主要包 括主备QoS流的QFI(QoS flow identity，QoS流标识),数据包检测与计费规则等。具体如下：分配主备QoS流对应的QFI等QoS流相关资源{例如，PCC(Policy Charging Control，策略计费控制)规则等}。两条QoS流的计费或者QoS策略可以相同，也可不同(例如可以不再对第二QoS流进行计费)，本实施例不做限制。
SMF此时还可以根据URLLC业务类型和/或终端类型，决策是否通知UPF和/或UE开启双传输(双发和/或双收)功能。
具体包括：
●若URLLC终端为高移动终端(通过QoS参数，业务类型等和终端类型体现)，则表示其网路存在较大不稳定性，SMF在下发主备路径建立通知消息时携带双传输指示通知，指示UPF和UE进行双传输。
●若URLLC终端为低移动终端，则表示其网络路径相对稳定，则只为其建立主备路径，后续在需要时再开启双传输。
S903.SMF给AMF发送主备QoS流创建请求，所述请求消息携带：主备QoS流QFI，PDU Session ID(主备QoS流若位于不同的PDU会话，则需要携带两个PDU Session ID)，TFT，QoS，备份标签，双传输指示(可选)等；
备份标签用于指示两条QoS流之间的关系，可以称为主备关系，关联(associated)关系或者绑定关系，UE或者UPF可以根据该备份标签，确定可以分别在两条QoS流上传输相同的数据。
S904-906.AMF收到SMF发来的主备QoS流建立请求，给第一接入设备发送QoS流建立请求，所述请求消息携带PDU Session ID，和QoS规则等；第一接入设备收到QoS流建立请求时，将QoS规则映射为radio QoS规则，发送无线重配置信息给UE，完成第一QoS流建立；第一接入设备给AMF发送QoS流建立应答消息，通知AMF，第一QoS流无线侧建立完成；
S907.AMF发起备份QoS建立流程。AMF给第二接入设备发送QoS流创建请求消息，所述请求消息携带：第一QoS流QFI，PDU Session ID，第二QoS流QFI，PDU Session ID(可与第一QoS流所在的PDU Session ID相同，也可不同，不做限制)，备份标签，双传输指示(可选)，QoS等；
S908.第二接入设备收到备份QoS流创建请求，将QoS规则映射为radio QoS规则，发送无线重配置信息给UE，完成第二QoS流建立；
需要说明的是，第一和第二QoS流的建立顺序可以不受限制。
UE侧根据备份标签和第一QoS流标识(QFI，PDU Session ID)和第二QoS流标识(PDU Session ID，QFI)，完成两个QoS流的绑定(或关联)，具体的，将即将建立的第二QoS流绑定之已经存在的第一QoS流，完成主备路径的关联。可选的，如果所述重配置消息中包含双传输指示，UE开启双传输，具体实现可以参考附图4，图5中的方式，例如：
●上行双发。UE执行数据包复制，将第一QoS流数据本地复制一份，将原数据包通过第一QoS流所对应的无线承载发送至第一接入设备。将复制后的数据包通过第二QoS流所在的无线承载发送至第二接入设备。UE为第一QoS流和第二QoS流的数据包添加双传输协议头，协议头携带包序号，标识等。UPF通过解析双传输协议头，可以实现去重操作。
●下行双收。UE收到第一接入设备发来的第一QoS流相对应的数据包和第二接 入设备发来的第二QoS流相对应的数据包，根据数据包中的双传输协议头信息(主要包含序列号和标识等)进行数据包去重。
S909.第二接入设备给AMF发送QoS流建立应答消息，通知AMF，第二QoS流无线侧建立完成。
S910.AMF向SMF发送主备QoS流建立应答消息；
该消息包括：第一QoS流标识和第二QoS流标识等。
S911.SMF通知UPF，建立第一和第二QoS流UPF侧用户面资源。
具体的，SMF分配资源(隧道，以及SMF从别处获得的计费QoS规则)，发给UPF，UPF存储/安装这些规则，实现用户面资源的建立。
此外，SMF向UPF发送N4会话修改消息，该消息携带以下内容：
a.第一QoS流标识和第二QoS流标识，备份标签。UPF侧根据备份标签和第一QoS流标识(QFI，PDU Session ID)和第二QoS流标识(PDU Session ID，QFI)。完成两个QoS流的绑定，即完成主备路径的关联。
b.双传输指示(可选)。根据该指示，参考附图4，图5，UPF执行如下动作：
b1.下行双发。UPF收到DN发来的与第一QoS流相对应的数据包时，执行数据包复制，将原数据包通过第一QoS流所在的N3隧道发送至第一接入设备。将复制后的数据包通过第二QoS流所在的N3隧道发送至第二接入设备。UPF为第一QoS流和第二QoS流的数据包添加双传输协议头，协议头携带包序号，标识等。UE通过解析双传输协议头，可以实现去重操作；
b2.上行双收。UPF收到第一接入设备发来的第一QoS流相对应的数据包和第二接入设备发来的第二QoS流相对应的数据包，根据数据包中的双传输协议头信息(主要包含序列号和标识等)进行数据包去重。
c.其他PCC规则，UPF建立第二QoS流相关的策略计费规则等。
UPF向SMF发送N4会话修改应答消息，完成UPF侧主备QoS流用户面资源的创建。
本实施例通过网络侧识别到URLLC业务，进而为该业务建立主备两条路径来进行业务传输的质量提升和差错情况下的可靠性保障，且实施例中两个接入设备之间没有通信需求，能够实现UE同时通过3GPP与Non-3GPP混合接入的场景，实现传输效益的最大化。
参考图8A的架构和附图10，为初始阶段即建立主备路径(即第一传输路径和第二传输路径)的另一个实施例1000流程示意图，本实施例中第一接入设备和第二接入设备之间有通信接口，UE可以通过第一接入设备和第二接入设备建立同一个PDU会话，其中UE的控制面上下文位于第一接入设备，即AMF与第一接入设备存在信令面连接。下面对该实施例1000说明如下；
S1001.主备传输路径建立决策，具体可以参考前述实施例步骤S901；
S1002.SMF发起建立所述主备路径,具体可以参考前述实施例步骤S902；
S1003.SMF给AMF发送主备QoS流创建请求，所述请求消息携带：
第一QoS流QFI，第二QoS流QFI，PDU Session ID(主备QoS流位于同一个PDU会话)，TFT，QoS，备份标签，双传输指示(可选)等；
S1004.AMF收到SMF发来的主备QoS流建立请求，给第一接入设备发送主备QoS流建立请求，所述请求消息携带PDU Session ID，第一QoS流QFI，第二QoS流QFI,QoS规 则，备份标签，双传输指示(可选)等；
S1005.第一接入设备发起第二接入设备添加流程(参考现有技术中主基站发起辅助基站添加流程，详细可参照3GPP标准TS36.300)；
第一接入设备向第二接入设备发送QoS流建立请求消息，所述请求消息携带第二QoS流QFI，UPF侧第一隧道信息，PDU Session ID，QoS规则等。
S1006.第二接入设备为第二QoS流分配无线资源信息，并将所分配的无线资源信息发送给第一接入设备
S1007.第一接入设备通知UE建立第一QoS流和第二QoS流，所述通知消息包括：
●第一QoS流标识，第二QoS流标识，PDU Session ID，备份标签。UE根据这些信息实现建立第一QoS流和第二QoS流的主备关系，完成主备路径的关联。
●双传输指示(可选)，指示UE执行双收双发。
●第一接入设备为第一QoS流分配的无线资源信息，UE根据这些无线资源信息，向第一接入设备发起无线重配置消息，完成第一QoS流的建立。
●第二接入设备为第二QoS流分配的无线资源信息，UE根据这些无线资源信息，向第二接入设备发起无线重配置消息，完成第二QoS流的建立。
S1008.UE向第一接入设备发起无线重配置信息，完成第一QoS流的建立；
S1009.UE向第二接入设备发起无线重配置信息，完成第二QoS流的建立
S1010.第一接入设备向AMF发送QoS流建立应答消息，所述应答消息携带第一QoS流和第二QoS流的QFI，PDU Session ID等；
S1011.AMF向SMF发送主备QoS流建立应答消息；
该消息包括：第一QoS流标识和第二QoS流标识等。
S1012.SMF通知UPF，建立第一，第二QoS流UPF侧用户面资源；
具体的，SMF分配资源(隧道，以及SMF从别处获得的计费QoS规则)，发给UPF，UPF存储/安装这些规则，实现用户面资源的建立。
此外，SMF向UPF发送N4会话修改消息，该消息携带以下内容：
a.第一QoS流标识和第二QoS流标识，备份标签。UPF侧根据备份标签和第一QoS流标识(QFI，PDU Session ID)和第二QoS流标识(PDU Session ID，QFI)。完成两个QoS流的绑定，即完成主备路径的关联。
b.双传输指示(可选)。根据该指示，参考附图4,图5，UPF执行如下动作：
b1.下行双发。UPF收到DN发来的与第一QoS流相对应的数据包时，执行数据包复制，将原数据包通过第一QoS流所在的N3隧道发送至第一接入设备。将复制后的数据包通过第二QoS流所在的N3隧道发送至第二接入设备。UPF为第一QoS流和第二QoS流的数据包添加双传输协议头，协议头携带包序号，标识等。UE通过解析双传输协议头，可以实现去重操作。
b2.上行双收。UPF收到第一接入设备发来的第一QoS流相对应的数据包和第二接入设备发来的第二QoS流相对应的数据包，根据数据包中的双传输协议头信息(主要包含序列号和标识等)进行数据包去重。
c.其他PCC规则，UPF建立第二QoS流相关的策略计费规则等。
UPF向SMF发送N4会话修改应答消息，完成UPF侧主备QoS流用户面资源的创建。
本实施例中两个接入设备之间通过交互实现两个传输路径的建立，核心网可以只给一 个接入设备发送主备传输路径建立请求即可以实现主备传输路径的建立。由于对于同一种接入技术，现有核心网一般只允许其中一个接入设备与AMF有控制面连接(如主基站和辅基站机制)，本实施例的方案对网络改动较小，更容易与现网兼容。
参考图11，是基于图8A,8B的架构，核心网在当前已经存在第一传输路径基础上，发起建立第二传输路径的建立流程。实施例1100步骤具体说明如下：
S1101.第二传输路径建立决策。可以分为以下几种情况：
a.UE发送QoS提升请求或者链路故障通知至SMF，包含QoS参数,链路故障通知，备份路径建立指示(可选，可能性很小)等；SMF根据UE的类型(URLLC终端)，QoS提升需求等，并参考网络负荷情况，以及备份路径指示标签(可选)，决策为UE的所述请求建立备份QoS流；
b.SMF收到UE的QoS提升请求或者链路故障通知后，还可以进一步向PCF请求授权，即向PCF发送备份路径建立请求，请求消息携带QoS参数(如5QI或者具体QoS需求)，PCF根据UE签约信息和QoS参数，决策可以授权SMF为UE建立备份路径，向SMF发送主备路径建立应答消息，所述消息指示SMF可以为UE的所述请求建立备份QoS流；
c.PCF向SMF发送业务请求，包括QoS参数和备份标签(可选，PCF收到DN的业务请求后，根据QoS参数和UE签约信息决策需要为该业务建立主备路径，此种情况可以携带备份标签)，同时PCF还可以在业务请求中携带原QoS流的QFI和PDU Session ID等；SMF根据UE的类型(URLLC终端)，QoS需求等，并参考网络负荷情况，以及备份标签(可选)以及原QoS流标识，决策建立备份QoS流(或者按照PCF的主备建立指示，级前述备份标签，为UE建立主备路径)；
d.UPF感知到链路质量发生恶化，例如低于预设值，通知SMF，携带PDU Session ID，QFI等；SMF根据UE的类型(URLLC终端)，QoS提升需求等，并参考网络负荷情况，以及备份路径指示标签(可选)，决策为UE的所述请求建立备份QoS流；
e.UPF感知到链路质量发生恶化，通知SMF；SMF根据UE的类型(URLLC终端)，QoS提升需求等，并参考网络负荷情况，以及备份路径指示标签(可选)，决策需要为UE的所述请求建立备份QoS流；SMF向PCF发送备份路径建立请求，请求消息携带QoS参数(如5QI或者具体QoS需求)；PCF根据UE签约信息和QoS参数，决策可以授权SMF为UE建立备份路径，PCF向SMF发送主备路径建立应答消息，所述消息指示SMF可以为UE的所述请求建立备份QoS流。
S1102.SMF发起建立备份路径，包括：SMF分配备份QoS流用户面资源，主要包括主备QoS流的QFI,数据包检测与计费规则等。具体如下：分配备份QoS流对应的QFI等QoS流相关资源{例如，PCC(Policy Charging Control，策略计费控制)规则等}。备份QoS流的计费或者QoS策略可以和主QoS流相同，也可不同(例如可以不再对备份QoS流进行计费)，本实施例不做限制。
SMF此时还可以根据URLLC业务类型和/或终端类型，决策是否通知UPF和/或UE开启双传输(双发和/或双收)功能。
具体包括：
●若URLLC终端为高移动终端(通过QoS参数，业务类型等和终端类型体现)， 则表示其网路存在较大不稳定性，SMF在下发备份路径建立通知消息时携带双传输指示通知，指示UPF和UE进行双传输。
●若URLLC终端为低移动终端，则表示其网络路径相对稳定，则可以只为其建立备份路径，后续在需要时再开启双传输。
S1103.SMF给AMF发送备份QoS流创建请求，所述请求消息携带：主备QoS流QFI，PDU Session ID(主备QoS流若位于不同的PDU会话，则需要携带两个PDU Session ID)，TFT，QoS，备份标签，双传输指示(可选)等；
备份标签用于指示两条QoS流之间的关系，可以称为主备关系，关联(associated)关系或者绑定关系，UE或者UPF可以根据该备份标签，确定可以分别在两条QoS流上传输相同的数据。
S1104.AMF发起备份QoS建立流程。AMF给第二接入设备发送QoS流创建请求消息，所述请求消息携带：第一QoS流QFI，PDU Session ID，第二QoS流QFI，PDU Session ID(可与第一QoS流所在的PDU Session ID相同，也可不同，不做限制)，备份标签，双传输指示(可选)，QoS等；
S1105.第二接入设备收到备份QoS流创建请求，将QoS规则映射为radio QoS规则，发送无线重配置信息给UE，完成第二QoS流建立；
UE侧根据备份标签和第一QoS流标识(QFI，PDU Session ID)和第二QoS流标识(PDU Session ID，QFI)，完成两个QoS流的绑定(或关联)，具体的，将即将建立的第二QoS流绑定之已经存在的第一QoS流，完成主备路径的关联。可选的，如果所述重配置消息中包含双传输指示，UE开启双传输，参考附图4，图5，具体实现如下：
●上行双发。UE执行数据包复制，将第一QoS流数据本地复制一份，将原数据包通过第一QoS流所对应的无线承载发送至第一接入设备。将复制后的数据包通过第二QoS流所在的无线承载发送至第二接入设备。UE为第一QoS流和第二QoS流的数据包添加双传输协议头，协议头携带包序号，标识等。UPF通过解析双传输协议头，可以实现去重操作。
●下行双收。UE收到第一接入设备发来的第一QoS流相对应的数据包和第二接入设备发来的第二QoS流相对应的数据包，根据数据包中的双传输协议头信息(主要包含序列号和标识等)进行数据包去重
S1106.第二接入设备给AMF发送QoS流建立应答消息，通知AMF，第二QoS流无线侧建立完成。
S1107.AMF向SMF发送主备QoS流建立应答消息；
该消息包括：第一QoS流标识和第二QoS流标识等。
S1108.SMF通知UPF，建立第二QoS流UPF侧用户面资源。
SMF向UPF发送N4会话修改消息，该消息携带以下内容：
a.第一QoS流标识和第二QoS流标识，备份标签。UPF侧根据备份标签和第一QoS流标识(QFI，PDU Session ID)和第二QoS流标识(PDU Session ID，QFI)。完成两个QoS流的绑定，即完成主备路径的关联。
b.双传输指示(可选)。根据该指示，参考附图4，图5，UPF执行如下动作：
b1.下行双发。UPF收到DN发来的与第一QoS流相对应的数据包时，执行数据包复制，将原数据包通过第一QoS流所在的N3隧道发送至第一接入设备。 将复制后的数据包通过第二QoS流所在的N3隧道发送至第二接入设备。UPF为第一QoS流和第二QoS流的数据包添加双传输协议头，协议头携带包序号，标识等。UE通过解析双传输协议头，可以实现去重操作；
b2.上行双收。UPF收到第一接入设备发来的第一QoS流相对应的数据包和第二接入设备发来的第二QoS流相对应的数据包，根据数据包中的双传输协议头信息(主要包含序列号和标识等)进行数据包去重。
c.其他PCC规则，UPF建立第二QoS流相关的策略计费规则等。
UPF向SMF发送N4会话修改应答消息，完成UPF侧备份QoS流用户面资源的创建。
本实施例中，核心网发起建立一条新的传输路径(第二传输路径)，负责承载两条传输路径的接入设备之间可以没有交互，这种方式既可以实现3GPP接入设备分别承载两条传输路径，也可以实现3GPP和非3GPP接入设备分别承载两条传输路径。需要说明的是，第一接入设备和第二接入设备在实现上可以是同一个接入设备(如同一个基站)。
参考图12，是基于图8A的架构，核心网在当前已经存在第一传输路径基础上，发起建立第二传输路径的建立流程。实施例1200步骤具体说明如下：
S1201.主备传输路径建立决策，具体可以参考前述实施例步骤S1101；
S1202.SMF发起建立备份路径,具体可以参考前述实施例步骤S1102；
S1203.SMF给AMF发送第二QoS流创建请求，所述请求消息携带:第一QoS流QFI，第二QoS流QFI，PDU Session ID(主备QoS流位于同一个PDU会话)，TFT，QoS，备份标签，双传输指示(可选)等；
S1204.AMF收到SMF发来的第二(备份)QoS流建立请求，向第一接入设备发送备份QoS流建立请求，所述请求消息携带PDU Session ID，第一QoS流QFI，第二QoS流QFI,QoS规则，备份标签，双传输指示(可选)等.所述请求消息用于指示第一接入设备，在第二接入设备和UE之间建立备份QoS流。
S1205.第一接入设备发起第二接入设备添加流程(参考现有技术，主基站发起辅助基站添加流程，详细可参照TS36.300)；
第一接入设备向第二接入设备发送QoS建立请求消息，所述请求消息携带第二QoS流QFI，PDU Session ID，QoS规则等。
S1206.第二接入设备为第二QoS流分配无线资源信息，并将所分配的无线资源信息发送给第一接入设备
S1207.第一接入设备通知UE建立第二QoS流，所述通知消息包括：
●第一QoS流标识，第二QoS流标识，PDU Session ID，备份标签。UE根据这些信息实现建立第一QoS流和第二QoS流的主备关系，完成主备路径的关联。
●双传输指示(可选)，指示UE执行双收双发。
●第二接入设备为第二QoS流分配的无线资源信息，UE根据这些无线资源信息，可完成第二QoS流的建立
S1208.UE向第二接入设备发起无线重配置信息，完成第二QoS流的建立；
S1209.第一接入设备向AMF发送QoS流建立应答消息；
S1210.AMF向SMF发送主备QoS流建立应答消息；
S1211.SMF通知UPF，建立第二QoS流UPF侧用户面资源；
具体的，SMF分配资源(隧道，以及SMF从别处获得的计费QoS规则)，发给UPF，UPF存储/安装这些规则，实现用户面资源的建立。
此外，SMF向UPF发送N4会话修改消息，该消息携带以下内容：
a.第一QoS流标识和第二QoS流标识，备份标签。UPF侧根据备份标签和第一QoS流标识(QFI，PDU Session ID)和第二QoS流标识(PDU Session ID，QFI)。完成两个QoS流的绑定，完成主备路径的关联
b.双传输指示(可选)。根据该指示，参考附图4，图5，UPF执行如下动作：
b1.下行双发。UPF收到DN发来的与第一QoS流相对应的数据包时，执行数据包复制，将原数据包通过第一QoS流所在的N3隧道发送至第一接入设备。将复制后的数据包通过第二QoS流所在的N3隧道发送至第二接入设备。UPF为第一QoS流和第二QoS流的数据包添加双传输协议头，协议头携带包序号，标识等。UE通过解析双传输协议头，可以实现去重操作。
b2.上行双收。UPF收到第一接入设备发来的第一QoS流相对应的数据包和第二接入设备发来的第二QoS流相对应的数据包，根据数据包中的双传输协议头信息(主要包含序列号和标识等)进行数据包去重。
c.其他PCC规则，UPF建立第二QoS流相关的策略计费规则等。
UPF向SMF发送N4会话修改应答消息，完成UPF侧主备QoS流用户面资源的创建。
本实施例核心网通过第一接入设备通知第二接入设备和UE来进行第二传输路径的建立。由于对于同一种接入技术，现有核心网一般只允许其中一个接入设备与AMF有控制面连接(如主基站和辅基站机制)，本实施例的方案对网络改动较小，更容易与现网兼容。
本发明前述实施例中的方法还可以应用于目前的4G网络，一种可能的适用架构为图13所示的架构，图13中，UE通过3GPP接入设备(E-UTRAN)接入核心网；UE在4G中也可以通过3GPP接入设备和Non-3GPP接入设备同时接入网络，只要将UE接入网络的接入设备与MME之间均有控制面连接存在即可。对图13中涉及的网元名称和功能描述如下表二所示：
Figure PCTCN2017108396-appb-000002
表二
参考前述实施例S900，S1000，S1100和S1200的方法流程，本发明在4G网络中实施的时候，由PGW网元执行SMF在本发明前述实施例中相应的功能；MME网元执行AMF在本发明前述实施例中相应的功能；PCRF执行PCF本发明前述实施例中相应的功能，其他相关 的网元，也可以类似的参照前述实施例实施，这里不再赘述。
在4G中，承载(bearer)是区分QoS的最小粒度，一个承载内，所有的业务流使用相同的转发处理，包括调度策略，队列管理，流量整形，资源配置等；要提供不同的QoS处理，需使用不同的承载，因此在4G中，一条传输路径和一个承载对应。
以上分别就本发明方案在5G和4G网络架构下的实施进行了说明。前述所有实施例中的终端(Terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)等。
接入设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非3GPP接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
上述所有实施例中，涉及SMF实体，PGW的动作可以由图2所示的通信设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本申请实施例对此不作任何限制。涉及终端的动作也可以由图2所示的通信设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
以上主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述会话功能实体或者终端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对会话功能实体或者终端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，图14示出了前述所有实施例中所涉及的会话功能实体1400的一种可能的结构示意图。该会话功能实体包括决策模块1401和处理模块1402。决策模块1401用于确定建立终端与用户面功能实体之间的第一传输路径和第二传输路径，或者在所述第一传输路径已经存在的情况下，确定建立第二传输路径；处理模块1402，用于发起建立所述第一和第二传输路径，或者在所述第一传输路径已经存在的情况下，发起建立所述第二传输路径；所述处理模块1402进一步用于指示所述终端或所述用户面功能实体在所述第一和第二传输路径上传输相同的数据。
可选的，会话功能实体还进一步包括通知模块1403，所述通知模块1403用于在所述 处理模块1402发起建立所述第二传输路径时，通知所述用户面功能实体和/或终端在所述第一和第二传输路径开始传输相同的数据；或者在所述第二传输路径建立后完成后，根据终端或者网络侧请求，通知所述用户面功能实体和/或终端在所述第一和第二传输路径上开始传输相同的数据，具体的双传输处理方式，可以参考前述实施例和附图4和附图5中的内容。
可选的，决策模块1401根据所述终端或者策略功能实体发送的业务请求，获取业务QoS信息，根据所述QoS信息确定需要建立终端与用户面功能实体之间的所述第一和第二传输路径；或者，所述决策模块1401根据所述终端发送的业务请求中携带的主备传输路径建立指示或者双播指示，向策略功能实体请求授权，根据所述授权结果确定需要建立终端与用户面功能实体之间的第一和第二传输路径；
可选的，决策模块1401接收所述终端或者策略功能实体发送的请求消息，根据所述请求消息确定需要建立终端与用户面功能实体之间的第二传输路径；或者，所述决策模块1401接收用户面功能实体发送的关于所述第一传输路径的通知消息，根据所述通知消息，确定需要建立所述第二传输路径，例如，所述通知消息可以是第一传输路径故障通知消息。
可选的，处理模块1402给移动性管理实体发送所述第一和第二传输路径建立请求，通知所述移动性管理实体根据所述第一和第二传输路径建立请求，分别指示第一接入设备和第二接入设备与所述终端协商建立所述第一和第二传输路径。
其中，会话功能实体可以是SMF或者PGW,前述所有实施例涉及的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图15示出了前述所有实施例中所涉及的终端的一种可能的装置结构示意图，该装置1500可以是终端，也可以是终端内的芯片，本申请实施例对此不做具体限定。其中，该装置1500包括：交互模块1501和处理模块1502。其中，交互模块1501用于接收会话功能实体发送的消息，所述消息指示所述终端设备在用户面功能实体和终端之间第一传输路径和第二传输路径上传输相同的数据；处理模块1502用于在所述第一和第二传输路径上传输相同的数据。
可选的，交互模块1501进一步用于发送业务请求给会话功能实体，所述业务请求中携带建立至少两条传输路径，或者建立第二传输路径的指示。
可选的，所述交互模块1501与第一接入设备和第二接入设备分别协商建立所述第一传输路径和第二传输路径。
可选的，所述处理模块1502在所述第一和第二传输路径上传输相同的数据，参考前述实施例和附图4和图5，包括：所述处理模块1502在所述第一和第二传输路径上发送相同的数据给所述用户面功能实体用户面功能实体；或者，所述处理模块1502从所述第一和第二传输路径上接收所述用户面功能实体用户面功能实体发送的相同的数据并对所述接收的数据去重，或者所述处理模块1502从所述第一和第二传输路径中选择一条传输路径来接收数据。
可选的，当该装置1500是芯片时，那么交互模块1501的功能/实现过程还可以通过管脚或电路等来实现。
其中，前述所有实施例涉及的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
由于本申请实施例提供的会话功能实体1400和装置1500用于执行前述所有提高业务可靠性的方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (34)

  1. 一种终端设备，其特征在于，所述终端设备包括交互模块和处理模块，
    所述交互模块用于接收会话功能实体发送的消息，所述消息用于指示所述处理模块在用户面功能实体和终端之间的第一传输路径和第二传输路径上传输相同的数据；
    所述处理模块用于在所述第一和第二传输路径上传输相同的数据。
  2. 如权利要求1中所述的终端设备，其特征在于，所述交互模块进一步用于发送业务请求给所述会话功能实体，所述业务请求中携带建立两条传输路径，或者建立第二传输路径的指示。
  3. 如权利要求1或者2中所述的终端设备，其特征在于，所述交互模块与第一接入设备和第二接入设备分别协商建立所述第一传输路径和第二传输路径。
  4. 如权利要求1-3任一项所述的终端设备，其特征在于，所述处理模块在所述第一和第二传输路径上传输相同的数据，包括：所述处理模块在所述第一传输路径和第二传输路径上发送相同的数据给所述用户面功能实体；或者，所述处理模块从所述第一传输路径和第二传输路径上接收所述用户面功能实体发送的相同的数据并对所述接收的数据去重。
  5. 如权利要求1-3任一项所述的终端设备，其特征在于，所述处理模块在所述第一和第二传输路径上传输相同的数据，包括：所述处理模块在所述第一传输路径和第二传输路径上发送相同的数据给所述用户面功能实体；或者，所述处理模块从所述第一传输路径和第二传输路径中选择一条传输路径接收所述用户面功能实体发送的数据。
  6. 一种会话功能实体，其特征在于，包括决策模块和处理模块，
    所述决策模块，用于确定建立终端与用户面功能实体之间的第一传输路径和第二传输路径，或者在所述第一传输路径已经存在的情况下，确定建立第二传输路径；
    所述处理模块，用于发起建立所述第一和第二传输路径，或者在所述第一传输路径已经存在的情况下，发起建立所述第二传输路径；所述处理模块进一步用于指示所述终端或所述用户面功能实体在所述第一和第二传输路径上传输相同的数据。
  7. 如权利要求6中所述的会话功能实体，其特征在于，所述会话功能实体还进一步包括通知模块，所述通知模块用于在所述处理模块发起建立所述第二传输路径时，通知所述用户面功能实体和/或终端在所述第一和第二传输路径开始传输相同的数据；或者在所述第二传输路径建立后完成后，根据终端或者网络侧请求，通知所述用户面功能实体和/或终端在所述第一和第二传输路径上开始传输相同的数据。
  8. 如权利要求6或者7中所述的会话功能实体，其特征在于，
    所述决策模块用于确定建立终端与用户面功能实体之间的第一传输路径和第二传输路径，包括：所述决策模块根据所述终端或者策略功能实体发送的业务请求，获取业务QoS(Quality of Service，服务质量)信息，根据所述QoS信息确定需要建立终端与用户面功能实体之间的所述第一和第二传输路径；或者，所述决策模块根据所述终端发送的业务请求中携带的主备传输路径建立指示或者双播指示，向策略功能实体请求授权，根据所述授权结果确定需要建立终端与用户面功能实体之间的第一和第二传输路径；
    所述决策模块用于在所述第一传输路径已经存在的情况下，确定建立第二传输路径，包括：所述决策模块接收所述终端或者策略功能实体发送的请求消息，根据所述请求消息确定需要建立终端与用户面功能实体之间的第二传输路径；或者，所述决策模块接收用户面功能实体发送的关于所述第一传输路径的通知消息，根据所述通知消息，确定需要建立 所述第二传输路径。
  9. 如权利要求6-8中任一项所述的会话功能实体，其特征在于，所述处理模块用于发起建立所述第一和第二传输路径；包括
    所述处理模块给移动性管理实体发送所述第一和第二传输路径建立请求，通知所述移动性管理实体根据所述第一和第二传输路径建立请求，分别指示第一接入设备和第二接入设备与所述终端协商建立所述第一和第二传输路径。
  10. 一种提升业务可靠性的网络，其特征在于，所述网络包括会话功能实体和用户面功能实体，
    所述会话功能实体用于决策并发起建立终端与所述用户面功能实体之间的至少两条传输路径，并指示所述终端或所述用户面功能实体在所述至少两条路径上传输相同的数据；
    所述用户面功能实体用于根据所述会话功能实体的所述指示，给所述至少两条传输路径分配用户面资源，并在所述至少两条传输路径上与所述终端传输相同的数据。
  11. 如权利要求10中所述的网络，其特征在于，还包括策略功能实体，用于授权所述会话功能实体发起建立所述终端和用户面功能实体之间的至少两条传输路径，所述至少两条传输路径用于给同一个用户终端传输相同的数据。
  12. 一种提升业务可靠性的方法，其特征在于，所述方法包括：
    会话功能实体确定建立终端与用户面功能实体之间的第一传输路径和第二传输路径；
    所述会话功能实体发起建立所述第一和第二传输路径；
    所述会话功能实体指示所述终端或所述用户面功能实体在所述第一和第二传输路径上传输相同的数据。
  13. 如权利要求12中所述的方法，其特征在于，所述会话功能实体确定建立终端与用户面功能实体之间的第一传输路径和第二传输路径，包括：
    所述会话功能实体根据所述终端或者策略功能实体发送的业务请求，获取业务QoS信息，根据所述QoS信息确定需要建立终端与用户面功能实体之间的所述第一和第二传输路径；或者
    所述会话功能实体根据所述终端发送的业务请求中携带的主备传输路径建立指示或者双播指示，向策略功能实体请求授权，根据所述授权结果确定需要建立终端与用户面功能实体之间的第一和第二传输路径。
  14. 如权利要求12或13所述的方法，其特征在于，所述会话功能实体发起建立所述第一和第二传输路径，还进一步包括：
    所述会话功能实体在发起建立所述第一和第二传输路径时，通知所述用户面功能实体和/或终端通过所述建立好的第一和第二传输路径开始传输相同的数据。
  15. 如权利要求12或13所述的方法，其特征在于，所述方法进一步包括：
    所述会话功能实体在所述第一和第二传输路径建立后完成后，通知所述用户面功能实体和/或终端在所述第一和第二传输路径上开始传输相同的数据。
  16. 如权利要求12-15中任一项所述的方法，其特征在于，所述会话功能实体发起建立所述第一和第二传输路径；包括：
    所述会话功能实体给移动性管理实体发送所述第一和第二传输路径建立请求，通知所述移动性管理实体根据所述第一和第二传输路径建立请求，分别指示第一接入设备和第二接入设备与所述终端协商建立所述第一和第二传输路径。
  17. 如权利要求12-15中任一项所述的方法，其特征在于，所述会话功能实体发起建立所述第一和第二传输路径；包括
    所述会话功能实体给移动性管理实体发送所述第一和第二传输路径建立请求；
    所述移动性管理实体根据所述第一和第二传输路径建立请求，指示第一接入设备建立所述第一传输路径，并指示所述第一接入设备通知第二接入设备建立所述第二传输路径。
  18. 如权利要求12-17中任一项所述方法，其特征在于，所述会话功能实体指示所述终端或用户面功能实体在所述第一和第二传输路径上传输相同的数据，包括：所述会话功能实体给所述终端或者用户面功能实体用户面功能实体发送关联标识，所述关联标识指示所述终端或用户面功能实体在所述第一和第二传输路径上传输相同的数据。
  19. 如权利要求12-18中任一项所述的方法，其特征在于，所述终端或所述用户面功能实体在所述第一和第二传输路径上传输相同的数据，包括：所述用户面功能实体或者终端在所述第一和第二传输路径上发送相同的数据；或者，所述用户面功能实体或者终端从所述第一和第二传输路径上接收相同的数据并对所述接收的数据去重。
  20. 如权利要求12-19中任一项所述的方法，其特征在于，
    所述会话功能实体为会话管理功能实体SMF，所述用户面功能实体为UPF或者；
    所述所述会话功能实体为分组数据网关PGW,所述用户面功能实体为网关用户面功能GW-U。
  21. 一种提升业务可靠性的方法，应用于终端和用户面功能实体用户面功能实体之间已存在第一传输路径的通信网络中，其特征在于，所述方法包括：
    会话功能实体确定建立终端与用户面功能实体之间的第二传输路径；
    所述会话功能实体发起建立所述第二传输路径，并指示所述终端或用户面功能实体在所述第一和第二传输路径上传输相同的数据。
  22. 如权利要求21中的方法，其特征在于，所述会话功能实体确定需要建立终端与用户面功能实体之间的第二传输路径，包括：
    所述会话功能实体接收所述终端或者策略功能实体发送的请求消息，根据所述请求消息确定需要建立终端与用户面功能实体之间的第二传输路径。
  23. 如权利要求21中所述的方法，其特征在于，所述会话功能实体确定需要建立所述第二传输路径，具体包括：
    所述会话功能实体接收用户面功能实体发送的关于所述第一传输路径的通知消息，根据所述通知消息，确定需要建立所述第二传输路径。
  24. 如权利要求21-23任一项所述的方法，其特征在于，所述第一传输路径通过第一接入设备建立；所述会话功能实体发起建立第二传输路径包括：
    所述会话功能实体给移动性管理实体发送所述第二传输路径创建请求；
    所述移动性管理实体根据所述第二传输路径创建请求，指示第二接入设备与所述终端协商建立所述第二传输路径。
  25. 如权利要求21-23任一项所述的方法，其特征在于，所述第一传输路径通过第一接入设备建立；所述会话功能实体发起建立第二传输路径；包括：
    所述会话功能实体给移动性管理实体发送所述第二传输路径创建请求；
    所述移动性管理实体根据所述第二传输路径创建请求，指示所述第一接入设备通知第二接入设备建立所述第二传输路径。
  26. 如权利要求21-25任一项所述的方法，其特征在于，所述会话功能实体发起建立第二传输路径，还进一步包括：
    所述会话功能实体在发起建立所述第二传输路径时，通知用户面功能实体和/或终端，在所述第二传输路径建立后完成后，开始通过所述建立的第二传输路径传输与所述第一传输路径相同的数据。
  27. 如权利要求21-25任一项所述的方法，其特征在于，所述方法进一步包括：
    所述会话功能实体在所述第二传输路径建立后完成后，通知所述用户面功能实体和/或终端开始在所述第二传输路径传输相同数据。
  28. 如权利要求21-27任一项所述的方法，其特征在于，所述终端或所述用户面功能实体在所述第一和第二传输路径上传输相同的数据，包括：所述用户面功能实体或者终端在所述第一和第二传输路径上发送相同的数据；或者，所述用户面功能实体或者终端从所述第一和第二传输路径上接收相同的数据并对所述接收的数据去重。
  29. 如权利要求21-28中任一项所述的方法，其特征在于，
    所述会话功能实体为会话管理功能实体SMF,所述用户面功能实体为UPF,或者；
    所述所述会话功能实体分组数据网关PGW,所述用户面功能实体为网关用户面功能GW-U。
  30. 一种提升业务可靠性的方法，其特征在于，所述方法包括：
    终端与接入设备交互，建立与用户面功能实体用户面功能实体之间的第一传输路径和第二传输路径；
    终端接收会话功能实体经由所述接入设备发送的消息，所述消息指示所述终端在所述第一传输路径和第二传输路径上传输相同的数据。
  31. 如权利要求30中所述的方法，其特征在于，所述终端与接入设备交互，建立与用户面功能实体用户面功能实体之间的第一传输路径和第二传输路径，包括：
    所述终端发送业务请求给会话功能实体，所述业务请求中携带建立两条传输路径，或者建立第二传输路径的指示。
  32. 如权利要求30或者31中所述的方法，其特征在于，所述终端与第一接入设备和第二接入设备分别协商建立所述第一传输路径和第二传输路径。
  33. 如权利要求30-32任一项所述的方法，其特征在于，所述终端在所述第一和第二传输路径上传输相同的数据，包括：所述终端在所述第一和第二传输路径上发送相同的数据给所述用户面功能实体用户面功能实体；或者，所述终端从所述第一和第二传输路径上接收所述用户面功能实体用户面功能实体发送的相同的数据并对所述接收的数据去重。
  34. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求12-33任意一项所述的方法。
PCT/CN2017/108396 2017-10-30 2017-10-30 提升业务可靠性的方法、设备及系统 WO2019084725A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
KR1020207014662A KR102413507B1 (ko) 2017-10-30 2017-10-30 서비스 신뢰성 개선 방법, 디바이스 및 시스템
JP2020524129A JP7175977B2 (ja) 2017-10-30 2017-10-30 サービスの信頼性を向上させる方法、デバイス、およびシステム
CN202111056184.XA CN113891496A (zh) 2017-10-30 2017-10-30 提升业务可靠性的方法、设备及系统
BR112020008149-3A BR112020008149A2 (pt) 2017-10-30 2017-10-30 método para melhorar confiabilidade de serviço, dispositivo, e sistema
PCT/CN2017/108396 WO2019084725A1 (zh) 2017-10-30 2017-10-30 提升业务可靠性的方法、设备及系统
EP17930784.8A EP3703466B1 (en) 2017-10-30 2017-10-30 Service reliability improving method, device, and system
CN201780096080.7A CN111247869B (zh) 2017-10-30 2017-10-30 提升业务可靠性的方法、设备及系统
US16/862,001 US11432297B2 (en) 2017-10-30 2020-04-29 Method for improving service reliability, device, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/108396 WO2019084725A1 (zh) 2017-10-30 2017-10-30 提升业务可靠性的方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/862,001 Continuation US11432297B2 (en) 2017-10-30 2020-04-29 Method for improving service reliability, device, and system

Publications (1)

Publication Number Publication Date
WO2019084725A1 true WO2019084725A1 (zh) 2019-05-09

Family

ID=66333394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/108396 WO2019084725A1 (zh) 2017-10-30 2017-10-30 提升业务可靠性的方法、设备及系统

Country Status (7)

Country Link
US (1) US11432297B2 (zh)
EP (1) EP3703466B1 (zh)
JP (1) JP7175977B2 (zh)
KR (1) KR102413507B1 (zh)
CN (2) CN111247869B (zh)
BR (1) BR112020008149A2 (zh)
WO (1) WO2019084725A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021141825A1 (en) * 2020-01-08 2021-07-15 Cisco Technology, Inc. Ultra-reliable low latency communications (urllc) support for wireless access
CN113316098A (zh) * 2021-04-20 2021-08-27 新华三技术有限公司 一种建立业务通道、公网对讲的方法和公网对讲设备
CN113328783A (zh) * 2021-05-25 2021-08-31 广州爱浦路网络技术有限公司 天地一体化信息网络中的数据传输方法、装置和存储介质
CN113473508A (zh) * 2020-03-30 2021-10-01 华为技术有限公司 一种通信方法和通信装置
KR20210149287A (ko) * 2020-06-01 2021-12-09 한국전자통신연구원 5g와 atsc 3.0의 통합 코어 네트워크, 제어 평면 엔티티 및 제어 평면 엔티티에서의 멀티미디어 콘텐츠 전송 제어 방법
JP2022515733A (ja) * 2019-05-17 2022-02-22 ▲騰▼▲訊▼科技（深▲セン▼）有限公司 データ伝送方法及びその装置、機器並びにコンピュータプログラム
JP2022550214A (ja) * 2019-11-21 2022-11-30 スマートスカイ ネットワークス エルエルシー 空対地ＷｉＦｉシステムを強化する為の方法及び装置
US12028803B2 (en) 2020-11-16 2024-07-02 Smartsky Networks LLC Method and apparatus for enhancing an air-to-ground WiFi system

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102396950B1 (ko) * 2018-05-21 2022-05-12 삼성전자 주식회사 5g 무선통신 네트워크 시스템에서 최고 신뢰성있는 서비스를 위한 이중 전송 방법 및 장치
US10531436B1 (en) * 2018-09-12 2020-01-07 Capital One Services, Llc Multiple network connections to increase data throughput of mobile device
US11005715B2 (en) 2018-12-21 2021-05-11 T-Moblle USA, Inc. Latency-sensitive network-traffic quality of service
US11044194B2 (en) * 2019-02-28 2021-06-22 T-Mobile Usa, Inc. QoS for latency-sensitive network-traffic flows
CN113645662B (zh) * 2021-08-17 2023-08-18 中国联合网络通信集团有限公司 业务处理方法及装置
CN114051047B (zh) * 2021-10-29 2023-06-09 恒安嘉新（北京）科技股份公司 一种会话消息的备份方法、装置、网络设备和存储介质
WO2023141909A1 (zh) * 2022-01-27 2023-08-03 Oppo广东移动通信有限公司 无线通信方法、远端ue以及网元
CN116939700A (zh) * 2022-04-06 2023-10-24 华为技术有限公司 通信方法和通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009078675A1 (en) * 2007-12-18 2009-06-25 Electronics And Telecommunications Research Institute Seamless service method controlled by user terminal
CN105517028A (zh) * 2014-10-17 2016-04-20 电信科学技术研究院 一种触发和配置传输路径的方法及设备
CN107027144A (zh) * 2016-02-01 2017-08-08 中国移动通信集团公司 一种高速移动场景检测方法和装置

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7046646B2 (en) * 2001-01-29 2006-05-16 Ipr Licensing, Inc. Method and apparatus for simple PPP handoff for mobile users
JP4036627B2 (ja) * 2001-09-27 2008-01-23 株式会社エヌ・ティ・ティ・ドコモ 移動通信システム、移動通信方法、基地局及び移動局
KR20060033658A (ko) * 2004-10-15 2006-04-19 삼성전자주식회사 이동통신시스템에서의 핸드오버 장치 및 방법
KR100678096B1 (ko) * 2006-02-14 2007-02-02 삼성전자주식회사 다중 입력 다중 출력 방식을 이용한 광대역 분산 네트워크시스템의 핸드오프 제어방법
US9155118B2 (en) * 2007-01-22 2015-10-06 Qualcomm Incorporated Multi-link support for network based mobility management systems
US8599720B2 (en) * 2009-06-26 2013-12-03 Qualcomm Incorporated Optimized resource usage with network initiated QoS
KR20140116554A (ko) * 2010-02-12 2014-10-02 인터디지탈 테크날러지 코포레이션 다중 사이트 간의 데이터 분할
CN105245452B (zh) * 2012-06-06 2018-11-16 华为技术有限公司 多协议标签交换流量工程隧道建立方法及设备
US9408125B2 (en) * 2012-07-05 2016-08-02 Qualcomm Incorporated Aggregation of data bearers for carrier aggregation
US9554389B2 (en) 2012-08-31 2017-01-24 Qualcomm Incorporated Selectively allocating quality of service to support multiple concurrent sessions for a client device
US20140335882A1 (en) * 2013-05-10 2014-11-13 Electronics & Telecommunications Research Institute Method for configuring dual connectivity
WO2015008989A1 (en) * 2013-07-14 2015-01-22 Lg Electronics Inc. Method and apparatus for managing data radio bearers for dual connectivity in wireless communication system
US10230650B2 (en) * 2015-06-26 2019-03-12 Huawei Technologies Co., Ltd. Joint radio link control (RLC) signaling with network coding
CN106559806B (zh) * 2015-09-25 2020-08-21 努比亚技术有限公司 双通道数据传输方法、装置、网络节点及移动终端
CN112566201A (zh) * 2015-10-09 2021-03-26 苹果公司 网络发起的分组数据网络连接
CN107040942A (zh) * 2016-02-04 2017-08-11 华为技术有限公司 业务流传输方法、装置及系统
US10356184B2 (en) * 2016-03-31 2019-07-16 Huawei Technologies Co., Ltd. Systems and methods for service and session continuity in software defined topology management
US10897507B2 (en) * 2016-04-01 2021-01-19 Qualcomm Incorporated Mechanism to enable connectivity sessions and IP session establishment
WO2017166300A1 (zh) 2016-04-01 2017-10-05 华为技术有限公司 一种无线资源管理方法和装置
US10587497B2 (en) * 2016-08-22 2020-03-10 Qualcomm Incorporated Channel sensing for independent links
GB201621072D0 (en) * 2016-12-12 2017-01-25 Samsung Electronics Co Ltd NR QOS handling
US10448386B2 (en) * 2017-01-06 2019-10-15 Kt Corporation Method and apparatus for controlling redundant data transmission
CN110663206B (zh) * 2017-03-23 2022-11-01 弗劳恩霍夫应用研究促进协会 在移动通信网络中发送数据分组的方法、装置和介质
WO2018188717A1 (en) * 2017-04-10 2018-10-18 Nokia Technologies Oy Control mechanism for packet duplication in multi-connectivity communication
US11576222B2 (en) * 2017-05-12 2023-02-07 Nokia Technologies Oy Protocol data unit session splitting function and signaling
WO2019006085A1 (en) * 2017-06-30 2019-01-03 Intel Corporation V2X COMMUNICATIONS USING MULTIPLE RAT (MULTI-RAT) ACCESS TECHNOLOGIES
KR102386305B1 (ko) * 2017-07-25 2022-04-14 삼성전자주식회사 무선 네트워크 시스템에서 트래픽을 처리하는 방법 및 장치
EP4236591A3 (en) 2017-08-09 2023-11-22 Nec Corporation Pdu session resource set up request message indicating either permission for pdu session or possibility to perform pdu session split
US10798775B2 (en) * 2017-08-10 2020-10-06 Qualcomm Incorporated Techniques and apparatuses for duplication bearer management
CN112153121A (zh) * 2017-08-29 2020-12-29 华为技术有限公司 数据传输方法、设备及系统
US11206105B2 (en) * 2017-09-07 2021-12-21 Shenzhen Heytap Technology Corp., Ltd. Data transmission method and terminal device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009078675A1 (en) * 2007-12-18 2009-06-25 Electronics And Telecommunications Research Institute Seamless service method controlled by user terminal
CN105517028A (zh) * 2014-10-17 2016-04-20 电信科学技术研究院 一种触发和配置传输路径的方法及设备
CN107027144A (zh) * 2016-02-01 2017-08-08 中国移动通信集团公司 一种高速移动场景检测方法和装置

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022515733A (ja) * 2019-05-17 2022-02-22 ▲騰▼▲訊▼科技（深▲セン▼）有限公司 データ伝送方法及びその装置、機器並びにコンピュータプログラム
JP7252341B2 (ja) 2019-05-17 2023-04-04 ▲騰▼▲訊▼科技（深▲セン▼）有限公司 データ伝送方法及びその装置、機器並びにコンピュータプログラム
JP2022550214A (ja) * 2019-11-21 2022-11-30 スマートスカイ ネットワークス エルエルシー 空対地ＷｉＦｉシステムを強化する為の方法及び装置
WO2021141825A1 (en) * 2020-01-08 2021-07-15 Cisco Technology, Inc. Ultra-reliable low latency communications (urllc) support for wireless access
US11303558B2 (en) 2020-01-08 2022-04-12 Cisco Technology, Inc. Ultra-reliable low latency communications (URLLC) support for wireless access
CN113473508A (zh) * 2020-03-30 2021-10-01 华为技术有限公司 一种通信方法和通信装置
CN113473508B (zh) * 2020-03-30 2023-09-08 华为技术有限公司 一种通信方法和通信装置
KR20210149287A (ko) * 2020-06-01 2021-12-09 한국전자통신연구원 5g와 atsc 3.0의 통합 코어 네트워크, 제어 평면 엔티티 및 제어 평면 엔티티에서의 멀티미디어 콘텐츠 전송 제어 방법
KR102593727B1 (ko) 2020-06-01 2023-10-26 한국전자통신연구원 5g와 atsc 3.0의 통합 코어 네트워크, 제어 평면 엔티티 및 제어 평면 엔티티에서의 멀티미디어 콘텐츠 전송 제어 방법
US12028803B2 (en) 2020-11-16 2024-07-02 Smartsky Networks LLC Method and apparatus for enhancing an air-to-ground WiFi system
CN113316098A (zh) * 2021-04-20 2021-08-27 新华三技术有限公司 一种建立业务通道、公网对讲的方法和公网对讲设备
CN113328783A (zh) * 2021-05-25 2021-08-31 广州爱浦路网络技术有限公司 天地一体化信息网络中的数据传输方法、装置和存储介质

Also Published As

Publication number Publication date
KR102413507B1 (ko) 2022-06-24
CN111247869B (zh) 2021-12-14
EP3703466B1 (en) 2023-09-13
EP3703466A1 (en) 2020-09-02
JP2021501523A (ja) 2021-01-14
US11432297B2 (en) 2022-08-30
JP7175977B2 (ja) 2022-11-21
EP3703466A4 (en) 2020-10-28
CN111247869A (zh) 2020-06-05
CN113891496A (zh) 2022-01-04
KR20200073270A (ko) 2020-06-23
BR112020008149A2 (pt) 2020-11-03
US20200260457A1 (en) 2020-08-13

Similar Documents

Publication Publication Date Title
WO2019084725A1 (zh) 提升业务可靠性的方法、设备及系统
EP3694181B1 (en) Session establishment method, device and system
US11115876B2 (en) Service continuity implementation method, device, and service continuity implementation system
CN111432440B (zh) 实现业务连续性的方法、装置及系统
CN110166407B (zh) QoS流处理方法、设备及系统
JP6940041B2 (ja) サービスのサービス品質を検出するための方法、デバイスおよびシステム
KR102581335B1 (ko) 서비스 품질 모니터링 방법 및 시스템, 및 디바이스
WO2019091396A1 (zh) 通信方法及通信设备
WO2021032131A1 (zh) 一种用户面信息上报方法及装置
CN107135521B (zh) 一种流量控制方法、装置和系统
CN112019363B (zh) 确定业务传输需求的方法、设备及系统
CN114270933B (zh) 用于支持ue的切换的设备和方法
KR102476193B1 (ko) 레이트 제어 방법, 장치, 및 시스템
WO2020228686A1 (zh) 多连接系统中的数据无线承载控制方法、装置和系统
WO2020029671A1 (zh) 一种直连通信的方法、amf、接入网功能实体及终端
WO2023029625A1 (zh) 一种服务质量的处理方法、装置和通信系统
WO2022193127A1 (zh) 业务调度方法、装置及系统
WO2020192263A1 (zh) 计费规则绑定的方法、设备及系统
WO2021046746A1 (zh) 上报会话管理信息的方法、设备及系统
JP2023531091A (ja) アプリケーション要求処理方法、システム、電子機器及び記憶媒体
JP2024520949A (ja) ネットワークアクセス方法、ネットワーク機器及び記憶媒体
WO2017161970A1 (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: 17930784

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020524129

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207014662

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017930784

Country of ref document: EP

Effective date: 20200525

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020008149

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020008149

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200424