CN113677041B - Resource release management method and device - Google Patents
Resource release management method and device Download PDFInfo
- Publication number
- CN113677041B CN113677041B CN202010406374.9A CN202010406374A CN113677041B CN 113677041 B CN113677041 B CN 113677041B CN 202010406374 A CN202010406374 A CN 202010406374A CN 113677041 B CN113677041 B CN 113677041B
- Authority
- CN
- China
- Prior art keywords
- resource release
- core network
- base station
- resource
- duration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 27
- 238000000034 method Methods 0.000 claims abstract description 46
- 230000004048 modification Effects 0.000 claims description 20
- 238000012986 modification Methods 0.000 claims description 20
- 238000013468 resource allocation Methods 0.000 claims description 16
- 230000005856 abnormality Effects 0.000 claims description 6
- 230000009365 direct transmission Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 abstract description 30
- 230000003993 interaction Effects 0.000 abstract description 15
- 230000011664 signaling Effects 0.000 abstract description 15
- 230000005540 biological transmission Effects 0.000 abstract description 7
- 238000004891 communication Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000004083 survival effect Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to the technical field of communication, discloses a resource release management method and a resource release management device, and solves the problems that in the registration process of UE, due to different core network registration processes, the time waiting for signaling interaction is overtime, or the time waiting for the UE which completes registration to send data is overtime, so that a base station initiates release of resources configured for the UE, and unnecessary signaling interaction is increased. And when the current working state is determined to meet the resource release condition, sending a resource release request of the UE to the core network, executing a non-resource release command received in a set time length when the working state is determined to meet the overtime release rule, and feeding back a result. Therefore, when the resource release process is initiated due to different registration processes of the core network or overtime of waiting for receiving data, the non-resource release instruction sent by the core network can be responded, and the problem that unnecessary signaling interaction is increased when UE registration or access failure re-access required by data transmission occurs is effectively avoided.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for resource release management.
Background
With the gradual construction of the 5G independent networking architecture, the interaction process among the terminal, the base station and the core network is gradually perfected, in general, after receiving a connection establishment request sent by the terminal through an air interface, the base station 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 the identification information of the terminal carried in the connection establishment request, and after receiving an initial context request corresponding to the terminal sent by the core network, the base station further establishes special air interface resources for the terminal, thereby ensuring signaling and data transmission of the terminal. In addition, in order to ensure effective utilization of resources, the base station 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 the core network within a certain time period, or the base station determines that resources are not required to be configured for the terminal, or the base station can not provide resources for the terminal due to self failure, the base station initiates a UE context release request for a certain terminal (UE, userEquipment) to the core network, 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, the processing procedure after the base station initiates the UE context release request is: and the base station sends a UE context release request to the core network, and simultaneously starts a timer, further 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 yes, the corresponding failure response message is fed back to the core network aiming at the other downlink messages sent by the core network, further releases the resources configured for the terminal after determining that the timer is overtime, and directly releases the resources configured for the terminal after the timer is overtime if the other downlink messages sent by the core network are not received.
However, because the registration process of the terminal and the session resource allocation process of the protocol data unit are not bound in the 5G protocol, the configuration information of the core network has flexibility, and because different core networks can be configured with different registration processes, the base station needs to adapt to different core network registration modes, part of the core networks carry registration receiving information for the terminal in an initial context request message, and part of the core networks directly carry registration receiving information for the terminal in a downlink direct transmission message, and after the registration is completed, the initial context request is sent again, thus, the waiting time of the base station is increased, and the base station is triggered to send a UE context release request to the core network, so that the terminal registration is failed, and the terminal is required to restart the access process; in addition, when no service data exists in the registered terminal for a period of time, the base station is triggered to initiate a UE context release request to the core network, and even if the core network is concurrent with the protocol data unit session resource PDU Session Resource modification process, the terminal also replies failure to the core network and needs to re-establish connection with the terminal, so that an unnecessary signaling interaction flow is increased, the waiting time of the terminal is too long, and the use experience of a user is seriously affected.
Disclosure of Invention
The embodiment of the invention provides a resource release management method and device, which are used for solving the problems that in the prior art, due to different core network registration processes, the time waiting for signaling interaction is overtime, or the time waiting for the UE which completes 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 specific technical scheme provided by the embodiment of the invention is as follows:
A resource release management method, comprising:
When the base station determines that the current working state meets the preset resource release condition, the base station sends a resource release request for User Equipment (UE) 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 flow when the current working state is determined to meet a timeout 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 base station determines that the current working state meets a preset resource release condition, including:
When the base station judges that the current working state meets any one or combination of the following conditions, the base station determines that the resource release condition is met: the base station waits for the duration of receiving the resource allocation indication sent by the core network to reach the preset first duration;
The base station waits for the duration of receiving the data sent by the UE to reach a preset second duration;
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 resources, which 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;
The base station determines that an abnormality occurs inside and cannot provide resources for the UE.
Optionally, the method further comprises:
after the base station sends a resource release request for User Equipment (UE) to a core network, if the resource release instruction sent by the core network is received within a set time period, immediately releasing the resources allocated for the UE; or alternatively
After the base station sends a resource release request for User Equipment (UE) to a core network, if any instruction sent by the core network is not received within a set duration, the resources allocated for the UE are released.
Optionally, the determining that the current working state meets a timeout release rule in the resource release condition includes:
And when the base station determines that the current working state meets any one or combination of the following, determining that a timeout release rule in the resource release condition is met:
the base station waits for the duration of receiving the resource allocation indication sent by the core network to reach the preset first duration;
and the base station waits for the duration of receiving the data sent by the UE to reach the preset second duration.
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 according to the non-resource release instruction, if so, the base station executes the non-resource release instruction and replies a corresponding execution result to the core network, otherwise, the base station directly executes the non-resource release instruction.
Optionally, the method further comprises:
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 to not meet a timeout 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 according to the non-resource release instruction, if so, the base station informs the core network that the non-resource release instruction fails to be executed and releases the resources allocated to the UE when the set time length is overtime, otherwise, directly releases the resources allocated to the UE when the set time length is overtime.
A resource release management device, comprising at least: a processor and a memory:
the processor is configured to read the program in the memory and perform the following operations:
When the current working state is determined to meet the preset resource release condition, a resource release request aiming at User Equipment (UE) is sent 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 flow when the current working state is determined to meet a timeout 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 determining that the current working state meets a preset resource release condition, and the processor is configured to:
when the current working state is judged to meet any one or combination of the following conditions, determining that the resource release condition is met:
Waiting for receiving a duration of a resource allocation instruction sent by a core network to reach a preset first duration;
Waiting for the duration of receiving the data sent by the UE to reach a preset second duration;
it is determined that resources have been allocated for the UE, but the UE cannot use the corresponding resources.
Optionally, the UE cannot use the corresponding resources, which at least includes any one or a combination of the following:
Determining to disconnect from the UE;
determining that the UE establishes connection with other base stations;
And determining that abnormality occurs inside, and failing to provide resources for the UE.
Optionally, the processor is further configured to:
After a resource release request for User Equipment (UE) is sent to a core network, if a resource release instruction sent by the core network is received within a set time period, immediately releasing resources allocated for the UE; or alternatively
After a resource release request for User Equipment (UE) is sent to a core network, if any instruction sent by the core network is not received within a set duration, the resources allocated for the UE are released.
Optionally, when the determining that the current working state meets a timeout release rule in the resource release condition, the processor is configured to:
when the current working state is determined to meet any one or combination of the following, determining to meet a timeout release rule in the resource release condition:
Waiting for receiving a duration of a resource allocation instruction sent by a core network to reach a preset first duration;
Waiting for the duration of receiving the data sent by the UE to reach a preset second duration.
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 according to the non-resource release instruction, if so, executing the non-resource release instruction, and replying a 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 not executing the non-resource release instruction when the current working state is determined to not meet a timeout release rule in the resource release condition;
And determining whether a processing result needs to be fed back to the core network according to the non-resource release instruction, if so, notifying the core network that the non-resource release instruction fails to be executed, 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:
a transmitting unit for transmitting a resource release request for the user equipment UE to the core network when determining that the current working state meets a preset resource release condition;
The processing unit is used for determining that a non-resource release instruction sent by the core network is received within a set time period, and stopping a resource release flow when the current working state is determined to meet a timeout release rule in the resource release condition;
and the execution unit is used for executing the non-resource release command and feeding back a corresponding execution result to the core network.
A storage medium, which when executed by a processor, enables execution of the resource release management method of any one of the above.
The invention has the following beneficial effects:
the embodiment of the disclosure provides a resource release management method and device, when a base station determines that a current working state meets a preset resource release condition, a base station sends a resource release request for 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 period, and when the current working state meets a timeout release rule in the resource release condition, the base station stops a resource release process, further the base station executes the non-resource release instruction, and feeds back a corresponding execution result to the core network.
In this way, the time length of waiting for signaling interaction is overtime in the registration process of the UE, or the time length of waiting for the UE which completes registration to send data is overtime, so that when the resource release process is initiated, the non-resource release instruction sent by the core network can be responded, and the problem that unnecessary signaling interaction is increased when the UE registration or access failure re-access required by data transmission occurs is effectively avoided.
Drawings
Fig. 1 is a schematic flow chart of resource release in the prior art in an embodiment of the disclosure;
FIG. 2 is a flow chart of resource release management in an embodiment of the disclosure;
fig. 3 is a schematic physical structure diagram of a resource release management device according to an embodiment of the disclosure;
fig. 4 is a schematic logic structure diagram of a resource release management device according to an embodiment of the disclosure.
Detailed Description
In order to solve the problem that in the prior art, the base station releases resources configured for the terminal due to different core network registration processes, and unnecessary signaling interaction is increased. In the disclosure, when a base station determines that a resource release condition is met, 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 duration, and when the current working state of the base station is determined to meet a preset timeout release condition, the base station stops starting a resource release process, and further, the base station executes the non-resource release instruction and feeds back a corresponding execution result to the core network.
In the present disclosure, a signaling interaction procedure between a 5G base station, a UE, and a core network is involved.
Under a scene: in the process of initially requesting the UE to access the registration of the 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 comprising the registration request of the UE to the core network, waits for the core network to return an initial context establishment request carrying a registration acceptance instruction, and in the process, if the duration of waiting for the core network to reply the initial context establishment request, which is determined by the base station, reaches a preset duration, the base station initiates a resource release request to the core network.
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 flow based on the current working state, determining whether to continue to execute the initial context establishment request sent by the core network, feeding back a corresponding execution result to the core network, or directly releasing the resources allocated to the UE when the set time length is over.
Another scenario is: and when the UE finishes registration, and the base station determines that the time length for waiting to receive the data of the UE reaches the preset time length or determines that the UE cannot use the allocated resources, initiating a resource release request to the core network in the process of interaction between the UE, the core network and the base station.
And the base station further judges whether a non-resource release instruction sent by the core network is received within a set time length, and meanwhile, based on the current working state, determines whether to execute the non-resource release instruction, feeds back a corresponding execution result to the core network, or directly releases resources allocated to the UE when the set time length is over.
The resource release management method according to the embodiment of the present disclosure is described below with reference to fig. 2:
Step 201: and when the base station determines that the current working state meets the preset resource release condition, sending 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 combination of the following, the base station determines that a preset resource release condition is met: the base station waits for a duration of receiving the resource allocation indication sent by the core network to reach a preset first duration, or the base station waits for a duration of receiving the data sent by the UE to reach a preset second duration, or the base station determines that resources are allocated to the UE, but the UE cannot use the corresponding resources.
Specifically, in the following description, the base station initiates a scenario of a resource release request based on a current working state in the UE registration process, and after the UE registration is completed, the base station initiates a scenario of a resource release request based on the current working state:
and in the first scenario, initiating a resource release request in the UE registration process.
The base station establishes air interface signaling transmission for the UE based on a radio resource connection establishment request sent by the UE, receives radio resource establishment completion information carrying (Non Access Stratum, NAS) non-access stratum information sent by the UE, further sends initial UE information carrying 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 the duration of waiting to receive the initial context establishment request reaches a preset first duration, or the base station determines that resources are allocated to the UE, but when the UE cannot use the corresponding resources, the base station determines that the current working state meets a preset resource release condition, and the base station sends a UE context release request to a core network for the UE.
And secondly, initiating a resource release request in the interaction process after the UE registration is completed.
After the UE registration is completed, the base station adopts a survival detection mechanism to detect the survival state of the UE, specifically, after receiving the interactive data sent by the UE, a survival detection timer is started, the timing duration of the survival detection timer is set to be a preset second duration, when the base station determines that the duration of waiting to receive the data sent by the UE reaches the preset second duration, or the base station determines that resources are allocated to the UE, but when the UE cannot use the corresponding resources, the base station determines that the current working state meets the 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 to the UE, but the UE cannot use the responsive resources, 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; the base station determines that an abnormality occurs inside 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, the base station bottom layer determines to disconnect the UE.
In this way, by setting the first duration and the second duration, the time for the base station to wait for receiving the information is limited, excessive time occupied by configuration of one UE is avoided, and by detecting the connection state of the UE and the internal running state, a resource release process is initiated in time, a resource release request is sent to the core network, and resource waste caused by the occupation of resources by invalid UE is avoided.
Step 202: is the set time period set by the base station timed out? If yes, go to step 203, otherwise, go to step 204.
After the base station sends the resource release request to the core network, timing is started based on the set time length, further, the base station judges whether the time length waiting to receive the core network reply instruction reaches the set time length, if yes, the operation defined in the step 203 is executed, otherwise, the operation defined in the step 204 is executed, wherein the set time length is preset by the base station based on actual configuration requirements.
For example, continuing to describe scenario one and scenario two in step 201, after the base station sends a UE context release request to the core network, a timer is started according to a set duration, and it is determined whether an instruction replied by the core network is received before the timer times out.
In this way, the set duration is used as a condition for defining whether to release the resources allocated to the UE immediately, on the one hand, the instruction retention time returned by the receiving core network is avoided, on the other hand, the waiting time is avoided being too long.
Step 203: the base station immediately releases the resources allocated for the UE.
And when the base station determines that the time length for waiting to receive the core network reply instruction reaches the set time length, immediately releasing the resources allocated for the UE.
Specifically, the base station determines that any instruction sent by the core network is not received within the set duration, or the base station determines that a resource release instruction sent by the core network is received within the set duration, or the base station determines that a non-resource release instruction sent by the core network is received within the preset duration, but when the working state of the base station when judging whether the preset resource release condition is met or not does not meet the overtime resource release rule in the resource release condition, the base station immediately releases the resource allocated to the UE. When the base station determines that the current working state meets any one or combination of the following, determining that a timeout release rule in the resource release condition is met: the base station waits for the duration of receiving the resource allocation indication sent by the core network to reach the preset first duration; and the base station waits for the duration of receiving the data sent by the UE to reach the preset second duration.
Step 204: the base station determines whether a resource release instruction sent by the core network is received, if yes, 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 duration waiting for receiving the core network reply instruction, if so, directly executes step 203, does not wait for the timeout of the set duration, and directly releases resources configured for the UE. 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 duration, that is, before the timer expires, the base station directly stops the timer and releases the resources 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 duration, further, the base station judges whether a non-resource release instruction sent by the core network is received, if yes, the operation defined in step 206 is executed, further, the current working state is judged, otherwise, the operation defined in step 202 is executed in a returning mode, and after the set duration is overtime, the resources allocated to the UE are directly released.
Step 206: the base station determines whether the current working state meets the timeout release rule in the resource release condition, if yes, step 207 is executed, otherwise step 208 is executed.
After the base station determines that the non-resource release instruction sent by the core network is received within the set duration, further, the base station determines whether the working state when the resource release condition is satisfied, and if yes, the operation defined in step 207 is executed, otherwise, the operation defined in step 208 is executed. The time-out release rule is included in a resource release condition, specifically, when the base station determines that the current working state meets any one or a combination of the following, the base station determines that the time-out release rule in the resource release condition is met: the base station waits for the duration of receiving the resource allocation indication sent by the core network to reach the preset first duration; and the base station waits for the duration of receiving the data sent by the UE to reach the preset second duration.
For example, in the process of UE registration, due to different core network registration procedures, when the base station waits for the duration of receiving the initial context establishment request sent by the core network to reach the preset first duration, the base station sends a UE context release request for the UE to the core network, starts a timer, sets the timing duration of the timer to be the set duration, and further determines that the resource release procedure is stopped when the initial context establishment request sent by the core network or other non-resource release instructions are received in the set duration.
In this way, considering that the base station may wait for the time-out initiated resource release request due to the different access flows of different core networks, by further judging whether the working state meeting the resource release condition further meets the time-out release rule in the resource release condition, the base station effectively avoids releasing the resources of the UE required by service processing, on one hand, avoids the UE from reinitiating the registration flow, influencing the user perception, on the other hand, avoids adding unnecessary signaling process, and meanwhile, avoids causing too long time delay of voice service.
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 base station determines whether an execution result needs to be fed back to the core network according to the non-resource release instruction, if yes, the base station executes the non-resource release instruction and replies a corresponding execution result to the core network, otherwise, the base station directly executes the non-resource release instruction.
For example, continuing with the example of step 206, when the base station receives the initial context establishment request message sent by the core network, the base station establishes a security configuration of an access layer (Acess Stratum, AS) for the UE, configures air interface radio resources for the UE, and replies an initial context establishment response message for the core network, thereby completing registration and service request flows of the UE; when the base station receives a protocol data unit session resource (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 (user Data Radio Bearer, DRB) of an air interface of the UE, and replies PDU Session Resource an establishment request response to the core network; when receiving PUD Session Resource modification request information sent by the core network, the base station performs internal update based on actual configuration requirements or configures the UE to complete DRB modification of an air interface of the UE.
When the base station receives the UE context modification request message sent by the core network, based on the actual configuration requirement, determining to update internally or inform the UE to update, and replying a UE context modification response message for the core network; when the base station receives the downlink direct transmission message sent by the core network, the downlink direct transmission message is directly forwarded to the UE, and the message is not required to be replied 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 the core network is received within a set time length, but the base station judges the working state meeting the resource release condition, and when the 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 combination of the following, determining that a timeout release rule in the resource release condition is met: the base station waits for the duration of receiving the resource allocation indication sent by the core network to reach the preset first duration; and the base station waits for the duration of receiving the data sent by the UE to reach the preset second duration.
Step 209: and the base station judges whether a processing result needs to be fed back to the core network according to the non-resource release instruction, if yes, 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 the processing result needs to be fed back to the core network according to the non-resource release instruction, and if yes, executes the operation defined in step 210. Otherwise, directly executing step 202, where the base station immediately releases the resources allocated to the UE when the set time length expires.
For example, after receiving the downlink direct-current information sent by the core network, the base station directly discards the downlink direct-current information without replying a message to the core network, and releases the resources allocated to the UE when the set time period is determined to be over.
Step 210: and the base station informs the core network of the failure of executing the non-resource release instruction.
And the base station informs the core network of failure in execution of the non-resource release instruction when determining that the 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 length is over.
For example, when receiving a context establishment request message sent by a core network, a base station informs the core network of information about initial context establishment failure, and a UE registration and service request procedure fails; the base station receives PDU Session Resource setup/modification request information sent by the core network, and notifies the core network PDU Session Resource of a failure message of the setup/modification request; and the base station informs the core network of the information of the UE context modification failure after receiving the UE context modification request message sent by the core network.
Based on the same inventive concept, referring to fig. 3, the present disclosure provides a resource release management device, at least including: a processor 301 and a memory 302,
Wherein the processor 301 is configured to read the program in the memory 301, and perform the following operations:
When the current working state is determined to meet the preset resource release condition, a resource release request aiming at User Equipment (UE) is sent 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 flow when the current working state is determined to meet a timeout 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 determining that the current working state meets a preset resource release condition, and the processor is configured to:
when the current working state is judged to meet any one or combination of the following conditions, determining that the resource release condition is met:
Waiting for receiving a duration of a resource allocation instruction sent by a core network to reach a preset first duration;
Waiting for the duration of receiving the data sent by the UE to reach a preset second duration;
it is determined that resources have been allocated for the UE, but the UE cannot use the corresponding resources.
Optionally, the UE cannot use the corresponding resources, which at least includes any one or a combination of the following:
Determining to disconnect from the UE;
determining that the UE establishes connection with other base stations;
And determining that abnormality occurs inside, and failing to provide resources for the UE.
Optionally, the processor is further configured to:
After a resource release request for User Equipment (UE) is sent to a core network, if a resource release instruction sent by the core network is received within a set time period, immediately releasing resources allocated for the UE; or alternatively
After a resource release request for User Equipment (UE) is sent to a core network, if any instruction sent by the core network is not received within a set duration, the resources allocated for the UE are released.
Optionally, when the determining that the current working state meets a timeout release rule in the resource release condition, the processor is configured to:
when the current working state is determined to meet any one or combination of the following, determining to meet a timeout release rule in the resource release condition:
Waiting for receiving a duration of a resource allocation instruction sent by a core network to reach a preset first duration;
Waiting for the duration of receiving the data sent by the UE to reach a preset second duration.
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 according to the non-resource release instruction, if so, executing the non-resource release instruction, and replying a 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 not executing the non-resource release instruction when the current working state is determined to not meet a timeout release rule in the resource release condition;
And determining whether a processing result needs to be fed back to the core network according to the non-resource release instruction, if so, notifying the core network that the non-resource release instruction fails to be executed, 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 device, which at least includes: transmission section 401, processing section 402, and execution section 403:
A sending unit 401, configured to send a resource release request for the UE to the core network when determining that the current working state meets a preset resource release condition;
A processing unit 402, configured to determine that a non-resource release instruction sent by the core network is received within a set duration, and stop a resource release flow when it is determined that the current working state meets a timeout release rule in the resource release condition;
And 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, a storage medium is proposed in an embodiment of the disclosure, which when instructions in the storage medium are executed by an electronic device, enables the electronic device to perform any one of the methods described above.
In summary, in the embodiment of the present disclosure, when determining that the current working state meets the preset resource release condition, the base station sends a resource release request for the UE to the core network, then the base station determines that a non-resource release instruction sent by the core network is received within a set duration, and when determining that the current working state meets the timeout release rule in the resource release condition, stops the resource release process, and then the base station executes the non-resource release instruction and feeds back a corresponding execution result to the core network.
In this way, the time length of waiting for signaling interaction is overtime in the registration process of the UE, or the time length of waiting for the UE which completes registration to send data is overtime, so that when the resource release process is initiated, the non-resource release instruction sent by the core network can be responded, and the problem that unnecessary signaling interaction is increased when the UE registration or access failure re-access required by data transmission occurs is effectively avoided. It will be appreciated by those skilled in the art that 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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. It is therefore intended that the following claims be interpreted as including the 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 to 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 and the equivalents thereof, the present invention is also intended to include such modifications and variations.
Claims (14)
1. A resource release management method, comprising:
When the base station determines that the current working state meets the preset resource release condition, the base station sends a resource release request for User Equipment (UE) to a core network;
The base station determines that a non-resource release command sent by the core network is received within a set time length, and stops a resource release flow when determining that the current working state meets a timeout release rule in the resource release condition, wherein the non-resource release command comprises an initial context establishment request or PDU establishment request message or PDU session resource modification request message or UE context modification request message or downlink direct transmission message;
the base station executes the non-resource release command and feeds back a corresponding execution result to the core network;
the determining that the current working state meets the timeout release rule in the resource release condition includes:
And when the base station determines that the current working state meets any one or combination of the following, determining that a timeout release rule in the resource release condition is met:
the base station waits for the duration of receiving the resource allocation indication sent by the core network to reach the preset first duration;
and the base station waits for the duration of receiving the data sent by the UE to reach the preset second duration.
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 judges that the current working state meets any one or combination of the following conditions, the base station determines that the resource release condition is met: the base station waits for the duration of receiving the resource allocation indication sent by the core network to reach the preset first duration;
The base station waits for the duration of receiving the data sent by the UE to reach a preset second duration;
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 is unable to use the corresponding resources, comprising at least 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;
The base station determines that an abnormality occurs inside and cannot provide resources for the UE.
4. A method as claimed in any one of claims 1 to 3, further comprising:
after the base station sends a resource release request for User Equipment (UE) to a core network, if the resource release instruction sent by the core network is received within a set time period, immediately releasing the resources allocated for the UE; or alternatively
After the base station sends a resource release request for User Equipment (UE) to a core network, if any instruction sent by the core network is not received within a set duration, the resources allocated for the UE are released.
5. The method of claim 1, wherein 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 according to the non-resource release command, if so, the base station executes the non-resource release command and replies a corresponding execution result to the core network, otherwise, the base station directly executes the non-resource release command.
6. The method as recited in claim 1, further comprising:
The base station determines that a non-resource release command sent by the core network is received within a set time length, and does not execute the non-resource release command when the current working state is determined to not meet a timeout 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 according to the non-resource release command, if so, the base station informs the core network that the non-resource release command fails to be executed and releases the resources allocated to the UE when the set time length is overtime, otherwise, directly releases the resources allocated to the UE when the set time length is overtime.
7. A resource release management device, comprising at least: a processor and a memory:
the processor is configured to read the program in the memory and perform the following operations:
When the current working state is determined to meet the preset resource release condition, a resource release request aiming at User Equipment (UE) is sent to a core network;
Determining that a non-resource release command sent by the core network is received within a set time length, and stopping a resource release flow when the current working state is determined to meet a timeout release rule in the resource release condition, wherein the non-resource release command comprises an initial context establishment request or PDU establishment request message or PDU session resource modification request or UE context modification request message or downlink direct transfer message;
executing the non-resource release command and feeding back a corresponding execution result to the core network;
the determining that the current working state meets the timeout release rule in the resource release condition includes:
when the resource release management device determines that the current working state meets any one or combination of the following, determining that a timeout release rule in the resource release condition is met:
The resource release management device waits for the duration of receiving the resource allocation instruction sent by the core network to reach the preset first duration;
And the resource release management device waits for the duration of receiving the data sent by the UE to reach the preset second duration.
8. The apparatus of claim 7, wherein the processor is configured to, when the current operating state is determined to satisfy a preset resource release condition:
when the current working state is judged to meet any one or combination of the following conditions, determining that the resource release condition is met:
Waiting for receiving a duration of a resource allocation instruction sent by a core network to reach a preset first duration;
Waiting for the duration of receiving the data sent by the UE to reach a preset second duration;
it is determined that resources have been allocated for the UE, but the UE cannot use the corresponding resources.
9. The apparatus of claim 8, wherein the UE is unable to use the corresponding resources, comprising at least any one or a combination of:
Determining to disconnect from the UE;
determining that the UE establishes connection with other base stations;
And determining that abnormality occurs inside, and failing to provide resources for the UE.
10. The apparatus of any of claims 7-9, wherein the processor is further to:
After a resource release request for User Equipment (UE) is sent to a core network, if a resource release instruction sent by the core network is received within a set time period, immediately releasing resources allocated for the UE; or alternatively
After a resource release request for User Equipment (UE) is sent to a core network, if any instruction sent by the core network is not received within a set duration, the resources allocated for the UE are released.
11. The apparatus of claim 7, wherein the processor is configured to, when feeding back the corresponding execution result to the core network:
and judging whether an execution result needs to be fed back to the core network according to the non-resource release command, if so, executing the non-resource release command, and replying a corresponding execution result to the core network, otherwise, directly executing the non-resource release command.
12. The apparatus of claim 7, wherein the processor is further configured to:
Determining that a non-resource release command sent by the core network is received within a set time period, and not executing the non-resource release command when the current working state is determined to not meet a timeout release rule in the resource release condition;
and determining whether a processing result needs to be fed back to the core network according to the non-resource release command, if so, notifying the core network that the non-resource release command fails to be executed, 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.
13. A resource release management apparatus, comprising:
a transmitting unit for transmitting a resource release request for the user equipment UE to the core network when determining that the current working state meets a preset resource release condition;
The processing unit determines that a non-resource release command sent by the core network is received within a set time length, and stops a resource release flow when the current working state is determined to meet a timeout release rule in the resource release condition, wherein the non-resource release command comprises an initial context establishment request or PDU establishment request message or PDU session resource modification request message or a UE context modification request message or a downlink direct transmission message;
the execution unit executes the non-resource release command and feeds back a corresponding execution result to the core network;
the determining that the current working state meets the timeout release rule in the resource release condition includes:
when the resource release management device determines that the current working state meets any one or combination of the following, determining that a timeout release rule in the resource release condition is met:
The resource release management device waits for the duration of receiving the resource allocation instruction sent by the core network to reach the preset first duration;
And the resource release management device waits for the duration of receiving the data sent by the UE to reach the preset second duration.
14. A storage medium, wherein instructions in the storage medium, when executed by a processor, enable the execution of the resource release management method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010406374.9A CN113677041B (en) | 2020-05-14 | 2020-05-14 | Resource release management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010406374.9A CN113677041B (en) | 2020-05-14 | 2020-05-14 | Resource release management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113677041A CN113677041A (en) | 2021-11-19 |
| CN113677041B true CN113677041B (en) | 2024-08-20 |
Family
ID=78537185
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010406374.9A Active CN113677041B (en) | 2020-05-14 | 2020-05-14 | Resource release management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113677041B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20040054220A (en) * | 2002-12-18 | 2004-06-25 | 삼성전자주식회사 | Apparatus and Method For Handling A Holding Call In Wireless Communication System |
| WO2016191943A1 (en) * | 2015-05-29 | 2016-12-08 | 华为技术有限公司 | Method, base station, and user equipment for resource scheduling |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103826327B (en) * | 2014-01-28 | 2018-03-23 | 大唐移动通信设备有限公司 | A kind of method and apparatus of communication service release |
| US20170127471A1 (en) * | 2014-03-21 | 2017-05-04 | Nokia Solutions And Networks Oy | Resource release for proximity-based communications |
| CN106211332B (en) * | 2015-05-05 | 2021-08-17 | 中兴通讯股份有限公司 | Resource allocation method and device |
-
2020
- 2020-05-14 CN CN202010406374.9A patent/CN113677041B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20040054220A (en) * | 2002-12-18 | 2004-06-25 | 삼성전자주식회사 | Apparatus and Method For Handling A Holding Call In Wireless Communication System |
| WO2016191943A1 (en) * | 2015-05-29 | 2016-12-08 | 华为技术有限公司 | Method, base station, and user equipment for resource scheduling |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113677041A (en) | 2021-11-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4926216B2 (en) | Method and communication apparatus for processing uplink grant | |
| CN110351878B (en) | Random access processing method and related equipment | |
| WO2017101209A1 (en) | Service transmission method and apparatus | |
| CN106211362B (en) | Cluster session method and device, terminal equipment and network side equipment | |
| JP2011082984A (en) | Method and apparatus for handling radio link failure in wireless communication system | |
| CN104113928A (en) | Radio bearer control (RBC) message processing method and device | |
| JP7069395B2 (en) | Random access method and terminal | |
| WO2018024016A1 (en) | Wireless-network access method and device | |
| CN109756990A (en) | A kind of accidental access method and mobile communication terminal | |
| US20220167457A1 (en) | Maintaining, suspending, or modifying existing pur configuration in response to a ue entering into rrc connected mode | |
| US20240049327A1 (en) | Communication method, apparatus, and system | |
| WO2021134728A1 (en) | Context management method and apparatus | |
| JP2023535041A (en) | Data transmission method, device and system | |
| CN105025593B (en) | Method and equipment for releasing entity | |
| WO2022183970A1 (en) | Communication method, and device | |
| JP4902623B2 (en) | Method and communication apparatus for improving resumption efficiency of RRC process | |
| CN113677041B (en) | Resource release management method and device | |
| CN111372291B (en) | Radio Resource Control (RRC) connection reestablishment method and device | |
| CN101772189A (en) | Message processing method and user equipment | |
| CN104349502B (en) | A kind of wireless heterogeneous networks connection processing method, device and base station | |
| CN114051288B (en) | Terminal state change control method and device | |
| CN108243510B (en) | Method and device for allocating context resources to terminal | |
| CN108377553B (en) | Resource maintenance method and device | |
| CN117837265A (en) | Method and device for transmitting small data | |
| CN108924904B (en) | Uplink data transmission method, device and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |