Bearer identification allocation method, device, equipment and storage medium

Abstract

The present application proposes a method, device, session management network element, access and mobility management network element, and storage medium for allocating a bearer identifier. The method includes: when creating a current session for a terminal, sending an EBI allocation request message to the AMF; receiving a PDU session update message sent by the AMF, the PDU session update message including information about the session to be preempted; when it is determined that the session to be preempted cannot be processed, sending a first PDU session update response message to the AMF, the first PDU session update response message including a first cause value for not being able to process the session to be preempted, the first cause value being used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session. Compared with traditional technologies, this method improves the success rate of EBI allocation.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method and device for allocating a bearer identifier, a session management network element, an access and mobility management network element, and a storage medium. Background Art

[0002] With the official commercial launch of 5th Generation (5G) networks, 5G networks will become an everyday reality. However, in the early stages of 5G commercialization, limited by the maturity of the technology and the level of support from terminal devices, 5G networks cannot yet achieve widespread coverage. 5G networks and 4th Generation (4G) networks will coexist for a long time. In this networking scenario, interoperability between 5G and 4G networks will exist. Therefore, when establishing a 5G session, the Session Management Function (SMF) must request the Access and Mobility Management Function (AMF) to allocate an Evolved Packet System Bearer Identity (EBI) in advance. Furthermore, because the session identifier ranges used by 5G and 4G networks are different, if the number of EBIs requested by the SMF exceeds the maximum number supported by the 4G network, or if the AMF selects a different SMF for the same Data Network Name (DNN) during session creation, the AMF will decide to initiate EBI preemption. However, the traditional EBI preemption method has a low EBI allocation success rate. Summary of the Invention

[0003] The present application provides a method and apparatus for allocating a bearer identifier, a session management network element, an access and mobility management network element, and a storage medium.

[0004] In a first aspect, an embodiment of the present application provides a method for allocating a bearer identifier, including:

[0005] When creating the current session for the terminal, send an Evolved Packet System Bearer Identity (EBI) Allocation Request message to the access and mobility management network element (AMF);

[0006] Receive a protocol data unit (PDU) session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted;

[0007] When it is determined that the session to be preempted cannot be processed, a first PDU session update response message is sent to the AMF, where the first PDU session update response message includes a first cause value for not being able to process the session to be preempted, and the first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session.

[0008] In a second aspect, an embodiment of the present application provides a device for distributing a bearer identifier, including:

[0009] A first sending module is configured to send an evolved packet system bearer identifier EBI allocation request message to the access and mobility management network element AMF when creating a current session for the terminal;

[0010] A receiving module, configured to receive a protocol data unit (PDU) session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted;

[0011] a determination module, configured to determine that the session to be preempted cannot be processed;

[0012] The second sending module is used to send a first PDU session update response message to the AMF when the determination module determines that the session to be preempted cannot be processed, wherein the first PDU session update response message includes a first cause value for not being able to process the session to be preempted, and the first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session.

[0013] In a third aspect, an embodiment of the present application provides a session management network element, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements any one of the methods in the embodiments of the present application when executing the computer program.

[0014] In a fourth aspect, an embodiment of the present application provides a method for allocating a bearer identifier, including:

[0015] Receiving an Evolved Packet System Bearer Identifier (EBI) allocation request message sent by a session management network element (SMF), where the EBI allocation request message is sent when the SMF creates a current session for a terminal;

[0016] When it is determined that EBI preemption is required according to the EBI allocation request message, a protocol data unit PDU session update message is sent to the SMF, where the PDU session update message includes information about the session to be preempted;

[0017] Receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first cause value for not being able to process the session to be preempted;

[0018] According to the first reason value, it is determined that the EBI preemption is successful, and the EBI of the session to be preempted is allocated to the current session.

[0019] In a fifth aspect, an embodiment of the present application provides a device for distributing a bearer identifier, including:

[0020] A first receiving module is configured to receive an Evolved Packet System Bearer Identifier (EBI) allocation request message sent by a session management network element (SMF), where the EBI allocation request message is sent when the SMF creates a current session for a terminal.

[0021] A sending module, configured to send a protocol data unit (PDU) session update message to the SMF when it is determined that EBI preemption is required according to the EBI allocation request message, wherein the PDU session update message includes information about the session to be preempted;

[0022] A second receiving module is configured to receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first cause value for not being able to process the session to be preempted;

[0023] The first processing module is configured to determine, based on the first reason value, that the EBI preemption is successful, and allocate the EBI of the session to be preempted to the current session.

[0024] In a sixth aspect, an embodiment of the present application provides an access and mobility management network element, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements any one of the methods in the embodiments of the present application when executing the computer program.

[0025] In a seventh aspect, an embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.

[0026] The bearer identifier allocation method, apparatus, session management network element, and storage medium provided in the embodiments of the present application are as follows: when creating a current session for a terminal, the session management network element sends an EBI allocation request message to the AMF, then receives a PDU session update message from the AMF. When the session management network element determines that it cannot process the session to be preempted, it sends a first PDU session update response message to the AMF, wherein the first PDU session update response message carries a first cause value indicating that it cannot process the session to be preempted. Because the session management network element can report the first cause value indicating that it cannot process the session to be preempted when determining that it cannot process the session to be preempted, the AMF can perform refined processing on EBI allocation based on the first cause value, thereby determining that EBI preemption is successful based on the refined first cause value and allocating the EBI of the session to be preempted to the current session. In conventional techniques, the session management network element only reports that it cannot process the session to be preempted, causing the AMF to directly conclude that EBI preemption has failed, resulting in an inability to allocate an EBI to the current session. Therefore, compared with conventional techniques, the present application improves the success rate of EBI allocation.

[0027] The bearer identifier allocation method, device, access and mobility management network element and storage medium provided in the embodiments of the present application receive an EBI allocation request message sent by the SMF, and when it is determined that EBI preemption is required based on the EBI allocation request message, send a PDU session update message to the SMF, and then receive a first PDU session update response message sent by the SMF. The first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first reason value for not being able to process the session to be preempted, and based on the first reason value, determines that the EBI preemption is successful, and allocates the EBI of the session to be preempted to the current session. Since the first PDU session update response message received by the access and mobility management network element carries the first cause value that the SMF cannot process the session to be preempted, the AMF can perform fine-grained processing on the EBI allocation based on the first cause value, so that the EBI preemption can be determined to be successful based on the detailed first cause value, and the EBI of the session to be preempted can be allocated to the current session; in the traditional technology, the AMF directly determines that the EBI preemption has failed when the SMF cannot process the session to be preempted, resulting in the inability to allocate EBI to the current session. Therefore, compared with the traditional technology, the present application improves the success rate of EBI allocation. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A schematic diagram of the internal structure of a communication system provided in an embodiment of the present application;

[0029] Figure 2 A flowchart of a method for allocating a bearer identifier provided in an embodiment of the present application;

[0030] Figure 3 Another flowchart of the method for allocating a bearer identifier provided in an embodiment of the present application;

[0031] Figure 4 A schematic diagram of another flow chart of the method for allocating a bearer identifier provided in an embodiment of the present application;

[0032] Figure 5 A schematic diagram of another flow chart of the method for allocating a bearer identifier provided in an embodiment of the present application;

[0033] Figure 6 A schematic diagram of another flow chart of the method for allocating a bearer identifier provided in an embodiment of the present application;

[0034] Figure 7 A schematic diagram of another flow chart of the method for allocating a bearer identifier provided in an embodiment of the present application;

[0035] Figure 8 A schematic diagram of another flow chart of the method for allocating a bearer identifier provided in an embodiment of the present application;

[0036] Figure 9 A schematic diagram of another flow chart of the method for allocating a bearer identifier provided in an embodiment of the present application;

[0037] Figure 10 A schematic diagram of the internal structure of a distribution device carrying an identifier provided in an embodiment of the present application;

[0038] Figure 11 A schematic diagram of another internal structure of a distribution device carrying an identifier provided in an embodiment of the present application;

[0039] Figure 12 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The method for allocating a bearer identifier provided in the embodiment of the present application can be applied to Figure 1 The communication system shown includes a terminal 10, access network equipment 11, and core network equipment 12. The core network equipment includes the SMF and AMF. The AMF is used to allocate EBIs to terminals, and the SMF is used to manage sessions established by terminals. Terminal 10 is a converged terminal, meaning it supports both 5G and 4G network standards. Optionally, terminal 10 can be a smartphone, tablet, smartwatch, fitness tracker, virtual reality device, or IoT sensor.

[0041] To make the purpose, technical solutions and advantages of this application more clear, the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of this application can be combined with each other in any way.

[0042] The following is an introduction using SMF as an example, specifically:

[0043] Figure 2 A flow chart of the method for allocating a bearer identifier provided in an embodiment of the present application. Figure 2 As shown, the method may include:

[0044] S101. When creating a current session for a terminal, an EBI allocation request message is sent to the AMF.

[0045] In the early stages of 5G network commercialization, limited by the maturity of the technology and the level of support from terminal devices, 5G networks cannot yet provide widespread coverage. Therefore, the actual network will adopt a hybrid networking approach. For example, areas with high traffic volume can be covered by 5G networks, while other areas can be covered by 4G networks. In other words, the actual network will include both 5G and 4G networks. In this networking approach, interoperability between 5G and 4G networks will exist. To ensure smooth handover of end-user sessions from 5G to 4G networks, when a terminal establishes a current session on a 5G network, the SMF sends an EBI allocation request message to the AMF, requesting that the AMF allocate an EBI for the current session. It is understood that if the AMF successfully allocates an EBI for the current session, the current session can be smoothly handed over from the 5G network to the 4G network. If the AMF fails to allocate an EBI for the current session, the current session cannot be handed over from the 5G network to the 4G network.

[0046] S102. Receive a protocol data unit (PDU) session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted.

[0047] Among them, after AMF receives the EBI allocation request message sent by SMF, AMF can decide whether to initiate the EBI preemption process based on the following two situations:

[0048] 1. Determine whether to initiate EBI preemption based on the number of sessions / flows established historically, the number of sessions / flows included in the current session, and the maximum number of EBIs supported by the 4G network. When the maximum number of EBIs supported by the 4G network cannot meet the number of sessions / flows included in the current session, the AMF decides to initiate EBI preemption. For example, the maximum number of EBIs supported by the 4G network is 11, the number of sessions / flows that the terminal has established historically in the 5G network is 10, and the number of sessions / flows included in the current session is 4. In this way, since the maximum number of EBIs supported by the 4G network cannot meet the number of sessions / flows included in the current session, the AMF decides to initiate EBI preemption.

[0049] 2. During the session creation process, AMF selects different SMFs for the created session based on the terminal's DNN. That is, there are multiple anchor points in the 5G network, while there is only one anchor point in the 4G network. In this way, when the SMF selected by AMF for the current session based on the same DNN is different from the SMF selected for the historical session, AMF decision needs to preempt EBI.

[0050] When it is determined that EBI preemption is required, AMF sends a PDU session update message to SMF, where the PDU session update message includes information about the session to be preempted.

[0051] S103. When it is determined that the session to be preempted cannot be processed, a first PDU session update response message is sent to the AMF, where the first PDU session update response message includes a first cause value for not being able to process the session to be preempted, and the first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session.

[0052] Among them, the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal. The SMF searches for the session to be preempted according to the information of the session to be preempted included in the PDU session update message. When the session search fails, the SMF sends a first PDU session update response message to the AMF, carrying the first cause value of the session search failure "the context of the session to be preempted does not exist". In this way, after receiving the first PDU session update response message, the AMF can judge that the session to be preempted no longer exists based on the first cause value "the context of the session to be preempted does not exist", thereby determining that the EBI of the session to be preempted is successfully preempted, and allocates the EBI previously allocated to the session to be preempted to the current session.

[0053] SMF searches for the session to be preempted based on the information of the session to be preempted included in the PDU session update message. When SMF finds an internal abnormality in itself, that is, the network element where the session to be preempted is located is abnormal, SMF sends a first PDU session update response message to AMF, carrying the first reason value "the network element where the session to be preempted is located is abnormal" that cannot handle the session to be preempted. In this way, after AMF receives the first PDU session update response message, it can judge that the SMF where the session to be preempted is located is abnormal based on the first reason value "the network element where the session to be preempted is located is abnormal", thereby determining that the EBI of the session to be preempted is successfully preempted, and assigning the EBI previously allocated to the session to be preempted to the current session.

[0054] In a method for allocating a bearer identifier provided in an embodiment of the present application, when creating a current session for a terminal, a session management network element sends an EBI allocation request message to an AMF, then receives a PDU session update message from the AMF. When the session management network element determines that it cannot process the session to be preempted, it sends a first PDU session update response message to the AMF, wherein the first PDU session update response message carries a first cause value indicating that it cannot process the session to be preempted. Because the session management network element can report the first cause value indicating that it cannot process the session to be preempted when determining that it cannot process the session to be preempted, the AMF can perform refined processing on EBI allocation based on the first cause value, thereby determining that EBI preemption is successful based on the refined first cause value and allocating the EBI of the session to be preempted to the current session. In conventional techniques, however, the session management network element only reports that it cannot process the session to be preempted, causing the AMF to directly conclude that EBI preemption has failed, resulting in an inability to allocate an EBI to the current session. Therefore, compared with conventional techniques, the present application improves the success rate of EBI allocation.

[0055] When the SMF determines that the session to be preempted can be processed, in order to ensure the rationality of EBI preemption, optionally, after the above S102, the method may further include: when it is determined that preemption of the EBI of the session to be preempted is not allowed, sending a second PDU session update response message to the AMF, the second PDU session update response message including a second cause value, and the second cause value is used to indicate that the AMF failed to preempt the EBI of the session to be preempted.

[0056] Among them, the SMF can find the session to be preempted based on the information of the session to be preempted included in the PDU session update message, and determines that the SMF where the session to be preempted is located is normal. However, the SMF determines that the EBI of the session to be preempted is not allowed to be preempted based on the information of the session to be preempted. At this time, the SMF sends a second PDU session update response message to the AMF, carrying the second cause value "preemption not allowed". In this way, after receiving the second PDU session update response message, the AMF can determine that the SMF where the session to be preempted is located does not agree to preempt the EBI of the session to be preempted based on the second cause value "preemption not allowed", thereby determining that the preemption of the EBI of the session to be preempted has failed.

[0057] Optionally, the process in which the SMF determines that the EBI of the session to be preempted is not allowed to be preempted based on the information of the session to be preempted can be: determining that the EBI of the session to be preempted is not allowed to be preempted according to the service priority of the session to be preempted; or determining that the EBI of the session to be preempted is not allowed to be preempted according to local configuration information.

[0058] Specifically, if the SMF discovers that the session to be preempted is currently performing high-priority services, the SMF will not preempt the EBI of the session to be preempted in order to ensure that the high-priority services can be switched normally. Alternatively, if the local configuration information in the SMF contains the session identifier of a session that is not allowed to be preempted, and the local configuration information also contains the session identifier of the session to be preempted, the SMF will also not preempt the EBI of the session to be preempted.

[0059] In this embodiment, when the SMF determines that the EBI of the session to be preempted is not allowed to be preempted based on the service priority of the session to be preempted and the local configuration information, it sends a second PDU session update response message to the AMF, carrying the second cause value "preemption not allowed". In this way, the AMF can determine that the preemption of the EBI of the session to be preempted has failed and will not allocate the EBI of the session to be preempted to the current session, thereby ensuring that the session of the high-priority service can be switched normally, and further ensuring the rationality of the EBI preemption.

[0060] Next, we will take AMF as an example to introduce the execution subject.

[0061] Figure 3 Another flow chart of the method for allocating a bearer identifier provided in the embodiment of the present application. Figure 3 As shown, the method may include:

[0062] S201. Receive an EBI allocation request message sent by an SMF, where the EBI allocation request message is sent when the SMF creates a current session for a terminal.

[0063] In the early stages of 5G network commercialization, limited by the maturity of the technology and the level of support from terminal devices, 5G networks cannot yet provide widespread coverage. Therefore, the actual network will adopt a hybrid networking approach. For example, areas with high traffic volume may be covered by 5G networks, while other areas may be covered by 4G networks. In other words, the actual network will include both 5G and 4G networks. In this networking approach, interoperability between 5G and 4G networks will exist. To ensure smooth handover of end-user sessions from 5G to 4G networks, when a terminal establishes a current session on the 5G network, the SMF sends an EBI allocation request message to the AMF, requesting that the AMF allocate an EBI for the current session. This allows the AMF to receive the EBI allocation request message sent by the SMF when the terminal establishes the current session on the 5G network. It is understood that if the AMF successfully allocates an EBI for the current session, it indicates that the current session can be smoothly handed over from the 5G network to the 4G network. If the AMF fails to allocate an EBI for the current session, it indicates that the current session cannot be handed over from the 5G network to the 4G network.

[0064] S202: When it is determined according to the EBI allocation request message that EBI preemption is required, a PDU session update message is sent to the SMF, where the PDU session update message includes information about the session to be preempted.

[0065] Among them, after AMF receives the EBI allocation request message sent by SMF, AMF can decide whether to initiate the EBI preemption process based on the following two situations:

[0066] 1. Determine whether to initiate EBI preemption based on the number of sessions / flows established historically, the number of sessions / flows included in the current session, and the maximum number of EBIs supported by the 4G network. When the maximum number of EBIs supported by the 4G network cannot meet the number of sessions / flows included in the current session, the AMF decides to initiate EBI preemption. For example, the maximum number of EBIs supported by the 4G network is 11, the number of sessions / flows that the terminal has established historically in the 5G network is 10, and the number of sessions / flows included in the current session is 4. In this way, since the maximum number of EBIs supported by the 4G network cannot meet the number of sessions / flows included in the current session, the AMF decides to initiate EBI preemption.

[0067] 2. During the session creation process, AMF selects different SMFs for the created session based on the terminal's DNN. That is, there are multiple anchor points in the 5G network, while there is only one anchor point in the 4G network. In this way, when the SMF selected by AMF for the current session based on the same DNN is different from the SMF selected for the historical session, AMF decision needs to preempt EBI.

[0068] S203. Receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first reason value for not being able to process the session to be preempted.

[0069] The first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal. The SMF searches for the session to be preempted based on the information of the session to be preempted included in the PDU session update message. When the session search fails, the SMF sends a first PDU session update response message to the AMF, carrying the first cause value of the session search failure "the context of the session to be preempted does not exist".

[0070] SMF searches for the session to be preempted based on the information of the session to be preempted included in the PDU session update message. When SMF finds an internal abnormality within itself, that is, the network element where the session to be preempted is located is abnormal, SMF sends a first PDU session update response message to AMF, carrying the first reason value for being unable to process the session to be preempted, "the network element where the session to be preempted is located is abnormal."

[0071] S204: Determine, based on the first cause value, that the EBI preemption is successful, and allocate the EBI of the session to be preempted to the current session.

[0072] Among them, after the AMF receives the first PDU session update response message, it can judge that the session to be preempted no longer exists according to the first cause value "the context of the session to be preempted does not exist", thereby determining that the EBI of the session to be preempted is successfully preempted, and assigning the EBI previously allocated to the session to be preempted to the current session.

[0073] After the AMF receives the first PDU session update response message, it can judge that the SMF where the session to be preempted is located is abnormal based on the first cause value "the network element where the session to be preempted is located is abnormal", thereby determining that the EBI of the session to be preempted is successfully preempted, and assigning the EBI previously allocated to the session to be preempted to the current session.

[0074] The bearer identifier allocation method provided in an embodiment of the present application receives an EBI allocation request message sent by an SMF, and when it is determined that EBI preemption is required based on the EBI allocation request message, sends a PDU session update message to the SMF, and then receives a first PDU session update response message sent by the SMF. The first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first reason value for not being able to process the session to be preempted, and based on the first reason value, determines that the EBI preemption is successful, and allocates the EBI of the session to be preempted to the current session. Since the first PDU session update response message received by the access and mobility management network element carries the first cause value that the SMF cannot process the session to be preempted, the AMF can perform fine-grained processing on the EBI allocation based on the first cause value, so that the EBI preemption can be determined to be successful based on the detailed first cause value, and the EBI of the session to be preempted can be allocated to the current session; in the traditional technology, the AMF directly determines that the EBI preemption has failed when the SMF cannot process the session to be preempted, resulting in the inability to allocate EBI to the current session. Therefore, compared with the traditional technology, the present application improves the success rate of EBI allocation.

[0075] In order to ensure the rationality of EBI preemption, optionally, based on the above embodiment, the method may also include: receiving a second PDU session update response message sent by the SMF, the second PDU session update response message is sent when the SMF determines that preemption of the EBI of the session to be preempted is not allowed, and the second PDU session update response message includes a second cause value; according to the second cause value, determining that the EBI preemption failed, and sending an EBI allocation failure message to the SMF.

[0076] Among them, the SMF can find the session to be preempted according to the information of the session to be preempted included in the PDU session update message, and determines that the SMF where the session to be preempted is located is normal. However, the SMF determines that the EBI of the session to be preempted is not allowed to be preempted based on the information of the session to be preempted. At this time, the AMF can receive the second PDU session update response message sent by the SMF. The second PDU session update response message carries the second cause value "preemption not allowed". In this way, the AMF determines that the SMF where the session to be preempted is located does not agree to preempt the EBI of the session to be preempted according to the second cause value "preemption not allowed", and thus determines that the preemption of the EBI of the session to be preempted has failed.

[0077] Optionally, the process in which the SMF determines that the EBI of the session to be preempted is not allowed to be preempted based on the information of the session to be preempted can be: determining that the EBI of the session to be preempted is not allowed to be preempted according to the service priority of the session to be preempted; or determining that the EBI of the session to be preempted is not allowed to be preempted according to local configuration information.

[0078] Specifically, if the SMF discovers that the session to be preempted is currently performing high-priority services, the SMF will not preempt the EBI of the session to be preempted in order to ensure that the high-priority services can be switched normally. Alternatively, if the local configuration information in the SMF contains the session identifier of a session that is not allowed to be preempted, and the local configuration information also contains the session identifier of the session to be preempted, the SMF will also not preempt the EBI of the session to be preempted.

[0079] In this embodiment, when the SMF determines that preemption of the EBI of the session to be preempted is not allowed based on the service priority of the session to be preempted and local configuration information, the AMF may receive a second PDU session update response message sent by the SMF, where the second PDU session update response message carries the second cause value "preemption not allowed". In this way, the AMF can determine that preemption of the EBI of the session to be preempted has failed and will not allocate the EBI of the session to be preempted to the current session, thereby ensuring that sessions with high-priority services can be switched normally and further ensuring the rationality of EBI preemption.

[0080] To facilitate understanding by those skilled in the art, the following takes the interaction between SMF and AMF as an example for introduction, specifically:

[0081] Example 1

[0082] like Figure 4 and Figure 5 As shown, in this example, when a non-first PDU session is initiated by the terminal (the non-first PDU here is the current session, which may include one or more streams), when the AMF performs EBI preemption according to the local configuration decision, the session to be preempted no longer exists on the SMF. The processing steps between SMF and AMF are as follows:

[0083] S301. The SMF to which the current session belongs sends a Namf_Communication_EBIAssignment Request message (EBI assignment request message) to the AMF.

[0084] S302. AMF decides to preempt EBI, and AMF sends Nsmf_PDUSession_UpdateSMContext message (PDU session update message) to the SMF to which the session to be preempted belongs.

[0085] The SMF to which the current session belongs and the SMF to which the session to be preempted belongs may be the same SMF or different SMFs. Figure 4 The flowchart of the EBI allocation process is as follows: Figure 5A flowchart of the EBI allocation process when the SMF to which the current session belongs and the SMF to which the session to be preempted belongs are different SMFs.

[0086] S303. The SMF to which the session to be preempted belongs fails to search for the session according to the information of the session to be preempted carried in the PDU session update message, and replies to the AMF with an Nsmf_PDUSession_UpdateSMContext Response message (first PDU session update response message), carrying the first cause value "the context of the session to be preempted does not exist".

[0087] S304: The AMF determines that the session to be preempted no longer exists based on the first cause value, and determines that the EBI preemption is successful. The AMF sends a Namf_Communication_EBIAssignment Response (EBI assignment success response) to the SMF to which the current session belongs, carrying a list of EBIs to be reallocated after the preemption. Each EBI in the EBI list is an EBI allocated for the current session.

[0088] Since the AMF has sensed that the session to be preempted no longer exists at the SMF, the method may optionally further include:

[0089] S305. The AMF locally releases the relevant resources of the session to be preempted.

[0090] Example 2

[0091] like Figure 6 and Figure 7 As shown, in this example, when a non-first PDU session is initiated by the terminal (the non-first PDU here is the current session, which may include one or more streams), the AMF performs EBI preemption according to the local configuration decision. At this time, the SMF system where the session to be preempted is located is abnormal. The processing steps between SMF and AMF are as follows:

[0092] S401. The SMF to which the current session belongs sends a Namf_Communication_EBIAssignment Request message (EBI assignment request message) to the AMF.

[0093] S402. AMF decides to preempt EBI, and AMF sends Nsmf_PDUSession_UpdateSMContext message (PDU session update message) to the SMF to which the session to be preempted belongs.

[0094] The SMF to which the current session belongs and the SMF to which the session to be preempted belongs may be the same SMF or different SMFs. Figure 6The flowchart of the EBI allocation process is as follows: Figure 7 A flowchart of the EBI allocation process when the SMF to which the current session belongs and the SMF to which the session to be preempted belongs are different SMFs.

[0095] S403. After receiving the PDU session update message, the SMF to which the session to be preempted belongs discovers an internal abnormality and replies with an Nsmf_PDUSession_UpdateSMContext Response message (first PDU session update response message) carrying the first cause value "abnormality in the network element where the session to be preempted is located".

[0096] S404: The AMF determines that the SMF of the session to be preempted is abnormal based on the first cause value, determines that the EBI preemption is successful, and responds to the SMF of the current session with a Namf_Communication_EBIAssignment Response (EBI assignment success response), which carries the list of EBIs to be reallocated after the preemption. Each EBI in the EBI list is the EBI allocated for the current session.

[0097] Optionally, although AMF has sensed that the SMF where the session to be preempted is located is abnormal, it cannot be determined whether the session to be preempted is actually released, and whether AMF retains the relevant resources of the session to be preempted. Of course, AMF can also decide whether to retain the relevant resources of the session to be preempted based on local configuration.

[0098] Example 3

[0099] like Figure 8 and Figure 9 As shown, in this example, when a non-first PDU session is created for the terminal (the non-first PDU here is the current session, which may include one or more streams), the AMF performs EBI preemption according to the local configuration decision. At this time, the session to be preempted is performing high-priority services. The processing steps between SMF and AMF are as follows:

[0100] S501. The SMF to which the current session belongs sends a Namf_Communication_EBIAssignment Request message (EBI assignment request message) to the AMF.

[0101] S502. AMF decides to perform EBI preemption, and AMF sends an Nsmf_PDUSession_UpdateSMContext message (PDU session update message) to the SMF to which the session to be preempted belongs.

[0102] The SMF to which the current session belongs and the SMF to which the session to be preempted belongs may be the same SMF or different SMFs. Figure 8 The flowchart of the EBI allocation process is as follows: Figure 9 A flowchart of the EBI allocation process when the SMF to which the current session belongs and the SMF to which the session to be preempted belongs are different SMFs.

[0103] S503. After the SMF to which the session to be preempted belongs receives the PDU session update message, it finds that a high-priority service is in progress under the session to be preempted or, according to local configuration, preemption of the EBI of the session to be preempted is not allowed. It replies with an Nsmf_PDUSession_UpdateSMContext Response message (the second PDU session update response message) carrying the second cause value "preemption not allowed".

[0104] S504. The AMF determines, based on the second reason value, that the SMF where the session to be preempted is located does not agree to preempt, determines that the EBI preemption fails, and replies Namf_Communication_EBIAssignment Error (EBI allocation failure response) to the SMF to which the current session belongs, which may carry the reason value for the allocation failure.

[0105] Figure 10 A schematic diagram of the internal structure of the distribution device carrying the identifier provided in the embodiment of the present application is shown as follows: Figure 10 As shown, the device may include: a first sending module 20, a receiving module 21, a determining module 22 and a second sending module 23.

[0106] Specifically, the first sending module 20 is used to send an EBI allocation request message to the AMF when creating a current session for the terminal;

[0107] The receiving module 21 is used to receive the PDU session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted;

[0108] The determination module 22 is used to determine that the session to be preempted cannot be processed;

[0109] The second sending module 23 is used to send a first PDU session update response message to the AMF when the determination module determines that the session to be preempted cannot be processed. The first PDU session update response message includes a first cause value for not being able to process the session to be preempted. The first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session.

[0110] In the apparatus for allocating bearer identifiers provided in an embodiment of the present application, when creating a current session for a terminal, a session management network element sends an EBI allocation request message to an AMF, then receives a PDU session update message from the AMF. When the session management network element determines that it cannot process the session to be preempted, it sends a first PDU session update response message to the AMF, wherein the first PDU session update response message carries a first cause value indicating that it cannot process the session to be preempted. Because the session management network element can report the first cause value indicating that it cannot process the session to be preempted when determining that it cannot process the session to be preempted, the AMF can perform refined processing on EBI allocation based on the first cause value, thereby determining that EBI preemption is successful based on the refined first cause value and allocating the EBI of the session to be preempted to the current session. In conventional techniques, however, the session management network element only reports that it cannot process the session to be preempted, causing the AMF to directly conclude that EBI preemption has failed, resulting in an inability to allocate an EBI to the current session. Therefore, compared with conventional techniques, the present application improves the success rate of EBI allocation.

[0111] Optionally, based on the above embodiment, the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

[0112] Optionally, based on the above embodiment, the determining module 22 is further configured to determine that the EBI of the session to be preempted is not allowed to be preempted; and the apparatus further comprises: a third sending module.

[0113] Specifically, the third sending module is used to send a second PDU session update response message to the AMF when the determination module determines that preemption of the EBI of the session to be preempted is not allowed, and the second PDU session update response message includes a second cause value, and the second cause value is used to indicate that the AMF failed to preempt the EBI of the session to be preempted.

[0114] Optionally, based on the above embodiment, the determination module 22 is specifically used to determine that the EBI of the session to be preempted is not allowed to be preempted according to the service priority of the session to be preempted; or, the determination module 22 is specifically used to determine that the EBI of the session to be preempted is not allowed to be preempted according to local configuration information.

[0115] Figure 11 Another internal structure diagram of the distribution device carrying the identifier provided in the embodiment of the present application is as follows Figure 11 As shown, the device may include: a first receiving module 30 , a sending module 31 , a second receiving module 32 and a first processing module 33 .

[0116] Specifically, the first receiving module 30 is used to receive an EBI allocation request message sent by the SMF, where the EBI allocation request message is sent when the SMF creates a current session for the terminal;

[0117] The sending module 31 is configured to send a PDU session update message to the SMF when it is determined that EBI preemption is required according to the EBI allocation request message, wherein the PDU session update message includes information about the session to be preempted;

[0118] The second receiving module 32 is used to receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first cause value for not being able to process the session to be preempted;

[0119] The first processing module 33 is configured to determine, based on the first cause value, that the EBI preemption is successful, and allocate the EBI of the session to be preempted to the current session.

[0120] The bearer identifier allocation device provided in an embodiment of the present application receives an EBI allocation request message sent by the SMF, and when it is determined that EBI preemption is required based on the EBI allocation request message, sends a PDU session update message to the SMF, and then receives a first PDU session update response message sent by the SMF. The first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first reason value for not being able to process the session to be preempted, and based on the first reason value, determines that the EBI preemption is successful, and allocates the EBI of the session to be preempted to the current session. Since the first PDU session update response message received by the access and mobility management network element carries the first cause value that the SMF cannot process the session to be preempted, the AMF can perform fine-grained processing on the EBI allocation based on the first cause value, so that the EBI preemption can be determined to be successful based on the detailed first cause value, and the EBI of the session to be preempted can be allocated to the current session; in the traditional technology, the AMF directly determines that the EBI preemption has failed when the SMF cannot process the session to be preempted, resulting in the inability to allocate EBI to the current session. Therefore, compared with the traditional technology, the present application improves the success rate of EBI allocation.

[0121] Optionally, based on the above embodiment, the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

[0122] Optionally, based on the above embodiment, the device further includes: a third receiving module and a second processing module.

[0123] Specifically, the third receiving module is used to receive a second PDU session update response message sent by the SMF, where the second PDU session update response message is sent when the SMF determines that the EBI of the session to be preempted is not allowed to be preempted, and the second PDU session update response message includes a second cause value;

[0124] The second processing module is used to determine that the EBI preemption fails according to the second cause value, and send an EBI allocation failure message to the SMF.

[0125] In one embodiment, a computer device is provided. The computer device may be a session management network element or an access and mobility management network element. The internal structure diagram of the computer device may be as follows: Figure 12 As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store data in the bearer identifier allocation process. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a method for allocating a bearer identifier is implemented.

[0126] Those skilled in the art will understand that Figure 12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0127] In one embodiment, a session management network element is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0128] When creating the current session for the terminal, an EBI allocation request message is sent to the AMF;

[0129] Receive a PDU session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted;

[0130] When it is determined that the session to be preempted cannot be processed, a first PDU session update response message is sent to the AMF, where the first PDU session update response message includes a first cause value for not being able to process the session to be preempted, and the first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session.

[0131] Optionally, the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

[0132] In one embodiment, when the processor executes the computer program, the following steps are further implemented: when it is determined that preemption of the EBI of the session to be preempted is not allowed, a second PDU session update response message is sent to the AMF, wherein the second PDU session update response message includes a second cause value, and the second cause value is used to indicate that the AMF fails to preempt the EBI of the session to be preempted.

[0133] In one embodiment, when executing the computer program, the processor further implements the following steps: determining, based on the service priority of the session to be preempted, that the EBI of the session to be preempted is not allowed to be preempted; or, based on local configuration information, determining, based on the EBI of the session to be preempted, that the EBI of the session to be preempted is not allowed to be preempted.

[0134] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0135] When creating the current session for the terminal, an EBI allocation request message is sent to the AMF;

[0136] Receive a PDU session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted;

[0137] When it is determined that the session to be preempted cannot be processed, a first PDU session update response message is sent to the AMF, where the first PDU session update response message includes a first cause value for not being able to process the session to be preempted, and the first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session.

[0138] Optionally, the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

[0139] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: determining, based on the service priority of the session to be preempted, that the EBI of the session to be preempted is not allowed to be preempted; or, based on local configuration information, determining, based on the EBI of the session to be preempted, that the EBI of the session to be preempted is not allowed to be preempted.

[0140] In one embodiment, an access and mobility management network element is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0141] Receive an EBI allocation request message sent by the SMF, where the EBI allocation request message is sent when the SMF creates a current session for the terminal;

[0142] When it is determined that EBI preemption is required according to the EBI allocation request message, a PDU session update message is sent to the SMF, where the PDU session update message includes information about the session to be preempted;

[0143] Receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first cause value for not being able to process the session to be preempted;

[0144] According to the first reason value, it is determined that the EBI preemption is successful, and the EBI of the session to be preempted is allocated to the current session.

[0145] Optionally, the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

[0146] In one embodiment, when the processor executes the computer program, it also implements the following steps: receiving a second PDU session update response message sent by the SMF, the second PDU session update response message is sent when the SMF determines that preemption of the EBI of the session to be preempted is not allowed, and the second PDU session update response message includes a second cause value; according to the second cause value, determining that the EBI preemption failed, and sending an EBI allocation failure message to the SMF.

[0147] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0148] Receive an EBI allocation request message sent by the SMF, where the EBI allocation request message is sent when the SMF creates a current session for the terminal;

[0149] When it is determined that EBI preemption is required according to the EBI allocation request message, a PDU session update message is sent to the SMF, where the PDU session update message includes information about the session to be preempted;

[0150] Receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first cause value for not being able to process the session to be preempted;

[0151] According to the first reason value, it is determined that the EBI preemption is successful, and the EBI of the session to be preempted is allocated to the current session.

[0152] Optionally, the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

[0153] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving a second PDU session update response message sent by the SMF, the second PDU session update response message is sent when the SMF determines that preemption of the EBI of the session to be preempted is not allowed, and the second PDU session update response message includes a second cause value; according to the second cause value, determining that the EBI preemption failed, and sending an EBI allocation failure message to the SMF.

[0154] The bearer identifier allocation device, session management network element, access and mobility management network element, and storage medium provided in the above embodiments can execute the bearer identifier allocation method provided in any embodiment of the present application, and have the corresponding functional modules and beneficial effects of executing the method. For technical details not fully described in the above embodiments, please refer to the bearer identifier allocation method provided in any embodiment of the present application.

[0155] The above description is merely an exemplary embodiment of the present application and is not intended to limit the scope of protection of the present application.

[0156] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0157] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a fault injection test apparatus, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0158] The block diagram of any logical flow in the accompanying drawings of the present application can represent program steps, or can represent interconnected logical circuits, modules and functions, or can represent a combination of program steps and logical circuits, modules and functions. The computer program can be stored on a memory. The memory can have any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory device and system (digital versatile disc DVD or CD optical disc) etc. Computer-readable media can include non-transient storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FPGA) and a processor based on a multi-core processor architecture.

[0159] The above description of exemplary embodiments of the present application has been provided by way of exemplary and non-limiting examples. However, various modifications and adaptations of the above embodiments will be apparent to those skilled in the art, when considered in conjunction with the accompanying drawings and the appended claims, without departing from the scope of the present application. Therefore, the proper scope of the present application will be determined by reference to the appended claims.

Claims

1. A method for allocating a bearer identifier, characterized in that: include: When creating the current session for the terminal, send an Evolved Packet System Bearer Identity (EBI) Allocation Request message to the access and mobility management network element (AMF); Receive a protocol data unit (PDU) session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted; When it is determined that the session to be preempted cannot be processed, a first PDU session update response message is sent to the AMF, where the first PDU session update response message includes a first cause value for not being able to process the session to be preempted, and the first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session; the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

2. The method according to claim 1, characterized in that Also includes: When it is determined that preemption of the EBI of the session to be preempted is not allowed, a second PDU session update response message is sent to the AMF, where the second PDU session update response message includes a second cause value, and the second cause value is used to indicate that the AMF failed to preempt the EBI of the session to be preempted.

3. The method according to claim 2, characterized in that The determining that the EBI of the session to be preempted is not allowed to be preempted includes: Determining, according to the service priority of the session to be preempted, an EBI that is not allowed to preempt the session to be preempted; or, According to the local configuration information, it is determined that the EBI of the session to be preempted is not allowed to be preempted.

4. A method for allocating a bearer identifier, characterized in that: include: Receiving an Evolved Packet System Bearer Identifier (EBI) allocation request message sent by a session management network element (SMF), where the EBI allocation request message is sent when the SMF creates a current session for a terminal; When it is determined that EBI preemption is required according to the EBI allocation request message, a protocol data unit PDU session update message is sent to the SMF, where the PDU session update message includes information about the session to be preempted; Receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first cause value for not being able to process the session to be preempted; Determining, based on the first reason value, that the EBI preemption is successful, and allocating the EBI of the session to be preempted to the current session; The first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

5. The method according to claim 4, characterized in that Also includes: Receive a second PDU session update response message sent by the SMF, where the second PDU session update response message is sent when the SMF determines that preemption of the EBI of the session to be preempted is not allowed, and the second PDU session update response message includes a second cause value; According to the second cause value, it is determined that the EBI preemption fails, and an EBI allocation failure message is sent to the SMF.

6. A distribution device carrying a logo, characterized in that: include: A first sending module is configured to send an evolved packet system bearer identifier EBI allocation request message to the access and mobility management network element AMF when creating a current session for the terminal; A receiving module, configured to receive a protocol data unit (PDU) session update message sent by the AMF, where the PDU session update message includes information about the session to be preempted; a determination module, configured to determine that the session to be preempted cannot be processed; The second sending module is used to send a first PDU session update response message to the AMF when the determination module determines that the session to be preempted cannot be processed. The first PDU session update response message includes a first cause value for not being able to process the session to be preempted. The first cause value is used to indicate that the AMF successfully preempts the EBI of the session to be preempted and allocates the EBI to the current session; the first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

7. The device according to claim 6, characterized in that The determining module is further configured to determine that the EBI of the session to be preempted is not allowed to be preempted; the apparatus further comprises: The third sending module is used to send a second PDU session update response message to the AMF when the determination module determines that the EBI of the session to be preempted is not allowed to be preempted, wherein the second PDU session update response message includes a second cause value, and the second cause value is used to indicate that the AMF failed to preempt the EBI of the session to be preempted.

8. The device according to claim 7, characterized in that The determining module is specifically configured to determine, based on the service priority of the session to be preempted, an EBI that is not allowed to preempt the session to be preempted; or, According to the local configuration information, it is determined that the EBI of the session to be preempted is not allowed to be preempted.

9. A distribution device for carrying a logo, characterized in that: include: A first receiving module is configured to receive an Evolved Packet System Bearer Identifier (EBI) allocation request message sent by a session management network element (SMF), where the EBI allocation request message is sent when the SMF creates a current session for a terminal. A sending module, configured to send a protocol data unit (PDU) session update message to the SMF when it is determined that EBI preemption is required according to the EBI allocation request message, wherein the PDU session update message includes information about the session to be preempted; A second receiving module is configured to receive a first PDU session update response message sent by the SMF, where the first PDU session update response message is sent when the SMF determines that the session to be preempted cannot be processed, and the first PDU session update response message includes a first cause value for not being able to process the session to be preempted; a first processing module, configured to determine, based on the first reason value, that the EBI preemption is successful, and allocate the EBI of the session to be preempted to the current session; The first cause value includes that the context of the session to be preempted does not exist or the network element where the session to be preempted is located is abnormal.

10. The device according to claim 9, characterized in that Also includes: A third receiving module is configured to receive a second PDU session update response message sent by the SMF, where the second PDU session update response message is sent when the SMF determines that the EBI of the to-be-preempted session is not allowed to be preempted, and the second PDU session update response message includes a second cause value; The second processing module is used to determine that the EBI preemption fails according to the second reason value, and send an EBI allocation failure message to the SMF.

11. A session management network element, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 are implemented.

12. An access and mobility management network element, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to claim 4 or 5 are implemented.

13. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images