Device, method, and computer program for network slice selection

Abstract

A method includes receiving, at a first network entity, information indicating a first data network identification associated with a request from a communication device; and selecting, at the first network entity, a second data network identification available with respect to the communication device when the first data network identification is not available with respect to the communication device, the selection being dependent on information associated with the communication device.

Description

Technical Field

[0001] The present disclosure relates to an apparatus, a method and a computer program, and is particularly but not exclusively directed to an apparatus, a method and a computer program used in a communication system. Background Art

[0002] A communication system can be viewed as a facility that enables a communication session between two or more entities (such as user terminals, base stations / access points, and / or other nodes) by providing a carrier between the various entities involved in the communication path. A communication system can be provided, for example, by a communication network and one or more compatible communication devices.

[0003] Access to the communication system can be through appropriate communication equipment or terminals. The communication equipment is provided with appropriate signal receiving and transmitting means for achieving communication, such as achieving access to the communication network or direct communication with other communication equipment. The communication equipment can access the carrier provided by the station or access point and transmit and / or receive communications on the carrier.

[0004] Communication systems and associated equipment typically operate according to a given standard or specification that states what the various entities associated with the system are allowed to do and how it should be achieved. Summary of the invention

[0005] According to one aspect, a method is provided, comprising: receiving information at a first network entity indicating a first data network identifier associated with a request from a communication device; and when the first data network identifier is not available with respect to the communication device, selecting at the first network entity a second data network identifier available with respect to the communication device, optionally, the selection depending on information associated with the communication device.

[0006] The method may include determining, at a first network entity, that the first data network identification is unavailable.

[0007] The method may include determining that the first data network identification is unavailable by determining that the first data network identification is one or more of: not supported by the network; not allowed with respect to the communication device; not allowed by a policy associated with the communication device; and not allowed by a subscription associated with the communication device.

[0008] The information associated with the communication device used to select the second network identifier includes one or more of the following: single network slice selection assistance information, an expected service set, communication device capability subscription data and service-related data.

[0009] At least a portion of the information associated with the communication device is provided by the communication device.

[0010] At least a portion of the information associated with the communication device may be provided by the communication device in the request from the communication device.

[0011] The method may include using the second data network identifier to select a second network entity, and causing a message having at least one of the first data identifier and the second data identifier to be sent to the second network entity.

[0012] The method may comprise causing information to be provided to the second network entity, the information indicating which of the first data identifier and the second data identifier is to be used when the second network entity communicates with the communication device.

[0013] The second data network entity may provide session management functionality.

[0014] The method may comprise causing information regarding a configuration problem of the communication device to be sent to a third network entity, the third network entity providing policy information associated with the communication device.

[0015] Information about the configuration problem of the communication device is associated with a first data network identification of the communication device.

[0016] The method may comprise receiving, at the first network entity, information from a third network entity requesting notification of the configuration problem of the communication device.

[0017] The third network entity may provide a policy control function.

[0018] The request from the communication device may include a protocol data unit session request.

[0019] The first entity may include a mobility management function.

[0020] The method may be performed in a first entity or in an apparatus of the first entity.

[0021] According to another aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising the computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least: receive information indicating a first data network identifier associated with a request from a communication device; and when the first data network identifier is not available with respect to the communication device, select a second data network identifier available with respect to the communication device, optionally, the selection depending on information associated with the communication device.

[0022] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to determine that the first data network identification is unavailable.

[0023] The at least one memory and the computer code may be configured to, with the at least one processor, determine that the first data network identifier is unavailable by determining that the first data network identifier is one or more of: not supported by the network; not allowed with respect to the communication device; not allowed by a policy associated with the communication device; and not allowed by a subscription associated with the communication device.

[0024] The information associated with the communication device used to select the second network identifier includes one or more of the following: single network slice selection assistance information, an expected service set, communication device capability subscription data and service-related data.

[0025] At least a portion of the information associated with the communication device is provided by the communication device.

[0026] At least a portion of the information associated with the communication device may be provided by the communication device in the request from the communication device.

[0027] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to use the second data network identifier to select a second network entity, and cause a message having at least one of the first data identifier and the second data identifier to be sent to the second network entity.

[0028] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to cause information to be provided to the second network entity, the information indicating which of the first and second data identifiers is to be used when the second network entity communicates with the communication device.

[0029] The second data network entity may provide session management functionality.

[0030] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to cause information regarding a configuration problem of the communication device to be sent to a third network entity, the third network entity providing policy information associated with the communication device.

[0031] Information about the configuration problem of the communication device is associated with a first data network identification of the communication device.

[0032] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to receive information from a third network entity requesting notification of said configuration problem of said communication device.

[0033] The third network entity may provide a policy control function.

[0034] The request from the communication device may include a protocol data unit session request.

[0035] The apparatus may be provided in a first entity.The first entity may include a mobility management function.

[0036] According to one aspect, an apparatus is provided, comprising a circuit system configured to: receive information indicating a first data network identifier associated with a request from a communication device; and when the first data network identifier is not available with respect to the communication device, select a second data network identifier available with respect to the communication device, the selection optionally depending on information associated with the communication device.

[0037] The circuitry may be configured to determine that the first data network identification is not available.

[0038] The circuit system can be configured to determine that the first data network identifier is unavailable by determining that the first data network identifier is one or more of: not supported by the network; not allowed with respect to the communication device; not allowed by a policy associated with the communication device; and not allowed by a subscription associated with the communication device.

[0039] The information associated with the communication device used to select the second network identifier includes one or more of the following: single network slice selection assistance information, an expected service set, communication device capability subscription data and service-related data.

[0040] At least a portion of the information associated with the communication device is provided by the communication device.

[0041] At least a portion of the information associated with the communication device may be provided by the communication device in the request from the communication device.

[0042] The circuit system may be configured to use the second data network identification to select a second network entity and cause a message having at least one of the first data identification and the second data identification to be sent to the second network entity.

[0043] The circuit system may be configured to cause information to be provided to the second network entity, the information indicating which of the first data identifier and the second data identifier is to be used when the second network entity communicates with the communication device.

[0044] The second data network entity may provide session management functionality.

[0045] The circuitry may be configured such that information regarding configuration issues of the communications device will be sent to a third network entity that provides policy information associated with the communications device.

[0046] The information about the configuration problem of the communication device is associated with a first data network identification of the communication device.

[0047] The circuitry may be configured to receive information from a third network entity requesting notification of the configuration problem of the communication device.

[0048] The third network entity may provide a policy control function.

[0049] The request from the communication device may include a protocol data unit session request.

[0050] The apparatus may be provided in a first entity. The first entity may comprise a mobility management function.

[0051] According to another aspect, an apparatus is provided, comprising components for: receiving information indicating a first data network identification associated with a request from a communication device; and when the first data network identification is not available with respect to the communication device, selecting a second data network identification available with respect to the communication device, the selection optionally depending on information associated with the communication device.

[0052] The component may be configured to determine that the first data network identifier is unavailable.

[0053] Components may be configured to determine that the first data network identifier is unavailable by determining that the first data network identifier is one or more of: not supported by a network; not allowed with respect to the communication device; not allowed by a policy associated with the communication device; and not allowed by a subscription associated with the communication device.

[0054] The information associated with the communication device used to select the second network identifier includes one or more of the following: single network slice selection assistance information, an expected service set, communication device capability subscription data and service-related data.

[0055] At least a portion of the information associated with the communication device may be provided by the communication device.

[0056] At least a portion of the information associated with the communication device may be provided by the communication device in the request from the communication device.

[0057] The component may be configured to use the second data network identifier to select a second network entity, and cause a message having at least one of the first data identifier and the second data identifier to be sent to the second network entity.

[0058] The means may be configured to cause information to be provided to the second network entity, the information indicating which of the first data identifier and the second data identifier is to be used when the second network entity communicates with the communication device.

[0059] The second data network entity may provide session management functionality.

[0060] Means may be provided for causing information regarding configuration issues of the communication device to be sent to a third network entity, the third network entity providing policy information associated with the communication device.

[0061] The information about the configuration problem of the communication device is associated with a first data network identification of the communication device.

[0062] Means may be provided for receiving information from a third network entity requesting notification of said configuration problem of said communication device.

[0063] The third network entity may provide a policy control function.

[0064] The request from the communication device may include a protocol data unit session request.

[0065] The apparatus may be provided in a first entity.The first entity may comprise a mobility management function.

[0066] According to another aspect, a method is provided, the method comprising: receiving, at a second network entity, a request from a first network entity, the request comprising a first data network identifier and a second data network identifier, the first data network identifier being associated with the request from a communication device and being unavailable with respect to the communication device, the second data network identifier being available with respect to the communication device; and providing, by the second network entity, a response to the request, the response being directed to the communication device and comprising at least one of the second data network identifier and the first data network identifier.

[0067] The method may include receiving information from the first network entity indicating which one or more of the first data identifier and the second data identifier are to be used when the second network entity provides the response.

[0068] The second data network entity may provide session management functionality.

[0069] The request from the communication device may include a protocol data unit session request.

[0070] The response to the communication device may include a protocol data session response.

[0071] The first entity may include a mobility management function.

[0072] The method may be performed in the second entity or in an apparatus of the second entity.

[0073] According to another aspect, an apparatus is provided, the apparatus comprising a component for: receiving a request from a first network entity, the request comprising a first data network identifier and a second data network identifier, the first data network identifier being associated with the request from a communication device and being unavailable with respect to the communication device, the second data network identifier being available with respect to the communication device; and providing a response to the request, the response being directed to the communication device and comprising at least one of the second data network identifier and the first data network identifier.

[0074] The component may be configured to receive information from the first network entity, the information indicating which one or more of the first data identifier and the second data identifier are to be used in the response.

[0075] The request from the communication device may include a protocol data unit session request.

[0076] The response to the communication device may include a protocol data session response.

[0077] The first entity may include a mobility management function.

[0078] The means may be in the second entity.The second entity may be a session management function.

[0079] According to another aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least: receive a request from a first network entity, the request comprising a first data network identifier and a second data network identifier, the first data network identifier being associated with the request from a communication device and being unavailable with respect to the communication device, the second data network identifier being available with respect to the communication device; and provide a response to the request, the response being directed to the communication device and comprising at least one of the second data network identifier and the first data network identifier.

[0080] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to receive from the first network entity an indication of which one or more of the first data identifier and the second data identifier are to be used in the response.

[0081] The request from the communication device may include a protocol data unit session request.

[0082] The response to the communication device may include a protocol data session response.

[0083] The first entity may include a mobility management function.

[0084] The means may be provided in the second entity.The second data network entity may provide session management functionality.

[0085] According to another aspect, an apparatus is provided that includes a circuit system that is configured to: receive a request from a first network entity, the request including a first data network identifier and a second data network identifier, the first data network identifier being associated with the request from a communication device and being unavailable with respect to the communication device, the second data network identifier being available with respect to the communication device; and provide a response to the request, the response being directed to the communication device and including at least one of the second data network identifier and the first data network identifier.

[0086] According to another aspect, a method is provided, comprising: causing, by a third network entity, a request to be sent to a first network entity, the request being about when the first network entity selects a second data network identifier available with respect to a communication device when a first data network identifier is not available with respect to the communication device, the first network entity notifying the third network entity, the first data network identifier being associated with the request from the communication device; and when the first network entity selects the second data network identifier, receiving, at the third network entity, a notification from the first network entity, the notification including the second data network identifier and optionally the first data network identifier.

[0087] The method may include, in response to receiving the notification, updating a routing policy associated with the communication device.

[0088] The request from the communication device may include a protocol data unit session request.

[0089] The first entity may include a mobility management function.

[0090] The method may be performed in a third entity or in an apparatus of said third entity.

[0091] The third network entity may provide a policy control function.

[0092] According to another aspect, an apparatus is provided, the apparatus comprising a component for: causing a request to be sent to a first network entity, the request being about when the first network entity selects a second data network identifier available with respect to a communication device when a first data network identifier is not available with respect to the communication device, the first network entity notifying the third network entity, the first data network identifier being associated with the request from the communication device; and when the first network entity selects the second data network identifier, receiving a notification from the first network entity, the notification including the second data network identifier and optionally the first data network identifier.

[0093] Means may be used to update a routing policy associated with the communication device in response to receiving the notification.

[0094] The request from the communication device may include a protocol data unit session request.

[0095] The first entity may include a mobility management function.

[0096] The means may be or be provided in said third entity.

[0097] The third network entity may provide a policy control function.

[0098] According to another aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising the computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least: cause a request to be sent to a first network entity, the request being about when the first network entity selects a second data network identifier available with respect to a communication device when a first data network identifier is not available with respect to the communication device, the first network entity notifying the third network entity, the first data network identifier being associated with the request from the communication device; and when the first network entity selects the second data network identifier, receiving a notification from the first network entity, the notification comprising the second data network identifier and optionally the first data network identifier.

[0099] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to: update a routing policy associated with the communication device in response to receiving the notification.

[0100] The request from the communication device may include a protocol data unit session request.

[0101] The first entity may include a mobility management function.

[0102] The means may be or be provided in said third entity.

[0103] The third network entity may provide a policy control function.

[0104] According to another aspect, an apparatus is provided that includes a circuit system that is configured to: cause a request to be sent to a first network entity, the request being about when the first network entity selects a second data network identifier available with respect to a communication device when a first data network identifier is not available with respect to the communication device, the first network entity notifying the third network entity, the first data network identifier being associated with the request from the communication device; and when the first network entity selects the second data network identifier, receive a notification from the first network entity, the notification including the second data network identifier and optionally the first data network identifier.

[0105] According to another aspect, a method is provided, comprising: causing a request to be sent by a communication device together with a first data network identifier; and receiving information at the communication device indicating that the first data network identifier is updated to a second data network identifier.

[0106] Receiving information may include receiving a response to the request and the second data network identification.

[0107] Receiving information may include receiving an update to routing information.

[0108] The method may comprise providing, in the request, information for use by the first network entity in determining that the first data network identity is to be updated.

[0109] The request may include a protocol data unit session request.

[0110] The received information may be received in a protocol data unit session response.

[0111] The method may be executed in a communication device or an apparatus of the communication device.

[0112] According to another aspect, an apparatus is provided that includes circuitry configured to: cause a request to be sent with a first data network identification; and receive information indicating that the first data network identification is updated to a second data network identification.

[0113] According to another aspect, an apparatus is provided, comprising at least one processor and a memory, the at least one memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least: cause a request to be sent together with a first data network identifier; and receive information indicating that the first data network identifier is updated to a second data network identifier.

[0114] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to receive a response to the request and the second data network identification.

[0115] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to receive an update of the routing information.

[0116] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to provide, in the request, information used by the first network entity to determine that the first data network identity is to be updated.

[0117] The request comprises a protocol data unit session request.

[0118] The received information may be received in a protocol data unit session response.

[0119] The apparatus may be provided in a communication device, or may be the communication device.

[0120] According to another aspect, an apparatus is provided, comprising: causing a request to be sent together with a first data network identifier; and receiving information indicating that the first data network identifier is updated to a second data network identifier.

[0121] The component may be configured to receive a response to the request and the second data network identification.

[0122] The component may be operable to receive updates of routing information.

[0123] The means may be configured to provide, in the request, information used by the first network entity to determine that the first data network identity is to be updated.

[0124] The request may include a protocol data unit session request.

[0125] The received information may be received in a protocol data unit session response.

[0126] The apparatus may be in a communication device or may be the communication device.

[0127] According to another aspect, a method is provided comprising: determining, at a first network entity, information about an incorrect configuration of a communication device; and causing information about the determined incorrect configuration of the communication device to be provided to a third network entity.

[0128] A method may include receiving, at a first network entity, a request from a third network entity requesting that the first network entity notify the third network entity when the first network entity determines a misconfiguration of a communications device.

[0129] Determining the misconfiguration may include determining one or more of the following: a request associated with the communication device includes a data network identifier that is unavailable to the communication device; a request associated with the communication device indicates a session type that is unavailable to the communication device; a request associated with the communication device indicates single network slice selection assistance information that is unavailable to the communication device; and a request associated with the communication device indicates a session and service continuity mode that is unavailable to the communication device.

[0130] The method may include determining that the first data network identification is unavailable by determining that the first data network identification is one or more of: not supported by the network; not allowed with respect to the communication device; not allowed by a policy associated with the communication device; and not allowed by a subscription associated with the communication device.

[0131] The third network entity may provide a policy control function.

[0132] The request associated with the communication device may be a protocol data unit session request.

[0133] The first entity may include a mobility management function or a session management function.

[0134] The method may be performed in a first entity or in an apparatus of the first entity.

[0135] According to another aspect, a method is provided, comprising: receiving information at a first network entity indicating a first data network identification associated with a request from a communication device, the first data network identification being unavailable; and in response, causing information to be provided to a third network entity.

[0136] According to another aspect, an apparatus is provided, comprising at least one processor and at least one memory, the at least one memory including the computer code for one or more programs, the at least one memory and the computer code being configured to, with the at least one processor, cause the apparatus to at least: receive information at a first network entity indicating a first data network identifier associated with a request from a communication device, the first data network identifier being unavailable; and in response, cause information to be provided to a third network entity.

[0137] According to another aspect, an apparatus is provided, the apparatus comprising means for determining, at a first network entity, information regarding an incorrect configuration of a communication device; and causing information regarding the determined incorrect configuration of the communication device to be provided to a third network entity.

[0138] The means may be configured to receive a request from a third network entity, the request requiring the first network entity to notify the third network entity when the first network entity determines an erroneous configuration of the communication device.

[0139] The component can be used to determine the misconfiguration by determining one or more of the following: a request associated with the communication device includes a data network identifier that is unavailable to the communication device; a request associated with the communication device indicates a session type that is unavailable to the communication device; a request associated with the communication device indicates single network slice selection assistance information that is unavailable to the communication device; and a request associated with the communication device indicates a session and service continuity mode that is unavailable to the communication device.

[0140] Components may be configured to determine that the first data network identifier is unavailable by determining that the first data network identifier is one or more of: not supported by a network; not allowed with respect to the communication device; not allowed by a policy associated with the communication device; and not allowed by a subscription associated with the communication device.

[0141] The third network entity may provide a policy control function.

[0142] The request associated with the communication device may be a protocol data unit session request.

[0143] The means may be provided in the first entity or in an apparatus of the first entity.

[0144] The first entity may include a mobility management function or a session management function.

[0145] According to another aspect, an apparatus is provided, comprising at least one processor and a memory, the at least one memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least: determine information about an incorrect configuration of a communication device; and cause information about the determined incorrect configuration of the communication device to be provided to a third network entity.

[0146] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to receive a request from a third network entity requesting the first network entity to notify the third network entity upon determining an erroneous configuration of the communication device.

[0147] At least one memory and computer code may be configured to, together with at least one processor, cause the apparatus to determine the misconfiguration by determining one or more of the following: a request associated with the communication device includes a data network identifier that is unavailable to the communication device; a request associated with the communication device indicates a session type that is unavailable to the communication device; a request associated with the communication device indicates single network slice selection assistance information that is unavailable to the communication device; and a request associated with the communication device indicates a session and service continuity mode that is unavailable to the communication device.

[0148] At least one memory and computer code may be configured to, with at least one processor, determine that the first data network identifier is unavailable by determining that the first data network identifier is one or more of: not supported by a network; not allowed with respect to the communication device; not allowed by a policy associated with the communication device; and not allowed by a subscription associated with the communication device.

[0149] The third network entity may provide a policy control function.

[0150] The request associated with the communication device may be a protocol data unit session request.

[0151] The device may be provided in the first entity or in a device of the first entity

[0152] The first entity may include a mobility management function or a session management function.

[0153] According to another aspect, a method is provided, comprising causing, by a third network entity, a request to be sent to a first network entity, the request requiring the first network entity to notify the third network entity when the first network entity determines an erroneous configuration of a communication device.

[0154] The method may be executed in a third entity or in a device of a third entity.

[0155] The third entity may be a policy control function.

[0156] According to another aspect, an apparatus is provided comprising means for causing, by a third network entity, a request to be sent to a first network entity, the request requiring the first network entity to notify the third network entity when the first network entity determines an erroneous configuration of a communication device.

[0157] The apparatus may be a third entity, or the apparatus may be provided in a third entity.

[0158] The third entity may be a policy control function.

[0159] According to another aspect, an apparatus is provided, comprising at least one processor and at least one memory, the at least one memory including computer code for one or more programs, the at least one memory and the computer code being configured to, with the at least one processor, cause the apparatus to at least cause a request to be sent to a first network entity, the request requiring the first network entity to notify the third network entity when the first network entity determines an incorrect configuration of a communication device.

[0160] The apparatus may be a third entity, or the apparatus may be provided in a third entity.

[0161] The third entity may be a policy control function.

[0162] According to one aspect, there is provided a computer program comprising computer executable code configured to cause any of the aforementioned methods to be performed when run on at least one processor.

[0163] According to one aspect, a computer-readable medium is provided, comprising program instructions stored thereon, the program instructions being used to execute at least one of the above methods.

[0164] According to one aspect, a non-transitory computer-readable medium is provided, comprising the program instructions stored thereon, wherein the program instructions are used to execute at least one of the above methods.

[0165] According to one aspect, a non-volatile tangible storage medium is provided, comprising program instructions stored thereon, the program instructions being used to execute at least one of the above methods.

[0166] In the above, many different aspects are described. It should be understood that further aspects can be provided by combining any two or more of the above aspects.

[0167] Various other aspects are also described in the following detailed description and appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0168] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0169] Figure 1 A schematic diagram of a communication system is shown;

[0170] Figure 2 A schematic diagram of a communication device is shown;

[0171] Figure 3 A schematic diagram of the device is shown;

[0172] Figure 4A schematic diagram of a non-volatile storage medium storing instructions is shown, which, when executed by a processor, allows the processor to perform one or more steps of the method of some embodiments;

[0173] Figure 5 The signaling flow of some embodiments is shown;

[0174] Figure 6 Methods of some embodiments are shown that are performed in a first network entity;

[0175] Figure 7 Methods of some embodiments are shown that are performed in a second network entity;

[0176] Figure 8 The method of some embodiments is shown to be performed in a third network entity;

[0177] Fig. 9 Methods of some embodiments are shown to be performed in a communication device; and

[0178] Fig.10 Another approach of some embodiments is shown. DETAILED DESCRIPTION

[0179] In the following, certain embodiments are explained with reference to a communication device capable of communicating via a wireless cellular system and a communication system serving the communication device. Figures 1 to 4 , certain general principles of wireless communication systems, their access systems and communication devices are briefly explained to help understand the technologies underlying the examples.

[0180] An example of a wireless communication system is an architecture standardized by the 3rd Generation Partnership Project (3GPP). Developments based on the latest 3GPP are generally referred to as 5G. Other examples of radio access systems include wireless access systems provided by base stations of systems based on technologies such as wireless local area networks (WLAN) and / or WiMAX (Worldwide Interoperability for Microwave Access). It should be understood that although some embodiments are described in the context of a 5G system, other embodiments may be provided in any other suitable system, including but not limited to subsequent systems or similar protocols defined outside of the 3GPP discussions.

[0181] refer to Figure 1 , Figure 1 An example system in which some embodiments may be provided is shown. The system may be wireless communication. It should be understood that Figure 1 The system is a 5G system, but other embodiments may be used in conjunction with any other suitable standard or system.

[0182] A communication device 102 is provided. This will be referred to as a UE, but it will be appreciated that the device may be any suitable communication device, and the term UE is intended to encompass any such device. Some examples of communication devices will be discussed below, and the term UE used in this document is intended to encompass any one or more of these devices and / or any other suitable device.

[0183] The communication device has a wireless connection to the access node AN 104. The access node may be a gNB or ng-eNB. It should be understood that the information exchange between the UE and the AMF may alternatively be performed via a non-3GPP access 5GC (5G core network). For example, this may be via a non-3GPP interconnection function for non-3gpp access N3IWF, a trusted non-3GPP access function TNGF, an access gateway for wired access W-AGF, or any other similar function.

[0184] AN 104 is configured to communicate with an access and mobility management function (AMF) 110. The AMF may provide functions related to UE-based authentication, authorization, registration, mobility and / or connection management.

[0185] The AMF 110 is configured to communicate with a session management function (SMF) 112. The SMF may provide session management functions, such as allocating an Internet Protocol (IP) address to a UE.

[0186] AMF 110 and SMF 112 are configured to communicate with a policy control function (PCF) 114. The PCF may determine, for a given UE, policies regarding mobility and session management for enforcement by the UE, AMF or SMF.

[0187] The access node AN 104 is configured to communicate with a user plane function (UPF) 106. The UPF 106 is configured to communicate with a data network DN 108.

[0188] Figure 2 An example of a communication device 300 is shown, such as Figure 1 102, 104 or 105 shown in the figure. The wireless communication device 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include a mobile station (MS) or mobile device, such as a mobile phone or so-called "smart phone", a computer provided with a wireless interface card or other wireless interface (e.g., a USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine type communication (MTC) device, an IoT type communication device, or any combination of these devices.

[0189] The device 300 may receive signals over the air or radio interface 307 via suitable means for receiving, and may transmit signals via suitable means for transmitting radio signals. Figure 2 In the mobile device, the transceiver device is schematically designated by block 306. The transceiver device 306 may be provided, for example, by a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0190] The wireless communication device 300 may be provided with at least one processor 301a and at least one memory. The at least one memory may include at least one ROM 302a and / or at least one RAM 302b. The communication device may include other possible components 303 for use in software and hardware assisted execution of the tasks it is designed to perform, including access control and communication with access systems and other communication devices. At least one processor 301 is coupled to at least one memory. At least one processor 301 may be configured to execute appropriate software code 308 to implement one or more of the following aspects. The software code 308 may be stored in at least one memory, for example, in at least one ROM 211b.

[0191] The communication device may include other possible components 303 for use in software and hardware to assist in performing the tasks it is designed to perform, including control of access and communications with access systems and other communication devices.

[0192] The processor, storage means and other related control means may be provided on an appropriate circuit board and / or in a chipset. This feature is indicated by reference 304 .

[0193] The device may optionally have a user interface, such as a keyboard 305, a touch-sensitive screen or keyboard, a combination thereof, or the like.

[0194] Depending on the type of device, one or more of a display, speaker and microphone may optionally be provided.

[0195] The communication protocol and / or parameters that should be used for the connection are also typically defined.A communication device can access a communication system based on various access technologies.

[0196] The example device is Figure 3 is shown in . Figure 3An example of an apparatus 200 for a network function is shown, such as AMF or PCF or SMF or any other suitable function. The apparatus includes at least one memory. The at least one memory may be at least one random access memory (RAM) 211a and / or at least one read-only memory (ROM) 211b, at least one processor 212, 213 and an input / output interface 214. At least one processor 212, 213 is coupled to the RAM 211a and the ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215 to implement one or more of the following aspects. The software code 215 may be stored in the ROM 211b.

[0197] Figure 4 A schematic diagram of a non-volatile storage medium 1600a (e.g., a computer disk (CD) or digital versatile disk (DVD)) and 1200b (e.g., a universal serial bus (USB) memory stick) storing instructions and / or parameters 1602 that, when executed by a processor, allow the processor to perform one or more steps of any method of any embodiment.

[0198] One or more of the following aspects are related to a 5G system (5GS). (5G is sometimes referred to as New Radio (NR)). However, it should be understood that some of these aspects may be transposed for other radio access technology systems, such as UTRAN (3G radio), Long Term Evolution (LTE) of Universal Mobile Telecommunications System (UMTS), and / or any other suitable system.

[0199] In some embodiments, the first network entity (such as, AMF) may receive signaling information from N1 from the UE indicating the first (requested) data network identity or data network name (DNN).

[0200] The first network entity may detect that the first (requested) data network identity is not supported by the network and / or is not allowed by a subscription and / or policy associated with the UE.

[0201] The first network entity may consider further information in the UE subscription and / or the UE request and select a second (accepted) data network identity (DNN) supported by the network and the subscription and / or policy associated with the user.

[0202] If the first network entity chooses to replace the DNN requested by the UE by the second (accepted) DNN, the first network entity uses the second DNN for the remaining process, including passing the second (accepted) DNN to the second network entity for operations related to the PDU session. The second network entity may be an SMF.

[0203] The first network entity may also communicate an indication to the second network entity as to whether the second network entity expects the UE's requested or second (accepted) DNN to be included in the SMF response to the UE. The response may be a PDU Session Establishment Accept response. The indication may be implicit (by including the UE's requested DNN and the second DNN) or explicit by including a specific indicator to send the DNN to the UE.

[0204] The data used by the first entity to determine whether it needs to consider another DNN (second data network identifier) ​​in addition to the DNN requested by the UE may include one or more of the following: data identifying the expected service set; service-related data; and capabilities of the communication device.

[0205] In some embodiments, the data identifying the intended service set may be S-NSSAI (Single Network Slice Selection Assistance Information) data, etc. A network slice is a logical end-to-end network. Each slice can serve a specific service type. For example, a communication device can access multiple slices through the same (R)AN (or a 5G AN entity connects the UE to the 5GC). S-NSSAI is used to identify network slices that support a specific service set. In some embodiments, S-NSSAI may include SST (Slice / Service Type) and / or SD (Slice Differentiator). When performing selection of the second (acceptable) data network identifier (DNN), the AMF may consider only the SST or all S-NSSAI.

[0206] SST refers to network slicing behavior based on functions and services. In some embodiments, SST may identify one of eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communication), or MIoT (massive internet of things). It should be understood that, alternatively or additionally, SST may identify any other suitable service type.

[0207] SD differentiates different slices of the same slice / service type. S-NSSAI can be associated with one or more network IDs, such as PLMN ID, network-specific value, standard value.

[0208] The S-NSSAI may be provided by the UE or may be a subscribed S-NSSAI identifying the expected service set.

[0209] In some embodiments, the capabilities of the data related to the communication device may include, for example, CIoT (Cellular IoT) capabilities. This may be provided by the communication device. This information may be provided as part of the preferred network behavior of the communication device. Alternatively or additionally, different device capability data may be provided.

[0210] The service-related data may be provided by the communication device and / or included in the subscription data.

[0211] In some embodiments, based on one or more of the above criteria, the AMF may replace the requested explicit (i.e., non-empty) DNN value with another DNN value. The AMF may notify the PCF that a DNN configuration problem in the UE has been detected. The PCF updates the UE (communication device) policy of the communication device. The policy has been updated because the previous policy has become obsolete due to the communication device requesting an unsupported DNN. The AMF notification to the PCF may be controlled by an explicit request from the PCF so that the AMF requests a policy update (indicating that a DNN configuration problem in the UE has been detected) from the PCF when the AMF detects this UE configuration problem.

[0212] The updating of the policy provides a mechanism whereby communication device(s) UE with outdated configuration are determined and repair of the configuration policy is triggered.

[0213] The AMF indication that a DNN configuration issue in the UE has been detected may trigger the PCF to perform a UE policy configuration (URSP – UE Routing Selection Policy) update.

[0214] Some embodiments provide a method by which the AMF can decide which of the supported DNNs to use instead of an unsupported DNN requested by the communication device.

[0215] Now refer to Figure 5 Describes an example of the interaction between the communication device, AMF and PCF.

[0216] In step S1, as part of the policy information about the UE sent to the AMF, the PCF sends a request to the AMF to be notified when a configuration problem in the UE is detected. This may be a misconfiguration problem in the UE. In some embodiments, the configuration problem may be a DNN problem. However, in other embodiments, the misconfiguration problem may be any other suitable misconfiguration problem.

[0217] The request may be for a specific communication device or any UE for which the PCF stores policy information. The notification from the AMF may be any appropriate update. In some embodiments, the notification may be an Npcf_AM Policy Control_Update message.

[0218] In step S2, the UE sends a PDU (Protocol Data Unit) session establishment request to the 5GC (5G Core Network) processed by the AMF. The UE can provide the requested DNN that the AMF needs to consider, because the AMF needs a DNN for SMF selection.

[0219] In step S3, the AMF determines that there is a problem with the DNN requested by the UE.

[0220] The problem may be that the DNN in the request is not supported by the network or by the UE's subscription. In this case, the AMF may select a supported DNN. This may be as described above. The selection may take into account one or more S-NSSAI information, UE capability information (such as CIoT support and preferred network behavior), and subscription information related to S-NSSAI and / or CIoT.

[0221] After replacing the UE's requested DNN with the supported DNN, the AMF uses the supported DNN in the network for selecting the SMF. In step S4, the AMF sends a PDU session request to the SMF. The request may include the updated DNN and, optionally, the DNN requested by the UE. The AMF may optionally pass an indication to the SMF as to whether the SMF expects to include the requested UE or the second (accepted) DNN in the SMF response to the UE. The indication may be implicit (by including both the UE's requested DNN and the second DNN) or explicit by including a specific indicator to send the DNN to the UE.

[0222] In the PDU session related process, the SMF includes the DNN. The included (multiple) DNNs may depend on the information received from the AMF. For example, in step S5, the SMF sends a PDU session accept message to the AMF using the updated DNN.

[0223] In step S6, the PDU session accept message provided by the SMF to the AMF can be directed by the AMF to the UE.

[0224] The AMF may indicate to the SMF (in step S4) whether the replaced DNN may be displayed to the UE, or whether the DNN replacement needs to be performed only within the network and hidden from the UE. The UE may include the requested DNN in its request (see step S2) message, and the SMF includes the DNN in an SMF reply message (such as a PDU Session Establishment Accept message) (this may be the message of step S5). Messages from the SMF may be carried by the AMF in a downlink container. The AMF is not expected to open the SMF container or change its contents. Therefore, the AMF needs to inform the SMF what value to send if the DNN requested by the UE has changed. For example, in a message directed to the UE, the AMF informs the SMF whether to use the replaced DNN or the DNN requested by the UE (step S6).

[0225] It should be understood that the SMF may use the DNN requested by the UE in the response message. For example, as described later, the DNN value is updated by the PCF. However, in some embodiments, even if the DNN value is updated by the PCF as described later, the SMF may use the updated DNN value.

[0226] It should be understood that in some embodiments, when the SMF uses the UE-requested DNN value in its message, the core network component may use an updated DNN value.

[0227] As described above, when a DNN configuration problem is detected in a communication device, the AMF may be configured (by the PCF in step S1) to determine that a PCRT (Policy Control Request Trigger) condition has occurred.

[0228] In some embodiments, this condition may be set by the PCF at the initialization of the AMF-PCF association related to the policy for the UE.

[0229] In some embodiments, this condition may be removed or demolished by the PCF as a trigger condition.

[0230] In step S7, when the AMF detects a DNN configuration problem in the communication equipment conditions, the AMF issues an update to the PCF. This may be an Npcf_UE Policy Control_Update message or any other message sent to the PCF. The update message may include one or more of the following: the S-NSSAI received from the UE, the corresponding S-NNSAI used by the HPLMN (Home Public Land Mobile Network) (if different), and the DNN received from the UE.

[0231] In step S8, the update message may trigger the PCF to update the information associated with the communication device. This may ensure that the UE has an updated DNN. The UE may store the updated DNN. For example, the PCF may update the URSP associated with the communication device. The update from the PCF to the UE may include an update to the URSP rules. The URSP rules indicate which DNN the UE should use to carry the application's traffic. When the application is started on the UE, the UE will ensure that a PDU session is established for the DNN configured in the URSP. In some embodiments, the UE will store new or updated URSP rules with an updated DNN.

[0232] In some embodiments, steps S7 and S8 may be run in parallel with steps S4 to S6, or even occur before these steps.

[0233] In some embodiments, steps S1 , S7 and S8 may be omitted.

[0234] In some embodiments, step S6 may be omitted.

[0235] In another embodiment, the AMF may determine that there is a problem with the DNN. When the problem is determined, the AMF may cause the SMF to return a response to the UE with an updated DNN. The UE then updates its stored DNN to the updated DNN and uses the updated DNN in the future. In some embodiments, the response from the network corresponds to a PDU session accept response from step S6 of the SMF. Therefore, the message can be used by the UE to detect that the network has replaced the DNN requested by the UE with another DNN that the serving network wants to use, rather than the DNN requested by the UE. In this way, the UE can store the updated DNN replaced by the network in place of the DNN requested by the UE, or as an alias for the DNN requested by the UE. In this way, the network dynamically indicates to the UE that the DNN requested by the UE is invalid, and that the UE should start using another ("updated") DNN instead of the one it requested. In this embodiment, steps S1, S7 and S8 may be omitted.

[0236] It should be understood that 5GC (5G core network) supports PDU connection service, that is, a service that provides PDU exchange between a communication network and a data network identified by a DNN. The PDU connection service can be supported via a PDU session, which is established based on a request from a communication device.

[0237] The subscription information for each S-NSSAI may contain a list of subscribed DNNs and a default DNN. When the communication device does not provide a DNN in the NAS (non-access layer message) containing a PDU session establishment request for a given S-NSSAI, if a default DNN exists in the subscription information, the serving AMF determines the DNN for the requested PDU session by selecting the default DNN for the S-NSSAI. Otherwise, the serving AMF selects the DNN corresponding to the S-NSSAI. This may be as described above.

[0238] If the DNN offered by the communication device is not supported by the network and the AMF cannot select an SMF by querying the NRF (e.g. the NRF does not provide an SMF either in the HPLMN or in the local PLMN that supports the requested DNN), the AMF replaces the unsupported DNN with a supported DNN. This may be as outlined above. When determining which DNN value to use, the AMF may take into account the S-NSSAI indicated by the UE and the UE's preferred network behavior or subscription data or both.

[0239] refer to Figure 6, which illustrates a method of some embodiments. The method may be performed in a first network entity, or may be performed by an apparatus in the first network entity. The apparatus may include at least one processor and at least one memory, the memory including computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least perform Figure 6 method.

[0240] In step A1 , the first network receives information from the communication device, the information indicating a first data network identification associated with the request.

[0241] In step A2, when the first data network identifier is not available for the communication device, the first network entity selects a second data network identifier that is available for the communication device, the selection depending on information associated with the communication device.

[0242] The first network entity may be an AMF or any other suitable network entity.

[0243] refer to Figure 7 , which illustrates a method of some embodiments. The method may be performed in the second network entity, or may be performed by an apparatus in the second network entity. The apparatus may include at least one processor and at least one memory, the memory including computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least perform Figure 7 method.

[0244] In step B2, the second network entity receives a request from the first network entity, the request including a first data network identifier associated with the request from the communication device and unavailable to the communication device, and a second data network identifier available to the communication device.

[0245] In step B2, the second network entity provides a response to the request, wherein the response is directed to the communication device and includes at least one of the second data network identifier and the first data network identifier.

[0246] The second network entity may be a SMF or any other suitable network function.

[0247] refer to Figure 8, which illustrates the methods of some embodiments. The method may be executed in a third network entity, or may be executed by a device in the third network entity. The device may include at least one processor and at least one memory, the memory including computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the device to at least execute Figure 8 method.

[0248] In step C1, the third network entity causes a request to be sent to the first network entity, the request being about the first network entity notifying the third network entity when the first network entity selects a second data network identification available with respect to the communication device when a first data network identification is not available with respect to the communication device, the first network entity notifying the third network entity, the first data network identification being associated with the request from the communication device.

[0249] In step C2, when the first network entity selects the second data network identifier, the third network entity receives a notification from the first network entity, the notification including the second data network identifier and the optional first data network identifier. The third network entity may be a PCF or any other suitable network function.

[0250] refer to Fig. 9 , which illustrates a method of some embodiments. The method may be performed in a communication device or by an apparatus in a communication device. The apparatus may include at least one processor and at least one memory, the memory including computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least perform Fig. 9 method.

[0251] In step D1 , the communication device causes a request to be sent together with a first data network identification.

[0252] In step D2, the communication device receives information indicating that the first data network identifier is updated to a second data network identifier.

[0253] refer to Fig.10 , Fig.10 Another embodiment is shown.

[0254] In step T1, the network function receives a request from PCF 114, which requires the network function to notify the PCF when there is an incorrect configuration of the communication device. The network function may be an AMF, an SMF, or any other suitable network function. In some embodiments, this step may be optional.

[0255] In step T2, the network function determines that there is an incorrect configuration of the communication device.

[0256] In step T3, the network function causes a notification of the misconfiguration to be provided to the PCF.

[0257] For example, in step T2, AMF detects a user request for PDU session establishment for an unknown DNN or a DNN to which the user is not subscribed (as described above). In this case, it is AMF that notifies PCF in step T3.

[0258] In another example, the AMF of the HPLMN detects a user registration request for an unknown S-NSSAI or an S-NSSAI to which the user is not subscribed in step T2. In this case, the AMF notifies the PCF in step T3.

[0259] In another example, in step T2, SMF detects a UE request for PDU session establishment for an unknown PDU session type or a PDU session type that the user has not subscribed to or is incompatible with DNN. In this case, it is the SMF that notifies the PCF in step T3.

[0260] In another example, in step T2, SMF detects a UE request for PDU session establishment for an unknown SSC (session and service continuity) mode or an SSC mode that the user has not subscribed to or is incompatible with DNN. In this case, it is the SMF that notifies the PCF in step T3.

[0261] Note that although example embodiments are described above, several variations and modifications may be made to the disclosed solution without departing from the scope of the invention. For example, the above aspects are not limited to 5GS. These aspects may be transposed to other radio access technology systems.

[0262] Therefore, the embodiments may vary within the scope of the appended claims. Generally, some embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be performed by a controller, microprocessor, or other computing device, although the embodiments are not limited thereto. Although various embodiments may be shown and described as block diagrams, flow charts, or using some other graphical representation, it is well known that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0263] The embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the entity involved or by hardware or a combination of software and hardware. Furthermore, in this regard, it should be noted that any process, e.g. Figures 5 to 10The processes in the software 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 physical media such as memory chips or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as DVD and its data variants CD.

[0264] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include one or more general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), gate-level circuits, and processors based on multi-core processor architectures, as non-limiting examples.

[0265] Alternatively or additionally, some embodiments may be implemented using a circuit system. The circuit system may be configured to perform one or more of the aforementioned functions and / or method steps. The circuit system may be provided in a base station and / or a communication device.

[0266] The term "circuitry" as used in this application may refer to one or more or all of the following:

[0267] (a) Pure hardware circuit implementation (such as implementation only in analog and / or digital circuit systems);

[0268] (b) a combination of hardware circuitry and software, such as:

[0269] (i) a combination of analog and / or (multiple) digital hardware circuits and software / firmware, and

[0270] (ii) any portion of hardware processor(s) with software (including digital signal processor(s), software and memory that work together to enable an apparatus (such as a communication device or base station) to perform the various functions described above; and

[0271] (c) Hardware circuit(s) and / or processor(s) that require software (e.g., firmware) for operation, such as microprocessor(s) or portions of microprocessor(s), but where the software is not needed for operation, the software may not be present.

[0272] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also includes an implementation of merely a hardware circuit or processor (or multiple processors) or portions of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuitry" also covers, for example, an integrated device.

[0273] The foregoing description has provided a complete and informative description of some embodiments by way of illustrative, non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description when read in conjunction with the accompanying drawings and the appended claims. Nevertheless, all such and similar modifications of the teachings will still fall within the scope defined by the appended claims.

Claims

1. A method for communication, the method comprising: The following request is sent by a third network entity of the network to a first network entity of the network: the third network entity is notified when the first network entity determines a data network name DNN configuration problem in a communication device, wherein the DNN configuration problem in the communication device is determined by the first network entity when the communication device requests a DNN and the network does not support the DNN; as well as A notification regarding the DNN configuration problem in the communication device is received (T3) by the third network entity from the first network entity.

2. The method of claim 1, wherein the request is part of a policy control message sent to an access and mobility function.

3. The method according to claim 1, further comprising: updating URSP rules associated with the communication device; and The updated URSP rule is sent to the communication device, wherein the updated URSP rule indicates another data network name, the another data network name identifying another data network to be used to carry traffic of the communication device. The method of claim 1 , wherein receiving the notification comprises receiving an Npcf_UEPolicyControl_Update message.

5. The method according to any one of claims 1 to 4, wherein the third network entity comprises a policy control function and the first network entity comprises an access and mobility function.

6. A method for communication, comprising: receiving (S1) at a first network entity of a network from a third network entity of the network a request that the third network entity be notified when the first network entity determines a data network name DNN configuration problem in a communication device; receiving, at the first network entity, N1 signaling from the communication device, the N1 signaling indicating a DNN requested by the communication device; determining, at the first network entity, that a DNN configuration problem exists in the communication device, wherein the DNN configuration problem is determined when the network does not support the DNN requested by the communication device; as well as A notification regarding the DNN configuration problem in the communication device is sent (S7) by the first network entity to the third network entity.

7. The method of claim 6, wherein the request is part of policy control information received from a policy control function. The method of claim 6 , wherein sending the notification comprises sending an Npcf_UEPolicyControl_Update message.

9. The method of claim 6, wherein the N1 signaling comprises a PDU session establishment request.

10. The method according to any of claims 6 to 9, wherein the third network entity comprises a policy control function and the first network entity comprises an access and mobility function.

11. A third network entity of a network, comprising at least one processor and a memory, the at least one memory comprising computer code, wherein the at least one memory and the computer code are configured to, together with the at least one processor, cause the third network entity to at least perform: sending, by the third network entity, a request to a first network entity of the network, the third network entity being notified when the first network entity determines a data network name DNN configuration problem in a communication device, wherein the DNN configuration problem in the communication device is determined by the first network entity when the communication device requests a DNN and the network does not support the DNN; and A notification regarding the DNN configuration problem in the communication device is received (T3) by the third network entity from the first network entity.

12. The third network entity according to claim 11, wherein the request is part of a policy control information sent to an access and mobility function.

13. The third network entity according to claim 11, wherein the at least one memory and the computer code are configured to, together with the at least one processor, cause the third network entity to at least perform: updating URSP rules associated with the communication device; and The updated URSP rule is sent to the communication device, wherein the updated URSP rule indicates another data network name, the another data network name identifying another data network to be used to carry traffic of the communication device.

14. The third network entity of claim 11, wherein receiving the notification comprises receiving an Npcf_UEPolicyControl_Update message.

15. The third network entity according to any of claims 11 to 14, wherein the third network entity comprises a policy control function and the first network entity comprises an access and mobility function.

16. A first network entity of a network, comprising at least one processor and at least one memory, the at least one memory comprising computer code, the at least one memory and the computer code being configured to, together with the at least one processor, cause the first network entity to at least perform: receiving (S1) at the first network entity a request from a third network entity of the network, the third network entity being notified when the first network entity determines a data network name DNN configuration problem in a communication device; receiving, at the first network entity, N1 signaling from the communication device, the N1 signaling indicating a DNN requested by the communication device; determining a DNN configuration problem in the communication device, wherein the DNN configuration problem is determined when the network does not support the DNN requested by the communication device; and A notification regarding the DNN configuration problem in the communication device is sent (S7) to the third network entity.

17. The first network entity of claim 16, wherein the request is part of policy control information received from a policy control function.

18. The first network entity of claim 16, wherein sending the notification comprises sending an Npcf_UEPolicyControl_Update message.

19. The first network entity of claim 16, wherein the N1 signaling comprises a PDU session establishment request.

20. The first network entity according to any of claims 16 to 19, wherein the third network entity comprises a policy control function and the first network entity comprises an access and mobility function.

21. A computer readable medium comprising program instructions stored thereon, the program instructions being used to execute the method according to any one of claims 1 to 10.

Images