Communication method, device and system, electronic equipment, storage medium and program product

Abstract

The invention relates to the technical field of communication, and particularly provides a communication method, device and system, electronic equipment, a storage medium and a program product. According to the session establishment method and device, when the first communication device receives the request for acquiring the first strategy, the session type of the established session can be indicated in the sent first strategy, and therefore it can be guaranteed that terminals belonging to the same DualSteer device can establish sessions of the same session type. And the third communication equipment can also manage and control the session establishment process based on the session type carried in the request, so that the situation that the session types of the DualSteer associated terminals are inconsistent is avoided.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method and device, a system, an electronic device, a storage medium and a program product. Background Art

[0002] DualSteer means that a terminal or device can simultaneously connect to multiple Radio Access Technology types (Radio Access Technology type, RAT type). A DualSteer device can be considered to be composed of two terminals (UE), and the two UEs can access the network through two 3GPPs respectively to implement DualSteer. In this way, the two terminals establish PDU sessions through different RATs respectively. The core network can establish PDU sessions for the two terminals respectively to associate them, which is regarded as a dual-steering session. At the same time, the same address is assigned to the two PDU sessions to form multi-stream data transmission.

[0003] However, for the two DualSteer terminals, if the same address is to be assigned to the PDU sessions established for multi-stream transmission, the session types of the two PDU sessions must be the same. In other words, if the session types of the two PDU sessions are different, the same address cannot be assigned, and the excellent transmission effect of DualSteer multi-stream transmission cannot be exerted. Therefore, how to achieve the same session type for the terminals in the DualSteer device is a problem that needs to be solved. Summary of the invention

[0004] The present disclosure is proposed in view of the above problems. The present disclosure provides a communication method and device, a system, an electronic device, a storage medium and a program product.

[0005] According to one aspect of the present disclosure, a communication method is provided, where a first communication device performs a first operation, where the first operation includes at least one of the following:

[0006] receiving a first request, wherein the first request includes first information, and the first request is used to request obtaining a first policy;

[0007] Sending second information; wherein the second information includes the first strategy;

[0008] The first policy includes a first session type.

[0009] According to another aspect of the present disclosure, another communication method is provided, where a third communication device performs a third operation, and the third operation includes at least one of the following:

[0010] receiving a fourth request, wherein the fourth request carries a second session type;

[0011] Request or obtain seventh information;

[0012] Sending a fourth response, the fourth response including at least one of the following:

[0013] First session type;

[0014] PDU session establishment accept;

[0015] PDU session establishment rejected;

[0016] PDU session establishment rejection reason.

[0017] According to another aspect of the present disclosure, a communication device is provided, including a transceiver unit, wherein the transceiver unit is configured to perform at least one of the following:

[0018] receiving a first request, wherein the first request includes first information, and the first request is used to request obtaining a first policy;

[0019] Sending second information; wherein the second information includes the first strategy;

[0020] The first policy includes a first session type.

[0021] According to another aspect of the present disclosure, another communication device is provided, including a transceiver unit, wherein the transceiver unit is configured to perform at least one of the following:

[0022] receiving a fourth request, wherein the fourth request carries a second session type;

[0023] Request or obtain seventh information;

[0024] Sending a fourth response, the fourth response including at least one of the following:

[0025] First session type;

[0026] PDU session establishment accept;

[0027] PDU session establishment rejected;

[0028] PDU session establishment rejection reason.

[0029] According to another aspect of the present disclosure, there is provided a communication system, comprising:

[0030] A first communication device, configured to implement a communication method executed by the first communication device;

[0031] The third communication device is used to implement the communication method executed by the third communication device.

[0032] According to another aspect of the present disclosure, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the method described in any one of the above embodiments.

[0033] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, the method described in any of the above embodiments is implemented.

[0034] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the method described in any one of the above embodiments is implemented.

[0035] As described in detail below, according to a communication method and apparatus, system, electronic device, storage medium and program product of an embodiment of the present disclosure, in the present disclosure, when the first communication device receives a request to obtain a first policy, it can indicate the session type of the established session in the sent first policy, so that it can ensure that terminals belonging to the same DualSteer device can establish sessions of the same session type. In addition, the third communication device can also manage and control the session establishment process based on the session type carried in the request to avoid the situation where the DualSteer associated terminal session type is inconsistent.

[0036] It is to be understood that both the foregoing general description and the following detailed description are exemplary, and are intended to provide further explanation of the technology as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above and other purposes, features and advantages of the present disclosure will become more apparent by describing the embodiments of the present disclosure in more detail in conjunction with the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation of the present disclosure. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

[0038] Figure 1 The present invention is a block diagram of a wireless communication system to which the embodiments of the present disclosure can be applied.

[0039] Figure 2 A flow chart of a communication method provided in an embodiment of the present disclosure.

[0040] Figure 3 An interactive schematic diagram of a registration information acquisition process provided in an embodiment of the present disclosure.

[0041] Figure 4An interactive flow chart of a policy selection process during a PDU session establishment process provided by an embodiment of the present disclosure.

[0042] Figure 5 A schematic diagram of DualSteer multi-stream transmission provided in an embodiment of the present disclosure.

[0043] Figure 6 A flowchart of another communication method provided by an embodiment of the present disclosure.

[0044] Figure 7 A flow chart of another communication method provided by the embodiment of the present disclosure

[0045] Figure 8 A flowchart of another communication method provided by an embodiment of the present disclosure.

[0046] Fig. 9 A structural block diagram of a communication device provided in an embodiment of the present disclosure.

[0047] Fig.10 A structural block diagram of another communication device provided in an embodiment of the present disclosure.

[0048] Fig.11 A structural block diagram of a communication system provided in an embodiment of the present disclosure.

[0049] Fig.12 A hardware block diagram of an electronic device provided in an embodiment of the present disclosure.

[0050] Fig.13 A schematic diagram of a computer-readable storage medium provided for an embodiment of the present disclosure. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present disclosure more obvious, the exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited to the exemplary embodiments described here.

[0052] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship. "And / or" in the specification and claims represents at least one of the connected objects, for example, "A and / or B" covers three schemes, namely, scheme one: including A and excluding B; scheme two: including B and excluding A; scheme three: including both A and B.

[0053] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies. The following description describes a New Radio (NR) system for example, and NR terms are used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system.

[0054] Figure 1 FIG. 1 is a block diagram of a wireless communication system to which the embodiments of the present disclosure can be applied. Figure 1As shown, the wireless communication system includes a terminal 11 and a network side device 12 . Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) equipment, a robot, a wearable device (Wearable Device), a vehicle-mounted equipment (Vehicle User Equipment, VUE), a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home equipment with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal computer (personal computer, PC), a teller machine or a self-service machine and other terminal side devices, and the wearable device includes: a smart watch, a smart bracelet, a smart headset, a smart glasses, a smart jewelry (smart bracelet, a smart bracelet, a smart ring, a smart necklace, a smart anklet, a smart anklet, etc.), a smart wristband, a smart clothing, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network device, a radio access network (RAN), a radio access network function or a radio access network unit.The access network device may include a base station, a wireless local area network (WLAN) access point or a wireless fidelity (WiFi) node, etc. The base station may be called a node B, an evolved node B (eNB), an access point, a base transceiver station (RTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home node B, a home evolved node B, a transmission and reception point (TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unfed Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0055] In the present disclosure, the first communication device may be a PCF, or any one of a core network device or an access network device. The second communication device may be a UDM, or any one of a core network device or an access network device. The third communication device may be an SMF, or any one of a core network device or an access network device.

[0056] The application scenario of the present disclosure is a communication scenario involving multiple access technologies.

[0057] Specifically, multiple access technology means that the terminal or device accesses the network through multiple radio access technology types RAT (Radio Access Technology) type. The specific definition of RAT type is as follows: Identifies the access network transmission technology used for 3GPP access and non-3GPP access, such as NR, NB-IOT, Untrusted non-3GPP, Trusted non-3GPP, Trusted IEEE 802.11non-3GPP access, Wireline, Wireline-cable, Wireline-BBF, etc. For example, a terminal accesses the 5G network through a 3GPP access, and also accesses the 6G network through another 3GPP access. Or, two terminals under a device access the 5G and 6G networks respectively. For example, terminal A and terminal B are associated with each other and are two terminals in a dual-direction device, where terminal A accesses the 5G network through 3GPP access, and terminal B accesses the 6G network through 3GPP access.

[0058] The present disclosure has no special restrictions on the specific network accessed by the terminal's multiple access technology, or on the specific RAT type. The network type (also referred to as the type of network system), or access technology, or RAT type, or first access, or second access, etc. involved in the present disclosure may include but are not limited to: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial communication network (Non-Terrestrial) The present invention relates to wireless networks, NTN systems, UMTS systems, WLAN systems, WiFi systems, 5G systems, 6G systems, NB-IOT (Narrowband Internet of Things), untrusted non-3GPP access, trusted non-3GPP access, Trusted IEEE802.11, non-3GPP access, Wireline, Wireline-cable, Wireline-BBF or other communication systems, etc., not to be exhaustive.

[0059] It should be noted that communication scenarios involving multiple access technologies may include separate multiple access communication scenarios, such as a terminal initiating a multiple access session establishment request to establish a session in multiple access modes; they may also include communication scenarios that may involve multiple access technologies in single access scenarios, such as two terminals under one device requesting to establish two different sessions in two different access modes. For example, in the process of establishing a PDU session, it may be a process in which a user establishes a PDU session in a single access mode, or some users establish a PDU session in a single access mode, and some users establish a multi-access session through DualSteer technology, etc. This mixed scenario is also within the scope of application of the present disclosure.

[0060] Exemplarily, in the present disclosure, the communication scenarios of multi-access technologies may include but are not limited to: PDU session establishment scenarios involving multi-access technologies. The multi-access technologies involved in the present disclosure may include but are not limited to DualSteer (also referred to as dual steering or other names, and the present disclosure has special restrictions on naming) technology or other dual access or multi-access technologies. For ease of explanation, the following will take the DualSteer device, or the PDU session establishment process of the terminal as an example for specific explanation.

[0061] In addition, the present disclosure has no special restrictions on the structural form between two terminals with a DualSteer association relationship (referred to as DualSteer terminals or DualSteer associated terminals or DualSteer devices, which have two terminals). Exemplarily, the two DualSteer terminals can be two independent terminal devices, but they have a DualSteer association relationship, and a PDU session for DualSteer can be established to achieve multi-stream transmission. Or, exemplarily, two DualSteer terminals can form a DualSteer device. For example, a DualSteer device can have two terminals, each of which corresponds to a globally unique subscription permanent identifier (SUPI). The DualSteer device can access the network separately as two terminals through two SUPIs. That is, the first terminal and the second terminal belong to the same dual-steering device.

[0062] The dual-steering device or dual-steering terminal (also referred to as terminal, terminal device, user equipment (UE), mobile station, mobile terminal, etc.) involved in the present disclosure has dual-steering capability and can communicate with the core network. Specifically, the dual-steering device or dual-steering terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. Based on this, the dual-steering terminal can be but is not limited to: a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. The embodiments of the present application have no special restrictions on the specific technology and specific device form adopted by the terminal. In addition, the terminal can be fixed or movable. The terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface; it can also be deployed on an airplane, balloon, or artificial satellite in the air. The embodiment of the present application has no special restrictions on the application scenario of the terminal.

[0063] As described in the background technology, for DualSteer terminals, in order to give full play to their advantages of multi-stream transmission, the session types of the PDU sessions established by the two DualSteer terminals are required to be the same, otherwise, the core network cannot assign the same address (such as IP address) to them, and multi-stream transmission cannot be achieved. For example, if UE1 and UE2 are DualSteer terminals with a DualSteer association relationship, and UE1 accesses the network to establish an Ethernet type session, while UE2 establishes an IPv4 type session. In this case, even if UE1 and UE2 have a DualSteer association relationship, the established session is also used for DualSteer multi-stream transmission, but true multi-stream transmission cannot be achieved, because the purpose of the DualSteer feature is to improve reliability on the one hand, so that data can be transmitted under multiple RAT types, and on the other hand, to improve the uplink and downlink transmission rates, because the uplink and downlink rates are greatly improved when data is transmitted through two RAT types. If the two sessions are of different session types, the session switching cannot be achieved, so the DualSteer feature cannot be truly realized.

[0064] In view of the above situation, the present disclosure provides a new design concept: when the DualSteer terminal accesses the network, the network side can indicate the session type in the policy association stage. In other words, the network side can send the same session type indication to the DualSteer terminal, so that the two DualSteer terminals can establish a PDU session of the same session type for multi-stream transmission. Furthermore, the present disclosure also makes further possible optimizations in terms of the indication method and trigger conditions of the session type. In addition, in order to avoid the indication of the above session type being ignored or the terminal not establishing a PDU session according to the type indication, the present disclosure further provides a solution for the third communication device to perform PDU session control management based on the DualSteer terminal session type to ensure that the session type established by the DualSteer terminal for the DualSteer session is consistent. The following is a detailed description.

[0065] The present disclosure provides a communication method, which is applied to a first communication device.

[0066] For example, please refer to Figure 2 , Figure 2 The flowchart of a communication method provided by an embodiment of the present disclosure is as follows. In the present disclosure, the first communication device may perform a first operation, and the first operation includes but is not limited to at least one of the following (i.e., S202 and S204). For ease of understanding, Figure 2 The first operation includes S202 and S204. Figure 2 Describe this plan in detail.

[0067] like Figure 2 As shown, the communication method includes:

[0068] S202: Receive a first request, where the first request includes first information and is used to request to obtain a first policy.

[0069] In one implementation, the first request may be at least one of the following:

[0070] Terminal policy control establishment request (i.e. Npcf_UEPolicyControl_Create Request);

[0071] Terminal policy control update request (ie, Npcf_UEPolicyControl_Update Request).

[0072] In another implementation, the first strategy may be at least one of the following:

[0073] URSP (UE Route Selection Policy) rules;

[0074] DualSteer Policy.

[0075] The first strategy is used for at least one of the following:

[0076] Trigger the terminal or DualSteer device to establish a new multi-access session;

[0077] At least one terminal under the DualSteer device is triggered to establish at least one new session, where the session types of the sessions are the same.

[0078] The first information includes at least one of the following:

[0079] First terminal identification information;

[0080] capability information of the first terminal;

[0081] The first contract information; wherein, the first contract information satisfies at least one of the following: the first contract information is used to indicate at least one of that the first terminal belongs to a dual-steering device or that a first association relationship exists between the first terminal and the second terminal; the first contract information includes at least one of the following: an association identifier.

[0082] The first terminal identification information may include but is not limited to at least one of the following: a Generic Public Subscription Identifier (GPSI), a SUPI, or an identifier used to indicate a terminal in a DualSteer device, which is not exhaustive.

[0083] Among them, the capability information of the first terminal is used to indicate at least one of the following: the first terminal has or supports DualSteer capability, or the first terminal is a terminal in a DualSteer device, or the terminal supports continuous transmission or the terminal has the ability to support continuous transmission, or the terminal supports discontinuous transmission or the terminal has the ability to support discontinuous transmission, or the terminal has the ability to establish a session in a multi-access mode, or the terminal has the ability to establish a session under two 3GPP accesses, etc.

[0084] The first contract information includes at least one of the following:

[0085] An association identifier, used to indicate that the terminal has a DualSteer association relationship with other terminals;

[0086] capability information of the first terminal;

[0087] The authorization or permission result may specifically include at least one of the following: authorizing or permitting the first terminal to perform DualSteer related operations (for example, establishing a DualSteer session, or initiating a session establishment request under multiple access modes), or authorizing or permitting the first terminal to send a first policy.

[0088] In other words, in the present disclosure, the first communication device has the ability to receive policy requests and send policies. In other words, the first communication device has policy control capabilities. Therefore, the first communication function can be implemented by any device, apparatus, network function, etc. that has a policy control function. Exemplarily, policy control is generally implemented through a policy control function (PCF) in a 5G core network. Therefore, the first communication device in the present disclosure may include but is not limited to PCF. In addition, with the development of network technology, future 6G networks or other networks (such as dedicated networks, etc.) can implement policy control functions through other network functions. Therefore, the first communication device in the present disclosure can also be implemented by these network functions.

[0089] In an exemplary embodiment, the first communication device may be specifically a PCF, and the initiator of the first request may include but is not limited to: an access and mobility management function (AMF) or a session management function (SMF). During the PDU session establishment process, the AMF may receive a session establishment request from the terminal and trigger the establishment of a UE policy association. At this time, it is necessary to obtain the UE policy (Policy) from the PCF, that is, send a first request to the PCF. Alternatively, when the AMF triggers the establishment of a UE policy association, the SMF may be selected first, and the SMF initiates a policy association to the PCF, that is, sends a first request.

[0090] In the present disclosure, the first request is used to request a first policy, that is, to request a first communication device to perform policy association and feedback the first policy. The first information carried in the first request may specifically be any information related to the PDU session. Among them, if the first request is a policy association request for a DualSteer terminal, or the first request is a policy association request for a DualSteer session, the first information may also specifically include DualSteer related information. For example, the first information may be used to indicate that the terminal and / or session associated with the currently requested policy is (or indicates whether it is) a DualSteer terminal and / or session. For another example, the first information may specifically indicate which terminals and / or sessions have a DualSteer association relationship with the terminal and / or session associated with the currently requested policy. This will be described in detail later.

[0091] S204, sending second information; wherein the second information includes a first policy; and the first policy includes a first session type.

[0092] The present disclosure does not specifically stipulate how the first communication device selects the first strategy, and any custom method or related technical implementation can be used in actual scenarios. It should be noted that in the DualSteer scenario, the first strategy and / or the second strategy may include at least one of the following: a strategy for establishing a multi-access session, and / or a strategy for establishing a dual-direction session, and / or a strategy not used to establish a dual-direction session, and / or a strategy for dual-direction session switching, and / or a strategy for session switching, and / or a strategy for switching a session or traffic established on the first access to a session or traffic on the second access, and / or a strategy for establishing a session for a DualSteer device, and / or a strategy for establishing a new session for a terminal under a DualSteer device, and the session belongs to the same DualSteer association. For example, the first strategy and / or the second strategy may include: a UE Route Selection Policy (URSP) for a DualSteer device terminal, and may also include a URSP for non-DualSteer services. Among them, URSP is used for the terminal to determine the routing method of outgoing traffic; the traffic can be routed to an established PDU session, or it can be offloaded to a non-3gpp access outside the PDU session, or trigger the establishment of a new PDU session. In other words, the technical solution provided by the present disclosure is not limited to the scenario with only DualSteer terminals, and can be implemented in accordance with this solution for any scenario. In addition, it should be understood that if the first information carried by the first request indicates that the current terminal and / or session is a DualSteer terminal and / or session, the first policy may specifically be a policy for DualSteer. However, if the first information does not make such an indication, the first policy may be customized by the first communication device.

[0093] In one implementation, the second information is sent by at least one of the following:

[0094] Terminal policy control establishment response (i.e. Npcf_UEPolicyControl_Create Response);

[0095] Terminal policy control update response (ie, Npcf_UEPolicyControl_Update Response).

[0096] The policy used for DualSteer may be a policy related to any related operation such as establishment and switching of DualSteer and / or PDU session and / or multi-access session. In an exemplary embodiment, the first policy may be used for but not limited to at least one of the following: traffic routing, diversion, switching to a dual-steering session; establishing a dual-steering session. At this time, the first session type may specifically be a session type of a dual-steering session.

[0097] The dual-direction session satisfies at least one of the following:

[0098] It consists of two PDU sessions;

[0099] Each PDU session is established by one terminal;

[0100] The terminals corresponding to each PDU session belong to the same DualSteer device;

[0101] It is a multi-access type session;

[0102] Established by a terminal with dual-turn capability;

[0103] Two PDU sessions are established on two different RATs.

[0104] The dual-direction conversation involved in the present disclosure includes at least one of the following: a first conversation; a second conversation.

[0105] The first session refers to the session corresponding to the first request, and may also be specifically a session requested to be established by the first terminal. In other words, the first session is established by the first terminal. The session type of the first session is the first session type. In other words, the first session type satisfies at least one of the following: the first session type is the session type of the dual-direction session, and the first session type is the session type of the first session.

[0106] and / or,

[0107] The second session refers to the session corresponding to the second request (described in detail below), and can also be specifically a session requested to be established by the second terminal. In other words, the second session is established by the second terminal. The session type of the second session is the second session type. In other words, the second session type satisfies at least one of the following: the second session type is the session type of the dual-direction session, and the second session type is the session type of the second session.

[0108] It should be noted that in the present disclosure, the first policy sent by the first communication device also includes a first session type. The first session type means the session type assigned or determined by the first communication device for the current session (i.e., the first session). The present disclosure has no particular restrictions on the scope and selection method of the first session type.

[0109] In one implementation, the first policy sent by the first communication device may be a URSP rule, in which a route selection descriptor under at least one traffic descriptor includes a first session type; or, the path selection descriptors under all traffic descriptors include the first session type.

[0110] In one implementation, the second policy sent by the first communication device may be a URSP rule, in which a route selection descriptor under at least one traffic descriptor includes a second session type; or, the path selection descriptors under all traffic descriptors include the second session type.

[0111] In an exemplary embodiment, the first session type involved in the present disclosure may include but is not limited to at least one of the following:

[0112] DualSteer session type;

[0113] IPv4 session type;

[0114] IPv6 session type;

[0115] IPv4v6 session type;

[0116] Multiple access session type.

[0117] It should be understood that the first session type included in the first policy may be a specific session type. Also, it should be understood that with the advancement of technology, in addition to the above-mentioned session types, the first session type may also have other possibilities, which will not be described in detail.

[0118] In addition, during specific implementation, different session types may be indicated by a route selection descriptor (RSD) under a traffic descriptor, and further, may be indicated by a PDUsession type field in the RSD.

[0119] In summary, in the present disclosure, when a communication device receives a request to obtain a first policy, it can carry an indication of the session type in the sent first policy, so that the recipient of the first policy can establish subsequent PDU sessions based on it, thereby ensuring that DualSteer associated terminals can establish the same type of PDU sessions. In summary, the technical solution provided by the present disclosure can achieve the same session type for DualSteer associated terminals, solve the problem of different session types of DualSteer associated terminals limiting the development of DualSteer technology, and is conducive to giving full play to the advantages of multi-stream transmission and improving communication quality.

[0120] In one implementation, the first policy may also be used by the terminal to match or route traffic to a PDU session, the session type of which is the session type indicated in the first policy.

[0121] On this basis, further, in the present disclosure, the operation of the first communication device sending the second information can be performed only when certain conditions are met; conversely, if the condition is not met, or the condition changes and no longer meets the condition, the first strategy will not be sent temporarily, or other strategies will be sent, or the current first strategy will be updated or deleted, as described in detail below.

[0122] In an exemplary embodiment, when a first condition is met, the first communication device sends the second information.

[0123] The first condition may include but is not limited to at least one of the following:

[0124] The second terminal is in a registered state;

[0125] The first terminal is in a registered state;

[0126] The first terminal and the second terminal have a first capability;

[0127] There is a first association relationship between the first terminal and the second terminal.

[0128] Among them, the registration state (also referred to as the registration state) involved in the present disclosure means that the terminal has been registered with the network or core network (the network can be a 5G network or a 4G network, etc., and the core network can be a 5G core network or a 4G core network, etc., and the related instructions about the core network and the network side equipment can be referred to in the previous text, and no further details are given), and is in a registered state; or it can be understood that the terminal enters or is in the RM-REGISTERED state (registration management-registered); or it can also be understood that the terminal is not in the RM-DEREGISTERED state (registration management-deregistered). In addition, in contrast to the registration state, the terminal may also be in a non-registered state, which can be specifically a deregistered state or an unregistered state, or it can be understood that the terminal enters the RM-DEREGISTERED state, or the terminal is not in the RM-REGISTERED state.

[0129] In one implementation, when the first terminal and the second terminal are DualSteer associated, and the first terminal and the second terminal are both in a registered state, the PCF sends a URSP rule to the first terminal and the second terminal, and the URSP rule sent to the first terminal and the second terminal satisfies at least one of the following:

[0130] Contains the same traffic descriptor;

[0131] Contains the same routing descriptor;

[0132] Contains the same session type;

[0133] The path selection descriptor under the same traffic descriptor of the first terminal and the second terminal is the same;

[0134] In the path selection descriptor under the same traffic descriptor of the first terminal and the second terminal, the session type is the same.

[0135] In the present disclosure, the first condition requires that both the first terminal and the second terminal are in a registered state, that is, only when both terminals belonging to the same DualSteer device are in a registered state, can the subsequent PDU session establishment process be performed, and only then can the DualSteer associated transmission be established. If one of the terminals is not in a registered state, for example, it has not yet registered with the network or has been deregistered from the network, then for a registered DualSteer terminal, DualSteer multi-stream transmission cannot be implemented at this time, and there is no need to send the first DualSteer associated policy for it.

[0136] In one embodiment, the first strategy and / or the second strategy are used for a terminal in a dual-steering device to establish a session, or for a terminal in a dual-steering device to route traffic to a session; the first strategy and / or the second strategy are used for one terminal in a dual-steering device to switch a session to another session of another terminal in the dual-steering device. The first strategy and / or the second strategy are used to establish a dual-steering session, or a multi-access session, or to establish a session between a first terminal or a second terminal, and the sessions are associated (dual-steering association).

[0137] The first capability involved in the present disclosure satisfies at least one of the following:

[0138] The first capability is used to describe that the terminal has or supports dual-steering capability;

[0139] The first capability includes at least one of the following:

[0140] Support or have dual steering capability;

[0141] Support traffic diversion and / or switching to dual-direction sessions;

[0142] Support continuous or discontinuous transmission;

[0143] Supporting traffic diversion and / or switching to a session of a first access corresponding to a first SUPI or switching to a session of a second access corresponding to a second SUPI; wherein the first SUPI is different from the second SUPI, and the first access is different from the second access.

[0144] In the present disclosure, the first condition requires that both the first terminal and the second terminal have the first capability. This is because it is possible to establish a session or a multi-access session with dual-steering association only when both DualSteer terminals support at least one of the above DualSteer-related capabilities. Therefore, if one of the two terminals with a DualSteer association does not support the first capability, it is also impossible to establish a valid session or a multi-access session with dual-steering association, and there is no need to send the first policy of DualSteer association to it.

[0145] The first association relationship involved in the present disclosure may satisfy at least one of the following:

[0146] The first terminal and the second terminal belong to the same dual-steering device;

[0147] The first terminal identifier and the second terminal identifier correspond to the same association identifier.

[0148] Among them, the first terminal and the second terminal belong to the same dual-steering device, that is, as mentioned above, a DualSteer device can have two terminals. At this time, the two terminals can have a DualSteer association relationship and can establish two sessions to achieve multi-stream transmission or establish a multi-access session.

[0149] In one implementation, the first association relationship may be identified or indicated by an association identifier; or the first association relationship corresponds to an association identifier; or an association identifier is used to indicate an association relationship. The association identifier may be a string or a numerical value.

[0150] If the first terminal identifier and the second terminal identifier correspond to the same association identifier, it means that the first terminal and the second terminal have a DualSteer association relationship, and this association relationship can be uniquely indicated by an association identifier. For example, SUPI1 of the first terminal and SUPI2 of the second terminal are associated with an association identifier a (here only for illustration), in this case, SUPI1 and SUPI2 correspond to the same DualSteer association identifier a, indicating that the two are associated, that is, the two terminals have a DualSteer association relationship.

[0151] In one implementation, the association relationship may describe at least one of the following. When the first terminal and the second terminal have an association relationship, at least one of the following exists:

[0152] The PDU session established by the first terminal and the second terminal can be switched to each other;

[0153] The first terminal and the second terminal support the DualSteer feature;

[0154] The first terminal and the second terminal are terminals in the same DualSteer device.

[0155] In addition, in the actual implementation scenario, the relationship between the terminal identifier and the association identifier can be maintained in the contract information, registration information, attribute information, first information or other possible information of the terminal, and a custom design is sufficient. For example, the relationship between the above-mentioned DualSteer association identifier and the terminal's SUPI is maintained in the contract information of the terminal, then the first association relationship can also be understood as: the contract information of the first terminal and the contract information of the second terminal contain the same association identifier. It should be understood that any method that can indicate that there is a DualSteer association relationship between two terminals through an association identifier is within the achievable scope of this embodiment and will not be repeated.

[0156] Based on the first condition, before executing S204, the first communication device may also determine whether there is a second terminal associated with the first terminal of the current session, whether the second terminal is in a registered state, and whether the second terminal supports the first capability. Thus, when all these conditions are met, it is determined that the first condition is met and the first policy is sent.

[0157] Wherein, whether the second terminal is in a registered state can be obtained by the first communication device querying the second communication device. At this time, for the first communication device, the communication method executed by it can also include at least one of the following:

[0158] The first communication device sends a third request to the second communication device, where the third request is used to request to obtain or subscribe to a registration status of the terminal.

[0159] The first communication device receives fifth information from the second communication device, where the fifth information includes a registration status of at least one terminal.

[0160] The third request may carry at least one of the following information:

[0161] First terminal identification (such as SUPI);

[0162] Second terminal identification (such as SUPI);

[0163] First ability;

[0164] The first association relationship, or an identifier corresponding to the first association relationship.

[0165] In one implementation, the registration status of the terminal under the DualSteer device is obtained through a third request.

[0166] In one implementation, the fifth information includes at least one of the following:

[0167] The registration status of the first terminal;

[0168] The registration status of the second terminal.

[0169] The registration state (also referred to as registration state) includes at least one of the following:

[0170] RM-REGISTERED status (Registration Management-Registered);

[0171] RM-DEREGISTERED state (Registration Management - Deregistration).

[0172] Among them, acquisition means a single acquisition, that is, obtaining the current registration status of the terminal; subscription means a long-term subscription, that is, obtaining the registration status of the terminal from the current time and its changes. In addition, the third request is used to request to obtain or subscribe to the registration status of the terminal. Specifically, the third request can request the registration status of one or more terminals. In the multi-access communication scenario concerned by the present disclosure, the third request can be used to request to obtain or subscribe to the registration status of the terminal with which it has a DualSteer association relationship.

[0173] In the present disclosure, the second communication device may be any network function, entity or apparatus having a registration status storage capability. Exemplarily, the second communication device may be specifically a Unified Data Management (UDM).

[0174] For example, please refer to Figure 3 , Figure 3 The following is an interactive diagram of a registration information acquisition process provided by an embodiment of the present disclosure. Figure 3 As shown, the PCF (i.e., the first communication device) can send a subscription request (i.e., the third request) to the UDM (i.e., the second communication device), and the subscription request carries at least one of the terminal identifier (at this time, the registration status of the associated terminal UE2 and / or the registration status of the own UE1) and the association identifier (at this time, the registration status of the two UEs is requested), and the subscription request is used to request the subscription terminal registration status. After receiving the subscription request, the UDM can send a subscription response to the PCF to indicate that the subscription request has been received.

[0175] Afterwards, UDM may confirm the registration status of the requested terminal (referred to as the target terminal, which may be UE1 and / or UE2), and send a notification message (ie, the fifth information) to the PCF, which specifically carries the registration status of the target terminal.

[0176] In one implementation, if the registration status of a terminal is subscribed, the registration status of the terminal changes after registration or deregistration, and the UDM may notify the PCF of the registration status change and send fifth information, where the fifth information carries the registration status of the terminal.

[0177] If the target terminal completes the registration process after the subscription request, the UDM sends a notification message to the PCF after the registration is completed, which carries relevant indication information that the target terminal has completed registration (or is in a registered state). For example, the information carried in the notification message may be: Event ID: Registered. The Event ID is used to indicate the subscribed event, and the event is: terminal status.

[0178] Through this method, the PCF can subscribe to the registration status of the two terminals in the DualSteer device, and determine whether to send the DualSteer policy (ie, the first policy) according to the registration status.

[0179] In one implementation, the PCF may also indirectly obtain the terminal registration status from the UDM through the AMF. For example, the PCF sends a request to the AMF, and the AMF obtains the terminal registration status from the UDM instead of the PCF. In other words, the first communication device may directly request the UDM to obtain the terminal registration status, or may request the UDM to obtain the terminal registration status indirectly (for example, through the AMF).

[0180] In one implementation, the UDM or other core network devices may maintain the registration status of two associated terminals.

[0181] In addition, in a possible embodiment, for querying the terminal registration status, a limiting condition may be preset, for example, it may be limited to obtaining or subscribing to the registration status only when two UEs have a DualSteer association relationship. In this case, after receiving the third request, the UDM may notify or reject the specific registration status based on whether the requester and the target terminal have a DualSteer association relationship.

[0182] In addition, the first condition also requires that the two terminals have a DualSteer association relationship and both terminals have the first capability. This information can be carried in the first information. In other words, when the terminal requests the first strategy from the first communication device, it can carry its own capability information and the relevant information of the DualSteer association relationship. Whether the terminal supports the DualSteer association relationship or who the DualSteer associated terminal is can generally be indicated by the DualSteer association identifier or contract information.

[0183] Then, in an exemplary embodiment, the terminal requested by the third request to obtain registration information may satisfy at least one of the following:

[0184] The terminal is at least one of the first terminal or the second terminal;

[0185] The terminal is a dual-steering device;

[0186] The terminal has a first association relationship.

[0187] In addition, in the present disclosure, the first information may include but is not limited to at least one of the following:

[0188] First terminal identification information (i.e., information that can uniquely identify a terminal, for example, which may include but is not limited to SUPI);

[0189] Capability information of the first terminal (i.e., capabilities possessed by the terminal and / or capabilities not possessed by the terminal; based on which, it can be determined whether the terminal supports the first capability);

[0190] The first contract information; wherein, the first contract information satisfies at least one of the following: the first contract information is used to indicate at least one of that the first terminal belongs to a dual-steering device or that a first association relationship exists between the first terminal and the second terminal; the first contract information includes at least one of the following: an association identifier.

[0191] Based on this, after receiving the first request, the first communication device can learn about the situation of the first terminal. Therefore, when providing specific feedback on the first request, it can further consider whether to allocate a policy for DualSteer to it, and further query the UDM for the registration information of the second terminal to determine whether the first condition is met and then send the first policy.

[0192] In the present disclosure, the first communication device can support policy requests of other terminals in addition to sending policies to the first terminal. In addition, how to point two terminals with DualSteer association to the same PCF can be achieved through related technologies, which will not be discussed in the present disclosure.

[0193] Exemplarily, in a possible embodiment, the first communication device in the present disclosure may further perform a second operation in addition to the above-mentioned first operation. Specifically, the first communication device may further perform the second operation, and the second operation includes at least one of the following:

[0194] receiving a second request, the second request including third information, the second request being used to request establishment of a policy association for the second terminal;

[0195] sending fourth information, wherein the fourth information includes the second strategy;

[0196] The second policy includes the first session type.

[0197] Exemplarily, the second strategy is used for at least one of the following: traffic routing, diversion, switching to a dual-direction session; establishing a dual-direction session. The scope and content of the dual-direction session refer to the above text and are not described in detail.

[0198] It should be understood that the second request relative to the second terminal may be equal to or equivalent to the first request relative to the first terminal, and is used to request to establish a policy association for the corresponding terminal. For related instructions, please refer to the previous instructions on the first request and will not be repeated here.

[0199] Exemplarily, the third information may include but is not limited to at least one of the following:

[0200] Second terminal identification information;

[0201] capability information of the second terminal;

[0202] The second contract information; wherein, the second contract information satisfies at least one of the following: the second contract information is used to indicate at least one of that the second terminal belongs to a dual-direction device or that a first association relationship exists between the first terminal and the second terminal; the second contract information includes at least one of the following: an association identifier.

[0203] For easier understanding, please refer to Figure 4 , Figure 4 An interactive flow chart of a policy selection process during a PDU session establishment process provided by an embodiment of the present disclosure.

[0204] like Figure 4 As shown, the process may include two interaction processes of UE1 and UE2. For UE1, there are the following processes:

[0205] S1, UE1 with DualSteer capability can initiate a registration request (i.e., registration request) to AMF.

[0206] S2. After receiving the registration request, AMF triggers the sending of a first request to PCF (the request message may be specifically: Npcf_UEPolicyControl_Create Request) to request the establishment of a policy association control, which carries the first information. In specific implementation, the first information can be obtained from the UE or from the UDM, without any special restrictions. The first information may include but is not limited to: association information or contract information (i.e., subscription) between SUPI1 and UE1's capabilities (i.e., capability, which may be specifically: Dualsteercapable, i.e., whether Dualsteer is supported) and UE1; wherein, the contract information is used to indicate that UE1 can be used for Dualsteer services.

[0207] In a possible embodiment, before executing S2, the AMF may further perform the following operations:

[0208] S1+A, AMF sends a get request to UDM (specifically, it can be: Nudm_SDM_Get request).

[0209] S1+B, UDM sends a get response to AMF (which may specifically be: Nudm_SDM_Get response), which may carry DualSteer-related indication information of the terminal.

[0210] S3, PCF sends the second information to AMF (which can be sent through the response message of the policy control establishment request, which can be specifically: Npcf_UEPolicyControl_Create Response), which carries the first policy (for example, it can be recorded as URSP rule1 for DualSteer), and the first policy carries the first session type (for example, DualSteer session type). After that, AMF establishes the first session according to the first policy and the first session type.

[0211] In a possible embodiment, the PCF performs the operation of sending the second information in S3 only when the first condition is met. In other words, when UE 1 and UE 2 are both in the registered state, UE 1 has the Dual Steer capability, and UE 1 and UE 2 have a Dual Steer association relationship, the PCF sends the first policy to the AMF, and carries the first session type therein.

[0212] Afterwards, AMF notifies UE1 of the first policy and the first session type, and UE1 establishes a PDU session of the first session type.

[0213] For UE2, the process is as follows:

[0214] S4, UE2 with DualSteer capability can initiate a registration request (i.e., registration request) to AMF, wherein the registration request can indicate that UE2 supports DualSteer capability and has a DualSteer association relationship with UE1.

[0215] S5, after receiving the registration request, the AMF triggers to send a second request to the PCF to request to establish a policy association control, which carries the third information. The third information may include but is not limited to: the capabilities of SUPI2 and UE2 (i.e., capability) and the subscription information of UE2 (i.e., subscription).

[0216] like Figure 4 As shown, before S5, there can also be S4+A and S4+B, that is, AMF obtains the DualSteer related information of the terminal from UDM. Its implementation method is the same as S1+A and S1+B, which will not be repeated.

[0217] S6: PCF sends fourth information to AMF, which carries the second policy (for example, it can be recorded as URSP rule1 for DualSteer), and the second policy carries the first session type (for example, DualSteer session type).

[0218] Similarly, in a possible embodiment, the PCF performs the operation of sending the fourth information in S6 only when the first condition is met. In other words, when UE 1 and UE 2 are both in the registered state, UE 2 has the Dual Steer capability, and UE 1 and UE 2 have a Dual Steer association relationship, the PCF sends the second policy to the AMF and carries the first session type therein (this also means that the first session type is the same as the second session type, both of which are the first session type).

[0219] Exemplarily, in a possible embodiment, the first request and the second request may be specifically Npcf_UEPolicyControl_Create Request, and the second information and the fourth information may be sent via Npcf_UEPolicyControl_Create Response.

[0220] In addition, it should be understood that when the policy association request of two DualSteer terminals UE1 and UE2 is processed, when the condition "UE 1 and UE 2 are both in the registered state, UE1 and UE 2 have Dual Steer capabilities, and UE 1 and UE 2 have a DualSteer association relationship" is met, the first conditions corresponding to the second information and the fourth information are also met. In this case, sending the second information and the fourth information can actually be processed as follows: when the first condition is met, the second information is sent to the first terminal, and the fourth information is sent to the second terminal. For example, Figure 4 S3 and S6 in the illustrated embodiment can be triggered and executed simultaneously when the aforementioned first condition is met.

[0221] In summary, in this embodiment, the PCF carries the indication information of the same first session type in the policy sent to UE1 and UE2, and UE1 and UE2 can establish the same type of PDU session based on this, thereby realizing DualSteer multi-stream transmission.

[0222] In the above embodiment, when the first condition is met, the first communication device may send the first policy and indicate the session type of the DualSteer terminal. In addition, the first condition may not be met or the condition may change so that the first condition is no longer met. In this regard, the communication method performed by the first communication device in the present disclosure may also include:

[0223] When the second condition is met, the first policy is deleted or updated.

[0224] The second condition includes at least one of the following:

[0225] The first association relationship between the first terminal and the second terminal is released;

[0226] at least one of the first terminal and the second terminal disabling a first capability;

[0227] At least one of the first terminal and the second terminal is in a deregistered state.

[0228] As described above, when the first condition is met, the first communication device can allocate a DualSteer policy (i.e., DualSteer Policy) to the terminal to implement DualSteer multi-stream transmission. However, when the first condition is not met or no longer met, that is, when the second condition in this embodiment is met, DualSteer multi-stream transmission cannot be implemented at this time, and DualSteerPolicy is no longer applicable. At this time, it can be deleted or updated. In another implementation, when the second condition is met, the updated first policy is sent.

[0229] Deletion means deleting the original DualSteer Policy and no longer applying it. However, it should be noted that the policies deleted at this time only include the policies used for DualSteer, and do not include other policies, such as the normal URSP rule policy.

[0230] Here, updating means updating the current policy to another policy that is suitable for the current situation. In actual implementation, a global update can also be performed, that is, a full set of URSP rules can be sent to overwrite the original DualSteer policy.

[0231] At the specific execution level, when the second condition is met, the first communication device may execute at least one of the following: updating the first policy; sending a new first policy; instructing deletion of the first policy.

[0232] In addition, as mentioned above, the two DualSteer terminals may be independent of each other or may belong to the same DualSteer Device. In this regard, when the first communication device specifically sends the second information, it may have the following different sending modes:

[0233] Mode 1: The first communication device sends the second information to the first terminal. Regardless of the structural relationship between the first terminal and the second terminal, as long as the first terminal has external communication capabilities, the second information can be sent directly to the first terminal. It should be noted that the sender of the second information is the first communication device, and the final receiver is the first terminal. The sender and receiver are forwarded through an intermediate device (such as the AMF mentioned above), and the two are in an indirect communication relationship.

[0234] or,

[0235] Mode 2: The first communication device sends the second information to the dual-steering device, and the first terminal and the second terminal belong to the same dual-steering device. In this case, the first terminal and the second terminal belong to the same DualSteer Device. In this case, the DualSteer Device can assume the external communication function, and the DualSteer Device can be directly used as the final receiving end of the second information to realize the transmission of the first policy.

[0236] It should be understood that the above description is made by taking the first terminal as an example, and the second terminal may also implement indirect transmission of the fourth information according to the above method 1 or method 2.

[0237] In addition, as described above, in a possible embodiment, the first terminal and the second terminal belong to the same dual-steering device. At this time, based on the different service types supported by the dual-steering device, the first strategy determined by the first communication device may also be different.

[0238] In an exemplary embodiment, the first strategy may satisfy at least one of the following:

[0239] When the dual-steering device supports continuous transmission, the routing descriptor of the first strategy includes: a first terminal identifier and / or a second terminal identifier;

[0240] or,

[0241] When the dual-direction device does not support continuous transmission, the routing descriptor of the first strategy includes: a first terminal identifier or a second terminal identifier.

[0242] In other words, when the DualSteer Device supports continuous transmission, the RSD corresponding to the traffic descriptor of the first strategy or the RSD under the traffic descriptor may contain identifiers of UE1 and UE2 at the same time, or the path selection member route selection component (RSC) may contain at least one identifier of UE1 and UE2 (for example, SUPI1 and SUPI2); conversely, when the DualSteer Device does not support continuous transmission, the RSD corresponding to the traffic descriptor of the first strategy may contain only one identifier of UE1 or UE2.

[0243] For example. When the DualSteer Device supports continuous transmission, the PCF selects a certain first strategy to support matching different APP traffic to the sessions of UE 1 or UE 2, respectively, so that traffic can be transmitted on the PDU sessions of UE1 and UE2 at the same time. In addition, since UE 1 and UE 2 belong to a Dual Steer device, at this time, there can be multiple UE SUPIs under the traffic descriptor in the first strategy, namely SUPI1 and SUPI2.

[0244] When DualSteer Device does not support continuous transmission, PCF selects the first strategy to only support matching all APP traffic to only one session of UE 1 or UE 2. Therefore, the RSD under all traffic descriptors can only include or carry one UE identifier, that is, the traffic of these applications can only be matched or diverted to the session of one terminal. For example: when there is a traffic descriptor APP1 in the DualSteer policy of UE 1 to realize routing the traffic of APP1 to the session of UE1, but because continuous transmission is not supported, only one of UE1 and UE2 can have traffic at the same time, then the traffic descriptor APP1 cannot exist in the DualSteer policy of UE 2, because the traffic of the same APP does not support continuous transmission and cannot be transmitted in two sessions at the same time; or, there can also be a traffic descriptor APP1 in the URSP rule or DualSteer rule of UE2, but the RSD still carries the identifier SUPI1 corresponding to UE1, that is, only traffic diversion to the PDU session of UE1 is supported.

[0245] In addition, it should be noted that in the DualSteer multi-stream transmission scenario, a terminal that supports the DualSteer function can establish a session for DualSteer or a session that is not used for DualSteer. A terminal can also establish multiple sessions. For easier understanding, please refer to Figure 5 , Figure 5 A schematic diagram of DualSteer multi-stream transmission provided in an embodiment of the present disclosure.

[0246] like Figure 5 As shown in the figure, a DualSteer Device (i.e., a dual-steering device) can have two terminals, namely, UE1 (whose UE identifier is SUPI1) and UE2 (whose UE identifier is SUPI2). UE1 and UE2 access the network through two 3GPP links. At this time, the DualSteer Session A (i.e., Figure 5DualSteerSession A) established with UE2 (i.e. Figure 5 The dual-direction session B in the example is two sessions with a DualSteer association relationship. In addition, UE2 can also establish a non-DualSteer Session B (i.e. Figure 5 Then, when UE2 requests the first communication device to associate a policy, that is, after the first communication device receives the first request, the first communication device selects a determined policy for UE2, which may include a non-multi-stream transmission policy in addition to the first policy, for example, Figure 5 The non-dual-steering session B in the is assigned a non-multi-stream transmission strategy. Sessions not used for DualSteer can be considered as ordinary PDU sessions; sessions used for DualSteer can be considered as having an association relationship with sessions established with other terminals in the DualSteer device.

[0247] In other words, the first communication device may further perform the following operation: sending a third policy, where the third policy is used for non-dual-steer transmission. In one implementation, the third policy is a URSP rule, or does not include a DualSteer policy.

[0248] In specific implementation, the third strategy can be sent in combination with the first strategy. In other words, in a possible embodiment, the second information also includes a third strategy for non-dual steering transmission. For example, Figure 4 In the illustrated embodiment, the second information sent by the PCF includes both the URSP rule for Dual Steer and the URSP rule for non-Dual Steer services.

[0249] Alternatively, the third strategy may also be sent separately. In other words, in another possible embodiment, the communication method executed by the first communication device further includes: sending sixth information, wherein the sixth information includes the third strategy for non-dual steering transmission.

[0250] In addition, in some of the embodiments described above, for example, when the second condition is met or the first condition is not met, the first communication device may not send the first policy, but in this case, it does not affect its sending of the third policy. For example, when the first condition is not met, the PCF does not send the first policy for DualSteer, but only sends the third policy for non-DualSteer.

[0251] The present disclosure also provides another communication method, which is applied to a third communication device. The communication method can be used as an auxiliary coordination solution for the method executed by the first communication device side to specifically control the PDU session establishment process based on the session type of the DualSteer terminal to avoid the situation where the session type for the DualSteer session established by the DualSteer terminal is inconsistent.

[0252] For details, please refer to Figure 6 , Figure 6 A flowchart of another communication method provided by an embodiment of the present disclosure. In the present disclosure, the third communication device may perform a third operation, and the third operation includes but is not limited to at least one of the following (ie, S602-S606). For ease of understanding, Figure 6 The third operation includes S602-S606. Figure 6 Describe this plan in detail. Figure 6 As shown, the communication method includes:

[0253] S602: Receive a fourth request, where the fourth request carries a second session type.

[0254] In the present disclosure, the fourth request may be specifically a session establishment request or SM context creation, which may be specifically a session establishment request for any terminal. Exemplarily, in the DualSteer scenario involved in the present disclosure, the fourth request is a session establishment request for any DualSteer terminal.

[0255] Based on this, the third communication device in the present disclosure may be specifically any device, apparatus or network function with a session management function. In an exemplary embodiment, the third communication device may be specifically an SMF. In a common PDU session establishment scenario, the session establishment request may be initiated by the AMF to the SMF.

[0256] Exemplarily, the second session type satisfies at least one of the following: the second session type is a session type of a dual-direction session; the second session type is a session type of a second session.

[0257] In addition, the first session is established by the first terminal; and / or the second session is established by the second terminal.

[0258] Please refer to the previous article and I will not repeat it here.

[0259] S604, request or obtain seventh information.

[0260] In the present disclosure, the seventh information may be specifically the DualSteer related information of the terminal (referred to as the current terminal) corresponding to the fourth request. Exemplarily, it may include but is not limited to: whether there are other terminals that have a DualSteer association relationship with the current terminal; if so, whether the associated terminal has been connected to the network; if it has been connected to the network, what session type is used to access the network, etc. In other words, the seventh information (or referred to as DualSteer related information) may include: whether there is a terminal that has a DualSteer association relationship with the current terminal, and the relevant access information (or registration information) of the associated terminal. Among them, when the associated terminal has first accessed the network, the relevant access information of the associated terminal includes at least the session type of its access to the network. In other words, the seventh information can at least characterize the session type with which the DualSteer associated terminal accesses the network. Thus, the third communication device can control whether the current terminal is allowed to access the network in the second session type requested by the fourth request.

[0261] In an exemplary embodiment, the seventh information may include but is not limited to at least one of the following:

[0262] First association relationship;

[0263] First session type;

[0264] First strategy;

[0265] First signing information;

[0266] Second signing information.

[0267] Exemplarily, the third communication device may request or obtain the seventh information from the second communication device. As described above, the second communication device maintains the contract information of the terminal. Specifically, in a possible embodiment, this step can be implemented as follows: the third communication device sends a fifth request to the second communication device, and the fifth request is used to request to obtain or subscribe to the contract information of at least one of the first terminal and the second terminal; the third communication device receives a fifth response from the second communication device, and the fifth response carries the seventh information.

[0268] S606: Send a fourth response, where the fourth response includes at least one of the following:

[0269] First session type;

[0270] PDU session establishment accept;

[0271] PDU session establishment rejected;

[0272] PDU session establishment rejection reason.

[0273] For the third communication device, if the session type requested by the terminal that accesses the network later in the received session establishment request is inconsistent with the session type in the seventh information, that is, the first session type is inconsistent with the second session type, the fourth response sent by the third communication device may specifically be: rejecting the current session establishment request, and / or modifying the current session type. In other words, the third communication device can control the DualSteer associated terminal to access the network with the same session type. If the type of the terminal that accesses the network later is inconsistent with the session type of the terminal that accessed the network earlier, the third communication device may reject the session, or may modify the session type. Conversely, if the session type requested by the terminal that accesses the network later is consistent with the session type in the seventh information, the third communication device may accept the session establishment.

[0274] Specifically, when the SMF directly rejects the session, the fourth response may include: PDU session establishment rejection, at least one of the PDU session establishment rejection reason. If the PDU session establishment rejection reason is inconsistent session type, the fourth response may further include: the first session type.

[0275] Specifically, when the SMF modifies the session type, the fourth response may at least include: the modified session type, i.e., the first session type. On this basis, the SMF refuses to establish a session with the second session type requested by it. At this time, the fourth response may further include: at least one of a PDU session establishment rejection and a PDU session establishment rejection reason.

[0276] Specifically, when the SMF accepts the current session, the fourth response may include: PDU session establishment acceptance.

[0277] For example, please refer to Figure 7 , Figure 7 FIG. 1 is a flow chart of another communication method provided by an embodiment of the present disclosure. Figure 7 As shown, UE1 and UE2 are a group of terminals with DualSteer association, and UE1 first accesses the network and has established a session for DualSteer, the session type is the first session type (for the specific implementation method, refer to the first communication device mentioned above). UE2 accesses the network later, and its access process is as follows:

[0278] S1, UE2 sends a PDU session establishment request (i.e., PDU session establishment request) to AMF. The session is used for DualSteer and the session type is the second session type.

[0279] In an actual implementation scenario, UE1 may also notify UE2 of its own session type so that UE2 can establish a PDU session of the same type for DualSteer.

[0280] S2, AMF sends the SM context creation of the PDU session to SMF (that is, the fourth request above, which can be specifically Nsmf_PDUSession_CreateSMContext request), and carries the second session type therein.

[0281] S3-S4, SMF requests UDM to obtain the contract information (which may be Nudm_SDM_Get request, also known as the fifth request), and receives a response message from UDM (Nudm_SDM_Get response, also known as the fifth response), which carries the seventh information.

[0282] Specifically, SMF requests UDM to obtain DualSteer related information of UE2, for example, whether there are other terminals that have a DualSteer association relationship with UE2; if so, whether the associated terminal has accessed the network; if it has accessed the network, what session type is used to access the network, etc. Based on this, SMF can obtain the access information of UE1 and learn that the session type of UE1 accessing the network is the first session type.

[0283] S5. Based on the first session type and the second session type, SMF sends an SM context creation response message of the PDU session to AMF (i.e., Nsmf_PDUSession_CreateSMContext response, also the fourth response), which specifically carries at least one of the first session type, PDU session establishment acceptance, PDU session establishment rejection, and PDU session establishment rejection reason.

[0284] Specifically, if the first session type is inconsistent with the second session type, the SMF may modify the second session type to the first session type, and carry the modified first session type and further other information in the fourth response; or, if the first session type is inconsistent with the second session type, the SMF may reject the session, and carry at least one of PDU session establishment rejection and PDU session establishment rejection reason in the fourth response, and further other information; or, if the first session type is consistent with the second session type, the SMF may accept the session, and carry PDU session establishment acceptance in the fourth response.

[0285] S6, AMF feeds back a PDU session establishment response to UE2. In specific implementation, if SMF rejects the session, AMF can send a PDU session establishment reject message to UE2, namely, PDU session establishment reject.

[0286] In summary, in Figure 7 In the illustrated embodiment, the third communication device can receive the fourth request, and control and manage whether the current session is accepted based on the second session type and the seventh information carried in the fourth request, thereby avoiding inconsistency in the session types of the DualSteer associated terminals.

[0287] In the present disclosure Figure 6 and Figure 7 In one embodiment shown, the first session type and the second session type may be different, or they may be the same.

[0288] Furthermore, it should be understood that Figure 6 The illustrated embodiment, in addition to being used for session management for the terminal that accesses later in the DualSteer associated terminal, can also perform session management for the session of the terminal that accesses first or other non-DualSteer terminals. For example, the SMF may also receive a fourth request for UE1, which carries the first session type, and then the SMF may still query or obtain the seventh information, thereby sending a fourth response accordingly. For example, if the SMF inquires that the DualSteer associated terminal of UE1 is UE2, and UE2 has not yet accessed the network, at this time, the SMF may accept the session establishment request and carry the PDU session acceptance in the fourth response.

[0289] The above describes the core strategies on the SMF side in detail. Now we will explain the specific implementation methods in detail.

[0290] Exemplarily, in the present disclosure, the third communication device may also determine the content of the fourth response by whether the third condition is satisfied.

[0291] In a possible embodiment, the third communication device sends a fourth response, which may include but is not limited to at least one of the following:

[0292] When the third condition is not met, sending the fourth response, wherein the fourth response includes a PDU session establishment rejection;

[0293] When the third condition is met, the fourth response is sent, wherein the fourth response includes at least one of a PDU session establishment acceptance and a first session type.

[0294] The third condition involved in the present disclosure may specifically include but is not limited to at least one of the following:

[0295] There is a first association relationship between the first terminal and the second terminal;

[0296] The first terminal and the second terminal meet a first condition;

[0297] The first session type is the same as the second session type.

[0298] Exemplarily, the first condition includes at least one of the following: the second terminal is in a registered state; the first terminal is in a registered state; the first terminal and the second terminal have a first capability; and a first association relationship exists between the first terminal and the second terminal.

[0299] Exemplarily, the first association relationship satisfies at least one of the following: the first terminal and the second terminal belong to the same dual-steering device; the first terminal identifier and the second terminal identifier correspond to the same association identifier.

[0300] Exemplarily, the first capability satisfies at least one of the following: the first capability is used to describe that the terminal has or supports dual steering capability; the first capability includes at least one of the following: supporting or having dual steering capability; supporting traffic diversion, and / or, switching to a dual steering session; supporting continuous or discontinuous transmission; supporting traffic diversion, and / or, switching to a session of a first access corresponding to a first SUPI or switching to a session of a second access corresponding to a second SUPI; wherein the first SUPI is different from the second SUPI, and the first access is different from the second access.

[0301] For relevant contents about the first relationship, the first condition, the first capability, etc., please refer to the previous text and no further explanation will be given.

[0302] It should also be noted that, in the present disclosure, the rejection reason of the third communication device rejecting the establishment of the PDU session may include but is not limited to the situation that the session types of the DualSteer terminals described in the present disclosure are inconsistent. In addition, there may be other possible situations.

[0303] Exemplarily, the PDU session establishment rejection reasons involved in the present disclosure may include but are not limited to at least one of the following:

[0304] The session type is not allowed (i.e., PDU session type not allowed);

[0305] The session type is inconsistent with the dual steer terminal session type (i.e., PDU session type not thesame as dual steer UE);

[0306] Only IPv4 session type is allowed (i.e. PDU session type IPv4 only allowed);

[0307] Only IPv6 session type is allowed (i.e. PDU session type IPv6 only allowed);

[0308] Only IPv4v6 session type is allowed (i.e. PDU session type IPv4v6 only allowed);

[0309] Only multiple access session types are allowed (ie, PDU session type Ethernet only allowed).

[0310] For example, if the current network only allows IPv4 session type, if the second session type carried in the fourth request received by the third communication device is not an IPv4 session type, the third communication device may also refuse to establish the PDU session in the fourth response.

[0311] In addition to direct rejection, as mentioned above, the third communication device can also modify the session type, the essence of which is to modify the session type that does not meet the network and / or session requirements to a session type that meets its requirements. For example, in the above-mentioned scenario where only IPv4 session types are allowed, if the session type carried in the fourth request is not an IPv4 session type, the third communication device can modify the session type to an IPv4 session type to meet network requirements. For another example, in the scenario described above where the session types of the DualSteer-associated terminals are inconsistent, if the second session type carried in the fourth request is inconsistent with the first session type, the third communication device can modify the second session type to the first session type to meet the DualSteer session requirements.

[0312] Therefore, in an exemplary embodiment, before the third communication device sends the fourth response, the method further includes:

[0313] The third communication device modifies the second session type in the fourth request to the first session type.

[0314] For easier understanding, please refer to Figure 8 , Figure 8 FIG. 1 is a flow chart of another communication method provided by an embodiment of the present disclosure. Figure 8 As shown, UE1 and UE2 are a group of terminals with a DualSteer association relationship, and UE1 first accesses the network and has established a session for DualSteer, and the session type is the first session type (for the specific implementation method, refer to the first communication device mentioned above).

[0315] S1-S2, such as Figure 8 As shown, after UE1 accesses the network, SMF saves the PDU session type (ie, the first session type) used by UE1 for DualSteer to UDM.

[0316] Specifically, SMF can update the UE subscription information stored in UDM through an update request (or a request to update the terminal subscription information), which can be a Nudm_UECM_Update request message. After the update, the content stored in UDM may include but is not limited to: SUPI1 of UE1, association identifier (used to identify DualSteer association), PDU session type, SUPI2 of UE2. Accordingly, in S2, UDM feeds back an update response (i.e., Nudm_UECM_Update response message) to SMF.

[0317] Afterwards, UE2 accesses the network, and the access process is as follows:

[0318] S3, UE2 sends a PDU session establishment request (i.e., PDU session establishment request) to AMF. The session is used for DualSteer, and the session type is the second session type.

[0319] S4, AMF sends an SM context creation request for the PDU session to SMF (that is, the fourth request above, which can be specifically Nsmf_PDUSession_CreateSMContext request), and carries the second session type therein.

[0320] S5, SMF sends a get request (specifically, Nudm_SDM_Get request) to UDM to request to obtain the contract information of the terminal.

[0321] Specifically, this step is essentially used to at least obtain the session type for DualSteer of UE1. In an actual implementation scenario, the acquisition request may carry at least one of the following information: SUPI 2 of UE2, SUPI 1 of UE1, and an association identifier.

[0322] In actual scenarios, for SMF, if the request type initiated by UE is Dual Steer session, in other words, only when the session type it requests belongs to DualSteer session type, and the session will be used for DualSteer transmission later, SMF needs to check the PDU session type of UE1; otherwise, it can be processed normally without executing the following steps: Figure 8The query and subsequent modification operations of S5-S6 are shown.

[0323] S6, SMF receives a get response (specifically Nudm_SDM_Get response) sent from UDM, which carries at least the first session type of UE1.

[0324] S7, SMF modifies the session type, that is, changes the first session type to the second session type.

[0325] S8, SMF sends the SM context creation of the PDU session to AMF (that is, the fourth request above, which can be specifically Nsmf_PDUSession_CreateSMContext request), and carries the second session type and the PDU session establishment acceptance.

[0326] S9, AMF sends a PDU session establishment accept message to UE2, i.e., a PDU session establishment acceptance message. The session acceptance message carries the second session type, which is the session type modified by SMF.

[0327] In this way, by modifying the session type through SMF, it can be ensured that the PDU session used by the DualSteer terminal for DualSteer can access the network according to the same session type, giving full play to the transmission advantages of DualSteer technology, improving efficiency and saving resources.

[0328] In summary, in the communication method provided by the present disclosure, when the first communication device receives a request to obtain a first policy, it can carry an indication of the session type in the sent first policy. In this way, the recipient of the first policy can establish subsequent PDU sessions based on this, thereby ensuring that the DualSteer associated terminals can establish the same type of PDU sessions. In addition, the third communication device can also manage and control the session establishment process based on the session type carried in the request to avoid inconsistencies in the session types of the DualSteer associated terminals. In summary, the technical solution provided by the present disclosure can achieve the same session types for DualSteer associated terminals, solve the problem of different session types of DualSteer associated terminals limiting the development of DualSteer technology, and is conducive to giving full play to the advantages of multi-stream transmission and improving communication quality.

[0329] The present disclosure also provides a communication device. Fig. 9 A structural block diagram of a communication device provided in an embodiment of the present disclosure, such as Fig. 9 As shown, the communication device 900 includes a transceiver unit 910, and the transceiver unit 910 is used to perform at least one of the following:

[0330] receiving a first request, wherein the first request includes first information, and the first request is used to request obtaining a first policy;

[0331] Sending second information; wherein the second information includes the first strategy;

[0332] The first policy includes a first session type.

[0333] In an exemplary embodiment, the first strategy is used for at least one of the following: traffic routing, diversion, switching to a dual-direction session; establishing a dual-direction session;

[0334] The dual-direction conversation includes at least one of the following:

[0335] First session;

[0336] Second session.

[0337] In an exemplary embodiment, the first session type includes at least one of the following:

[0338] Double turn session type;

[0339] IPv4 session type;

[0340] IPv6 session type;

[0341] IPv4v6 session type;

[0342] Multiple access session type.

[0343] In an exemplary embodiment, the sending of the second information includes:

[0344] The second information is sent when a first condition is met, where the first condition includes at least one of the following:

[0345] The second terminal is in a registered state;

[0346] The first terminal is in a registered state;

[0347] The first terminal and the second terminal have a first capability;

[0348] There is a first association relationship between the first terminal and the second terminal.

[0349] In an exemplary embodiment, the first association relationship satisfies at least one of the following:

[0350] The first terminal and the second terminal belong to the same dual-steering device;

[0351] The first terminal identifier and the second terminal identifier correspond to the same association identifier.

[0352] In an exemplary embodiment, the first capability satisfies at least one of the following:

[0353] The first capability is used to describe that the terminal has or supports dual-steering capability;

[0354] The first capability includes at least one of the following:

[0355] Support or have dual steering capability;

[0356] Support traffic diversion and / or switching to dual-direction sessions;

[0357] Support continuous or discontinuous transmission;

[0358] Supporting traffic diversion and / or switching to a session of a first access corresponding to a first SUPI or switching to a session of a second access corresponding to a second SUPI; wherein the first SUPI is different from the second SUPI, and the first access is different from the second access.

[0359] In an exemplary embodiment, the transceiver unit 910 is further used for at least one of the following:

[0360] receiving a second request, the second request including third information, the second request being used to request establishment of a policy association for the second terminal;

[0361] sending fourth information, wherein the fourth information includes the second strategy;

[0362] The second policy includes the first session type.

[0363] In an exemplary embodiment, the second strategy is used for at least one of the following: traffic routing, diversion, switching to a dual-direction session; and establishing a dual-direction session.

[0364] In an exemplary embodiment, the transceiver unit 910 is specifically configured to: when a first condition is met, send the second information to the first terminal, and send the fourth information to the second terminal;

[0365] Wherein, the fourth information includes a second strategy;

[0366] The second policy includes the first session type.

[0367] In an exemplary embodiment, the first information includes at least one of the following:

[0368] First terminal identification information;

[0369] capability information of the first terminal;

[0370] The first contract information; wherein, the first contract information satisfies at least one of the following: the first contract information is used to indicate at least one of that the first terminal belongs to a dual-steering device or that a first association relationship exists between the first terminal and the second terminal; the first contract information includes at least one of the following: an association identifier.

[0371] In an exemplary embodiment, the third information includes at least one of the following:

[0372] Second terminal identification information;

[0373] capability information of the second terminal;

[0374] The second contract information; wherein, the second contract information satisfies at least one of the following: the second contract information is used to indicate at least one of that the second terminal belongs to a dual-direction device or that a first association relationship exists between the first terminal and the second terminal; the second contract information includes at least one of the following: an association identifier.

[0375] In an exemplary embodiment, the communication device further includes a processing unit, configured to delete or update the first strategy when a second condition is met;

[0376] The second condition includes at least one of the following:

[0377] The first association relationship between the first terminal and the second terminal is released;

[0378] at least one of the first terminal and the second terminal disabling a first capability;

[0379] At least one of the first terminal and the second terminal is in a deregistered state.

[0380] In an exemplary embodiment, the transceiver unit 910 is further configured to perform at least one of the following:

[0381] Sending a third request to the second communication device, where the third request is used to request to obtain or subscribe to the registration status of the terminal;

[0382] Fifth information is received from the second communication device, where the fifth information includes a registration status of at least one terminal.

[0383] In an exemplary embodiment, the terminal satisfies at least one of the following:

[0384] The terminal is at least one of the first terminal or the second terminal;

[0385] The terminal is a dual-steering device;

[0386] The terminal has a first association relationship.

[0387] In an exemplary embodiment, the transceiver unit 910 is specifically configured to: send the second information to the first terminal; or send the second information to a dual-steering device, where the first terminal and the second terminal belong to the same dual-steering device.

[0388] In an exemplary embodiment, the first terminal and the second terminal belong to the same dual-direction device.

[0389] In an exemplary embodiment, the first strategy satisfies at least one of the following:

[0390] When the dual-steering device supports continuous transmission, the routing descriptor of the first strategy includes: a first terminal identifier and / or a second terminal identifier;

[0391] When the dual-direction device does not support continuous transmission, the routing descriptor of the first strategy includes: a first terminal identifier or a second terminal identifier.

[0392] In an exemplary embodiment, the second information further includes a third strategy for non-dual steering transmission; or, the transceiver unit 910 is further used to send sixth information, and the sixth information includes the third strategy for non-dual steering transmission.

[0393] The present disclosure also provides another communication device. Fig.10 A structural block diagram of another communication device provided in an embodiment of the present disclosure, such as Fig.10 As shown, the communication device 1000 includes a transceiver unit 1010, and the transceiver unit 1010 is used to perform at least one of the following:

[0394] receiving a fourth request, wherein the fourth request carries a second session type;

[0395] Request or obtain seventh information;

[0396] Sending a fourth response, the fourth response including at least one of the following:

[0397] First session type;

[0398] PDU session establishment accept;

[0399] PDU session establishment rejected;

[0400] PDU session establishment rejection reason.

[0401] In an exemplary embodiment, the first session type is different from the second session type.

[0402] In an exemplary embodiment, the transceiver unit 1010 is specifically used for at least one of the following:

[0403] When the third condition is not met, sending the fourth response, wherein the fourth response includes a PDU session establishment rejection;

[0404] When the third condition is met, the fourth response is sent, wherein the fourth response includes at least one of a PDU session establishment acceptance and a first session type.

[0405] In an exemplary embodiment, the third condition includes at least one of the following:

[0406] There is a first association relationship between the first terminal and the second terminal;

[0407] The first terminal and the second terminal meet a first condition;

[0408] The first session type is the same as the second session type.

[0409] In an exemplary embodiment, the first condition includes at least one of the following:

[0410] The second terminal is in a registered state;

[0411] The first terminal is in a registered state;

[0412] The first terminal and the second terminal have a first capability;

[0413] There is a first association relationship between the first terminal and the second terminal.

[0414] In an exemplary embodiment, the first association relationship satisfies at least one of the following:

[0415] The first terminal and the second terminal belong to the same dual-steering device;

[0416] The first terminal identifier and the second terminal identifier correspond to the same association identifier.

[0417] In an exemplary embodiment, the first capability satisfies at least one of the following:

[0418] The first capability is used to describe that the terminal has or supports dual-steering capability;

[0419] The first capability includes at least one of the following:

[0420] Support or have dual steering capability;

[0421] Support traffic diversion and / or switching to dual-direction sessions;

[0422] Support continuous or discontinuous transmission;

[0423] Supporting traffic diversion and / or switching to a session of a first access corresponding to a first SUPI or switching to a session of a second access corresponding to a second SUPI; wherein the first SUPI is different from the second SUPI, and the first access is different from the second access.

[0424] In an exemplary embodiment, the seventh information includes at least one of the following:

[0425] First association relationship;

[0426] First session type;

[0427] First strategy;

[0428] First signing information;

[0429] Second signing information.

[0430] In an exemplary embodiment, the transceiver unit 1010 is specifically configured to:

[0431] Sending a fifth request to the second communication device, where the fifth request is used to request to obtain or subscribe to contract information of at least one of the first terminal and the second terminal;

[0432] A fifth response is received from the second communication device, where the fifth response carries the seventh information.

[0433] In an exemplary embodiment, the first session type satisfies at least one of the following:

[0434] The first session type is a dual-direction session type;

[0435] The first session type is a session type of the first session.

[0436] In an exemplary embodiment, the first session type includes at least one of the following:

[0437] Double turn session type;

[0438] IPv4 session type;

[0439] IPv6 session type;

[0440] IPv4v6 session type;

[0441] Multiple access session type.

[0442] In an exemplary embodiment, the second session type satisfies at least one of the following:

[0443] The second session type is a dual-direction session type;

[0444] The second session type is a session type of the second session.

[0445] In an exemplary embodiment, the first session is established by the first terminal; and / or the second session is established by the second terminal.

[0446] In an exemplary embodiment, the PDU session establishment rejection reason includes at least one of the following:

[0447] The session type is not allowed;

[0448] The session type is inconsistent with the dual-direction terminal session type;

[0449] Only IPv4 session type is allowed;

[0450] Only IPv6 session type is allowed;

[0451] Only IPv4v6 session types are allowed;

[0452] Only multi-access session type is allowed.

[0453] In an exemplary embodiment, the communication device 1000 may further include a processing unit, which is specifically configured to: before sending the fourth response, modify the second session type in the fourth request to the first session type.

[0454] The present disclosure also provides a communication system. Fig.11 A structural block diagram of a communication system provided in an embodiment of the present disclosure, such as Fig.11 As shown, the communication system 1100 includes:

[0455] A first communication device 1110, configured to implement the communication method performed by the first communication device in any one of the above embodiments;

[0456] The third communication device 1120 is used to implement the communication method executed by the third communication device in any one of the above embodiments.

[0457] In a further embodiment, the communication system 1100 may also include a second communication device.

[0458] For any parts not described in detail, please refer to the previous text.

[0459] Fig.12 The electronic device 1200 according to the embodiment of the present disclosure includes at least a memory, a processor and a computer program stored in the memory, and the processor executes the computer program to implement the communication method described in any of the above embodiments.

[0460] Fig.12The electronic device 1200 shown specifically includes: a central processing unit (CPU) 1201, a graphics processing unit (GPU) 1202 and a memory 1203. These units are connected to each other via a bus 1204. The central processing unit (CPU) 1201 and / or the graphics processing unit (GPU) 1202 can be used as the above-mentioned processor, and the memory 1203 can be used as the above-mentioned memory storing computer-readable instructions. In addition, the electronic device 1200 may also include a communication unit 1205, a storage unit 1206, an output unit 1207, an input unit 1208 and an external device 1209, which are also connected to the bus 1204.

[0461] Fig.13 A schematic diagram of a computer-readable storage medium provided in an embodiment of the present disclosure. A computer-readable storage medium according to an embodiment of the present disclosure stores a computer program / instruction. For example, Fig.13 In the illustrated embodiment, a computer-readable storage medium 1300 stores computer-readable instructions 1301. When the computer program / instructions are executed by the processor, the communication method described in any of the foregoing embodiments of the present disclosure is implemented. The computer-readable storage medium includes, but is not limited to, for example, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

[0462] The present disclosure further provides a computer program product, including a computer program, which implements the communication method described in any of the foregoing embodiments of the present disclosure when executed by a processor.

[0463] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0464] The block diagrams of the devices, apparatuses, equipment, and systems involved in this disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including," "comprising," "having," and the like are open words, referring to "including but not limited to," and can be used interchangeably therewith. The words "or" and "and" used herein refer to the words "and / or," and can be used interchangeably therewith, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to," and can be used interchangeably therewith.

[0465] Additionally, as used herein, "or" used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not mean that the example described is preferred or better than other examples.

[0466] It should also be noted that in the system and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0467] Various changes, substitutions, and modifications of the techniques described herein may be made without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of the present disclosure is not limited to the specific aspects of the processes, machines, manufactures, compositions of events, means, methods, and actions described above. Currently existing or later to be developed processes, machines, manufactures, compositions of events, means, methods, or actions that perform substantially the same functions or achieve substantially the same results as the corresponding aspects described herein may be utilized. Thus, the appended claims include such processes, machines, manufactures, compositions of events, means, methods, or actions within their scope.

[0468] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0469] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A communication method, characterized in that: The first communication device performs a first operation, where the first operation includes at least one of the following: receiving a first request, wherein the first request includes first information, and the first request is used to request obtaining a first policy; Sending second information; wherein the second information includes the first strategy; The first policy includes a first session type.

2. The method according to claim 1, characterized in that The first strategy is used for at least one of the following: traffic routing, diversion, switching to a dual-direction session; establishing a dual-direction session; The dual-direction conversation includes at least one of the following: First session; Second session.

3. The method according to claim 1, characterized in that The first session type includes at least one of the following: Double turn session type; IPv4 session type; IPv6 session type; IPv4v6 session type; Multiple access session type.

4. The method according to claim 1, characterized in that The sending of the second information comprises: The second information is sent when a first condition is met, where the first condition includes at least one of the following: The second terminal is in a registered state; The first terminal is in a registered state; The first terminal and the second terminal have a first capability; There is a first association relationship between the first terminal and the second terminal.

5. The method according to claim 4, characterized in that The first association relationship satisfies at least one of the following: The first terminal and the second terminal belong to the same dual-steering device; The first terminal identifier and the second terminal identifier correspond to the same association identifier.

6. The method according to claim 4, characterized in that The first capability satisfies at least one of the following: The first capability is used to describe that the terminal has or supports dual steering capability; The first capability includes at least one of the following: Support or have dual steering capability; Support traffic diversion and / or switching to dual-direction sessions; Support continuous or discontinuous transmission; Supporting traffic diversion and / or switching to a session of a first access corresponding to a first SUPI or switching to a session of a second access corresponding to a second SUPI; wherein the first SUPI is different from the second SUPI, and the first access is different from the second access.

7. The method according to any one of claims 1 to 6, characterized in that: The first communication device performs a second operation, where the second operation includes at least one of the following: receiving a second request, the second request including third information, the second request being used to request establishment of a policy association for the second terminal; sending fourth information, wherein the fourth information includes the second strategy; The second policy includes the first session type.

8. The method according to claim 7, characterized in that in, The second strategy is used for at least one of the following: traffic routing, diversion, switching to a dual-direction session; and establishing a dual-direction session.

9. The method according to any one of claims 1 to 8, characterized in that: The sending of the second information comprises: When the first condition is met, sending the second information to the first terminal, and sending fourth information to the second terminal; Wherein, the fourth information includes a second strategy; The second policy includes the first session type.

10. The method according to any one of claims 1 to 9, characterized in that: The first information includes at least one of the following: First terminal identification information; capability information of the first terminal; The first contract information; wherein, the first contract information satisfies at least one of the following: the first contract information is used to indicate at least one of that the first terminal belongs to a dual-steering device or that a first association relationship exists between the first terminal and the second terminal; the first contract information includes at least one of the following: an association identifier.

11. The method according to claim 7, characterized in that The third information includes at least one of the following: Second terminal identification information; capability information of the second terminal; The second contract information; wherein, the second contract information satisfies at least one of the following: the second contract information is used to indicate at least one of that the second terminal belongs to a dual-direction device or that a first association relationship exists between the first terminal and the second terminal; the second contract information includes at least one of the following: an association identifier.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: When the second condition is met, deleting or updating the first strategy; The second condition includes at least one of the following: The first association relationship between the first terminal and the second terminal is released; at least one of the first terminal and the second terminal disabling a first capability; At least one of the first terminal and the second terminal is in a deregistered state.

13. The method according to any one of claims 1 to 12, characterized in that: The method further comprises at least one of the following: Sending a third request to the second communication device, where the third request is used to request to obtain or subscribe to the registration status of the terminal; Fifth information is received from the second communication device, where the fifth information includes a registration status of at least one terminal.

14. The method according to claim 13, characterized in that The terminal satisfies at least one of the following: The terminal is at least one of the first terminal or the second terminal; The terminal is a dual-steering device; The terminal has a first association relationship.

15. The method according to any one of claims 1 to 14, characterized in that: The sending of the second information comprises: sending the second information to the first terminal; or, The second information is sent to a dual-steering device, wherein the first terminal and the second terminal belong to the same dual-steering device.

16. The method according to any one of claims 1 to 15, characterized in that: The first terminal and the second terminal belong to the same double-turn device.

17. The method according to claim 16, characterized in that The first strategy satisfies at least one of the following: When the dual-steering device supports continuous transmission, the routing descriptor of the first strategy includes: a first terminal identifier and / or a second terminal identifier; When the dual-direction device does not support continuous transmission, the routing descriptor of the first strategy includes: a first terminal identifier or a second terminal identifier.

18. The method according to any one of claims 1 to 17, characterized in that: The second information also includes a third strategy for non-dual steering transmission; or, The method further includes sending sixth information including a third strategy for non-dual steering transmission.

19. A communication method, characterized in that: The third communication device performs a third operation, where the third operation includes at least one of the following: receiving a fourth request, wherein the fourth request carries a second session type; Request or obtain seventh information; Sending a fourth response, the fourth response including at least one of the following: First session type; PDU session establishment accept; PDU session establishment rejected; PDU session establishment rejection reason.

20. The method according to claim 19, characterized in that The first session type is different from the second session type.

21. The method according to claim 19 or 20, characterized in that The sending of the fourth response includes at least one of the following: When the third condition is not met, sending the fourth response, wherein the fourth response includes a PDU session establishment rejection; When the third condition is met, the fourth response is sent, wherein the fourth response includes at least one of a PDU session establishment acceptance and a first session type.

22. The method according to claim 21, characterized in that The third condition includes at least one of the following: There is a first association relationship between the first terminal and the second terminal; The first terminal and the second terminal meet a first condition; The first session type is the same as the second session type.

23. The method according to claim 22, characterized in that The first condition includes at least one of the following: The second terminal is in a registered state; The first terminal is in a registered state; The first terminal and the second terminal have a first capability; There is a first association relationship between the first terminal and the second terminal.

24. The method according to claim 22, characterized in that The first association relationship satisfies at least one of the following: The first terminal and the second terminal belong to the same dual-steering device; The first terminal identifier and the second terminal identifier correspond to the same association identifier.

25. The method according to claim 23, characterized in that The first capability satisfies at least one of the following: The first capability is used to describe that the terminal has or supports dual steering capability; The first capability includes at least one of the following: Support or have dual steering capability; Support traffic diversion and / or switching to dual-direction sessions; Support continuous or discontinuous transmission; Supporting traffic diversion and / or switching to a session of a first access corresponding to a first SUPI or switching to a session of a second access corresponding to a second SUPI; wherein the first SUPI is different from the second SUPI, and the first access is different from the second access.

26. The method according to any one of claims 19 to 25, characterized in that: The seventh information includes at least one of the following: First association relationship; First session type; First strategy; First signing information; Second signing information.

27. The method according to any one of claims 19 to 26, characterized in that: The request to obtain the seventh information includes: Sending a fifth request to the second communication device, where the fifth request is used to request to obtain or subscribe to contract information of at least one of the first terminal and the second terminal; A fifth response is received from the second communication device, where the fifth response carries the seventh information.

28. The method according to any one of claims 19 to 27, characterized in that: The first session type satisfies at least one of the following: The first session type is a dual-direction session type; The first session type is a session type of the first session.

29. The method according to claim 28, characterized in that The first session type includes at least one of the following: Double turn session type; IPv4 session type; IPv6 session type; IPv4v6 session type; Multiple access session type.

30. The method according to any one of claims 19 to 29, characterized in that: The second session type satisfies at least one of the following: The second session type is a dual-direction session type; The second session type is a session type of the second session.

31. The method according to any one of claims 28 to 30, characterized in that: The first session is established by the first terminal; and / or, The second session is established by the second terminal.

32. The method according to any one of claims 19 to 31, characterized in that: The PDU session establishment rejection reason includes at least one of the following: The session type is not allowed; The session type is inconsistent with the dual-direction terminal session type; Only IPv4 session type is allowed; Only IPv6 session type is allowed; Only IPv4v6 session types are allowed; Only multi-access session type is allowed.

33. The method according to any one of claims 19 to 32, characterized in that: Before sending the fourth response, the method further includes: The second session type in the fourth request is modified to the first session type.

34. A communication device, characterized in that: The device comprises a transceiver unit, wherein the transceiver unit is configured to perform at least one of the following: receiving a first request, wherein the first request includes first information, and the first request is used to request obtaining a first policy; Sending second information; wherein the second information includes the first strategy; The first policy includes a first session type.

35. A communication device, characterized in that: The device comprises a transceiver unit, wherein the transceiver unit is configured to perform at least one of the following: receiving a fourth request, wherein the fourth request carries a second session type; Request or obtain seventh information; Sending a fourth response, the fourth response including at least one of the following: First session type; PDU session establishment accept; PDU session establishment rejected; PDU session establishment rejection reason.

36. A communication system, characterized in that: include: A first communication device, configured to implement the communication method according to any one of claims 1 to 18; A third communication device, used to implement the communication method as described in any one of claims 19-33.

37. An electronic device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the method according to any one of claims 1 to 33.

38. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 33 is implemented.

39. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method described in any one of claims 1 to 33 is implemented.

Images