WO2020249183A1 - Appareil, procédé et programme informatique - Google Patents

Appareil, procédé et programme informatique Download PDF

Info

Publication number
WO2020249183A1
WO2020249183A1 PCT/EP2019/065111 EP2019065111W WO2020249183A1 WO 2020249183 A1 WO2020249183 A1 WO 2020249183A1 EP 2019065111 W EP2019065111 W EP 2019065111W WO 2020249183 A1 WO2020249183 A1 WO 2020249183A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
data unit
protocol data
request
management function
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2019/065111
Other languages
English (en)
Inventor
Juhani Korja PEKKA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2019/065111 priority Critical patent/WO2020249183A1/fr
Publication of WO2020249183A1 publication Critical patent/WO2020249183A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover

Definitions

  • This disclosure relates to wireless telecommunications. More particularly, the present disclosure relates to an apparatus, method and computer program for acknowledging changes in session information for Protocol Data Unit (PDU) sessions.
  • PDU Protocol Data Unit
  • a User Equipment (UE) with multiple established PDU sessions may be served by different Session Management Functions (SMFs).
  • SMFs Session Management Functions
  • an apparatus comprising means for performing: sending, to a first session management function, a first request to update information of a first protocol data unit session; sending, to a second session management function, a second request to update information of a second protocol data unit session; receiving a first response to the first request before receiving a second response to the second request; sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • the means are further configured to perform: receiving a path switch request from the radio access network before sending the first request and sending the second request.
  • the path switch request is an N2 path switch request.
  • the path switch request is sent from the radio access network during a handover of a user equipment from a source base station to a target base station in the radio access network.
  • the handover is an Xn handover.
  • the means are further configured to perform: receiving, subsequent to sending the first acknowledgement message to the radio access network, the second response; and sending a second acknowledgement message to the radio access network; wherein the second acknowledgement message comprises session information of the first protocol data unit session received in the first response and session information of the second protocol data unit session received in the second response.
  • the first protocol data unit session comprises Ultra Reliable Low Latency Communication data transmission.
  • the first session management function is located at an edge of the radio access network and the second session management function is not located at an edge of the radio access network.
  • the apparatus comprises an access and mobility management function.
  • an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: sending, to a first session management function, a first request to update information of a first protocol data unit session; sending, to a second session management function, a second request to update information of a second protocol data unit session; receiving a first response to the first request before receiving a second response to the second request; sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform: receiving a path switch request from the radio access network before sending the first request and sending the second request.
  • the path switch request is an N2 path switch request.
  • the path switch request is sent from the radio access network during a handover of a user equipment from a source base station to a target base station in the radio access network.
  • the handover is an Xn handover.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform: receiving, subsequent to sending the first acknowledgement message to the radio access network, the second response; and sending a second acknowledgement message to the radio access network; wherein the second acknowledgement message comprises session information of the first protocol data unit session received in the first response and session information of the second protocol data unit session received in the second response.
  • the first protocol data unit session comprises Ultra Reliable Low Latency Communication data transmission.
  • the first session management function is located at an edge of the radio access network and the second session management function is not located at an edge of the radio access network.
  • the apparatus comprises an access and mobility management function.
  • an apparatus comprising: circuitry for sending, to a first session management function, a first request to update information of a first protocol data unit session; circuitry for sending, to a second session management function, a second request to update information of a second protocol data unit session; circuitry for receiving a first response to the first request before receiving a second response to the second request; and circuitry for sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • a method comprising: sending, to a first session management function, a first request to update information of a first protocol data unit session; sending, to a second session management function, a second request to update information of a second protocol data unit session; receiving a first response to the first request before receiving a second response to the second request; sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • the method comprises: receiving a path switch request from the radio access network before sending the first request and sending the second request.
  • the path switch request is an N2 path switch request
  • the path switch request is sent from the radio access network during a handover of a user equipment from a source base station to a target base station in the radio access network.
  • the handover is an Xn handover.
  • the method comprises: receiving, subsequent to sending the first acknowledgement message to the radio access network, the second response; and sending a second acknowledgement message to the radio access network; wherein the second acknowledgement message comprises session information of the first protocol data unit session received in the first response and session information of the second protocol data unit session received in the second response.
  • the first protocol data unit session comprises
  • the first session management function is located at an edge of the radio access network and the second session management function is not located at an edge of the radio access network.
  • the method is performed by an access and mobility management function.
  • a computer program comprising instructions for causing an apparatus to perform at least the following: sending, to a first session management function, a first request to update information of a first protocol data unit session; sending, to a second session management function, a second request to update information of a second protocol data unit session; receiving a first response to the first request before receiving a second response to the second request; sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • a computer program comprising instructions stored thereon for performing at least the following: sending, to a first session management function, a first request to update information of a first protocol data unit session; sending, to a second session management function, a second request to update information of a second protocol data unit session; receiving a first response to the first request before receiving a second response to the second request; sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: sending, to a first session management function, a first request to update information of a first protocol data unit session; sending, to a second session management function, a second request to update information of a second protocol data unit session; receiving a first response to the first request before receiving a second response to the second request; sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: sending, to a first session management function, a first request to update information of a first protocol data unit session; sending, to a second session management function, a second request to update information of a second protocol data unit session; receiving a first response to the first request before receiving a second response to the second request; sending a first acknowledgement message to a radio access network before receiving the response to the second request; wherein the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • an apparatus comprising means for performing: receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • the means are further configured to perform: sending a path switch request to the access and mobility management function before receiving the first acknowledgement message from the access and mobility management function.
  • the path switch request is an N2 path switch request.
  • the path switch request is sent during a handover of a user equipment from a source base station to a target base station.
  • the handover is an Xn handover.
  • the path switch request comprises an indication of whether or not the apparatus will accept a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information.
  • the means are further configured to perform: receiving, subsequent to receiving the first acknowledgement message from the access and mobility management function, a second acknowledgement message from the access and mobility management function; and wherein the second acknowledgement message comprises session information of the first protocol data unit session and session information of the second protocol data unit session.
  • the first protocol data unit session comprises Ultra Reliable Low Latency Communication data transmission.
  • the apparatus is a next generation radio access network node.
  • an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform: sending a path switch request to the access and mobility management function before receiving the first acknowledgement message from the access and mobility management function.
  • the path switch request is an N2 path switch request.
  • the path switch request is sent during a handover of a user equipment from a source base station to a target base station.
  • the handover is an Xn handover.
  • the path switch request comprises an indication of whether or not the apparatus will accept a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform: receiving, subsequent to receiving the first acknowledgement message from the access and mobility management function, a second acknowledgement message from the access and mobility management function; and wherein the second acknowledgement message comprises session information of the first protocol data unit session and session information of the second protocol data unit session.
  • the first protocol data unit session comprises Ultra Reliable Low Latency Communication data transmission.
  • the apparatus is a next generation radio access network node.
  • an apparatus comprising: circuitry for receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • a method comprising: receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • the method further comprises: sending a path switch request to the access and mobility management function before receiving the first acknowledgement message from the access and mobility management function.
  • the path switch request is an N2 path switch request.
  • the path switch request is sent during a handover of a user equipment from a source base station to a target base station.
  • the handover is an Xn handover.
  • the path switch request comprises an indication of whether or not the apparatus will accept a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information.
  • the method comprises: receiving, subsequent to receiving the first acknowledgement message from the access and mobility management function, a second acknowledgement message from the access and mobility management function; and wherein the second acknowledgement message comprises session information of the first protocol data unit session and session information of the second protocol data unit session.
  • the first protocol data unit session comprises Ultra Reliable Low Latency Communication data transmission.
  • the method is performed by a next generation radio access network node.
  • a computer program comprising instructions for causing an apparatus to perform at least the following: receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • a fourteenth aspect there is provided a computer program comprising instructions stored thereon for performing at least the following: receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: receiving a first acknowledgement message from an access and mobility management function; wherein the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • Figure 1 shows a schematic representation of part of a network
  • Figure 2 shows a schematic representation of a method for data transmission
  • Figure 3 shows a schematic representation of an apparatus according to an example
  • Figure 4 shows a schematic representation of an apparatus according to an example
  • Figure 5 shows a flow diagram of a method according to an example
  • Figure 6 shows a flow diagram of a method according to an example.
  • the present disclosure relates to wireless communications. More particularly, some examples relate to an apparatus, method and computer program for acknowledging changes in session information for one or more PDU sessions in a network while deferring acknowledging changes in other PDU sessions in the network,
  • a UE having two or more established PDU sessions may be served by different SMFs.
  • a PDU session usually belongs to one specific network slice instance per Public Land Mobile Network (PLMN). This is discussed, for example, in 3GPP, TS 23.501 ; System Architecture for the 5G System; Stage 2; Sections 5.6.1 and 5.15.1.
  • PLMN Public Land Mobile Network
  • edge computing is supported by the 5G Core Network (5GC) selecting a User Plane Function (UPF) close to a UE. This selection could be for providing a Local Area Data Network (LADN) service, for example.
  • Edge computing may be considered to comprise a method of bringing computer data storage closer to the location where it is needed. For example, in a telecommunications network, computer data storage could be brought closer to a UE than in a centralised telecommunications network. In such cases, functionality provided near a UE at a network edge may be able to respond more quickly to changes in the state of the UE than functionality provided at a network core.
  • 5GC functions such as a SMF and Access and
  • Mobility Management Function could also be deployed close to a UE.
  • the deployment of a SMF and AMF may depend on the expected UE mobility pattern.
  • Ultra Reliable Low Latency Communication is a Slice/Service Type (SST). This is discussed, for example, in 3GPP, TS 23.501 ; System Architecture for the 5G System; Stage 2; Section 5.15.2.2.
  • a URLLC transmission can be considered to be a latency critical transmission.
  • Figure 1 shows an example of part of a telecommunication network 100.
  • the network 100 is a 5G network. It will be understood that network 100 may also comprise various other components.
  • the network 100 may comprise a UE 101.
  • the UE 101 may be connectable to gNBs 104a and 104b. Such a connection may be made over either interface 103a or interface 103b, for example.
  • interface 103a and/or interface 103b may be an air interface.
  • An interface 107 may be provided between gNB 104a and gNB 104b.
  • interface 107 may be an Xn interface.
  • a UE in the network may be connected to source gNB 104a and then handed over to target gNB 104b in a handover procedure.
  • the handover procedure may comprise an Xn handover in some examples.
  • Each gNB 104a and 104b may be connected to an Access and Mobility Management Function (AMF) 105 via interfaces 1 13a and 1 13b.
  • AMF Access and Mobility Management Function
  • interface 1 13a is an N2 interface.
  • interface 1 13b is an N2 interface.
  • Session Management Function (SMF) 1 1 1 may be connected to AMF 105.
  • SMF 1 1 1 may also be connected to User Plane Function (UPF) 109.
  • the network may comprise one or more other SMFs.
  • one or more SMFs in the network may be located at a network edge while one or more other SMFs in the network are not located at the network edge.
  • each PDU session for UE 101 may be managed by a different SMF.
  • UPF 109 may be connected to Radio Access Network (RAN) 1 15.
  • RAN 1 15 may comprise gNB 104a and gNB 104b.
  • Figure 2 shows an example message flow.
  • a UE or other device may be connected to NG-RAN 215.
  • NG-RAN 215 may comprise a target gNB and a source gNB for the handover of a device.
  • a UE will be used as an example of a device connected to NG-RAN 215 in the following example, however it will be understood that in other examples a different device could be used.
  • the UE connected to NG-RAN 215 will be served by a different SMF for each PDU session established for the UE.
  • SMF 21 1 a for a first PDU session
  • SMF 21 1 b for a second PDU session. It will be understood, however, that the UE could have one or more PDU sessions established and could be served by a respective one or more SMFs, where the UE is served by a different SMF for each PDU session.
  • the first PDU session comprises a latency critical PDU session.
  • the first PDU session may comprise URLLC data transmissions.
  • SMF 21 1 a is located at a network edge close to the UE.
  • the second PDU session comprises a PDU session in which latency is not critical.
  • the second PDU session may, in some examples, comprise non-URLLC data transmissions.
  • SMF 21 1 b is located at a central site of a network, i.e. SMF 21 1 b may not be located at the network edge.
  • NG-RAN 215 sends a path switch request to AMF 205.
  • the path switch request may be sent as described in 3GPP TS 38.413, 3GPP TS 23.501 and 3GPP TS 23.502, for example.
  • the path switch request may be caused by a UE handover between two or more base stations.
  • the handover may be over an Xn interface from a source gNB to a target gNB, such that the handover is an Xn handover.
  • the two or more base stations may comprise one or more gNBs.
  • the path switch request comprises an N2 path switch request i.e. a request to switch from one N2 path to another N2 path.
  • NG-RAN 215 comprises one or more base stations.
  • NG-RAN 215 comprises one or more gNBs.
  • AMF 205 sends a first PDU session update request for the first PDU session to SMF 211a.
  • the first PDU session update request may comprise a Nsmf_PDUSession_UpdateSMContext Request as described in 3GPP TS 23.501 and 3GPP TS 23.502.
  • SMF 211 a performs session modification and UPF tunnel management for the first PDU session.
  • Example methods of session modification and UPF tunnel management are given in 3GPP TS 23.501 and 3GPP TS 23.502.
  • SMF 211 a may select a new UPF(s) for the first PDU session during this session modification.
  • AMF 205 sends a second PDU session update request for the second PDU session to SMF 211 b.
  • AMF 205 may send the second PDU session update request at approximately the same time as the first PDU session update request.
  • the second PDU session update request may comprise a Nsmf_PDUSession_UpdateSMContext Request as described in 3GPP TS 23.501 and 3GPP TS 23.502.
  • the requests sent at steps 222 and 223 may, in some examples, be sent simultaneously or approximately simultaneously.
  • SMF 211 b performs session modification and UPF tunnel management for the second PDU session.
  • Example methods of session modification and UPF tunnel management are given in 3GPP TS 23.501 and 3GPP TS 23.502.
  • SMF 211 b may select a new UPF(s) for the second PDU session during this session modification.
  • AMF 205 monitors for responses from SMFs 211 a and 211 b for the context request messages sent at 222 and 223. In some examples, AMF 205 monitors for Nsmf_PDUSession_UpdateSMContext Responses.
  • AMF 205 receives a response to the request sent at 222.
  • the response is received from SMF 211 a.
  • the response may comprise information regarding the first PDU session.
  • the response may comprise a Nsmf_PDUSession_UpdateSMContext Response message for the first PDU session.
  • the response sent at 225 may be received before the response sent at 227 because, for example, SMF 211 a may be located at a network edge while SMF 211 b may be located at a central site (non-edge) site of a network.
  • AMF 205 sends an acknowledgement to NG-RAN 215 for the path switch request sent at 221.
  • the acknowledgment may comprise an N2 Path Switch Request acknowledgement.
  • the acknowledgment is sent as soon as AMF 205 receives the response sent at step 225.
  • the acknowledgement may be sent to a target gNB of an Xn handover in NG- RAN 215.
  • the acknowledgement sent at 226 may comprise session information received at AMF 205 from SMF 211 a for the first PDU session.
  • the session information may be sent in a list.
  • the list may be comprise a PDU Session Resource Switched List.
  • the PDU Session Resource Switched List may be considered as a PDU Session Resource Acknowledged List.
  • the list may comprise session information for all PDU sessions for which the AMF 205 has received a PDU session update request response for.
  • the acknowledgment may also comprise a“PDU Session Resource Deferred List”.
  • the PDU Session Resource Deferred List may comprise one or more PDU Session identifiers (IDs) for PDU sessions for which a response has not yet been received to the one or more PDU session update requests sent at 222 and 223. PDU sessions for which a response has not yet been received to the one or more PDU session update requests sent at 222 and 223, for example, can be considered to be “deferred” PDU sessions.
  • IDs PDU Session identifiers
  • NG-RAN 215 can prepare to wait for further acknowledgment messages to arrive.
  • a target gNB in NG-RAN 215 can preserve Xn user plane tunnelling via a source gNB of an Xn handover for a PDU session marked as deferred in the PDU Resource Deferred List.
  • a target gNB of an N2 handover may use a Security Context Information Element included in an N2 Path Switch Request Acknowledge message sent at 226 as defined in“3GPP TS 33.501 ; System Architecture and procedures for the 5G System; Stage 2”.
  • the PDU Session Resource Deferred List sent at 226 would comprise a session ID for a PDU session managed by SMF 211 b.
  • a path switch request acknowledgment at 226 comprising session information of the first PDU session, which may be a latency critical data session and/or a URLLC data transmission, it is not necessary to wait for a response for the second PDU session which may be non-latency critical and/or a non-URLLC data transmission.
  • AMF 205 receives a subsequent response to the request sent at 223.
  • the response may comprise information about the second PDU session.
  • SMF 211 a and SMF 211 b are shown, it will be understood that further SMFs other than SMF 211 b may send responses after step 226.
  • AMF 205 may update the PDU Session Resource Switched List to include session information received from SMF 211 b. AMF 205 may also update the PDU Session Resource Deferred List to remove the Session ID of the second PDU session.
  • AMF 205 sends a second path switch request acknowledgement to NG-RAN 215.
  • Step 228 may take place after one response subsequent to the response at received at 225 is received from a SMF (such as SMF 211 b) in the network.
  • Step 228 may take place after responses from all SMFs in a network are received.
  • Step 228 may take place after a threshold number of responses from SMFs in the network are received.
  • the second patch switch request acknowledgement message may comprise an updated PDU Session Resource Deferred List and updated PDU Session Resource Switched List.
  • the PDU Session Resource Switched List may comprise session information for the first and second PDU session.
  • the PDU Session Resource Deferred List comprises PDU Session ID(s) for one or more PDU sessions for which AMF is still waiting for a response from.
  • the PDU Session Resource Deferred List may comprise no session IDs.
  • the second path switch request acknowledgement message may comprise a Security Context Information Element that can be used by a target gNB of NG-RAN 215.
  • the content of the Security Context Information element for the acknowledgement message sent at 228 is the same as the content of the Security Context Information element for the acknowledgement message sent at 226.
  • the target gNB may check the PDU Session ID with a UE context that is maintained by the target gNB.
  • the target gNB when the PDU Session Resource Switched List is included the target gNB will continue to use the Security Context received in the first path switch request acknowledgement message sent at 226.
  • a security context included in the message sent by the AMF 205 at 226 may be the same as a security context sent by the AMF 205 at 228.
  • the Security Context may be used as specified in 3GPP, TS 33.501.
  • the Security Context can be used to derive (calculate) a security key at the target gNB.
  • the security context from the first path switch request acknowledgement can be used to derive the security key at NG-RAN 215 for the subsequent path switch request acknowledgement messages.
  • the security context received at the NG-RAN 215 in step 226 could be used by a target gNB at step 228. This can prevent changes in Security Context such that the amount of computation at NG-RAN 215 in deriving security keys can be reduced.
  • a security mode control procedure can be used after a final path switch is sent in order to change a security key.
  • the final path switch may be an N2 path switch.
  • NG-RAN 215 may indicate in a N2 Path Switch Request message sent at 221 that NG-RAN 215 will accept deferred PDU sessions by including an information element“Deferred PDU session capabilities”. In some examples, NG- RAN 215 may indicate in“Deferred PDU session capabilities” that it will not accept deferred PDU sessions. AMF 205 may use the absence of“Deferred PDU session capabilities” in N2 Path Switch Request message to detect that NG-RAN 215 either does not accept deferred PDU sessions or does not support“Deferred PDU session capabilities”. Alternatively, NG-RAN 215 may indicate its node level capability to support processing deferred PDU sessions to AMF 205 using a New Generation (NG) Setup Request message (as described in 3GPP; TS 38.413).
  • NG New Generation
  • an AMF is provided with a mechanism in which the AMF can send acknowledgements to a NG-RAN node of tunnel modifications made by a network edge SMF before acknowledging tunnel modifications made by a central SMF.
  • a possible wireless communication device will now be described in more detail with reference to Figure 3 showing a schematic, partially sectioned view of a communication device 300.
  • a communication device is often referred to as user equipment (UE) or terminal.
  • An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals.
  • Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, or any combinations of these or the like.
  • a mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on.
  • Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data.
  • Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information.
  • a wireless communication device may be for example a mobile device, that is, a device not fixed to a particular location, or it may be a stationary device.
  • the wireless device may need human interaction for communication, or may not need human interaction for communication.
  • UE or“user” are used to refer to any type of wireless communication device.
  • the wireless device 300 may receive signals over an air or radio interface 307 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals.
  • transceiver apparatus is designated schematically by block 306.
  • the transceiver apparatus 306 may be provided for example by means of a radio part and associated antenna arrangement.
  • the antenna arrangement may be arranged internally or externally to the wireless device.
  • a wireless device is typically provided with at least one data processing entity 301 , at least one memory 302 and other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices.
  • the data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 304.
  • the user may control the operation of the wireless device by means of a suitable user interface such as key pad 305, voice commands, touch sensitive screen or pad, combinations thereof or the like.
  • a display 308, a speaker and a microphone can be also provided.
  • a wireless communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
  • the communication devices 302, 304, 305 may access the communication system based on various access techniques.
  • Figure 4 shows an example of a control apparatus 400 for a communication system, for example to be coupled to and/or for controlling a station of an access system, such as a RAN node, e.g. a base station, gNB, a central unit of a cloud architecture or a node of a core network such as an MME or S-GW, a scheduling entity such as a spectrum management entity, or a server or host, or an IAB or relay node.
  • the apparatus may be coupled to or be integrated with an AMF and/or SMF.
  • the apparatus 400 may be coupled to an NG-RAN node, or to a part of a UPF.
  • the control apparatus may be integrated with or external to a node or module of a core network or RAN.
  • base stations comprise a separate control apparatus unit or module.
  • the control apparatus can be another network element such as a radio network controller or a spectrum controller.
  • each base station may have such a control apparatus as well as a control apparatus being provided in a radio network controller.
  • the control apparatus 400 can be arranged to provide control on communications in the service area of the system.
  • the control apparatus 400 comprises at least one memory 401 , at least one data processing unit 402, 403 and an input/output interface 404. Via the interface the control apparatus can be coupled to a receiver and a transmitter of the base station.
  • the receiver and/or the transmitter may be implemented as a radio front end or a remote radio head.
  • Figure 5 is a flow chart of a method according to an example. The flow chart of Figure 5 is viewed from the perspective of an apparatus such as AMF 205, for example.
  • 5501 comprises sending, to a first session management function, a first request to update information of a first protocol data unit session.
  • 5502 comprises sending, to a second session management function, a second request to update information of a second protocol data unit session.
  • 5503 comprises receiving a first response to the first request before receiving a second response to the second request.
  • S504 comprises sending a first acknowledgement message to a radio access network before receiving the response to the second request.
  • the first acknowledgement message comprises session information of the first protocol data unit session received in the first response and a list of one or more protocol data unit sessions for which a response is yet to be received, wherein the list comprises a session identifier of the second protocol data unit session.
  • Figure 6 is a flow chart of a method according to an example.
  • the flow chart of Figure 6 is viewed from the perspective of an apparatus such as NG-RAN 215, for example.
  • S601 comprises receiving a first acknowledgement message from an access and mobility management function.
  • the first acknowledgement message comprises information of a first protocol data unit session and a list of protocol data unit sessions for which the access and mobility management function is waiting for updated information, wherein the list comprises a session identifier of a second protocol data unit session.
  • the various example embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • circuitry may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
  • hardware-only circuit implementations such as implementations in only analog and/or digital circuitry
  • combinations of hardware circuits and software such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the example embodiments of this invention may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware.
  • Computer software or program also called program product, including software routines, applets and/or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks.
  • a computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out example embodiments.
  • the one or more computer-executable components may be at least one software code or portions of it.
  • any blocks of the logic flow as in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions.
  • the software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.
  • the physical media is a non-transitory media.
  • the memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.
  • Example embodiments of the inventions may be practiced in various components such as integrated circuit modules.
  • the design of integrated circuits is by and large a highly automated process.
  • Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

Landscapes

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

Abstract

L'invention concerne un appareil comprenant des moyens pour effectuer : l'envoi, à une première fonction de gestion de session (211a), d'une première demande pour mettre à jour des informations d'une première session d'unité de données de protocole; l'envoi, à une seconde fonction de gestion de session (211b), d'une seconde demande pour mettre à jour des informations d'une seconde session d'unité de données de protocole; la réception d'une première réponse à la première demande avant de recevoir une seconde réponse à la seconde demande; l'envoi d'un premier message d'accusé de réception à un réseau d'accès radio (215) avant de recevoir la réponse à la seconde demande; le premier message d'accusé de réception comprenant des informations de session de la première session d'unité de données de protocole reçues dans la première réponse et une liste d'une ou plusieurs sessions d'unité de données de protocole pour lesquelles une réponse reste encore à recevoir, la liste comprenant un identifiant de session de la seconde session d'unité de données de protocole.
PCT/EP2019/065111 2019-06-11 2019-06-11 Appareil, procédé et programme informatique Ceased WO2020249183A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/065111 WO2020249183A1 (fr) 2019-06-11 2019-06-11 Appareil, procédé et programme informatique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/065111 WO2020249183A1 (fr) 2019-06-11 2019-06-11 Appareil, procédé et programme informatique

Publications (1)

Publication Number Publication Date
WO2020249183A1 true WO2020249183A1 (fr) 2020-12-17

Family

ID=66821267

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/065111 Ceased WO2020249183A1 (fr) 2019-06-11 2019-06-11 Appareil, procédé et programme informatique

Country Status (1)

Country Link
WO (1) WO2020249183A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115915180A (zh) * 2021-08-10 2023-04-04 维沃移动通信有限公司 计算会话释放方法、设备及可读存储介质
CN115915179A (zh) * 2021-08-10 2023-04-04 维沃移动通信有限公司 计算会话更新方法、装置、终端及网络功能实体
US20240188047A1 (en) * 2021-08-10 2024-06-06 Vivo Mobile Communication Co., Ltd. Computing session update method and apparatus, and communication device
WO2024255443A1 (fr) * 2023-06-12 2024-12-19 大唐移动通信设备有限公司 Procédé pour effectuer une commutation entre un ran basé sur un service et un ran non basé sur un service, et élément de réseau et appareil

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180098251A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Method and apparatus for serving mobile communication devices using tunneling protocols
WO2018171916A1 (fr) * 2017-03-21 2018-09-27 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et nœud permettant de gérer un transfert intercellulaire dans des réseaux 5g

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180098251A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Method and apparatus for serving mobile communication devices using tunneling protocols
WO2018171916A1 (fr) * 2017-03-21 2018-09-27 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et nœud permettant de gérer un transfert intercellulaire dans des réseaux 5g

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16)", vol. SA WG2, 1 April 2019 (2019-04-01), XP051751807, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/Latest%5FSA2%5FSpecs/DRAFT%5FINTERIM/Archive/23502%2Dg02%5FMCC%5FCorrections%2Ezip> [retrieved on 20190401] *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115915180A (zh) * 2021-08-10 2023-04-04 维沃移动通信有限公司 计算会话释放方法、设备及可读存储介质
CN115915179A (zh) * 2021-08-10 2023-04-04 维沃移动通信有限公司 计算会话更新方法、装置、终端及网络功能实体
US20240188047A1 (en) * 2021-08-10 2024-06-06 Vivo Mobile Communication Co., Ltd. Computing session update method and apparatus, and communication device
EP4387309A4 (fr) * 2021-08-10 2024-11-27 Vivo Mobile Communication Co., Ltd. Procédé et appareil de mise à jour de session de calcul, et dispositif de communication
WO2024255443A1 (fr) * 2023-06-12 2024-12-19 大唐移动通信设备有限公司 Procédé pour effectuer une commutation entre un ran basé sur un service et un ran non basé sur un service, et élément de réseau et appareil

Similar Documents

Publication Publication Date Title
US11438034B2 (en) Apparatuses and methods for a physical random access channel (PRACH) retransmission
WO2020249183A1 (fr) Appareil, procédé et programme informatique
CN107006055A (zh) 用于双连接切换的方法、装置和系统
CN101128054B (zh) 基于访问类别限制列表提供服务状态信息的装置与方法
US11751130B2 (en) Apparatus, method and computer program
WO2020221459A1 (fr) Appareil, procédé et programme informatique
US20230363019A1 (en) Method for information transmission
WO2020260750A1 (fr) Appareil, procédé et programme informatique
US9392631B2 (en) Wireless communication apparatus
US20250037022A1 (en) Apparatus, method and computer program
US12028777B2 (en) Apparatus and method to indicate whether a node is tracking the location of a user equipment
WO2023185929A1 (fr) Procédé et appareil de commande de ressources, terminal et dispositif côté réseau
CN119343954A (zh) 方法、装置和计算机程序
CN108924668B (zh) 图片加载、数据提供方法及装置
US20190140786A1 (en) Method, system and apparatus
CN110166537B (zh) 一种pdu会话建立方法、网络设备和用户终端
EP4254996A1 (fr) Gestion d&#39;adresses de cuup partagées
EP4208965A1 (fr) Procédé, appareil et programme d&#39;ordinateur
CN114269004B (zh) 物联网终端的附着方法和通信方法以及相应的系统
CN115209448B (zh) 终端注册方法、终端及网络侧设备
WO2020169492A1 (fr) Gestion de ressources dans des réseaux de communication
CN115529663A (zh) 资源处理方法、装置、电子设备及存储介质
CN106131209B (zh) 一种提供信息的方法、基站和终端设备
US20190053063A1 (en) Method, system and apparatus
WO2024041470A1 (fr) Procédé de réception de message d&#39;informations de système, procédé d&#39;envoi de message d&#39;informations de système, et terminal et dispositif côté réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19729758

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19729758

Country of ref document: EP

Kind code of ref document: A1