WO2020216023A1 - 冗余协议数据单元会话的配置方法及装置 - Google Patents

冗余协议数据单元会话的配置方法及装置 Download PDF

Info

Publication number
WO2020216023A1
WO2020216023A1 PCT/CN2020/082591 CN2020082591W WO2020216023A1 WO 2020216023 A1 WO2020216023 A1 WO 2020216023A1 CN 2020082591 W CN2020082591 W CN 2020082591W WO 2020216023 A1 WO2020216023 A1 WO 2020216023A1
Authority
WO
WIPO (PCT)
Prior art keywords
redundant
pdu session
qos flow
indication information
ran
Prior art date
Application number
PCT/CN2020/082591
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 EP20796435.4A priority Critical patent/EP3962165A4/en
Priority to US17/606,560 priority patent/US12035168B2/en
Publication of WO2020216023A1 publication Critical patent/WO2020216023A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0273—Traffic management, e.g. flow control or congestion control adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP]
    • 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
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • 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
    • 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
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and device for configuring redundant PDU Session.
  • the mobile communication system includes mobile user equipment (User Equipment, UE) and network equipment (Network), where the network equipment also includes a radio access network (Radio Access Network, RAN) and a core network (Core Network, CN).
  • the RAN includes: one or more cell groups, or one or more base stations, or one or more Node Bs.
  • CN refers to the 5G core network (5G Core), which includes: Access and Mobility Management Function (AMF), User Plane Function (UPF), System Management Function ( System Management Function, SMF) and other network elements.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • SMF System Management Function
  • the UE establishes two or more connections with the network equipment.
  • the CN UPF network element of the core network
  • the two cell groups of the RAN have respectively established connections.
  • the RAN includes a master node (Master node, MN) and a secondary node (Secondary node, SN).
  • the UE starts to establish 2 redundant PDU Sessions, and configures a different combination of DNN and S-NSSAI for each session.
  • the present invention is directed to redundant sessions, so in the present invention, redundant sessions are also referred to as sessions for short, that is, PDU Session in the present invention refers to redundant PDU Session.
  • SMF determines whether the session can be established. SMF makes this decision based on the combination of S-NSSA, DNN, user authorization and local policy configuration. SMF decides to use RSN to distinguish the PDU session, which uses MN (master NG-RAN) or SN to send user plane data.
  • configuring the PDU Session on the MN (or SN) means that the user data of the PDU Session is sent on the MN or SN. As shown in Figure 3, the user plane of one PDU Session is established on UPF1, and the user plane of another PDU Session is established on UPF2.
  • the present invention provides a technical solution that can realize the establishment and modification of multiple user plane connections.
  • the embodiment of the present invention provides a redundant PDU Session configuration method and device, so as to at least solve the problem of how to realize multiple user plane connections in related technologies.
  • a method for configuring redundant PDU Session including: acquiring first redundancy indication information for establishing or modifying PDU Session and/or QoS flow; according to the first redundancy indication information , Configure the redundant PDU Session and/or redundant QoS flow on the corresponding RAN node.
  • the first redundancy indication information is PDU Session level redundancy indication information, or the first redundancy indication information is QoS flow level redundancy indication information.
  • the first redundancy indication information includes at least one of the following: indicating whether the PDU Session and/or QoS flow is a redundant PDU Session and/or redundant QoS flow; indicating the redundant PDU Session and/or The redundant QoS flow is configured to the corresponding RAN node.
  • obtaining the first redundancy indication information for establishing or modifying the PDU Session and/or QoS flow includes: the RAN master node obtains the first redundancy indication information for establishing or modifying the PDU Session and/or QoS flow from the core network.
  • configuring redundant PDU Session and/or redundant QoS flow on the corresponding RAN node includes: configuring the redundant PDU Session and/or redundant QoS flow on the RAN master node, or The redundant PDU Session and/or redundant QoS flow are configured on the RAN secondary node.
  • obtaining the first redundancy indication information for establishing or modifying PDU Session and/or QoS flow includes: the target RAN master node obtains the first redundancy indication information for establishing PDU Session and/or QoS flow from the source RAN master node.
  • configuring redundant PDU Session and/or redundant QoS flow on the corresponding RAN node includes: configuring the redundant PDU Session and/or redundant QoS flow on the target RAN master node, or Configure the redundant PDU Session and/or redundant QoS flow on the target RAN secondary node.
  • the RAN master node before configuring the redundant PDU Session and/or redundant QoS flow on the RAN secondary node, it also includes: the RAN master node sends to the RAN secondary node a message to establish or modify the PDU Session and/or QoS flow The second redundant indication information.
  • the second redundancy indication information is PDU Session level redundancy indication information, or the second redundancy indication information is QoS flow level redundancy indication information.
  • the second redundancy indication information is used to indicate whether the PDU Session and/or QoS flow are redundant PDU Session and/or redundant QoS flow.
  • the PDU Session if it is newly established, before acquiring the first redundancy indication information for establishing or modifying the PDU Session and/or QoS flow, it also includes: the core network receives the UE initiated request to establish multiple PDU Sessions, where Each PDU Session carries PDU Session level or QoS level redundancy indication information; the core network determines to establish the multiple PDU Sessions, and sends a PDU Session establishment request message to the RAN master node MN, and carries the PDU Session level or QoS level redundancy indication information.
  • all QoS flows of a redundant PDU Session are redundant QoS flows
  • the type of the PDU Session is Non-split PDU Session
  • the bearers corresponding to all QoS flows contained in it are configured on the same RAN node.
  • the configuration of redundant PDU Session and/or redundant QoS flow on a RAN node means that both the upper and lower layers of the corresponding bearer are configured on the RAN node.
  • the corresponding bearer type is MN terminated MCG bearer.
  • the corresponding bearer type is SN terminated SCG bearer.
  • a device for configuring redundant PDU Session including: an acquisition module configured to acquire first redundancy indication information for establishing or modifying PDU Session and/or QoS flow; and a configuration module, It is set to configure redundant PDU Session and/or redundant QoS flow on the corresponding RAN node according to the first redundancy indication information.
  • the first redundancy indication information is PDU Session level redundancy indication information, or the first redundancy indication information is QoS flow level redundancy indication information.
  • the first redundancy indication information includes at least one of the following: indicating whether the PDU Session and/or QoS flow is a redundant PDU Session and/or redundant QoS flow; indicating the redundant PDU Session and/or The redundant QoS flow is configured to the corresponding RAN node.
  • the obtaining module includes: a first obtaining unit, configured to obtain the first redundancy indication information for establishing or modifying the PDU Session and/or QoS flow from the core network through the RAN master node.
  • the configuration module includes: a first configuration unit, configured to configure the redundant PDU Session and/or redundant QoS flow on the RAN master node, or configure the redundant PDU Session and/or redundant The QoS flow is configured on the RAN secondary node.
  • the acquiring module includes: a second acquiring unit, configured to acquire, from the source RAN master node through the target RAN master node, first redundancy indication information for establishing a PDU Session and/or QoS flow.
  • the configuration module includes: a second configuration unit, configured to configure the redundant PDU Session and/or redundant QoS flow on the target RAN master node, or configure the redundant PDU Session and/or redundant QoS flow The remaining QoS flow is configured on the target RAN secondary node.
  • the device further includes: a sending module, configured to send the establishment or the RAN to the RAN secondary node through the RAN master node before configuring the redundant PDU Session and/or redundant QoS flow on the RAN secondary node Modify the second redundancy indication information of the PDU Session and/or QoS flow.
  • a sending module configured to send the establishment or the RAN to the RAN secondary node through the RAN master node before configuring the redundant PDU Session and/or redundant QoS flow on the RAN secondary node Modify the second redundancy indication information of the PDU Session and/or QoS flow.
  • the second redundancy indication information is PDU Session level redundancy indication information, or the second redundancy indication information is QoS flow level redundancy indication information.
  • the second redundancy indication information is used to indicate whether the PDU Session and/or QoS flow are redundant PDU Session and/or redundant QoS flow.
  • a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in the foregoing method embodiment when running.
  • an electronic device including a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to execute the above method embodiments Steps in.
  • the redundancy indication information for establishing or modifying the PDU Session and/or QoS flow is obtained, and the redundant PDU Session and/or QoS flow are configured to the corresponding RAN node according to the redundancy indication information , which can realize the establishment and modification of multiple connections on the user plane.
  • Figure 1 is a schematic diagram of a dual-connection network architecture according to related technologies
  • Figure 2 is a schematic diagram of a high-level architecture of a single device according to related technologies
  • Figure 3 is a schematic diagram of a solution architecture according to related technologies
  • Fig. 5 is a flowchart of establishing redundant PDU Session/redundant QoS flow according to an embodiment of the present invention
  • Fig. 6 is a flowchart of modifying redundant PDU Session/redundant QoS flow according to an embodiment of the present invention
  • Fig. 7 is a flowchart of establishing redundant PDU Session/redundant QoS flow in a handover scenario according to an embodiment of the present invention
  • Figure 8 is a flowchart of initiating the establishment of redundant PDU Session/Redundant QoS flow according to an embodiment of the present invention
  • Fig. 9 is a schematic structural diagram of a redundant PDU Session configuration according to an embodiment of the present invention.
  • FIG. 1 is a flowchart according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:
  • Step S402 Obtain redundant indication information for establishing or modifying PDU Session and/or QoS flow;
  • Step S404 according to the redundancy indication information, configure redundant PDU Session and/or redundant QoS flow on the corresponding RAN node.
  • the RAN master node MN obtains the redundancy indication information of the PDU Session and/or QoS flow that needs to be established or modified from the core network.
  • the target RAN master node Target MN obtains redundant indication information of the PDU Session and/or QoS flow that need to be established from the original RAN master node Source MN.
  • the redundancy indication information may be a PDU Session level or a QoS flow level, and may indicate whether the PDU Session and/or QoS flow is a redundant PDU Session and/or redundant QoS flow. It may indicate that the redundant PDU Session and/or redundant QoS flow are configured to a certain RAN node.
  • the primary node when the redundancy indication information indicates that the redundant PDU Session and/or redundant QoS flow are configured on the secondary node, the primary node sends new redundancy indication information to the secondary node, and the redundancy indication
  • the information may be a PDU Session level or a QoS flow level, and is used to indicate whether the PDU Session and/or QoS flow is a redundant PDU Session and/or redundant QoS flow.
  • all QoS flows of a redundant PDU Session are redundant QoS flows, and the master node is not allowed to separate the PDU Session (that is, the type of the PDU Session is Non-split PDU Session (non-separated session),
  • the bearers corresponding to all QoS flows must be configured on the same RAN node)
  • the redundant PDU Session and/or redundant QoS flow are configured on a RAN node, which means that the high-level (SDAP, PDCP) and low-level (RLC, MAC, and physical layers) of the corresponding bearer are configured in this On the RAN node.
  • SDAP high-level
  • PDCP low-level
  • RLC low-level
  • MAC MAC
  • the corresponding bearer type is MN terminated MCG bearer
  • the corresponding bearer type is SN terminated SCG bearer
  • Step 1 The UE initiates 2 PDU Session establishment/requests to the network (dual connection is taken as an example here, of course, it can also be the establishment of multiple PDU Session establishment/requests). Each PDU Session carries the redundancy of the PDU Session level or QoS level. I instructions.
  • Step 2 The core network decides to establish the two PDU Sessions, and the core network sends a PDU Session establishment request message to the RAN master node MN, and carries the PDU Session level or QoS level redundancy indication information.
  • This embodiment specifically describes the process of RAN establishing a redundant PDU Session and/or redundant QoS flow, as shown in Figure 5, including the following steps:
  • Step S501 The RAN receives the PDU Session Resource setup request message sent by the core network (CN, core network, in the 5G system, it refers to the AMF, and in the 4G system, the MME), and the message contains 1 or Multiple PDU Sessions, each of which contains one or more QoS flows.
  • the core network CN, core network, in the 5G system, it refers to the AMF, and in the 4G system, the MME
  • the message contains 1 or Multiple PDU Sessions, each of which contains one or more QoS flows.
  • One or more PDU Sessions in the PDU Session include a redundancy indicator of the PDU Session level, and/or one or more PDU Sessions in the PDU Session include a redundancy indicator of the QoS flow level.
  • a certain PDU Session contains QoS flow-level redundancy indication information, it means that one or more QoS flows of this PDU Session are redundant QoS flows. At this time, each PDU session contains redundant indication information. QoS flow is redundant QoS flow.
  • Step S502 The RAN judges whether the PDU Session/QoS flow is a redundant PDU Session/QoS flow. If the judgment result is no, there is no provision in this embodiment, and step S507 is directly executed. If the judgment result is yes, step S503 is executed.
  • the PDU Session when a certain PDU Session contains PDU Session level redundancy indication information, the PDU Session is a redundant PDU Session, and all QoS flows it contains are redundant QoS flows. At this time, the PDU Session does not Contains QoS flow level redundant indication information.
  • the redundancy indication information may be at the PDU Session level or at the QoS flow level.
  • the core network configures PDU Session level and/or QoS flow level redundancy indication information and sends it to the RAN. Therefore, the RAN can learn which PDU Session or Sessions are redundant PDU Sessions, and which QoS flow or QoS flows are redundant QoS flows.
  • Step S503 It is further determined whether the redundant PDU Session/QoS flow is established on the MN or the SN. If it is established on the MN, step S504 is executed, and if it is established on the SN, then step S505 is executed.
  • the different values of the redundancy indication information can be identified by RSN (redundant sequence number, redundant sequence number). They respectively represent that the corresponding PDU Session or the corresponding QoS flow needs to be configured on different nodes of the RAN.
  • RSN redundant sequence number
  • MN master node
  • SN secondary node
  • one of the nodes is node 0 (primary node), one node is node 1 (secondary node 1), one node is node 2 (secondary node 2), and one node is node 3 (secondary node 3)
  • the redundant PDU Session/QoS flow needs to be configured on the secondary node 2
  • the RAN configures it as a non-split PDU Session, that is, the RAN does not allow the QoS flow of the PDU session to be configured on different RAN nodes, but all of the PDU Session QoS flow is configured on a certain RAN node.
  • the RAN configures the QoS flow on a certain RAN node according to the redundancy indication information of the redundant QoS flow.
  • the redundant QoS flows are configured with the same redundant indication information (that is, the RSN value is the same, and these redundant QoS flows are all configured in the same).
  • the present invention also allows the redundant QoS flow to be configured with different redundant indication information (ie: RSN values are different, these redundant QoS flows Flow allows to be configured on different RAN nodes).
  • the RAN reads the request message. If a certain PDU Session/QoS has redundant indication information, the PDU Session/QoS is redundant PDU Session/Redundant QoS flow, and then according to the redundant indication information With a value, the RAN can learn that the PDU Session/QoS flow is configured on a certain node.
  • configuring all the QoS flows of a certain redundant PDU Session, or a certain redundant QoS flow on a certain RAN node means that the higher layer (SDAP, PDCP) and the corresponding bearer of the QoS flow are configured
  • the lower layers (RLC, MAC and physical layer) are all configured on the RAN node.
  • Step S504 Establish the redundant PDU Session/redundant QoS flow on the master node MN, and the bearer type is MN terminated MCG bearer.
  • Step S505 When the redundant indication information of the redundant PDU Session and/or redundant QoS flow is required to be configured on the secondary node, the primary node sends the SN addition request message or the SN modification request message to the secondary node.
  • the IE "PDU Session Resource Setup Info-SN terminated" contains the redundant indication information of one or more redundant PDU Sessions and/or redundant QoS flow requested to be established and other related configuration information.
  • the redundancy indication information sent by the MN to the SN can be at the PDU Session level or at the QoS flow level.
  • the redundant indication information sent by the MN to the SN may be different from the redundant indication information received from the core network.
  • the RAN can learn whether the PDU Session/QoS flow is a redundant PDU Session/Redundant QoS flow, on the other hand, by reading For the value of the redundancy indication information of a certain PDU Session/QoS flow, the RAN can learn which RAN node the PDU Session/QoS flow needs to be configured on.
  • the redundancy indication information sent from the MN to the SN may only indicate whether a certain PDU Session/QoS flow is redundant PDU Session/Redundant QoS flow.
  • Step S506 The secondary node receives the SN addition request message or SN modification request message sent by the primary node, and the redundancy indication information contained in the message indicates that the redundant PDU Session and/or redundant QoS flow are configured on the secondary node , The secondary node configures its corresponding bearer type as SN terminated SCG bearer, and the secondary node is not allowed to change the bearer type until the redundancy information indicates the change.
  • the redundant indication information of redundant PDU Session and/or redundant QoS flow in the message is important, because if there is no such redundant indication information, SN is likely to configure the bearer of these PDU Session/QoS flows as SN terminated split bearer or SN terminated MCG bearer.
  • Step S507 Repeat the above steps for the next received PDU Session/Redundant QoS flow.
  • This embodiment describes the process in which the RAN modifies the redundant PDU Session and/or redundant QoS flow.
  • 5GC can configure it as a redundant PDU Session when the PDU Session is established, which is also a normal PDU Session (that is, not a redundant PDU Session) when the PDU Session is established.
  • the 5GC modifies the PDU Session to a redundant PDU Session; subsequently, the 5GC can also modify a redundant PDU Session to a normal PDU Session (that is, not a redundant PDU Session).
  • 5GC can configure it as a redundant QoS flow when the QoS flow is established, which is also a normal QoS flow (that is, not a redundant QoS flow) when the QoS flow is established, and then Ground, 5GC modifies this QoS flow to redundant QoS flow; subsequently, 5GC can also modify a certain redundant QoS flow to ordinary QoS flow (that is, different redundant QoS flows).
  • the method flow of this embodiment includes the following steps:
  • Step S601 The RAN receives the PDU Session Resource modify request message sent by the core network.
  • the message includes: whether to modify the redundancy indication information of one or more PDU Sessions, and/or modify one or more QoS flows The value of the redundant indication information.
  • the modification of the redundancy indication information of the PDU Session or the modification of the redundancy indication information of the QoS flow includes: modifying a certain/some redundant PDU Session or redundant QoS flow to a non-redundant PDU Session or a non-redundant QoS flow (That is, the PDU Session or QoS flow is not configured with redundant indication information), or one/some non-redundant PDU Session or non-redundant QoS flow is modified to redundant PDU Session or redundant QoS flow (ie: Configure redundancy indication information for the PDU Session or QoS flow), or modify the value of the redundancy indication information of a certain/some redundant PDU Session or redundant QoS flow (for example, modify the value of RSN from 0 to 1, or the value of RSN is modified from 0 to 1, that is, the redundant PDU Session or redundant QoS flow is reconfigured from one RAN node to another RAN node).
  • Step S602 The RAN judges whether the modified PDU Session/QoS flow is a redundant PDU Session/QoS flow. If the judgment result is no, there is no provision in this embodiment, and step S607 is directly executed. If the judgment result is yes, step S603 is executed.
  • Step S603 It is further determined whether the redundant PDU Session/QoS flow is established on the MN or the SN after modification. If it is established on the MN, step S604 is executed, and if it is established on the SN, step S605 is executed.
  • the RAN performs corresponding configuration according to whether there is redundancy indication information after each PDU Session and/or QoS flow is modified, or the value of the modified new redundancy indication information.
  • RAN can modify or not modify its configuration .
  • Step S604 Establish the redundant PDU Session/redundant QoS flow on the master node MN, and the bearer type is MN terminated MCG bearer.
  • Step S605 When the redundant indication information of the redundant PDU Session and/or redundant QoS flow is required to be configured on the secondary node, the primary node sends an SN modification request message to the secondary node, the information element IE in the message PDU Session Resource Modification Info-SN terminated" includes: whether to modify one or more PDU Session redundant indication information.
  • Step S606 The secondary node receives the SN modification request message sent by the master node, and performs corresponding configuration.
  • the SN configures it as SN terminated SCG bearer; for the PDU Session and/or QoS flow with redundant indication information that were originally redundant PDU Session or redundant QoS flow, but now there is no redundant indication information configured PDU Session Or QoS flow, the PDU Session or QoS flow is a non-redundant PDU Session or a non-redundant QoS flow, and the SN may or may not be reconfigured.
  • Step S607 Repeat the above steps for the next received PDU Session/Redundant QoS flow.
  • This embodiment describes the process in which the original RAN node transmits redundant PDU Session and/or redundant QoS flow to the target RAN node in the handover process.
  • SN change without MN change MN handover without SN change
  • MN handover without SN change MN handover without SN change
  • both MN and SN Handover MN handover with SN change
  • the original NG-RAN node transfers the redundant indication information of each PDU Session and/or QoS flow from the source node (source NG-RAN) to the target node (Target NG-RAN).
  • This redundant indication information If it is a switch based on the NG interface, it will pass through the NG interface. If it is a switch based on the Xn interface, it will pass through the Xn interface.
  • the process of this embodiment includes the following steps:
  • Step S701 In the handover request message sent by the original RAN node to the target RAN node, each redundant PDU Session and/or redundant QoS flow includes a redundant indication information.
  • the redundant indication information of each PDU Session and/or QoS flow is sent from the original RAN node to the target RAN node.
  • the redundant indication information is sent through a handover request message.
  • the original RAN node is the original MN node (Source MN)
  • the target RAN node is the target MN node (Target MN). That is: the handover request message is sent from Source MN to Target MN.
  • Step S702 The RAN judges whether the PDU Session/QoS flow is a redundant PDU Session/QoS flow. If the judgment result is no, there is no provision in this embodiment, and step S707 is directly executed. If the judgment result is yes, step S703 is executed.
  • Step S703 It is further judged whether the redundant PDU Session/QoS flow is established on the MN or the SN. If it is established on the MN, step S704 is executed, and if it is established on the SN, step S705 is executed.
  • the target MN configures the redundant PDU Session and/or the redundant QoS flow in the corresponding RAN target master node or target according to the redundant indication information of each redundant PDU Session and/or each redundant QoS flow On the secondary node.
  • the target MN in this embodiment is similar to the RAN in Embodiment 1.
  • Step S704 Establish the redundant PDU Session/redundant QoS flow on the master node MN, and the bearer type is MN terminated MCG bearer.
  • Step S705 When the redundant indication information of the redundant PDU Session and/or redundant QoS flow is required to be configured on the target secondary node, the target primary node sends an SN addition request message to the target secondary node, the IE in the message "PDU Session Resource Setup Info-SN terminated" contains the redundant indication information of one or more redundant PDU Sessions and/or redundant QoS flow requested to be established and other related configuration information.
  • the target primary node replaces the primary node
  • the target secondary node replaces the secondary node
  • the SN modification request message is not included in the message. Everything else is the same.
  • the redundancy indication information sent by the MN to the SN can be at the PDU Session level or at the QoS flow level.
  • the redundant indication information sent by the target MN to the target SN may be different from the redundant indication information received from the original master node.
  • the target master node can learn whether the PDU Session/QoS flow is a redundant PDU Session/Redundant QoS flow, on the other hand By reading the value of the redundancy indication information of a certain PDU Session/QoS flow, the target master node can learn which target RAN node the PDU Session/QoS flow needs to be configured on.
  • the redundancy indication information sent from the MN to the SN may only indicate whether a certain PDU Session/QoS flow is a redundant PDU Session/Redundant QoS flow.
  • Step S706 The target secondary node receives the SN addition request message or SN modification request message sent by the target master node, and the redundancy indication information contained in the message indicates that the redundant PDU Session and/or redundant QoS flow are configured in the secondary On the node, the secondary node configures its corresponding bearer type as SN terminated SCG bearer, and the secondary node is not allowed to change the bearer type until the redundancy information indicates a change.
  • the redundancy indication information refer to Embodiment 2.
  • the redundant indication information of the redundant PDU Session and/or redundant QoS flow in the message is important, because if there is no such redundant indication information, the SN is likely to configure the bearer of these PDU Session/QoS flows as SN terminated split bearer Or SN terminated MCG bearer.
  • Step S707 Repeat the above steps for the next received PDU Session/Redundant QoS flow.
  • the UE initiates a redundant PDU Session or initiates a request to establish a partial redundant QoS flow in the PDU Session.
  • the preset condition is that the UE has the ability to establish dual connections, the UE has already established dual links with the network, or the UE knows that it can establish dual connections with the current network.
  • the UE has the ability to establish dual connections, the UE has already established dual links with the network, or the UE knows that it can establish dual connections with the current network.
  • only dual connections are taken as an example, of course, multiple connections with more than two connections may also be used.
  • the process of this embodiment includes the following steps:
  • Step S801 The UE initiates two PDU Session Establishment Request message to the network.
  • the two PDU Sessions each carry redundant indication information, and may also include other configuration information (such as DNN and/or S- NSSAI)
  • the redundancy indication information may be at the PDU Session level or at the QoS flow level.
  • the redundancy indication information is at the PDU Session level, all QoS flows included in the two PDU Sessions are redundant QoS flows; when the redundancy indication information is at the QoS flow level, the two PDU Sessions Some of the included QoS flows are redundant QoS flows and the others are non-redundant QoS flows.
  • Step S802 After the network decides to establish a PDU Session for the two PDU Sessions, it establishes redundant PDU Sessions or redundant QoS flows on different RAN nodes according to the redundancy indication information configured in the PDU Session.
  • the network reads the redundancy indication information in the PDU Session establishment request message, and can learn the mutual redundancy relationship between the two PDU Sessions.
  • the network When the redundancy indication information is at the PDU Session level, the network establishes the two PDU Sessions on different RAN nodes respectively, and the type of each PDU Session is a Non-split PDU Session type.
  • the bearer type of all QoS flows of one PDU Session is MN terminated MCG bearer; the bearer type of all QoS flows of another PDU Session is SN terminated SCG bearer.
  • the network establishes the redundant QoS flow on different RAN nodes, and the type of each PDU Session can be a split PDU Session type.
  • the bearer type of the redundant QoS flow of one PDU Session is MN terminated MCG bearer; the bearer type of the redundant QoS flow of another PDU Session is SN terminated SCG bearer.
  • the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes a number of instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the present invention.
  • a redundant PDU Session configuration device which is used to implement the above-mentioned embodiments and preferred implementations, and what has been described will not be repeated.
  • the terms “module” and “unit” can be a combination of software and/or hardware that implements predetermined functions.
  • the devices described in the following embodiments are preferably implemented by software, hardware or a combination of software and hardware is also possible and conceived.
  • FIG. 9 is a structural block diagram of a redundant PDU Session configuration device according to an embodiment of the present invention. As shown in FIG. 9, the device includes an acquisition module 10 and a configuration module 20.
  • the obtaining module 10 is configured to obtain the first redundancy indication information for establishing or modifying the PDU Session and/or QoS flow.
  • the configuration module 20 is configured to configure the redundant PDU Session and/or redundant QoS flow on the corresponding RAN node according to the first redundancy indication information.
  • the first redundancy indication information is PDU Session level redundancy indication information, or the first redundancy indication information is QoS flow level redundancy indication information. It is used to indicate whether the PDU Session and/or QoS flow is a redundant PDU Session and/or redundant QoS flow; or it is used to indicate that the redundant PDU Session and/or redundant QoS flow is configured to the corresponding RAN node.
  • the acquiring module 10 may further include a first acquiring unit 101.
  • the first obtaining unit 101 is configured to obtain the first redundancy indication information for establishing or modifying the PDU Session and/or QoS flow from the core network through the RAN master node.
  • the configuration module 20 may further include a first configuration unit 201.
  • the first configuration unit 201 is configured to configure the redundant PDU Session and/or redundant QoS flow on the RAN master node, or configure the redundant PDU Session and/or redundant QoS flow on the RAN secondary node. Node.
  • the obtaining module 10 may further include a second obtaining unit 102.
  • the second acquiring unit 102 is configured to acquire the first redundancy indication information for establishing a PDU Session and/or QoS flow from the source RAN master node through the target RAN master node.
  • the configuration module 20 may further include a second configuration unit 202.
  • the second configuration unit 202 is configured to configure the redundant PDU Session and/or redundant QoS flow to the target RAN master node, or configure the redundant PDU Session and/or redundant QoS flow to the target On the RAN secondary node.
  • the device for configuring the redundant PDU Session may further include the sending module 30.
  • the sending module 30 is configured to send the establishment or modification of the PDU Session and/or QoS flow to the RAN secondary node through the RAN primary node before configuring the redundant PDU Session and/or redundant QoS flow on the RAN secondary node.
  • the second redundant indication information of the flow may be further included in the device for configuring the redundant PDU Session.
  • the second redundancy indication information is PDU Session level redundancy indication information, or the second redundancy indication information is QoS flow level redundancy indication information.
  • the second redundancy indication information is used to indicate whether the PDU Session and/or QoS flow are redundant PDU Session and/or redundant QoS flow.
  • the embodiment of the present invention also provides a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in the foregoing method embodiment when running.
  • the foregoing storage medium may include, but is not limited to: U disk, Read-Only Memory (Read-Only Memory, ROM for short), Random Access Memory (Random Access Memory, RAM for short), Various media that can store computer programs, such as mobile hard disks, magnetic disks, or optical disks.
  • An embodiment of the present invention also provides an electronic device, including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute the steps in any of the foregoing method embodiments.
  • the aforementioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the aforementioned processor, and the input-output device is connected to the aforementioned processor.
  • modules or steps of the present invention can be implemented by a general computing device. They can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Above, alternatively, they can be implemented with program codes executable by the computing device, so that they can be stored in the storage device for execution by the computing device, and in some cases, can be executed in a different order than here. Perform the steps shown or described, or fabricate them into individual integrated circuit modules, or fabricate multiple modules or steps of them into a single integrated circuit module to achieve. In this way, the present invention is not limited to any specific combination of hardware and software.

Landscapes

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

Abstract

本发明提供了一种冗余PDU Session的配置方法及装置，该方法包括：获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息；根据所述第一冗余指示信息，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上。在本发明中，通过获取建立或修改PDU Session和/或QoS flow的冗余指示信息，并根据该冗余指示信息将冗余PDU Session和/或QoS flow的配置至相应的RAN节点上，从而可以实现用户面多连接的建立和修改。

Description

冗余协议数据单元会话的配置方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种冗余PDU Session的配置方法及装置。
背景技术
移动通信系统包括移动用户设备(User Equipment，UE)和网络设备(Network)，其中网络设备又包括无线接入网(Radio Access Network，RAN)和核心网(Core Network，CN)。RAN包括：1个或多个小区组(Cell group)，或1个或多个基站，或1个或多个节点B(Node B)。在5G系统中，CN是指5G核心网(5G Core)，其包括：接入和移动管理功能(Access and Mobility Management Function，AMF)、用户面功能(User Plane Function，UPF)、系统管理功能(System Management Function，SMF)等网元。
在双连接系统中，UE与网络设备建立了2个或2个以上的连接。如图1所示，CN(核心网的UPF网元)与RAN的两个小区组分别建立了连接，此时的RAN包括主节点(Master node，MN)和辅节点(Secondary node，SN)。
在5G应用场景的研究报告3GPP TR23.725的Solution 1中提出了基于双连接的冗余用户面路径的方案。具体内容可见3GPP协议的描述，如图2所示。
UE启动建立2个冗余的会话(redundant PDU Session)，并为每个会话配置不同的DNN和S-NSSAI组合。如图3所示。本发明是针对冗余的会话，所以在本发明中，将冗余的会话也简称为会话，即，本发明中的PDU Session指的是redundant PDU Session。
SMF决定所述会话能否建立。SMF做此决定的依据是S-NSSA、DNN、 用户授权和本地政策配置等组合。SMF决定采用RSN区别所述PDU session，哪个采用MN(master NG-RAN)或SN发送用户面数据。本发明中将PDU Session配置在MN(或者SN)上，是指该PDU Session的用户数据在MN或者SN上发送。如图3所述，一个PDU Session的用户面建立在UPF1上，另一个PDU Session的用户面建立在UPF2上。
在现有技术中，尚未提供如何实现多个用户面连接的技术方案，因此本发明提供了一种可实现多个用户面连接的建立和修改技术方案。
发明内容
本发明实施例提供了一种冗余PDU Session的配置方法及装置，以至少解决相关技术中如何实现多个用户面连接的问题。
根据本发明的一个实施例，提供了一种冗余PDU Session的配置方法，包括：获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息；根据所述第一冗余指示信息，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上。
其中，所述第一冗余指示信息为PDU Session级别的冗余指示信息，或所述第一冗余指示信息为QoS flow级别的冗余指示信息。
其中，所述第一冗余指示信息包括至少以下之一：指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow；指示所述冗余PDU Session和/或冗余QoS flow配置到对应的RAN节点。
其中，获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息，包括：RAN主节点从核心网获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息。
其中，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上，包括：将所述冗余PDU Session和/或冗余QoS flow配置到的所述RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上。
其中，获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息，包括：目标RAN主节点从源RAN主节点获取建立PDU Session和/或QoS flow的第一冗余指示信息。
其中，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上，包括：将所述冗余PDU Session和/或冗余QoS flow配置到的所述目标RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到目标RAN辅节点上。
其中，将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上之前，还包括：所述RAN主节点向所述RAN辅节点发送建立或修改PDU Session和/或QoS flow的第二冗余指示信息。
其中，所述第二冗余指示信息为PDU Session级别的冗余指示信息，或所述第二冗余指示信息为QoS flow级别的冗余指示信息。
其中，所述第二冗余指示信息用于指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow。
其中，如果所述PDU Session是新建立的，获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息之前，还包括：核心网接收UE发起的建立多个PDU Session的请求，其中，每个PDU Session都携带PDU Session级别或QoS级别的冗余指示信息；所述核心网确定建立所述多个PDU Session，并向RAN主节点MN发送PDU Session的建立请求消息，并携带所述PDU Session级别或QoS级别的冗余指示信息。
其中，一个冗余PDU Session的所有QoS flow均为冗余QoS flow，所述PDU Session的类型为Non-split PDU Session，其包含的全部QoS flow所对应的承载配置在一个相同的RAN节点上。
其中，冗余PDU Session和/或冗余QoS flow配置到一个RAN节点上是指其对应承载的高层和低层均配置在该RAN节点上。
其中，当冗余PDU Session和/或冗余QoS flow配置到RAN主节点上，则对应的承载类型为MN terminated MCG bearer。
其中，当冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上，则对应的承载类型为SN terminated SCG bearer。
根据本发明的另一个实施例，提供了一种冗余PDU Session的配置装置，包括：获取模块，设置为获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息；配置模块，设置为根据所述第一冗余指示信息，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上。
其中，所述第一冗余指示信息为PDU Session级别的冗余指示信息，或所述第一冗余指示信息为QoS flow级别的冗余指示信息。
其中，所述第一冗余指示信息包括至少以下之一：指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow；指示所述冗余PDU Session和/或冗余QoS flow配置到对应的RAN节点。
其中，获取模块包括：第一获取单元，设置为通过RAN主节点从核心网获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息。
其中，配置模块包括：第一配置单元，设置为将所述冗余PDU Session和/或冗余QoS flow配置到的所述RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上。
其中，获取模块包括：第二获取单元，设置为通过目标RAN主节点从源RAN主节点获取建立PDU Session和/或QoS flow的第一冗余指示信息。
其中，配置模块包括：第二配置单元，设置为将所述冗余PDU Session和/或冗余QoS flow配置到的所述目标RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到目标RAN辅节点上。
其中，该装置还包括：发送模块，设置为在将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上之前，通过所述RAN主节点向所述RAN辅节点发送建立或修改PDU Session和/或QoS flow的第二冗余指示信息。
其中，所述第二冗余指示信息为PDU Session级别的冗余指示信息， 或所述第二冗余指示信息为QoS flow级别的冗余指示信息。
其中，所述第二冗余指示信息用于指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow。
根据本发明的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述方法实施例中的步骤。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述方法实施例中的步骤。
在本发明上述实施例，通过获取建立或修改PDU Session和/或QoS flow的冗余指示信息，并根据该冗余指示信息将冗余PDU Session和/或QoS flow的配置至相应的RAN节点上，从而可以实现用户面多连接的建立和修改。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的双连接网络架构示意图；
图2是根据相关技术的单装置高层架构示意图；
图3是根据相关技术的解决方案架构示意图；
图4是根据本发明实施例的冗余PDU Session的配置方法流程图；
图5是根据本发明实施例的建立冗余PDU Session/冗余QoS flow的流程图；
图6是根据本发明实施例的修改冗余PDU Session/冗余QoS flow的流程图；
图7是根据本发明实施例的切换场景中建立冗余PDU Session/冗余QoS flow的流程图；
图8是根据本发明实施例的发起建立冗余PDU Session/冗余QoS flow的流程图
图9是根据本发明实施例的冗余PDU Session的配置的结构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种冗余PDU Session的配置方法，图1是根据本发明实施例的流程图，如图4所示，该流程包括如下步骤：
步骤S402，获取建立或修改PDU Session和/或QoS flow的冗余指示信息；
步骤S404，根据所述冗余指示信息，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上。
在上述步骤S402中，RAN主节点MN从核心网获得需要建立或修改的PDU Session和/或QoS flow的冗余指示信息。对于切换(handover)场景，目标RAN主节点Target MN从原RAN主节点Source MN分别获得需要建立的PDU Session和/或QoS flow的冗余指示信息。
在上述实施例中，所述冗余指示信息可以是PDU Session级别也可以是QoS flow级别，可以指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow，也可以指示所述冗余PDU Session和/或冗余QoS flow配置到某个RAN节点。
在上述步骤S404中，当所述冗余指示信息指示所述冗余PDU Session 和/或冗余QoS flow配置到辅节点上，主节点向辅节点发送新的冗余指示信息，该冗余指示信息可以是PDU Session级别也可以是QoS flow级别，用于指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow。
在上述实施例中，一个冗余PDU Session的所有QoS flow都是冗余QoS flow，主节点不允许分离该PDU Session(即：该PDU Session的类型是Non-split PDU Session(非分离会话)，其包含的全部QoS flow所对应的承载必须配置在一个相同的RAN节点上)
在上述实施例中，冗余PDU Session和/或冗余QoS flow配置到一个RAN节点上，是指其对应承载的高层(SDAP，PDCP)和低层(RLC，MAC和物理层)都配置在该RAN节点上。
在上述实施例中，当冗余PDU Session和/或冗余QoS flow配置到主节点上，则对应的承载类型为MN terminated MCG bearer，当冗余PDU Session和/或冗余QoS flow配置到辅节点上，则对应的承载类型为SN terminated SCG bearer。
在上述实施例中，如果所述PDU Session是新建立的，则在上述步骤S404之前，还包括如下步骤：
步骤1：UE向网络发起2个PDU Session建立/请求(此处以双连接为例，当然也可以是建立多个PDU Session建立/请求)，每个PDU Session都携带PDU Session级别或QoS级别的冗余指示信息。
步骤2：核心网决定建立所述2个PDU Session，核心网向RAN主节点MN发送PDU Session的建立请求消息，并携带PDU Session级别或QoS级别的冗余指示信息。
下面通过实施例对不同的应用场景进行具体描述。
实施例1：
本实施例具体描述了RAN建立冗余PDU Session和/或冗余QoS flow的过程，如图5所示，包括如下步骤：
步骤S501：RAN接收到核心网(CN，core network，在5G系统中，是指AMF，在4G系统中是指MME)发送的PDU Session Resource setup request消息，该消息中包含请求建立的1个或多个PDU Session，其中的每个PDU Session包含1个或多个QoS flow。所述PDU Session中的1个或多个PDU Session包含PDU Session级别的冗余指示，和/或所述PDU Session中的1个或多个PDU Session包含QoS flow级别的冗余指示。
在本实施例中，当某个PDU Session包含PDU Session级别的冗余指示信息，是指这个PDU Session是冗余PDU Session，此时该PDU Session的所包含的QoS flow都是冗余QoS flow。
在本实施例中，当某个PDU Session包含QoS flow级别的冗余指示信息，是指这个PDU Session的1个或多个QoS flow是冗余QoS flow，此时每个包含冗余指示信息的QoS flow就是冗余QoS flow。
步骤S502：RAN判断该PDU Session/QoS flow是否是冗余PDU Session/QoS flow。如果判断结果为否，则在本实施例中不做规定，直接执行步骤S507。如果判断结果为是，则执行步骤S503。
在本实施例中，当某个PDU Session包含PDU Session级别的冗余指示信息，则该PDU Session就是冗余PDU Session，其包含的所有QoS flow都是冗余QoS flow，此时该PDU Session不包含QoS flow级别的冗余指示信息。
在本实施例中，冗余指示信息可以是PDU Session级别的，也可以是QoS flow级别的。核心网配置PDU Session级别和/或QoS flow级别的冗余指示信息，并发送到RAN。于是，RAN可以获知哪个或哪些PDU Session是冗余PDU Session，以及哪个或哪些QoS flow是冗余QoS flow。
步骤S503，进一步判断该冗余PDU Session/QoS flow是建立在MN上，还是建立在SN。如果是建立在MN上，则执行步骤S504，如果是建立在SN上，则执行步骤S505。
在本实施中，冗余指示信息的不同取值，可以采用RSN(redundant  sequence number，冗余序列号)来标识。分别代表了所对应的PDU Session或所对应的QoS flow需要配置在RAN的不同节点上。当RAN是双连接节点，其中一个节点是主节点(MN，master node)，另一个节点是辅节点(SN，Secondary node)，可以用RSN＝0表示所述冗余PDU Session/QoS flow需要配置在MN上，用RSN＝1表示所述冗余PDU Session/QoS flow需要配置在SN上。当RAN是多连接节点，其中一个节点是节点0(主节点),一个节点是节点1(辅节点1)，一个节点是节点2(辅节点2)，一个节点是节点3(辅节点3)，则用RSN＝0表示所述冗余PDU Session/QoS flow需要配置在MN上，用RSN＝1表示所述冗余PDU Session/QoS flow需要配置在辅节点1上，用RSN＝2表示所述冗余PDU Session/QoS flow需要配置在辅节点2上，用RSN＝3表示所述冗余PDU Session/QoS flow需要配置在辅节点3上。
在本实施例中，当某个PDU Session是冗余PDU Session，则其所包含的所有QoS flow都是冗余QoS flow。根据该冗余PDU Session的冗余指示信息，RAN将其配置为non-split PDU Session，即：RAN不允许该PDU session的QoS flow配置在不同的RAN节点上，而是将该PDU Session的全部QoS flow都配置在某一个RAN节点上。
在本实施例中，当某个QoS flow是冗余QoS flow，根据该冗余QoS flow的冗余指示信息，RAN将该QoS flow配置在某个RAN节点上。
在本实施例中，当多个冗余QoS flow属于同一个PDU Session，则所述冗余QoS flow配置相同的冗余指示信息(即：RSN取值相同，这些冗余QoS flow都配置在相同的RAN节点上)；另一方面，为了支持冗余QoS flow的配置灵活化，本发明也允许所述冗余QoS flow配置不同的冗余指示信息(即：RSN取值不同，这些冗余QoS flow允许配置在不同的RAN节点上)。
在本实施例中，RAN读取该请求消息，如果某个PDU Session/QoS有冗余指示信息，则该PDU Session/QoS为冗余PDU Session/冗余QoS  flow，再根据冗余指示信息的取值，RAN可以获知该PDU Session/QoS flow配置在某个节点上。
在本实施例中，将某个冗余PDU Session的全部QoS flow，或某个冗余QoS flow配置在某个RAN节点上，是指将所述QoS flow对应承载的高层(SDAP，PDCP)和低层(RLC，MAC和物理层)都配置在该RAN节点上。对于冗余PDU Session，其包含的QoS flow可以是多个，这些QoS flow可以配置在一个或多个承载上，则这些承载的高层和低层都必须配置在相同的所述RAN节点上。
步骤S504：将该冗余PDU Session/冗余QoS flow建立在主节点MN上，承载类型为MN terminated MCG bearer。
在3GPP Rel-15的5G多连接系统(MR-DC with 5GC)中，一个RAN节点是MN，另一个RAN节点是SN。如果用RSN＝0表示所述冗余PDU Session或冗余QoS flow需要配置在MN上，则对应的承载必须为MN terminated MCG bearer。用RSN＝1表示所述冗余PDU Session或冗余QoS flow需要配置在SN上，则对应的承载必须为SN terminated SCG bearer。
步骤S505：当所述冗余PDU Session和/或冗余QoS flow的冗余指示信息，要求其配置在辅节点上，则主节点向辅节点发送SN addition request message或SN modification request message消息中的IE“PDU Session Resource Setup Info–SN terminated”包含请求建立的1个或多个冗余PDU Session和/或冗余QoS flow的冗余指示信息及其他相关配置信息。
MN发送到SN的冗余指示信息可以是PDU Session级别的，也可以是QoS flow级别的。
针对某个冗余PDU Session或冗余QoS flow，MN发送到SN的冗余指示信息，可以不同于从核心网接收到的冗余指示信息。
一方面通过读取来自核心网某个PDU Session/QoS flow是否配置了冗余指示信息，RAN可以获知该PDU Session/QoS flow是否是冗余PDU Session/冗余QoS flow，另一方面通过读取某个PDU Session/QoS flow的 冗余指示信息的取值，RAN可以获知该PDU Session/QoS flow需要配置在哪个RAN节点上。
在该步骤S505的请求消息中，如果某个或某些PDU Session/QoS flow配置了冗余指示信息，则其为冗余PDU Session/冗余QoS flow，且其必须配置在SN上。因此，从MN发送到SN的冗余指示信息可以仅指示某个或某些PDU Session/QoS flow是否是冗余PDU Session/冗余QoS flow。
步骤S506：辅节点接收到主节点发送的SN addition request message或SN modification request message，消息中包含的冗余指示信息指示所述冗余PDU Session和/或冗余QoS flow配置在所述辅节点上，则辅节点将其对应的承载类型配置为SN terminated SCG bearer，而且辅节点不允许改变该承载类型直到冗余信息指示改变。
消息中的冗余PDU Session和/或冗余QoS flow的冗余指示信息是重要的，因为，如果无此冗余指示信息，SN很可能将这些PDU Session/QoS flow的承载配置为SN terminated split bearer或SN terminated MCG bearer。
步骤S507：对下一个接收到的PDU Session/冗余QoS flow重复执行上述的步骤。
实施例2：
本实施例描述了RAN修改冗余PDU Session和/或冗余QoS flow的过程。
对于某个配置为冗余PDU Session的PDU Session，5GC可以在该PDU Session建立时候配置其为冗余PDU Session，也是该PDU Session建立时候是普通PDU Session(即：不是冗余PDU Session)，随后地，5GC将该PDU Session修改为冗余PDU Session；随后地，5GC也可以将某个冗余PDU Session修改为普通PDU Session(即：不是冗余PDU Session)。
对于某个配置为冗余QoS flow的QoS flow，5GC可以在该QoS flow建立时候配置其为冗余QoS flow，也是该QoS flow建立时候是普通QoS flow(即：不是冗余QoS flow)，随后地，5GC将该QoS flow修改为冗余 QoS flow；随后地，5GC也可以将某个冗余QoS flow修改为普通QoS flow(即：不同冗余QoS flow)。
如图6所示，本实施例的方法流程包括如下步骤：
步骤S601：RAN接收到核心网发送的PDU Session Resource modify request消息，该消息中包括：修改1个或多个PDU Session的冗余指示信息的有无，和/或修改1个或多个QoS flow的冗余指示信息的取值。
所述修改PDU Session的冗余指示信息或修改QoS flow的冗余指示信息，包括：将某个/某些冗余PDU Session或冗余QoS flow修改为非冗余PDU Session或非冗余QoS flow(即：所述PDU Session或QoS flow不配置冗余指示信息)，或将某个/某些非冗余PDU Session或非冗余QoS flow修改为冗余PDU Session或冗余QoS flow(即：为所述PDU Session或QoS flow配置冗余指示信息)，或将某个/某些冗余PDU Session或冗余QoS flow的冗余指示信息的取值修改(如：RSN取值从0修改为1，或者RSN取值从0修改为1，即：该冗余PDU Session或冗余QoS flow从一个RAN节点重配置到另一个RAN节点)。
步骤S602：RAN判断该PDU Session/QoS flow修改后是否是冗余PDU Session/QoS flow。如果判断结果为否，则在本实施例中不做规定，直接执行步骤S607。如果判断结果为是，则执行步骤S603。
步骤S603：进一步判断该冗余PDU Session/QoS flow修改后是建立在MN上，还是建立在SN。如果是建立在MN上，则执行步骤S604，如果是建立在SN上，则执行步骤S605。
在本实施例中，RAN根据每个PDU Session和/或QoS flow修改后有无冗余指示信息，或修改后的新的冗余指示信息的取值，进行相应的配置。
将新的冗余PDU Session和/或冗余QoS flow配置到冗余指示信息所指示的RAN节点上，或者将已有的冗余PDU Session和/或已有的QoS flow配置到修改后的冗余指示信息所指示的新的RAN节点上，而对于从冗余PDU Session和/或冗余QoS flow修改为非冗余PDU Session和/或非冗余 QoS flow，RAN可以修改或不修改其配置。
步骤S604：将该冗余PDU Session/冗余QoS flow建立在主节点MN上，承载类型为MN terminated MCG bearer。
步骤S605：当所述冗余PDU Session和/或冗余QoS flow的冗余指示信息，要求其配置在辅节点上，则主节点向辅节点发送SN modification request message，消息中的信息单元IE“PDU Session Resource Modification Info–SN terminated”包括：修改1个或多个PDU Session的冗余指示信息的有无。
步骤S606：辅节点接收到主节点发送的SN modification request message，并进行相应的配置。
对于新配置了冗余指示信息的PDU Session和/或QoS flow，SN将其配置为SN terminated SCG bearer；对于原先是冗余PDU Session或冗余QoS flow但现在没有配置冗余指示信息的PDU Session或QoS flow，所述PDU Session或QoS flow是非冗余PDU Session或非冗余QoS flow，SN可以重新配置也可以不重新配置。
步骤S607：对下一个接收到的PDU Session/冗余QoS flow重复执行上述的步骤。
实施例3：
本实施例描述了切换(handover)过程中，原RAN节点向目标RAN节点传递冗余PDU Session和/或冗余QoS flow的流程。
由于UE的移动性，或者基站信号的波动，可能触发至少三种类型的切换：MN不改变的SN切换(SN change)，SN不改变的MN切换(MN handover without SN change)，MN和SN都切换(MN handover with SN change)，具体见3GPP TS37.340。
原NG-RAN node(source MN)将每个PDU Session和/或QoS flow的冗余指示信息，从原节点(source NG-RAN)传递到目标节点(Target NG-RAN)，该冗余指示信息的传递，如果是基于NG接口的切换则通过 NG接口，如果是基于Xn接口的切换则通过Xn接口。
如图7所示，本实施例的流程包括如下步骤：
步骤S701：原RAN节点发送到目标RAN节点的handover request消息中，对于每一个冗余PDU Session和/或冗余QoS flow都包括一个冗余指示信息。
与实施例1相比，在本实施例中，每个PDU Session和/或QoS flow的冗余指示信息，从原RAN节点发送到目标RAN节点。该冗余指示信息通过handover request消息发送。
对于MR-DC with 5GC系统，原RAN节点就是原MN节点(Source MN)，目标RAN节点就是目标MN节点(Target MN)。即：handover request消息从Source MN发送到Target MN。
步骤S702：RAN判断该PDU Session/QoS flow是否是冗余PDU Session/QoS flow。如果判断结果为否，则在本实施例中不做规定，直接执行步骤S707。如果判断结果为是，则执行步骤S703。
步骤S703：进一步判断该冗余PDU Session/QoS flow是建立在MN上，还是建立在SN。如果是建立在MN上，则执行步骤S704，如果是建立在SN上，则执行步骤S705。
目标MN根据每个冗余PDU Session和/或每个冗余QoS flow的冗余指示信息，将所述冗余PDU Session和/或所述冗余QoS flow配置在相应的RAN目标主节点或目标辅节点上。
与实施例1相比，本实施例中的目标MN类似于实施例1中的RAN。
步骤S704：将该冗余PDU Session/冗余QoS flow建立在主节点MN上，承载类型为MN terminated MCG bearer。
步骤S705：当所述冗余PDU Session和/或冗余QoS flow的冗余指示信息，要求其配置在目标辅节点上，则目标主节点向目标辅节点发送SN addition request message，消息中的IE“PDU Session Resource Setup Info– SN terminated”包含请求建立的1个或多个冗余PDU Session和/或冗余QoS flow的冗余指示信息及其他相关配置信息。
与实施例1相比，在本实施例中，目标主节点取代了主节点，目标辅节点取代了辅节点，消息中不包括SN modification request消息。其他都相同。
MN发送到SN的冗余指示信息可以是PDU Session级别的，也可以是QoS flow级别的。
针对某个冗余PDU Session或冗余QoS flow，目标MN发送到目标SN的冗余指示信息，可以不同于从原主节点接收到的冗余指示信息。
一方面通过读取来自原主节点的某个PDU Session/QoS flow是否配置了冗余指示信息，目标主节点可以获知该PDU Session/QoS flow是否是冗余PDU Session/冗余QoS flow，另一方面通过读取某个PDU Session/QoS flow的冗余指示信息的取值，目标主节点可以获知该PDU Session/QoS flow需要配置在哪个目标RAN节点上。
在该步骤S705的请求消息中，如果某个/某些PDU Session/QoS flow配置了冗余指示信息，则其为冗余PDU Session/冗余QoS flow，且其必须配置在SN上。因此，从MN发送到SN的冗余指示信息可以仅指示某个/某些PDU Session/QoS flow是否是冗余PDU Session/冗余QoS flow。
步骤S706：目标辅节点接收到目标主节点发送的SN addition request message或SN modification request message，消息中包含的冗余指示信息指示所述冗余PDU Session和/或冗余QoS flow配置在所述辅节点上，则辅节点将其对应的承载类型配置为SN terminated SCG bearer，而且辅节点不允许改变该承载类型直到冗余信息指示改变，修改冗余指示信息的过程可参见实施例2。
消息中的冗余PDU Session和/或冗余QoS flow的冗余指示信息是重要的，因为如果无此冗余指示信息，SN很可能将这些PDU Session/QoS flow的承载配置为SN terminated split bearer或SN terminated MCG bearer。
步骤S707：对下一个接收到的PDU Session/冗余QoS flow重复执行上述的步骤。
实施例4：
在本实施例中，UE发起冗余PDU Session或发起PDU Session中部分冗余QoS flow的建立请求。
在本实施例中，预设条件为，UE具备建立双连接的能力，UE已经与网络建立了双链接，或者UE已知其与当前网络可以建立双连接。为了描述方便，在本实施例中，仅是以双连接为例，当然也可以是多于两个连接的多连接。
如图8所示，本实施例的流程包括如下步骤：
步骤S801：UE向网络发起2个PDU Session的建立请求(PDU Session Establishment Request message)，这个两个PDUSession都分别带有冗余指示信息，还可以包括其他配置信息(如：DNN和/或S-NSSAI)
所述冗余指示信息可以是PDU Session级别的，也可以是QoS flow级别的。当冗余指示信息是PDU Session级别的，则所述两个PDU Session所包含的全部QoS flow都是冗余QoS flow；当冗余指示信息是QoS flow级别的，则所述两个PDU Session所包含的QoS flow中部分是冗余QoS flow而其他是非冗余QoS flow。
步骤S802：网络决定为所述2个PDU Session建立PDU Session后，根据所述PDU Session所配置的冗余指示信息，分别在不同的RAN节点上建立冗余PDU Session或冗余QoS flow。
网络读取PDU Session建立请求消息中的冗余指示信息，可以获知这两个PDU Session的相互冗余关系。
当冗余指示信息是PDU Session级别的，网络将所述2个PDU Session分别建立在不同的RAN节点上，每个PDU Session的类型都是Non-split PDU Session类型。在双连接网络中，1个PDU Session的全部QoS flow的承载类型是MN terminated MCG bearer；另一个PDU Session的全部QoS  flow的承载类型是SN terminated SCG bearer。
当冗余指示信息是QoS flow级别的，网络将冗余QoS flow分别建立在不同的RAN节点上，每个PDU Session的类型可以是split PDU Session类型。在双连接网络中，1个PDU Session的冗余QoS flow的承载类型是MN terminated MCG bearer；另一个PDU Session的冗余QoS flow的承载类型是SN terminated SCG bearer。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种冗余PDU Session的配置装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”和“单元”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图9是根据本发明实施例的冗余PDU Session的配置装置的结构框图，如图9所示，该装置包括获取模块10和配置模块20。
获取模块10设置为获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息。配置模块20设置为根据所述第一冗余指示信息，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上。
所述第一冗余指示信息为PDU Session级别的冗余指示信息，或所述第一冗余指示信息为QoS flow级别的冗余指示信息。用于指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow；或用 于指示所述冗余PDU Session和/或冗余QoS flow配置到对应的RAN节点。
在上述实施例中，获取模块10还可以包括第一获取单元101。第一获取单元101设置为通过RAN主节点从核心网获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息。
在上述实施例中，配置模块20还可以包括第一配置单元201。第一配置单元201设置为将所述冗余PDU Session和/或冗余QoS flow配置到的所述RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上。
在上述实施例中，获取模块10还可以还包括第二获取单元102。第二获取单元102设置为通过目标RAN主节点从源RAN主节点获取建立PDU Session和/或QoS flow的第一冗余指示信息。
在上述实施例中，配置模块20还可以包括第二配置单元202。第二配置单元202设置为将所述冗余PDU Session和/或冗余QoS flow配置到的所述目标RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到目标RAN辅节点上。
在上述实施例中，该冗余PDU Session的配置装置还可以包括发送模块30。发送模块30设置为在将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上之前，通过所述RAN主节点向所述RAN辅节点发送建立或修改PDU Session和/或QoS flow的第二冗余指示信息。
所述第二冗余指示信息为PDU Session级别的冗余指示信息，或所述第二冗余指示信息为QoS flow级别的冗余指示信息。所述第二冗余指示信息用于指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow。
本发明的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random  Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (27)

  1. 一种冗余协议数据单元会话PDU Session的配置方法，包括：
    获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息；
    根据所述第一冗余指示信息，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上。
  2. 根据权利要求1所述的方法，其中，所述第一冗余指示信息为PDU Session级别的冗余指示信息，或所述第一冗余指示信息为QoS flow级别的冗余指示信息。
  3. 根据权利要求2所述的方法，其中，所述第一冗余指示信息包括至少以下之一：
    指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow；
    指示所述冗余PDU Session和/或冗余QoS flow配置到对应的RAN节点。
  4. 根据权利要求1所述的方法，其中，获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息，包括：
    RAN主节点从核心网获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息。
  5. 根据权利要求4所述的方法，其中，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上，包括：
    将所述冗余PDU Session和/或冗余QoS flow配置到的所述RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上。
  6. 根据权利要求1所述的方法，其中，获取建立或修改PDU  Session和/或QoS flow的第一冗余指示信息，包括：
    目标RAN主节点从源RAN主节点获取建立PDU Session和/或QoS flow的第一冗余指示信息。
  7. 根据权利要求6所述的方法，其中，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上，包括：
    将所述冗余PDU Session和/或冗余QoS flow配置到的所述目标RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到目标RAN辅节点上。
  8. 根据权利要求5或7所述的方法，其中，将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上之前，还包括：
    所述RAN主节点向所述RAN辅节点发送建立或修改PDU Session和/或QoS flow的第二冗余指示信息。
  9. 根据权利要求8所述的方法，其中，所述第二冗余指示信息为PDU Session级别的冗余指示信息，或所述第二冗余指示信息为QoS flow级别的冗余指示信息。
  10. 根据权利要求9所述的方法，其中，所述第二冗余指示信息设置为指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow。
  11. 根据权利要求1所述的方法，其中，如果所述PDU Session是新建立的，获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息之前，还包括：
    核心网接收UE发起的建立多个PDU Session的请求，其中，每个PDU Session都携带PDU Session级别或QoS级别的冗余指示信息；
    所述核心网确定建立所述多个PDU Session，并向RAN主节点MN发送PDU Session的建立请求消息，并携带所述PDU Session级别或QoS级别的冗余指示信息。
  12. 根据权利要求1所述的方法，其中，一个冗余PDU Session的所有QoS flow均为冗余QoS flow，所述PDU Session的类型为Non-split PDU Session，其包含的全部QoS flow所对应的承载配置在一个相同的RAN节点上。
  13. 根据权利要求1所述的方法，其中，冗余PDU Session和/或冗余QoS flow配置到一个RAN节点上是指其对应承载的高层和低层均配置在该RAN节点上。
  14. 根据权利要求1所述的方法，其中，当冗余PDU Session和/或冗余QoS flow配置到RAN主节点上，则对应的承载类型为MN terminated MCG bearer。
  15. 根据权利要求1所述的方法，其中，当冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上，则对应的承载类型为SN terminated SCG bearer。
  16. 一种冗余协议数据单元会话PDU Session的配置装置，包括：
    获取模块，设置为获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息；
    配置模块，设置为根据所述第一冗余指示信息，将冗余PDU Session和/或冗余QoS flow配置在相应的RAN节点上。
  17. 根据权利要求16所述的装置，其中，所述第一冗余指示信息为PDU Session级别的冗余指示信息，或所述第一冗余指示信息为QoS flow级别的冗余指示信息。
  18. 根据权利要求17所述的装置，其中，所述第一冗余指示信息包括至少以下之一：
    指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow；
    指示所述冗余PDU Session和/或冗余QoS flow配置到对应的RAN节点。
  19. 根据权利要求16所述的装置，其中，获取模块包括：
    第一获取单元，设置为通过RAN主节点从核心网获取建立或修改PDU Session和/或QoS flow的第一冗余指示信息。
  20. 根据权利要求19所述的装置，其中，配置模块包括：
    第一配置单元，设置为将所述冗余PDU Session和/或冗余QoS flow配置到的所述RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到RAN辅节点上。
  21. 根据权利要求16所述的装置，其中，获取模块包括：
    第二获取单元，设置为通过目标RAN主节点从源RAN主节点获取建立PDU Session和/或QoS flow的第一冗余指示信息。
  22. 根据权利要求21所述的装置，其中，配置模块包括：
    第二配置单元，设置为将所述冗余PDU Session和/或冗余QoS flow配置到的所述目标RAN主节点上，或将所述冗余PDU Session和/或冗余QoS flow配置到目标RAN辅节点上。
  23. 根据权利要求20或22所述的装置，其中，还包括：
    发送模块，设置为在将所述冗余PDU Session和/或冗余QoS flow 配置到RAN辅节点上之前，通过所述RAN主节点向所述RAN辅节点发送建立或修改PDU Session和/或QoS flow的第二冗余指示信息。
  24. 根据权利要求23所述的装置，其中，所述第二冗余指示信息为PDU Session级别的冗余指示信息，或所述第二冗余指示信息为QoS flow级别的冗余指示信息。
  25. 根据权利要求24所述的装置，其中，所述第二冗余指示信息用于指示所述PDU Session和/或QoS flow是否为冗余PDU Session和/或冗余QoS flow。
  26. 一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至15任一项中所述的方法。
  27. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至15任一项中所述的方法。
PCT/CN2020/082591 2019-04-26 2020-03-31 冗余协议数据单元会话的配置方法及装置 WO2020216023A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20796435.4A EP3962165A4 (en) 2019-04-26 2020-03-31 REDUNDANT PROTOCOL DATA UNIT SESSION CONFIGURATION METHOD AND APPARATUS
US17/606,560 US12035168B2 (en) 2019-04-26 2020-03-31 Method and device for configuring redundant protocol data unit session

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910346241.4A CN111083742B (zh) 2019-04-26 2019-04-26 冗余协议数据单元会话的配置方法及装置
CN201910346241.4 2019-04-26

Publications (1)

Publication Number Publication Date
WO2020216023A1 true WO2020216023A1 (zh) 2020-10-29

Family

ID=70310306

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/082591 WO2020216023A1 (zh) 2019-04-26 2020-03-31 冗余协议数据单元会话的配置方法及装置

Country Status (3)

Country Link
EP (1) EP3962165A4 (zh)
CN (1) CN111083742B (zh)
WO (1) WO2020216023A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4210426A4 (en) * 2020-09-30 2023-11-15 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR PERFORMING DATA TRANSMISSION USING DUAL TERMINAL DEVICES
CN113015163A (zh) * 2021-03-05 2021-06-22 成都中科微信息技术研究院有限公司 一种提高ue接入5g-nr基站成功率的方法以及ue入网方法
WO2023019550A1 (en) * 2021-08-20 2023-02-23 Lenovo (Beijing) Limited Methods and apparatuses for supporting connectivity of multiple sns in mr-dc scenario

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109076628A (zh) * 2016-06-17 2018-12-21 华为技术有限公司 用于高移动性场景下的超可靠和低延迟通信的会话管理的方法和系统
CN109392023A (zh) * 2017-08-10 2019-02-26 北京三星通信技术研究有限公司 一种数据流的操作控制的方法及设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105704197B (zh) * 2014-11-28 2020-04-10 电信科学技术研究院 一种数据传输方法及系统
CN109075919B (zh) * 2016-04-19 2021-10-29 诺基亚技术有限公司 拆分承载双/多连接重传分集
US10448386B2 (en) * 2017-01-06 2019-10-15 Kt Corporation Method and apparatus for controlling redundant data transmission
KR102016728B1 (ko) * 2017-01-06 2019-09-02 주식회사 케이티 데이터 중복 전송을 제어하는 방법 및 그 장치
CN109246765B (zh) * 2017-06-13 2023-12-29 中兴通讯股份有限公司 一种用户面数据会话的管理方法和装置
US20180367288A1 (en) * 2017-06-16 2018-12-20 Huawei Technologies Co., Ltd. Dynamic activation and deactivation of packet duplication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109076628A (zh) * 2016-06-17 2018-12-21 华为技术有限公司 用于高移动性场景下的超可靠和低延迟通信的会话管理的方法和系统
CN109392023A (zh) * 2017-08-10 2019-02-26 北京三星通信技术研究有限公司 一种数据流的操作控制的方法及设备

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
3GPP TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS: "Study on enhancement of Ultra-Reliable Low-Latency Communication (URLLC) support in the 5G Core network", 3GPP TR 23.725 V16.1.0, 25 March 2019 (2019-03-25), pages 1 - 91, XP051722870 *
3GPP TR23.725
3GPP TS 37.340
SAMSUNG: "Supporting two NG-U tunnels for a single PDU Session", 3GPP TSG-RAN WG3 #103BIS R3-191497, 29 March 2019 (2019-03-29), XP051694951, DOI: 20200628192506X *
See also references of EP3962165A4

Also Published As

Publication number Publication date
US20220232413A1 (en) 2022-07-21
CN111083742B (zh) 2024-06-25
CN111083742A (zh) 2020-04-28
EP3962165A4 (en) 2022-12-28
EP3962165A1 (en) 2022-03-02

Similar Documents

Publication Publication Date Title
JP6988004B2 (ja) 集中型ユニットと分散型ユニットのアーキテクチャにおける通信方法および通信デバイス
WO2018145671A1 (zh) 跨系统的切换方法和装置、计算机存储介质
WO2020216023A1 (zh) 冗余协议数据单元会话的配置方法及装置
JP7175927B2 (ja) 無線ベアラ構成方法および装置
WO2019184651A1 (zh) 一种通信方法及装置
EP3820238B1 (en) Notification methods
KR102341580B1 (ko) 복제 전송을 위한 방법 및 장치
US11284458B2 (en) Handling of mapped EPS bearer context with duplicate EPS bearer ID
WO2014127677A1 (zh) 数据传输方法、装置及系统
WO2018233446A1 (zh) 数据传输方法、装置、系统、网元、存储介质及处理器
US11558925B2 (en) Notification method and device for execution of PDCP data recovery
CN108401273B (zh) 一种路由方法和装置
EP3836735A1 (en) Method and apparatus for restoring data radio bearer, and storage medium and electronic apparatus
JP6829308B2 (ja) セッション管理方法及びセッション管理ネットワーク要素
CN110636639A (zh) 一种会话管理方法及装置
WO2018010583A1 (zh) 网络系统
JP7123138B2 (ja) 通信方法及び通信装置
WO2021129018A1 (zh) 网络连接的重建立方法及装置、存储介质、电子装置
WO2021032216A1 (zh) 冗余会话建立方法及装置、无线承载建立方法及装置、节点、终端、介质
WO2019119236A1 (zh) 网络重定向方法及终端、接入网设备、移动管理设备
CN113950121B (zh) 一种上下文恢复方法及装置
WO2022078867A1 (en) Methods, apparatuses and computer program for data transmission in inactive state
US12035168B2 (en) Method and device for configuring redundant protocol data unit session
CN109587756B9 (zh) 用于网络接入的方法和设备
WO2018076215A1 (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: 20796435

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020796435

Country of ref document: EP

Effective date: 20211126