阅读说明：本技术 一种资源释放管理方法及装置 (Resource release management method and device ) 是由 张亚静 于 2020-05-14 设计创作，主要内容包括：本公开涉及通信技术领域,公开了一种资源释放管理方法及装置,解决在UE的注册过程中由于核心网注册流程不同导致等待进行信令交互的时长超时,或者,等待已完成注册的UE发送数据的时长超时,致使基站发起释放为UE配置的资源,增加不必要信令交互的问题。确定当前的工作状态满足资源释放条件时,向核心网发送UE的资源释放请求,并在确定所述工作状态满足超时释放规则时,执行在设定时长内接收到的非资源释放命令,并反馈结果。这样,因核心网注册流程不同或者等待接收数据超时,而发起资源释放流程时,能够响应于核心网发送的非资源释放指令,有效避免出现有数据传输需要的UE注册或接入失败重新接入时导致增加不必要的信令交互的问题。(The disclosure relates to the technical field of communication, and discloses a resource release management method and a resource release management device, which solve the problems that in the registration process of UE, due to different core network registration flows, the time length for waiting for signaling interaction is overtime, or the time length for waiting for the UE which finishes registration to send data is overtime, so that a base station initiates the release of resources configured for the UE, and unnecessary signaling interaction is increased. And when the current working state meets the resource release condition, sending a resource release request of the UE to a core network, and when the working state meets an overtime release rule, executing a non-resource release command received within a set time length, and feeding back a result. Therefore, when the resource release process is initiated due to different core network registration processes or overtime waiting for receiving data, the non-resource release instruction sent by the core network can be responded, and the problem of unnecessary signaling interaction increase caused by UE registration or access failure re-access required by existing data transmission is effectively avoided.)

1. A resource release management method, comprising:

when the base station determines that the current working state meets a preset resource release condition, a resource release request aiming at User Equipment (UE) is sent to a core network;

the base station determines that a non-resource release instruction sent by the core network is received within a set time length, and stops a resource release process when the current working state meets an overtime release rule in the resource release condition;

and the base station executes the non-resource release command and feeds back a corresponding execution result to the core network.

2. The method of claim 1, wherein the base station determining that the current operating state meets a preset resource release condition comprises:

when the base station determines that the current working state meets any one or a combination of the following conditions, the base station determines that the resource release condition is met: the base station waits for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

the time length of the base station waiting for receiving the data sent by the UE reaches a preset second time length;

the base station determines that resources have been allocated for the UE but the UE cannot use the corresponding resources.

3. The method of claim 2, wherein the UE cannot use the corresponding resources, at least comprising any one or a combination of:

the base station determines to disconnect from the UE;

the base station determines that the UE establishes connection with other base stations;

and the base station determines that the interior is abnormal and cannot provide resources for the UE.

4. The method of any one of claims 1-3, further comprising:

after the base station sends a resource release request aiming at User Equipment (UE) to a core network, if a resource release instruction sent by the core network is determined to be received within a set time length, resources allocated to the UE are immediately released; alternatively, the first and second electrodes may be,

after the base station sends a resource release request aiming at User Equipment (UE) to a core network, if any instruction sent by the core network is not received within a set time length, resources allocated to the UE are released.

5. A method according to any of claims 1-3, wherein said determining that the current operating state satisfies a timeout release rule in the resource release condition comprises:

when the base station determines that the current working state meets any one or a combination of the following conditions, determining that a timeout release rule in the resource release condition is met:

the base station waits for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

and the time length of the base station waiting for receiving the data sent by the UE reaches a preset second time length.

6. The method of claim 5, wherein the feeding back the corresponding execution result to the core network comprises:

and the base station judges whether an execution result needs to be fed back to the core network or not according to the non-resource release instruction, if so, the non-resource release instruction is executed, and a corresponding execution result is replied to the core network, otherwise, the non-resource release instruction is directly executed.

7. The method of claim 1, further comprising:

the base station determines that a non-resource release instruction sent by the core network is received within a set time length, and does not execute the non-resource release instruction when the current working state is determined not to meet an overtime release rule in the resource release condition;

and the base station judges whether a processing result needs to be fed back to the core network or not according to the non-resource release instruction, if so, the base station informs the core network that the non-resource release instruction fails to execute, and releases the resources allocated to the UE when the set time length is overtime, otherwise, the base station directly releases the resources allocated to the UE when the set time length is overtime.

8. A resource release management apparatus, comprising at least: a processor and a memory:

wherein the processor is configured to read the program in the memory and perform the following operations:

when the current working state meets the preset resource release condition, sending a resource release request aiming at User Equipment (UE) to a core network;

determining that a non-resource release instruction sent by the core network is received within a set time length, and stopping a resource release process when the current working state meets an overtime release rule in the resource release condition;

and executing the non-resource release command and feeding back a corresponding execution result to the core network.

9. The apparatus of claim 8, wherein the processor, upon determining that the current operating state satisfies a preset resource release condition, is configured to:

when the current working state is judged to meet any one or combination of the following conditions, the resource release condition is determined to be met:

waiting for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

waiting for the duration of receiving the data sent by the UE to reach a preset second duration;

determining that resources have been allocated for the UE but the UE cannot use the corresponding resources.

10. The apparatus of claim 9, wherein when the UE cannot use the corresponding resource, at least any one or a combination of the following is included:

determining to disconnect from the UE;

determining that the UE establishes a connection with other base stations;

and determining that the UE cannot provide resources for the UE due to the internal abnormality.

11. The apparatus of any of claims 8-10, wherein the processor is further to:

after a resource release request aiming at User Equipment (UE) is sent to a core network, if a resource release instruction sent by the core network is determined to be received within a set time length, resources allocated to the UE are immediately released; alternatively, the first and second electrodes may be,

after a resource release request aiming at User Equipment (UE) is sent to a core network, if any instruction sent by the core network is not received within a set time length, resources allocated to the UE are released.

12. The apparatus according to any of claims 8-10, wherein the processor, upon determining that the current operating state satisfies a timeout release rule in the resource release condition, is configured to:

determining that a timeout release rule in the resource release condition is satisfied when the current working state is determined to satisfy any one or a combination of the following:

waiting for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

and waiting for receiving the time length of the data sent by the UE to reach a preset second time length.

13. The apparatus as claimed in claim 12, wherein said processor is configured to, when feeding back the corresponding execution result to said core network:

and judging whether an execution result needs to be fed back to the core network or not according to the non-resource release instruction, if so, executing the non-resource release instruction and replying the corresponding execution result to the core network, otherwise, directly executing the non-resource release instruction.

14. The apparatus of claim 8, wherein the processor is further to:

determining that a non-resource release instruction sent by the core network is received within a set time length, and when the current working state is determined not to meet an overtime release rule in the resource release condition, not executing the non-resource release instruction;

and determining whether a processing result needs to be fed back to the core network or not according to the non-resource release instruction, if so, notifying the core network that the non-resource release instruction fails to execute, and releasing the resources allocated to the UE when the set time length is overtime, otherwise, directly releasing the resources allocated to the UE when the set time length is overtime.

15. A resource release management apparatus, comprising:

the sending unit is used for sending a resource release request aiming at the user equipment UE to the core network when the current working state is determined to meet the preset resource release condition;

the processing unit is used for stopping a resource release process when determining that a non-resource release instruction sent by the core network is received within a set time length and determining that the current working state meets an overtime release rule in the resource release condition;

and the execution unit executes the non-resource release command and feeds back a corresponding execution result to the core network.

16. A storage medium, wherein instructions in the storage medium, when executed by a processor, enable execution of the resource release management method of any one of claims 1 to 7.

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a resource release management method and apparatus.

Background

With the gradual construction of a 5G independent networking architecture, the interaction process among a terminal, a base station and a core network is gradually improved, in general, the base station receives a connection establishment request sent by the terminal through an air interface, configures terminal context information and air interface context information for the terminal, sends a registration request of the terminal to the core network based on identification information of the terminal carried in the connection establishment request, and further establishes a special air interface resource for the terminal after the base station receives an initial context request corresponding to the terminal sent by the core network, so as to ensure signaling and data transmission of the terminal. In addition, in order to ensure effective utilization of resources, the base station determines that the terminal does not send a data transmission request within a certain time, or the base station does not receive an initial context establishment request sent by a core network within a timing duration, or the base station determines that resources do not need to be configured for the terminal, or the base station initiates a UE context release request for a certain terminal (UE) to the core network after failing to provide resources for the terminal due to a self-fault, and the base station releases all resources configured for the terminal after receiving a UE context release command sent by the core network.

In the prior art, referring to fig. 1, a processing procedure after a base station initiates a UE context release request is as follows: the base station sends a UE context release request to a core network, and simultaneously starts a timer, and then stops the timer after determining that a context release command sent by the core network is received, and releases resources configured for the terminal, otherwise, when the context release command sent by the core network is not received, further judges whether other downlink messages sent by the core network are received, if so, feeds back corresponding failure response messages to the core network aiming at the other downlink messages sent by the core network, and then releases the resources configured for the terminal after determining that the timer is overtime, and if not, directly releases the resources configured for the terminal after the timer is overtime.

However, the configuration information of the core network is flexible due to the unbinding of the registration process of the terminal and the session resource configuration process of the protocol data unit in the 5G protocol, and different core networks can be configured with different registration flows, the base station needs to adapt to different core network registration modes, part of the core networks carry the registration receiving information for the terminal in the initial context request message, and part of the core networks directly carry the registration receiving information for the terminal in the downlink direct transmission message, and after the registration is completed, the initial context request is sent, so that the waiting time of the base station is increased, the base station is triggered to send the UE context release request to the core network, the registration failure of the terminal is caused, and the terminal needs to initiate an access flow again; in addition, when the terminal which completes registration has no service data within a period of time, the base station is also triggered to initiate a UE context release request to the core network, and even if the core network concurrently sends a protocol data unit Session Resource PDU Session Resource modification process, the terminal also fails to reply to the core network, and needs to re-establish connection with the terminal, so that unnecessary signaling interaction flows are also added, which causes the terminal to wait for too long time, and seriously affects the user experience.

Disclosure of Invention

The embodiment of the invention provides a resource release management method and a resource release management device, which are used for solving the problems that in the prior art, due to different core network registration flows in the registration process of UE, the time length for waiting for signaling interaction is overtime, or the time length for waiting for UE which finishes registration to send data is overtime, so that a base station initiates release to configure resources for a terminal, and unnecessary signaling interaction is increased.

The embodiment of the invention provides the following specific technical scheme:

a resource release management method, comprising:

when the base station determines that the current working state meets a preset resource release condition, a resource release request aiming at User Equipment (UE) is sent to a core network;

the base station determines that a non-resource release instruction sent by the core network is received within a set time length, and stops a resource release process when the current working state meets an overtime release rule in the resource release condition;

and the base station executes the non-resource release command and feeds back a corresponding execution result to the core network.

Optionally, the determining, by the base station, that the current working state meets the preset resource release condition includes:

when the base station determines that the current working state meets any one or a combination of the following conditions, the base station determines that the resource release condition is met: the base station waits for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

the time length of the base station waiting for receiving the data sent by the UE reaches a preset second time length;

the base station determines that resources have been allocated for the UE but the UE cannot use the corresponding resources.

Optionally, the UE cannot use the corresponding resource, and at least includes any one or a combination of the following:

the base station determines to disconnect from the UE;

the base station determines that the UE establishes connection with other base stations;

and the base station determines that the interior is abnormal and cannot provide resources for the UE.

Optionally, further comprising:

after the base station sends a resource release request aiming at User Equipment (UE) to a core network, if a resource release instruction sent by the core network is determined to be received within a set time length, resources allocated to the UE are immediately released; alternatively, the first and second electrodes may be,

after the base station sends a resource release request aiming at User Equipment (UE) to a core network, if any instruction sent by the core network is not received within a set time length, resources allocated to the UE are released.

Optionally, the determining that the current working state meets the timeout release rule in the resource release condition includes:

when the base station determines that the current working state meets any one or a combination of the following conditions, determining that a timeout release rule in the resource release condition is met:

the base station waits for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

and the time length of the base station waiting for receiving the data sent by the UE reaches a preset second time length.

Optionally, the feeding back the corresponding execution result to the core network includes:

and the base station judges whether an execution result needs to be fed back to the core network or not according to the non-resource release instruction, if so, the non-resource release instruction is executed, and a corresponding execution result is replied to the core network, otherwise, the non-resource release instruction is directly executed.

Optionally, further comprising:

the base station determines that a non-resource release instruction sent by the core network is received within a set time length, and does not execute the non-resource release instruction when the current working state is determined not to meet an overtime release rule in the resource release condition;

and the base station judges whether a processing result needs to be fed back to the core network or not according to the non-resource release instruction, if so, the base station informs the core network that the non-resource release instruction fails to execute, and releases the resources allocated to the UE when the set time length is overtime, otherwise, the base station directly releases the resources allocated to the UE when the set time length is overtime.

A resource release management apparatus, comprising at least: a processor and a memory:

wherein the processor is configured to read the program in the memory and perform the following operations:

when the current working state meets the preset resource release condition, sending a resource release request aiming at User Equipment (UE) to a core network;

determining that a non-resource release instruction sent by the core network is received within a set time length, and stopping a resource release process when the current working state meets an overtime release rule in the resource release condition;

and executing the non-resource release command and feeding back a corresponding execution result to the core network.

Optionally, the processor is configured to determine that the current working state meets a preset resource release condition, and:

when the current working state is judged to meet any one or combination of the following conditions, the resource release condition is determined to be met:

waiting for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

waiting for the duration of receiving the data sent by the UE to reach a preset second duration;

determining that resources have been allocated for the UE but the UE cannot use the corresponding resources.

Optionally, the UE cannot use the corresponding resource, and at least includes any one or a combination of the following:

determining to disconnect from the UE;

determining that the UE establishes a connection with other base stations;

and determining that the UE cannot provide resources for the UE due to the internal abnormality.

Optionally, the processor is further configured to:

after a resource release request aiming at User Equipment (UE) is sent to a core network, if a resource release instruction sent by the core network is determined to be received within a set time length, resources allocated to the UE are immediately released; alternatively, the first and second electrodes may be,

after a resource release request aiming at User Equipment (UE) is sent to a core network, if any instruction sent by the core network is not received within a set time length, resources allocated to the UE are released.

Optionally, when it is determined that the current working state meets a timeout release rule in the resource release condition, the processor is configured to:

determining that a timeout release rule in the resource release condition is satisfied when the current working state is determined to satisfy any one or a combination of the following:

waiting for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

and waiting for receiving the time length of the data sent by the UE to reach a preset second time length.

Optionally, when the corresponding execution result is fed back to the core network, the processor is configured to:

and judging whether an execution result needs to be fed back to the core network or not according to the non-resource release instruction, if so, executing the non-resource release instruction and replying the corresponding execution result to the core network, otherwise, directly executing the non-resource release instruction.

Optionally, the processor is further configured to:

determining that a non-resource release instruction sent by the core network is received within a set time length, and when the current working state is determined not to meet an overtime release rule in the resource release condition, not executing the non-resource release instruction;

and determining whether a processing result needs to be fed back to the core network or not according to the non-resource release instruction, if so, notifying the core network that the non-resource release instruction fails to execute, and releasing the resources allocated to the UE when the set time length is overtime, otherwise, directly releasing the resources allocated to the UE when the set time length is overtime.

A resource release management apparatus, comprising:

the sending unit is used for sending a resource release request aiming at the user equipment UE to the core network when the current working state is determined to meet the preset resource release condition;

the processing unit is used for stopping a resource release process when determining that a non-resource release instruction sent by the core network is received within a set time length and determining that the current working state meets an overtime release rule in the resource release condition;

and the execution unit executes the non-resource release command and feeds back a corresponding execution result to the core network.

A storage medium having instructions that, when executed by a processor, enable performance of any of the above-described resource release management methods.

The invention has the following beneficial effects:

the embodiment of the disclosure provides a resource release management method and a device, wherein a base station sends a resource release request for UE to a core network when determining that a current working state meets a preset resource release condition, then the base station determines that a non-resource release instruction sent by the core network is received within a set time length, and stops a resource release process when determining that the current working state meets an overtime release rule in the resource release condition, and then the base station executes the non-resource release instruction and feeds back a corresponding execution result to the core network.

Therefore, in the registration process of the UE, because the time length for waiting for signaling interaction is overtime or the time length for waiting for the UE which finishes registration to send data is overtime, when a resource release process is initiated, a non-resource release instruction sent by a core network can still be responded, and the problem that unnecessary signaling interaction is increased when the UE which is required by existing data transmission is registered or access is failed and accessed again is effectively avoided.

Drawings

Fig. 1 is a schematic flow chart of resource release in the prior art in the embodiment of the present disclosure;

FIG. 2 is a flow chart illustrating resource release management in an embodiment of the present disclosure;

fig. 3 is a schematic physical structure diagram of a resource release management apparatus according to an embodiment of the present disclosure;

fig. 4 is a schematic logical structure diagram of a resource release management apparatus according to an embodiment of the present disclosure.

Detailed Description

The method and the device aim to solve the problems that in the prior art, due to different core network registration flows, a base station releases resources configured for a terminal, and unnecessary signaling interaction is increased. In the disclosure, when a base station determines that a resource release condition is satisfied, a resource release request for User Equipment (UE) is sent to a core network, then the base station determines that a non-resource release instruction sent by the core network is received within a set time, and when it is determined that a current working state of the base station satisfies a preset timeout release condition, the base station stops starting a resource release process, and then executes the non-resource release instruction, and feeds back a corresponding execution result to the core network.

The disclosure relates to a signaling interaction process among a 5G base station, a UE, and a core network.

In one scenario: in the registration process of a UE initially requesting to access a core network, the UE sends a wireless connection control request to a base station, after the base station allocates air interface resources for the UE, the base station sends initial UE information including the registration request of the UE to the core network, and waits for the core network to return an initial context establishment request carrying a registration acceptance indication, and in the process, if the time length determined by the base station for waiting for the core network to reply the initial context establishment request reaches a preset time length, the base station initiates a resource release request to the core network.

And if the base station determines that the initial context establishment request sent by the core network is received within the set time length, determining whether to stop the resource release process or not based on the current working state, determining whether to continue executing the initial context establishment request sent by the core network and feed back a corresponding execution result to the core network, or directly releasing the resources allocated to the UE when the set time length is overtime.

In another scenario: when the UE finishes registration and the UE, a core network and a base station interact with each other, the base station determines that the time length for waiting for receiving the data of the UE reaches a preset time length or the UE cannot use the allocated resources, and initiates a resource release request to the core network.

And then the base station judges whether a non-resource release instruction sent by the core network is received within a set time length, and simultaneously determines whether to execute the non-resource release instruction and feed back a corresponding execution result to the core network or directly release the resources allocated to the UE when the set time length is overtime based on the current working state.

The following describes, with reference to fig. 2, a resource release management method according to an embodiment of the present disclosure:

step 201: and when the base station determines that the current working state meets the preset resource release condition, the base station sends a resource release request aiming at the UE to the core network.

When the base station determines that the current working state meets any one or a combination of the following conditions, the base station determines that a preset resource release condition is met: the base station waits for receiving a time length of a resource allocation indication sent by a core network to reach a preset first time length, or the base station waits for receiving a time length of data sent by the UE to reach a preset second time length, or the base station determines that resources are allocated aiming at the UE, but the UE cannot use corresponding resources.

Specifically, the following description is made in the context in which the base station initiates a resource release request based on the current operating state during the UE registration process, and in the context in which the base station initiates a resource release request based on the current operating state after the UE registration is completed:

scenario one, a resource release request is initiated in the UE registration process.

The base station establishes air interface signaling transmission for the UE based on a wireless resource connection establishment request sent by the UE, receives wireless resource establishment completion information which is sent by the UE and carries Non Access Stratum (NAS) information, sends initial UE information carrying the NAS information to a core network, and waits for receiving an initial context establishment request sent by the core network to complete a registration process of the UE.

Further, the base station determines that a time length for waiting for receiving the initial context establishment request reaches a preset first time length, or determines that resources are allocated to the UE, but the UE cannot use corresponding resources, and determines that a current working state meets a preset resource release condition, and the base station sends a UE context release request for the UE to a core network.

And a second scenario, initiating a resource release request in the interactive process after the UE registration is completed.

After the UE is registered, the base station detects a survival state of the UE by using a survival detection mechanism, specifically, after receiving interactive data sent by the UE, starts a survival detection timer, and sets a timing duration of the survival detection timer to a preset second duration, the base station determines that a duration of waiting for receiving data sent by the UE reaches the preset second duration, or when the base station determines that resources are allocated for the UE but the UE cannot use corresponding resources, determines that a current working state meets a preset resource release condition, and the base station sends a UE context release request for the UE to the core network.

It should be noted that the base station determines that resources have been allocated for the UE, but the UE cannot use the resources for response, and the corresponding scenario includes, but is not limited to, the base station determining to disconnect from the UE; the base station determines that the UE establishes connection with other base stations; and the base station determines that the interior is abnormal and cannot provide resources for the UE. Specifically, when the base station bottom layer detects that the UE is lost and cannot establish communication connection, it is determined that the UE is disconnected.

Therefore, the time for the base station to wait for receiving the information is limited by setting the first time length and the second time length, the excessive time occupied by the configuration of the UE is avoided, the resource release process is timely initiated by detecting the connection state and the internal running state of the UE, the resource release request is sent to the core network, and the resource waste caused by the fact that the invalid UE occupies the resources is avoided.

Step 202: is the set duration set by the base station time out? If so, go to step 203, otherwise, go to step 204.

After the base station sends a resource release request to the core network, timing is started based on a set time length, and further, the base station judges whether the time length waiting for receiving the core network reply instruction reaches the set time length, if so, the operation defined in step 203 is executed, otherwise, the operation defined in step 204 is executed, wherein the set time length is preset by the base station based on actual configuration.

For example, continuing the description of scenario one and scenario two in step 201, after the base station sends the UE context release request to the core network, the base station starts a timer according to a set duration, and determines whether to receive an instruction replied by the core network before the timer expires.

In this way, the set duration is used as a condition for defining whether to immediately release the resources allocated to the UE, on one hand, the set duration is the command reserve time returned by the receiving core network, and on the other hand, the waiting time is prevented from being too long.

Step 203: and the base station immediately releases the resources allocated to the UE.

And the base station immediately releases the resources allocated to the UE when determining that the time length for waiting for receiving the core network reply instruction reaches the set time length.

Specifically, the base station determines that any instruction sent by a core network is not received within the set time length, or the base station determines that a resource release instruction sent by the core network is received within the set time length, or the base station determines that a non-resource release instruction sent by the core network is received within the preset time length, but when the working state of the base station determines whether a preset resource release condition is met does not meet an overtime resource release rule in the resource release condition, the base station immediately releases the resource allocated to the UE. Wherein, when the base station determines that the current working state meets any one or a combination of the following conditions, the base station determines that a timeout release rule in the resource release condition is met: the base station waits for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length; and the time length of the base station waiting for receiving the data sent by the UE reaches a preset second time length.

Step 204: the base station determines whether a resource release instruction sent by the core network is received, if so, step 203 is executed, otherwise, step 205 is executed.

Specifically, the base station determines whether a resource release instruction sent by the core network is received within a set time length of waiting for receiving a core network reply instruction, and if so, directly executes step 203, and directly releases the resource configured for the UE without waiting for the set time length to be overtime. If the resource release instruction sent by the core network is not received, the operation defined in step 205 is further executed.

For example, continuing with the example in step 202, when the base station determines that the UE context release instruction sent by the core network is received within the set time duration, that is, before the timer expires, the base station directly stops the timer and releases the resource configured for the UE.

Step 205: the base station determines whether a non-resource release instruction sent by the core network is received, if yes, step 206 is executed, otherwise, step 202 is executed.

When the base station determines that the resource release instruction sent by the core network is not received within the set time length, the base station further determines whether a non-resource release instruction sent by the core network is received, if so, the operation defined in step 206 is executed, the current working state is further determined, otherwise, the operation defined in step 202 is returned to, and the resource allocated to the UE is directly released after the set time length is overtime.

Step 206: the base station determines whether the current working state meets an overtime release rule in the resource release condition, if so, step 207 is executed, otherwise, step 208 is executed.

After the base station determines that a non-resource release instruction sent by the core network is received within a set time length, further, the base station determines whether the working state when the resource release condition is met and whether an overtime release rule in the resource release condition is met, if yes, the operation defined in step 207 is executed, otherwise, the operation defined in step 208 is executed. Specifically, when the base station determines that the current working state meets any one or a combination of the following conditions, the base station determines that the timeout release rule in the resource release conditions is met: the base station waits for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length; and the time length of the base station waiting for receiving the data sent by the UE reaches a preset second time length.

Long.

For example, in the UE registration process, due to different core network registration flows, when a time length for a base station to wait for receiving an initial context setup request sent by a core network reaches a preset first time length, the base station sends a UE context release request for the UE to the core network, starts a timer, sets a timing time length of the timer as a set time length, and further, when it is determined that the initial context setup request sent by the core network or other non-resource release instructions are received within the set time length, stops a resource release flow.

Therefore, considering that the base station may have the situation of waiting for the resource release request initiated overtime due to the difference of different core network access flows, the base station effectively avoids releasing the resource of the UE required by service processing by further judging whether the working state meeting the resource release condition further meets the overtime release rule in the resource release condition, on one hand, the UE is prevented from initiating the registration flow again to influence the user perception, on the other hand, the unnecessary signaling process is prevented from being added, and meanwhile, the time delay of the voice service is prevented from being too long.

Step 207: and the base station stops the resource release process, executes the non-resource release instruction and feeds back a corresponding execution result to the core network.

The method comprises the steps that a base station determines that a non-resource release instruction sent by a core network is received within a set time length, and when the current working state of the base station meets a preset overtime release condition, the base station stops a release process, executes a non-resource release command and feeds back a corresponding execution result to the core network.

For example, continuing with the example of step 206 for explanation, when the base station receives the initial context setup request message sent by the core network, the base station sets up security configuration of an Access Stratum (AS) for the UE, configures air interface wireless resources for the UE, and further replies an initial context setup response message for the core network to complete registration and service request flow of the UE; when the base station receives a Protocol Data Unit Session Resource (PDU Session Resource) establishment request message sent by the core network, the base station configures the UE through an air interface reconfiguration message, completes the configuration of a Data Radio Bearer (DRB) of the air interface of the UE, and replies a PDU Session Resource establishment request response to the core network; and when the base station receives a PUD Session Resource modification request message sent by the core network, the base station needs to perform internal updating based on actual configuration, or configures the UE to complete DRB modification of the air interface of the UE.

When the base station receives the UE context modification request message sent by the core network, the base station determines to perform internal update or informs the UE to perform update based on actual configuration requirements, and replies a UE context modification response message for the core network; and when the base station receives the downlink direct transmission message sent by the core network, the base station directly forwards the downlink direct transmission message to the UE without replying the message for the core network.

Step 208: the base station does not execute the non-resource release instruction.

The base station determines that a non-resource release command sent by a core network is received within a set time length, but the base station judges that the working state of a resource release condition is met, and when an overtime release rule in the resource release condition is not met, the base station determines that the non-resource release command sent by the core network is not executed.

Specifically, when the base station determines that the current working state meets any one or a combination of the following conditions, it determines that a timeout release rule in the resource release condition is met: the base station waits for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length; and the time length of the base station waiting for receiving the data sent by the UE reaches a preset second time length.

Step 209: and the base station judges whether a processing result needs to be fed back to the core network or not according to the non-resource release instruction, if so, the step 210 is executed, and if not, the step 202 is executed.

After determining that the non-resource release instruction sent by the core network is not executed, the base station further determines whether to feed back a processing result to the core network according to the non-resource release instruction, and if so, executes the operation defined in step 210. Otherwise, step 202 is directly executed, and the base station immediately releases the resources allocated to the UE when the set duration expires.

For example, after receiving the downlink direct transmission information sent by the core network, the base station directly discards the downlink direct transmission information without replying a message to the core network, and releases the resource allocated to the UE when determining that the set time duration is exceeded.

Step 210: and the base station informs the core network that the execution of the non-resource release instruction fails.

And the base station informs the core network that the execution of the non-resource release instruction fails when determining that a processing result needs to be fed back to the core network based on the non-resource release instruction received from the core network, and immediately releases the resources allocated to the UE when determining that the set time duration is over.

For example, if the base station receives a context establishment request message sent by a core network, the base station notifies the core network of information of initial context establishment failure, and the UE registration and service request process fails; the base station receives PDU Session Resource establishment/modification request information sent by the core network, and then notifies the core network of the failure message of the PDU Session Resource establishment/modification request; and the base station receives the UE context modification request message sent by the core network and informs the core network of the information of UE context modification failure.

Based on the same inventive concept, referring to fig. 3, the present disclosure provides a resource release management apparatus, at least including: a processor 301 and a memory 302, which,

wherein, the processor 301 is configured to read the program in the memory 301, and execute the following operations:

when the current working state meets the preset resource release condition, sending a resource release request aiming at User Equipment (UE) to a core network;

determining that a non-resource release instruction sent by the core network is received within a set time length, and stopping a resource release process when the current working state meets an overtime release rule in the resource release condition;

and executing the non-resource release command and feeding back a corresponding execution result to the core network.

Optionally, the processor is configured to determine that the current working state meets a preset resource release condition, and:

when the current working state is judged to meet any one or combination of the following conditions, the resource release condition is determined to be met:

waiting for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

waiting for the duration of receiving the data sent by the UE to reach a preset second duration;

determining that resources have been allocated for the UE but the UE cannot use the corresponding resources.

Optionally, the UE cannot use the corresponding resource, and at least includes any one or a combination of the following:

determining to disconnect from the UE;

determining that the UE establishes a connection with other base stations;

and determining that the UE cannot provide resources for the UE due to the internal abnormality.

Optionally, the processor is further configured to:

after a resource release request aiming at User Equipment (UE) is sent to a core network, if a resource release instruction sent by the core network is determined to be received within a set time length, resources allocated to the UE are immediately released; alternatively, the first and second electrodes may be,

after a resource release request aiming at User Equipment (UE) is sent to a core network, if any instruction sent by the core network is not received within a set time length, resources allocated to the UE are released.

Optionally, when it is determined that the current working state meets a timeout release rule in the resource release condition, the processor is configured to:

determining that a timeout release rule in the resource release condition is satisfied when the current working state is determined to satisfy any one or a combination of the following:

waiting for receiving the time length of the resource allocation indication sent by the core network to reach a preset first time length;

and waiting for receiving the time length of the data sent by the UE to reach a preset second time length.

Optionally, when the corresponding execution result is fed back to the core network, the processor is configured to:

and judging whether an execution result needs to be fed back to the core network or not according to the non-resource release instruction, if so, executing the non-resource release instruction and replying the corresponding execution result to the core network, otherwise, directly executing the non-resource release instruction.

Optionally, the processor is further configured to:

determining that a non-resource release instruction sent by the core network is received within a set time length, and when the current working state is determined not to meet an overtime release rule in the resource release condition, not executing the non-resource release instruction;

and determining whether a processing result needs to be fed back to the core network or not according to the non-resource release instruction, if so, notifying the core network that the non-resource release instruction fails to execute, and releasing the resources allocated to the UE when the set time length is overtime, otherwise, directly releasing the resources allocated to the UE when the set time length is overtime.

Based on the same inventive concept, referring to fig. 4, an embodiment of the present disclosure provides a resource release management apparatus, which at least includes: transmission unit 401, processing unit 402, and execution unit 403:

a sending unit 401, configured to send a resource release request for a UE to a core network when determining that a current working state meets a preset resource release condition;

the processing unit 402 is configured to determine that a non-resource release instruction sent by the core network is received within a set time length, and stop a resource release process when the current working state meets an overtime release rule in the resource release condition;

the execution unit 403 executes the non-resource release command, and feeds back a corresponding execution result to the core network.

Based on the same inventive concept, the disclosed embodiments provide a storage medium, and when instructions in the storage medium are executed by an electronic device, the electronic device is enabled to execute any one of the above methods.

In summary, in the embodiment of the present disclosure, when determining that a current working state meets a preset resource release condition, a base station sends a resource release request for a user equipment UE to a core network, then the base station determines that a non-resource release instruction sent by the core network is received within a set time length, and when determining that the current working state meets an timeout release rule in the resource release condition, stops a resource release process, and then the base station executes the non-resource release command and feeds back a corresponding execution result to the core network.

Therefore, in the registration process of the UE, because the time length for waiting for signaling interaction is overtime or the time length for waiting for the UE which finishes registration to send data is overtime, when a resource release process is initiated, a non-resource release instruction sent by a core network can still be responded, and the problem that unnecessary signaling interaction is increased when the UE which is required by existing data transmission is registered or access is failed and accessed again is effectively avoided. As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.