A connection method, terminal equipment, AMF network element and computer storage medium
By sending the UL NAS transport between the terminal device and the AMF network element, carrying the target network resource identifier and processing the recommended network resources in the DL NAS transport, the major signaling overhead caused by network element congestion in mobile networks is solved, and the terminal is improved The efficiency and speed of the connection between the device and the network.
Patent Information
- Application Number
- CN202210145891.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-02-17
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-02-17
AI Technical Summary
In existing mobile networks, signaling interaction between terminal devices and networks has a large overhead, especially when network elements are congested, resulting in service denial and multiple signaling interactions, which increases network complexity and the implementation burden of terminal devices. .
After the terminal device establishes a connection with the AMF network element, the target network resource identifier is carried by sending the UL NAS transport, and the recommended network resource identifier in the DL NAS transport/PDU Session Establish Reject is received and processed to avoid frequent signaling interactions and reduce signaling overhead .
It effectively reduces the signaling overhead between the network and the terminal device, improves the speed and reliability of PDU session connection, and reduces the complexity of signaling interaction caused by network congestion.
Smart Images

Figure CN114390722B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technology of requesting network slices or data network names (Data Network Name, DNN) by terminals in mobile networks, and in particular to a connection method, terminal equipment, access and mobility management function (Access and Mobility management Function, AMF) network element station and computing storage medium. Background Art
[0002] At present, after the mobile core network evolves to cloud platform and virtual machine technology, the traditional telecommunication network is increasingly evolving towards integration. The addition of the slicing function of the fifth generation mobile communication technology (5G) makes the signaling plane and user plane network elements belong to one or more slices. When providing services to terminal users, the existing network uses the request + allow / reject method. If the service is rejected due to congestion of a certain network element, the network will give the terminal a fallback time and the type of rejection. Congestion includes: general congestion, congestion of a certain slice, congestion of a certain DNN, or congestion of a certain slice and DNN.
[0003] However, with this request + rejection method, only when the user requests it can we know whether the service is rejected due to network element congestion, which causes more signaling interactions between the network and the terminal. It can be seen that the existing network uses the request + allow / reject method, which has a technical problem of high signaling overhead. Summary of the invention
[0004] The embodiments of the present application provide a connection method, a terminal device, an AMF network element, and a computer storage medium, which can reduce the signaling overhead generated by the interaction between the network and the terminal when the network provides services to the terminal.
[0005] The technical solution of this application is implemented as follows:
[0006] The embodiment of the present application provides a connection method, which is applied in a terminal device and includes:
[0007] After establishing a connection with the AMF network element of the core network, sending a first UL NAS transport to the AMF network element; wherein the first UL NAS transport carries an identifier of a first target network resource;
[0008] Receiving a first DL NAStransport / PDU Session Establish Reject returned from the AMF network element for the first target network resource to establish a PDU session connection with the core network;
[0009] The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
[0010] An embodiment of the present application provides a connection method, which is applied to an AMF network element of a core network, including:
[0011] After establishing a connection with the AMF network element, receiving a first UL NAS transport sent from a terminal device; wherein the first UL NAS transport carries a first target network resource;
[0012] When the first target network resource is congested, sending a first DL NAS transport / PDU Session Establish Reject to the terminal device to establish a PDU session connection with the terminal device;
[0013] The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
[0014] The embodiment of the present application provides an optional connection method, which is applied in a terminal device and includes:
[0015] Sending a third Service Request to the AMF network element of the core network; wherein the third Service Request includes: an identifier of a fourth target network resource;
[0016] Receive a second Service Reject returned from the AMF network element for the fourth target network resource; wherein the second Service Reject includes: a rejection reason for the fourth target network resource and a fallback time for the fourth target network resource;
[0017] According to the second Service Reject, a fourth Service Request is sent to the AMF network element to establish a connection with the AMF network element.
[0018] An embodiment of the present application provides an optional connection method, which is applied to an AMF network element of a core network, including:
[0019] A third Service Request is received from the terminal device; wherein the third Service Request includes: an identifier of a fourth target network resource;
[0020] When the fourth target network resource is congested, sending a second Service Reject to the terminal device; wherein the second Service Reject includes: a rejection reason of the fourth target network resource and a fallback time of the fourth target network resource;
[0021] receiving a fourth Service Request sent from the terminal device;
[0022] According to the fourth Service Request, establish a connection with the AMF network element.
[0023] The present application provides a terminal device, including:
[0024] A first sending module is used to send a first UL NAS transport to the AMF network element of the core network after establishing a connection with the AMF network element; wherein the first UL NAS transport carries an identifier of a first target network resource;
[0025] A first receiving module is used to receive a first DL NAS transport / PDU Session Establish Reject returned from the AMF network element for the first target network resource, so as to establish a PDU session connection with the core network;
[0026] The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
[0027] An embodiment of the present application provides an AMF network element of a core network, including:
[0028] A second receiving module is configured to receive a first UL NAS transport sent from a terminal device after establishing a connection with the AMF network element; wherein the first UL NAS transport carries a first target network resource;
[0029] A second sending module, configured to send a first DL NAS transport / PDU Session Establish Reject to the terminal device to establish a PDU session connection with the terminal device when the first target network resource is congested;
[0030] The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
[0031] The present application provides a terminal device, including:
[0032] A third sending module is used to send a third Service Request to the AMF network element of the core network; wherein the third Service Request includes: an identifier of a fourth target network resource;
[0033] A third receiving module is used to receive a second Service Reject returned from the AMF network element for the fourth target network resource; wherein the second Service Reject includes: a rejection reason for the fourth target network resource and a fallback time of the fourth target network resource;
[0034] The first connection module is used to send a fourth Service Request to the AMF network element according to the second Service Reject to establish a connection with the AMF network element.
[0035] An embodiment of the present application provides an AMF network element of a core network, including:
[0036] A fourth receiving module, configured to receive a third Service Request sent from a terminal device; wherein the third Service Request includes: an identifier of a fourth target network resource;
[0037] A fourth sending module, configured to send a second Service Reject to the terminal device when the fourth target network resource is congested; wherein the second Service Reject includes: a rejection reason of the fourth target network resource and a fallback time of the fourth target network resource;
[0038] A fifth receiving module, configured to receive a fourth Service Request sent from the terminal device;
[0039] The second connection module is used to establish a connection with the AMF network element according to the fourth Service Request.
[0040] The present application provides a terminal device, including:
[0041] A processor and a storage medium storing instructions executable by the processor, wherein the storage medium relies on the processor to perform operations through a communication bus, and when the instructions are executed by the processor, the connection method performed by the terminal device in one or more of the above embodiments is executed.
[0042] An embodiment of the present application provides an AMF network element of a core network, including:
[0043] A processor and a storage medium storing instructions executable by the processor, wherein the storage medium relies on the processor to perform operations through a communication bus, and when the instructions are executed by the processor, the connection method performed by the AMF network element described in one or more of the above embodiments is executed.
[0044] An embodiment of the present application provides a computer storage medium storing executable instructions. When the executable instructions are executed by one or more processors, the processors execute the connection method described in one or more embodiments.
[0045] An embodiment of the present application provides a connection method, a terminal device, an AMF network element and a computer storage medium, comprising: after establishing a connection with the AMF network element of the core network, sending a first UL NAS transport to the AMF network element; wherein the first UL NAS transport carries an identifier of a first target network resource, receiving a first DL NAS transport / PDU Session Establish Reject returned from the AMF network element for the first target network resource, wherein the first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that has the same service as the service provided by the first target network resource and is not congested; that is, in an embodiment of the present application, after establishing a connection with the AMF of the core network, the terminal device sends the first UL NAS transport to the AMF network element when establishing a PDU session, and upon receiving the first DL NAS transport / PDU Session Establish Reject returned from the AMF network element Reject carries the first recommended network resource, so that the terminal device can know the available network resources in the core network, so as to prevent the signaling overhead caused by frequent signaling interaction between the terminal device and the core network due to network congestion, reduce the signaling overhead when the network provides services to the terminal device, and help the terminal device and the network to quickly establish a PDU session connection. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] Figure 1 A schematic diagram of the structure of an optional connection system provided in an embodiment of the present application;
[0047] Figure 2 A schematic diagram of an optional connection method provided in an embodiment of the present application;
[0048] Figure 3 A schematic diagram of the process interaction for establishing a PDU session connection between a terminal device and a core network in the related technology;
[0049] Figure 4 A schematic diagram of an example of an optional connection method provided in an embodiment of the present application;
[0050] Figure 5 A schematic diagram of a flow chart of an optional connection method provided in an embodiment of the present application;
[0051] Figure 6 A schematic diagram of a flow chart of another optional connection method provided in an embodiment of the present application;
[0052] Figure 7 A flowchart of another optional connection method provided in an embodiment of the present application;
[0053] Figure 8 A flowchart of another optional connection method provided in an embodiment of the present application;
[0054] Fig. 9 A schematic diagram of the structure of an optional terminal device provided in an embodiment of the present application;
[0055] Fig.10 A schematic diagram of the structure of another optional terminal device provided in an embodiment of the present application;
[0056] Fig.11 A schematic diagram of the structure of an optional AMF network element of a core network provided in an embodiment of the present application;
[0057] Fig.12 A schematic diagram of the structure of another optional AMF network element of the core network provided in an embodiment of the present application;
[0058] Fig.13 A schematic diagram of the structure of another optional terminal device provided in an embodiment of the present application;
[0059] Fig.14 A schematic diagram of the structure of another optional AMF network element of the core network provided in an embodiment of the present application. DETAILED DESCRIPTION
[0060] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.
[0061] The embodiment of the present application provides a connection method, which is applied to a connection system. Figure 1 A schematic diagram of an optional connection system provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the connection system 100 may include: a terminal device 11 and an AMF network element 12 of a core network; wherein,
[0062] The terminal device 11 establishes a connection with the AMF network element 12 of the core network through a service request message (Service Request), and the terminal device 11, the AMF network element 12 of the core network, the 5G session management function (5G Session Management Function, SMF) network element of the core network and the 5G user plane function (5G User Plane Function, UPF) network element of the core network enable the terminal device to establish a PDU session connection with the core network.
[0063] Based on the above Figure 1 The connection system provided, Figure 2 A schematic diagram of an optional connection method provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the connection method may include:
[0064] S201: After the terminal device 11 establishes a connection with the AMF network element 12 of the core network, the terminal device 11 sends a first UL NAS transport to the AMF network element 12;
[0065] In the related technology, since network resources are divided into different slices to provide different types of services to users of terminal devices, when congestion occurs in different network elements, the following are used respectively: general congestion rejection of AMF non-access stratum (NAS) signaling; congestion rejection of a slice requested by the terminal device; congestion rejection of a DNN requested by the terminal device; or congestion rejection of a slice and DNN requested by the terminal device, as well as SMF network element congestion rejection of a slice requested by the terminal device for a PDU session, congestion rejection of a requested DNN, or congestion rejection of a requested slice and DNN.
[0066] Figure 3 A schematic diagram of the process interaction of establishing a PDU session connection between a terminal device and a core network in a connection method in the related art, such as Figure 3 As shown, the process of establishing a PDU session connection between the terminal device and the core network may include:
[0067] S301: User Equipment (UE) sends Service Request() to AMF network element;
[0068] Specifically, when the UE is in an idle state (5GMM idle state) of 5G Mobility Management (5GMM), the UE starts a service request process to establish a non-access stratum (NAS) connection.
[0069] S302: When the AMF network element determines that there is no congestion, it sends Service Accept() to the UE;
[0070] Among them, Service Accept is a service acceptance message.
[0071] S303: When the AMF network element determines congestion, it sends a Service Reject (#22congestion, T3346) to the UE;
[0072] Among them, Service Reject (#22congestion, T3346) is a service rejection message, #22congestion indicates the reason for service rejection, and T3346 indicates the fallback time of service rejection.
[0073] When the AMF network element determines that there is no congestion, the authentication and security procedure re-establishes the existing active PDU session (Authentication and security procedure.re-establish the existed active PDUsession), so Service Accept() is sent to the UE. Assuming that the request / reject process is started during congestion (current request / reject procedure during congestion), then when the AMF network element determines that it is general congestion (general congestion), Service Reject (#22congestion, T3346) is sent to the UE.
[0074] In this way, the UE cannot request other services until the back off timer is expired.
[0075] S304: UE sends UL NAS transport (dnn, s-nssai, Payload container (PDU Session Establish Request)) to the AMF network element;
[0076] Among them, UL NAS transport (dnn, s-nssai, Payload container (PDU Session Establish Request)) represents the uplink non-access layer transmission message, dnn represents the requested data network name, and the single network slice selection assistance message (Single-Network Slice Selection Assistance Information, S-NSSAI).
[0077] When the UE is in the 5GMM connected state, the UE sends a UL NAS transport (dnn, s-nssai, Payload container (PDU Session Establish Request)) to the AMF network element, where dnn and s-nssai are the network resources requested by the UE.
[0078] S305: The AMF network element sends Nsmf_PDUSession_CreateSMContext Request() to the SMF network element;
[0079] S306: The SMF network element sends Nsmf_PDUSession_CreateSMContext Response (fail) to the AMF network element;
[0080] S307: The SMF network element sends a DL NAS transport / PDU Session Establish Reject (#22#67#69, T3396 / T3484 / T3485) to the UE;
[0081] Among them, Nsmf_PDUSession_CreateSMContext Request() is a request message for establishing a PDU session connection to the SMF network element, Nsmf_PDUSession_CreateSMContext Response(fail) is a response message after the SMF network element fails to establish a connection, DL NAS transport / PDU Session Establish Reject(#22#67#69, T3396 / T3484 / T3485) is a rejection message of downlink non-access layer transport / PDU session establishment returned by the AMF network element to the UE. When the SMF network element fails to be selected due to SMF network element congestion (SMF selection fail because of SMF congestion), it means that the network resources requested by the UE are congested. Therefore, the AMF will receive the Nsmf_PDUSession_CreateSMContext Response(fail) sent by the SMF, and the UE will receive the DL NAS transport / PDU Session Establish Reject(#22#67#69, T3396 / T3484 / T3485) sent by the SMF.
[0082] In this way, the UE cannot request PDU until the congestion DNN and / or S-NSSAI timer expires (UE cannot request PDU on congestion DNN and / or S-NSSAI until back off timer is expired.).
[0083] S308: When the AMF network element establishes a connection with the SMF network element, the SMF network element sends an N4Session Establishment Request() to the corresponding UPF network element;
[0084] Among them, the corresponding UPF is selected based on dnn, s-nassi, Qos, and UE policy;
[0085] S309: The corresponding UPF sends N4 Session Establishment Response (fail) to SMF;
[0086] S310: The SMF network element sends Nsmf_Communication_N1N2MessageTransfer() to the AMF network element;
[0087] S311: AMF network element sends DL NAS transport / PDU Session Establish Reject (#22#67#69, T3396 / T3484 / T3485) to the UE;
[0088] When the UPF network element fails to be selected due to UPF network element congestion, it means that the network resources requested by the UE are congested. Therefore, the SMF will receive the N4 Session Establishment Response (fail) sent by the UPF, the SMF will receive the Nsmf_Communication_N1N2MessageTransfer() sent by the AMF, and the UE will receive the DL NAStransport / PDU Session Establish Reject (#22#67#69, T3396 / T3484 / T3485) sent by the AMF.
[0089] In this way, the UE cannot request PDU until the congestion DNN and / or S-NSSAI timer expires (UE cannot request PDU on congestion DNN and / or S-NSSAI until back off timer is expired.).
[0090] It should be noted that for congestion standards, such as reaching the upper limit of the number of users of the terminal device, the AMF network element will reject the signaling request sent by the terminal device and carry the rejection reason #22congestion and a backoff time T3346, which is the NAS signaling general congestion rejection. If it is a signaling process related to the establishment of a PDU session, according to the inter-network signaling interaction between the AMF network element and the SMF network element, due to the congestion of the backend of the AMF network element, the PDU session request cannot be successfully forwarded by the AMF network element. The AMF network element will reject the terminal device based on DNN, network slices, and DNN and network slices with 3 different reasons (#22congestion, #67 "insufficientresources for specific slice and DNN", #69 "insufficient resources for specificslice") and 3 different backoff times (T3396, T3484, T3485).
[0091] Similar to the above process, the SMF network element, based on the situation of the backend UPF network element and the data network (DN), if the signaling plane and / or user plane congestion standards are reached, will reject the terminal based on the PDU session request of the terminal device, based on DNN, network slicing, and DNN and network slicing with 3 different reasons (#22, #67, #69) and 3 different backoff times (T3396, T3484, T3485).
[0092] However, due to the uncertainty of the service requests from a large number of terminal devices, the corresponding network resources change dynamically. With the introduction of cloud technology and virtual machine technology, network resources can be quickly and dynamically deployed to cope with this situation. However, the request + allowance / rejection method that can be used in related technologies: only when the user of the terminal device requests it, can we know whether the service is rejected due to network element congestion. This rejection causes more signaling interactions between the network and the terminal device, resulting in increased implementation complexity of the terminal device and the network. Taking the terminal as an example, if it can support up to 15 session requests, each request rejected by congestion needs to maintain a backoff time related to the network slice and / or DNN. This undoubtedly increases the signaling overhead between the terminal device and the network.
[0093] In order to reduce the signaling overhead between the terminal device and the network, a connection method is provided in an embodiment of the present application. After the terminal device establishes a connection with the AMF network element, the terminal device sends a first UL NAS transport to the AMF network element, wherein the first UL NAS transport carries an identifier of a first target network resource; the first target network resource here can be selected from the network resources provided by the AMF network element according to the service type required by the terminal device, or can be selected from the network resources recommended by the AMF network element. Here, the embodiment of the present application does not make specific limitations on this.
[0094] Among them, the first target network resource includes: DNN and / or network slice, that is, the first target network resource can be DNN, it can also be a network slice, it can also be DNN and network slice. Taking network slice as an example, the first network slice is carried to the first UL NAS transport, so that the AMF network element can establish a PDU session connection based on the first network slice.
[0095] S202: When the first target network resources are congested, the AMF network element 12 sends a first DL NAS transport / PDU Session Establish Reject to the terminal device 11 to establish a PDU session connection with the terminal device 11.
[0096] Taking the first target network resource as the first network slice as an example, after receiving the first network slice, the AMF network element determines whether the first network slice is congested. If the first network slice is not congested, a connection is established between the AMF network element and the terminal device. If the first network slice is congested, the AMF network element sends a first DL NAS transport / PDU Session Establish Reject to the terminal device, so that the AMF network element establishes a PDU session connection with the terminal device.
[0097] Among them, the first DL NAS transport / PDU Session Establish Reject includes: the identifier of the first recommended network resource; the first recommended network resource is: a network resource that has the same service as the service provided by the first target network resource and is not congested; that is, the first recommended network resource carried in the first DL NAS transport / PDU Session Establish Reject can provide a reference for the terminal device to re-establish a connection with the AMF network element, so that the AMF network element and the terminal device establish a PDU session connection.
[0098] It should be noted that the first DL NAS transport / PDU Session Establish Reject may be a message generated according to Nsmf_PDUSession_CreateSMContext Request returned by the SMF network element, or may be a message generated by the SMF network element according to Nsmf_Communication_N1N2MessageTransfer. This embodiment of the present application does not specifically limit this.
[0099] In addition, in order to establish a PDU session connection between the terminal device and the core network, in an optional embodiment, the terminal device establishes a PDU session connection with the core network, including:
[0100] The terminal device sends the second UL NAS transport to the AMF network element;
[0101] When the second target network resources are not congested, the second target network resources are used to establish a PDU session connection with the terminal device.
[0102] Specifically, after receiving the first DL NAS transport / PDU Session Establish Reject, the terminal device sends a second UL NAS transport to the AMF network element in order to establish a PDU session connection, wherein the second target network resources carried in the second UL NAS transport are selected from the first recommended network resources; in this way, since the second target network resources are selected from the first recommended network resources, and the first recommended network resources are non-congested network resources, if the second target network resources are still not congested when the second UL NAS transport is received, the second target network resources are used to establish a PDU session connection with the terminal device.
[0103] Among them, the process of establishing a PDU session connection between the terminal device and the AMF network element includes the interaction between the AMF network element and the SMF network element and the interaction between the SMF network element and the UPF network element, thereby establishing the PDU session connection.
[0104] Before establishing a PDU session, the terminal device and the AMF network element need to establish a connection. In order to establish a connection between the terminal device and the AMF network element, in an optional embodiment, the method may further include:
[0105] The terminal device sends a first Service Request to the AMF network element; wherein the first Service Request includes: an identifier of a third target network resource;
[0106] When the third target network resource is congested, the AMF network element sends a first Service Reject to the terminal device; wherein the first Service Reject includes: the rejection reason of the third target network resource and the fallback time of the third target network resource;
[0107] Based on the first Service Reject, the terminal device sends a second Service Request to the AMF network element to establish a connection with the AMF network element.
[0108] Specifically, the first Service Request sent by the terminal device to the AMF includes: an identifier of the third target network resource, so that the AMF network element can determine whether the third target network resource is congested, and when the third target network resource is congested, the AMF network element sends a first Service Reject to the terminal device, and the first Service Reject carries the rejection reason of the third target network resource and the fallback time of the third target network resource, so that when the terminal device establishes a connection with the AMF network element, the terminal device can know whether the third target network resource requested by itself is congested, and how long it will take to alleviate the congestion, which helps the terminal device to quickly establish a connection with the AMF network element.
[0109] In addition, after receiving the first Service Reject, the terminal device has not established a connection with the AMF network element. Therefore, in order to establish a connection, the terminal device continues to send a second Service Request to the AMF network element so that the terminal device can establish a connection with the AMF network element.
[0110] In order to reduce the signaling overhead between the terminal device and the network, in an optional embodiment, the first ServiceReject further includes: an identifier of the second recommended network resource;
[0111] The second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested.
[0112] That is to say, the second recommended network resources are carried to the first Service Reject, so that the terminal knows which network resources in the core network are not congested and can be used. In this way, the terminal device can refer to the second recommended network resources when sending the second Service Request to reduce the network interaction signaling between the terminal device and the core network, thereby reducing the signaling overhead.
[0113] Finally, in order to realize the connection between the terminal device and the AMF network element, in an optional embodiment, according to the first Service Reject, a second Service Request is sent to the AMF network element to establish a connection with the AMF network element, including:
[0114] The terminal device sends a second Service Request to the AMF network element;
[0115] When the first target network resources carried in the second Service Request are not congested, the AMF network element uses the first target network resources to establish a connection with the terminal device.
[0116] Here, the second Service Request sent by the terminal device to the AMF network element carries the first target network resource, wherein the first target network resource is selected from the second recommended network resource. In this way, the connection established between the terminal device and the AMF network element can be accelerated.
[0117] Since the second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested, it can be seen that the first target network resource selected from the second recommended network resource can not only provide the terminal device with the service required by the terminal device, but also the probability that the first target network resource is not congested is relatively high. In this way, the speed of establishing a connection between the terminal device and the AMF network element can be improved, while reducing the signaling overhead between the terminal device and the network.
[0118] In addition, the embodiment of the present application also provides a connection method, which can realize the establishment of a connection between the terminal device and the AMF network element through the following S203-S206:
[0119] S203: The terminal device sends a third Service Request to the AMF network element of the core network;
[0120] The third Service Request includes: an identifier of a fourth target network resource;
[0121] S204: When the fourth target network resource is congested, the AMF network element sends a second ServiceReject to the terminal device;
[0122] The second Service Reject includes: a rejection reason of the fourth target network resource and a fallback time of the fourth target network resource;
[0123] S205: The terminal device sends a fourth Service Request to the AMF network element based on the second Service Reject to establish a connection with the AMF network element.
[0124] S206: The AMF network element establishes a connection with the AMF network element according to the fourth Service Request.
[0125] In an optional embodiment, the second Service Reject further includes: an identifier of a third recommended network resource;
[0126] The third recommended network resource is: a network resource that provides the same service as the service provided by the fourth target network resource and is not congested.
[0127] In an optional embodiment, S206 may include:
[0128] The terminal device sends a fourth Service Request to the AMF network element to establish a connection with the AMF network element;
[0129] When the fifth target network resource carried in the fourth Service Request is not congested, the AMF network element establishes a connection with the terminal device by using the fifth target network resource;
[0130] The fourth Service Request includes: an identifier of a fifth target network resource; and the fifth target network resource is selected from the third recommended network resources.
[0131] It should be noted that the fourth target network resource is equivalent to the third target network resource, the fifth target network resource is equivalent to the first target network resource, and the third recommended network resource is equivalent to the second recommended network resource.
[0132] Through the above-mentioned connection method, the terminal device and the AMF network element establish a connection using the fifth target network resources, which is similar to the process in which the aforementioned terminal device establishes a connection with the AMF network element using the first target network resources, and will not be repeated here.
[0133] After the terminal device establishes a connection with the AMF network element, the terminal device can use the fifth target network resource to establish a PDU session connection with the core network. The terminal device can also use the following S207-S208 to establish a PDU session connection with the core network:
[0134] S207: After establishing a connection with the AMF network element, the terminal device sends a third UL NAS transport to the AMF network element;
[0135] The third UL NAS transport carries an identifier of a fifth target network resource;
[0136] S208: When the fifth target network resource is congested, the AMF network element sends a second DL NAS transport / PDU Session Establish Reject to the terminal device to establish a PDU session connection with the terminal device;
[0137] The second DL NAS transport / PDU Session Establish Reject includes: an identifier of a fourth recommended network resource; the fourth recommended network resource is: a network resource that provides the same service as that provided by the fifth target network resource and is not congested.
[0138] In an optional embodiment, establishing a PDU session connection with a terminal device includes:
[0139] The terminal device sends the fourth UL NAS transport to the AMF network element to establish a PDU session connection with the core network;
[0140] When the sixth target network resource is not congested, the AMF network element uses the sixth target network resource to establish a PDU session connection with the terminal device;
[0141] The sixth target network resource carried in the fourth UL NAS transport is selected from the fourth recommended network resource.
[0142] Among them, the fourth target network resources include: DNN and / or network slices.
[0143] The above-mentioned third UL NAS transport is equivalent to the above-mentioned first UL NAS transport, the above-mentioned second DL NAS transport / PDU Session Establish Reject is equivalent to the first and second DL NAS transport / PDUSession Establish Reject, the above-mentioned fourth recommended network resources are equivalent to the above-mentioned first recommended network resources, the above-mentioned fourth UL NAS transport is equivalent to the above-mentioned second UL NAS transport, and the above-mentioned sixth target network resources are equivalent to the above-mentioned second target network resources.
[0144] The above-mentioned terminal device uses the sixth target network resources to establish a PDU session connection with the core network, which is similar to the process in which the aforementioned terminal device uses the second target network resources to establish a PDU session connection with the core network, and will not be repeated here.
[0145] That is to say, the connection method provided in the embodiment of the present application can add the identifier of the target network resource to be queried in the Service Request when the terminal device establishes a connection with the AMF network element, and by adding the identifier of the recommended network resource in the Service Reject, the terminal device and the AMF network element can quickly establish a connection while reducing the signaling overhead, and provide available network resources for establishing a PDU session connection between the terminal device and the core network.
[0146] In addition, when the available network resources provided are congested, further adding an identifier of the recommended network resources in the DL NAS transport / PDUSession Establish Reject can further speed up the process of establishing the PDU session.
[0147] The following is an example to describe the connection method in one or more of the above embodiments.
[0148] Figure 4 A schematic diagram of an example of an optional connection method provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the process of establishing a PDU session connection between the terminal device and the core network may include:
[0149] S401: UE sends a Service Request (Query DNN, Query S-NSSAI) to the AMF network element;
[0150] Specifically, when the UE is in the idle state of 5GMM, the UE starts the service request process to establish a NAS connection. Specifically, the Query DNN and Query S-NSSAI in the Service Request (Query DNN, Query S-NSSAI) sent by the UE to the AMF network element are the DNN to be queried and the S-NSSAI to be queried, respectively.
[0151] S402: When the AMF network element determines that there is no congestion, it sends Service Accept() to the UE;
[0152] Among them, when the AMF network element determines that there is no congestion, the authentication and security procedure re-establishes the existing active PDU session (Authentication and security procedure.re-establish the existed active PDUsession), so it sends Service Accept() to the UE.
[0153] S403: When the AMF network element determines congestion, it sends a Service Reject (#22#67#69, T3346 / T3396 / T3486, suggested NSSAI) to the UE;
[0154] Assuming that the current request / reject procedure during congestion is started, then when the AMF network element determines that it is general congestion, SMF selection fails because of SMF congestion.
[0155] In this way, the UE initiates a new service request based on the suggested slice list (UE trigger new service request procedure based on suggested NSSAI). Since the DNN and slice information to be queried are added in the Service Request, this is the first congestion check point. The AMF can advance the congestion check process of the SMF. If it is found that the SMF is congested, the subsequent PDU establishment process of the UE will not be initiated to the congested DNN and slice information (Because the SMF congestion check is running on service request procedure. If it's congestion. UE and network will not handle PDU establishment procedure on congestion DNN and / or S-NSSAI), eliminating redundant signaling interaction. If the suggested slice list is carried in the Service Reject, the UE can initiate the NAS signaling process to these non-congested network resources, as well as the subsequent PDU establishment process, to bring better customer experience.
[0156] S404: UE sends UL NAS transport (dnn, s-nssai, Payload container (PDU Session Establish Request)) to the AMF network element;
[0157] When the UE is in the 5GMM connected state, the UE sends a UL NAS transport (dnn, s-nssai, Payload container (PDU Session Establish Request)) to the AMF network element, where dnn and s-nssai are the dnn and s-nssai when the UE establishes a connection with the AMF respectively.
[0158] S405: The AMF network element sends Nsmf_PDUSession_CreateSMContext Request() to the SMF network element;
[0159] S406: The SMF network element sends Nsmf_PDUSession_CreateSMContext Response (fail) to the AMF network element;
[0160] S407: The SMF network element sends a DL NAS transport / PDU Session Establish Reject (#22#67#69, T3396 / T3484 / T3485, suggested NSSAI) to the UE;
[0161] That is to say, when the SMF network element fails to be selected due to SMF network element congestion (SMF selection failbecause of SMF congestion), it means that the network resources requested by the UE are congested. Therefore, the AMF will receive the Nsmf_PDUSession_CreateSMContext Response(fail) sent by the SMF, and the UE will receive the DL NAStransport / PDU Session Establish Reject(#22#67#69, T3396 / T3484 / T3485, suggestedNSSAI) sent by the SMF.
[0162] In this way, the UE initiates a new service request based on the suggested slice list (UE trigger new service request procedure based on suggested NSSAI). When the established slice list is not congested, the PDU session will be successfully established without waiting for the timer to expire (The suggested NSSAI is not congestion, the PDU session will be created successfully, no need block service until back off timer is expired). This is the second congestion checkpoint. Since the established slice list is carried in the PDU establishment rejection message, the UE can request a PDU session from these non-congested network resources instead of waiting for the fallback message and trying to request to establish the same PDU session again on the original congested network resources. This brings a better user experience to customers.
[0163] S408: When the AMF network element establishes a connection with the SMF network element, the SMF network element sends an N4Session Establishment Request() to the corresponding UPF network element;
[0164] Among them, the corresponding UPF is selected based on dnn, s-nassi, Qos, and UE policy.
[0165] S409: The corresponding UPF sends N4 Session Establishment Response (fail) to SMF;
[0166] S410: The SMF network element sends Nsmf_Communication_N1N2MessageTransfer() to the AMF network element;
[0167] S411: AMF network element sends DL NAS transport / PDU Session Establish Reject (#22#67#69, T3396 / T3484 / T3485, suggested NSSAI) to the UE;
[0168] Among them, when the UPF network element fails to be selected due to UPF network element congestion, it means that the network resources requested by the UE are congested. Therefore, the SMF will receive the N4 Session Establishment Response (fail) sent by the UPF, the SMF will receive the Nsmf_Communication_N1N2MessageTransfer() sent by the AMF, and the UE will receive the DL NAStransport / PDU Session Establish Reject (#22#67#69, T3396 / T3484 / T3485, suggestedNSSAI) sent by the AMF.
[0169] In this way, the UE initiates a new service request based on the suggested slice list (UE trigger new service request procedure based on suggested NSSAI). When the established slice list is not congested, the PDU session will be successfully established without waiting for the timer to expire (The suggested NSSAI is not congestion, the PDU session will be created successfully, no need block service until back off timer is expired). This is used as the third congestion checkpoint and is handled in the same way as the second congestion checkpoint. The established slice list is carried in the PDU session reject message, allowing the UE to have one more selection process instead of waiting for the backoff timeout, thereby bringing a better user experience.
[0170] That is to say, in the 5GMM idle state, during the NAS signaling establishment process triggered by the Service Request process, the Query mechanism is added to the Service Request message sent by the terminal, because if it is a Service Request message triggered by the session management layer (SessionManagement), the NAS signaling is established and then sent immediately after the UL NAStransport message contains (session layer PDU session establish request message). Add the two optional information elements Query S-NSSAI and Query DNN to establish the PDU session in the Service Request message, and the AMF / SMF / Network Slice Admission Control (NSAC) can query the S-NSSAI and DNN to reply to the congestion situation. In this way, congestion can be pre-processed in advance between the Service Request establishing NAS signaling and sending the PDU session establishment request. If there is congestion, the PDU session establishment request / reject signaling process completed by the UE through the UL / DL NAS transport message can be omitted, and the UE can start different back-off timers for different DNN and / or slice combinations. These operations can also be avoided to a certain extent, thereby reducing the complexity of UE implementation. Based on the query results, the UE relatively intelligently reselects the slice / DNN to integrate the network and the terminal into a system to coordinate the slice / DNN resources. Furthermore, if the network side determines that there is congestion in the queried slice, it can carry the slice information of the allowed slice list (allow NSSAI) with similar services but not congested. The UE selects a slice that meets the needs in this suggested slice list (suggestedNSSAI) and then establishes the PDU SESSION.
[0171] In the 5GMM connected state, similar to the idle process, when sending a request, if the requested slice is rejected by the network side, the rejection message can carry information about slices with similar services but not congested in the allowed slice list (allow NSSAI). The UE selects a slice that meets the needs from the suggested slice list (suggested NSSAI) and then establishes the PDU Session.
[0172] The messages that need to be modified are: Service Request, Service Reject and PDU Session Establishment Reject. Table 1 shows the modified Service Request, Table 2 shows the modified Service Reject, and Table 3 shows the modified PDU Session Establishment Reject.
[0173] Table 1
[0174]
[0175] Table 2
[0176]
[0177] Table 3
[0178]
[0179] It can be seen that in this example, by using the query + service request method, the network and the terminal are treated as a system, rather than the network alone solving the congestion problem caused by the imbalance of resources of each network element. This can effectively reduce the invalid signaling interaction process caused by congestion and reduce the network signaling plane load; in addition, due to the introduction of queries, the terminal will not request congested network services, and the network and terminal will never avoid the backoff time of maintaining each DNN and / or slice, reducing the complexity of implementation; congestion and the inability to request the same service within the backoff time lead to a poor user experience. After adding the query mechanism, this poor user experience will be reduced.
[0180] Introduce the method of querying before requesting, and shorten the time interval between query and request as much as possible to solve the problem of network congestion. The specific implementation is that in the 5GMM idle state, only the service request message triggered by the session layer will add the two information elements of Query S-NSSAI and Query DNN to assist AMF / SMF to determine in advance whether the entire slice / DNN channel resources are available. If there is no congestion, the session establishment process will be carried out with a high success rate. If there is congestion, the network element can reject the request in advance and carry the suggested slice / DNN information, saving the signaling process and improving the user experience. In the 5GMM connection state, the PDU establishment rejection message carries the suggested slice / DNN information to help the terminal select other slices and / or DNN resources for service.
[0181] In addition to pre-querying slices and DNN, it can be used not only to query congestion, but also to query more network parameters, such as slices that meet the Vehicle-to-Everything (V2X) requirements, the number of online users, and different indicators of latency. On the basis of satisfying the requested service, based on these values, the terminal can select better and more idle network resources to request services. This can be understood as the terminal intelligently assisting the network in balancing resources, achieving the system intelligence of the terminal plus the network.
[0182] An embodiment of the present application provides a connection method, comprising: after establishing a connection with an AMF network element of a core network, sending a first UL NAS transport to the AMF network element; wherein the first UL NAS transport carries an identifier of a first target network resource, receiving a first DL NAS transport / PDU Session Establish Reject returned from the AMF network element for the first target network resource, wherein the first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that has the same service as the service provided by the first target network resource and is not congested; that is, in an embodiment of the present application, after establishing a connection with the AMF of the core network, the terminal device sends the first UL NAS transport to the AMF network element to establish a PDU session, and upon receiving the first DL NAS transport / PDU Session Establish Reject returned from the AMF network element, Reject carries the first recommended network resource, so that the terminal device can know the available network resources in the core network, so as to prevent the signaling overhead caused by frequent signaling interaction between the terminal device and the core network due to network congestion, reduce the signaling overhead when the network provides services to the terminal device, and help the terminal device and the network to quickly establish a PDU session connection.
[0183] The above connection method is described below by connecting each device deployed in the system.
[0184] First, the connection method is described from the terminal device side.
[0185] The present application embodiment provides a connection method, which is applied to a terminal device. Figure 5 A schematic diagram of an optional connection method provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the connection method may include:
[0186] S501: After establishing a connection with the AMF network element of the core network, sending a first UL NAS transport to the AMF network element;
[0187] S502: Receive a first DL NAS transport / PDU Session Establish Reject returned from the AMF network element for the first target network resource, so as to establish a PDU session connection with the core network;
[0188] The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested; and the first UL NAS transport carries the identifier of the first target network resource.
[0189] In an optional embodiment, establishing a PDU session connection with a core network includes:
[0190] Send a second UL NAS transport to the AMF network element to establish a PDU session connection with the core network; wherein the second target network resources carried in the second UL NAS transport are selected from the first recommended network resources.
[0191] In an optional embodiment, the above method may further include:
[0192] Sending a first Service Request to the AMF network element; wherein the first Service Request includes: an identifier of a third target network resource;
[0193] Receive a first Service Reject returned from the AMF network element for the third target network resource; wherein the first Service Reject includes: a rejection reason for the third target network resource and a fallback time of the third target network resource;
[0194] Based on the first Service Reject, a second Service Request is sent to the AMF network element to establish a connection with the AMF network element.
[0195] In an optional embodiment, the first target network resources include: DNN and / or network slices.
[0196] In an optional embodiment, the first Service Reject further includes: an identifier of the second recommended network resource;
[0197] The second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested.
[0198] In an optional embodiment, according to the first Service Reject, sending a second Service Request to the AMF network element to establish a connection with the AMF network element includes:
[0199] Send a second Service Request to the AMF network element to establish a connection with the AMF network element;
[0200] The second Service Request includes: an identifier of a first target network resource; and the first target network resource is selected from the second recommended network resources.
[0201] The present application embodiment provides a connection method, which is applied to a terminal device. Figure 6 A flow chart of another optional connection method provided in the embodiment of the present application is as follows: Figure 6 As shown, the connection method may include:
[0202] S601: Send a third Service Request to the AMF network element of the core network;
[0203] The third Service Request includes: an identifier of a fourth target network resource;
[0204] S602: Receive a second Service Reject returned from the AMF network element for the fourth target network resource;
[0205] The second Service Reject includes: a rejection reason of the fourth target network resource and a fallback time of the fourth target network resource;
[0206] S603: Based on the second Service Reject, send a fourth Service Request to the AMF network element to establish a connection with the AMF network element.
[0207] In an optional embodiment, the second Service Reject further includes: an identifier of a third recommended network resource;
[0208] The third recommended network resource is: a network resource that provides the same service as the service provided by the fourth target network resource and is not congested.
[0209] In an optional embodiment, S603 may include:
[0210] Send a fourth Service Request to the AMF network element to establish a connection with the AMF network element;
[0211] The fourth Service Request includes: an identifier of a fifth target network resource; and the fifth target network resource is selected from the third recommended network resources.
[0212] In an optional embodiment, the above method further includes:
[0213] After establishing a connection with the AMF network element, sending a third UL NAS transport to the AMF network element; wherein the third UL NAS transport carries an identifier of the fifth target network resource;
[0214] receiving a second DL NAS transport / PDUSession Establish Reject returned from the AMF network element for the fifth target network resource to establish a PDU session connection with the core network;
[0215] The second DL NAS transport / PDU Session Establish Reject includes: an identifier of a fourth recommended network resource; the fourth recommended network resource is: a network resource that provides the same service as that provided by the fifth target network resource and is not congested.
[0216] In an optional embodiment, establishing a PDU session connection with the core network includes:
[0217] Send a fourth UL NAS transport to the AMF network element to establish a PDU session connection with the core network; wherein the sixth target network resource carried in the fourth UL NAS transport is selected from the fourth recommended network resource.
[0218] In an optional embodiment, the fourth target network resource includes: DNN and / or network slice.
[0219] Secondly, the above connection method is described based on the AMF network element side of the core network.
[0220] The embodiment of the present application provides a connection method, which is applied to the AMF network element of the core network. Figure 7 A flow chart of another optional connection method provided in the embodiment of the present application is as follows: Figure 7 As shown, the connection method may include:
[0221] S701: After establishing a connection with the AMF network element, receiving a first UL NAS transport sent by a terminal device;
[0222] S702: When the first target network resource is congested, sending a first DL NAS transport / PDUSession Establish Reject to the terminal device to establish a PDU session connection with the terminal device;
[0223] The first UL NAS transport carries the first target network resource; the first DL NAS transport / PDU Session Establish Reject includes: an identifier of the first recommended network resource; the first recommended network resource is: a network resource that has the same service as the service provided by the first target network resource and is not congested.
[0224] In an optional embodiment, establishing a PDU session connection with a terminal device includes:
[0225] receiving a second UL NAS transport sent from the terminal device; wherein the second target network resource carried in the second UL NAS transport is selected from the first recommended network resource;
[0226] When the second target network resources are not congested, the second target network resources are used to establish a PDU session connection with the terminal device.
[0227] In an optional embodiment, the first target network resources include: DNN and / or network slices.
[0228] In an optional embodiment, the above method may further include:
[0229] A first Service Request sent from a terminal device is received; wherein the first Service Request includes: an identifier of a third target network resource;
[0230] When the third target network resource is congested, a first Service Reject is sent to the terminal device; wherein the first Service Reject includes: a rejection reason of the third target network resource and a fallback time of the third target network resource;
[0231] Receiving a second Service Request sent from the terminal device;
[0232] Based on the second Service Request, establish a connection with the AMF network element.
[0233] In an optional embodiment, the first Service Reject further includes: an identifier of the second recommended network resource;
[0234] The second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested.
[0235] In an optional embodiment, establishing a connection with the AMF network element according to the second Service Request includes:
[0236] When the first target network resource carried in the second Service Request is not congested, establishing a connection with the terminal device by using the first target network resource;
[0237] The first target network resource is selected from the second recommended network resources.
[0238] The present application embodiment provides a connection method, which is applied to a terminal device. Figure 8 A flow chart of another optional connection method provided in the embodiment of the present application is as follows: Figure 8 As shown, the connection method may include:
[0239] S801: receiving a third Service Request sent from a terminal device;
[0240] The third Service Request includes: an identifier of a fourth target network resource;
[0241] S802: When the fourth target network resource is congested, sending a second Service Reject to the terminal device;
[0242] The second Service Reject includes: a rejection reason of the fourth target network resource and a fallback time of the fourth target network resource;
[0243] S803: receiving a fourth Service Request sent from the terminal device;
[0244] S804: Establish a connection with the AMF network element according to the fourth Service Request.
[0245] In an optional embodiment, the second Service Reject further includes: an identifier of a third recommended network resource;
[0246] The third recommended network resource is: a network resource that provides the same service as the service provided by the fourth target network resource and is not congested.
[0247] In an optional embodiment, S804 may include:
[0248] When the fifth target network resource carried in the fourth Service Request is not congested, establishing a connection with the terminal device by using the fifth target network resource;
[0249] The fifth target network resource is selected from the third recommended network resource.
[0250] In an optional embodiment, the above method further includes:
[0251] After establishing a connection with the AMF network element, receiving a third UL NAS transport sent from the terminal device; wherein the third UL NAS transport carries a fifth target network resource;
[0252] When the fifth target network resource is congested, sending a second DL NAS transport / PDUSession Establish Reject to the terminal device to establish a PDU session connection with the terminal device;
[0253] The second DL NAS transport / PDU Session Establish Reject includes: an identifier of a fourth recommended network resource; the fourth recommended network resource is: a network resource that provides the same service as that provided by the fifth target network resource and is not congested.
[0254] In an optional embodiment, establishing a PDU session connection with a terminal device includes:
[0255] receiving a fourth UL NAS transport sent from the terminal device; wherein the sixth target network resource carried in the fourth UL NAS transport is selected from the fourth recommended network resource;
[0256] When the sixth target network resources are not congested, the sixth target network resources are used to establish a PDU session connection with the terminal device.
[0257] In an optional embodiment, the fourth target network resources include: DNN and / or network slices.
[0258] In addition, based on the same inventive concept as the aforementioned embodiments, an embodiment of the present application provides a terminal device that is consistent with the terminal device provided by one or more of the aforementioned embodiments.
[0259] Fig. 9 A schematic diagram of the structure of an optional terminal device provided in an embodiment of the present application, such as Fig. 9As shown, the terminal device includes:
[0260] A first sending module 91 is used to send a first UL NAS transport to the AMF network element after establishing a connection with the AMF network element of the core network; wherein the first UL NAS transport carries an identifier of a first target network resource;
[0261] A first receiving module 92 is used to receive a first DLNAS transport / PDU Session Establish Reject returned from the AMF network element for the first target network resource to establish a PDU session connection with the core network;
[0262] The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
[0263] In an optional embodiment, the first receiving module 92 establishes a PDU session connection with the core network, including:
[0264] Send a second UL NAS transport to the AMF network element to establish a PDU session connection with the core network; wherein the second target network resources carried in the second UL NAS transport are selected from the first recommended network resources.
[0265] In an optional embodiment, the first target network resources include: DNN and / or network slices.
[0266] In an optional embodiment, the terminal device is further used for:
[0267] Sending a first Service Request to the AMF network element; wherein the first Service Request includes: an identifier of a third target network resource;
[0268] Receive a first Service Reject returned from the AMF network element for the third target network resource; wherein the first Service Reject includes: a rejection reason for the third target network resource and a fallback time of the third target network resource;
[0269] Based on the first Service Reject, a second Service Request is sent to the AMF network element to establish a connection with the AMF network element.
[0270] In an optional embodiment, the first Service Reject further includes: an identifier of the second recommended network resource;
[0271] The second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested.
[0272] In an optional embodiment, the terminal device sends a second Service Request to the AMF network element according to the Service Reject to establish a connection with the AMF network element, including:
[0273] Send a second Service Request to the AMF network element to establish a connection with the AMF network element;
[0274] The second Service Request includes: a first target network resource; the first target network resource is selected from the second recommended network resources.
[0275] In practical applications, the first sending module 91 and the first receiving module 92 may be implemented by a processor located on the terminal device, specifically a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA).
[0276] Fig.10 A schematic diagram of the structure of another optional terminal device provided in an embodiment of the present application, such as Fig.10 As shown, the terminal device includes:
[0277] The third sending module 101 is used to send a third Service Request to the AMF network element of the core network;
[0278] The third Service Request includes: an identifier of a fourth target network resource;
[0279] The third receiving module 102 is used to receive a second Service Reject returned from the AMF network element for the fourth target network resource;
[0280] The second Service Reject includes: a rejection reason of the fourth target network resource and a fallback time of the fourth target network resource;
[0281] The first connection module 103 is used to send a fourth ServiceRequest to the AMF network element according to the second Service Reject to establish a connection with the AMF network element.
[0282] In an optional embodiment, the second Service Reject further includes: an identifier of a third recommended network resource;
[0283] The third recommended network resource is: a network resource that provides the same service as the service provided by the fourth target network resource and is not congested.
[0284] In an optional embodiment, the first connection module 103 is specifically configured to:
[0285] Send a fourth Service Request to the AMF network element to establish a connection with the AMF network element;
[0286] The fourth Service Request includes: an identifier of a fifth target network resource; and the fifth target network resource is selected from the third recommended network resources.
[0287] In an optional embodiment, the terminal device is further used for:
[0288] After establishing a connection with the AMF network element, a third UL NAS transport is sent to the AMF network element;
[0289] The third UL NAS transport carries an identifier of a fifth target network resource;
[0290] receiving a second DL NAS transport / PDUSession Establish Reject returned from the AMF network element for the fifth target network resource to establish a PDU session connection with the core network;
[0291] The second DL NAS transport / PDU Session Establish Reject includes: an identifier of a fourth recommended network resource; the fourth recommended network resource is: a network resource that provides the same service as that provided by the fifth target network resource and is not congested.
[0292] In an optional embodiment, the terminal device establishes a PDU session connection with the core network, including:
[0293] Send the fourth UL NAS transport to the AMF network element to establish a PDU session connection with the core network;
[0294] The sixth target network resource carried in the fourth UL NAS transport is selected from the fourth recommended network resource.
[0295] In an optional embodiment, the fourth target network resource includes: DNN and / or network slice.
[0296] In practical applications, the third sending module 101, the third receiving module 102 and the first connecting module 103 may be implemented by a processor located on the terminal device, specifically a CPU, an MPU, a DSP or an FPGA.
[0297] An embodiment of the present application provides an AMF network element of a core network, which is consistent with the AMF network element of the core network described in one or more of the above embodiments.
[0298] Fig.11 A schematic diagram of the structure of an optional AMF network element of a core network provided in an embodiment of the present application, such as Fig.11 As shown, the AMF network elements of the core network include:
[0299] The second receiving module 111 is used to receive a first UL NAS transport sent from the terminal device after establishing a connection with the AMF network element; wherein the first UL NAS transport carries a first target network resource;
[0300] The second sending module 112 is used to send a first DL NAS transport / PDU Session Establish Reject to the terminal device to establish a PDU session connection with the terminal device when the first target network resource is congested;
[0301] The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
[0302] In an optional embodiment, the second sending module 112 establishes a PDU session connection with the terminal device, including:
[0303] receiving a second UL NAS transport sent from the terminal device; wherein the second target network resource carried in the second UL NAS transport is selected from the first recommended network resource;
[0304] When the second target network resources are not congested, the second target network resources are used to establish a PDU session connection with the terminal device.
[0305] In an optional embodiment, the first target network resources include: DNN and / or network slices.
[0306] In an optional embodiment, the AMF network element is further used for:
[0307] A first Service Request sent from a terminal device is received; wherein the first Service Request includes: an identifier of a third target network resource;
[0308] When the third target network resource is congested, a first Service Reject is sent to the terminal device; wherein the first Service Reject includes: a rejection reason of the third target network resource and a fallback time of the third target network resource;
[0309] Receiving a second Service Request sent from the terminal device;
[0310] Based on the second Service Request, establish a connection with the AMF network element.
[0311] In an optional embodiment, Service Reject further includes: an identifier of a second recommended network resource;
[0312] The second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested.
[0313] In an optional embodiment, the AMF network element establishes a connection with the AMF network element according to the second Service Request, including:
[0314] When the first target network resource carried in the second Service Request is not congested, establishing a connection with the terminal device by using the first target network resource;
[0315] The first target network resource is selected from the second recommended network resources.
[0316] In actual applications, the above-mentioned second receiving module 81 and the second sending module 82 can be implemented by a processor on the AMF network element located in the core network, specifically a CPU, MPU, DSP or FPGA.
[0317] Fig.12 A schematic diagram of the structure of another optional AMF network element of the core network provided in an embodiment of the present application, such as Fig.12 As shown, the AMF network elements of the core network include:
[0318] The fourth receiving module 121 is used to receive a third Service Request sent from the terminal device;
[0319] The third Service Request includes: an identifier of a fourth target network resource;
[0320] A fourth sending module 122, configured to send a second Service Reject to the terminal device when the fourth target network resource is congested;
[0321] The second Service Reject includes: a rejection reason of the fourth target network resource and a fallback time of the fourth target network resource;
[0322] The fifth receiving module 123 is used to receive a fourth Service Request sent from the terminal device;
[0323] The second connection module 124 is used to establish a connection with the AMF network element according to the fourth Service Request.
[0324] In an optional embodiment, the second Service Reject further includes: an identifier of a third recommended network resource;
[0325] The third recommended network resource is: a network resource that provides the same service as the service provided by the fourth target network resource and is not congested.
[0326] In an optional embodiment, the second connection module 124 is specifically configured to:
[0327] When the fifth target network resource carried in the fourth Service Request is not congested, establishing a connection with the terminal device by using the fifth target network resource;
[0328] The fifth target network resource is selected from the third recommended network resource.
[0329] In an optional embodiment, the AMF network element is further used for:
[0330] After establishing a connection with the AMF network element, receiving a third UL NAS transport sent from the terminal device; wherein the third UL NAS transport carries a fifth target network resource;
[0331] When the fifth target network resource is congested, sending a second DL NAS transport / PDUSession Establish Reject to the terminal device to establish a PDU session connection with the terminal device;
[0332] The second DL NAS transport / PDU Session Establish Reject includes: an identifier of a fourth recommended network resource; the fourth recommended network resource is: a network resource that provides the same service as that provided by the fifth target network resource and is not congested.
[0333] In an optional embodiment, the AMF network element establishes a PDU session connection with the terminal device, including:
[0334] receiving a fourth UL NAS transport sent from the terminal device; wherein the sixth target network resource carried in the fourth UL NAS transport is selected from the fourth recommended network resource;
[0335] When the sixth target network resources are not congested, the sixth target network resources are used to establish a PDU session connection with the terminal device.
[0336] In an optional embodiment, the fourth target network resources include: DNN and / or network slices.
[0337] In actual applications, the fourth receiving module 121, the fourth sending module 122, the fifth receiving module 123 and the second connection module 124 can be implemented by a processor located on the AMF network element of the core network, specifically a CPU, MPU, DSP or FPGA.
[0338] Fig.13 A schematic diagram of the structure of another optional terminal device provided in the embodiment of the present application, such as Fig.13 As shown, the embodiment of the present application provides a terminal device 1300, including:
[0339] A processor 131 and a storage medium 132 storing executable instructions of the processor 131, wherein the storage medium 132 relies on the processor 131 to perform operations through a communication bus 133, and when the instructions are executed by the processor 131, the connection method performed by the above-mentioned terminal device in one or more of the above-mentioned embodiments is executed.
[0340] It should be noted that in actual application, the various components in the terminal are coupled together through the communication bus 133. It is understandable that the communication bus 133 is used to realize the connection and communication between these components. In addition to the data bus, the communication bus 133 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Fig.13 Various buses are labeled as communication buses 133.
[0341] Fig.14A schematic diagram of the structure of an AMF network element of another optional core network provided in an embodiment of the present application, such as Fig.14 As shown, the embodiment of the present application provides an AMF network element 1400 of a core network, including:
[0342] A processor 141 and a storage medium 142 storing executable instructions of the processor 141, wherein the storage medium 142 relies on the processor 141 to perform operations through a communication bus 143. When the instructions are executed by the processor 141, the connection method performed by the AMF network element of the above-mentioned core network in one or more of the above-mentioned embodiments is executed.
[0343] It should be noted that in actual application, the various components in the terminal are coupled together through the communication bus 143. It is understandable that the communication bus 143 is used to realize the connection and communication between these components. In addition to the data bus, the communication bus 143 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Fig.14 Various buses are labeled as communication buses 143.
[0344] An embodiment of the present application provides a computer storage medium storing executable instructions. When the executable instructions are executed by one or more processors, the processor executes the connection method as executed by the terminal device in one or more of the above embodiments, or the connection method as executed by the AMF network element of the core network in one or more of the above embodiments.
[0345] Among them, the computer-readable storage medium can be a ferromagnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM) and other memories.
[0346] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of hardware embodiments, software embodiments, or embodiments in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
[0347] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0348] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0349] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0350] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application.
Claims
1. A connection method, characterized in that: The method is applied in a terminal device, comprising: Sending a first Service Request to the AMF network element; wherein the first Service Request includes: an identifier of a third target network resource; the first Service Request includes: Query S-NSSAI and Query DNN; Receive a first Service Reject returned from the AMF network element for the third target network resource; wherein the first Service Reject includes: a rejection reason for the third target network resource and a fallback time for the third target network resource; Sending a second Service Request to the AMF network element according to the first Service Reject to establish a connection with the AMF network element; After establishing a connection with the AMF network element of the core network, sending a first UL NAS transport to the AMF network element; wherein the first UL NAS transport carries an identifier of a first target network resource, so that the AMF network element establishes a PDU session connection based on the first target network resource; Receiving a first DL NAS transport / PDUSession Establish Reject returned from the AMF network element for the first target network resource to establish a PDU session connection with the core network; The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
2. The method according to claim 1, characterized in that The establishing a PDU session connection with the core network includes: Send a second UL NAS transport to the AMF network element to establish a PDU session connection with the core network; wherein the second target network resources carried in the second UL NAS transport are selected from the first recommended network resources.
3. The method according to claim 1, characterized in that The first target network resources include: DNN and / or network slices.
4. The method according to claim 1, characterized in that The first Service Reject also includes: an identifier of a second recommended network resource; The second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested.
5. The method according to claim 4, characterized in that The sending a second Service Request to the AMF network element according to the first Service Reject to establish a connection with the AMF network element includes: Sending a second Service Request to the AMF network element to establish a connection with the AMF network element; The second Service Request includes: an identifier of a first target network resource; and the first target network resource is selected from the second recommended network resources.
6. A connection method, characterized in that: The method is applied to an AMF network element of a core network, including: A first Service Request is received from a terminal device; wherein the first Service Request includes: an identifier of a third target network resource; the first Service Request includes: Query S-NSSAI and QueryDNN; When the third target network resource is congested, sending a first Service Reject to the terminal device; wherein the first Service Reject includes: a rejection reason of the third target network resource and a fallback time of the third target network resource; Receiving a second Service Request sent from the terminal device; Establishing a connection with the terminal device according to the second Service Request; After establishing a connection with the terminal device, receiving a first UL NAS transport sent from the terminal device; wherein the first UL NAS transport carries a first target network resource, so that the AMF network element establishes a PDU session connection based on the first target network resource; When the first target network resource is congested, sending a first DL NAS transport / PDUSession Establish Reject to the terminal device to establish a PDU session connection with the terminal device; The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that provides the same service as that provided by the first target network resource and is not congested.
7. The method according to claim 6, characterized in that The establishing a PDU session connection with the terminal device includes: receiving a second UL NAS transport sent from the terminal device; wherein the second target network resource carried in the second UL NAS transport is selected from the first recommended network resource; When the second target network resources are not congested, the second target network resources are used to establish a PDU session connection with the terminal device.
8. The method according to claim 6, characterized in that The first target network resources include: DNN and / or network slices.
9. The method according to claim 6, characterized in that The first Service Reject also includes: an identifier of a second recommended network resource; The second recommended network resource is a network resource that provides the same service as the service provided by the third target network resource and is not congested.
10. The method according to claim 9, characterized in that The establishing a connection with the terminal device according to the second Service Request includes: When the first target network resource carried in the second Service Request is not congested, establishing a connection with the terminal device by using the first target network resource; The first target network resource is selected from the second recommended network resources.
11. A terminal device, characterized in that: include: A first sending module is used to send a first ULNAS transport to the AMF network element of the core network after establishing a connection with the AMF network element; wherein the first UL NAS transport carries an identifier of a first target network resource, so that the AMF network element establishes a PDU session connection based on the first target network resource; A first receiving module is used to receive a first DLNAS transport / PDU Session Establish Reject returned from the AMF network element for the first target network resource, so as to establish a PDU session connection with the core network; The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that has the same service as the service provided by the first target network resource and is not congested; The terminal device is also used to: send a first Service Request to the AMF network element; wherein the first Service Request includes: an identifier of a third target network resource; the first Service Request includes: Query S-NSSAI and QueryDNN; receive a first Service Reject returned from the AMF network element for the third target network resource; wherein the first Service Reject includes: a rejection reason for the third target network resource and a fallback time for the third target network resource; and according to the first Service Reject, send a second Service Request to the AMF network element to establish a connection with the AMF network element.
12. An AMF network element of a core network, characterized in that: include: A second receiving module is configured to receive a first UL NAS transport sent from the terminal device after establishing a connection with the terminal device; wherein the first UL NAS transport carries a first target network resource, so that the AMF network element establishes a PDU session connection based on the first target network resource; A second sending module, configured to send a first DLNAS transport / PDU Session Establish Reject to the terminal device when the first target network resource is congested, so as to establish a PDU session connection with the terminal device; The first DL NAS transport / PDU Session Establish Reject includes: an identifier of a first recommended network resource; the first recommended network resource is: a network resource that has the same service as the service provided by the first target network resource and is not congested; The AMF network element is also used to: receive a first Service Request sent from a terminal device; wherein the first Service Request includes: an identifier of a third target network resource; the first Service Request includes: QueryS-NSSAI and Query DNN; when the third target network resource is congested, send a first Service Reject to the terminal device; wherein the first Service Reject includes: a rejection reason for the third target network resource and a fallback time for the third target network resource; receive a second Service Request sent from the terminal device; and establish a connection with the terminal device according to the second Service Request.
13. A terminal device, characterized in that: include: A processor and a storage medium storing instructions executable by the processor, wherein the storage medium relies on the processor to perform operations through a communication bus, and when the instructions are executed by the processor, the connection method described in any one of claims 1 to 5 is executed.
14. An AMF network element of a core network, characterized in that: include: A processor and a storage medium storing instructions executable by the processor, wherein the storage medium relies on the processor to perform operations through a communication bus, and when the instructions are executed by the processor, the connection method described in any one of claims 6 to 10 is executed.
15. A computer storage medium, characterized in that Executable instructions are stored, and when the executable instructions are executed by one or more processors, the processors execute the connection method according to any one of claims 1 to 5, or the connection method according to any one of claims 6 to 10.
