Application of the influence on slice selection

Abstract

Example embodiments of the present disclosure relate to application function impact on slice selection. A method includes receiving, at a first network entity from a second network entity via at least one third network entity, configuration information for a device, wherein the configuration information includes at least one application area reference identity, the at least one application area reference identity being associated with an application service area for the device; determining, at the first network entity, information about the application service area corresponding to the at least one application area reference identity based on a relationship between the application service area and the application area reference identity; and transmitting, at the first network entity to the device, the information about the application service area.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more specifically to methods, apparatuses, devices, and computer-readable storage media for influencing application functionality in slice selection. Background Technology

[0002] A communication network can be used as a facility to enable communication between two or more communication devices or to provide communication devices with access to a data network. A mobile or wireless communication network is an example of a communication network. Services can be provided to communication devices by an application server.

[0003] Communication networks can operate according to standards provided by organizations such as the 3rd Generation Partnership Project (3GPP) or the European Telecommunications Standards Institute (ETSI). Examples of standards provided by 3GPP are the so-called 3GPP standards for cellular technologies, such as those for 4G, 5G, and 6G technologies. Summary of the Invention

[0004] In a first aspect of this disclosure, a first network entity is provided. The first network entity includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: receive configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application region reference identifier, the at least one application region reference identifier being associated with an application service region for the device; determine information about an application service region corresponding to the at least one application region reference identifier based on a relationship between the application service region and the application region reference identifier; and transmit the information about the application service region to the device.

[0005] In a second aspect of this disclosure, a second network entity is provided. The second network entity includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: determine configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region; and transmit the configuration information for the device to the first network entity via at least one third network entity.

[0006] In a third aspect of this disclosure, an apparatus is provided. The apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause a first network entity to at least: receive information from the first network entity, wherein the information includes information about an application service area of ​​a network slice and the service duration of the application service area; and perform communication on the application service area based on the information.

[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application region reference identifier, the at least one application region reference identifier being associated with an application service region for the device; determining information about an application service region corresponding to the at least one application region reference identifier based on a relationship between the application service region and the application region reference identifier; and transmitting the information about the application service region to the device.

[0008] In a fifth aspect of this disclosure, a method is provided. The method includes: determining configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region; and transmitting the configuration information for the device to a first network entity via at least one third network entity.

[0009] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving information from a first network entity, wherein the information includes information about an application service area of ​​a network slice and the service duration of the application service area; and performing communication on the application service area based on the information.

[0010] In a seventh aspect of this disclosure, a first network entity is provided. The first network entity includes: means for receiving configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application area reference identifier, the at least one application area reference identifier being associated with an application service area for the device; means for determining information about an application service area corresponding to the at least one application area reference identifier based on a relationship between the application service area and the application area reference identifier; and means for transmitting the information about the application service area to the device.

[0011] In an eighth aspect of this disclosure, a second network entity is provided. The second network entity includes: components for determining configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region; and components for transmitting the configuration information for the device to a first network entity via at least one third network entity.

[0012] In a ninth aspect of this disclosure, an apparatus is provided. The apparatus includes: components for receiving information from a first network entity, wherein the information includes information about an application service area of ​​a network slice and the service duration of the application service area; and components for performing communication on the application service area based on the information.

[0013] In a tenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect, the fifth aspect, or the sixth aspect.

[0014] In the eleventh aspect of this disclosure, a computer program including instructions is provided, wherein the computer program is executed by at least one processor of a device, the device causing the device to perform at least the method according to the fourth aspect, the fifth aspect, or the sixth aspect.

[0015] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0016] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 The signaling flow illustrating the process by which AF affects an application service area according to some example embodiments of this disclosure is shown; Figure 3 The signaling flow illustrates an example process for determining and transmitting at least one application area reference ID according to some example embodiments of this disclosure; Figure 4 The signaling flow shown is an example procedure for transmitting at least one application area reference ID according to some example embodiments of this disclosure; Figure 5 The signaling flow shown is an example procedure for transmitting at least one application area reference ID according to some example embodiments of this disclosure; Figure 6 The signaling flow shown is an example procedure for transmitting at least one application area reference ID according to some example embodiments of this disclosure; Figure 7 The signaling flow shown is an example procedure for transmitting at least one application area reference ID according to some example embodiments of this disclosure; Figure 8 The signaling flow illustrating the process by which AF affects an application service area according to some example embodiments of this disclosure is shown; Figure 9 A schematic diagram of an example architecture that can implement the solutions provided in this disclosure is shown; Figure 10 The signaling flow shown is an example procedure for transmitting at least one application area reference ID according to some example embodiments of this disclosure; Figure 11 The signaling flow shown is an example procedure for transmitting at least one application area reference ID according to some example embodiments of this disclosure; Figure 12 A flowchart is shown illustrating a method implemented at a first network entity according to some example embodiments of the present disclosure; Figure 13 A flowchart is shown illustrating a method implemented at a second network entity according to some example embodiments of this disclosure; Figure 14 A flowchart is shown illustrating a method implemented at a device according to some example embodiments of the present disclosure; Figure 15 A flowchart is shown illustrating a method implemented at a first network entity according to some exemplary embodiments of the present disclosure; Figure 16 A flowchart is shown illustrating a method implemented at a second network entity according to some exemplary embodiments of the present disclosure; Figure 17 A flowchart is shown illustrating a method implemented at an apparatus according to some example embodiments of the present disclosure; Figure 18 A flowchart is shown illustrating a method implemented at a radio access network device according to some example embodiments of the present disclosure; Figure 19 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 20 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0017] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0018] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0019] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0020] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment includes that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, it is to be noted that those skilled in the art will recognize, whether explicitly described or not, that such features, structures, or characteristics apply in conjunction with other embodiments.

[0021] It should be understood that although terms such as "first," "second," etc., preceding nouns may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another, and they do not restrict the order of the nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0022] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions, wherein the list of two or more elements is connected by “and” or “or”, means at least one of these elements, or any two or more of these elements, or at least all of these elements.

[0023] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used herein, the terms “comprising,” “including,” “having,” “possessing,” “containing,” and / or “comprising encompassing” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0025] As used in this application, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions), and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts of (multiple) microprocessors, but the software may be absent when the operation does not require the software.

[0026] This definition of "circuit" applies to all uses of the term in this application. As a further example, as used in this application, the term "circuit" also covers only hardware circuitry or processors (or processors), or portions of hardware circuitry or servers and their accompanying software and / or firmware implementations. For example, where applicable to certain claim elements, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0027] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as fifth-generation (5G) systems, Long Term Evolution (LTE), LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) New Radio (NR) communication protocols, and / or any other currently known or under development protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, future types of communication technologies and systems that can implement this disclosure will inevitably emerge. The scope of this disclosure should not be considered limited to the systems described above.

[0028] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header End (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femto, pico, or non-terrestrial network (NTN)) or non-terrestrial network equipment (such as satellite network equipment), low Earth orbit (LEO) satellites and geostationary Earth orbit (GEO) satellites, spacecraft network equipment, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves as a UE facing the parent node, and the DU portion of the IAB node behaves as a base station facing the next-hop IAB node.

[0029] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, smart devices, wireless client equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal equipment may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.

[0030] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0031] The core network functions described herein can be implemented as core network entities comprising a combination of hardware processing circuitry and software and / or firmware including machine-readable instructions, or software including machine-readable instructions executable by at least one processor of the hardware processing circuitry. The hardware processing circuitry includes at least one processor and at least one memory storing machine-readable instructions executable by at least one processor of the hardware processing circuitry. The processor includes any one or a combination of accelerators, microprocessors, cores of multi-core microprocessors, microcontrollers, programmable integrated circuits, programmable gate arrays, digital signal processors, central processing units, graphics processing units, and tensor processing units. The memory includes any or a combination of volatile or non-volatile memory (e.g., flash memory, cache, random access memory (RAM), and / or read-only memory (ROM)). The memory stores machine-readable instructions for the software and / or firmware to be executed by at least one processor of the hardware processing circuitry. The machine-readable instructions can be executed by at least one processor of the hardware processing circuitry, causing the hardware processing circuitry to perform the actions or operations of the methods described herein. For example, the session management function described herein can be implemented as a session management entity, and correspondingly, the session management policy control function described herein can be implemented as a session management policy control entity.

[0032] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure can be implemented is shown. For example... Figure 1 As shown, the communication environment 100 may involve multiple communication devices, including a first network entity 110 and a second network entity 120 of the core network, as well as apparatus 130, radio access network (RAN) equipment 140 and operator equipment 150.

[0033] exist Figure 1In the example, device 130 may be a UE, and RAN device 140 may be a base station serving the UE. First network entity 110 and second network entity 120 may be core network entities in the core network that support communication between device 130, RAN device 140, and other network entities. An example of first network entity 110 may implement or include Access and Mobility Management (AMF) functions for device 130. An example of second network entity may implement or include Application Functions (AF). For example, device 130 may be or be included in a terminal device served by RAN device 140, and RAN device 140 may be implemented as or include a gNB.

[0034] Operator equipment 150 may be equipment associated with or implemented at a network operator and may be responsible for managing, maintaining, and operating the network, such as monitoring, troubleshooting, and ensuring network stability. Examples of operator equipment 150 may include an Operations, Administration, and Maintenance (OAM) entity.

[0035] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure.

[0036] In the following description, for illustrative purposes, some example embodiments are described in which device 130 operates as a UE and RAN device 140 operates as a base station or gNB. However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other device, and the operations described in connection with the network device can be implemented at the terminal device or other device.

[0037] In some example embodiments, the transmission direction from RAN device 140 to device 130 is referred to as the downlink (DL), and the transmission direction from device 130 to RAN device 140 is referred to as the uplink (UL). In the DL, RAN device 140 is a transmit (TX) device (or transmitter), and device 130 is a receive (RX) device (or receiver). In the UL, device 130 is a TX device (or transmitter), and RAN device 140 is an RX device (or receiver).

[0038] Communication in communication environment 100 may be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols, wireless local network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication may utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0039] The impact of Open Functions (AF) on traffic routing has already been discussed in 5G NR. AF can influence user plane traffic routing decisions by interacting with other core network entities, such as Policy Control Functions (PCF) and Session Management Functions (SMF). A key effect of AF is optimizing traffic paths to meet specific network requirements, including low latency, high bandwidth, or Service Function Specific Chains (SFCs). AF exchanges information with PCFs or Network Open Functions (NEFs).

[0040] The impact of AFs on SFCs has been discussed. AFs can send requests to the PCF via the NEF to influence the path of user plane traffic through the SFC. These requests can specify how traffic should be routed using predefined functions. The impact on the SFC can enable the application layer to improve user experience and network resource utilization. Flexible traffic control and optimization can be achieved by using AFs and other core network entities, such as the NEF and PCF.

[0041] Network slices can correspond to logical networks that are part of the physical network. Network slices can be configured and managed independently to meet the requirements of different users or applications. Support for network slice usage control has been discussed. Usage control can be implemented through the configuration of network control slice usage policies configured in the UE. Alternatively, usage control can be implemented through the configuration of Packet Data Unit (PDU) session inactivity timers and network slice deregistration inactivity timers. Individual Network Slice Selection Assistance Information (S-NSSAI) can be used by the UE to indicate to the network the slices it requires during registration with the network or initiation of a PDU session. The network can then select appropriate network slices based on the S-NSSAI provided by the UE and allocate corresponding resources on the slices.

[0042] If the S-NSSAI is dedicated to a single AF, and if the operator policy authorizes the provision of deregistration inactivity timer values ​​and / or PDU session inactivity timer values ​​for the S-NSSAI, the AF can use an external parameter provisioning process to provide the deregistration inactivity timer values ​​and PDU session inactivity timer values. In this case, the timer values ​​provided by the AF can be stored in the Unified Data Management Function (UDM) and provided to the AMF and / or SMF as part of the subscription data for the corresponding S-NSSAI. If no AF is authorized to provide deregistration inactivity timer values ​​and / or PDU session inactivity timer values ​​for the S-NSSAI (i.e., no timer values ​​are received from the UDM), the slice deregistration inactivity timer values ​​and PDU session inactivity timer values ​​can be pre-configured in the AMF and / or SMF, or received by the AMF and / or SMF respectively during the Access and Mobility Management (AM) policy association and / or session policy association processes.

[0043] Currently, there are two different use cases for S-NSSAI in 5G NR. In the first use case, the AF may have agreed with the operator to use different network slices and S-NSSAIs at different locations within the Public Land Mobile Network (PLMN) based on a Service Level Agreement (SLA). For example, the first S-NSSAI could correspond to the first Tracking Area (TA) and the second TA, and the second S-NSSAI could correspond to the third TA and the fourth TA. As another example, a larger company may have multiple subsidiaries in different locations, and each subsidiary can be managed independently in its respective location. Each subsidiary can have an independent AF in its respective location; for example, the first subsidiary in the first location could have a first sub-AF, the second subsidiary in the second location could have a second sub-AF, and so on. All sub-AFs of a subsidiary can be controlled by the company's main AF. In the second use case, the AF may have agreed with the operator to use the same network slice and S-NSSAI at different but non-adjacent locations based on an SLA.

[0044] In the above scenario, the same S-NSSAI may be unavailable during UE mobility. Therefore, a method is needed to address this issue regarding AF's impact on S-NSSAI and network slicing.

[0045] According to some example embodiments of this disclosure, a solution for AF (Application Service) influencing network slice selection is provided. In the solution provided in this disclosure, a first network entity receives device configuration information from a second network entity. This configuration information includes at least one Application Region Reference Identifier (ID) associated with an application service region for the device. The first network entity determines information about the application service region corresponding to the at least one application region reference ID based on the relationship between the application service region and the application region reference ID. The first network entity then transmits the information about the application service region to the device. The first network entity may implement or include AMF (Application Service Function), and the second network entity may implement or include AF.

[0046] Using the solution presented in this paper, AF can influence a device's S-NSSAI, network slice selection, and application service area when the same S-NSSAI is unavailable to the device. In cases where AF is untrusted, the application area reference ID can be used to hide network details from external entities.

[0047] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0048] Figure 2 Signaling flow 200 illustrating the process by which an application service area (AF) affects an application service area according to some example embodiments of this disclosure is shown. For discussion purposes, reference will be made to... Figure 1 To describe Figure 2 For example, by using Figure 1 The first network entity 110, the second network entity 120, and the device 130.

[0049] In signaling flow 200, as part of the SLA, the second network entity 120 may, together with the operator, determine (202) at least one application area reference ID that identifies at least one area. The application area reference ID may indicate an application service area applicable to a network slice and may be negotiated between the operator and the second network entity 120.

[0050] For example, the second network entity 120 may negotiate with the operator and agree on network slicing support in different regions. Regions may be geographical areas, for example, regions may be divided by regional postal code or regional name. Additionally, the second network entity 120 may also identify other potential regions with the operator for future network slicing support.

[0051] An application area reference ID (TAI) can indicate or identify an application service area. Depending on the specific network slice, an application service area can be the entire PLMN, one or more cells, or one or more tracking areas (TAs). By associating an area with a corresponding cell ID or TAI, the area can be mapped to the corresponding cell or TA that is a network topology region. For example, a first area can be mapped to a first cell ID, a second area can be mapped to a second cell ID, and a third area can be mapped to a third cell ID and a fourth cell ID. In another example, a first area can be mapped to a first TAI, a second area can be mapped to a second TAI, and a third area can be mapped to a third TAI and a fourth cell TAI.

[0052] These application area reference IDs can be associated with regions and corresponding cell IDs. For example, a first application area reference ID can be associated with a first region having a first cell ID and a second region having a second cell ID, and a second application area reference ID can be associated with a third region having a third cell ID and a fourth cell ID. The association between the application area reference IDs and cells can then be configured by the operator for the RAN equipment. The association can then be reported by the RAN equipment to the first network entity during NG establishment. See below for further details. Figure 3 Describe an example of determining the application region reference ID.

[0053] By using the application reference ID, network details can be hidden from external entities if the first network entity is untrusted. The security of communications within the network can be ensured by using the application reference ID provided in this disclosure.

[0054] Based on the determined application region reference ID, the second network entity 120 determines (204) configuration information for the device 130. The configuration information includes at least one application reference ID for the application region reference ID. For example, the second network entity 120 may request an update for regions supporting slices. The second network entity 120 may add slice support to regions mapped to the corresponding application region reference ID. For example, the second network entity 120 may request the addition of a second application region reference ID.

[0055] The second network entity 120 may determine configuration information based on service deployment in the area where the device 130 is located. In some example embodiments, the second network entity 120 may determine whether to update the configuration in response to the mobility of the device 130.

[0056] In some example embodiments, the configuration information may also include at least one of the service durations for S-NSSAI or application service areas for at least one network slice.

[0057] For example, the first network entity 110 can provide the device 130 with more information to select network slices, such as the S-NSSAI for at least one corresponding network slice and the service duration of the service on that network slice. The device 130 can use the S-NSSAI to request the network to obtain service on the corresponding network slice for the service duration. Additionally, the first network entity 110 can configure more information in the configuration information, such as partially allowed S-NSSAI and network slice replacement information.

[0058] Using the determined configuration information, the second network entity 120 can initiate an update to the network slicing service, for example, by adding slicing support to the application service region. Furthermore, the second network entity 120 can stop providing slicing services in some regions by removing the corresponding application region reference ID from the updated configuration information.

[0059] Then, the second network entity 120 transmits (206) configuration information to the first network entity 110 via at least one third network entity (not shown). The configuration information includes at least one application area reference ID associated with the application service area of ​​device 130. Accordingly, the first network entity 110 receives (208) configuration information from the second network entity 120 via at least one third network entity (not shown).

[0060] For example, the second network entity 120 can transmit configuration information including a second application region reference ID to add slice support in the region corresponding to the second application region reference ID. The configuration information can be transmitted to the first network entity 110 in the SFC.

[0061] In some example embodiments, at least one third network entity may include a network entity implementing UDM. In such an example embodiment, the second network entity 120 may transmit configuration information to a network entity implementing NEF. The network entity implementing NEF may then transmit configuration information to the first network entity 110 via the third network entity implementing UDM. References below Figure 4 Examples describing such example embodiments.

[0062] Alternatively, in some example embodiments, at least one third network entity may include a network entity implementing PCF. In such an example embodiment, the second network entity 120 may transmit configuration information to the network entity implementing NEF, and then the network entity implementing NEF may transmit the configuration information to the third network entity via the network entity implementing the User Data Repository (UDR). See below for reference. Figure 5 and Figure 7 Examples describing such example embodiments.

[0063] Alternatively, in some example embodiments, at least one third network entity may include a network entity implementing PCF. In such an example embodiment, the second network entity 120 may transmit configuration information to the third network entity. The third network entity may then transmit the configuration information to the first network entity 110. See below for further details. Figure 6 Examples describing such example embodiments.

[0064] After receiving configuration information from the second network entity 120, the first network entity 110 determines (212) information about the application service area corresponding to at least one application service area reference ID based on the relationship between the application service area and the application area reference ID.

[0065] For example, the first network entity 110 may receive at least one application region reference ID in configuration information from the second network entity 120. The at least one application region reference ID may be associated with an application service region on which the device 130 performs communication. Since the device 130 may not be aware of the application region reference ID, the first network entity 110 may have to convert the at least one application region reference ID into information about the application service region so that the device 130 can use this information to perform communication on the corresponding network slice. For example, the first network entity 110 may map the at least one application region reference ID to an application service region based on the relationship between the application region reference ID and the application service region.

[0066] In some example embodiments, the first network entity 110 may receive the relationship from the RAN device. The first network entity 110 may then determine information about the application service area corresponding to at least one application service area reference ID based on the relationship. In some example embodiments, the RAN device may be a gNB or be included in a gNB.

[0067] For example, the RAN device can indicate the mapping between an application area reference ID and an application service area to the first network entity. The mapping and the application area reference ID can be determined by the second network entity 120 and the operator and transmitted to the RAN device associated with the application service area. Alternatively, the mapping between the application area reference ID and the application service area can be pre-configured before negotiation between the second network entity 120 and the operator, and this mapping can be indicated to the first network entity 110. For example, an application area reference ID can be pre-configured for each city.

[0068] In some example embodiments, the first network entity 110 may receive relationships from the RAN device via a setup request message or a RAN configuration update message.

[0069] For example, the RAN device may indicate the mapping to the first network entity 110 during the NG establishment request process, so that the first network entity 110 can know which application area reference ID can involve which RAN device. Alternatively, the RAN device may indicate the mapping to the first network entity 110 via a RAN configuration update message.

[0070] Using the solution provided in this paper, the first network entity 110 can convert the application region reference ID into information about the application service region. Therefore, network details can be hidden from external entities, and communication within the network can be protected.

[0071] Based on the determination of this information, the first network entity 110 transmits (214) information about the application service area to the device 130. Accordingly, the device 130 receives (216) information from the first network entity 110.

[0072] In some example embodiments where the third network entity includes a network entity implementing UDM, the first network entity 110 may transmit information to the device 130 via a configuration message. In such example embodiments, the configuration message may be a Non-Access Stratum (NAS) configuration update message.

[0073] In some example embodiments where the third network entity includes a network entity implementing PCF, the first network entity 110 may transmit this information to device 130 via a policy modification message. In such example embodiments, the policy modification message may indicate a modification to the AM policy or routing policy of device 130.

[0074] Based on the information received from the first network entity 110, the device 130 performs (218) communication on the application service area based on the information.

[0075] Additionally, in some example embodiments, the first network entity 110 may transmit configuration information to the device 130 in association with information about the application service area. For example, the first network entity 110 may also provide an S-NSSAI for at least one network slice and a service duration for the corresponding application service area. The device 130 may use the S-NSSAI to request the network to communicate on the corresponding network slice during the service duration.

[0076] In some example embodiments, information about the application service area can indicate at least one cell or tracking area. The device 130 can perform communication on the cell or tracking area indicated by the information, based on configuration information.

[0077] For example, information about the application service area indicated to device 130 may indicate the cells or tracking areas that device 130 can connect to. Device 130 may connect to RAN equipment that provides these cells or tracking areas indicated by the information. For example, the information may indicate the at least one cell or tracking area by at least one cell ID or tracking area ID (TAI).

[0078] Using the solution provided in this disclosure, communication is performed in the indicated application service area by connecting to the corresponding RAN device that provides the application service area, and the network slice service is used based on S-NSSAI and service duration.

[0079] In signaling flow 200, first network entity 110 may implement or include AMF, second network entity 120 may implement or include AF, and device 130 may include or be included in terminal equipment.

[0080] As briefly mentioned above, in some example embodiments, the second network entity 120 may determine at least one application area reference ID with the operator and may indicate that at least one application area reference ID to the first network entity 110. Now refer to Figure 3 Example description.

[0081] Figure 3 Signaling stream 300 illustrates an example process for determining and transmitting at least one application region reference ID according to some example embodiments of this disclosure. Figure 3 This involves AF 310, carrier equipment 320, RAN equipment 330, and AMF 340. AF 310 can be considered as... Figure 2 An example of the first network entity 110 may be included in the second network entity. Carrier equipment 320 can be considered... Figure 1 Example of operator equipment 150. RAN equipment 330 can be considered as... Figure 1 Example of RAN device 140. AMF 340 can be considered as Figure 2 An example of the second network entity 120 may be included in the second network entity.

[0082] In signaling flow 300, at point 301, as part of the SLA, AF 310 and Carrier 210 can determine the Application Area Reference ID. It should be noted that a trusted AF can know network details and can directly provide application services by cell ID or TAI. Only in the case of an untrusted AF can the Application Area Reference ID be used to hide network details from external entities.

[0083] Then at 303, operator equipment 320 can transmit configuration to RAN equipment 330. This configuration may include at least one of the following: an application area reference ID, or an S-NSSAI for at least one network slice, and an application service area corresponding to the application area reference ID. The application service area can be provided to the RAN equipment based on a list of cell IDs or TAIs.

[0084] At 305, RAN device 330 may transmit an establishment request to AMF 340. The establishment request may include an application area reference ID. Accordingly, at 307, AMF 340 may transmit an establishment response to RAN device 330. In some example embodiments, the establishment request may be an NG establishment request, and the establishment response may be an NG establishment response.

[0085] As briefly mentioned above, in some example embodiments, at least one third network entity may include a network entity implementing UDM, and the second network entity 120 may transmit configuration information to a network entity implementing NEF. Now refer to Figure 4 Example description.

[0086] Figure 4 Signaling stream 400 illustrates an example process for transmitting at least one application area reference ID according to some example embodiments of this disclosure. Figure 4 This involves AF 410, NEF 420, UDM 430, UDR 440, AMF 450, and UE 460. AF 410 can be considered as... Figure 1 An example of the first network entity 110 may be included in the first network entity 110. AMF 450 can be considered as... Figure 1 An example of the second network entity 120 may be included in the second network entity 120. UE 460 can be considered as Figure 1 Example of device 130. AMF 450 may be an AMF serving UE 460.

[0087] Signaling flow 400 involves the parameter supply process of AF 410. AF 410 can provide new parameters and transmit them to AMF 450 via the process in signaling flow 400 to trigger an update to UE 460.

[0088] In signaling flow 400, at point 401, AMF 450 can send a Nudm_SDM_Subscribe request to UDM 430. Then, at point 403, AF 410 can subscribe to a network entity (not shown) that implements network data analysis functionality via NEF 420. AF 410 can then receive UE mobility analysis and / or UE communication analysis from the network entity (not shown) that implements network data analysis functionality. At point 405, AF 410 and NEF 420 can verify the received data and derive expected UE behavior parameters.

[0089] At 407, AF 410 can initiate an update to the application area reference ID and transmit an Nnef_ParameterProvision_Create / Update / Delete request to NEF 420. At 409, NEF 420 can transmit a Nudm_ParameterProvision_Create / Update / Delete request to UDM 430. The request may include at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration.

[0090] Then at 411, UDM 430 can transmit Nudr_DM_Query to UDR 440. Correspondingly, UDR 440 can transmit a Nudr_DM_Query response to UDM 430. At 413, UDM 430 can transmit Nudr_DM_Update to UDR 440. The Nudr_DM_Update message may include at least one of the following: application area reference ID, S-NSSAI of at least one network slice, or service duration. Correspondingly, UDR 440 can respond to UDM 430 with a Nudr_DM_Update response.

[0091] At 415, UDM 430 can transmit Nudm_ParameterProvision_Create / Update / Delete responses to NEF 420. At 417, NEF 420 can transmit Nnef_ParameterProvision_Create / Update / Delete responses to AF 410.

[0092] At position 419, UDM 430 can transmit a Nudm_SDM_Notification to AMF 450. This notification may include at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration.

[0093] Based on the mapping received from the RAN equipment providing the application service area, AMF 450 can determine information about the application service area corresponding to the application area reference ID. At 421, AMF 450 can transmit a UE configuration update message to the UE. The UE configuration update message may include information about at least one of the following: the application service area, the S-NSSAI for at least one network slice, or the service duration. Additionally, the UE configuration update message may also include at least one of the following: updated allowed S-NSSAI, partially allowed S-NSSAI, and slice replacement information.

[0094] As briefly mentioned above, in some example embodiments, the third network entity may be a network entity implementing PCF, and the second network entity 120 may transmit configuration information to the network entity implementing NEF. Now refer to Figure 5 Example description.

[0095] Figure 5 Signaling flow 500 is shown as an example process for sending at least one application area reference ID according to some example embodiments of this disclosure. Figure 5 This involves UE 510, AMF 520, PCF 530 for UE 510, the network entity implementing Bootstrap Server (BSF) function 540, PCF 550 for terminal PDU sessions, UDR 560, NEF 570, and AF 580. AF 580 can be considered as... Figure 1 An example of the second network entity 120 may be included in the second network entity 120. AMF 520 can be considered as... Figure 1 An example of the first network entity 110 or included in the first network entity 110. UE 510 can be considered as Figure 1 Example of device 130. AMF 520 may be an AMF serving UE 510.

[0096] Signaling flow 500 involves the process by which AF 580 affects AM policy. AF 580 can provide new parameters and transmit them to AMF 520 via the process in signaling flow 500 to trigger an update to UE 510.

[0097] At 501, AMF 520, PCF 530 of terminal UE 510, and BSF 540 can perform AM policy association establishment. Then at 503, PCF 530 can transmit Nudr_DM_Subscribe to UDR 560. At 505, AF 580 can transmit an Nnef_AMInfluence_Create / Update / Delete request to NEF 570. At 507, NEF 570 can transmit a Nudr_DM_Create / Update / Delete request to UDR 560. These requests may include at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration. Accordingly, at 509, UDR 560 can transmit a Nudr_DM_Create / Update / Delete response to NEF 570. Then at 511, NEF 570 can transmit an Nnef_AMInfluence_Create / Update / Delete response to AF 580.

[0098] At position 513, the UDR 560 can transmit Nudr_DM_Notify to the PCF530. The Nudr_DM_Notify message may include at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration.

[0099] At 515, PCF530, BSF 540, and PCF 550 can perform either the first or second procedure as follows.

[0100] For example, the first process may include the following steps: PCF 530 can subscribe to BSF 540 and provide binding information to AMF 520. Then, the PCF for the UE can determine AM policy information and subscribe to BSF 540. SMF can establish AM policy association and register with BSF 540. BSF 540 can call Nbsf_Management_Notify to notify PCF 550 of registration in BSF 540. Then, PCF 550 sends a notification to PCF 530. PCF 530 can subscribe to the start / stop of application traffic and transmit a request to PCF 550. PCF 550 can generate Policy and Charging Control (PCC) rules. Then, PCF 530 can install PCC rules and Policy Control Request Triggers to detect "Start / Stop of Application Service" in SMF. SMF detects that the Policy Control Request Trigger is met and reports the start / stop of application traffic to the PCF serving the PDU session. Then, the start / stop of application traffic can be notified to PCF 530. The PCF 550 can provide multiple notifications to the PCF 530. The PCF checks the operator's policies and can then modify AM policy information based on reports of application traffic start / stop.

[0101] For another example, the second process may include the following steps: PCF 530 may subscribe to BSF 540 or provide PCF binding information to AMF 520. PCF 530 may determine AM policy information and call Nbsf_Management_Subscribe to subscribe to BSF 540 to receive notifications in BSF 540. SMF may establish an AM policy association and register with BSF 540. BSF 540 may call Nbsf_Management_Notify to notify PCF of the PDU sessions to be registered.

[0102] Then at 517, AMF 520 and PCF 530 can perform the AM policy association modification procedure. During the AM policy association modification procedure, PCF 530 can transmit the Application Area Reference ID, S-NSSAI, and service duration for at least one network slice to AMF 520. At 519, AMF 520 can transmit an AM policy modification message to UE 510. The AM policy modification message may include at least one of the Application Area Reference ID, S-NSSAI, and service duration for at least one network slice.

[0103] As briefly mentioned above, in some example embodiments, at least one third network entity may include a network entity implementing PCF, and the second network entity 120 may transmit configuration information to the third network entity. Now refer to Figure 6 Example description.

[0104] Figure 6 Signaling stream 600 illustrates an example process for sending at least one application area reference ID according to some example embodiments of this disclosure. Figure 6 This involves UE 610, AMF 620, PCF 630, BSF 640, and AF 650. AF 650 can be considered as... Figure 1 An example of the second network entity 120 is included in the second network entity 120. AMF 620 can be considered as... Figure 1 An example of the first network entity 110 or included in the first network entity 110. UE 610 can be considered as Figure 1 Example of device 130. AMF 620 may be an AMF serving UE 610.

[0105] Signaling flow 600 involves the process by which AF 650 affects AM policy. AF 650 can provide new parameters and transmit them to AMF 620 via the process in signaling flow 600 to trigger an update to UE 610.

[0106] exist Figure 6 In an example embodiment, AF 650 can, for example, identify a specific UE 610 based on its IP address. AF 650 can then initiate an update to the application area reference ID and application service area for that specific UE 610.

[0107] At point 601, AMF 620, PCF 630, and BSF 640 can perform AM policy association establishment as described above at point 501. Then at point 603, AF 650 can transmit Nbsf_Management_Subscribe to BSF 640. Correspondingly, at point 605, BSF 640 can transmit Nbsf_Management_Notify to AF 650.

[0108] At 607, AF 650 may send an Npcf_AMPolicyAuthorization request to PCF 630, which may include at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration. At 609, PCF 630 may correspondingly transmit an Npcf_AMPolicyAuthorization response to AF 650.

[0109] At point 611, AMF 620 and PCF 630 can perform an AM policy association modification procedure. During the AM policy association modification procedure, PCF 630 can transmit the Application Area Reference ID, S-NSSAI, and Service Duration for at least one network slice to AMF 620. Then at point 613, AMF 620 can transmit an AM policy modification message to UE 610. The AM policy modification message may include at least one of the following: Application Area Reference ID, S-NSSAI for at least one network slice, or Service Duration.

[0110] As briefly mentioned above, in some example embodiments, at least one third network entity may include a network entity implementing PCF, and the second network entity 120 may transmit configuration information to the network entity implementing NEF. Now refer to Figure 7 Example description.

[0111] Figure 7 Signaling stream 700 is shown as an example process for transmitting at least one application area reference ID according to some example embodiments of the present disclosure. Figure 7 This involves UE 710, RAN equipment 720, AMF 730, PCF 740, UDM 750, UDR 760, NEF770, and AF 780. AF 780 can be considered as... Figure 1 An example of the second network entity 120 may be included in the second network entity 120. The AMF 730 can be considered as... Figure 1 An example of the first network entity 110 or included in the first network entity 110. UE 710 can be considered as Figure 1 Example of device 130. AMF 730 may be an AMF serving UE 710.

[0112] Signaling flow 700 involves the process of AF 780 affecting AM policy. AF 780 can provide new parameters and transmit them to AMF 720 via the process in signaling flow 600 to trigger an update to UE 6610.

[0113] First, UE 710, RAN device 720, AMF 730, PCF 740, UDM 750, and UDR 760 can perform the UE registration procedure. At 701, AMF 730 and PCF 740 can perform the policy association procedure. At 703, PCF 740 can transmit the Nudr_DM_Subscribe message to UDR 760.

[0114] At 705, AF 780 can create an AF request, which includes at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration. Then at 707, AF 780 can transmit an Nnef_ServiceParameter_Create / Update / Delete request to NEF 770. This request can include at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration. At 709, UDM 750 and NEF 770 can exchange Nudm_SDM_Get messages.

[0115] Then, at 711, UDM 750, UDR 760, and NEF 770 can perform the authorization process for service-specific parameters. Then, at 713, NEF 770 can store, update, or remove information in UDR 760 regarding the application area reference ID, S-NSSAI, and service duration of at least one network slice. Subsequently, at 715, NEF can transmit the Nnef_ServiceParameter_Create / Update / Delete response to AF 780.

[0116] At 717, UDR 760 can provide AMF 730 with information about the application area reference ID, S-NSSAI, and service duration for at least one network slice via a Nudr_DM_Notify message. At 719, UE 710, RAN device 720, AMF 730, and PCF 740 can perform a UE policy delivery procedure. During the UE policy delivery procedure, PCF can determine updates to the UE routing policy rules and transmit them to AMF 730. AMF 730 can then transmit an AM policy modification message to UE 710. The AM policy modification message may include at least one of the application area reference ID, S-NSSAI for at least one network slice, or service duration.

[0117] At 721, AMF 730 can transmit Npcf_EventExposure_Notify to NEF 770. At 723, NEF 770 can transmit Nnef_ServiceParameter_Notify to AF 780 as a response to action 707.

[0118] According to some example embodiments of this disclosure, a solution for AF (Application Functionality) influencing network slice selection is provided. In the solution provided in this disclosure, the apparatus may receive an Application Region Reference ID associated with an Application Service Region (ASPR) of the apparatus. The apparatus determines that the service duration of the ASPR is to be updated and transmits a request to update the service duration to a second network entity. The apparatus then receives information including the updated service duration of the ASPR.

[0119] The solution presented in this paper enables devices to request network updates to service durations based on device requirements by using an Application Region Reference ID (APRI) corresponding to the Application Service Region. AF can influence a device's S-NSSAI, network slice selection, and Application Service Region when the same S-NSSAI is not applicable. In cases where AF is untrusted, the APRI can be used to hide network details from external entities.

[0120] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0121] Figure 8 Signaling flow 800 illustrating the process by which an application service area (AF) affects an application service area according to some example embodiments of this disclosure is shown. For discussion purposes, reference will be made to... Figure 1 To describe Figure 8 For example, by using Figure 1 The first network entity 110, the second network entity 120, the device 130, and the RAN equipment 140 are included.

[0122] In signaling flow 800, the second network entity 120 may first determine (802) at least one application area reference identifier (ID) identifying at least one area as part of the SLA, in conjunction with operator equipment (not shown). It should be understood that this can be done with... Figure 2 The application area reference ID (802) is determined in a similar manner to the determination of (202) in the previous section, therefore the relevant description is omitted here. The operator equipment can transmit at least one application area reference ID to the RAN equipment 140, as described above. Figure 3 Described.

[0123] RAN device 140 receives (804) at least one application area reference ID that identifies at least one application service area of ​​the RAN device.

[0124] Then, RAN device 140 transmits (806) an application reference ID associated with the application serving area of ​​device 130 to device 130. Accordingly, device 130 receives (808) an application area reference ID from RAN device 140. In some example embodiments, RAN device 140 may provide a serving cell or tracking area for the device, and the application area reference ID received from RAN device 140 may correspond to a serving cell or tracking area. In some example embodiments, the application area reference ID is transmitted to device 130 via a System Information Block (SIB).

[0125] For example, RAN device 140 can broadcast at least one application area reference ID to all devices served by RAN device 140 using SIB. RAN device 140 can broadcast the application area reference ID to each serving cell provided by RAN device 140, and devices in the serving cell can receive the application area reference ID and know that the application area reference ID corresponds to the cell to which it is located. In other words, device 130 can know the corresponding application area reference ID of its serving cell.

[0126] Knowing the corresponding application region reference ID for the application service region, device 130 can initiate a request to update the service duration of the application based on its own needs. Device 130 can transmit the request with the application region reference ID to the first network entity 110, which can understand which application service region needs to be updated.

[0127] Device 130 determines (812) to update the service duration of the application service area. For example, if device 130 needs more time to perform communication with applications provided on the application service area, device 130 may determine to extend the service duration of the application service area. Alternatively, if device 130 needs to stop the service on the application service area, it may transmit a request to reduce or terminate the service duration of the application service area.

[0128] Based on this determination, device 130 transmits (814) a request to update the service duration of the application service area. This request includes an application area reference ID corresponding to the application service area. Accordingly, second network entity 120 receives (816) the request from device 130. See below. Figure 9 The architecture in which device 130 is able to transmit requests to second network entity 120 is described.

[0129] For example, device 130 may want to adjust the service duration of the serving cell based on its own needs. Since the second network entity 120 may not know network details such as the cell ID and corresponding network slice, device 130 may need to notify the second network entity 120 of the application area reference ID associated with the serving cell. Device 130 may have already received the application area reference ID corresponding to the serving cell from RAN device 140. Therefore, device 130 can transmit a request to update the service duration in association with the corresponding application area reference ID.

[0130] After receiving a request from device 130, second network entity 120 determines configuration information (818) for updating the service duration of an application service region based on the application area reference ID. For example, device 130 may request to update the service duration of its serving cell, and this request may include the application area reference ID corresponding to the serving cell. Second network entity 120 can understand which application service region corresponds to the application area reference ID received from device 130. Then, second network entity 120 can determine the configuration information for updating the service duration.

[0131] Based on this determination, the second network entity 120 transmits (822) configuration information for updating the service duration of the application service area to the first network entity 110 via at least one third network entity (not shown). The configuration information includes an application area reference ID associated with the application service area. Accordingly, the first network entity 110 receives (824) configuration information from the second network entity 120 via at least one third network entity (not shown). Additionally, the configuration information may also include an S-NSSAI corresponding to the application service area. For example, if the application area reference ID is not unique, the S-NSSAI corresponding to the application service area may be provided by device 130 upon request. The second network entity 120 may determine the corresponding application service area and network slice with the help of the S-NSSAI.

[0132] In some example embodiments, at least one third network entity may include a network entity implementing PCF, and the second network entity 120 may transmit configuration information to the third network entity. In such an example embodiment, the third network entity may transmit configuration information to the first network entity 110. References below... Figure 10 Examples describing such example embodiments.

[0133] Alternatively, in some example embodiments, at least one third network entity may include a network entity implementing PCF, and the second network entity 120 may transmit configuration information to the network entity implementing NEF. In such example embodiments, the network entity implementing NEF may transmit configuration information to the third network entity via a network entity implementing a User Data Repository (UDR). References below... Figure 11 Examples describing such example embodiments.

[0134] Based on the configuration information received from the second network entity 120, the first network entity 110 determines (826) the updated service duration. For example, the first network entity 110 may determine the updated service duration for an application service region corresponding to an application region reference ID based on the received configuration information. The configuration information may include the application region reference ID for which the device 130 requests an update to its service duration. The first network entity 110 may convert the application region reference ID into the corresponding application service region. Then, the first network entity 110 may have information about the application service regions for which the device 130 may need to update its service duration.

[0135] In some example embodiments, the first network entity 110 may determine the application service area corresponding to the application area reference identifier based on the relationship between the application area reference identifier and the application service area. This relationship may be received from the RAN device 140 via an establishment request. In some example embodiments, the RAN device 140 receives the relationship between the application area reference identifier and the application service area from the operator.

[0136] After determining the updated service duration, the first network entity 110 transmits (828) information including the updated service duration to the device 130. Accordingly, the device 130 receives (832) information from the first network entity 110. Additionally, the information may also include S-NSSAI for at least one network slice.

[0137] In some example embodiments, apparatus 130 may perform communication over an application service area based on an updated service duration. For example, apparatus 130 may receive an updated service duration for an on-demand network slice based on information received from a first network entity 110.

[0138] In some example embodiments where the third network entity includes a network entity implementing PCF, the first network entity 110 may transmit information to the device 130 via a policy modification message. In such example embodiments, the policy modification message may indicate a modification to the AM policy or routing policy for the device 130. Alternatively, in some example embodiments, the first network entity 110 may transmit information to the device 130 via a NAS configuration update message.

[0139] Figure 9 A schematic diagram of an example architecture that can implement the solutions provided in this disclosure is shown. Figure 9 As shown, UE 910 may include at least one Vertical Application Layer (VAL) client 911. UE 910 may communicate with VAL server 930 via VAL-Uu interface 920 to indicate a request for updating the service duration of the application service area. For example, UE 910 may use VAL client 911 to initiate a request for updating the service duration by using the application area reference ID and the corresponding S-NSSAI. Then, the AF may use the reference below... Figure 10 and Figure 11 The described process is to transmit updated service durations to UE 910. The notification management client 912 can receive notifications from VAL server 920 and transmit them to VAL client 910.

[0140] As briefly mentioned above, in some example embodiments, at least one third network entity may include a network entity implementing PCF, and the second network entity 120 may transmit configuration information to the third network entity. Now refer to Figure 10 Example description.

[0141] Figure 10 Signaling stream 1000 illustrates an example process for transmitting at least one application area reference ID according to some example embodiments of this disclosure. Figure 10 This involves UE 1010, AMF 1020, PCF 1030, BSF 1040, AF 1050, and RAN equipment 1060. AF 1050 can be considered as... Figure 1 An example of the second network entity 120 or included in the second network entity 120. AMF 1020 can be considered as Figure 1 An example of the first network entity 110 or included in the first network entity 110. UE 1010 can be considered as Figure 1 Example of device 130. AMF 1020 may be an AMF serving UE 1010. RAN device 1060 may be considered as Figure 1 Example of RAN device 140. RAN device 1060 can serve UE 1010.

[0142] Signaling flow 1000 involves the process of AF 1050 affecting AM policy. AF 1050 can transmit updated service duration to UE 1010's AMF 1020 via the process in signaling flow 1000.

[0143] In signaling flow 1000, at point 1001, RAN device 1060 transmits an application area reference ID to UE 1010. For example, RAN device 1060 may broadcast at least one application area reference ID to all devices served by RAN device 1060. UE 1010 may receive the application area reference ID corresponding to its serving cell. Therefore, UE 1010 may use the application area reference ID to initiate a request to AF 1050.

[0144] At 1003, UE 1010 determines that it needs to update the service duration of its application service area. For example, UE 1010 may want to extend the service duration of its application service area. Then at 1005, UE 1010 transmits a request to AF 1050 to update the service duration. This request includes the application area reference ID corresponding to the application service area of ​​UE 1010.

[0145] Processes 1007 to 1017 are similar Figure 6 The process is described in steps 601 to 611. At 1007, AMF 1020, PCF 1030, and BSF 1040 can perform AM policy association establishment as described above at 501. Then at 1009, AF 1050 can transmit Nbsf_Management_Subscribe to BSF 1040. Correspondingly, at 1011, BSF 1040 can transmit Nbsf_Management_Notify to AF 1050.

[0146] At 1013, AF 1050 can transmit an Npcf_AMPolicyAuthorization request to PCF 61030, which may include at least one of the following: application area reference ID, S-NSSAI for at least one network slice, or service duration. At 1015, PCF 1030 can correspondingly transmit an Npcf_AMPolicyAuthorization response to AF 1050.

[0147] At point 1017, AMF 1020 and PCF 1030 can perform the AM policy association modification process. During the AM policy association modification process, PCF 1030 can transmit the application area reference ID, S-NSSAI, and service duration for at least one network slice to AMF 1020.

[0148] At position 1019, AMF 1020 transmits an AM policy modification message to UE 1010. The AM policy modification message may include the updated service duration for the applied service area.

[0149] As briefly mentioned above, in some example embodiments, at least one third network entity may include a network entity implementing PCF, and the second network entity 120 may transmit configuration information to the network entity implementing NEF. Now refer to Figure 11 Example description.

[0150] Figure 11 Signaling stream 1100 illustrates an example process for transmitting at least one application area reference ID according to some example embodiments of this disclosure. Figure 11 This involves UE 1110, RAN equipment 1120, AMF 1130, PCF 1140, UDM 1150, UDR 1160, NEF 1170, and AF 1180. AF 1180 can be considered as... Figure 1 An example of the second network entity 120 or included in the second network entity 120. AMF 1130 can be considered as Figure 1 An example of the first network entity 110 or included in the first network entity 110. UE 1110 can be considered as Figure 1 Example of device 130. AMF 1130 may be an AMF serving UE 1110.

[0151] Signaling flow 1100 involves the process of AF 1180 affecting AM policy. AF 1180 can transmit updated service duration to UE 1110's AMF 1130 via the process in signaling flow 1100.

[0152] In signaling flow 1100, procedures 1101 to 1105 are similar to Figure 10 Processes 1001 to 1005 and 1107 to 1123 are similar to... Figure 7 Procedures 701 to 719 are described. At 1101, RAN device 1160 transmits an application area reference ID to UE 1110. For example, RAN device 1160 may broadcast at least one application area reference ID to all devices served by RAN device 1160. UE 1110 may receive the application area reference ID corresponding to its serving cell. Therefore, UE 1110 may use the application area reference ID to initiate a request to AF 1150.

[0153] At 1103, UE 1110 determines that it needs to update the service duration of its application service area. For example, UE 1110 may want to extend the service duration of its application service area. Then at 1105, UE 1110 transmits a request to AF 1150 to update the service duration. This request includes the application area reference ID corresponding to the application service area of ​​UE 1110.

[0154] At 1107, AMF 1130 and PCF 1140 can perform the policy association procedure. At 1109, PCF 1140 can transmit the Nudr_DM_Subscribe message to UDR 1160.

[0155] At 1111, AF 1180 can create an AF request, including the application area reference ID, the S-NSSAI for at least one network slice, and the service duration. Then at 1113, AF 1180 can transmit an Nnef_ServiceParameter_Create / Update / Delete request to NEF 1170. This request can include at least one of the application area reference ID, the S-NSSAI for at least one network slice, or the service duration. At 1115, UDM 1150 and NEF 1170 can exchange Nudm_SDM_Get messages.

[0156] Then, at 1117, UDM 1150, UDR 1160, and NEF 1170 can perform the authorization process for service-specific parameters. Then, at 1119, NEF 1170 can store, update, or remove information in UDR 1160 regarding the application area reference ID, S-NSSAI, and service duration of at least one network slice. Subsequently, at 1121, NEF can transmit the Nnef_ServiceParameter_Create / Update / Delete response to AF 1180.

[0157] At 1123, UDR 1160 can provide AMF 1130 with information about the application area reference ID, S-NSSAI, and service duration of at least one network slice via the Nudr_DM_Notify message.

[0158] At 1125, UE 1110, RAN device 1120, AMF 1130, and PCF 1140 can perform a UE policy delivery procedure. During this procedure, PCF 1140 can provide AMF 1130 with the updated service duration of the application service area. AMF 1130 can then transmit the updated service duration of the application service area to UE 1110 via a policy modification message. The policy modification message can include the updated service duration of the application service area. The policy modification message can indicate modifications to the URSP of UE 1110. Actions 1129 and 1132 are related to... Figure 7 Actions 721 and 723 are the same, and their descriptions are omitted here.

[0159] Figure 12A flowchart of an example method 1200 implemented at a first network entity according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1200 is described from the perspective of the first network entity 110 in the network.

[0160] At box 1210, a first network entity 110 receives configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application area reference identifier, the at least one application area reference identifier being associated with an application service area for the device.

[0161] In box 1220, the first network entity 110 determines information about the application service region corresponding to the at least one application region reference identifier based on the relationship between the application service region and the application region reference identifier.

[0162] In frame 1230, the first network entity 110 transmits the information about the application service area to the device.

[0163] By converting at least one application service area reference identifier into a corresponding application service area, the first network entity can understand which application service area to use for communication. In this way, network details can be hidden from untrusted external entities, thereby improving network security.

[0164] In some example embodiments, the configuration information also includes at least one of the following: auxiliary information S-NSSAI for a single network slice of at least one network slice, or the service duration of the application service area. In this way, the application service area can be used only during the service duration. Therefore, the flexibility in using the application service area can be improved.

[0165] In some example embodiments, method 1200 further includes transmitting the configuration information to the device in association with the information about the application service area.

[0166] In some example embodiments, method 1200 further includes: receiving the relationship from a radio access network device; and determining, based on the relationship, the information regarding the application service area corresponding to the at least one application service area reference identifier.

[0167] In some example embodiments, the radio access network equipment includes or is included in a next-generation node B (gNB).

[0168] In some example embodiments, the relationship is received from the radio access network device via an establishment request message or a radio access network (RAN) configuration update message.

[0169] In some example embodiments, the information regarding the application service area indicates at least one cell or tracking area. In this way, the network entity can be indicated that the cell or tracking area is supported by the network slice, and the device can request the service of the network slice.

[0170] In some example embodiments, method 1200 further includes: receiving the configuration information from the third network entity, wherein the configuration information is received by the third network entity from the second network entity via a network entity implementing the Network Open Function (NEF); and transmitting the information about the application service area to the device via a Non-Access Stratum (NAS) configuration update message.

[0171] In some example embodiments, method 1200 further includes: receiving the configuration information from the third network entity, wherein the configuration information is received by the third network entity from the second network entity; and transmitting the information about the application service area to the device via a policy modification message.

[0172] In some example embodiments, method 1200 further includes: receiving the configuration information from the third network entity, wherein the configuration information is received by the third network entity from a network entity implementing a User Data Repository (UDR), wherein the configuration information is received by the network entity implementing the UDR from a network entity implementing a Network Application Function (NEF), and wherein the configuration information is received by the network entity implementing the NEF from the second network entity; and transmitting the information about the application service area to the device via a policy modification message. In this way, information about the application service area can be sent to the device in the service function chain, and signaling overhead can be saved.

[0173] In some example embodiments, the policy modification message indicates a modification to the Access and Mobility Management (AM) policy or routing policy for the device.

[0174] In some example embodiments, the first network entity implements or includes the Access and Mobility Management Function (AMF), the second network entity implements or includes the Application Function (AF), and the apparatus is included in or is included in a terminal device.

[0175] Figure 13 A flowchart of an example method 1300 implemented at a second network entity according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1300 is described from the perspective of the second network entity 120 in the network.

[0176] In box 1310, the second network entity 120 determines configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region.

[0177] At frame 1320, the second network entity 120 transmits the configuration information for the device to the first network entity via at least one third network entity.

[0178] In some example embodiments, method 1300 further includes: determining, with the operator as part of a Service Level Agreement (SLA), the at least one application area reference identifier that identifies at least one area.

[0179] In some example embodiments, the configuration information also includes at least one of the following: single network slice selection auxiliary information S-NSSAI for the at least one network slice or the duration of the application service area.

[0180] In some example embodiments, method 1300 further includes: transmitting the configuration information to a network entity implementing the Network Open Function (NEF), wherein the configuration information is transmitted from the NEF-implementing network entity to the first network entity via the third network entity.

[0181] In some example embodiments, method 1300 further includes: transmitting the configuration information to the third network entity, wherein the configuration information will be transmitted from the third network entity to the first network entity.

[0182] In some example embodiments, method 1300 further includes: transmitting the configuration information to a network entity implementing NEF, wherein the configuration information is transmitted from the network entity implementing NEF to the third network entity via a network entity implementing a User Data Repository (UDR).

[0183] Figure 14 A flowchart of an example method 1400 implemented at a device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 The angle description method of the device 130 in the middle is 1400.

[0184] At frame 1410, device 130 receives information from a first network entity, wherein the information includes information about the application service area of ​​the network slice and the service duration of the application service area.

[0185] In box 1420, device 130 performs communication on the application service area based on the information.

[0186] In some example embodiments, the information also includes: individual network slice selection assistance information S-NSSAI for at least one network slice.

[0187] In some example embodiments, method 1400 further includes: performing communication on a cell or tracking area indicated by the information about the application service area based on the information.

[0188] In some example embodiments, the information described herein is received from the first network entity via at least one of the following: a Non-Access Stratum (NAS) configuration update message or a policy modification message.

[0189] Figure 15 A flowchart of an example method 1500 implemented at a first network entity according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1500 is described from the perspective of the first network entity 110 in the network.

[0190] At box 1510, the first network entity 110 receives configuration information from the second network entity via at least one third network entity for updating the service duration of an application service area for a device, wherein the configuration information includes an application area reference identifier associated with the application service area.

[0191] In box 1520, the first network entity 110 determines the service duration of the updated application service area corresponding to the application area reference identifier based on the received configuration information.

[0192] In frame 1530, the first network entity 110 transmits information to the device, including updated service duration.

[0193] By using an application region reference identifier corresponding to an application service region, the first network entity can understand which application service region's service duration needs to be updated. In this way, network details can be hidden from untrusted external entities, thereby improving network security.

[0194] In some example embodiments, the configuration information also includes S-NSSAI corresponding to the application service region.

[0195] In some example embodiments, method 1500 further includes: determining the application service area corresponding to the application area reference identifier based on the relationship between the application area reference identifier and the application service area, wherein the relationship is received from the radio access network device via an establishment request message or a run configuration update message.

[0196] In some example embodiments, method 1500 further includes: receiving configuration information from a third network entity, wherein the information is received by the third network entity from a second network entity; and transmitting information including an updated service duration to the device via a policy modification message.

[0197] In some example embodiments, method 1500 further includes: receiving information from a third network entity, wherein the information is received by the third network entity from a second network entity via a network entity implementing a User Data Repository (UDR) and a network entity implementing a Network Open Function (NEF); and transmitting information including an updated service duration to the device via a policy modification message.

[0198] In some example embodiments, the first network entity implements or includes the Access and Mobility Management Function (AMF), the second network entity implements or includes the Application Function (AF), the apparatus includes or is included in a terminal device, and the radio access network device implements or includes a next-generation node (gNB).

[0199] Figure 16 A flowchart of an example method 1600 implemented at a second network entity according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1600 is described from the perspective of the second network entity 120 in the network.

[0200] In box 1610, the second network entity 120 receives a request from the device to update the service duration, wherein the request includes an application region reference identifier associated with the application service region.

[0201] In box 1620, the second network entity 120 determines the configuration information for updating the service duration of the application service region based on the application region reference identifier.

[0202] In box 1630, the second network entity 120 transmits configuration information for updating the service duration of the application service area to the second network entity serving the device via at least one third network entity, wherein the configuration information includes an application area reference identifier associated with the application service area.

[0203] In some example embodiments, the configuration information also includes S-NSSAI corresponding to the application service region. In this way, the application service region can be used only during the service duration. Therefore, the flexibility in using the application service region can be improved.

[0204] In some example embodiments, method 1600 further includes determining an application area reference identifier that identifies at least one region based on a Service Level Agreement (SLA) with the operator. Therefore, when the device is located in different regions, the second network entity 120 can be enabled to use different application area reference identifiers.

[0205] In some example embodiments, method 1600 further includes transmitting information for updating the service duration of the application service area to a third network entity, wherein the information will be transmitted from at least one third network entity to a second network entity.

[0206] In some example embodiments, method 1600 further includes transmitting information for updating the service duration of the application service area to a network entity implementing the network open function, wherein the information is transmitted from a network entity implementing the NEF to at least one third network entity via a network entity implementing the UDR.

[0207] Figure 17 A flowchart of an example method 1700 implemented at a device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 The angle description method of the device 130 in the middle is 1700.

[0208] In frame 1710, device 130 receives from radio access network equipment an application area reference identifier associated with the application service area of ​​the device.

[0209] In frame 1720, device 130 determines the service duration of the application service area to be updated.

[0210] In box 1730, device 130 transmits a request to the second network entity to update the service duration of the application service area, wherein the request includes an application area reference identifier.

[0211] In block 1740, device 130 receives from a first network entity information including the service duration of an updated application service area, wherein the service duration of the updated application service area is determined by the first network entity based on information received from a second network entity.

[0212] In this way, the device can update the service duration of the application service area based on the needs of device 130. Therefore, the flexibility of using the application service area can be improved.

[0213] In some example embodiments, the radio access network device provides a serving cell or tracking area to the device, and an application area reference identifier received from the radio access network device corresponds to the serving cell or tracking area. In this way, the device can know the application area reference identifier corresponding to the application serving area currently serving the device. Therefore, the device can use the application area reference identifier to request an updated service duration from a second network entity without disclosing network details, thereby improving network security.

[0214] In some example embodiments, the application area reference identifier is received from the radio access network equipment via the System Information Block (SIB).

[0215] In some example embodiments, the information also includes individual network slice selection assistance information S-NSSAI for at least one network slice.

[0216] In some example embodiments, method 1700 further includes: performing communication on the application service region based on the updated service duration.

[0217] In some example embodiments, information is received via at least one of a Non-Access Stratum (NAS) configuration update message or a policy modification message.

[0218] Figure 18 A flowchart of an example method 1800 implemented at a radio access network device according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1800 describes the radio access network device 140 from the perspective of the radio access network device 140.

[0219] At box 1810, radio access network device 140 receives from the operator at least one application area reference identifier that identifies at least one application service area of ​​the radio access network device.

[0220] At box 1820, wireless access network device 140 sends an application area reference identifier associated with the application service area of ​​the device to the device.

[0221] In some example embodiments, the application area reference identifier is transmitted to the device via the System Information Block (SIB).

[0222] In some example embodiments, method 1800 further includes: receiving configuration information about the relationship between an application area reference identifier and an application service area from an operator; and transmitting the relationship between the application area reference identifier and the application service area to a second network entity.

[0223] In some example embodiments, a first network entity capable of performing any method 1200 (e.g., Figure 1 The first network entity 110 may include components for performing the corresponding operations of method 1200. This device can be implemented in any suitable form. For example, the device can be implemented in a circuit or software module. The first network entity may be implemented as or included in... Figure 1 In the first network entity 110.

[0224] In some example embodiments, the first network entity includes: components for receiving configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application area reference identifier, the at least one application area reference identifier being associated with an application service area for the device; components for determining information about an application service area corresponding to the at least one application area reference identifier based on the relationship between the application service area and the application area reference identifier; and components for transmitting the information about the application service area to the device.

[0225] In some example embodiments, the configuration information also includes at least one of the following: single network slice selection auxiliary information S-NSSAI or service duration of the application service area for at least one network slice.

[0226] In some example embodiments, the first network entity further includes a component for transmitting configuration information to the device in association with information about the application service area.

[0227] In some example embodiments, the first network entity further includes: a component for receiving relationships from radio access network equipment; and a component for determining information about an application service area corresponding to at least one application area reference identifier based on the relationships.

[0228] In some example embodiments, the radio access network device includes or is included in a next-generation node (B gNB).

[0229] In some example embodiments, the relationship is received from the radio access network device via an establishment request message or a radio access network (RAN) configuration update message.

[0230] In some example embodiments, information about the application service area indicates at least one cell or tracking area.

[0231] In some example embodiments, the first network entity further includes: a component for receiving configuration information from a third network entity, wherein the configuration information is received by the third network entity from the second network entity via a network entity implementing the Network Open Function (NEF); and a component for transmitting information about the application service area to the device via a Non-Access Stratum (NAS) configuration update message.

[0232] In some example embodiments, the first network entity further includes: a component for receiving configuration information from a third network entity, wherein the configuration information is received by the third network entity from the second network entity; and a component for transmitting information about the application service area to the device via a policy modification message.

[0233] In some example embodiments, the first network entity further includes: a component for receiving configuration information from a third network entity, wherein the configuration information is received by the third network entity from a network entity implementing a User Data Repository (UDR), wherein the configuration information is received by the network entity implementing the UDR from a network entity implementing the Network Application Function (NEF), and wherein the configuration information is received by the network entity implementing the NEF from a second network entity; and a component for transmitting information about the application service area to the device via a policy modification message.

[0234] In some example embodiments, the policy modification message indicates a modification to the device's access and mobility management AM policy or routing policy.

[0235] In some example embodiments, the first network entity implements or includes the Access and Mobility Management Function (AMF), the second network entity implements or includes the Application Function (AF), and the device includes or is included in a terminal device.

[0236] In some example embodiments, a second network entity capable of performing any method 1300 (e.g., Figure 1 The second network entity 120 may include components for performing the corresponding operations of method 1300. This device can be implemented in any suitable form. For example, the device can be implemented in a circuit or software module. The second network entity may be implemented as or included in... Figure 1 In the second network entity 120.

[0237] In some example embodiments, the second network entity includes components for determining configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region; and components for transmitting the configuration information for the device to the first network entity via at least one third network entity.

[0238] In some example embodiments, the second network entity further includes a component for determining, with the operator as part of a Service Level Agreement (SLA), at least one application area reference identifier that identifies at least one area.

[0239] In some example embodiments, the configuration information also includes at least one of the following: the duration of the single network slice selection auxiliary information S-NSSAI or the application service area for at least one network slice.

[0240] In some example embodiments, the second network entity further includes a component for transmitting configuration information to a network entity implementing the Network Open Function (NEF), wherein the configuration information is transmitted from the NEF-implementing network entity to the first network entity via a third network entity.

[0241] In some example embodiments, the second network entity further includes a component for transmitting configuration information to a third network entity, wherein the configuration information is transmitted from the third network entity to the first network entity.

[0242] In some example embodiments, the second network entity further includes a component for transmitting configuration information to a network entity implementing NEF, wherein the configuration information is transmitted from the network entity implementing NEF to the third network entity via a network entity implementing a user data repository (UDR).

[0243] In some example embodiments, the apparatus capable of performing any method 1400 (e.g., Figure 1 The device 130 may include components for performing the corresponding operations of method 1400. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or software module. The device may be implemented as or included in... Figure 1 In device 130.

[0244] In some example embodiments, the apparatus includes: a component for receiving information from a first network entity, wherein the information includes information about the application service area of ​​a network slice and the service duration of the application service area; and a component for performing communication on the application service area based on the information.

[0245] In some example embodiments, the information also includes: individual network slice selection assistance information S-NSSAI for at least one network slice.

[0246] In some example embodiments, the apparatus further includes a component for performing communication on the cell or tracking area indicated by the information based on information about the application service area.

[0247] In some example embodiments, this information is received from the first network entity via at least one of a Non-Access Stratum (NAS) configuration update message or a policy modification message.

[0248] In some example embodiments, a first network entity capable of performing any method 1500 (e.g., Figure 1 The first network entity 110 may include components for performing the corresponding operations of method 1500. This device can be implemented in any suitable form. For example, the device can be implemented in a circuit or software module. The first network entity may be implemented as or included in... Figure 1 In the first network entity 110.

[0249] In some example embodiments, the first network entity includes: components for receiving configuration information for updating the service duration of an application service area of ​​the device from a second network entity via at least one third network entity, wherein the configuration information includes an application area reference identifier associated with the application service area; components for determining the updated service duration of the application service area corresponding to the application area reference identifier based on the received configuration information; and components for transmitting information including the updated service duration to the device.

[0250] In some example embodiments, the configuration information also includes S-NSSAI corresponding to the application service region.

[0251] In some example embodiments, the first network entity further includes a component for determining the application service area corresponding to the application area reference identifier based on the relationship between the application area reference identifier and the application service area, wherein the relationship is received from the radio access network device via an establishment request message or a run configuration update message.

[0252] In some example embodiments, the first network entity further includes: a component for receiving configuration information from a third network entity, wherein the information is received by the third network entity from the second network entity; and a component for transmitting information including updated service duration to the device via a policy modification message.

[0253] In some example embodiments, the first network entity further includes: a component for receiving information from a third network entity, wherein the information is received by the third network entity from the second network entity via a network entity implementing a User Data Repository (UDR) and a network entity implementing a Network Open Function (NEF); and a component for transmitting information including updated service duration to the device via a policy modification message.

[0254] In some example embodiments, the first network entity implements or includes the Access and Mobility Management Function (AMF), the second network entity implements or includes the Application Function (AF), the device includes or is included in a terminal device, and the radio access network device implements or includes a next-generation node (B gNB).

[0255] In some example embodiments, a second network entity capable of performing any method 1600 (e.g., Figure 1 The second network entity 130 may include components for performing the corresponding operations of method 1600. This device can be implemented in any suitable form. For example, it can be implemented in a circuit or software module. The second network entity may be implemented as or included in... Figure 1 In the second network entity 130.

[0256] In some example embodiments, the second network entity includes: components for receiving a request from the device for updating the service duration, wherein the request includes an application region reference identifier associated with the application service region; components for determining information for updating the service duration of the application service region based on the application region reference identifier; and components for transmitting configuration information for updating the service duration of the application service region to the second network entity serving the device via at least one third network entity, wherein the configuration information includes an application region reference identifier associated with the application service region.

[0257] In some example embodiments, the configuration information also includes S-NSSAI corresponding to the application service region.

[0258] In some example embodiments, the second network entity further includes a component for determining an application area reference identifier that identifies at least one area based on a Service Level Agreement (SLA) with the operator.

[0259] In some example embodiments, the second network entity further includes a component for transmitting information for updating the service duration of the application service area to a third network entity, wherein the information will be transmitted from at least one third network entity to the second network entity.

[0260] In some example embodiments, the second network entity further includes: a component for transmitting information for updating the service duration of the application service area to a network entity implementing the Network Open Function (NEF), and wherein the information is transmitted from the network entity implementing the NEF to at least one third network entity via a network entity implementing the UDR.

[0261] In some example embodiments, the apparatus capable of performing any method 1700 (e.g., Figure 1 The device 130 may include components for performing the corresponding operations of method 1700. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or software module. The device may be implemented as or included in... Figure 1 In device 130.

[0262] In some example embodiments, the apparatus includes: components for receiving an application area reference identifier associated with an application service area of ​​the apparatus from a radio access network device; components for determining a service duration to be updated for the application service area; components for transmitting a request to a second network entity to update the service duration of the application service area, wherein the request includes the application area reference identifier; and components for receiving information including the updated service duration of the application service area from a first network entity, wherein the updated service duration of the application service area is determined by the first network entity based on the information received from the second network entity.

[0263] In some example embodiments, the radio access network device provides a serving cell or tracking area to the apparatus, and wherein an application area reference identifier received from the radio access network device corresponds to the serving cell or tracking area.

[0264] In some example embodiments, the application area reference identifier is received from the radio access network equipment via the System Information Block (SIB).

[0265] In some example embodiments, the information also includes individual network slice selection assistance information S-NSSAI for at least one network slice.

[0266] In some example embodiments, the apparatus further includes a component for performing communication on the application service region based on the updated service duration.

[0267] In some example embodiments, the information is received via at least one of a Non-Access Stratum (NAS) configuration update message or a policy modification message.

[0268] In some example embodiments, a radio access network device capable of performing any method 1800 (e.g., Figure 1 The radio access network device 140 may include components for performing the corresponding operations of method 1800. The device can be implemented in any suitable form. For example, the device can be implemented in a circuit or software module. The radio access network device can be implemented as or included in... Figure 1 In the radio access network equipment 140.

[0269] In some example embodiments, the radio access network device includes: components for receiving from an operator an application area reference identifier that identifies at least one application service area of ​​the radio access network device; and components for transmitting to the device the application area reference identifier associated with the application service area of ​​the device.

[0270] In some example embodiments, the application area reference identifier is transmitted to the device via the System Information Block (SIB).

[0271] In some example embodiments, the radio access network device further includes: a component for receiving configuration information about the relationship between an application area reference identifier and an application service area from an operator; and a component for transmitting the relationship between the application area reference identifier and the application service area to a second network entity.

[0272] Figure 19 This is a simplified block diagram of a device 1900 suitable for implementing an example embodiment of the present disclosure. The device 1900 can be provided to implement a communication device, such as... Figure 1The first network entity 110 or the second network entity 120 are shown. As shown, the device 1900 includes one or more processors 1910, one or more memories 1920 coupled to the processors 1910, and one or more communication modules 1940 coupled to the processors 1910.

[0273] Communication module 1940 is used for bidirectional communication. Communication module 1940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 1940 may include at least one antenna.

[0274] As a non-limiting example, processor 1910 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1900 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.

[0275] Memory 1920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1924, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1922 and other volatile memories that will not persist for the duration of a power outage.

[0276] Computer program 1930 includes computer-executable instructions that are executed by an associated processor 1910. The instructions of program 1930 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1930 may be stored in memory (e.g., ROM 1924). Processor 1910 can perform any suitable actions and processes by loading program 1930 into RAM 1922.

[0277] Example embodiments of this disclosure can be implemented via program 1930, enabling device 1900 to execute as described in the reference. Figures 2 to 18 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0278] In some example embodiments, program 1930 may be tangibly contained in a computer-readable medium, which may be included in device 1900 (such as memory 1920) or other storage device accessible by device 1900. Device 1900 may load program 1930 from the computer-readable medium into RAM 1922 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0279] Figure 20 An example of a computer-readable medium 2000 is shown, which may be in the form of a CD, DVD, or other optical storage disc. Program 1930 is stored on the computer-readable medium 2000.

[0280] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0281] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.

[0282] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0283] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0284] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0285] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0286] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

[0287] Furthermore, the various embodiments of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0288] Clause 1. A first network entity, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: receive configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application region reference identifier associated with an application service region for the device; determine information about the application service region corresponding to the at least one application region reference identifier based on a relationship between the application service region and the application region reference identifier; and transmit the information about the application service region to the device.

[0289] Clause 2. The first network entity as described in Clause 1, wherein the configuration information further includes at least one of the following: single network slice selection auxiliary information S-NSSAI for at least one network slice, or the service duration of the application service area.

[0290] Clause 3. The first network entity as described in Clause 2, wherein the first network entity is further configured to: transmit the configuration information to the device in association with the information regarding the application service area.

[0291] Clause 4. A first network entity according to any one of Clauses 1 to 3, wherein the first network entity is configured to: receive the relationship from a radio access network device; and determine, based on the relationship, the information regarding the application service area corresponding to the at least one application service area reference identifier.

[0292] Clause 5. The first network entity as described in Clause 4, wherein the radio access network equipment includes or is included in the next-generation node B gNB.

[0293] Clause 6. The first network entity as described in Clause 4 or 5, wherein the relationship is received from the radio access network device via an establishment request message or a radio access network (RAN) configuration update message.

[0294] Clause 7. A first network entity pursuant to any one of Clauses 1 to 6, wherein the information regarding the application service area indicates at least one cell or tracking area.

[0295] Clause 8. A first network entity according to any one of Clauses 1 to 7, wherein the at least one third network entity includes a network entity implementing Unified Data Management (UDM) functionality, and wherein the first network entity is configured to: receive the configuration information from the third network entity, wherein the configuration information is received by the third network entity from the second network entity via a network entity implementing Network Open Function (NEF); and transmit the information about the application service area to the device via a Non-Access Stratum (NAS) configuration update message.

[0296] Clause 9. A first network entity according to any one of Clauses 1 to 7, wherein the at least one third network entity includes a network entity implementing a Policy Control Function (PCF), and wherein the first network entity is configured to: receive the configuration information from the third network entity, wherein the configuration information is received by the third network entity from the second network entity; and transmit the information about the application service area to the device via a policy modification message.

[0297] Clause 10. A first network entity according to any one of Clauses 1 to 7, wherein the at least one third network entity includes a network entity implementing PCF, and wherein the first network entity is configured to: receive the configuration information from the third network entity, wherein the configuration information is received by the third network entity from a network entity implementing a User Data Repository (UDR), wherein the configuration information is received by the network entity implementing the UDR from a network entity implementing NEF, and wherein the configuration information is received by the network entity implementing NEF from the second network entity; and transmit the information about the application service area to the device via a policy modification message.

[0298] Clause 11. The first network entity as described in Clause 10, wherein the policy modification message indicates a modification to the Access and Mobility Management (AM) policy or routing policy for the device.

[0299] Clause 12. A first network entity according to any one of Clauses 1 to 11, wherein the first network entity implements or includes an Access and Mobility Management Function (AMF), the second network entity implements or includes an Application Function (AF), and the means is included in or is included in a terminal device.

[0300] Clause 13. A second network entity, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: determine configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region; and transmit the configuration information for the device to the first network entity via at least one third network entity.

[0301] Clause 14. The second network entity as described in Clause 13, wherein the second network entity is configured to: determine, with the operator as part of a Service Level Agreement (SLA), the at least one application area reference identifier that identifies at least one area.

[0302] Clause 15. The second network entity as described in Clause 13 or 14, wherein the configuration information further includes at least one of the following: individual network slice selection assistance information S-NSSAI for the at least one network slice, or the duration of the application service area.

[0303] Clause 16. A second network entity according to any one of Clauses 13 to 15, wherein the at least one third network entity includes a network entity implementing Unified Data Management (UDM) functionality, and wherein the second network entity is configured to: transmit the configuration information to a network entity implementing Network Open Function (NEF), wherein the configuration information is transmitted from the NEF-implementing network entity to the first network entity via the third network entity.

[0304] Clause 17. A second network entity according to any one of Clauses 13 to 15, wherein the at least one third network entity includes a network entity implementing a policy control function (PCF), and wherein the second network entity is configured to: transmit the configuration information to the third network entity, wherein the configuration information will be transmitted from the third network entity to the first network entity.

[0305] Clause 18. A second network entity according to any one of Clauses 13 to 15, wherein the at least one third network entity includes a network entity implementing PCF, and wherein the second network entity is configured to: transmit the configuration information to a network entity implementing NEF, wherein the configuration information is transmitted from the network entity implementing NEF to the third network entity via a network entity implementing a User Data Repository (UDR).

[0306] Clause 19. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause a first network entity to at least: receive information from the first network entity, wherein the information includes information about an application service area of ​​a network slice and the service duration of the application service area; and perform communication on the application service area based on the information.

[0307] Clause 20. The apparatus according to Clause 19, wherein the information further includes: individual network slice selection assistance information S-NSSAI for at least one network slice.

[0308] Clause 21. The apparatus according to Clause 19 or 20, wherein the information regarding the application service area indicates at least one cell or tracking area, and wherein the apparatus is further configured to: perform communication on the cell or tracking area indicated by the information regarding the application service area based on the information.

[0309] Clause 22. The apparatus according to any one of Clauses 19 to 21, wherein the information is received from the first network entity via at least one of the following: a Non-Access Stratum (NAS) configuration update message, or a policy modification message.

[0310] Clause 23. A method comprising: receiving configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application region reference identifier associated with an application service region for the device; determining information about the application service region corresponding to the at least one application region reference identifier based on a relationship between the application service region and the application region reference identifier; and transmitting the information about the application service region to the device.

[0311] Clause 24. A method comprising: determining configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region; and transmitting the configuration information for the device to a first network entity via at least one third network entity.

[0312] Clause 25. A method comprising: receiving information from a first network entity, wherein the information includes information about an application service area of ​​a network slice and the service duration of the application service area; and performing communication on the application service area based on the information.

[0313] Clause 26. A first network entity, comprising: means for receiving configuration information for a device from a second network entity via at least one third network entity, wherein the configuration information includes at least one application region reference identifier associated with an application service region of the device; means for determining information about the application service region corresponding to the at least one application region reference identifier based on a relationship between the application service region and the application region reference identifier; and means for transmitting the information about the application service region to the device.

[0314] Clause 27. A second network entity, comprising: components for determining configuration information for a device, wherein the configuration information includes at least one application region reference identifier for an application service region; and components for transmitting the configuration information for the device to a first network entity via at least one third network entity.

[0315] Clause 28. An apparatus comprising: a component for receiving information from a first network entity, wherein the information includes information about an application service area of ​​a network slice and the service duration of the application service area; and a component for performing communication on the application service area based on the information.

[0316] Clause 29. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method as described in any one of Clauses 23 to 25.

Claims

1. A first network entity for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: Configuration information for a device is received from a second network entity via at least one third network entity, wherein the configuration information includes at least one application region reference identifier, the at least one application region reference identifier being associated with an application service region for the device; Based on the relationship between the application service region and the application region reference identifier, information about the application service region corresponding to the at least one application region reference identifier is determined. as well as The information about the application service area is transmitted to the device.

2. The first network entity according to claim 1, wherein the configuration information further includes at least one of the following: For a single network slice, select auxiliary information S-NSSAI for at least one network slice, or The duration of service in the application service area.

3. The first network entity according to claim 2, wherein the first network entity is further configured such that: The configuration information is transmitted to the device in association with the information about the application service area.

4. The first network entity according to claim 1, wherein the first network entity is configured such that: Receive the relationship from the radio access network equipment; and The information about the application service region corresponding to the at least one application service region reference identifier is determined based on the relationship.

5. The first network entity of claim 4, wherein the radio access network equipment comprises or is included in a next-generation node (gNB).

6. The first network entity of claim 4, wherein the relationship is received from the radio access network device via an establishment request message or a radio access network (RAN) configuration update message.

7. The first network entity of claim 1, wherein the information regarding the application service area indicates at least one cell or tracking area.

8. The first network entity according to claim 1, wherein the at least one third network entity includes a network entity implementing Unified Data Management (UDM) functionality, and wherein the first network entity is configured such that: The configuration information is received from the third network entity, wherein the configuration information is received by the third network entity from the second network entity via a network entity implementing the Network Open Function (NEF); and The information about the application service area is transmitted to the device via a non-access stratum NAS configuration update message.

9. The first network entity of claim 1, wherein the at least one third network entity comprises a network entity implementing a policy control function (PCF), and wherein the first network entity is configured such that: Receive the configuration information from the third network entity, wherein the configuration information is received by the third network entity from the second network entity; and The information about the application service area is transmitted to the device via a policy modification message.

10. The first network entity of claim 1, wherein the at least one third network entity comprises a network entity implementing PCF, and wherein the first network entity is such that: The configuration information is received from the third network entity, wherein the configuration information is received by the third network entity from the network entity implementing the User Data Repository (UDR). in, The configuration information is received by the network entity implementing UDR from the network entity implementing NEF, and the configuration information is received by the network entity implementing NEF from the second network entity; as well as The information about the application service area is transmitted to the device via a policy modification message.

Images