Method for message processing and associated devices and apparatuses

Abstract

Embodiments herein relate to a method performed by an access and mobility management function, AMF, and a user equipment, UE, for message handling, and a corresponding AMF and UE. In particular, embodiments herein relate to a method performed by an access and mobility management function, AMF, and a user equipment, UE, for handling a service request, and a corresponding AMF and UE.

Description

[0001] This application is a divisional application of Chinese invention patent application entitled “Method for Message Processing and Associated Apparatus and Devices” (application number 201880006148.2, application date January 9, 2018). Technical Field

[0002] An embodiment for processing service requests is disclosed. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) has begun research on the development and design of next-generation mobile communication systems (also known as 5G mobile communication systems or next-generation (NG) systems, or simply "5G" or "NG"). It can be concluded from the 3GPP next-generation research phase that the Mobility Management (MM) function and the Session Management (SM) function (SMF) will be separated. See, for example, 3GPP TR23.799v14.0.0 (2016-12). The MM function (MMF) is also called the Access and Mobility Management Function (AMF), therefore, AMF and MMF are equivalent. Summary of the Invention

[0004] Due to the separation of AMF and SMF and the single NAS terminal in the AMF in 5G, the 5G Service Request (SR) process processing differs from that of 3G and 4G. This disclosure addresses the following issues concerning 5G SR process processing: (1) User plane (UP) establishment delay; (2) Effective NAS signaling for total PDU session synchronization between user equipment (UE) and the network; and (3) The use of general logic for processing mobile termination (MT) and mobile origination (MO) services.

[0005] It can improve the UP establishment latency in the SR process because it is not necessary to bundle UP establishment for all PDU sessions in a single SR process.

[0006] For example, in one embodiment, when a User Equipment (UE) (i.e., a device capable of wireless communication, such as a smartphone, tablet, personal computer, meter, sensor, vending machine, etc.) initiates a NAS SR, the NAS SR indicates a set of one or more PDU sessions required for the reconstructed UP (i.e., a set of one or more PDUs requiring UP resources such as data radio bearers and associated UP tunnels) and requests a separate response for each PDU session (e.g., UP establishment to the network). Each involved SMF handles the UP establishment (or UP establishment failure handling) separately for each PDU session, and the AMF will only wait for the first PDU UP establishment before proceeding with NG2 establishment; other PDU sessions are handled asynchronously by the AMF for NG2 (and NG1). In another embodiment, the AMF connects several PDU sessions used for UP establishment based on a time budget. For example, the AMF may optionally collect SMF responses for different PDU sessions and use a response returned to the UE / Radio Access Network (RAN) within a time period determined by the time budget.

[0007] For the synchronization of the "total PDU session" state between the UE and the network (i.e., synchronizing the UE view of the previously established PDU session with the network view of the previously established PDU session), NAS logic is introduced and used only when the total PDU session state is out of sync (i.e., when the UE view is different from the network view).

[0008] Additionally, in some embodiments, when a UE initiates an SR procedure in response to a paging triggered by MT service, the UE indicates the corresponding PDU session requiring UP resources (in addition to indicating the corresponding PDU session, the UE may also indicate that it has another PDU session with uplink data to be sent to the network). Therefore, in one embodiment, the AMF includes the corresponding PDU session ID (e.g., a simplified representation) in the NG2 paging request, and the UE will use this information in the SR message to indicate the PDU session requested for UP reconstruction for MT service (as mentioned above, the SR message may also include information indicating other PDU sessions, e.g., the PDU session with uplink data to be sent by the UE).

[0009] In other embodiments, when a UE initiates an SR procedure in response to a paging triggered by MT services, the UE does not indicate the corresponding PDU session that needs to be UP. Instead, based on the information it stored when it received a data notification from the SMF that triggered the paging, the AMF obtains the PDU session ID and sends an NG11 SM notification request to the SMF that sent the notification.

[0010] The advantages provided by the embodiments disclosed herein include: (1) decoupling of UP setup delays for different PDU sessions, which is advantageous for individual service delays and also achieves network slicing isolation; (2) effective PDU session state synchronization between the UE and the network (in current 3G, service acceptance is always required in PMM connection mode, while in 4G there is no service acceptance and the lower layer is always used as the response); and (3) effective service reactivation is achieved, wherein the UE and network requirements are met in a normal manner. Attached Figure Description

[0011] The accompanying drawings, which are incorporated herein and form part of this specification, illustrate various embodiments.

[0012] Figure 1 This illustrates an exemplary next-generation communication architecture;

[0013] Figure 2 This is a message flow diagram illustrating a process according to one embodiment;

[0014] Figure 3 This is a message flow diagram illustrating a process according to one embodiment;

[0015] Figure 4 This is a flowchart illustrating a process according to one embodiment;

[0016] Figure 5 This is a flowchart illustrating a process according to one embodiment;

[0017] Figure 6 This is a flowchart illustrating a process according to one embodiment;

[0018] Figure 7 This is a block diagram of the AMF according to some embodiments;

[0019] Figure 8 This is a block diagram of a UE according to some embodiments;

[0020] Figure 9 This is a flowchart illustrating a process according to one embodiment;

[0021] Figure 10 This is a schematic diagram illustrating the functional modules of the AMF according to some embodiments;

[0022] Figure 11 This is a flowchart illustrating a process according to one embodiment;

[0023] Figure 12 This is a schematic diagram illustrating the functional modules of a UE according to some embodiments;

[0024] Figure 13 This is a flowchart illustrating a process according to one embodiment;

[0025] Figure 14 This is a schematic diagram illustrating the functional modules of the AMF according to some embodiments. Detailed Implementation

[0026] As mentioned above, AMF and SMF are separate in the 5G core network. Now refer to Figure 1 , Figure 1 An exemplary 5G communication system 100 is shown. The 5G communication system 100 shows a point-to-point reference point representation.

[0027] like Figure 1 As shown, a single NG1 interface is used for MM and SM related messages and procedures for UE 102. A single NG1 termination point is located in AMF 104.

[0028] AMF 104 and SMF 106 are separate NFs (Network Functions), with a standard NG11 interface defined between them. AMF 104 handles the mobility management portion of NAS signaling exchanged with UE 102, while SMF 106 handles the session management portion of NAS signaling exchanged with UE 102.

[0029] UE 102 can have multiple established PDU sessions, and can be served by different instances of SMF 106. AMF104 selects the SMF function for the PDU session. AMF can select different SMF functions for different PDU sessions.

[0030] AMF forwards NAS information related to Session Management (SM) to SMF.

[0031] After a PDU session is successfully established, the AMF stores the identifier of the UE's serving SMF (e.g., for each established PDU session, the AMF stores information used to link the PDU session ID and SMF ID; the PDU session ID identifies the PDU session, and the SMF ID identifies the SMF handling the identified PDU session. For example, the AMF may store a record with a first field and a second field, where the first field stores the PDU session ID and the second field stores the SMF ID), and the SMF stores the identifier of the UE's serving AMF. It is not expected that the AMF will maintain any additional session context information. The AMF does not need to know the content of the SM NAS message.

[0032] If a UE has multiple established PDU sessions using multiple User Plane (UP) functions (UPFs), the 5G system supports activating UE-CN UP connections independently for each PDU session. The following MM and SM interactions are envisioned: (1) During the transition from idle to connected state, for MT data transmission, the “impact of MM event” procedure is used, while for MO data transmission, the UE indicates that the PDU session with the UE-CN UP connection must be activated during the service request procedure; (2) When the UE is in connected state, during mobility procedures (e.g., handover), only the SMF with active UE-CN UP connections is updated within the AMF; and (3) During connected state, if the UE has already activated UE-CN UP connections for a subset of active PDU sessions, the NG system supports activating additional UE-CN UP connections for further PDU sessions.

[0033] Some NG2 signaling (e.g., handover-related signaling) may require the actions of both the AMF and SMF. In this case, the AMF is responsible for ensuring coordination between the AMF and the SMF. This corresponds to the following processes: (A) the NG2 impact of SM events; and (B) the impact of MM events.

[0034] The NG2 impact of the SM event process includes: (1) during the establishment / modification / release of a PDU session and the activation / deactivation of a UE-CN UP connection, the SMF interacts with the RAN via the AMF to establish, modify, and release radio and NG3 resources for the PDU session; and (2) during the establishment / modification of QoS for GBR flows or the modification of QoS rules for non-GBR flows, the SMF interacts with the RAN via the AMF to provide QoS information.

[0035] The effects of the MM event process include: (1) When transitioning from an idle state to a connected state, the SMF that will activate the UE-CN UP connection will interact with the RAN via the AMF to establish radio and NG3 resources for the PDU session.

[0036] As mentioned above, due to the separation of AMF and SMF and the single NAS terminal in the AMF in 5G, the Service Request (SR) process differs from that in 3G and 4G. Based on the different 5G SR processes, the following issues are addressed: (1) UP setup delay in the SR process; (2) effective NAS signaling for total PDU session synchronization between the user equipment (UE) and the network; and (3) the use of common logic in the SR process for Mobile Termination (MT) and Mobile Origin (MO) service processing.

[0037] Figure 2This is a flowchart illustrating a process according to one embodiment for establishing (e.g., re-establishing) a UP (i.e., establishing a UP resource) to enable the UE to send uplink data to the UP function (UPF).

[0038] When the UE has data to send to the UPF, the UE sends a Service Request (SR) (e.g., NG1 Service Request) which includes information (e.g., a first parameter) indicating the UE's PDU sessions that require UP establishment (step 201). For example, the SR may include a first ordered group of N bits (i.e., a "bitmap"), where each of the N bits corresponds to a different one of the N possible PDU sessions that may require UP establishment (e.g., the first bit in the string corresponds to the first PDU session, the second bit in the string corresponds to the second PDU session, etc.). In some embodiments, N is equal to the total number of PDU sessions that the UE considers active (e.g., N = 3), while in other embodiments, N is equal to the total number of possible active PDU sessions in the UE (e.g., N = 16). The value of each bit in the bit string indicates whether the PDU session corresponding to that bit requires UP establishment (e.g., if bit n is set to the value 1, then PDU session #n requires UP establishment, but if bit n is set to the value 0, then PDU session #n does not require UP establishment). In this way, the UE can notify the network of the UP status of each active PDU session for the UE.

[0039] Upon receiving the SR, the AMF examines the information included in the SR (e.g., a bitmap) to determine the PDU session for which UP resources will be established, and further examines the stored information mapping the PDU sessions to SMFs to determine the SMF that will handle the PDU session for each PDU for which UP will be established (a single SMF may handle multiple PDU sessions for the UE). After identifying the SMF that will handle the PDU session for which UP will be established, the AMF sends an NG11 message (notification or request) to each of the identified SMFs (step 203).

[0040] In some embodiments, the SR sent by the UE also includes PDU session status information (e.g., a second parameter) that identifies the state of the PDU session (e.g., active or inactive) for each possible PDU session. For example, the SR may include a second bitmap of N bits, where each of the N bits corresponds to a different one of the N possible PDU sessions (e.g., the first bit in the string corresponds to PDU session #1, the second bit in the string corresponds to PDU session #2, etc.). The value of each bit in the bit string indicates the state of the PDU session corresponding to that bit (e.g., if bit n is set to the value 1, then PDU session #n is active, but if bit n is set to the value 0, then PDU session #n is inactive). In this way, the UE can notify the network of the state of each possible PDU session for the UE.

[0041] In one embodiment, upon receiving an SR, the AMF checks for any discrepancies between the PDU session state information included in the SR (e.g., indicated by a second bitmap) and the PDU session state information previously stored by the AMF. For example, the AMF itself may store information containing information about the PDU session state of each UE it serves. In step 201a, if there are out-of-sync PDU sessions (i.e., if the PDU session state information included in the SR does not match the PDU session state information maintained by the AMF), the AMF may send an NG1 response (e.g., a NAS response) to the UE to synchronize the PDU session state information. That is, if there is a mismatch between the PDU session state indicated in the SR sent by the UE and the PDU session state information maintained by the AMF for the UE, step 201a can be performed, indicating that synchronization is required. As a specific example, if the UE sends an SR containing the bitmap "0000 0000 0011 0000", this means that the UE has indicated to the network that PDU sessions 5 and 6 are active. If the PDU session state information maintained by the AMF for the UE also indicates that PDU sessions 5 and 6 are active, there is no problem. However, if the PDU session state information maintained by the AMF for the UE only indicates that PDU session 5 is active, the AMF can instruct the UE to return the bitmap "0000 0000 00010000". This will instruct the UE to make PDU session 6 inactive.

[0042] In one embodiment, the UE may start a timer to monitor responses from the RAN.

[0043] In response to the NG11 message, each SMF replies to the AMF individually with an NG11 response (steps 204a-c). The NG11 response includes an NG2 SM container (i.e., an information block), which may include core network (CN) UP tunnel information and quality of service (QoS) information for the PDU session. The NG11 response may succeed or fail.

[0044] In step 205a, upon receiving the first NG11 response from an SMF (e.g., SMF1) (step 204a), the AMF generates an NG2MM container including information about AS security and other information, and sends the NG2 MM container along with the received NG2SM container to the RAN without waiting for responses from other SMFs. For example, in step 204a, without waiting for any other responses from other SMFs to which the AMF sent NG11 notifications, the AMF sends an NG2 message (e.g., context establishment) to the RAN including the NG2 SM container and the NG2 MM container.

[0045] In an embodiment, when there is a mismatch in PDU session state information as described above that has been detected by the AMF, the NG2 MM container includes an NG1 response (e.g., a NAS response).

[0046] In steps 205b-c, the NG11 responses from SMF2 and SMF3 (see steps 204b and 204c) are sent by the AMF to the RAN and UE, respectively. That is, in step 205b, the AMF sends an NG2 message to the RAN including the NG2 SM container received from SMF2 in step 204b, and in step 205c, in response to receiving the NG11 response in step 204c, the AMF sends a NAS message to the UE. In this example, the AMF sends the NAS message to the UE in response to receiving the NG11 response in step 204c because the NG11 response received in step 204c indicates that SMF3 has lost its PDU session and failed to synchronize with the AMF (i.e., SMF3 could directly respond to the UE with an NG1 response (e.g., a NAS response).

[0047] In some embodiments, instead of immediately sending an NG2 message (e.g., context establishment) to the RAN upon receiving the first NG11 response (i.e., without waiting for any response from other SMFs to which the AMF sent the NG11 notification), the AMF may include several NG2 SM containers in an NG2 message based on a time budget. The time budget may be based on a predetermined configuration or policy. In embodiments, the time budget may be based on learning the criticality of applications and / or services in a PDU session. For example, the AMF may activate a timer to expire after X seconds (X being the time budget), and when the timer expires, the AMF may send an NG2 message to the RAN containing an NG2MM container and each of the NG2 SM containers received by the AMF before the timer expires. The AMF may activate the timer immediately after sending the first NG11 notification, or it may activate the timer immediately after receiving the first NG11 response.

[0048] In step 206, the RAN sends an NG2 context establishment response to establish an UP for each PDU session individually. The NG2 context establishment response includes an NG2 SM container and information about the Access Network (AN) UP tunnel. In an embodiment, based on the response time measured by a timer, the UE takes further action to monitor the response from the RAN. If the AMF includes two or more NG2 SM containers in the NG2 message sent to the RAN (e.g., from different SMFs), the RAN may only send an NG2 response including the corresponding two or more NG2 containers (at the NG2 and N11 interfaces, if the requesting node sends several items in a request, the receiving node will respond with several corresponding items in a response), and for each NG2 container included in the NG2 response, the AMF sends the NG2 container to the appropriate SMF.

[0049] In step 207, the AMF forwards an NG2 context establishment response, including the radio access network, by sending an NG11 request to the appropriate SMF.

[0050] Figure 3 This is a message flow diagram illustrating a process according to some embodiments for re-establishing the UP from the UE to the network in response to a paging and service request triggered by MT data.

[0051] In step 301, UPF 112 receives downlink (DL)UP data for UE 102.

[0052] In step 302, UPF 112 sends a DL UP data notification message to SMF 106 to notify SMF 106 that UPF 112 has received DL UP data for UE 102.

[0053] In step 303, SMF 106 sends an UP establishment request to AMF 104.

[0054] In step 304, it is determined whether the UE is in “CN-IDLE” mode, and if so, the AMF triggers paging of the UE (i.e., triggers the sending of a paging message to the UE). In one embodiment, the AMF 104 includes PDU session identification information in the paging message sent to the UE to identify the PDU session for which the UP was established (i.e., information to identify which PDU session has MT data). In some embodiments, the AMF determines the PDU session identification information based on the SMF it receives from the UP establishment request. For example, in some embodiments, the AMF may store context information of the UE used for its services, and the context information may include information mapping the PDU session identifier to the SMF identifier.

[0055] In step 305, in response to receiving a paging message, the UE performs the SR procedure (sends an SR to the AMF). As described above, the SR may include information identifying the state of a PDU session for each possible PDU session (e.g., the second bitmap as described above). Additionally, if the AMF includes PDU session identification information in the paging message that identifies one or more PDU sessions with DL UP data for the UE, the UE may also include in the SR PDU session identification information for identifying the PDU session identified in the paging message (e.g., the PDU session identification information may be the first bitmap as described above). Furthermore, if the UE has uplink (UL) UP service on other PDU sessions at the same time the UE receives the paging message, the UE may also include in the SR information indicating that these other PDU sessions require UP establishment (e.g., if the UE has UL UP data on PDU session #3, the UE may set the bit corresponding to PDU session #3 in the first bitmap to a value of 1).

[0056] The remainder of the process is similar to the service request flow triggered by the UE, such as in Figure 2 As shown in the image.

[0057] In another embodiment, the AMF does not include PDU session identification information in the paging message sent to the UE. Instead, when receiving an SR from the UE, the AMF can associate the SMF / PDU session based on the UE identifier.

[0058] For example, when the AMF receives a request from the SMF indicating a PDU session for a specific UE (e.g., PDU session #1) and further indicating an SMF ID (e.g., SMF-ID 1), the AMF can store a record in a database (e.g., a file) with a first field, a second field, and a third field, where the first field contains a UE identifier for identifying the specific UE, the second field stores information identifying the PDU session, and the third field stores the SMF ID. Therefore, when the AMF receives an SR including the UE's ID from the UE, the AMF can retrieve a record from the database using the UE's ID and then obtain the PDU session ID and SMF ID from that record. Once the AMF has obtained the PDU session ID and SMF ID from the record, it can now send an NG11 message (e.g., a notification including the PDU session ID) to the SMF identified by the SMF ID. If the database contains more than one record (where the same UE ID is present in the UE ID field), the AMF can send an appropriate NG11 message to each of the identified SMFs.

[0059] Figure 4 This is a flowchart illustrating a process 400 according to one embodiment, which is performed by the AMF for message processing (e.g., service request processing).

[0060] Process 400 may begin at step 402, wherein the AMF receives a first message (e.g., a service request) sent by the UE, wherein the first message includes information (e.g., a first bit diagram) that identifies: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP.

[0061] In step 404, the AMF identifies the first SMF associated with the first PDU session.

[0062] In step 406, the AMF identifies the second SMF associated with the second PDU session.

[0063] In step 408, as a result of identifying the first SMF, the AMF sends a second message (e.g., NG11 notification / request) to the first SMF.

[0064] In step 410, as a result of identifying the second SMF, the AMF sends a third message (e.g., NG11 notification / request) to the second SMF.

[0065] In step 412, the AMF receives a response sent by the first SMF in response to the second message, wherein the response sent by the first SMF includes a first session management (SM) container (i.e., a set of SM information) for the access node (108) serving the UE.

[0066] In step 414, upon receiving a response from the first SMF, the AMF immediately (i.e., without waiting for any response from the second SMF) sends a message to the access node. This message includes a) a mobility management (MM) container; and b) a first SM container received from the first SMF.

[0067] In some embodiments, after sending a message to the access node including a) a mobility management (MM) container and b) a first SM container received from the first SMF, the AMF receives a response sent by the access node. The response sent by the access node includes Radio Access Network (RAN) UP information for the first SMF. Upon receiving the response from the access node, the AMF forwards the RAN UP information to the first SMF. The RAN UP information enables the first SMF to transmit RAN UP information to the UP function (UPF) for use in the first PDU session.

[0068] In some embodiments, the first SM container includes information indicating a first core network (CN) UP tunnel and a first quality of service (QoS).

[0069] In some embodiments, process 400 further includes steps 416 and 418.

[0070] In step 416, after sending a message to the access node, the AMF receives a response sent by the second SMF in response to the third message. The response sent by the second SMF includes a second SM container for the access node serving the UE.

[0071] In step 418, after receiving the response sent by the second SMF, the AMF sends a message to the access node including the second SM container received from the second SMF.

[0072] In some embodiments, after sending a message to the access node including a second SM container received from the second SMF, the AMF receives a response sent by the access node. The response sent by the access node includes Radio Access Network (RAN) UP information for the second SMF. Upon receiving the response from the access node, the AMF forwards the RAN UP information to the second SMF. The RAN UP information enables the second SMF to transmit RAN UP information to the UP function (UPF) for use in the second PDU session.

[0073] In some embodiments, the second SM container includes information indicating a second CN UP tunnel and a second QoS.

[0074] Figure 5 This is a flowchart illustrating a process 500 according to one embodiment, which is performed by the AMF for message processing (e.g., service request processing).

[0075] Process 500 may begin at step 502, wherein the AMF receives a first message (e.g., a service request) sent by the UE, wherein the first message includes information (e.g., a first bit diagram) that identifies: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP.

[0076] In step 504, the AMF identifies the first session management function (SMF) associated with the first PDU session.

[0077] In step 506, the AMF identifies the second SMF associated with the second PDU session.

[0078] In step 508, as a result of identifying the first SMF, the AMF sends a second message (e.g., NG11 notification / request) to the first SMF.

[0079] In step 510, as a result of identifying the second SMF, the AMF sends a third message (e.g., NG11 notification / request) to the second SMF.

[0080] In step 512, the AMF sets a timer. The AMF may also initialize a counter (e.g., set i = 0) to keep track of the number of SMF responses received by the AMF. In one embodiment, the timer is set based on a predetermined configuration and policy. In another embodiment, the timer is set based on the criticality level of the applications and services in the first PDU session and the second PDU session.

[0081] In step 514, the AMF determines whether it has received a response to one of the messages sent in steps 508 and 510. If no response has been received, process 500 proceeds to step 522; otherwise, if a response is received, process 500 proceeds to step 516.

[0082] In step 516, reached when the AMF receives a response to one of the messages sent in steps 508 and 510, the AMF increments a counter (e.g., calculates i = i + 1). The received response (e.g., a response sent by the first or second SMF) includes a Session Management (SM) container for the UE's access node.

[0083] In step 518, the AMF determines whether i is equal to the variable N, where N indicates the number of SMFs from which it can receive responses. If i = N, process 500 proceeds to step 519 (i.e., all expected responses have been received); otherwise, process 500 proceeds to step 522. In this embodiment, N = 2 because responses can be received from both the first and second SMFs. In another embodiment, N can be any number based on the number of SMFs from which responses can be received.

[0084] In step 519, the AMF disables the timer.

[0085] In step 522, the AMF determines whether the timer has expired. If the timer has not expired, process 500 returns to step 514; otherwise, process 500 continues to step 524.

[0086] In step 524, AMF determines whether i = 0. If i = 0, process 500 continues to step 526; otherwise, process 500 continues to step 520.

[0087] In step 526, the AMF indicates an error.

[0088] In step 520, the AMF sends a message to the access node. For each SMF response received at that time point, the message sent in step 520 includes the SM container included in the response. For example, the AMF may receive only one SMF response (e.g., a response sent by the first SMF). In this case, the AMF sends a message to the access node that includes: a) a Mobility Management (MM) container; and b) the SM container received from the first SMF. As another example, the AMF may receive a first response sent by the first SMF and also receive a second response sent by the second SMF before the timer expires, wherein the first response includes the first SM container and the second response includes the second SM container. In this case, the message sent by the AMF to the access node in step 520 will include: a) a Mobility Management (MM) container; b) the first SM container received from the first SMF; and c) the second SM container received from the second SMF.

[0089] In some embodiments of method 400 and / or 500, the first message further includes PDU session state information (e.g., a second bitmap) that identifies the state of the PDU session for each possible PDU session. In this embodiment, the method may further include: acquiring previously stored PDU session state information for the UE; determining whether the PDU session state information contained in the first message matches the acquired PDU state information for the UE; and in response to determining that the PDU session state information contained in the first message does not match the acquired PDU state information for the UE, sending a PDU session state synchronization message (e.g., an NG1 message) to the UE to synchronize the PDU session state information.

[0090] Figure 6 This is a flowchart illustrating a process 600 according to one embodiment, which is performed by the AMF for message processing (e.g., service request processing).

[0091] Process 600 may begin at step 602, wherein the AMF receives a first message (e.g., an NG11 request) sent by the Session Management Function (SMF) in response to a notification that downlink (DL) data for a User Equipment (UE) has been received. The UE has at least one PDU session, the DL data is associated with a specific PDU session within the UE's PDU session, and the first message includes information indicating a request to establish UP.

[0092] In step 604, in response to receiving the first message, the AMF sends a paging message to the UE via the access node, wherein the paging message includes information indicating the specific PDU session in the UE's PDU session.

[0093] Figure 7 This is a block diagram of AMF 104 according to some embodiments. For example... Figure 7As shown, AMF 104 may include: a data processing system (DPS) 702, which may include one or more processors 755 (e.g., a general-purpose microprocessor and / or one or more other processors, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.); a network interface 705 for connecting the AMF to a network so that the AMF 102 can communicate with other described functions (e.g., SMFs) and RAN 108; and a local storage unit (also referred to as a “data storage system”) 712, which may include one or more non-volatile storage devices and / or one or more volatile storage devices (e.g., random access memory (RAM)). In embodiments where the AMF 104 includes a general-purpose microprocessor, a computer program product (CPP) 741 may be provided. The CPP 741 includes a computer-readable medium (CRM) 742 storing a computer program (CP) 743, which includes computer-readable instructions (CRI) 744. CRM742 may be a non-transitory computer-readable medium, such as, but not limited to, magnetic media (e.g., hard disk), optical media (e.g., DVD), memory devices (e.g., random access memory), etc. In some embodiments, CRI 744 of computer program 743 is configured such that when executed by data processing system 702, CRI causes AMF to perform the steps described above (e.g., the steps described in the above-mentioned reference flowchart). In other embodiments, AMF may be configured to perform the steps described herein without code. That is, for example, data processing system 702 may consist of only one or more ASICs. Therefore, the features of the embodiments described herein may be implemented in hardware and / or software.

[0094] Figure 8 This is a block diagram of UE 102 according to some embodiments. For example... Figure 8As shown, UE 102 may include: a data processing system (DPS) 802, which may include one or more processors 855 (e.g., a general-purpose microprocessor and / or one or more other processors, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.); a radio transmitter 805 and a radio receiver 806 coupled to an antenna 822 for wireless communication with a radio access network (RAN) node (e.g., a TRP); and a local storage unit (also referred to as a “data storage system”) 812, which may include one or more non-volatile storage devices and / or one or more volatile storage devices (e.g., random access memory (RAM)). In embodiments where UE 102 includes a general-purpose microprocessor, a computer program product (CPP) 841 may be provided. CPP 841 includes a computer-readable medium (CRM) 842 storing a computer program (CP) 843, the computer program (CP) 843 including computer-readable instructions (CRI) 844. 842 may be a non-transitory computer-readable medium, such as, but not limited to, magnetic media (e.g., hard disk), optical media (e.g., DVD), memory devices (e.g., random access memory), etc. In some embodiments, the CRI 844 of the computer program 843 is configured such that when executed by the data processing system 802, the CRI causes the UE 102 to perform the steps described above (e.g., the steps described in the above-mentioned reference flowchart). In other embodiments, the UE 102 may be configured to perform the steps described herein without code. That is, for example, the data processing system 802 may consist of only one or more ASICs. Therefore, the features of the embodiments described herein may be implemented in hardware and / or software.

[0095] Brief description of various disclosed embodiments

[0096] I. Mobile Origin (MO) Service Request Processing

[0097] A1. A method (400) for message processing (e.g., service request processing) executed by an AMF (104), comprising:

[0098] Receive (402) a first message (e.g., a service request) sent by a user equipment (UE) (102), wherein the first message includes information (e.g., a first bit diagram) that identifies: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP;

[0099] Identify (404) the first SMF associated with the first PDU session;

[0100] Identify (406) the second SMF associated with the second PDU session;

[0101] As a result of identifying (404) the first SMF, send (408) a second message (e.g., NG11 notification / request) to the first SMF;

[0102] As a result of identifying (406) the second SMF, send (410) a third message (e.g., NG11 notification / request) to the second SMF;

[0103] Receive (412) a response sent by the first SMF in response to the second message, wherein the response sent by the first SMF includes a first session management (SM) container for serving the access node (108) of the UE; and

[0104] Upon receiving the response sent by the first SMF, a message (414) is immediately sent to the access node, the message including: a) a mobility management (MM) container; and b) the first SM container received from the first SMF.

[0105] A2. The method (400) according to embodiment A1 further includes:

[0106] After sending the message (414) to the access node, a response (416) is received by the second SMF in response to the third message, wherein the response sent by the second SMF includes a second session management (SM) container of the access node (108) for serving the UE (102); and

[0107] After receiving (416) the response sent by the second SMF, a message including the second SM container received from the second SMF is sent (418) to the access node (102).

[0108] A3. The method (400) according to embodiment A1 or A2, wherein the first message further includes PDU session state information (e.g., a second bitmap), the PDU session state information identifying the state of the PDU session for each possible PDU session.

[0109] A4. The method (400) according to embodiment A3 further includes:

[0110] Obtain the previously stored PDU session state information for the UE (102);

[0111] Determine whether the PDU session state information contained in the first message matches the acquired PDU state information for the UE (102).

[0112] A5. The method (400) according to embodiment A4 further includes:

[0113] In response to determining that the PDU session state information contained in the first message does not match the acquired PDU state information for the UE (102), a PDU session state synchronization message (e.g., NG1 message) is sent to the UE (102) to synchronize the PDU session state information.

[0114] A6. The method (400) according to embodiments A1-A5 further includes:

[0115] After sending the message to the access node including a) the mobility management (MM) container and b) the first SM container received from the first SMF, a response sent by the access node (108) is received, wherein the response sent by the access node (108) includes radio access network (RAN) UP information for the first SMF.

[0116] A7. The method (400) according to embodiment A6 further includes:

[0117] The RAN UP information is forwarded to the first SMF, wherein the RAN UP information enables the first SMF to transmit the RAN UP information to the UP function (UPF) for use in the first PDU session.

[0118] A8. The method (400) according to any one of embodiments A2-A7 further includes:

[0119] After sending the message to the access node (108) including the second SM container received from the second SMF, a response sent by the access node (108) is received, wherein the response sent by the access node (108) includes Radio Access Network (RAN) UP information for the second SMF.

[0120] A9. The method (400) according to embodiment A8 further includes:

[0121] The RAN UP information is forwarded to the second SMF, wherein the RAN UP information enables the second SMF to transmit the RAN UP information to the UP function (UPF) for use in the second PDU session.

[0122] A10. The method (400) according to any one of the above embodiments, wherein the information in the SR that identifies the first PDU session and the second PDU session for which UP is to be established includes a bitmap, the bitmap including at least a first bit corresponding to the first PDU session and a second bit corresponding to the second PDU session.

[0123] A11. The method (400) according to any one of the above embodiments, wherein the first SM container includes information indicating a first core network (CN) user plane (UP) tunnel and a first quality of service (QoS), and wherein the second SM container includes information indicating a second CN UP tunnel and a second QoS.

[0124] B1. An AMF (104) for message processing (e.g., service request processing), said AMF (104) being adapted to:

[0125] Receive (402) a first message (e.g., a service request) sent by a user equipment (UE) (102), wherein the first message includes information (e.g., a first bit diagram) that identifies: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP;

[0126] Identify (404) the first SMF associated with the first PDU session;

[0127] Identify (406) the second SMF associated with the second PDU session;

[0128] As a result of identifying (404) the first SMF, send (408) a second message (e.g., NG11 notification / request) to the first SMF;

[0129] As a result of identifying (406) the second SMF, send (410) a third message (e.g., NG11 notification / request) to the second SMF;

[0130] Receive (412) a response sent by the first SMF in response to the second message, wherein the response sent by the first SMF includes a first session management (SM) container for serving the access node (108) of the UE; and

[0131] Upon receiving the response sent by the first SMF, a message (414) is immediately sent to the access node, the message including: a) a mobility management (MM) container; and b) the first SM container received from the first SMF.

[0132] C1. An AMF (104) for message processing (e.g., service request processing), said AMF (104) comprising:

[0133] The first acquisition module (1002) is configured to acquire via a receiver a first message (e.g., a service request) sent by a user equipment UE (102), wherein the first message includes information (e.g., a first bit diagram) indicating: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP;

[0134] The first identification module (1004) is configured to identify (404) the first SMF associated with the first PDU session;

[0135] The second identification module (1006) is configured to identify (406) the second SMF associated with the second PDU session;

[0136] The first sending module (1008) is configured to send (408) a second message (e.g., NG11 notification / request) to the first SMF as a result of identifying (404) the first SMF;

[0137] The second sending module (1010) is configured to send (410) a third message (e.g., NG11 notification / request) to the second SMF as a result of identifying (406) the second SMF;

[0138] The second acquisition module (1012) is configured to acquire, via a receiver, a response sent by the first SMF in response to the second message, wherein the response sent by the first SMF includes a first session management (SM) container for serving the access node (108) of the UE; and

[0139] The third sending module (1014) is configured to immediately send a message (414) to the access node using a transmitter after receiving the response sent by the first SMF, the message including: a) a mobility management (MM) container; and b) the first SM container received from the first SMF.

[0140] B / C2a. The AMF(104) according to Example B1 is further adapted to:

[0141] After sending the message (414) to the access node, a response (416) is received by the second SMF in response to the third message, wherein the response sent by the second SMF includes a second session management (SM) container of the access node (108) for serving the UE (102); and

[0142] After receiving (416) the response sent by the second SMF, a message including the second SM container received from the second SMF is sent (418) to the access node (102).

[0143] B / C2b. According to Example C1, the AMF (104) further includes:

[0144] After the transmitter sends the message to the access node, the third obtaining module (1018) is configured to obtain, via the receiver, a response sent by the second SMF in response to the third message, wherein the response sent by the second SMF includes a second session management (SM) container of the access node (108) for serving the UE (102); and

[0145] After receiving the response sent by the second SMF via the receiver, the fourth sending module is configured to send a message to the access node (108) including the second SM container received from the second SMF.

[0146] B / C3. The AMF (104) according to any one of the above AMF embodiments, wherein the first message further includes PDU session state information (e.g., a second bitmap), the PDU session state information identifying the state of the PDU session for each possible PDU session.

[0147] B / C4. The AMF (104) according to embodiment B / C3, wherein the AMF (104) is further adapted to: acquire previously stored PDU session state information for the UE (102); and determine whether the PDU session state information contained in the first message matches the acquired PDU state information for the UE (102);

[0148] or,

[0149] The AMF (104) further includes: a first acquisition module (1022) configured to acquire previously stored PDU session state information for the UE (102); and a first determination module (1024) configured to determine whether the PDU session state information contained in the first message matches the acquired PDU state information for the UE (102).

[0150] B / C5. The AMF according to embodiment B / C4, wherein the AMF (104) is further adapted to: in response to determining that the PDU session state information contained in the first message does not match the acquired PDU state information for the UE (102), send a PDU session state synchronization message (e.g., NG1 message) to the UE (102) to synchronize the PDU session state information;

[0151] or,

[0152] The AMF (104) further includes a fifth transmitting module (1028) configured to, in response to determining that the PDU session state information contained in the first message does not match the acquired PDU state information for the UE (102), use a transmitter to send a PDU session state synchronization message (e.g., an NG1 message) to the UE (102) to synchronize the PDU session state information.

[0153] B / C6. The AMF (104) according to any one of the above AMF embodiments, wherein the AMF (104) is further adapted to:

[0154] After sending the message to the access node including a) the mobility management (MM) container and b) the first SM container received from the first SMF, a response sent by the access node is received, wherein the response sent by the access node includes radio access network (RAN) UP information for the first SMF.

[0155] B / C7. The AMF (104) according to embodiment B / C6, wherein the AMF (104) is further adapted to: forward the RAN UP information to the first SMF, wherein the RAN UP information enables the first SMF to transmit the RAN UP information to the UP function (UPF) for the first PDU session.

[0156] B / C8. The AMF (104) according to any one of the above AMF embodiments, wherein the AMF (104) is further adapted to: after sending the message to the access node (108) including the second SM container received from the second SMF, receive a response sent by the access node (108), wherein the response sent by the access node (108) includes radio access network (RAN) UP information for the second SMF.

[0157] B / C9. The AMF (104) according to embodiment B / C8, wherein the AMF (104) is further adapted to:

[0158] The RAN UP information is forwarded to the second SMF, wherein the RAN UP information enables the second SMF to transmit the RAN UP information to the UP function (UPF) for use in the second PDU session.

[0159] B / C10. The AMF (104) according to any one of the above AMF embodiments, wherein the information in the service request SR that identifies the first PDU session and the second PDU session for which an UP is to be established includes a bitmap, the bitmap including at least a first bit corresponding to the first PDU session and a second bit corresponding to the second PDU session.

[0160] B / C11. The AMF (104) according to any one of the above AMF embodiments, wherein the first SM container includes information indicating a first core network (CN) user plane (UP) tunnel and a first quality of service (QoS), and wherein the second SM container includes information indicating a second CN UP tunnel and a second QoS.

[0161] D1. A method (500) for message processing (e.g., service request processing) executed by an AMF (104), comprising:

[0162] Receive (502) a first message (e.g., a service request) sent by a user equipment (UE) (102), wherein the first message includes information (e.g., a first bit diagram) that identifies: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP;

[0163] Identify (504) the first SMF associated with the first PDU session;

[0164] Identify (506) the second SMF associated with the second PDU session;

[0165] As a result of identifying (504) the first SMF, send (508) a second message (e.g., NG11 notification / request) to the first SMF;

[0166] As a result of identifying (506) the second SMF, a third message (e.g., NG11 notification / request) is sent to the second SMF (510);

[0167] Set timer (512);

[0168] Receive (512) a response sent by the first SMF in response to the second message, wherein the response sent by the first SMF includes a first session management (SM) container for the access node (108) serving the UE (102); and

[0169] When the timer expires, a message (520) is sent to the access node (108), the message including: a) a mobility management (MM) container; and b) the first SM container received from the first SMF.

[0170] D2. According to the method (500) of embodiment D1, the method (500) further includes:

[0171] Before the timer expires, a response sent by the second SMF in response to the third message is received, wherein the response sent by the second SMF includes a second session management (SM) container for the access node (108) serving the UE (102); and

[0172] When the timer expires, a message (520) is sent to the access node (108), the message including: a) a mobility management (MM) container; b) the first SM container received from the first SMF; and c) the second SM container received from the second SMF.

[0173] D3. The method (500) according to embodiment D1 or D2, wherein the timer is set based on a predetermined configuration and strategy.

[0174] D4. The method (500) according to any one of embodiments D1 to D3, wherein the timer is set based on the criticality level of the applications and services in the first PDU session and the second PDU session.

[0175] D5. The method (500) according to any one of embodiments D1-D4, wherein the first message further includes PDU session state information (e.g., a second bitmap), the PDU session state information identifying the state of the PDU session for each possible PDU session.

[0176] D6. The method (500) according to embodiment D5 further includes:

[0177] Obtain the previously stored PDU session state information for the UE (102);

[0178] Determine whether the PDU session state information contained in the first message matches the acquired PDU state information for the UE (102).

[0179] D7. The method (500) according to embodiment D6 further includes:

[0180] In response to determining that the PDU session state information contained in the first message does not match the acquired PDU state information for the UE (102), a PDU session state synchronization message (e.g., NG1 message) is sent to the UE (102) to synchronize the PDU session state information.

[0181] D8. The method (500) according to any one of embodiments D1-D7, wherein the information in the SR that identifies the first PDU session and the second PDU session for which UP is to be established includes a bitmap, the bitmap including at least a first bit corresponding to the first PDU session and a second bit corresponding to the second PDU session.

[0182] E1. An AMF (104) for message processing (e.g., service request processing), said AMF (104) being adapted to:

[0183] Receive (502) a first message (e.g., a service request) sent by a user equipment (UE) (102), wherein the first message includes information (e.g., a first bit diagram) that identifies: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP;

[0184] Identify (504) the first SMF associated with the first PDU session;

[0185] Identify (506) the second SMF associated with the second PDU session;

[0186] As a result of identifying (504) the first SMF, send (508) a second message (e.g., NG11 notification / request) to the first SMF;

[0187] As a result of identifying (506) the second SMF, a third message (e.g., NG11 notification / request) is sent to the second SMF (510);

[0188] Set timer (512);

[0189] Receive (512) a response sent by the first SMF in response to the second message, wherein the response sent by the first SMF includes a first session management (SM) container for the access node (108) serving the UE (102); and

[0190] When the timer expires, a message (520) is sent to the access node (108), the message including: a) a mobility management (MM) container; and b) the first SM container received from the first SMF.

[0191] F1. An AMF (104) for message processing (e.g., service request processing), said AMF (104) comprising:

[0192] The first acquisition module (1002) is configured to acquire via a receiver a first message (e.g., a service request) sent by a user equipment UE (102), wherein the first message includes information (e.g., a first bit diagram) indicating: i) a first PDU session to be established for UP; and ii) a second PDU session to be established for UP;

[0193] The first identification module (1004) is configured to identify the first session management function (SMF) associated with the first PDU session;

[0194] The second identification module (1006) is configured to identify the second SMF associated with the second PDU session;

[0195] The first transmitting module (1008) is configured to send a second message (e.g., NG11 notification / request) to the first SMF using a transmitter as a result of identifying the first SMF;

[0196] The second transmitting module (1010) is configured to send a third message (e.g., NG11 notification / request) to the second SMF using a transmitter as a result of identifying the second SMF;

[0197] The first setting module (1016) is used to set the timer;

[0198] The second acquisition module (1012) is configured to acquire, via a receiver, a response sent by the first SMF in response to the second message, wherein the response sent by the first SMF includes a first session management (SM) container for serving the access node (108) of the UE (102); and

[0199] The third sending module (1014) is configured to send a message to the access node (108) when the timer expires, the message including: a) a mobility management (MM) container; and b) the first SM container received from the first SMF.

[0200] E / F2. According to embodiment E1 or F1, the AMF (104) is further adapted to:

[0201] Before the timer expires, a response sent by the second SMF in response to the third message is received, wherein the response sent by the second SMF includes a second session management (SM) container for the access node (108) serving the UE (102); and

[0202] When the timer expires, a message (520) is sent to the access node (108), the message including: a) a mobility management (MM) container; b) the first SM container received from the first SMF; and c) the second SM container received from the second SMF.

[0203] E / F3. The AMF (104) according to embodiments E1-E2 or F1-F2, wherein the timer is set based on a predetermined configuration and strategy.

[0204] E / F4. The AMF (104) according to embodiments E1-E2 or F1-F2, wherein the timer is set based on the criticality level of the applications and services in the first PDU session and the second PDU session.

[0205] II. Mobile Termination (MT) Service Request

[0206] G1. A method (600) for message processing (e.g., service request processing) executed by an AMF (104), comprising:

[0207] The receiver (602) receives a first message (e.g., an NG11 request) sent by the Session Management Function (SMF) in response to a notification received by the SMF that downlink (DL) data for the User Equipment (UE) (102) has been received, wherein the UE (102) has at least one PDU session, the DL data is associated with a specific PDU session in the UE (102)'s PDU sessions, and the first message includes information indicating a request to establish a User Plane (UP); and

[0208] In response to receiving (602) the first message, a paging message (108) is sent to the UE (102) via the access node (108), wherein the paging message includes information indicating the specific PDU session in the PDU session of the UE (102).

[0209] H1. An AMF (104) for message processing (e.g., service request processing), said AMF (104) being adapted to:

[0210] The receiver (602) receives a first message (e.g., an NG11 request) sent by the Session Management Function (SMF) in response to a notification received by the SMF that downlink (DL) data for the User Equipment (UE) (102) has been received, wherein the UE (102) has at least one PDU session, the DL data is associated with a specific PDU session in the UE (102)'s PDU sessions, and the first message includes information indicating a request to establish a User Plane (UP); and

[0211] In response to receiving (602) the first message, a paging message (108) is sent to the UE (102) via the access node (108), wherein the paging message includes information indicating the specific PDU session in the PDU session of the UE (102).

[0212] 11. An AMF (104) for message processing (e.g., service request processing), said AMF (104) comprising:

[0213] The first obtaining module (1002) is configured to obtain via a receiver a first message (e.g., an NG11 request) sent by a Session Management Function (SMF) in response to a notification received by the SMF that downlink (DL) data for a User Equipment (UE) (102) has been received, wherein the UE (102) has at least one PDU session, the DL data is associated with a specific PDU session in the UE's (102) PDU sessions, and the first message includes information indicating a request to establish a User Plane (UP); and

[0214] A first transmitting module (1008) is configured to, in response to receiving (602) the first message, send a (108) paging message to the UE (102) via an access node (108) using a transmitter, wherein the paging message includes information indicating the specific PDU session in the PDU session of the UE (102).

[0215] J1. A method (1100) for message processing (e.g., service request processing) executed by an AMF (104), comprising:

[0216] The receiving (1102) is a first message (e.g., an NG11 request) sent by the SMF in response to a notification that the SMF has received DL data for the user equipment (UE) (102) that it has been received, wherein the UE (102) has at least one PDU session, the DL data is associated with a specific PDU session in the UE (102)'s PDU sessions, and the first message includes information indicating a request to establish a user plane (UP); and

[0217] In response to receiving (1102) the first message:

[0218] Storage (1104) records, the records including: i) an SMF identifier for identifying the SMF; and ii) a PDU session identifier for identifying the specific PDU session, wherein the records are mapped to a UE identifier for identifying the UE (102); and

[0219] A paging message (1106) is sent to the UE (102) via the access node (108), wherein the paging message does not include information indicating the specific PDU session in the PDU session of the UE (102).

[0220] J2. The method (1100) according to embodiment J1 further includes:

[0221] Receive the SR sent by the UE (102); and

[0222] The response received the SR:

[0223] Use the UE identifier to obtain the stored SMF identifier and PDU session identifier; and

[0224] After obtaining the identifier, a message (e.g., an NG11 message including the PDU session identifier) ​​is sent to the SMF identified by the SMF identifier.

[0225] K1. An AMF(104) suitable for:

[0226] The receiving (1102) is a first message (e.g., an NG11 request) sent by the SMF in response to a notification that the SMF has received DL data for the user equipment (UE) (102) that it has been received, wherein the UE (102) has at least one PDU session, the DL data is associated with a specific PDU session in the UE (102)'s PDU sessions, and the first message includes information indicating a request to establish a user plane (UP); and

[0227] In response to receiving (1102) the first message:

[0228] Storage (1104) records, the records including: i) an SMF identifier for identifying the SMF; and ii) a PDU session identifier for identifying the specific PDU session, wherein the records are mapped to a UE identifier for identifying the UE (102); and

[0229] A paging message (1106) is sent to the UE (102) via the access node (108), wherein the paging message does not include information indicating the specific PDU session in the PDU session of the UE (102).

[0230] K2. The AMF(104) according to embodiment K1, wherein the AMF(104) is further adapted to:

[0231] Receive the SR sent by the UE (102); and

[0232] The response received the SR:

[0233] Use the UE identifier to obtain the stored SMF identifier and PDU session identifier; and

[0234] After obtaining the identifier, a message (e.g., an NG11 message including the PDU session identifier) ​​is sent to the SMF identified by the SMF identifier.

[0235] L1. An AMF (104), comprising:

[0236] A first acquisition module (1002) is configured to acquire, via a receiver, a first message (e.g., an NG11 request) sent by an SMF in response to a notification received by the SMF that DL data for a user equipment (UE) (102) has been received, wherein the UE (102) has at least one PDU session, the DL data is associated with a specific PDU session in the UE's (102) PDU sessions, and the first message includes information indicating a request to establish a user plane (UP); and

[0237] In response to receiving the first message:

[0238] A first storage module (1026) is configured to store (1104) records including: i) an SMF identifier for identifying the SMF; and ii) a PDU session identifier for identifying the specific PDU session, wherein the record is mapped to a UE identifier for identifying the UE (102); and

[0239] The first transmitting module (1008) is configured to use a transmitter to send a paging message to the UE (102) via the access node (108), wherein the paging message does not include information indicating the specific PDU session in the PDU session of the UE (102).

[0240] L2. The AMF (104) according to embodiment L1 further includes:

[0241] The second acquisition module (1012) is configured to acquire the SR transmitted by the UE (102) via a receiver; and

[0242] In response to receiving the SR:

[0243] The first acquisition module (1022) is configured to use the UE identifier to acquire the stored SMF identifier and PDU session identifier; and

[0244] The second sending module (1010) is configured to send a message (e.g., an NG11 message including the PDU session identifier) ​​to the SMF identified by the SMF identifier after obtaining the identifier.

[0245] III. UE Implementation

[0246] M1. A method (900, see) performed by a user equipment (UE) (102). Figure 9 ),include:

[0247] It is determined that (902) will establish the first PDU session for UP;

[0248] Generate (904)SR; and

[0249] Send the SR (906) to the AMF.

[0250] Generating the SR includes including information in the SR indicating that the determined first PDU session is a PDU session for which UP will be established.

[0251] M2. The method (900) according to embodiment M1, wherein determining the PDU session for which the UP is to be established includes:

[0252] Receive a paging message including PDU session identification information for identifying the first PDU session; and

[0253] The PDU session identifier information is obtained from the paging message.

[0254] M3. The method (900) according to embodiment M2 further includes:

[0255] It has been determined that a second PDU session for the UP will be established.

[0256] The generation of the SR further includes: including information in the SR indicating that the determined second PDU session is a PDU session for which UP will be established.

[0257] M4. The method (900) according to embodiment M3, wherein determining the second PDU session includes: determining a PDU session for the UE (102) having uplink UL UP data to be sent to the receiver.

[0258] M5. The method (900) according to embodiment M1, wherein determining the first PDU session includes: determining a PDU session for the UE (102) having UL UP data to be sent to the receiver.

[0259] M6. The method (900) according to embodiment M5, wherein the SR includes information indicating that the determined first PDU session is a PDU session for which UP is to be established, including: the SR includes a bitmap, wherein one bit of the bitmap corresponds to the first PDU session, and the bit corresponding to the first PDU session is set to the value 1.

[0260] N1. A user equipment (UE) (102), said UE (102) being adapted to:

[0261] Determine which UP's first PDU session will be established for it;

[0262] Generate SR; and

[0263] Send the SR to AMF,

[0264] The UE is adapted to generate the SR by performing a process that includes the following operations: the SR includes information indicating that the determined first PDU session is a PDU session for which UP will be established.

[0265] O1. A user equipment (UE) (102), the UE (102) comprising:

[0266] The determination module (1202) is used to determine the first PDU session for which a UP will be established;

[0267] SR generation module (1204), used to generate SR; and

[0268] SR transmission module (1206), used to transmit the SR to the AMF using a transmitter.

[0269] The SR generation module is configured to generate the SR by performing a process that includes the following operations: the SR includes information indicating that the determined first PDU session is a PDU session for which UP will be established.

[0270] IV. PDU Session State Synchronization

[0271] P1. A method (1300) for PDU session synchronization, comprising:

[0272] Receive (1302) a message sent by UE (102), the message including PDU session state information (e.g., bitmap), the PDU session state information identifying a group or more PDU sessions that the UE considers to be active;

[0273] In response to receiving the message, obtain (1304) the previously stored PDU session state information for the UE;

[0274] Determine (1306) whether the PDU session state information contained in the received message matches the acquired PDU state information for the UE; and

[0275] In response to determining that the PDU session state information in the received message does not match the obtained PDU state information for the UE, a (1308) PDU session state synchronization message (e.g., NG1 message) is sent to the UE to synchronize the PDU session state information.

[0276] P2. The method according to embodiment P1, wherein the PDU session state synchronization message includes previously stored PDU session state information for the UE.

[0277] P3. The method according to embodiment P1 or P2, wherein the PDU session state synchronization message includes information instructing the UE to disable PDU sessions included in the set of PDU sessions that the UE considers active.

[0278] Q1. An AMF (104) for PDU session synchronization, said AMF being adapted to:

[0279] Receive a message sent by the UE (102), the message including PDU session state information (e.g., a bitmap), the PDU session state information identifying a group or more PDU sessions that the UE considers to be active;

[0280] In response to receiving the message, the previously stored PDU session state information for the UE is retrieved;

[0281] Determine whether the PDU session state information contained in the received message matches the acquired PDU state information for the UE; and

[0282] In response to determining that the PDU session state information in the received message does not match the obtained PDU state information for the UE, a PDU session state synchronization message (e.g., NG1 message) is sent to the UE to synchronize the PDU session state information.

[0283] R1. An AMF (104) for PDU session synchronization, said AMF comprising:

[0284] The acquisition module (1402) is used to acquire a message sent by the UE (102), the message including PDU session state information (e.g., bitmap), the PDU session state information identifying a group or more PDU sessions that the UE considers to be active;

[0285] The acquisition module (1403) is adapted to acquire previously stored PDU session state information for the UE in response to receiving the message;

[0286] The determining module (1404) is adapted to determine whether the PDU session state information contained in the received message matches the acquired PDU state information for the UE; and

[0287] The PDU session state synchronization module (1406) is adapted to send a PDU session state synchronization message (e.g., NG1 message) to the UE to synchronize the PDU session state information in response to determining that the PDU session state information in the received message does not match the obtained PDU state information for the UE.

[0288] While various embodiments of this disclosure have been described herein, it should be understood that they are presented by way of example only and not as limiting. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above. Furthermore, unless otherwise stated herein or the context clearly contradicts it, this disclosure covers any combination of all possible variations of the foregoing elements.

[0289] Furthermore, although the process described above and illustrated in the accompanying figures is shown as a series of steps, this is merely for illustrative purposes. Therefore, it is expected that some steps can be added, some steps can be omitted, the order of the steps can be rearranged, and some steps can be performed in parallel.

[0290] abbreviations

[0291] AMF Access and Mobility Management Functions

[0292] CN Core Network

[0293] DL downlink

[0294] MM Mobility Management

[0295] PDU Protocol Data Unit

[0296] QoS (Quality of Service)

[0297] RAN (Radio Access Network)

[0298] SM Session Management

[0299] SMF Session Management Function

[0300] SR service request

[0301] UE User Equipment

[0302] UP User Plane

[0303] UPF User Plane Functions

Claims

1. A method executed by a user equipment (UE), comprising: It is determined that multiple Protocol Data Unit (PDU) sessions will be established for the User Plane UP. The Access and Mobility Management Function (AMF) sends a Non-Access Stratum (NAS) Service Request (SR), which includes information indicating that a defined number of PDU sessions will be established for the UP. The information indicating the determination of the plurality of PDU sessions for which the UP will be established includes a bitmap, wherein each bit of the bitmap indicates whether the corresponding PDU session among the plurality of PDU sessions needs to be established by the UP.

2. The method according to claim 1, further comprising: The UP is established for one or more PDU sessions among the plurality of PDU sessions.

3. The method according to claim 1, wherein, Determining that the multiple PDU sessions to be established for the UP is in response to: A paging message is received, the paging message including a PDU session identification information for identifying a PDU session.

4. The method of claim 3, further comprising: The PDU session identifier information is obtained from the paging message.

5. The method according to claim 1, wherein, Determining the plurality of PDU sessions includes determining that the UE has the plurality of PDU sessions for sending uplink UL UP data to the receiver.

6. The method of claim 1, further comprising: Receive a NAS response to the SR, the NAS response using a bitmap to indicate one or more established PDU sessions from the plurality of PDU sessions.

7. A computer program product comprising a non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium including program code to be executed by processing circuitry of a user equipment (UE), whereby execution of the program code causes the UE to perform operations including: It is determined that multiple Protocol Data Unit (PDU) sessions will be established for the User Plane UP. The Access and Mobility Management Function (AMF) sends a Non-Access Stratum (NAS) Service Request (SR), which includes information indicating that a defined number of PDU sessions for the UP will be established. in, The information indicating the determination of the plurality of PDU sessions for which the UP will be established includes a bitmap, wherein each bit of the bitmap indicates whether the corresponding PDU session among the plurality of PDU sessions needs to be established by the UP.

8. The computer program product according to claim 7, wherein, The non-transitory computer-readable storage medium includes additional program code, whereby execution of the additional program code causes the UE to perform further operations including: The UP is established for one or more PDU sessions among the plurality of PDU sessions.

9. The computer program product according to claim 7, wherein, Determining that the multiple PDU sessions to be established for the UP is in response to: A paging message is received, the paging message including a PDU session identification information for identifying a PDU session.

10. The computer program product according to claim 9, wherein, The non-transitory computer-readable storage medium includes additional program code, whereby execution of the additional program code causes the UE to perform further operations including: The PDU session identifier information is obtained from the paging message.

11. The computer program product according to claim 7, wherein, Determining the plurality of PDU sessions includes determining that the UE has the plurality of PDU sessions for sending uplink UL UP data to the receiver.

12. The computer program product according to claim 7, wherein, The non-transitory computer-readable storage medium includes additional program code, whereby execution of the additional program code causes the UE to perform further operations including: Receive a NAS response to the SR, the NAS response using a bitmap to indicate one or more established PDU sessions from the plurality of PDU sessions.

13. A user equipment (UE), the UE being adapted to: It is determined that multiple Protocol Data Unit (PDU) sessions will be established for the User Plane UP. The Access and Mobility Management Function (AMF) sends a Non-Access Stratum (NAS) Service Request (SR), which includes information indicating that a defined number of PDU sessions for the UP will be established. in, The information indicating the determination of the plurality of PDU sessions for which the UP will be established includes a bitmap, wherein each bit of the bitmap indicates whether the corresponding PDU session among the plurality of PDU sessions needs to be established by the UP.

14. The UE according to claim 13, further adapted to: The UP is established for one or more PDU sessions among the plurality of PDU sessions.

15. The UE according to claim 13, further adapted to: In response to receiving a paging message, it is determined that a plurality of PDU sessions will be established for the UP, wherein, The paging message includes a PDU session identification information used to identify a PDU session.

16. The UE according to claim 15, further adapted to: The PDU session identifier information is obtained from the paging message.

17. The UE according to claim 13, wherein, In order to determine the plurality of PDU sessions, the UE is further adapted to: determine that the UE has the plurality of PDU sessions for uplink UL UP data to be sent to the receiver.

18. The UE according to claim 13, wherein, The UE is further adapted to: Receive a NAS response to the SR, the NAS response using a bitmap to indicate one or more established PDU sessions from the plurality of PDU sessions.

Images