CN112188643A - PDU session establishment method, device, terminal and storage medium - Google Patents

PDU session establishment method, device, terminal and storage medium Download PDF

Info

Publication number
CN112188643A
CN112188643A CN202011075068.8A CN202011075068A CN112188643A CN 112188643 A CN112188643 A CN 112188643A CN 202011075068 A CN202011075068 A CN 202011075068A CN 112188643 A CN112188643 A CN 112188643A
Authority
CN
China
Prior art keywords
pdu session
session
priority
pdu
target
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.)
Granted
Application number
CN202011075068.8A
Other languages
Chinese (zh)
Other versions
CN112188643B (en
Inventor
刘君
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zeku Technology Beijing Corp Ltd
Original Assignee
Zeku Technology Beijing Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zeku Technology Beijing Corp Ltd filed Critical Zeku Technology Beijing Corp Ltd
Priority to CN202011075068.8A priority Critical patent/CN112188643B/en
Publication of CN112188643A publication Critical patent/CN112188643A/en
Application granted granted Critical
Publication of CN112188643B publication Critical patent/CN112188643B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the application discloses a method, a device, a terminal and a storage medium for establishing a PDU session, and belongs to the technical field of communication. The method comprises the following steps: acquiring a first session priority contained in a PDU session establishment request; in response to the number of activated PDU sessions reaching an upper number limit, determining a low priority PDU session from the activated PDU sessions according to the first session priority and a second session priority of the activated PDU session, the second session priority of the low priority PDU session being lower than the first session priority; and releasing the low-priority PDU session, and establishing a target PDU session according to the PDU session establishment request. By adopting the method provided by the embodiment of the application, the success rate and the establishment efficiency of the new PDU session can be improved when the PDU session reaches the upper limit of the number.

Description

PDU session establishment method, device, terminal and storage medium
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a method, a device, a terminal and a storage medium for establishing a PDU session.
Background
Protocol Data Unit (PDU) Session (Session) refers to a process of communication between a User Equipment (UE) and a Data Network (DN), and after a PDU Session is established, a Data transmission channel is established between the UE and the DN.
In the related protocol, Public Land Mobile Network (PLMN) specifies a PDU session upper limit, and when a UE initiates a PDU session request but the number of PDU sessions has reached the upper limit, the PDU session request will be rejected by the Network side.
Disclosure of Invention
The embodiment of the application provides a method, a device, a terminal and a storage medium for establishing a PDU session. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides a method for establishing a PDU session, where the method is used for a terminal, and the method includes:
acquiring a first session priority contained in a PDU session establishment request;
in response to the number of activated PDU sessions reaching an upper number limit, determining a low priority PDU session from the activated PDU sessions according to the first session priority and a second session priority of the activated PDU session, the second session priority of the low priority PDU session being lower than the first session priority;
and releasing the low-priority PDU session, and establishing a target PDU session according to the PDU session establishment request.
In another aspect, an embodiment of the present application provides an apparatus for establishing a PDU session, where the apparatus is used for a terminal, and the apparatus includes:
the priority acquisition module is used for acquiring a first session priority contained in the PDU session establishment request;
a session determining module, configured to determine, in response to a number of activated PDU sessions reaching an upper limit, a low priority PDU session from the activated PDU sessions according to the first session priority and a second session priority of the activated PDU session, where the second session priority of the low priority PDU session is lower than the first session priority;
and the session release establishing module is used for releasing the low-priority PDU session and establishing a target PDU session according to the PDU session establishment request.
In another aspect, an embodiment of the present application provides a terminal, where the terminal includes a processor and a memory; the memory stores at least one instruction for execution by the processor to implement the method for PDU session establishment as described in the above aspect.
In another aspect, a computer-readable storage medium is provided, which stores at least one instruction for execution by a processor to implement the PDU session establishment method according to the above aspect.
In another aspect, embodiments of the present application provide a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to make the computer device execute the PDU session establishment method provided by the above aspect.
In the embodiment of the application, the session priority is set for the PDU session, so that the terminal can release the activated PDU session with the session priority lower than the target PDU session according to the session priority of the target PDU session to be established and the session priority of the activated PDU session under the condition that the number of the activated PDU session reaches the upper limit of the number and the PDU session establishment request is received, so that the target PDU session is established by using the released PDU session resources, and the success rate and the establishment efficiency of newly establishing the PDU session are improved when the PDU session reaches the upper limit of the number.
Drawings
Fig. 1 is a flowchart illustrating a non-emergency service corresponding PDU session establishment procedure in the related art;
fig. 2 is a flowchart illustrating an emergency service-corresponding PDU session establishment procedure in the related art;
fig. 3 is a flowchart illustrating an emergency service-corresponding PDU session establishment procedure in the related art;
fig. 4 is a flowchart illustrating a method for establishing a PDU session according to an exemplary embodiment of the present application;
fig. 5 is an interaction diagram illustrating a process of establishing a PDU session between a UE and a network according to an exemplary embodiment of the present application;
fig. 6 is a flowchart illustrating a PDU session establishment method according to another exemplary embodiment of the present application;
fig. 7 is an interaction diagram illustrating a process of an SM layer rejecting an application layer PDU session setup request according to an exemplary embodiment of the present application;
fig. 8 is an interaction diagram illustrating a PDU session setup procedure in an idle state according to an exemplary embodiment of the present application;
FIG. 9 is a diagram illustrating a PDU session status information element in accordance with an illustrative embodiment;
FIG. 10 is an interaction diagram illustrating a PDU session establishment procedure in a connected state according to an exemplary embodiment of the present application;
fig. 11 is a block diagram illustrating a structure of an apparatus for establishing a PDU session according to an embodiment of the present application;
fig. 12 is a block diagram illustrating a structure of a terminal according to an exemplary embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Reference herein to "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
In the related art, the PLMN limits the number of PDU sessions, and usually, for the same terminal, the PLMN limits the number of PDU sessions in the active state to not more than 15. When the PDU session number upper limit specified by the PLMN is reached, if the UE initiates a non-emergency PDU session establishment request, the network side sends a rejection request containing a #65 reason to the UE. After the UE receives the rejection request, the PDU Session establishment is indicated to be failed, the current PDU Session number is used as the PDU Session number upper limit allowed by the current PLMN and is stored by a Session Management (SM) layer of the UE until the terminal is shut down, a card is plugged in or out or the terminal is registered to a new PLMN.
When the subsequent UE initiates the PDU session request of the non-emergency service again, the PDU session request is directly rejected by the SM layer, and the UE can continue to create a new PDU session after the application layer indicates to release the PDU session in the activated state.
Schematically, as shown in fig. 1, it shows a flow chart of a non-emergency service corresponding PDU session establishment procedure in the related art.
When the upper limit of the PDU SESSION number is reached, the application layer sends a PDU SESSION establishment request (AP _ PDU _ SESSION _ EST _ REQ) of non-emergency (Not emergency) service to the SM layer, the SM layer rejects the PDU SESSION establishment request and sends a response (AP _ PDU _ SESSION _ EST _ REJ) rejecting the establishment of the PDU SESSION to the application layer.
When the PDU SESSION needs to be continuously established for the current service, the application layer specifies the PDU SESSION needing to be released, sends a PDU SESSION RELEASE request (AP _ PDU _ SESSION _ EST _ REJ) to the SM layer, and further sends the PDU SESSION RELEASE request (SM _ PDU _ SESSION _ RELEASE _ REQ) to the network side by the SM layer. After receiving the PDU SESSION RELEASE request, the network side RELEASEs the appointed PDU SESSION, and sends a PDU SESSION RELEASE instruction (SM _ PDU _ SESSION _ Release _ COMMAND _ IND) to the SM layer, the SM layer feeds back a PDU SESSION RELEASE completion signaling (SM _ PDU _ SESSION _ Release _ COMPLETE) to the network side, and sends a PDU SESSION RELEASE completion message (AP _ PDU _ SESSION _ REL _ CNF) to the application side.
After receiving the PDU SESSION release completion message, the application side sends a PDU SESSION release request to the SM layer again, and since the number of PDU SESSIONs in an active state at this time is less than the upper limit of the number, the SM layer sends a PDU SESSION establishment request (SM _ PDU _ SESSION _ EST _ REQ) to a Mobility Management (MM) layer, and the MM layer further sends an uplink non-access stratum transport message (UL NAS transport) to the network side to request the network side to establish the PDU SESSION. After the network side completes the PDU session establishment, a downlink non-access stratum transport message (DL NAS transport) is sent to the MM layer to indicate that the PDU session is accepted. The MM layer transmits a PDU SESSION reception indication (SM _ PDU _ SESSION _ ACCEPT _ IND) to the SM layer, and finally transmits a PDU SESSION setup confirm message (AP _ PDU _ SESSION _ EST _ CNF) to the application layer by the SM layer.
When the subsequent UE initiates a PDU session request of the emergency service, the SM layer selects a non-emergency activated PDU session and establishes the PDU session for the emergency service through the local deactivation and registration process.
Schematically, as shown in fig. 2, it shows a flow chart of a PDU session setup procedure of an emergency service in the related art.
When the PDU SESSION number reaches the upper limit of the PDU SESSION number, when an application layer sends a PDU SESSION establishment request (AP _ PDU _ SESSION _ EST _ REQ) of an emergency service to an SM layer, the SM layer selects a PDU SESSION corresponding to a non-emergency service from the activated PDU SESSION request for local release, sends a PDU SESSION state (PDU _ SESSION _ UPDATE _ STATUS _ IND) to an MM layer, and the MM layer initiates a registration process to a network side according to the PDU SESSION state to synchronize the state of the PDU SESSION with the network side. In the registration process, the MM layer sends a registration request (MM _ REG _ REQ) message to the network side, the network side feeds back a registration acceptance (MM _ REG _ ACCEPT) message to the MM layer, and the MM layer sends a registration completion (MM _ REG _ COMPLETELE) message to the network side according to the registration acceptance message.
After the registration is completed, the MM layer sends a registration state indication (MM _ REG _ STATUS _ IND) to the SM layer, the SM layer determines that the PDU SESSION currently in an active state does not reach the upper limit of the number (because one PDU SESSION is released) according to the registration state, so that a PDU SESSION establishment request (SM _ PDU _ SESSION _ EST _ REQ) is sent to the MM layer, and the MM layer further sends an uplink non-access stratum transmission message (UL NAS transport) to the network side to request the network side to establish the PDU SESSION. After the network side completes the PDU session establishment, a downlink non-access stratum transport message (DL NAS transport) is sent to the MM layer to indicate that the PDU session is accepted. The MM layer transmits a PDU SESSION reception indication (SM _ PDU _ SESSION _ ACCEPT _ IND) to the SM layer, and finally transmits a PDU SESSION setup confirm message (AP _ PDU _ SESSION _ EST _ CNF) to the application layer by the SM layer.
In addition to releasing the activated PDU session through the above-described local release and registration procedure, in another way, the SM layer may explicitly release the activated PDU session through the air interface. As shown in fig. 3, when the upper limit of the PDU SESSION number is reached, and the application layer sends a PDU SESSION establishment request (AP _ PDU _ SESSION _ EST _ REQ) for an emergency (emergency) service to the SM layer, the SM layer selects a PDU SESSION corresponding to a non-emergency service from the activated PDU SESSION requests, and initiates a SESSION release procedure for the PDU SESSION. After the SM layer sends a PDU SESSION RELEASE request (SM _ PDU _ SESSION _ RELEASE _ REQ) to the network side, the network side RELEASEs the PDU SESSION indicated by the PDU SESSION RELEASE request and sends a PDU SESSION RELEASE COMMAND (SM _ PDU _ SESSION _ RELEASE _ COMMAND _ IND) to the SM layer, and the SM layer further feeds back a PDU SESSION RELEASE COMPLETE signaling (SM _ PDU _ SESSION _ RELEASE _ COMPLETE) to the network side.
After the release of the empty display of the PDU session is completed, the UE further interacts with the network side through a process similar to that in fig. 2, so as to establish the PDU session of the emergency service.
As can be seen from the above PDU session establishment process, for a PDU session establishment request of a non-emergency service, since the SM layer directly rejects the request, a user must initiate a PDU session release through an application layer, and an additional interactive process is required; in addition, for the PDU session establishment request of the emergency service, the SM layer can only randomly select the PDU session of the non-emergency service from the activated PDU sessions, and the problem that the normal use of other services is influenced because the PDU session is not properly selected exists; in addition, a large amount of air interface signaling interaction is required for the release of the PDU session initiation and the network side state synchronization process, which not only needs to occupy a large amount of wireless air interface resources, but also causes a large time delay for the PDU session establishment of the emergency service.
In the embodiment of the application, the PDU session is not simply divided into a non-emergency state and an emergency state, but the session priority is set for the PDU session based on the service characteristics. Based on the session priority, when the number of the PDU sessions reaches the upper limit of the number, the UE can select the low-priority PDU session to release according to the session priority of the PDU session to be created currently and the session priority of the activated PDU session so as to establish the high-priority PDU session, and the PDU session establishment process is simplified while the accuracy of PDU session release is improved and the influence on service use is reduced (without being indicated by a user through additional interaction). In addition, in the embodiment of the application, the release and establishment flows of the PDU session are improved for different UE states, so that the signaling interaction with the air interface of the network side is reduced, the occupation of wireless air interface resources is reduced, and the establishment speed of the PDU session is increased. The following description will be made by using exemplary embodiments.
Referring to fig. 4, a flowchart of a PDU session establishment method according to an exemplary embodiment of the present application is shown. The embodiment is described by taking the method executed by the UE as an example, and the process includes the following steps:
step 401, obtain the first session priority included in the PDU session setup request.
In a possible implementation manner, the PDU session establishment request is sent from the application layer of the UE to the SM layer, and is used to indicate that a target PDU session is created for the target service, where the PDU session establishment request carries a first session priority (priority level) of the target PDU session, which is determined by the application layer according to the target service.
In the embodiment of the application, the session priority is an index used for measuring the importance degree of the PDU session, wherein the higher the session priority is, the higher the importance degree of the PDU session is, and correspondingly, the higher the reliability requirement of the service corresponding to the PDU session on data transmission is.
Optionally, the session priority of the PDU session is divided into at least three levels. For example, the session priority of the PDU session is divided into 5 levels of 1, 2, 3, 4, and 5. The number of the session priorities is not limited in the embodiments of the present application. The following embodiments will be described in detail with respect to the determination of the session priority corresponding to the PDU session.
Step 402, in response to the number of activated PDU sessions reaching the upper limit, determining a low priority PDU session from the activated PDU sessions according to the first session priority and a second session priority of the activated PDU session, the second session priority of the low priority PDU session being lower than the first session priority.
Optionally, after receiving the PDU session establishment request, the terminal first detects whether the number of the PDU sessions currently in the active state reaches the upper limit of the number, and if not, establishes a target PDU session according to the PDU session establishment request; if not, an activated PDU session needs to be released first. The upper limit of the number is stored in the SM layer (stored when the network side refuses to establish the PDU session for # 65), and accordingly, the process of judging whether the upper limit of the number is reached is executed by the SM layer.
If the number of the activated PDU sessions reaches the upper limit of the number, the terminal determines whether the activated PDU sessions need to be released or not according to the target PDU sessions and the session priorities corresponding to the activated PDU sessions so as to establish the target PDU sessions.
In a possible implementation manner, the SM layer selects an activated PDU session with a session priority lower than that of the target PDU session as a low-priority PDU session (i.e. a subsequent PDU session to be released), so as to maximally reduce the influence of the release of the subsequent PDU session on the service.
In an illustrative example, when the number of the activated PDU sessions reaches the upper limit of 10 and the first session priority of the target PDU session is level 3, the SM layer determines the activated PDU session with the second session priority of level 1 as a low priority PDU session.
Step 403, releasing the low priority PDU session, and establishing the target PDU session according to the PDU session establishment request.
Further, the UE releases the low priority PDU session, so that the number of the activated PDU sessions is smaller than the upper limit of the number, and further interacts with the network side to create a target PDU session for a target service. It should be noted that after creating the target PDU session, the number of the activated PDU sessions will reach the upper limit again.
By adopting the scheme provided by the embodiment of the application, even if the PDU session establishment request corresponding to the non-emergency service is received under the condition that the number of the activated PDU sessions reaches the upper limit of the number, the SM layer can establish the PDU session for the non-emergency service as long as the activated PDU session with the session priority lower than that of the PDU session exists, and the upper layer (namely, the application layer) does not need to initiate a session release instruction, so that the interactive flow in the PDU session process is simplified, and the establishment speed of the PDU session is improved; meanwhile, the SM layer determines the PDU session to be released according to the session priority, so that the influence of the PDU session release on the service can be reduced to the maximum extent.
In an illustrative example, in the related art, the currently active PDU session includes PDU session 1, PDU session 2, PDU session 3, PDU session 4 and PDU session 5, and the service corresponding to PDU session 1 is an emergency service, while the services corresponding to the remaining PDU sessions are non-emergency services. When the upper limit of the number is 5, if a PDU session establishment request of non-emergency service is received, the SM layer directly rejects the request, and the PDU session can be continuously established only after the application layer indicates to release one of the PDU sessions in the activated state. For example, the application layer indicates that PDU session 2 is to be released in order to establish a PDU session for new non-emergency traffic.
By adopting the scheme provided by the embodiment of the application, the currently activated PDU session includes PDU session 1, PDU session 2, PDU session 3, PDU session 4 and PDU session 5, and when the session priority corresponding to each PDU session is 5, 3, 1, if a PDU session establishment request of a non-emergency service is received and the session priority included in the PDU session establishment request is 2 level, because the PDU session 5 with the session priority lower than 2 level exists in the activated PDU session, the SM layer does not reject the PDU session establishment request, but selects to release the PDU session 5, so as to establish the PDU session with the session priority of 2 level with the new non-emergency service.
Obviously, it can be seen from the above example that, with the solution provided by the embodiment of the present application, there is no need to interact with the application layer to indicate the PDU session to be released, and the determined released PDU session is more appropriate and has less impact on the service (in the related art, the session priority of the released PDU session is actually higher than the session priority of the PDU session to be established).
In summary, in the embodiment of the present application, by setting the session priority for the PDU session, the terminal can release the activated PDU session with the session priority lower than the target PDU session according to the session priority of the target PDU session to be established and the session priority of the activated PDU session when the number of the activated PDU session reaches the upper limit of the number and the PDU session establishment request is received, so as to establish the target PDU session by using the released PDU session resources, which is helpful to improve the success rate of creating a new PDU session and the establishment efficiency when the PDU session reaches the upper limit of the number.
In one possible embodiment, when the number of activated PDU sessions has not reached the upper limit of the number, the process of establishing a target PDU session based on a PDU session establishment request is as shown in FIG. 5.
Under the condition of being registered to the network, when a PDU SESSION needs to be created for a target service, an application layer sends a PDU SESSION establishment request (AP _ PDU _ SESSION _ EST _ REQ) containing a SESSION priority (priority level) to an SM layer. Since the number of activated PDU SESSIONs does not reach the upper limit of the number, the SM layer saves the SESSION priority included in the request and transmits a PDU SESSION setup request (SM _ PDU _ SESSION _ EST _ REQ) to the MM layer. The MM layer further interacts with the network side through a process similar to that in fig. 2, to implement PDU SESSION establishment of the emergency service, and feeds back (SM _ PDU _ SESSION N _ ACCEPT _ IND) to the SM layer, and finally the SM layer notifies the application layer that the PDU SESSION is completed (AP _ PDU _ SESSION _ EST _ CNF). And the SM layer stores the established PDU session and the session priority in an associated manner, so that the low-level PDU session needing to be released is determined based on the session priority when the upper limit of the number is reached.
Regarding the determination of the session priority, in a possible embodiment, the session priority is determined according to at least one of a service type and a service usage requirement of a service corresponding to the PDU session.
The service type is a service attribute of the service itself, and the services of different service types have different requirements for data transmission reliability, and the service type may include a short message service, a video service, a voice call service, a game data service, and the like, which is not limited in this embodiment of the present application.
In some embodiments, the UE stores the correspondence between different service types and the session priorities, and when a PDU session needs to be created for a certain service, the application layer determines the session priority of the PDU session to be created based on the correspondence. Schematically, the correspondence is shown in table one.
Watch 1
Type of service Session priority
Game data service 5
Voice call service 4
Video service 3
Short message service 1
The service use requirement is a service attribute determined according to user settings or user use habits, for example, for a user A, the service use requirement of the voice call service is set to be the highest level, and for a user B, the service use requirement of the video service is set to be the highest level; or, based on the service usage frequency of the user a, the service usage requirement of the voice call service with the highest usage frequency is set to the highest level, and based on the service usage frequency of the user B, the service usage requirement of the game data service with the highest usage frequency is set to the highest level.
In some embodiments, the UE determines service usage requirements of different services for the user by counting service usage records of the user, so as to determine session priorities of PDU sessions corresponding to various services.
Of course, the application layer may also comprehensively determine the session priority of the PDU session corresponding to the service based on the service type and the service usage requirement, which is not described herein again in this embodiment.
In other possible implementations, the application layer may also determine the session priority by using other attributes related to the service, which is not limited in this embodiment of the present application.
Referring to fig. 6, a flowchart of a PDU session establishment method according to another exemplary embodiment of the present application is shown. The embodiment is described by taking the method executed by the UE as an example, and the process includes the following steps:
step 601, acquiring a first session priority contained in the PDU session establishment request.
In a possible implementation manner, after receiving a PDU session establishment request sent by an application layer, the SM layer first detects that the number of activated PDU sessions reaches an upper limit of the number, and if the number reaches the upper limit, further detects whether there is an activated PDU session with a second session priority lower than the first session priority. If yes, go to step 603, otherwise go to step 602.
In response to the number of activated PDU sessions reaching the upper number limit and there being no second session priority lower than the first session priority, the PDU session setup request is rejected, step 602.
Since the SM layer stores the PDU session and the session priority in association in the PDU session creating process, the SM layer can determine whether the session priority is lower than the activated PDU session of the target PDU session by comparing each stored second session priority with the first session priority.
If there is no second session priority lower than the first session priority, indicating that the session importance of the target session is lower than that of the activated session, the SM layer rejects the PDU session establishment request. Optionally, after the SM layer rejects the PDU session establishment request, the user layer may further instruct to release the PDU session corresponding to the non-emergency service, which is not described herein again.
Optionally, when the first session priority in the PDU session establishment request is the lowest session priority, the SM layer directly rejects the PDU session establishment request without comparing the first session priority with the second session priority.
Illustratively, as shown in fig. 7, the SM layer stores a second session priority corresponding to each activated PDU session. When a PUD SESSION establishment request (AP _ PDU _ SESSION _ EST _ REQ) sent by an application layer is received under the condition that the upper limit of the number of PDU SESSIONs is reached, and the first SESSION priority contained in the request is lower than each second SESSION priority, the SM layer directly rejects the PDU SESSION establishment request (AP _ PDU _ SESSION _ EST _ REJ).
Step 603, in response to that the number of the activated PDU sessions reaches the upper limit of the number and that at least one second session priority lower than the first session priority exists, determining the activated PDU session corresponding to the lowest session priority in the second session priorities as the low priority PDU session.
In order to minimize the impact on the traffic when there are activated PDU sessions with a second session priority lower than the first session priority, in some embodiments, the SM layer determines the activated PDU session corresponding to the lowest session priority in the second session priority as a low priority PDU session, i.e., a PDU session to be released.
Optionally, when there are at least two activated PDU sessions with session priority lower than that of the target PDU session, the SM layer selects a low priority PDU session from the at least two activated PDU sessions according to the order of PDU session establishment or randomly.
In an illustrative example, the PDU session currently in an active state includes PDU session 1, PDU session 2, PDU session 3, PDU session 4, and PDU session 5, and when the session priority corresponding to each PDU session is 5, 3, 2, and 1, respectively, if a PDU session establishment request of a non-emergency service is received and the session priority included in the PDU session establishment request is 2 level, the SM layer determines PDU session 5 as a low-priority PDU session.
In the related art, after determining the PDU session to be released, the UE synchronizes the PDU session state with the network side through the local release and registration process (deactivates the PDU session to be released), or synchronizes the PDU session state with the network side in an explicit manner. In the above process, the UE and the network side need to perform more air interface signaling transmission, which affects the efficiency of establishing the PDU session.
In the embodiment of the application, after the low-priority PDU session is determined, the UE performs PDU session release and new PDU session establishment according to the current state in a manner corresponding to the current state, so that the number of times of interface signaling interaction between the UE and a network side is reduced, and the PDU session establishment efficiency is improved.
Step 604, in response to being in idle state, releasing the low priority PDU session through the SR flow, and establishing a target PDU session.
In an idle (idle) state, since the UE needs to execute a Service Request (Service Request) procedure, and in the SR procedure, a Service Request (Service Request) message sent by the MM layer to the network side includes a PDU session status (PDU session status) cell, in order to reduce the number of times of air interface signaling transmission, in this embodiment, the UE synchronizes the PDU session status with the network side through the SR procedure, and releases the low-priority PDU session, so as to subsequently establish a target PDU session.
Alternatively, this step may include the following substeps.
And responding to the idle state, releasing the local low-priority PDU session, and sending an SR message to the network side, wherein the SR message comprises the PDU session state, and the network side is used for deactivating the local low-priority PDU session according to the PDU session state.
In a possible implementation manner, when the low-priority PDU session is determined and currently in an idle state, the SM layer locally releases the low-priority PDU session, and sends a PDU session release request to the MM layer, where the PDU session release request includes a session identifier of the low-priority PDU session.
After receiving the PDU session release request, the MM layer sends a service request message to the network side through an air interface, wherein the service request message contains a PDU session state, and the session state of the low-priority PDU session in the PDU session state is an inactivated state.
The network side receives the service request message sent by the MM layer and locally deactivates the low-priority PDU session after acquiring the PDU session state contained in the service request message, thereby realizing the synchronization of the PDU session state with the SM layer of the UE side and releasing a PDU session resource.
And secondly, responding to a service acceptance message sent by a receiving network side, and sending a first uplink non-access stratum transmission message to the network side, wherein the first uplink non-access stratum transmission message is used for requesting to establish a target PDU session.
And the network side and the UE side realize the synchronization of the PDU conversation state, and the network side sends a service acceptance (Serviceaccept) message to the MM layer. Correspondingly, after receiving the service acceptance message, the MM layer determines that the low-level PDU session of the network side has been released, and further sends a first uplink non-access stratum transport (UL NAS transport) message to the network side to request the network side to establish a target PDU session.
In a possible implementation manner, after receiving the service acceptance message, the MM layer sends a PDU session release completion message to the SM layer, because the number of the activated PDU sessions after releasing the low priority PDU session is less than the upper limit of the number, the SM layer sends a PDU session establishment request to the MM layer, and after receiving the PDU session establishment request, the MM layer sends a first uplink non-access stratum transmission message to the network side.
And thirdly, in response to receiving a first downlink non-access stratum transmission message sent by a network side, determining that the target PDU session establishment is completed.
And after the network side completes the PDU session establishment according to the first uplink non-access stratum transmission message, the network side sends a PDU session establishment completion indication to the UE side to inform the UE that the target PDU session is established for the target service.
In one possible implementation, the MM layer receives a first downlink non-access stratum transport (DL NAS transport) message sent by the network side, thereby sending a PDU session acceptance indication to the SM layer, which informs the application layer that the target session is established.
Illustratively, as shown in fig. 8, the SM layer stores a second session priority corresponding to each activated PDU session. When a PUD SESSION establishment request (AP _ PDU _ SESSION _ EST _ REQ) sent by an application layer is received under the condition that the upper limit of the number of PDU SESSIONs is reached, and the first SESSION Priority contained in the request is greater than the second SESSION Priority of at least one activated PDU SESSION, the SM layer determines the Lowest SESSION Priority (Lowest Priority level) in the activated PDU SESSIONs and sends a PDU SESSION release request (SM _ PDU _ SESSION _ REL _ REQ) containing the Lowest SESSION Priority to the MM layer.
After receiving the PDU session release request, the MM layer sends a Service request (Service request) message containing the Pdu session status of the PDU session state to the network side in the SR process, indicates the network side to deactivate the PDU session with the local lowest session priority, and feeds back a Service acceptance (Service accept) message.
After receiving the service acceptance message, the MM layer completes the SR process and sends a PDU SESSION release completion indication (SM _ PDU _ Session _ REL _ CNF) to the SM layer so as to trigger the SM layer to send a PDU SESSION establishment request (SM _ PDU _ Session _ EST _ REQ) to the MM layer. After receiving the PDU session establishment request, the MM layer establishes a target PDU session with the network side through non-access layer transmission information, and further feeds back a PDU session establishment completion indication to the application layer through the SM layer.
Obviously, compared with the registration process in fig. 2 (3 air interface signaling), the number of air interface transmission signaling can be reduced by synchronizing the PDU session state with the network side through the idle SR process (only 2 air interface signaling is needed), and the length of the SR message is much smaller than that of the registration message; compared with the explicit indication process in fig. 3, 2 air interface signaling is saved, which is helpful to reduce occupied air interface transmission resources and improve PDU session establishment efficiency.
Step 605, in response to being in the connected state, releasing the low priority PDU session through the non-access stratum transport stream procedure and establishing a target PDU session.
In a connection (connect) state, in order to improve PDU session establishment efficiency and reduce air interface signaling interaction, in a possible implementation, a PDU session state field is additionally added to a non-access stratum transport message by a UE, so as to instruct a network side to deactivate a low-priority PDU session through the field, and establish a target PDU session for a target service.
Alternatively, this step may include the following substeps.
The method comprises the steps that firstly, in response to the connection state, a local low-priority PDU session is released, a second uplink non-access layer transmission message is sent to a network side, the second uplink non-access layer transmission message is used for requesting to establish a target PDU session and comprises a first PDU session state, the state corresponding to the low-priority PDU session in the first PDU session state is a deactivation state, and the network side is used for deactivating the local low-priority PDU session according to the second uplink non-access layer transmission message and establishing the target PDU session;
in this embodiment, a PDU session status cell (field) needs to be newly added to the uplink and downlink non-access stratum transmission message of the MM side, so that the network side synchronizes the PDU session status with the UE side through the uplink and downlink non-access stratum transmission message. Optionally, the PDU session status cell is unnecessary in the uplink and downlink non-access stratum transport message, and adopts a TLV (Tag-Length-Value) format, and the Length is 4 to 34 bytes.
In an illustrative example, the format of the PDU session status information element is shown in FIG. 9. The first byte in the PDU session status cell is used to write the PDU session status IEI, the second byte is used to write the PDU status content length, and the 3 rd to 4 th bytes are used to write PSI (1bit) of each PDU session, where PSI ═ 1 indicates that the PDU session is in an active status, PSI ═ 1 indicates that the PDU session is in an inactive status, and the 5 th to 34 th bytes are spare bytes.
And the network side receives the second uplink non-access stratum transmission message, and after recognizing that the second uplink non-access stratum transmission message contains the first PDU session state, the network side deactivates the low-priority PDU session according to the first PDU session state and the locally stored PDU session state, and establishes a target PDU session for the target service of the UE side.
And secondly, responding to a received second downlink non-access stratum transmission message sent by the network side, and determining that the target PDU session is established, wherein the second downlink non-access stratum transmission message contains a second PDU session state, and the state corresponding to the target PDU session in the first PDU session state is an activated state.
Further, after the network side completes the low-priority PDU session deactivation and the target PDU session establishment, a second downlink non-access stratum transmission message containing a second PDU session state is sent to the UE side, and the UE side is informed to complete the PDU session establishment.
Illustratively, as shown in fig. 10, the SM layer stores a second session priority corresponding to each activated PDU session. When a PUD SESSION establishment request (AP _ PDU _ SESSION _ EST _ REQ) sent by an application layer is received under the condition that the upper limit of the number of PDU SESSIONs is reached, and the first SESSION Priority contained in the request is greater than the second SESSION Priority of at least one activated PDU SESSION, the SM layer determines the Lowest SESSION Priority (Lowest Priority level) in the activated PDU SESSIONs and sends the PDU SESSION establishment request (SM _ PDU _ SESSION _ EST _ REQ) containing the Lowest SESSION Priority to the MM layer.
After receiving the PDU SESSION establishment request, the MM layer adds a PDU SESSION state (PDU SESSION STATUS) in an uplink non-access layer transmission message sent to the network side, so that the network side can deactivate the PDU SESSION with the lowest SESSION priority according to the SESSION state and establish a target PDU SESSION. After the target PDU session establishment is completed, the network side sends a downlink non-access layer transmission message carrying the PDU session state to the MM layer to indicate that the PDU session establishment is completed, and finally the MM layer feeds back the PDU session establishment completion indication to the application layer through the SM layer.
Obviously, the session release and establishment are realized through the non-access stratum transmission process, the registration flow shown in fig. 2 is omitted, and 3 pieces of air interface signaling are saved; compared with the explicit indication shown in fig. 3, 2 pieces of air interface signaling of the PDU session release flow can be omitted, the number of air interface signaling interactions in the PDU session establishment process is reduced, occupied air interface transmission resources are reduced, and the PDU session establishment efficiency is improved.
Step 606, the session identifier of the low priority PDU session is deleted, as well as the second session priority stored in association with the low priority PDU session.
In a possible implementation manner, after receiving a PDU session establishment completion indication or a PDU session release completion indication sent by the MM layer, the SM layer deletes the session identifier of the low-priority PDU session and deletes the second session priority stored in association with the low-priority PDU session, thereby avoiding the released PDU session from affecting the subsequent judgment process.
Step 607, responding to the successful establishment of the target PDU session, the first session priority and the session identification of the target PDU session are stored in association.
In a possible implementation manner, after the PDU session establishment is successful, that is, after the SM layer receives the PDU session establishment completion indication sent by the MM layer, the first session priority and the session identifier of the target PDU session are stored in association, so that when the PDU session establishment request is received again in the following, the PDU session establishment request is used as a determination basis for the PDU session to be released.
In this embodiment, in different states, the UE performs PDU session state synchronization with the network side through an SR flow (idle state) or a non-access stratum transmission flow (connected state) in combination with the characteristics of air interface signaling interaction in the state, so as to save the amount of air interface signaling in the PDU session release establishment process and improve the PDU session establishment speed.
Referring to fig. 11, a block diagram of an apparatus for establishing a PDU session according to an embodiment of the present application is shown. The apparatus may be implemented as all or a portion of the terminal in software, hardware, or a combination of both. The device includes:
a priority obtaining module 1101, configured to obtain a first session priority included in the PDU session establishment request;
a session determining module 1102, configured to determine, in response to the number of activated PDU sessions reaching an upper limit, a low priority PDU session from the activated PDU sessions according to the first session priority and a second session priority of the activated PDU session, where the second session priority of the low priority PDU session is lower than the first session priority;
a session release establishing module 1103, configured to release the low-priority PDU session, and establish a target PDU session according to the PDU session establishment request.
Optionally, the session determining module 1102 is configured to:
in response to there being at least one of the second session priorities that is lower than the first session priority, determining an activated PDU session corresponding to a lowest session priority of the second session priorities as the low priority PDU session.
Optionally, the apparatus further comprises:
a deleting module, configured to delete the session identifier of the low-priority PDU session and the second session priority stored in association with the low-priority PDU session;
and the storage module is used for responding to the successful establishment of the target PDU session and performing associated storage on the first session priority and the session identifier of the target PDU session.
Optionally, the session priority is determined according to at least one of a service type and a service usage requirement of a service corresponding to the PDU session.
Optionally, the session release establishing module 1103 includes:
a first release establishing unit, configured to release the low-priority PDU session through a service request SR process in response to being in an idle state, and establish the target PDU session;
and the second release establishing unit is used for responding to the connection state, releasing the low-priority PDU session through a non-access stratum transmission flow and establishing the target PDU session.
Optionally, the first release establishing unit is configured to:
in response to the idle state, releasing the local low-priority PDU session, and sending an SR message to a network side, wherein the SR message contains a PDU session state, and the network side is used for deactivating the local low-priority PDU session according to the PDU session state;
responding to a service acceptance message sent by the network side, and sending a first uplink non-access stratum transmission message to the network side, wherein the first uplink non-access stratum transmission message is used for requesting to establish the target PDU session;
and determining that the target PDU session establishment is completed in response to receiving a first downlink non-access stratum transmission message sent by the network side.
Optionally, the second release establishing unit is configured to:
in response to the connection state, releasing the local low priority PDU session, and sending a second uplink non-access stratum transmission message to the network side, wherein the second uplink non-access stratum transmission message is used for requesting to establish the target PDU session and comprises a first PDU session state, the state corresponding to the low priority PDU session in the first PDU session state is a deactivation state, and the network side is used for deactivating the local low priority PDU session according to the second uplink non-access stratum transmission message and establishing the target PDU session;
and determining that the target PDU session is established in response to receiving a second downlink non-access stratum transmission message sent by the network side, wherein the second downlink non-access stratum transmission message comprises a second PDU session state, and the state corresponding to the target PDU session in the first PDU session state is an activated state.
Optionally, the apparatus further comprises:
a request rejection module for rejecting the PDU session establishment request in response to the number of activated PDU sessions reaching the upper number limit and the absence of the second session priority being lower than the first session priority.
In summary, in the embodiment of the present application, by setting the session priority for the PDU session, the terminal can release the activated PDU session with the session priority lower than the target PDU session according to the session priority of the target PDU session to be established and the session priority of the activated PDU session when the number of the activated PDU session reaches the upper limit of the number and the PDU session establishment request is received, so as to establish the target PDU session by using the released PDU session resources, which is helpful to improve the success rate of creating a new PDU session and the establishment efficiency when the PDU session reaches the upper limit of the number.
Referring to fig. 12, a block diagram of a terminal according to an exemplary embodiment of the present application is shown. A terminal in the present application may include one or more of the following components: a processor 1201, a memory 1202, a receiver 1203, and a transmitter 1204.
Processor 1201 may include one or more processing cores. The processor 1201 connects various parts within the overall terminal using various interfaces and lines, performs various functions of the terminal and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 1202, and calling data stored in the memory 1202. Alternatively, the processor 1201 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 1201 may integrate one or a combination of several of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Neural-Network Processing Unit (NPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing contents required to be displayed by the touch display screen; the NPU is used for realizing an Artificial Intelligence (AI) function; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 1201, and may be implemented by a single chip.
The Memory 1202 may include a Random Access Memory (RAM) or a Read-Only Memory (ROM). Optionally, the memory 1202 includes a non-transitory computer-readable medium. The memory 1202 may be used to store instructions, programs, code sets, or instruction sets. The memory 1202 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, and the like; the storage data area may store data (such as audio data, a phonebook) created according to the use of the terminal, and the like.
The receiver 1203 and the transmitter 1204 may be implemented as one communication component, which may be a communication chip.
Optionally, the terminal may further include a display screen. A display screen is a display component for displaying a user interface. Optionally, the display screen further has a touch function, and through the touch function, a user can perform touch operation on the display screen by using any suitable object such as a finger, a touch pen, and the like.
In addition, those skilled in the art will appreciate that the configurations of the terminals shown in the above-described figures do not constitute limitations on the terminal equipment, which may include more or fewer components than shown, or some components in combination, or a different arrangement of components. For example, the terminal further includes a camera module, a radio frequency circuit, an input unit, a sensor (such as an acceleration sensor, an angular velocity sensor, a light sensor, and the like), an audio circuit, a Wireless Fidelity (WiFi) module, a power supply, a bluetooth module, and other components, which are not described herein again.
The present application further provides a computer-readable medium, where at least one instruction is stored, and the at least one instruction is loaded and executed by a processor to implement the PDU session establishment method according to the above embodiments.
Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to make the computer device execute the PDU session establishment method provided by the above aspect.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (11)

1. A PDU session establishment method, wherein the method is used for a terminal, and the method comprises:
acquiring a first session priority contained in a PDU session establishment request;
in response to the number of activated PDU sessions reaching an upper number limit, determining a low priority PDU session from the activated PDU sessions according to the first session priority and a second session priority of the activated PDU session, the second session priority of the low priority PDU session being lower than the first session priority;
and releasing the low-priority PDU session, and establishing a target PDU session according to the PDU session establishment request.
2. The method of claim 1, wherein determining a low priority PDU session from among the activated PDU sessions based on the first session priority and a second session priority of the activated PDU session comprises:
in response to there being at least one of the second session priorities that is lower than the first session priority, determining an activated PDU session corresponding to a lowest session priority of the second session priorities as the low priority PDU session.
3. The method of claim 2, wherein after releasing the low priority PDU session and establishing a target PDU session in accordance with the PDU session establishment request, the method further comprises:
deleting the session identifier of the low priority PDU session and the second session priority stored in association with the low priority PDU session;
and responding to the successful establishment of the target PDU session, and performing associated storage on the first session priority and the session identification of the target PDU session.
4. A method according to any of claims 1 to 3, wherein the session priority is determined in dependence on at least one of the service type and the service usage requirement of the service corresponding to the PDU session.
5. The method according to any of claims 1 to 3, wherein said releasing said low priority PDU session and establishing a target PDU session according to said PDU session establishment request comprises:
responding to the idle state, releasing the low-priority PDU session through a service request SR process, and establishing the target PDU session;
and responding to the connection state, releasing the low-priority PDU session through a non-access stratum transmission flow, and establishing the target PDU session.
6. The method of claim 5, wherein releasing the low priority PDU session and establishing the target PDU session via SR flow in response to being in an idle state comprises:
in response to the idle state, releasing the local low-priority PDU session, and sending an SR message to a network side, wherein the SR message contains a PDU session state, and the network side is used for deactivating the local low-priority PDU session according to the PDU session state;
responding to a service acceptance message sent by the network side, and sending a first uplink non-access stratum transmission message to the network side, wherein the first uplink non-access stratum transmission message is used for requesting to establish the target PDU session;
and determining that the target PDU session establishment is completed in response to receiving a first downlink non-access stratum transmission message sent by the network side.
7. The method of claim 5, wherein releasing the low priority PDU session and establishing the target PDU session via a non-access stratum transport flow in response to being in a connected state comprises:
in response to the connection state, releasing the local low priority PDU session, and sending a second uplink non-access stratum transmission message to the network side, wherein the second uplink non-access stratum transmission message is used for requesting to establish the target PDU session and comprises a first PDU session state, the state corresponding to the low priority PDU session in the first PDU session state is a deactivation state, and the network side is used for deactivating the local low priority PDU session according to the second uplink non-access stratum transmission message and establishing the target PDU session;
and determining that the target PDU session is established in response to receiving a second downlink non-access stratum transmission message sent by the network side, wherein the second downlink non-access stratum transmission message comprises a second PDU session state, and the state corresponding to the target PDU session in the first PDU session state is an activated state.
8. The method of any of claims 1 to 3, further comprising:
rejecting the PDU session establishment request in response to the number of activated PDU sessions reaching the upper number limit and the absence of the second session priority lower than the first session priority.
9. An apparatus for establishing a PDU session, wherein the apparatus is used for a terminal, the apparatus comprising:
the priority acquisition module is used for acquiring a first session priority contained in the PDU session establishment request;
a session determining module, configured to determine, in response to a number of activated PDU sessions reaching an upper limit, a low priority PDU session from the activated PDU sessions according to the first session priority and a second session priority of the activated PDU session, where the second session priority of the low priority PDU session is lower than the first session priority;
and the session release establishing module is used for releasing the low-priority PDU session and establishing a target PDU session according to the PDU session establishment request.
10. A terminal, characterized in that the terminal comprises a processor and a memory; the memory stores at least one instruction for execution by the processor to implement the method for PDU session establishment according to any of claims 1 to 8.
11. A computer-readable storage medium having stored thereon at least one instruction for execution by a processor to perform a method of PDU session establishment according to any of claims 1 to 8.
CN202011075068.8A 2020-10-09 2020-10-09 PDU session establishment method, device, terminal and storage medium Active CN112188643B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011075068.8A CN112188643B (en) 2020-10-09 2020-10-09 PDU session establishment method, device, terminal and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011075068.8A CN112188643B (en) 2020-10-09 2020-10-09 PDU session establishment method, device, terminal and storage medium

Publications (2)

Publication Number Publication Date
CN112188643A true CN112188643A (en) 2021-01-05
CN112188643B CN112188643B (en) 2022-11-15

Family

ID=73947931

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011075068.8A Active CN112188643B (en) 2020-10-09 2020-10-09 PDU session establishment method, device, terminal and storage medium

Country Status (1)

Country Link
CN (1) CN112188643B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113068237A (en) * 2021-03-29 2021-07-02 Oppo广东移动通信有限公司 Session management method, user equipment, computer storage medium and system
WO2021147672A1 (en) * 2020-01-23 2021-07-29 华为技术有限公司 Session processing method and communication device
WO2023010994A1 (en) * 2021-08-06 2023-02-09 华为技术有限公司 Network slice access control method and communication apparatus

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180359795A1 (en) * 2017-06-09 2018-12-13 Samsung Electronics Co., Ltd Method for establishing protocol data unit session in communication system
US20190109823A1 (en) * 2017-10-09 2019-04-11 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
CN110809899A (en) * 2017-10-20 2020-02-18 Oppo广东移动通信有限公司 Method for transmitting data, terminal equipment and network equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180359795A1 (en) * 2017-06-09 2018-12-13 Samsung Electronics Co., Ltd Method for establishing protocol data unit session in communication system
US20190109823A1 (en) * 2017-10-09 2019-04-11 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
CN110809899A (en) * 2017-10-20 2020-02-18 Oppo广东移动通信有限公司 Method for transmitting data, terminal equipment and network equipment
CN111182572A (en) * 2017-10-20 2020-05-19 Oppo广东移动通信有限公司 Method for transmitting data, terminal equipment and network equipment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA: ""PDU session number control based on priority"", 《3GPP TSG-CT WG1 MEETING #124-E C1-203553》 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021147672A1 (en) * 2020-01-23 2021-07-29 华为技术有限公司 Session processing method and communication device
CN113068237A (en) * 2021-03-29 2021-07-02 Oppo广东移动通信有限公司 Session management method, user equipment, computer storage medium and system
WO2023010994A1 (en) * 2021-08-06 2023-02-09 华为技术有限公司 Network slice access control method and communication apparatus

Also Published As

Publication number Publication date
CN112188643B (en) 2022-11-15

Similar Documents

Publication Publication Date Title
CN112188643B (en) PDU session establishment method, device, terminal and storage medium
CN111278106B (en) Paging indication method, paging method, terminal and network side equipment
CN110167051B (en) Communication method and communication equipment under centralized unit-distributed unit architecture
EP3821665B1 (en) Electronic device for supporting access to wireless media using target wake time (twt) defined in ieee 802.11 standard
EP3343865A1 (en) Method, system, and apparatus for implementing machine-to-machine service
CN111586807B (en) Network access method and communication device
CN113055954B (en) Communication service establishing method, device, terminal and storage medium
CN108632810A (en) Method, terminal device and the network equipment of control terminal equipment state
CN109151950B (en) Access control method, network equipment and terminal equipment
US11382019B2 (en) Session management method and apparatus, and communications system
EP3131276B1 (en) Incoming call forwarding method and user equipment
WO2015074238A1 (en) Method and apparatus for selecting information pushing terminal
CN110945959B (en) RRC connection state control method, device and storage medium
CN104936282A (en) Method and device for registering converged communication service
CN113207145B (en) Service-based measurement response method, device, terminal and storage medium
CN112243280B (en) Service initiation method, device, terminal and storage medium
CN111527767B (en) Method and equipment for improving network performance
CN109936861A (en) Communication means and access network equipment, terminal device, equipment of the core network
WO2023020240A1 (en) Device control method and apparatus, and chip, electronic device and storage medium
CN114828039A (en) Data transmission method, terminal and network side equipment
CN101668188A (en) Video server and method for controlling working condition of video server
EP3595345A1 (en) Control plane connection management method and device
CN108541046B (en) Network selection method, terminal and storage medium
CN112312494B (en) Communication method and terminal device
CN112770107B (en) Modification method of load bearing and related device

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