阅读说明：本技术 用于在无线通信中避免不必要消息的传输的方法及相关网络和网络节点 (Method for avoiding transmission of unnecessary messages in wireless communication and related network and network node ) 是由 I·塞德拉切克 P·赫德曼 K·约翰松 N·史 于 2020-02-11 设计创作，主要内容包括：在此公开了一种操作电信网络(100a,100b)的会话管理网络节点(600c,900)的方法,该方法由会话管理网络节点执行,包括：向管理网络节点600b发送(107,108,200)无线设备的会话建立请求的接受；从管理网络节点接收(113,202)消息,其中该消息包括由服务无线设备的无线电接入网络节点(600a)发送的会话连接拒绝消息,其中,会话连接拒绝消息指示对无线设备的会话建立请求的接受的拒绝；基于由无线电接入网络提供的会话连接拒绝消息,确定(119,206)无线电接入网络没有向无线设备发送会话建立请求的接受；响应于无线电接入网络没有向无线设备发送会话建立请求的接受,创建(119,208)会话建立拒绝消息；向无线设备发送(119,210)会话建立拒绝消息。(Disclosed herein is a method of operating a session managing network node (600c, 900) of a telecommunications network (100a, 100b), the method being performed by the session managing network node and comprising: sending (107, 108, 200) an acceptance of the session establishment request of the wireless device to the managing network node 600 b; receiving (113, 202) a message from a managing network node, wherein the message comprises a session connection rejection message sent by a radio access network node (600a) serving the wireless device, wherein the session connection rejection message indicates a rejection of acceptance of the session establishment request for the wireless device; determining (119, 206), based on a session connection rejection message provided by the radio access network, that the radio access network does not send an acceptance of the session establishment request to the wireless device; creating (119, 208) a session establishment reject message in response to the radio access network not sending an acceptance of the session establishment request to the wireless device; a session establishment rejection message is sent (119, 210) to the wireless device.)

1. A method of operating a session management network node (600c, 900) of a telecommunications network (100a, 100b), the method being performed by the session management network node, comprising:

sending (107, 108, 200) an acceptance of a session establishment request of the wireless device to the managing network node (600 b);

receiving (113, 202) a message from the managing network node, wherein the message comprises a session connection rejection message sent by a radio access network node (600a) serving the wireless device, wherein the session connection rejection message indicates a rejection of the acceptance of the session establishment request for the wireless device;

determining (119, 206) that the radio access network does not send the acceptance of the session establishment request to the wireless device based on the session connection rejection message provided by the radio access network;

creating (119, 208) a session establishment reject message in response to the radio access network not sending the acceptance of the session establishment request to the wireless device;

-sending (119, 210) the session establishment rejection message to the wireless device.

2. The method of claim 1, further comprising: -releasing (115, 204) the session.

3. The method of claim 1 or 2, wherein the determining comprises:

checking (113, 300) a reason for the rejection provided by the radio access network in the session connection message.

4. The method of claim 3, wherein the reason provided by the radio access network comprises at least one of: insufficient resources, insufficient resources for a particular slice and DNN, and insufficient resources for a particular slice.

5. The method according to any of claims 2 to 4, wherein creating the session establishment rejection message includes a value indicating the reason for the session establishment rejection in the session establishment rejection message.

6. The method of claim 5, wherein the value comprises at least one of: characters, numbers, and alphanumeric strings.

7. The method of any of claims 1 to 6, wherein the session is a protocol data unit session.

8. A method of operating a radio access network, RAN, node (600a) of a telecommunications network (100a, 100b), the method being performed by the RAN node, comprising:

sending (111, 400) a session connection rejection message to a managing network node (600b), wherein the session connection rejection message comprises a reason for rejection of a session establishment request for a wireless device for the radio access network;

receiving (121, 402) a request message from the managing network node, wherein the request message comprises a request for a radio access network node to forward a session setup rejection message sent by a session network node to the wireless device;

transmitting (123, 404) a rejection message to the wireless device, wherein the rejection message comprises the session establishment rejection message.

9. The method of claim 8, wherein the reason comprises at least one of: insufficient resources, insufficient resources for a particular slice and DNN, and insufficient resources for a particular slice.

10. The method of any of claims 8 to 9, wherein the request message comprises an N2 downlink NAS transport request message.

11. The method of any of claims 8 to 10, wherein the rejection message comprises a downlink NAS transport message.

12. A session management network node (600c) of a telecommunications network (100a, 100b), comprising:

a processor (610); and

a memory (620) coupled with the processor (610), wherein the memory comprises instructions that when executed by the processor (610) cause the session network node to perform operations according to any one of claims 1 to 7.

13. A radio access network node (600a) of a telecommunications network (100a, 100b), comprising:

a processor (610); and

a memory (620) coupled with the processor (610), wherein the memory comprises instructions that, when executed by the processor (610), cause the radio access network node to perform operations according to any one of claims 8 to 11.

Technical Field

The present disclosure relates to wireless communication systems, and more particularly, to avoiding transmission of unnecessary messages in wireless communication.

Background

The 3GPP Technical Specification (TS)23.501-V15.0.0 clause 4.2 describes a representative architecture for a 5G system. The 5G architecture is generally defined as service-based, and the interaction between network functions is represented in two ways, namely, a service-based representation and a reference point representation. In a service-based representation, network functions within the control plane, such as access and mobility management functions (AMFs), enable other authorized network functions to access their services. The representation also includes point-to-point reference points, if desired. The reference point represents the interaction that exists between the network function services in the network function that is shown to be described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and Session Management Function (SMF)).

The service-based interfaces are listed in TS 23.501-V15.0.0 clause 4.2.6. The reference points are listed in TS 23.501-V15.0.0 clause 4.2.7.

Fig. 1a depicts a non-roaming reference 5G system architecture. A service-based interface is used within the control plane. Fig. 1b depicts the reference 5G system architecture in a non-roaming scenario, using a reference point representation showing how the various network functions interact with each other.

Further background can be found, for example, in 3GPP TS 23.502-V15.4.1 clause 4.3.2, which describes a Protocol Data Unit (PDU) session establishment procedure. More specifically, 3GPP TS 23.502-V15.4.1 clause 4.2.3.2 describes a User Equipment (UE) triggered service request procedure.

Disclosure of Invention

The third generation partnership project (3GPP) SA2 group agreed in S2-1901089(http://3GPP. org/ftp/tsg _ SA/WG2_ Arch/TSGS 2_130_ Kochi/Docs/S2-1901089. zip): if the 5 th generation (5G) Radio Access Network (RAN) cannot allocate the radio resources required for the PDU SESSION, the 5G RAN does not send a Downlink non-Access stratum TRANSPORT (DL NAS TransPort) to the User Equipment (UE) that carries a protocol data Unit Session ESTABLISHMENT Accept (PDU Session ESTABLISHMENT).

If DL NAS TRANSPORT carrying PDU SESSION ESTABLISHHMENT ACCEPT is not sent to UE:

-according to TS 24.501(http:// www.3gpp.org/ftp/specs/archive/24_ series/24.501/245801-f 21.zip) sub-clause 6.4.1.6 bulletin a), upon expiry of timer T3580, the UE will retransmit PDU Session ESTABLISHMENT solicitation and send it to the Access and Mobility Function (AMF) (which is also referred to herein as the managing network node) using UL NAS TRANSPORT; and

-according to TS 24.501(http:// www.3gpp.org/ftp/specs/archive/24_ series/24.501/245801-f 21.zip) sub-clause 5.4.5.2.5 bulletin a)12), upon receiving UL NAS TRANSPORT with retransmitted PDU SESSION ESTABLISIVE REQUEST from the UE, the AMF performs local release of existing PDU SESSIONs, REQUESTs the SESSION Management Function (SMF) to perform local release of existing PDU SESSIONs, the AMF performs new SMF selection, and forwards the retransmitted PDU ESTABLISHMENT REQUEST to the new SMF.

Furthermore, if the new SMF ACCEPTs to establish a PDU SESSION with resources that the 5G RAN is not able to allocate and the 5G access network does not send to the UE the resources of DL NAS TRANSPORT carrying the PDU SESSION ESTABLISHMENT ACCEPT, the above will be repeated 5 times.

Thus, if the 5G access network does not send the DL NAS TRANSPORT carrying the PDU SESSION ESTABLISHMENT ACCEPT to the UE, this results in unnecessary 5GSM messages (up to 5 retransmissions of the PDU SESSION ESTABLISHMENT REQUEST) and unnecessary network actions (AMF selects SMF, SMF tries to establish PDU SESSION, AMF and SMF release PDU SESSION locally, all up to 5 times) sent over the air.

According to some embodiments of the inventive concept, a method of operating a session management network node in a radio access network may be provided. In such a method, the session management network node may accept a session establishment request by the wireless device. The acceptance may include establishing a session. The session management network node may receive a message from the management network node. The message may comprise a session connection reject message from the radio access network. The session connection rejection message may include a rejection of the acceptance of the session establishment request by the radio access network for the wireless device and a reason for the rejection for the radio access network. The session management network node may release the session; determining that the radio access network does not send an acceptance of the session establishment request to the wireless device based on a cause of the rejection provided by the radio access network; a session establishment rejection message may be created; and may send a session establishment reject message to the wireless device.

According to some embodiments of the inventive concept, a method of operating a radio access network node in a radio access network may be provided. In such a method, the radio access network node may send a session connection rejection message to the managing network node. The session connection rejection message may include a reason for rejection of the session establishment request for the wireless device by the radio access network. The radio access network node may receive a request message from the managing network node. The request message may comprise a request for the radio access network node to forward a session setup rejection message received from the session network node to the wireless device. The radio access network node may send a rejection message to the wireless device. The rejection message may comprise a session establishment rejection message.

According to some embodiments, the session network node may send a session establishment reject message and may determine that the message carrying the session establishment acceptance of the session management network node was not sent by the radio access network to the wireless device, and thus avoid unnecessary message exchanges.

An advantageous embodiment is directed to a method of operating a session management network node of a telecommunications network, the method performed by the session management network node, comprising: sending an acceptance of a session establishment request for the wireless device to a management network node; receiving a message from a managing network node, wherein the message comprises a session connection rejection message sent by a radio access network node serving the wireless device, wherein the session connection rejection message indicates a rejection of acceptance of the session establishment request for the wireless device; determining, based on a session connection rejection message provided by the radio access network, that the radio access network does not send an acceptance of the session establishment request to the wireless device; creating a session establishment rejection message in response to the radio access network not sending an acceptance of the session establishment request to the wireless device; sending a session establishment rejection message to the wireless device; and preferably, the session is released.

Another advantageous embodiment is directed to a method of operating a radio access network, RAN, node of a telecommunications network, the method performed by the RAN node, comprising: sending a session connection rejection message to a management network node, wherein the session connection rejection message includes a reason for rejection of a session establishment request for the wireless device for the radio access network; receiving a request message from a management network node, wherein the request message comprises a request for the radio access network node to forward a session setup rejection message sent by the session network node to the wireless device; sending a rejection message to the wireless device, wherein the rejection message comprises a session establishment rejection message.

The presently disclosed embodiments may operate to avoid unnecessary messages sent over the air (e.g., in 5GSM, up to 5 retransmissions of PDU SESSION ESTABLISHMENT REQUEST) and unnecessary network actions (e.g., AMF selects SMF, SMF attempts to establish PDU SESSION, AMF and SMF release PDU SESSION locally, all up to 5 times). When the SMF sends a PDU SESSION ESTABLISHMENT exception ACCEPT and the SMF may determine that a NAS message carrying a PDU usage ESTABLISHMENT exception ACCEPT was not sent by the 5G access network to the UE, then the SMF may prevent a useless message exchange (e.g., the repeated useless 5GSM message exchange discussed above).

Drawings

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of the inventive concepts. In the drawings:

FIG. 1a depicts a non-roaming reference 5G system in which some embodiments of the present solution may be implemented;

fig. 1b depicts a reference 5G system architecture in a non-roaming scenario in which some embodiments of the present solution may be implemented;

figure 1c is a message diagram illustrating communication of messages according to some embodiments of the present disclosure;

figures 2 to 4 are flowcharts illustrating radio access node operations according to some embodiments of the inventive concept;

fig. 5 is a block diagram of a wireless device according to some embodiments of the inventive concept;

fig. 6 is a block diagram of a network node according to some embodiments of the inventive concept.

Detailed Description

The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. The inventive concept may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. A component from one embodiment may be assumed by default to be present/used in another embodiment.

The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and should not be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded without departing from the scope of the described subject matter. The term "terminal" is used in a non-limiting manner and may refer to any type of radio communication terminal, as explained below. The term "terminal" herein may be interchangeably replaced with the terms "radio terminal", "radio communication terminal", "radio equipment", or "User Equipment (UE)".

If the 5G access network does not send a DL NAS TRANSPORT carrying a PDU SESSION ESTABLISHMENT ACCEPT to the UE, then in various embodiments, the SMF may send a PDU SESSION ESTABLISHMENT REJECT (PDU SESSION ESTABLISHMENT REJECT) when the SMF sends a PDU SESSION ESTABLISHMENT REJECT ACCEPT and the SMF may determine that a NAS message carrying a PDU SESSION ESTABLISHMENT ACCEPT is not sent by the 5G access network to the UE.

According to some embodiments of the inventive concept, signaling/messaging may be provided in a fifth generation system (5GS) radio access network.

In some embodiments of the inventive concept, the SMF may determine that the NAS message carrying the PDU SESSION ESTABLISHMENT ACCEPT was not sent by the 5G access network to the UE based on a reason provided by the 5G access network.

Fig. 1c is a message diagram illustrating communication of messages/signals according to some embodiments of the present disclosure.

Referring to FIG. 1 c:

at 101, a UE (e.g., wireless device 500) may send a PDU session setup request (also referred to as PDU session request below) to a managing network node (e.g., AMF network node 600 b).

At 103, the managing network node 600b may determine that the message corresponds to a request for a new PDU session and select a session managing network node (e.g., SMF network node 600 c).

At 105, the AMF network node 600b may send a PDU session creation Session Management (SM) context request to the selected SMF network node 600 c.

At 107 or 108, the SMF network node 600c may send a message to the AMF network node 600b carrying a response of the SMF network node 600c to the request to create the PDU session, preferably by sending a PDU session setup accept message intended for the wireless device, preferably in a Namf _ Communication _ NlN2MessageTransfer message or in an Nsmf _ pdussion _ CreateSMContext response message. The message may include accepting the PDU session request or rejecting the PDU session request. SMF network node 600c may also include NAS information (e.g., N2 SM information) if the message includes an acceptance of the PDU session request. If the PDU session request is accepted, SMF network node 600c may establish the PDU session.

At 109, if the SMF network node 600c accepts the PDU session request, the AMF network node 600b may send a session request message (e.g., AN N2PDU session request to the RAN network node 600a) to the radio access network node (e.g., (R) AN network node 600 a). The message may include NAS information (e.g., N2 SM information) received from the SMF network node, including whether the SMF network node 600c accepted the PDU session request.

At 111, when (R) AN network node 600a rejects the PDU session request, (R) AN network node 600a may send a session connection reject message, e.g., AN N2PDU session request acknowledgement (Ack), to the AMF network node 600 b. The session connection reject message may also include NAS information (e.g., N2 SM information) received from SMF network node 600c and the reason for the rejection. Rejection may occur when the SMF network node 600c accepts a PDU session request with resources that the radio access network cannot allocate. Reasons for rejection may include insufficient resources, insufficient resources for a particular slice and DNN, or insufficient resources for a particular slice.

At 113, the AMF network node 600b may forward the session connection reject message from the RAN network node 600a to the SMF network node 600c in, for example, an Nsmf _ congestion _ UpdateSMContext response. The session connection reject message may include a reason for rejection of the PDU session request by the (R) AN network node 600 a.

At 115, when the (R) AN network node 600a rejects the PDU session request, the SMF may release the PDU session established by the SMF network node 600 c.

At 117, when the SMF network node 600c releases the PDU session, the SMF network node 600c may send a message to the AMF network node 600b, e.g., an Nsmf _ PDU usage _ update smcontext response, updating the AMF network node 600 b.

At 119, the SMF network node 600c may determine, based on the content of the session connection rejection message, that a message carrying a response of the SMF network node 600c accepting the request to create the PDU session was not sent by the (R) AN network node 600a to the UE 500, e.g., the determination may be based on a reason provided by the (R) AN network node 600a for rejection of the PDU session request by the (R) AN network node 600a or the like.

SMF network node 600c may create a PDU SESSION ESTABLISHMENT request message. The PDU SESSION ESTABLISHMENT request message may include an information element including a reason for rejection of the PDU SESSION request by the radio access network (e.g., a 5GSM reason), for example, indicating insufficient resources, insufficient resources for a particular slice and DNN, and insufficient resources for a particular slice. The information element may include a value set by the SMF network node 600c for the reason for the rejection of the PDU session request by the (R) AN network node 600 a. The value set may include values indicating insufficient resources, insufficient resources for a particular slice and DNN, or insufficient resources for a particular slice. The values may include at least one of: characters, numbers, and alphanumeric strings. For example, the value may be #26 for insufficient resources, #69 for "insufficient resources for a particular slice," or #67 for "insufficient resources for a particular slice and DNN.

The SMF network node 600c may send a PDU SESSION ESTABLISHMENT REJECT message in the Namf _ Communication _ NlN2message transfer, e.g. to the AMF network node 600b, to the AMF network node 600b to be sent to the UE 500. The AMF network node 600b may respond to the SMF network node 600c with, for example, a Namf _ Communication _ NlN2 MessageTransfer.

At 121, the AMF network node 600b may send a seventh message (e.g., N2 downlink NAS transport request) to the (R) AN network node 600a, which may include the PDU SESSION ESTABLISHMENT exception request received from the SMF network node 600c to be sent to the UE 500.

At 123, RAN network node 600a may send a downlink NAS transport message to UE 500, which may include forwarding the PDU SESSION ESTABLISHMENT request from SMF network node 600 c.

At 125, the UE 500 may release the PDU session in response to receiving the downlink NAS transport message from the (R) AN network node 600 a.

The PDU Session initiation REJECT message may be sent using an N2 downlink NAS transport procedure (as in TS 38.413(http:// www.3gpp.org/ftp/specs/archive/38_ series/38.413/38413-f20.zip) sub-clause 8.6.2) instead of the N2PDU SESSION resource ESTABLISHMENT (as in TS 38.413(http:// www.3gpp.org/ftp/specs/archive/38_ series/38.413/38413-f20.zip) sub-clause 8.2.1). Using the N2 downlink NAS transport procedure may ensure that DL 5GSM messages are delivered to the UE when no additional resources are established.

The operation of the radio access network nodes 600a, 600b and 600c will now be discussed with reference to the flow diagrams of fig. 2 to 4 according to some embodiments of the inventive concept. For example, the modules may be stored in the memory 620 of fig. 6, and the modules may provide instructions such that when the instructions of the modules are executed by the respective radio access network node processors 610, the processors 610 perform the respective operations of the respective flow diagrams.

Fig. 2 and 3 illustrate the operation of a telecommunications network node 600 c. Fig. 4 illustrates the operation of a radio access network (R) AN network node 600 a. The session network node 600c and the radio access network node 600a of fig. 2-4 may each be provided according to the structure shown in fig. 6.

Referring first to fig. 2, at block 200, a processor 610 of a session management network node 600c (e.g., SMF network node) may accept a session setup request of a wireless device 500, preferably by sending a PDU session setup accept message intended for the wireless device, preferably in a Namf _ Communication _ NlN2message transfer message or in an Nsmf _ pdussion _ CreateSMContext response message. The session may be a Protocol Data Unit (PDU) session.

At block 202, the processor 610 of the session management network node 600c may receive a message from the management node 600b, the message comprising a session connection rejection message from the (R) AN network node 600 a. The session connection reject message may include a rejection of the acceptance of the session establishment request by the radio access network to the wireless device and a reason for possible rejection to the radio access network. The reason, when provided by the radio access network, may include at least one of: insufficient resources, insufficient resources for a particular slice and DNN, and insufficient resources for a particular slice.

At block 204, processor 610 of session management network node 600c may release the session it established in response to accepting the session establishment request of wireless device 500.

At block 206, the processor 610 of the session management network node 600c may determine that the radio access network did not send an acceptance of the session establishment request of the session management network node 600c for the wireless device 500. The session management network node 600c may make the determination based on the content of the session connection rejection message, e.g. based on the reason for the rejection provided by the radio access network in the session connection rejection message provided to the session management network node 600c or similar, as disclosed in block 202.

At block 208, the processor 610 of the session management network node 600c may create a session establishment reject message in response to the radio access network not sending an acceptance of the session establishment request to the wireless device. The session establishment rejection message may include a set of values for the reason for the session establishment rejection, e.g., indicating insufficient resources, insufficient resources for the particular slice and DNN, or insufficient resources for the particular slice. The values may include at least one of: characters, numbers, and alphanumeric strings. For example, the value may be #26 for insufficient resources, #69 for "insufficient resources for a particular slice," or #67 for "insufficient resources for a particular slice and DNN.

At block 210, processor 610 of session management network node 600c may send a session setup rejection message to the wireless device.

Referring to fig. 3, at block 300, the processor 610 of the session management network node 600c may determine that the radio access network did not send an acceptance of the session establishment request by the session management network node 600c for the wireless device 500 by examining the reason for the rejection of the acceptance of the session establishment request by the session management network node 600c by the radio access network in the session connect message.

Referring to fig. 4, at block 400, the processor 610 of (R) AN network node 600c may send a session connection rejection message to the managing network node 600 b. The session connection reject message may include a reason for rejection of a session establishment request (e.g., a PDU session request) for the wireless device by the radio access network. The reason may include at least one of: insufficient resources, insufficient resources for a particular slice and DNN, and insufficient resources for a particular slice.

At block 402, the processor 610 of (R) AN network node 600c may receive a request message from the managing network node 600 b. The request message may comprise a request for the (R) AN network node 600c to forward to the wireless device 500 a session establishment reject message received at the managing network node 600b from the session network node 600 c. The SESSION setup REJECT message forwarded from SESSION network node 600c (e.g., PDU SESSION ESTABLISHMENT REJECT message) may include an information element including a reason (e.g., 5GSM reason) for rejection of the PDU SESSION request by the radio access network. The information element may include a value set by the SMF network node 600c for the reason for the rejection of the PDU session request by the (R) AN network node 600 a. The value set may include values indicating insufficient resources, insufficient resources for a particular slice and DNN, or insufficient resources for a particular slice. The values may include at least one of: characters, numbers, and alphanumeric strings. For example, the value may be #26 for "insufficient resources, #69 for" insufficient resources for a particular slice, "or #67 for" insufficient resources for a particular slice and DNN. The request message may be an N2 downlink NAS transport request message.

At block 404, the processor 610 of (R) AN network node 600c may send a rejection message to the wireless device 500. The rejection message may comprise a session establishment rejection message. The rejection message may be a downlink NAS transport message.

Fig. 5 is a block diagram illustrating a wireless device 500 configured according to some embodiments. Wireless device 500 may include, but is not limited to, a wireless terminal, a wireless communication device, a wireless communication terminal, a terminal node/UE/device, and/or the like. The wireless device 500 includes AN RF front end 530, the RF front end 530 including one or more power amplifiers that transmit and receive through antennas of AN antenna array 540 to provide uplink and downlink radio communications with radio network nodes (e.g., base stations, enbs, gnbs, (R) AN network nodes, management network nodes, etc.) of a telecommunications network. Instead of or in addition to RF front end 530, wireless device 500 may include an optical receive front end configured to receive optical signaling from an optical WiFi AP. The wireless device 500 further includes: a processor circuit 510 (also referred to as a processor) coupled to the RF front end 530; and a memory circuit 520 (also referred to as a memory). The memory 520 stores computer readable program code that, when executed by the processor 510, causes the processor 510 to perform operations according to embodiments disclosed herein.

Fig. 6 is a block diagram illustrating a network node 600 (e.g., a base station, AN eNB, a gNB, (R) AN network node, more preferably AN AMF network node (also referred to herein as a management network node), AN SMF network node (also referred to herein as a session network node), etc.) of a telecommunications network. The network node 600 comprises: a processor circuit 610 (also referred to as a processor); memory circuit 620 (also referred to as memory); and a network interface 650 (e.g., a wired network interface and/or a wireless network interface) configured to communicate with other network nodes. The network node 600 may be configured as a radio network node comprising an RF front end and/or an optical signaling front end with one or more power amplifiers 630, transmitting and receiving through the antennas of an antenna array 640. The memory 620 stores computer readable program code that, when executed by the processor 610, causes the processor 610 to perform operations in accordance with embodiments disclosed herein. As will be readily understood by those skilled in the art reading this disclosure, network node 600 may be implemented, for example, as a network element on dedicated hardware, or as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, such as a cloud infrastructure.

Some of the embodiments that have been described above may be summarized in the following manner:

1. a method of operating a session management network node (600c, 900) of a telecommunications network (100a, 100b), the method being performed by the session management network node, comprising:

sending an acceptance (107, 108, 200) of a session establishment request of the wireless device to a managing network node (600 b);

receiving (113, 202) a message from a managing network node, wherein the message comprises a session connection rejection message sent by a radio access network node (600a) serving the wireless device, wherein the session connection rejection message indicates a rejection of acceptance of the session establishment request for the wireless device;

determining (119, 206), based on a session connection rejection message provided by the radio access network, that the radio access network does not send an acceptance of the session establishment request to the wireless device;

creating (119, 208) a session establishment reject message in response to the radio access network not sending an acceptance of the session establishment request to the wireless device;

sending (119, 210) a session establishment rejection message to the wireless device; and

the session is released (115, 204), preferably at least in the session management network node.

2. The method of embodiment 1, wherein determining comprises:

the cause of the rejection provided by the radio access network in the session connect message is checked (113, 300).

3. The method of embodiment 2, wherein the cause provided by the radio access network comprises at least one of: insufficient resources, insufficient resources for a particular slice and DNN, and insufficient resources for a particular slice.

4. The method according to any of embodiments 2 to 3, wherein creating a session establishment rejection message comprises including a value indicating a reason for the session establishment rejection into the session establishment rejection message.

5. The method of embodiment 4, wherein the values include at least one of: characters, numbers, and alphanumeric strings.

6. The method according to any of embodiments 1 to 5, wherein a session is a protocol data unit session.

7. A method of operating a radio access network, RAN, node (600a) of a telecommunications network (100a, 100b), the method being performed by the RAN node, comprising:

sending (111, 400) a session connection rejection message to a managing network node (600b), wherein the session connection rejection message comprises a reason for rejection of a session establishment request for the wireless device for the radio access network;

receiving (121, 402) a request message from a managing network node, wherein the request message comprises a request for the radio access network node to forward a session setup rejection message sent by the session network node to the wireless device;

transmitting (123, 404) a rejection message to the wireless device, wherein the rejection message comprises a session establishment rejection message.

8. The method of embodiment 7, wherein the cause comprises at least one of: insufficient resources, insufficient resources for a particular slice and DNN, and insufficient resources for a particular slice.

9. The method according to any of embodiments 7 to 8, wherein the request message comprises an N2 downlink NAS transport request message.

10. The method according to any of embodiments 7 to 9, wherein the rejection message comprises a downlink NAS transport message.

11. A session management network node (600c) of a telecommunications network (100a, 100b), comprising:

a processor (610); and

a memory (620) coupled with the processor (610), wherein the memory comprises instructions that when executed by the processor (610) cause the session network node to perform operations according to any of embodiments 1 to 6.

12. A radio access network node (600a) of a telecommunications network (100a, 100b), comprising:

a processor (610); and

a memory (620) coupled with the processor (610), wherein the memory comprises instructions that when executed by the processor (610) cause the radio access network node to perform operations according to any of embodiments 7 to 10.

In the above description of various embodiments of the inventive concept, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the inventive concept. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

When an element is referred to as being "connected," "coupled," "responsive" or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected to," "directly coupled to," "directly responsive to," or variants thereof, another element, there are no intervening elements present. Like numbers refer to like elements throughout. Further, "coupled," "connected," "responsive," or variations thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" includes any and all combinations of one or more of the associated list items.

It will be understood that, although the terms "first," "second," "third," etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus, a first element/operation in some embodiments may be termed a second element/operation in other embodiments without departing from the teachings of the present inventive concept. The same reference numbers or the same reference indicators indicate the same or similar elements throughout the specification.

As used herein, the terms "comprises," "comprising," "includes," "including," "contains," "containing," "has," "having," "possesses," "has," or variants thereof, are open-ended and include one or more stated features, integers, elements, steps, components, or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Further, as used herein, common abbreviations "e.g.," derived from the latin phrase "e.g.," may be used to introduce or specify general examples or illustrations of previously mentioned items, and is not intended to be limiting of such items. The common abbreviation "i.e.," derived from the latin phrase "i.e.," can be used to designate a particular item from a more general recitation.

Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It will be understood that blocks of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions which are executed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, a special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuits to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby produce means (functions) and/or structures for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.

These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the function/act specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of the inventive concept may be implemented in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor (such as a digital signal processor), which may be collectively referred to as "circuitry," "modules," or variations thereof.

It should also be noted that, in some alternative implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowchart and/or block diagrams may be separated into multiple blocks, and/or the functionality of two or more blocks of the flowchart and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the illustrated blocks and/or blocks/operations may be omitted without departing from the scope of the inventive concept. Further, although some of the figures include arrows on communication paths showing the primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Many variations and modifications may be made to the embodiments without substantially departing from the principles of the present inventive concept. All such variations and modifications are intended to be included herein within the scope of the present inventive concept. Accordingly, the above-disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of the inventive concept. Thus, to the maximum extent allowed by law, the scope of the present inventive concept is to be determined by the broadest permissible interpretation of the present disclosure, including examples of embodiments and equivalents thereof, and shall not be restricted or limited by the foregoing detailed description.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant art unless a different meaning is explicitly given and/or implied by the context in which it is used. Unless explicitly stated otherwise, all references to elements, devices, components, methods, steps, etc. are to be interpreted openly as referring to at least one instance of an element, device, component, method, step, etc.

The steps of any method disclosed herein do not necessarily have to be performed in the exact order disclosed, unless the steps are explicitly described as either following or preceding another step and/or it is implicit that a step must be following or preceding another step. Any feature of any embodiment disclosed herein may be applied to any other embodiment, as appropriate. Likewise, any advantage of any embodiment may apply to any other embodiment, and vice versa. Other objects, features and advantages of the disclosed embodiments will be apparent from the following description.