Device adding method, device, device adding apparatus, storage medium and program product

Abstract

The application relates to a device adding method, device, storage medium and program product. The method comprises the following steps: in the case that a gateway device adds a target device, sending data flow binding information to a core network device, the data flow binding information being used for instructing the core network device to bind a data flow of the target device to a target quality of service (Qos) flow of a protocol data unit (PDU) session; and then, receiving response information sent by the core network device in response to the data flow binding information. According to the method, the data flow of the target device can be bound to the Qos flow in the PDU session when the gateway device adds the target device.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a device adding method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the development of communication technology, 5G residential gateways (5G-RG) are typically connected to non-3GPP devices. The Protocol Data Unit (PDU) session between the 5G residential gateway and the data network can include one or more Quality of Service (QoS) streams.

[0003] After a PDU session is established, if a device is added to the 5G home gateway, the existing technology does not discuss the signaling process for binding the data flow of the device to the QoS flow. Summary of the Invention

[0004] This application provides a device addition method, apparatus, device, storage medium, and program product.

[0005] In a first aspect, a device addition method is provided for use in a gateway device. The method includes: when a target device is added to the gateway device, sending data flow binding information to a core network device, wherein the data flow binding information is used to instruct the core network device to bind the data flow of the target device to the target QoS flow of the Protocol Data Unit (PDU) session; and receiving response information sent by the core network device in response to the data flow binding information.

[0006] In one embodiment, sending data flow binding information to the core network device includes: sending a PDU session modification request message to the Access and Mobility Management Function (AMF), the PDU session modification request message carrying data flow binding information, the PDU session modification request message being used to trigger the AMF to send a context update request message to the Session Management Function (SMF), the context update request message carrying data flow binding information, and the data flow binding being used to trigger the SMF to bind the data flow of the target device to the target QoS flow.

[0007] In one embodiment, the target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

[0008] In one embodiment, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; and second indication information for instructing the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0009] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; second indication information for instructing the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0010] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0011] In one embodiment, the target device is a non-3GPP non-3rd Generation Partnership Project (3GPP) device.

[0012] In one embodiment, the gateway device is a 5G-home gateway or a user equipment.

[0013] Secondly, a device addition method is provided for core network devices. The method includes: receiving data flow binding information sent by a gateway device when adding a target device; binding the data flow of the target device to a target QoS flow of a Protocol Data Unit (PDU) session based on the data flow binding information; and sending response information to the gateway device in response to the data flow binding information.

[0014] In one embodiment, receiving data stream binding information sent by the gateway device includes: receiving a context update request message sent by the Access and Mobility Management Function (AMF), wherein the context update request message carries data stream binding information and is triggered by the gateway device sending a PDU session modification request message to the AMF.

[0015] In one embodiment, the target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

[0016] In one embodiment, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; and second indication information for instructing the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0017] In one embodiment, binding the data stream of the target device to the target QoS stream of the PDU session includes: sending a policy control update request message to the policy control function (PCF), the policy control update request message carrying the device identifier of the target device and policy rule creation indication information, the policy rule creation indication information being used to trigger the PCF to establish a dedicated QoS stream in the PDU session; and receiving response information sent by the PCF in response to the policy control update request message.

[0018] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; second indication information for instructing the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0019] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0020] In one embodiment, binding the data stream of the target device to the target QoS stream of the PDU session includes: sending a policy control update request message to the policy control function (PCF), the policy control update request message carrying the device identifier of the target device and update policy rule indication information, the update policy rule indication information being used to trigger the PCF to update the target QoS stream; and receiving response information sent by the PCF in response to the policy control update request message.

[0021] Thirdly, a device adding apparatus is provided, disposed in a gateway device, the apparatus comprising:

[0022] The sending module is used to send data flow binding information to the core network device when the gateway device adds a target device. The data flow binding information is used to instruct the core network device to bind the data flow of the target device to the target QoS flow of the Protocol Data Unit (PDU) session.

[0023] The receiving module is used to receive response information sent by the core network device in response to the data flow binding information.

[0024] In one embodiment, the sending module is specifically used to send a PDU session modification request message to the Access and Mobility Management Function (AMF). The PDU session modification request message carries data stream binding information. The PDU session modification request message is used to trigger the AMF to send a context update request message to the Session Management Function (SMF). The context update request message carries data stream binding information. The data stream binding is used to trigger the SMF to bind the data stream of the target device to the target QoS stream.

[0025] In one embodiment, the target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

[0026] In one embodiment, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; and second indication information for instructing the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0027] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; second indication information for instructing the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0028] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0029] In one embodiment, the target device is a non-3GPP non-3rd Generation Partnership Project (3GPP) device.

[0030] In one embodiment, the gateway device is a 5G-home gateway or a user equipment.

[0031] Fourthly, a device adding apparatus is provided, disposed in a core network device, the apparatus comprising:

[0032] The receiving module is used to receive data stream binding information sent by the gateway device, wherein the data stream binding information is sent by the gateway device when adding a target device;

[0033] The binding module is used to bind the data stream of the target device to the target QoS stream of the Protocol Data Unit (PDU) session based on the data stream binding information.

[0034] The sending module is used to send a response to the data stream binding information to the gateway device.

[0035] In one embodiment, the receiving module is specifically used to receive a context update request message sent by the Access and Mobility Management Function (AMF). The context update request message carries data stream binding information and is triggered by the gateway device sending a PDU session modification request message to the AMF.

[0036] In one embodiment, the target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

[0037] In one embodiment, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; and second indication information for instructing the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0038] In one embodiment, the sending module is further configured to send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and the policy rule creation instruction information. The policy rule creation instruction information is used to trigger the PCF to establish a dedicated QoS stream in the PDU session. The receiving module is further configured to receive the response information sent by the PCF in response to the policy control update request message.

[0039] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; second indication information for instructing the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0040] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0041] In one embodiment, the sending module is further configured to send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and update policy rule indication information. The update policy rule indication information is used to trigger the PCF to update the target QoS stream. The receiving module is further configured to receive response information sent by the PCF in response to the policy control update request message.

[0042] Fifthly, this application also provides a gateway device, including a memory, a transceiver, and a processor:

[0043] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and executing any of the methods described in the first aspect by controlling the transceiver.

[0044] In a sixth aspect, this application also provides a core network device, including a memory, a transceiver, and a processor: the memory for storing a computer program; the transceiver for transmitting and receiving data under the control of the processor; and the processor for reading the computer program in the memory and executing any of the methods described in the second aspect above by controlling the transceiver.

[0045] In a seventh aspect, this application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any of the steps described in the first aspect above; or, the computer program, when executed by a processor, implements any of the steps described in the second aspect above.

[0046] Eighthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements any of the steps described in the first aspect above; or, when executed by a processor, the computer program implements any of the steps described in the second aspect above.

[0047] The aforementioned device addition method, apparatus, device, storage medium, and program product, when adding a target device to a gateway device, sends data flow binding information to the core network device. This data flow binding information instructs the core network device to bind the target device's data flow to the target QoS flow of the Protocol Data Unit (PDU) session. Then, it receives a response from the core network device in response to the data flow binding information. Thus, the data flow binding information indicates the target QoS flow to which the data flow should be bound. By sending the data flow binding information to the core network device, the core network device can bind the target device's data flow to the target QoS flow according to the data flow binding information, and determine the data flow binding result based on the received response message. The above discussion of the signaling processing procedure enables the binding of the target device's data flow to the QoS flow in the PDU session when adding a target device to a gateway device. Attached Figure Description

[0048] Figure 1 This is a schematic diagram of a gateway device connecting multiple devices in one embodiment;

[0049] Figure 2 This is a schematic diagram illustrating the data stream binding of multiple devices in a PDU session in one embodiment;

[0050] Figure 3 This is a diagram illustrating the application environment of a device addition method in one embodiment.

[0051] Figure 4 A flowchart illustrating a device addition method in one embodiment;

[0052] Figure 5 This is a schematic diagram illustrating the data stream binding of each device in a PDU session when adding a target device in one embodiment;

[0053] Figure 6 This is a schematic diagram of signaling interaction between a gateway device and a core network device in one embodiment;

[0054] Figure 7 This is a schematic diagram of signaling interaction between a gateway device and a core network device in one embodiment;

[0055] Figure 8 This is a schematic diagram of signaling interaction between a gateway device and a core network device in one embodiment;

[0056] Figure 9A flowchart illustrating a device addition method in one embodiment;

[0057] Figure 10 This is a flowchart illustrating the step of binding a data stream from a target device to a dedicated QoS stream in one embodiment.

[0058] Figure 11 This is a flowchart illustrating the steps of binding a data stream from a target device to an existing QoS stream in one embodiment.

[0059] Figure 12 This is a structural block diagram of a device adding apparatus in one embodiment of this application;

[0060] Figure 13 This is a structural block diagram of a device adding apparatus in another embodiment of this application;

[0061] Figure 14 This is a schematic diagram of the gateway device in one embodiment of this application;

[0062] Figure 15 This is a schematic diagram of the core network device in one embodiment of this application. Detailed Implementation

[0063] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0064] With the development of communication technology, 5G residential gateways (5G-RG) are typically connected to non-3GPP (Non-Third Generation Partnership Project) devices. The Protocol Data Unit (PDU) session between the 5G residential gateway and the data network can include one or more Quality of Service (QoS) streams. For example... Figure 1 As shown, the 5G-RG device connects to multiple devices, which can correspond to different PDU sessions and different quality of service flows, such as... Figure 2 As shown, the data stream for each device can be a different QoS stream or the same QoS stream.

[0065] After a PDU session is established, if a device is added to the 5G home gateway, the existing technology does not discuss the signaling process for binding the data flow of the device to the QoS flow.

[0066] It should be noted that the beneficial effects or technical problems solved by the embodiments of this application are not limited to this one, but may also be other implicit or related problems. For details, please refer to the description of the embodiments below.

[0067] Please refer to Figure 3 This illustration shows an application scenario diagram of a device addition method provided in an embodiment of this application. For example... Figure 3 As shown, this application scenario can include gateway device 301 and core network device 302.

[0068] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0069] In one embodiment, such as Figure 4 As shown, a device addition method is provided, which is applied to Figure 3 Taking gateway device 301 as an example, the explanation includes the following steps:

[0070] Step 401: When a target device is added to the gateway device, the gateway device sends data flow binding information to the core network device.

[0071] Among them, the data flow binding information is used to instruct the core network device to bind the data flow of the target device to the target QoS flow of the Protocol Data Unit (PDU) session.

[0072] Optionally, the target equipment can be non-3GPP equipment that is not part of the 3GPP Partner Program.

[0073] Optionally, the gateway device can be a 5G-home gateway or a user device.

[0074] Optionally, the core network equipment can be a Session Management Function (SMF).

[0075] Optionally, there may be multiple target devices, and a target QoS stream can be bound to the data streams of multiple target devices at the same time. The data streams of multiple target devices can be bound to the same target QoS stream.

[0076] Optional, such as Figure 5 As shown, binding the data stream of the target device to the target QoS stream of the PDU session can include the following two cases: Method 1, binding the data stream of the target device to an existing QoS stream in the PDU session; Method 2, binding the data stream of the target device to a dedicated QoS stream in the PDU session.

[0077] Optionally, a dedicated QoS flow is a special type of QoS flow in a PDU session, used to meet the QoS requirements of specific services. The QoS parameters of a dedicated QoS flow can be dynamically allocated by the network according to service requirements or pre-configured.

[0078] Step 402: The gateway device receives the response information sent by the core network device for the data flow binding information.

[0079] Optionally, it can be determined whether the data stream of the target device has been successfully bound to the target QoS stream based on the response information sent by the core network device.

[0080] Optionally, the response information may be carried by messages related to PDU session modification, wherein the messages related to PDU session modification can coordinate the update of session parameters between the gateway device and the network. This application embodiment does not limit the type of messages related to PDU session modification.

[0081] In one possible implementation, the gateway device receives a PDU SessionModification Reject message sent by the core network device. The PDU Session Modification Reject message carries first response information, which is used to indicate that a data flow binding rejection message is sent to the gateway device when the network cannot complete the data flow binding.

[0082] In another possible implementation, the gateway device can receive a PDU Session Modification Command / ack message. The PDU Session Modification Command / ack message carries a second response message, which indicates that the data stream has been successfully bound to the target QoS stream. The second response message may also include QoS parameters, transmission configuration information, etc., where the QoS parameters may include QoS rules and QoS stream parameters.

[0083] The above-described device addition method, when adding a target device to a gateway device, involves sending data flow binding information to the core network device. This data flow binding information instructs the core network device to bind the target device's data flow to the target QoS flow of the Protocol Data Unit (PDU) session. Then, the core network device receives a response message from the core network device in response to the data flow binding information. Thus, the data flow binding information indicates the target QoS flow to which the data flow should be bound. By sending this information to the core network device, the core network device can bind the target device's data flow to the target QoS flow based on the data flow binding information and determine the data flow binding result based on the received response message. The signaling processing described above enables the binding of the target device's data flow to the QoS flow in the PDU session when adding a target device to a gateway device.

[0084] In one exemplary embodiment, sending data flow binding information to the core network device includes:

[0085] A PDU session modification request message is sent to the Access and Mobility Management Function (AMF). The PDU session modification request message carries data flow binding information. The PDU session modification request message is used to trigger the AMF to send a context update request message to the Session Management Function (SMF). The context update request message carries data flow binding information. The data flow binding is used to trigger the SMF to bind the data flow of the target device to the target QoS flow.

[0086] It is understandable that the PDU session modification is triggered by the gateway device.

[0087] Optionally, when the gateway device sends data flow binding information to the core network device, it can do so in the following way: send a Non-Access Stratum (NAS) message to the Access and Mobility Management Function (AMF), which is then received by the AMF and forwarded to the SMF. In this embodiment, the NAS message can be a PDU session modification request message.

[0088] For example, after receiving a PDU session modification request message (PDU Session ModificationRequest message), the AMF can send a context update request message (Nsmf_PDUSession_UpdateSMContext message) to the SMF based on the data stream binding information carried in the PDU Session Modification Request message.

[0089] Optionally, the PDU Session Modification Request message is transmitted via the Radio Access Network (RAN) and NG interfaces.

[0090] Optionally, both the PDU Session Modification Request message and the Nsmf_PDUSession_UpdateSMContext message can include a session management-related container, the SM Container, which is used to encapsulate data stream binding information.

[0091] In one exemplary embodiment, the target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

[0092] Optionally, the content of the data stream binding information may vary depending on the target QoS stream to be bound. The relevant content of the data stream binding information will be described below in the embodiments of this application.

[0093] Optionally, this application provides three types of data stream binding information, which will be described separately below:

[0094] In one possible implementation, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: 1. Device identifier of the target device; 2. First indication information, which is used to indicate the addition of a device; 3. Second indication information, which is used to instruct the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0095] Optionally, the data flow binding information may include a device identifier, a first indication information, and a second indication information. The specific form of the device identifier, the first indication information, and the second indication information is not limited. The device identifier may be the identifier of one or more target devices added by the gateway device, and the first indication information may be "ADD".

[0096] Optionally, when the data stream binding information includes a device identifier and a first indication information, that is, when the data stream binding information does not include a second indication information, and the device is added according to the indication of the first indication information, and the data stream binding information does not indicate the identifier of the existing data stream to be bound, then the data stream of the target device can be bound to a dedicated QoS stream.

[0097] Optionally, the target device's device ID is a unique identifier used to uniquely identify the device and users and services in the network.

[0098] Optionally, taking the data flow binding information including device identifier, first indication information, and second indication information as an example, the signaling interaction between the gateway device and the core network device can be as follows: Figure 6 As shown, it may include the following steps, wherein:

[0099] Step 1: The gateway device sends a NAS message (PDU session Modification Request message) to the AMF. The PDU session Modification Request message contains an SM Container, which is used to encapsulate data stream binding information, namely device identifier, first indication information and second indication information.

[0100] Step 2: AMF sends a context update request message (Nsmf_PDUSession_UpdateSMContext message) to SMF. The message contains an SM Container, which is used to encapsulate data stream binding information, namely device identifier, first indication information and second indication information.

[0101] Step 3: The SMF sends a policy control update request message (Npcf_SMPolicyControl_Update request message) to the Policy Control Function (PCF). This policy control update request message carries the device identifier of the target device and the policy rule creation instruction information. The policy rule creation instruction information is used to trigger the PCF to establish a dedicated QoS flow in the PDU session.

[0102] Optionally, the creation policy rule instruction information may include parameter requirement information for a dedicated QoS stream.

[0103] Optionally, after receiving the policy control update request message from the SMF, the PCF will dynamically generate policy decisions based on the policy rule creation instruction information, user subscription data, network status, and business requirements, and define specific QoS parameters, such as priority, bandwidth, and latency.

[0104] Step 4: The PCF sends a policy control update message (Npcf_SMPolicyControl_Update message) to the SMF. The Npcf_SMPolicyControl_Update message includes response information to the policy control update request message, which can be a specific policy rule.

[0105] Optionally, the policy rules can be policy decisions generated by PCF, which may include service flow templates, QoS parameters, and binding instructions. The service flow templates are used to define the filtering rules for data packets, and the binding instructions are used to specify that the data flow of the target device should be bound to a specific dedicated QoS flow.

[0106] For example, the PCF can send policy control update messages to the SMF through the N7 interface, and the SMF can receive policy control update messages through the N7 interface.

[0107] Step 5: SMF sends a PDU Session Modification Command / ack message to the gateway device.

[0108] Optionally, the SMF receives policy control update messages and parses their response information for QoS configuration. For example, the SMF can convert policies provided by the PCF into user-plane executable rules and send the rules to the User Plane Function (UPF).

[0109] Optionally, SMF can also trigger the PDU session modification process, sending N1 SM signaling, such as a PDU Session Modification Command / ack message, to the gateway device to update the QoS rules of the gateway device.

[0110] Among them, N1 SM is the session management signaling transmitted through the N1 interface, and the N1 interface is the control plane interface between the gateway device and the AMF.

[0111] In another possible implementation, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; second indication information for instructing the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0112] Optionally, the data flow binding information may include a device identifier, a first indication information, a second indication information, and a data flow identifier. The specific form of the device identifier, the first indication information, the second indication information, and the data flow identifier is not limited. The device identifier may be the identifier of one or more target devices added by the gateway device, and the first indication information may be "ADD".

[0113] Optionally, the data flow binding information may include a device identifier, a first indication information, and a data flow identifier, but excludes the second indication information. The data flow of the target device can be bound to an existing QoS flow based on the data flow identifier in the data flow binding information.

[0114] Optionally, the target device's device ID is a unique identifier used to uniquely identify the device and users and services in the network.

[0115] Optionally, taking the data flow binding information including device identifier, first indication information, and data flow identifier as an example, the signaling interaction between the gateway device and the core network device can be as follows: Figure 7 As shown, it may include the following steps, wherein:

[0116] Step 1: The gateway device sends a NAS message (PDU session Modification Request message) to the AMF. The PDU session Modification Request message contains an SM Container, which is used to encapsulate data stream binding information, namely device identifier, first indication information and data stream identifier.

[0117] Step 2: The AMF sends a context update request message (Nsmf_PDUSession_UpdateSMContext message) to the SMF. The message contains an SM Container, which is used to encapsulate data stream binding information, namely device identifier, first indication information and data stream identifier.

[0118] Step 3: The SMF sends a policy control update request message (Npcf_SMPolicyControl_Update request message) to the Policy Control Function (PCF). This policy control update request message carries the device identifier of the target device and the update policy rule indication information. The update policy rule indication information is used to trigger the PCF to update the target QoS flow.

[0119] Optionally, the update policy rule instruction information may include QoS parameter information when updating an existing QoS flow.

[0120] Optionally, after receiving the policy control update request message from the SMF, the PCF adjusts the target QoS stream and updates the QoS parameters.

[0121] Step 4: The PCF sends a policy control update message (Npcf_SMPolicyControl_Update message) to the SMF. The Npcf_SMPolicyControl_Update message includes response information to the policy control update request message, which can be a specific policy rule.

[0122] Optionally, the policy rules may include adjusted policy decisions and updated QoS parameters.

[0123] For example, the PCF can send policy control update messages to the SMF through the N7 interface, and the SMF can receive policy control update messages through the N7 interface.

[0124] Step 5: SMF sends a PDU Session Modification Command / ack message to the gateway device.

[0125] Optionally, the SMF receives policy control update messages and parses their response information to perform QoS flow binding and modification. For example, the SMF can update the traffic filter of the target QoS flow, adding the packet matching rules of the target device's data flow to the traffic filter of the target QoS flow. The SMF can send updated forwarding rules to the UPF, including modifying the packet detection rules and QoS enforcement rules, to ensure that the target device's data flow is processed according to the target QoS flow, and update the QoS parameters of the PDU session.

[0126] Optionally, SMF can also trigger the PDU session modification process, sending N1 SM signaling, such as a PDU Session Modification Command / ack message, to the gateway device to update the QoS rules of the gateway device.

[0127] In another possible implementation, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes the device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of the multiple QoS flows included in the PDU session.

[0128] Optionally, the device identifier list can be all devices connected to the gateway device, including the device identifiers of connected devices and the device identifiers of the target devices to be added.

[0129] Optionally, when the data stream binding information includes a list of device identifiers, one of the multiple QoS streams corresponding to the data streams of the connected devices in the device identifier list can be selected as the target QoS stream. In this embodiment, the process of selecting one of the multiple QoS streams as the target QoS stream is not limited.

[0130] Optionally, when the data flow binding information includes a data flow identifier, the data flow of the target device can be bound to an existing QoS flow based on the data flow identifier.

[0131] Optionally, when the data stream binding information includes a device identifier list and a data stream identifier, the target QoS stream can be determined based on the device identifier list or the data stream identifier. This application embodiment does not limit this.

[0132] For example, the data stream identifier can be a QoS stream bound to the data stream of any device in the device identifier list.

[0133] Optionally, taking the data flow binding information including a device identifier list and a data flow identifier as an example, the signaling interaction between the gateway device and the core network device can be as follows: Figure 8 As shown, it may include the following steps, wherein:

[0134] Step 1: The gateway device sends a NAS message (PDU session Modification Request message) to the AMF. The PDU session Modification Request message contains an SM Container, which is used to encapsulate data stream binding information, namely the device identifier list and the data stream identifier.

[0135] Step 2: AMF sends a context update request message (Nsmf_PDUSession_UpdateSMContext message) to SMF. The message contains an SM Container, which is used to encapsulate data stream binding information, namely the device identifier list and the data stream identifier.

[0136] Step 3: The SMF sends a policy control update request message (Npcf_SMPolicyControl_Update request message) to the Policy Control Function (PCF). This policy control update request message carries the device identifier of the target device and the update policy rule indication information. The update policy rule indication information is used to trigger the PCF to update the target QoS flow.

[0137] Step 4: The PCF sends a policy control update message (Npcf_SMPolicyControl_Update message) to the SMF. The Npcf_SMPolicyControl_Update message includes response information to the policy control update request message, which can be a specific policy rule.

[0138] Step 5: SMF sends a PDU Session Modification Command / ack message to the gateway device.

[0139] The specific implementation methods in this application embodiment have been described in detail in the above examples, and will not be repeated here.

[0140] The above describes the data stream binding information and signaling interaction process for different target QoS streams, which can bind the data stream of the target device to a dedicated QoS stream or to an existing QoS stream in the PDU session.

[0141] In one exemplary embodiment, such as Figure 9 As shown, a method for adding a device is provided. Taking the application of this method to a core network device as an example, the method includes the following steps 901 to 903. Wherein:

[0142] Step 901: Receive data stream binding information sent by the gateway device. The data stream binding information is sent by the gateway device when adding a target device.

[0143] Step 902: Based on the data stream binding information, bind the data stream of the target device to the target QoS stream of the Protocol Data Unit (PDU) session.

[0144] Step 903: Send a response message for the data flow binding information to the gateway device.

[0145] In an exemplary embodiment, receiving data flow binding information sent by a gateway device includes: receiving a context update request message sent by an Access and Mobility Management Function (AMF), wherein the context update request message carries data flow binding information and is triggered by the gateway device sending a PDU session modification request message to the AMF.

[0146] Optionally, the target QoS stream can be a dedicated QoS stream, or the target QoS stream can be an existing QoS stream in the PDU session.

[0147] In one possible implementation, such as Figure 10As shown, when the target QoS stream is a dedicated QoS stream, binding the data stream of the target device to the target QoS stream of the PDU session includes the following steps 1001 to 1002. Wherein:

[0148] Step 1001: Send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and the policy rule creation instruction information. The policy rule creation instruction information is used to trigger the PCF to establish a dedicated QoS flow in the PDU session.

[0149] Step 1002: Receive the response information sent by PCF in response to the policy control update request message.

[0150] Optionally, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: the device identifier of the target device; first indication information, which is used to indicate the addition of a device; and second indication information, which is used to instruct the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0151] In another possible implementation, such as Figure 11 As shown, when the target QoS flow is an existing QoS flow in the PDU session, the data flow of the target device is bound to the target QoS flow of the PDU session, including steps 1101 to 1102. Wherein:

[0152] Step 1101: Send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and update policy rule indication information. The update policy rule indication information is used to trigger the PCF to update the target QoS flow.

[0153] Step 1102: Receive the response information sent by PCF in response to the policy control update request message.

[0154] The following explains the content of the data stream binding information when the target QoS stream is an existing QoS stream in the PDU session.

[0155] Optionally, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information, which is used to indicate the addition of a device; second indication information, which is used to instruct the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0156] Optionally, if the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes the device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of the multiple QoS flows included in the PDU session.

[0157] The specific implementation method in this embodiment has been described in detail in the above-mentioned method embodiment on the gateway device side, and will not be repeated here.

[0158] It should be understood that, although Figure 3-11 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 3-11 At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0159] In one exemplary embodiment, such as Figure 12 As shown, a device adding apparatus 1200 is provided, including: a transmitting module 1201 and a receiving module 1202, wherein:

[0160] Sending module 1201 is used to send data flow binding information to core network device when the gateway device adds a target device. The data flow binding information is used to instruct the core network device to bind the data flow of the target device to the target QoS flow of the Protocol Data Unit (PDU) session.

[0161] The receiving module 1202 is used to receive the response information sent by the core network device in response to the data flow binding information.

[0162] In one embodiment, the sending module 1201 is specifically used to send a PDU session modification request message to the Access and Mobility Management Function (AMF). The PDU session modification request message carries data stream binding information and is used to trigger the AMF to send a context update request message to the Session Management Function (SMF). The context update request message carries data stream binding information and is used to trigger the SMF to bind the data stream of the target device to the target QoS stream.

[0163] In one embodiment, the target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

[0164] In one embodiment, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; and second indication information for instructing the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0165] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; second indication information for instructing the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0166] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0167] In one embodiment, the target device is a non-3GPP non-3rd Generation Partnership Project (3GPP) device.

[0168] In one embodiment, the gateway device is a 5G-home gateway or a user equipment.

[0169] In one exemplary embodiment, such as Figure 13 As shown, a device adding device 1300 is provided, which is installed in a core network device and includes a receiving module 1301, a binding module 1302 and a sending module 1303.

[0170] The receiving module 1301 is used to receive data stream binding information sent by the gateway device, wherein the data stream binding information is sent by the gateway device when adding a target device.

[0171] The binding module 1302 is used to bind the data stream of the target device to the target QoS stream of the Protocol Data Unit (PDU) session based on the data stream binding information.

[0172] The sending module 1303 is used to send a response to the data stream binding information to the gateway device.

[0173] In one embodiment, the receiving module 1301 is specifically used to receive a context update request message sent by the Access and Mobility Management Function (AMF). The context update request message carries data stream binding information and is triggered by the gateway device sending a PDU session modification request message to the AMF.

[0174] In one embodiment, the target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

[0175] In one embodiment, when the target QoS flow is a dedicated QoS flow, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; and second indication information for instructing the core network device to bind the data flow of the target device to the dedicated QoS flow.

[0176] In one embodiment, the sending module 1303 is further configured to send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and the policy rule creation instruction information. The policy rule creation instruction information is used to trigger the PCF to establish a dedicated QoS stream in the PDU session. The receiving module 1301 is further configured to receive the response information sent by the PCF in response to the policy control update request message.

[0177] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier of the target device; first indication information for indicating the addition of a device; second indication information for instructing the core network device to bind the data flow of the target device to an existing QoS flow in the PDU session; and a data flow identifier, which includes a QoS flow identifier or a packet filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0178] In one embodiment, when the target QoS flow is an existing QoS flow in the PDU session, the data flow binding information includes at least one of the following: a device identifier list, which includes device identifiers of devices connected to the gateway device and the device identifier of the target device; and a data flow identifier, which includes a QoS flow identifier or a group filter, wherein the QoS flow identifier is one of a plurality of QoS flows included in the PDU session.

[0179] In one embodiment, the sending module 1303 is further configured to send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and update policy rule indication information. The update policy rule indication information is used to trigger the PCF to update the target QoS stream. The receiving module 1301 is further configured to receive response information sent by the PCF in response to the policy control update request message.

[0180] Specific limitations regarding the device adding apparatus can be found in the limitations regarding the device adding method described above, and will not be repeated here. Each module in the aforementioned device adding apparatus can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0181] Figure 14 This is a schematic diagram of a gateway device provided in an embodiment of this application. The gateway device may include a processor 1400, a transceiver 1410, and a memory 1420. The transceiver 1410 is used to receive and send data under the control of the processor 1400.

[0182] The transceiver 1410 may be a combination of components, providing a unit for communicating with various other devices over a transmission medium. The processor 1400 is responsible for general processing, and the memory 1420 may store data used by the processor 1400 when performing operations.

[0183] The processor 1400 executes the steps performed by the gateway device in the above method embodiment by calling a program stored in memory, according to the obtained executable instructions.

[0184] Figure 15 This is a schematic diagram of the structure of a core network device provided in an embodiment of this application. The core network device may include a processor 1500, a transceiver 1510, and a memory 1520. The transceiver 1510 is used to receive and transmit data under the control of the processor 1500.

[0185] The transceiver 1510 may be a combination of components, providing a unit for communicating with various other devices over a transmission medium, the processor 1500 is responsible for general processing, and the memory 1520 may store the data used by the processor 1500 when performing operations.

[0186] The processor 1500 executes the steps performed by the core network device in the above method embodiment by calling the program stored in the memory, according to the obtained executable instructions.

[0187] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps described in the above method embodiments.

[0188] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps described in the above method embodiments.

[0189] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0190] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0191] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for adding equipment, characterized in that, For a gateway device, the method includes: When the gateway device adds a target device, it sends data flow binding information to the core network device. The data flow binding information is used to instruct the core network device to bind the data flow of the target device to the target QoS flow of the Protocol Data Unit (PDU) session. Receive the response information sent by the core network device in response to the data flow binding information.

2. The method according to claim 1, characterized in that, Sending data stream binding information to the core network equipment includes: A PDU session modification request message is sent to the Access and Mobility Management Function (AMF). The PDU session modification request message carries the data flow binding information. The PDU session modification request message is used to trigger the AMF to send a context update request message to the Session Management Function (SMF). The context update request message carries the data flow binding information. The data flow binding is used to trigger the SMF to bind the data flow of the target device to the target QoS flow.

3. The method according to claim 1, characterized in that, The target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

4. The method according to claim 3, characterized in that, When the target QoS stream is a dedicated QoS stream, the data stream binding information includes at least one of the following: The device identifier of the target device; First indication information, the first indication information being used to indicate the addition of equipment; The second instruction information is used to instruct the core network device to bind the data stream of the target device to a dedicated QoS stream.

5. The method according to claim 3, characterized in that, When the target QoS stream is an existing QoS stream in the PDU session, the data stream binding information includes at least one of the following: The device identifier of the target device; First indication information, the first indication information being used to indicate the addition of equipment; The second instruction information is used to instruct the core network device to bind the data flow of the target device to the existing QoS flow in the PDU session; A data stream identifier, which includes a QoS stream identifier or a group filter, wherein the QoS stream identifier is one of a plurality of QoS streams included in the PDU session.

6. The method according to claim 3, characterized in that, When the target QoS stream is an existing QoS stream in the PDU session, the data stream binding information includes at least one of the following: The device identifier list includes the device identifiers of devices connected to the gateway device and the device identifier of the target device. A data stream identifier, which includes a QoS stream identifier or a group filter, wherein the QoS stream identifier is one of a plurality of QoS streams included in the PDU session.

7. The method according to any one of claims 1 to 6, characterized in that, The target equipment is non-3GPP equipment and not part of the 3rd Generation Partnership Project.

8. The method according to any one of claims 1 to 6, characterized in that, The gateway device is a 5G-home gateway or user equipment.

9. A method for adding equipment, characterized in that, For use in core network equipment, the method includes; Receive data stream binding information sent by the gateway device, wherein the data stream binding information is sent by the gateway device when adding a target device; Based on the data stream binding information, the data stream of the target device is bound to the target QoS stream of the Protocol Data Unit (PDU) session; Send a response message for the data stream binding information to the gateway device.

10. The method according to claim 9, characterized in that, The data stream binding information sent by the receiving gateway device includes: The gateway device receives a context update request message sent by the Access and Mobility Management Function (AMF). The context update request message carries the data flow binding information. The context update request message is triggered by the gateway device sending a PDU session modification request message to the AMF.

11. The method according to claim 9, characterized in that, The target QoS stream is a dedicated QoS stream, or the target QoS stream is an existing QoS stream in the PDU session.

12. The method according to claim 11, characterized in that, When the target QoS stream is a dedicated QoS stream, the data stream binding information includes at least one of the following: The device identifier of the target device; First indication information, the first indication information being used to indicate the addition of equipment; The second instruction information is used to instruct the core network device to bind the data stream of the target device to a dedicated QoS stream.

13. The method according to claim 12, characterized in that, The step of binding the data stream of the target device to the target QoS stream of the PDU session includes: Send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and the policy rule creation instruction information. The policy rule creation instruction information is used to trigger the PCF to establish a dedicated QoS flow in the PDU session. Receive the response information sent by the PCF in response to the policy control update request message.

14. The method according to claim 11, characterized in that, When the target QoS stream is an existing QoS stream in the PDU session, the data stream binding information includes at least one of the following: The device identifier of the target device; First indication information, the first indication information being used to indicate the addition of equipment; The second instruction information is used to instruct the core network device to bind the data flow of the target device to the existing QoS flow in the PDU session; A data stream identifier, which includes a QoS stream identifier or a group filter, wherein the QoS stream identifier is one of a plurality of QoS streams included in the PDU session.

15. The method according to claim 11, characterized in that, When the target QoS stream is an existing QoS stream in the PDU session, the data stream binding information includes at least one of the following: The device identifier list includes the device identifiers of devices connected to the gateway device and the device identifier of the target device. A data stream identifier, which includes a QoS stream identifier or a group filter, wherein the QoS stream identifier is one of a plurality of QoS streams included in the PDU session.

16. The method according to claim 14 or 15, characterized in that, The step of binding the data stream of the target device to the target QoS stream of the PDU session includes: Send a policy control update request message to the policy control function (PCF). The policy control update request message carries the device identifier of the target device and update policy rule indication information. The update policy rule indication information is used to trigger the PCF to update the target QoS flow. Receive the response information sent by the PCF in response to the policy control update request message.

17. A device for adding equipment, characterized in that, For a gateway device, the apparatus includes: The sending module is used to send data flow binding information to the core network device when the gateway device adds a target device. The data flow binding information is used to instruct the core network device to bind the data flow of the target device to the target QoS flow of the Protocol Data Unit (PDU) session. The receiving module is used to receive response information sent by the core network device in response to the data flow binding information.

18. A device for adding equipment, characterized in that, For core network equipment, the apparatus includes: The receiving module is used to receive data stream binding information sent by the gateway device, wherein the data stream binding information is sent by the gateway device when adding a target device; The binding module is used to bind the data stream of the target device to the target QoS stream of the Protocol Data Unit (PDU) session based on the data stream binding information. The sending module is used to send a response to the data stream binding information to the gateway device.

19. A terminal, characterized in that, Includes memory, transceiver, and processor: Memory, used to store computer programs; A transceiver for sending and receiving data under the control of the processor; the processor for reading a computer program from the memory and executing the method according to any one of claims 1 to 8 by controlling the transceiver.

20. A core network device, characterized in that, Includes memory, transceiver, and processor: Memory, used to store computer programs; A transceiver for transmitting and receiving data under the control of the processor; the processor for reading a computer program from the memory and executing the method according to any one of claims 9 to 16 by controlling the transceiver.

21. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8; or, when the computer program is executed by a processor, it implements the steps of the method according to any one of claims 9 to 16.

22. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8; or, when the computer program is executed by a processor, it implements the steps of the method according to any one of claims 9 to 16.

Images