Method of managing connection to local area data network (LADN) in 5g network

Abstract

To provide a device and a method for background data transfers (BDTs) between local area data networks (LADNs).SOLUTION: An apparatus receives a message indicating a request from user equipment (UE) for data transfer of data originating from the UE. The apparatus sends, to a database, a request for subscription information associated with the UE and a policy profile associated with the UE to determine whether there is an existing BDT policy. Based on receiving a response indicating whether there is an existing BDT policy that can be re-used, the apparatus determines a BDT policy for the data transfer and a LADN to service the data transfer. The apparatus sends, to the LADN via a radio access network (RAN) node, a notification message of an arrival time and data rate for the data transfer.SELECTED DRAWING: Figure 10

Description

[Background technology]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application is a continuation of U.S. Provisional Patent Application No. 62 / 653,827, filed April 6, 2018. No. 60 / 699,999, filed on Oct. 1, 2003, which is incorporated herein by reference in its entirety.

[0002] Background Data Transfer (BDT) is a feature that allows you to transfer data at a constant rate. Data transfer to User Equipments (UE) for a specific period at a rate Allows the Application Server (AS) to be pre-configured Long Term Evolution is a resource management mechanism. LTE Evolved Packet Core (EPC) is a mobile termination (Mobile Terminated: MT) traffic BDT consists of the service capability service of the AS. Defines procedures for local area data networks. A Data Network (LADN) is a data network that can be accessed by UE only at a specific location. Packets for the Data Network (DN) Access to the DN via a Packet Data Unit (PDU) session is , may only be available in certain LADN service areas. LADN service areas may be a different set of tracking areas. ) The network uses the UE location to make the UE aware of the availability of the LAD NDC. may provide support for

[0003] The LADN provides a specific area defined as the service area. Repeated connections to a DN may be required, for example, due to certain mobility patterns. May contain lines.

[0004] Some Internet of Things (IoT) device applications Applications and IoT servers can only operate within the service area of the LADN. In addition, the UE may send Mobile Originated (MO) Pre-configuring BDT policies in 5G networks and sending traffic It may be necessary to

[0005] Therefore, data transfers in different LADNs, such as for MO traffic, can be handled by the device. A mechanism needs to be defined to allow for the scheduling and implementation of the Summary of the Invention

[0006] This Summary is provided in a simplified form to provide an overview of the Detailed Description, which is further described below. This Summary is intended to introduce key features or substantial aspects of the claimed subject matter. It is not intended to be used to characterize or limit the scope of the claimed subject matter. Moreover, claimed subject matter does not incorporate any of the features described anywhere in this disclosure. Nor is it intended to be constrained by limitations that address any or all of the disadvantages.

[0007] Service Capability Server (SCS) / Application Server The AS is a local area data network (LADN) / data network How to configure and manage background data transfers between (DNs) According to one embodiment, the device is a user terminal (U E) receiving a message indicating a request from the UE for data transfer of data originating from The device may have an existing Background Data Transfer (BDT) policy. Subscription information related to the UE, and The device sends a request to the database for the associated policy profile. Returns a response from the database indicating whether there is an existing BDT policy that can be Based on the response received, the device may determine the BDT for that data transfer. The device may decide the policy and the LADN to which it will provide data transfer. Radio Access Network (RAN) nodes connect to the LADN. , may send a notification message of the arrival time and data rate of that data transfer. .

[0008] BRIEF DESCRIPTION OF THE DRAWINGS To facilitate a better understanding of the present application, reference is made to the accompanying drawings, in which: In each of these drawings, like elements are referenced with like numerals. They should not be construed as limiting, but are intended to be illustrative only. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an exemplary non-roaming reference architecture that uses a service-based interface in the control plane. [Figure 2] FIG. 2 shows an exemplary 5G system architecture in a non-roaming case. [Figure 3A] FIG. 3A is a diagram of an example procedure for establishing a PDU session. [Figure 3B] FIG. 3B is a continuation of an exemplary procedure for establishing a PDU session. [Figure 4] FIG. 4 is a diagram of an exemplary procedure for background data transfer (BDT). [Figure 5] Figure 5 is a conceptual architecture diagram of network slicing. [Figure 6] FIG. 6 is a diagram of an exemplary LADN use case in a 5G network. [Figure 7] FIG. 7 is a diagram of an exemplary procedure for configuring information sharing and mobility support between LADNs. [Figure 8] FIG. 8 is a diagram of an exemplary procedure for moving a PDU session from a first LADN to a second LADN. [Figure 9] FIG. 9 is a diagram of an example procedure initiated by a UE to configure a BDT for MO traffic. [Figure 10] FIG. 10 is a diagram of an example procedure for BDT configuration for MO traffic initiated by the UE and configured by the DN / LADN. [Figure 11] FIG. 11 is a diagram of an example procedure for BDT policy configuration for MO traffic initiated by DN / LADN. [Figure 12] FIG. 12 is a diagram of an example procedure for a UE-initiated procedure for configuring a BDT policy for MO traffic in the EPC. [Figure 13] FIG. 13 is a diagram of an exemplary user interface for configuring background data transfer in a 5G network. [Figure 14] FIG. 14 is a diagram illustrating an example of a UE connected to an inventory management system. [Figure 15] FIG. 15 is a diagram illustrating an example of establishing a connection to the LAN. [Figure 16] FIG. 16 is an illustration of area notification via a Graphical User Interface (GUI). [Figure 17A] FIG. 17A illustrates an exemplary communication system. [Figure 17B] FIG. 17B is a system diagram of an example RAN and core network. [Figure 17C] FIG. 17C is a system diagram of an example RAN and core network. [Figure 17D] FIG. 17D is a system diagram of an example RAN and core network. [Figure 17E] FIG. 17E illustrates another example of a communication system. [Figure 17F] FIG. 17F is a block diagram of an example apparatus or device, such as a WTRU. [Figure 17G] FIG. 17G is a block diagram of an exemplary computing system. DETAILED DESCRIPTION OF THE INVENTION

[0010] Service Capability Server (SCS) / Application Server (AS) in the local area Information sharing between a set of data networks (LADN) / data networks (DN) The present invention provides a method and apparatus for configuring network connectivity and mobility support. Reusing session context information from a previous session This specification describes a simplified session establishment procedure for connecting to the LDAP server via Internet of Things (IoT) device applications will be included in the service documentation. Application Programming Interface (API) to help manage turbulence ication Programming Interface (API), and graphical user interface A GUI is also described herein. ) traffic, and then 2. A method for user equipment (UE) to transfer actual data later in LADN Also described herein.

[0011] Table 1 lists technologies that may be used in the architectures and examples described herein. This is a list of related acronyms.

[0012] [Table 1]

[0013] Table 2 lists technologies that may be used in the architectures and examples described herein. Here is a list of definitions related to

[0014] [Table 2]

[0015] FIG. 1 illustrates an exemplary non-roadmap using service-based interfaces in a control plane 50. As shown in the example of Figure 1, the UE 70 is a wireless access point. Access via the RAN 71 through the N1 interface 67 Access to the Mobility Management Function (AMF) 65. The Namf interface 62 is also The RAN 71 communicates with the Access Mobility via the N2 interface 68. The RAN 71 accesses the AMF 65 via the N3 interface 74. The UPF 72 accesses the User Plane Function (UPF) 72 via the N4 interface. Access to the Session Management Facility (SMF) 66 through the Nsmf interface 69. The UPF 72 is connected to the N6 interface 75 via the N7 interface 76. to access data network (DN) 73.

[0016] The example in Figure 1 also shows the Network Exposure Function (NEF) 51 and the Nnef interface. Phase 56, NF Repository Function (NRF) 52 and Nnr f interface 57, Policy Control Function (PCF) 53 and Npcf interface 58, Unified Data Management (UDM) 54 and Nudm Interface 59, Application Function (AF) 55 and Naf interface 60, and (AUSF) 64 and Naus f indicates other network functions (NFs) in the control plane, such as interface 61 are.

[0017] Figure 2 is a table of reference points that shows how various network functions interact with each other. 2 illustrates an exemplary 5G system architecture for a non-roaming case 200. End-to-end communication between 201 applications and applications in external networks The end communication may use services provided by the 3GPP system, or The services provided by a Service Capability Server (SCS) which may reside on a DN204. As shown in the example of Figure 2, the UE 201 may use the RAN 202. accesses the AMF 212 through the N1 interface 220. The RAN 202 is also shown with an N2 interface 22. 1. The RAN 202 accesses the AMF 212 via the N3 interface 222. The UPF 203 is accessed via the N4 interface 223. The SMF 213 is accessed via the N9 interface 234. F203 accesses DN204 via N6 interface 225. Example of Figure 2 The figure also shows other NFs in the control plane. The PCF 214 is The PCF 214 may communicate with the SMF 213 via the N7 interface 226. The PCF 214 may communicate with the SMF 213 via the N15 interface 226. The SMF 213 may communicate with the AMF 212 via an interface 233. It may communicate with the AMF 212 via the N11 interface 229. 3 may communicate with the UDM 211 via an N10 interface 228. The F212 may communicate with the UDM211 via an N8 interface 227. The AMF 212 communicates with the AUSF 210 via the N12 interface 230. The UDM211 communicates with the AUSF210 via the N13 interface 231. This may occur.

[0018] Applications in external networks are typically managed by an application server (AS). may use SCS for additional value-added services. The P system includes transport, subscriber management, and, but is not limited to, the MTC. This includes various architectural extensions that are triggered by the control plane device. The mobility management and session management functions are separated. The N1 220 NAS connection is managed by the Registration Management and Connection Management. for both Connection Management and Connection Management (RM / CM), and may be used for SM related messages and procedures towards the UE 201. The N1 220 termination point may be located within the AMF 212. The AMF 212 , the AMF 212 may deliver SM-related NAS information to the SMF 213. It may handle the registration management and connection management parts of the NAS signaling exchanged with 01. The SMF 213 is responsible for the session management parameters of the NAS signaling exchanged with the UE 201. May handle tickets.

[0019] A local area data network (LADN) is a network that can be accessed by a UE only at a specific location. A DN is defined as a DN that provides connectivity to a specific DN. The availability of the PDU session for the LADN may be provided to the UE. Access to the DN via the Internet may only be available in certain DN service areas. A 5G LTE service area may include a set of tracking areas. C supports making the UE aware of the availability of LADN based on the UE's location. may be provided.

[0020] The AMF 212 transmits the LADN information including information on the availability of the LADN to the UE 201. The AMF 212 provides the UE 201 with the information necessary to N available area) depending on whether you are tracking SMF213, and The LADN information may be configured in the AMF 212 for each DN. For example, for different UEs accessing the same LADN, the configured LADN service The area may be the same regardless of other factors (e.g., UE registration area) .

[0021] The LADN information provided to the UE 201 by the AMF 212 is the LADN data network If the UE 201 includes the Network Name (DNN) and the LDDN service area information that the UE 201 can use, The LADN service area information provided to the UE 201 during the registration procedure The tracking area that belongs to the current registration area of the UE 201 (i.e., the LADN subarea) AMF21 may contain a set of AMF21 service areas (intersection of the current registration area). 2 may not create a registration area based on the availability of LADN.

[0022] 3A-3B illustrate a PDU session 300 that may be initiated by a UE. 3A-3B are diagrams of an exemplary procedure for establishing a method for performing a method for a computer-implemented computer-implemented system. Although the tips are shown and described separately, they may not be connected to each other in a different order than shown. Multiple steps may be performed in parallel or simultaneously with each other. 5G Core (5GC) The network provides for the exchange of PDUs between the UE and the DN identified by the DNN. Each PDU supports PDU connectivity services, which may be services that A session is a single PDU session that may be requested by the UE when establishing a PDU session. It may support the following PDU session types: IPv4, IPv6, Ethernet and unstructured types are included. The PDU session may be, for example, an N1 interface between the UE and the SMF. using NAS SM signalling exchanged over the interface (at UE request) established (by UE and 5GC requests), modified (by UE and 5GC requests), and Upon request from the application server, the 5G C can trigger a specific application in the UE. Upon receiving the request, the UE may pass it to an identified application of the UE. be.

[0023] Referring to the example of FIG. 3A, the UE 301 transmits a PD to the AMF 303 via the RAN 302. AMF 303 may select an SMF and send a U establishment request (step 311). (Step 312), and the PDU session context is stored in the selected SMF, SMF305. A creation request may be sent (step 313). 3. Read and / or update the PDM 307 (step 314) A DU session context creation response may be sent (step 315). A PDU session may be authenticated and authorized between the UE 301 and the DN 308. (Step 316). The SMF 305 may select the PCF 306 (Step Then, the SMF 305 and the selected PCF, PCF 306, The SMF may then establish and / or modify application management policies (step 318). 305 may select a UPF (step 319). The SMF 306 may modify the session management policy (step 320). 5 then sends an N4 session establishment / modification request to the selected UPF, UPF 304 (Step 321).

[0024] Referring to the example of FIG. 3B, the UPF 304 then sends an N4 session establishment / modification response to The SMF 305 and the AMF 303 may transmit the The N1N2 message may be forwarded over the interface (step 323). The AMF 303 sends to the RAN 302 an N2 PDU, which may be an NAS message. The UE 301 and the RAN 302 may send a session request (step 324). , AN-specific resources may be set up (i.e., PDU session establishment acceptance) (Step 325). The RAN 302 then sends an N2PDU session request acknowledgement. The UE 301 may then transmit the first uplink data (step 326). Next, the AMF 303 may send the PDU session The SMF 305 may then send an SM context update request (step 328). The UPF 304 may then send an N4 session modification request (step 329). The SMF 305 may then send an N4 session modify response (step 330). SMF305 then sends the Nsmf PDU session SM context update to AMF303. Response (step 331) and Nsmf PDU session SM to AMF 303 The SMF 305 may send a context status notification (step 332). UE 301 may then configure an IPv6 address for UE 301. UE 301 may then receive the first downlink data The PCF 306 may receive the unsubscribe / unregister (step 334). Removal may be performed (step 335).

[0025] FIG. 4 is a diagram of an exemplary procedure for background data transfer (BDT) 400. Although each step of procedure 400 in FIG. 4 is shown and described separately, Multiple steps can be performed in a different order than shown, in parallel with each other, or simultaneously with each other. The BDT resource management procedure may be performed at a certain data rate for a specific period. This may allow the SCS / AS to pre-configure data transfer to the UE between The example in Figure 4 shows the procedure for configuring the forwarding policy for BDT in the EPC. .

[0026] Referring to the example in Figure 4, the third-party SCS / AS 405 may provide the SCEF 404 with A background data transfer request message may be sent (step 410). This background data transfer request message contains the SCS / AS identifier, TTRI, and U This may include capacity per E, number of UEs, and desired time window. SCS / AS40 5 may provide geographic area information. The SCEF 404 authorizes the SCS / AS request. The SCEF 404 may select one of the available PCRFs 403 (step 411). Select to enable the Policy Control and Charging (PCC) process. The PCRF 403 and the SCS may trigger a procedure (step 412). Future by SCEF 404 delivering parameters provided by AS 405 This may include negotiating background data transfer procedures. , the PCRF 403 responds to the SCEF 404 with possible forwarding policies and reference IDs. The SCEF 404 may include the TTRI, the reference ID, and a possible forwarding policy. By sending a Background Data Transfer Response message which may include , may deliver the reference ID and forwarding policy to the third-party SCS / AS 405 (S Step 413). SCS / AS 405 will use Reference I for future interaction with the PCRF. If more than one forwarding policy is received, the third-party SCS may store D. / AS405 selects one of them and sends the SCS / AS identifier, TTRI, and the SCEF 40 by sending another BDT Request message which may contain the forwarding policy specified. 4 and PCRF 403 about the selected forwarding policy (step 41 4) The SCEF 404 sends a background data transfer response message (TTRI). Confirm forwarding policy selection with a third-party SCS / AS405 by sending a The SCEF 404 may send the reference ID and the new forwarding address to the SPR (step 415). The PCRF 403 may remember the policy and future background data transfer policies. The SCS / AS 405 may continue with the negotiation of the route (step 416). The AF (which acts as an AF) is the same or different for each individual UE (through the Rx interface). The SCS / AS 405 may contact different PCRFs 403 and provide a reference ID. Alternatively or additionally, the SCS / AS 405 may provide session setup The set of chargeable parties at a time, or the set of chargeable parties during a session procedure By using the change of the property, the PCEF4 The selected forwarding policy 417 may be activated with 01 (step 417).

[0027] FIG. 5 is a diagram of a conceptual architecture 500 for network slicing. Network slicing may include both backhaul and core networks. Multiple networks behind the air interface over the fixed part of the mobile operator's network Used by mobile network operators to support multiple "virtual" networks Network slicing is a mechanism that can be used to share data across different RANs and and / or to support different service types operating across a single RAN , which involves "slicing" a network into multiple virtual networks. Slicing may require diverse requirements in functionality, performance, and independence, for example. Customized to provide optimized solutions for different potential market scenarios This allows operators to create customized networks.

[0028] Referring to the example of FIG. 5, the network slice instance is configured in the resource layer 503 as follows: Network functions, resources, and the network functions that operate them The network slice instance layer 502 may include a set 513. Multiple network slice instances 511a, 511b, 511c, 511d, 5 11e, 511f, 511g and 511h, or subnetwork slice instances may include instances 512a, 512b, 512c, 512d, 512e, and 512f. The subnetwork slice instance is responsible for the network functions and the A network that contains a set of resources that run a network function, but is itself a complete logical network. A subnetwork slice instance may not be a subnetwork slice. As shown using the network slice instance 512d, multiple network slice instances The service instance layer 501 is a layer that stores information about a service instance. The cabinets may include chests 510a, 510b, 510c, 510d, and 510e.

[0029] Network slicing technology is being incorporated into technologies such as 3GPP 5G networks. Network slicing may be part of the 5G network use cases. (e.g., large-scale IoT, critical communications, and advanced mobile broadband) It allows for related, diverse and highly demanding requirements. The 5G architecture will enable smartphones, over-the-top (OTT) content, and Mobile traffic from feature phones, data cards, and embedded M2M devices Relatively monolithic network and traffic handling various services such as Leverages transport framework, capabilities and extensions related to pre-5G architecture A specific set of performance and usage requirements efficiently supports a wide range of business needs In addition, it may not be flexible and scalable enough to accommodate new network services. The introduction of services may be more efficient. The cases are expected to operate simultaneously in the same operator network, and therefore In addition, the high flexibility and scalability that comes with 5G networks will be beneficial.

[0030] FIG. 6 is a diagram of an example LADN use case in a 5G network 600. In this example In some cases, commuter trains have video surveillance systems and electronic bulletin boards. Networks 603, Internet 608 and Multiple LADNs 605, 604, 6 They may have communications circuits that allow connections to 06 and 607. A train may contain an SCS / AS that hosts multiple AFs. When a train arrives at a station, Connect to an LADN such as LADN604 to upload video recordings from your surveillance system. And may download some local advertisements for bulletin boards. The device used for this (e.g., UE) also connects to the LADN to download the video. Load and / or upload content from your device for backup For video uploads and local ad downloads, trains may Connect to the DN to check whether the LADN supports video uploading or DN first determines if there are any local ads for the download Trains arrive and depart from each station on a relatively regular schedule, so LADN The connection and the length of time of the connection may be predictable. For example, if a train passes through a station on the same schedule, it may run at the same time once a day. At around the same time T1 601, LADN 604 and at around the same time T2 602, It may be connected to the net 608.

[0031] Each LADN along the line is allocated with different capacities by the network operator. For example, some LADNs may be designed to provide high uplink data rates. However, they may not have video / image content for download. Another LADN stores the desired video content but does not support uplink data transfer. Therefore, the device may have an SCS / AS that is not supported by the LADN. Before connecting to the LDAP server, the server must know what services it supports and must be able to You may be able to schedule or plan your visit to the service.

[0032] As mentioned above, based on the train schedule, it is possible to determine when the train will begin connecting to the LADN. In other words, the duration of the connection to the LADN can be predicted. Connections can be determined in advance according to train schedules. In some use cases, this may be repeated (periodically at fixed intervals). However, the 5GC defines the protocol for establishing a connection to the LADN (i.e., a PDU session). The mechanisms used are UE registration requests, PDU session establishment / activation requests, Location verification by AMF to ensure E is within the coverage area of the LADN, and It involves many steps, such as anchor point selection by the Session Management Function (SMF). Such connections to the LADN follow similar patterns in time and duration. This allows the UE, or in the example above the train, to complete the data transfer quickly and efficiently. Streamline the session establishment / activation mechanism for LADN so that It is desirable.

[0033] Additionally, we recognize the LADN's ability to save time and be more effective. Without this, it is not possible to schedule data transfers in one LADN (for example, train station 1). and scheduled activities in a pre-configured LADN (e.g., Train Station 2). For example, trains may not be able to upload video footage. However, if the LDPN you are connecting to has a high uplink data rate, If the LADN serving the next station does not support the high-speed uplink The current LADN may know if it supports link data transfer. Therefore, the current LADN will not be able to provide the train with uplink data for the next LADN. Schedule a transfer and notify the train to do it when it arrives at the next station The existing mechanisms of 5GC do not support such operations. The device can forward data in different LANs, such as for mail-originated (MO) traffic. A schedule and mechanisms to enable implementation must be defined. By sharing additional information between the Network Functions (NFs) serving the LADN, Possible mechanism for session establishment / activation on LADN The system needs to be streamlined.

[0034] Regarding the above operations, constrained IoT devices have group-based data transfer. In other words, it may be desirable to group IoT devices (e.g., sensors) It is better to schedule and perform data transfers across different LADNs for a group. It may be more efficient.

[0035] 5G LADNs are accessible to UEs only in specific locations and can only be connected to specific DNs. LA is a type of DN that provides the functionality and whose availability is provided to the UE. DN improves efficiency by reducing end-to-end delay and load on the traffic network. Operators and third-party services can connect to each other to realize efficient service delivery. Allows the UE to be hosted near the access point. Configure information sharing and mobility support in the PDU session that connects the LADN. You can transfer a PDU session from one LADN to another without repeating the procedure to establish a PDU session. Transferring the application, UE startup procedure, DN / LADN startup procedure and Background for MO traffic with LADN, including group-based BDT Data Transfer (BDT) configuration and how to perform MO BDT in LTE EPC and devices are described herein.

[0036] 7 through 16 (described below) illustrate various aspects of managing connections to the LAN. These figures illustrate embodiments of one or more nodes, apparatus, devices, servers, Various steps or operations performed by a network, function, or network are shown. For example, devices may operate alone or in conjunction with one another to perform the methods described herein. As used herein, the terms "device," "network device," "node," " Server, Device, Entity, Network Function, and Network The nodes and data nodes shown in these figures are sometimes used interchangeably. A device, server, function or network refers to a logical entity in a communications network. may be used, including one of the general architectures shown in the figures described herein. The form of software stored in the memory of the nodes of such a network may include (e.g., computer-executable instructions) and executes on that processor That is, the methods described herein may be implemented in a manner that is compatible with, for example, a node or computer. A form of software stored in the memory of a network node such as a computer system (e.g. For example, the software may be implemented in computer executable instructions, and this computer executable The executable instructions, when executed by a processor of a node, perform the steps described herein. Also, any transmitting and receiving steps shown in these figures may be , the node's processor and the computer-executable instructions that the processor executes (e.g. For example, it may be implemented by the node's communication circuitry under control of a It is understood that the nodes, devices, and functions described herein are part of a virtualized network. It is further understood that the present invention may be implemented as a network function.

[0037] In the embodiments described herein, the term "AF" refers to the SCS / AS within the LADN. The LDAP server may be used to configure policies and exchange information. The AF may not reside within the LAN. Instead, it is operated by a network operator that handles different service providers. It may be a standalone / independent application management feature created by

[0038] FIG. 7 illustrates a mobile device for information sharing and mobile device management between LADNs 700 that may be used in one embodiment. 7 is a diagram of an exemplary procedure for configuring a reliability support. Although each step is shown and described separately, it may be performed in a different order than shown. Multiple steps may be performed in parallel or simultaneously with one another. Information may be shared between a set of LADNs. A set of LADNs is a set of LADNs that are part of the same network. Various types of information may be shared, This includes but is not limited to the following:

[0039] They may be configured by LADN and support the same applications or or may be reused by other LDNAs belonging to the same network operator. , regarding charging policies and / or mobility support in the LADN context. Policies such as the BDT policy, which may include policies that

[0040] UE registration / connection information and session context information when the UE connects to the LADN UE-specific context may be shared between a set of LADNs.

[0041] Such information sharing results in connecting and / or distributing PDU sessions with the LADN. When establishing or updating a UE, registration and session management may be simplified. Another benefit is that mobility is supported. and, in the context of LADN, this includes:

[0042] In one LADN, registration and session termination occurs when the UE moves out of the service area. The context information is retained and can be read when the UE returns. For example, as shown in the use case above, this allows It may be more efficient when the UE's connection to the ADN is periodic.

[0043] Across multiple LADNs, registration and session context is maintained as the UE moves. This means that the UE may be connected to an edge device of one LADN. If you access content from the cache and the same content is cached, Move to another LADN that has the content cached, or move to a LADN or Edge if you need to access the original version of the content by going to the DN May be useful in caching use cases.

[0044] In the train use case above, each LADN along the track forms an LADN group. If trains are in close proximity to LADN, they may use information sharing. In some cases, it may connect to the LADN, and the LADN server (i.e., SCS / AS) may communicate with the CN configuring policies related to information sharing.

[0045] Referring to the example in Figure 7, to configure information sharing and mobility support, AF7 04 sends a request message to NEF 703 indicating a request for registration / session configuration This message may be used to configure policies in the network. This policy may apply to two or more LADNs to establish a UE connection. How connections and / or sessions can persist across the entire LDAP A request message may be encapsulated in another type of request message. Information may include, but is not limited to, AF ID, The UE ID (SUPI or GPSI) of the device that needs to be A list of LADN / DN identifiers indicating the LADN / DNs that are to be used by the AF to enable information sharing features. An indication of the type of LADN the policy may be associated with. Notifications, information and / or policies that may be shared across the entire LADN type of mobility, whether the core network supports mobility when the UE connects to a specific LADN An indication that the AF wants to support the UE type. Type or application type (e.g., mobile non-IoT devices) and LADN Applications that may get mobility support when connecting to mIoT, eMBB, etc.), as well as the level of mobility support.

[0046] An indication that the AF wishes to enable information sharing features supporting different LADNs. A policy or user policy that is shared across all AMFs, SMFs or UPFs that it serves. In addition, each PCF may have a different LADN. When configuring policies, policies and user contexts are also shared across all PCFs. may be shared.

[0047] Instead of a LADN identifier or list of DN identifiers, the AF should specify the L An indication of the type of ADN may be provided. For example, this indication is , LADN supporting certain services, L related to certain NSSAI or SST It may refer to an ADN or an LADN belonging to a certain network operator.

[0048] The types of information and / or policies that may be shared across the LADN include: background data transfer policy, charging policy, UE registration and session Context information, etc.

[0049] When a UE connects to a specific LADN, the AF informs the core network about the mobility support. The indication of willingness to support the AF is, for example, If you do not choose to do so, the UE connected to the LAN will move out of the service area. When the AMF notifies the SMF, the PDU session is started by the SMF as soon as When the AF enables mobility support, ,Unless the UE receives a clear PDU session release request from the network, the SMF , it may not release any existing PDU sessions for this LADN DNN.

[0050] The level of mobility support may indicate the extent to which mobility is supported. For example, this means that mobility can be to a single LADN or across multiple LADNs. In the case of a single LADN, this may indicate whether the UE When a user moves outside its service area, the registration status is maintained by the LADN. Whether the registration and session are active and whether the PDU session is released May indicate whether a context is being maintained. In the case of multiple LADNs, this When a UE moves, registration and session information and status are transferred from one LADN to another. may be forwarded from one LADN to another, which may be Including from one SMF and / or UPF to another SMF and / or UPF There are cases where this happens.

[0051] The AF also communicates with UEs, network entities and other services through service advertisements. The LADN provides a service discovery solution that enables efficient service discovery for service providers. It may also indicate the capabilities and service provisioning that can be performed. An example service is , the UE's location is near the service area of the LADN or is within the service area provided by the LADN. When the LADN detects that a particular service is available nearby, it automatically This may include a LADN that may send notifications to applications.

[0052] The NEF 703 identifies and selects a PCF (e.g., PCF 702) to AF 704 processes the request from the UE or requests related to each UE that AF 704 lists in the request. The NEF 703 processes the request and then sends an authorization request message to the PCF 702 along with the information received by the NEF 703. In addition, the NEF 703 may send a message to the requesting process (step 711). A new ID may be generated as a reference to the resource.

[0053] PCF702 will contact UDM / UDR701 to arrange subscription and postal services. The PCF 702 may obtain the license profile data (step 712). The ID and policy of 704 may include the identity of the LADN to which it may relate. UDM / UDR701 ensures that any existing associated policies configured for LADN / DN are The UDM / UDR 701 may use this information to identify whether Any policies related to the LADN / DN or target UE (e.g., information sharing, If you find the Background Data Transfer Policy and Billing Policy, 2, and the PCF 702 may return such policy profiles. You may reuse and / or modify the

[0054] PCF702 receives requests from AF704 and profiles from UDM / UDR701. Based on the registered data, a new policy may be determined (step 713). Recording and PDU session status for one LADN or for multiple LADNs The level of mobility support associated with connecting to the LADN, such as mobility across The type of information carried and the extent of information sharing within the same network slice, within one PLMN, etc. A policy for the scope of information sharing may be determined.

[0055] The type of information shared may be determined, for example, by the BDT policy configured by the LADN, or or a charging policy shared among a set of LADNs belonging to the same network operator. Another example may include policies such as registration / attachment information and and session context information.

[0056] The PCF 702 may then send an authorization response to the NEF 703 (step 714). , and the registration / session configuration response corresponds to the request for decision (step 710). The NEF 703 and the AF 704 may then be sent to the NEF 703 (step 715). The AF704 contains the policy identifier, the list of LADNs / DNs to which the policy applies, and the policy A security identifier may be provided.

[0057] PCF702 is a UDM / UDR(701) with subscription and policy plan. Update your profile to reflect new policies regarding information sharing and mobility support. The policy to be stored may be requested to be mirrored (step 716). 4 and 715. For example, PCF 702 may include: The existing BDT policy for MT traffic set by the set of LADNs , when shared / reused by a set of LADNs belonging to the same network operator The UE may request an indication that the

[0058] Steps 711, 712, 713, 714 and 716 are the components of step 710 of the AF. Note that this may be performed once for each UE specified in the request. The LADN or DN communicate directly with each other from an application layer perspective. In addition, we may share information regarding the BDT structure and schedule. The LADN communicates with other LADNs to send application and service layer messages. Use the exchange to inform the other LADN about the BDT schedule and policies. That's fine.

[0059] The LADN information described herein includes LADN service area information and LADN The LADN information may include the DNN. The AMF may be configured for different UEs that use the same LAN. may be the same regardless of other factors (e.g., UE registration area). The lack of availability means that application providers are forced to build LAs that serve more UEs. Dynamically configuring DN or providing application services to UE more efficiently This may prevent the

[0060] One solution is to provide different applications / services at different times. For this purpose, it is necessary to define flexible service areas for the LADN. For example, AMF The LADN service area is the daytime tracking area for application 1. However, changes to the entire registration area can be assigned to UEs at night. For application 2, the service area of the same LADN may be indicated to the UE. Therefore, the service area, application, and The application service ID or the specified service area is valid for A list of applications, indicating the period during which the specified service area is valid. time schedule, e.g., tracking area, registration area, cell, or geographic area Service area granularity, which may indicate the level of service area that includes the target area; and ,Some QoS parameters that may be supported within the service area, e.g., max. QoS parameters, which may indicate data rate and delay, are used to This may involve allowing more flexibility in the DN's service area.

[0061] In addition, the NWDAF may be configured to monitor, but not be limited to, the traffic load of the LADN, e.g. The amount of data being sent, the number of UEs, and the number of UEs allocated to transfer data to / from the LADN By taking into account factors including the total network resources This may help the MF and AF / AS make decisions. If the LADN becomes congested, the NWDAF contacts the SMF / AMF to resolve the congestion. To mitigate this, it is recommended to reduce the service area to reduce traffic load. The mobility statistics of the UE are based on the fact that it remains in the coverage area of the LADN and AF / AS and AF / AS who register for access to ADN and set up service areas and / or make recommendations to the AMF, collected by the NWDAF of a UE or group of UEs. may be collected.

[0062] During registration or session management related procedures, the UE may request access to the LADN. When requesting, the AMF will send the UE the service area information and their related attributes of the LADN. In addition, the network may be congested, e.g., the LADN may be congested, causing the Any associated attributes of the service area or LADN may be dynamically updated, resulting in the AM F or SMF for any change in the service area of the LADN or any of its related attributes. The UE may be notified. The UE configuration update procedure may be used for this notification. The AF or AS may also specify any parameters related to the service area. When changes need to be made, trigger network functions to initiate such actions. Good too.

[0063] FIG. 8 may be used in combination with any of the embodiments described herein. 1 shows an example procedure for moving a PDU session from a first LADN to a second LADN. 8 is a diagram of procedure 800. Each step of procedure 800 in FIG. 8 is shown and described separately. are shown, but may be performed in a different order than shown, in parallel with each other, or simultaneously with each other. Several steps may be performed. Referring to the example of FIG. 8, the UE 801 receives the AMF 802 may send a request to move the session from the first LADN to the second LADN. (Step 810). This request is sent via the PDU Session Establishment or PDU Session Modification message. The UE may also include a session message for a previously activated PDU session. session ID, the identifier of the LDPN / DN where the session needs to be activated, the session Identifier of the LADN / DN where the session last existed, whether this request is for the LADN / DN or a different The purpose is to reactivate a session that previously existed on the LADN / DN. and Q, e.g., aggregated maximum data rate, maximum delay, etc. The request may include information about the OS requirements. The AMF 802 then contacts the SMF (e.g. , SMF 803) and transmits the request to SMF 803 (step 811). Based on the availability of the PDU session, a different SMF than the one that originally established the PDU session may be selected. That's fine.

[0064] SMF803 receives subscription information and The session context may be obtained (step 812). The test may include, but is not limited to, QoS parameters, the session parameters set when the session was originally established, The periodic indication of the time interval between two active periods, the time The average length of the active period, and the status of the PDU session (e.g., active, Alternatively or additionally, SMF8 may contain information including: 03 is the number of subscribers from the UPF / NEF last used to anchor the session. The SMF803 may then obtain the subscription information and session context. Depending on the scenario, you may decide whether to use the same anchor point. In this case, the SMF 803 may first consider the service area of the LADN when making a decision. If the SMF803 is different from the SMF currently or previously providing the session , UDR / UDM804 indicates that the previous SMF is no longer serving the session A notification may be sent to the previous SMF. If the SMF providing the session is different from the SMF providing the session, the SMF contacts the SMF providing the session. The session context information is read and the session is now provided to the SMF. Session context information may indicate the current or previous session It may also include the identity of the UPF being used.

[0065] SMF803 stores some session context information, e.g., data rate, The PDU session may change if the active period length, connection to a different LADN, etc. The PCF 805 may communicate with the PCF 805 regarding policy configuration for the application (step 8). 13).

[0066] The PCF805 correlates the session ID, UE ID, and destination LADN ID. The PCF 805 may then retrieve the corresponding policy by Policies regarding data transfer through PDU sessions to the LADN (e.g., charging policies) The PCF 805 may update the policy (policy, data rate) (step 814). UDM / UDR804 and contacts that may store updated policies along with IDs A more detailed policy profile may be obtained by executing 5) SMF803 activates the PDU session and sends the request to the application that will provide the session. An anchor point is selected (step 816). The anchor point is the It can be UPF or NEF (e.g., UPF / NEF806) depending on the route. compared to the UPF / NEF selected when the session was previously activated. , different or the same UPF / NEF may be selected.

[0067] The SMF803 may update the session context information of the UDM / UDR804. (Step 817). The SMF 803 notifies the activation of the PDU session. A link point (e.g., UPF / NEF 806) may be notified (step 81 8), including, but not limited to, session ID, policy information (e.g., data rate Information including the maximum delay, maximum number of packets, and the LADN ID may be provided. ,By including session context information, AMF802, The AMF 802 may reply with an update notification (step 819). indicates that a PDU session has been activated, reactivated, or moved. If the UPF / NEF 806 is relocated, the new UP F / NEF 806 address may be provided. Compared to the procedure in Figures 3A-3B The procedure 800 for re-establishing a PDU session by sharing information is Reduces control signaling when moving from one LADN to another.

[0068] FIG. 9 may be used in combination with any of the embodiments described herein. An exemplary process initiated by the UE to configure BDT for MO traffic is shown in 9 is a diagram of procedure 900. Each step of procedure 900 in FIG. 9 is shown separately. and are listed, but in a different order than shown, parallel to each other, or In the train use case above, the network A railway operator may have one LADN installed at each station along the line. For example: The train schedules data transfer with the LADN at one station and then to the LADN at the next station. In this example, the next LADN may have a higher uplink data rate. The data rate may be higher or the train may take longer to reach the next station. You may not have the complete data to load, or the train may be at its last stop. We may upload captured security footage from the site, or Trains may schedule data transfers on a centralized data network, which This allows trains to be instructed on which LADN their data transfers should be directed to. UE (e.g., video cameras installed on trains or used by train passengers) The terminal device (which is connected to the network) initiates the configuration of the BDT procedure for MO traffic. For example, the UE may trigger the target LADN or DN to The configuration procedure may be initiated by initiating the configuration procedure for the Thus, BDT is a network of LADNs or centralized data networks (e.g., Internet Alternatively, the UE may be scheduled by a core network entity. The configuration procedure may be initiated by communicating directly with the entity.

[0069] Referring to the example of FIG. 9, a UE 901 communicates with an AMF 903 via a RAN node 902. By sending a message indicating a request for BDT for UE 901-originated traffic The procedure 900 may be initiated by (step 910). The request may include a request to pre-configure a BDT for traffic. Other types of request messages, such as registration requests, or session establishment / reactivation / modification requests. may be included in or combined with the message, including but not limited to, Information that may be included includes an indication that it is for MO traffic. , PDU sessions (R) that the UE may need to use for MO BDT. If there is an existing PDU session going from AN to UPF or AMF / NEF path PDU session identifier (ID) indicating whether there is a PDU session, The UE is currently connected to a DN / LADN that is different from the destination LADN of the requested data transfer. The ID of the DNN for the LADN / DN to which MO traffic is destined. ,e.g., cyclic data with time interval, average data size, data rate, maximum delay, and MO data traffic patterns, such as expected start times of data transfers, e.g. For example, application ID or IP describing traffic or ASP identification information 5-tuple (source address, destination address, source port number, destination port number) Application information related to the data being transferred, such as network Any existing BDT policies that may be stored in the network, and different LADNs Existing policies that may be configured for MO or MT traffic in BDT policy ID that indicates the policy, and the M O The UE may select a different LADN / DN as the destination for the BDT. Indication of flexibility for ADN / DN, if the UE is connected to a non-3GPP network an indication of whether you wish to transfer data over the network; and UE mobility patterns or predicted UE locations during background data transfers Examples include:

[0070] Upon receiving the request, the AMF 903 contacts the UDM / UDR 905 to whether UE 901 is authorized to use BDT for its MO traffic; and the destination LADN / DN, address or ASP identification information is valid for the MO BDT If the authorization is successful, the AMF 90 3 is the location of the destination LADN / DN, the location of the PDU session if one already exists Anchor point and the time of the session if the PDU session is not yet established Manage MO BDT configuration by considering the type (e.g., IP or non-IP) The AMF 903 selects an SMF (for example, SMF 904) to be used (step 912). With the information provided above regarding steps 910, 911 and 912, the selection The BDT request may be sent to the SMF (e.g., SMF 904) that has received the BDT request (step 913). Upon receiving a request from AMF 903, SMF 904 manages the BDT policy configuration. The PCF (e.g., PCF9) manages the BDT, including managing the 06) may be selected (step 914).

[0071] Factors that may be taken into consideration in selecting an appropriate PCF include, but are not limited to: However, the PCF serving the destination LADN / DN, the UE, or the network to which the UE registers PCF serving a network slice instance, if used for MO BDT The PCF manages the policies for existing PDU sessions, and The PCF that is serving the anchor point for the PDU session is different. Cases involving PCFs, e.g., a UE in a network served by one PCF Connect to a workslice and the destination LADN / DN is served by another PCF In such cases, depending on the network operator configuration and the agreement between operators, Either PCF may be selected. The selected PCF is determined by the MO BDT policy configuration. may communicate with other PCFs regarding

[0072] Alternatively, the AMF 903 selects a PCF in step 912 and For example, the UE 901 may send a request to the PCF to transmit non-IP data. and demonstrate the need for existing non-I through the AMF-NEF pathway for MO BDT. In this case, AMF903 may provide an ID for the PDU session. Step 912 selects PCF 906, and step 913 sends a BDT request to the PCF. Therefore, steps 914 and 915 may be omitted.

[0073] The SMF 904 sends a BDT request to the selected PCF (e.g., PCF 906). (Step 915). The PCF 906 communicates with the UDM / UDR 905 to contains information about whether there is an existing BDT policy configured for the destination LADN / DN. May request E901-related subscription information and policy profiles (Step 916). If the UE 901 provides the ID of an existing BDT policy, the PC F906 may include it in the message. In addition, the ID and The UDM / UDR 905 may also include the UE and LADN / DN. The BDT policy for the MT traffic may be returned (step 917). The UDM / UDR 905 may be set up for any existing B If the DT policy is configured to be shared, and if so, step 916 and step The PCF 906 may check whether it can be reused in step 917. Based on this information, the BDT policy for MO traffic may be determined. (Step 918). The PCF compares the LADN requested by the UE 901 and O A different LADN may be selected for the BDT. DT policy ID, UE ID and ID of destination LADN / DN, e.g., with time interval The periodic data, average data size, data rate and expected start time of data transfer Defined traffic patterns for MO traffic, such as between M o BDT policies may be reused (shared) by another UE or LADN / DN Indication of whether the UE wants to transfer data over a non-3GPP network In this case, the PCF may select an N3IWF and include the ID of the N3IWF), if and may contain information including the PDU session ID and type associated with the MO BDT. good.

[0074] The PCF 906 sends the MO traffic along with the policy ID as a reference to the UDM / UDR 905. The BDT policy for the traffic may be requested to be stored (step 919). The PCF 906 sends the BDT along with the policy ID and UDM / UDR ID to the SMF 904. A response may be sent (step 920), so that the SMF 904 can receive the data for transfer. Therefore, in the future, when you need to establish / activate a PDU session, you will need to The PCF 906 can read the T policy. If you select a destination LADN / DN different from the one identified by The ID of the LADN / DN may be indicated in the response message. 3 with the policy ID and UDM / UDR ID (step The AMF 903 communicates with the RAN node 902 regarding MO traffic. The AMF 903 may then return the BDT policy to the UE 901 (step 922). The RAN node 902 receives M from the UE served by the RAN to the LADN / DN. The core network may notify the presence of a BDT. may notify the UE of a UE-specific schedule of upcoming BDTs associated with the selected LADN. Given the UE traffic pattern and / or mobility pattern, the core network The network determines where the UE may start and end its MO data transfer, and For example, the UE 901 may determine the type of MO traffic at each of these locations. ADN1 is used for 5Mbps data download, and ADN2 is used for 15 minutes of video upload. The video was uploaded for 15 minutes using LDNA3 at a data rate of 10 Mbps. AMF903 also supports periodic data with time intervals, average data size, Traffic information such as data rates and expected start times for data transfers This may be done through the N2 interface. The SMF 904 forwards the MO traffic to the AF 908 residing in the destination LADN / DN. The NEF 907 may also notify the MO of the configured BDT policy. The BDT policy ID and PCF ID may be recorded (step 923). As an option, the PCF 906 may perform step 923. For example, In step 923, the LADN and AF 908 receive the arrival The user may be notified that there is a certain amount of data to be processed.

[0075] In the example of Figure 9, the PCF sends a BDT policy to the UE in response to the BDT request from the UE. The BDT policy may be sent first to the SMF and then to the AMF, and the policy for the UE at the top of the NAS message is delivered to the UE, or The PCF establishes a UE policy association, i.e., through the PCF-AMF path. AMF may send BDT policies directly. BDT policies are sent in NAS-MM messages. It may be delivered by AMF as the payload of a message.

[0076] FIG. 10 may be used in combination with any of the embodiments described herein. MO traffic initiated by the UE and configured by the DN / LADN 10 is a diagram of an exemplary procedure 1000 for BDT configuration of FIG. Although each step is shown and described separately, it may be performed in a different order than shown. , multiple steps may be performed in parallel with each other or simultaneously with each other. In this case, the request of UE 1001 configuring MO BDT is transmitted via RAN 1002 to AMF 1003 (step 1010), which then The BDT configuration procedure is started (step 1011). The DN is set by the UE1001 as the destination LADN / DN for MO traffic. Instead, the LADN / DN initiating the procedure may be, for example, , which may be overloaded and have limited bandwidth, or applications related to MO traffic. may not support the application or may not be compatible with the When MO traffic arrives based on the traffic pattern, the UE 1001 There is a possibility that you may be outside the service area, or that you may not be able to receive MO traffic due to some other condition. It may indicate to a network entity that it is not suitable to trust.

[0077] FIG. 11 may be used in combination with any of the embodiments described herein. BDT policy configuration for DN / LADN initiated MO traffic 11 is a diagram of an exemplary procedure 1100 of FIG. Although shown and described separately, they may be used in a different order than shown and in parallel with each other. Multiple steps may be performed sequentially or simultaneously with each other. For example, DN / LADN An SCS / AS may manage a group of sensors and schedule those sensors. In the example of FIG. 11, the AF 1106 may periodically report these measurements. A BDT request may be sent to the EF 1105 (step 1110). , including but not limited to, whether the request is for MO or MT traffic; If AF1106 resides in an LADN, the service area and time interval of that LADN will be included. Expected duration of cyclic data, average data size, data rate, maximum delay and data transfer traffic characteristics such as the start time of the transmission, the number of UEs, the data to be transmitted by the AF 1003, etc. It defines certain conditions for stopping BDT, such as the threshold for the amount of data and the maximum amount of data to be transferred. conditions on BDT, such as whether data is transferred via non-3GPP access; Whether background data transfer is group-based or not Next, the NEF 1105 authorizes the BDT request (step 1111), and then may send a BDT request to the PCF 1104 (step 1112 The PCF 1104 may send a BDT policy request to the UDM / UDR 1103. (Step 1113). The UDM / UDR 1103 sends the BDT policy to the PCF 1104. The PCF 1104 may then send a response (step 1114). The PCF 1104 may determine the BDT policy to be used (step 1115). The UDR 1103 may transmit the determined BDT policy regarding the MO traffic. ,The UDM / UDR 1103 determines the BDT policy for MO traffic. The RAN node 1101 may store the scheduled The BDT may be notified by the AMF 1102 (step 1117). The PCF 1104 sets up a paging policy for the BDT and 02, so that AMF1102 can At that time, the UE can be paged to connect to the network. , may be implemented for both MO and MT traffic.

[0078] The BDT may also be group-based for MT traffic. For example, , the LADN / DN may transmit MT data to a group of UEs. In Rio, MT data is broadcast to all devices within the LADN service area. In another exemplary scenario, the MT data may be transmitted to individual UEs. may be sent to a group of devices identified by a group ID instead of an ID. In both scenarios, the LADN / DN sends a BDT request to the core network. You may enter new parameters when you change the service area or group I of the LADN. D may be included in the request. Many IoT devices may overwhelm each device and require more efficient Group-based BDTs are particularly useful because they are deployed as groups for easy management. It is useful for IoT applications.

[0079] The BDT policy is set by the PCF for MO data transfers originating from a group of UEs. The AS / AF can also be set up by a group ID, e.g. BDT requests to the network by indicating the external group ID or internal group ID. Therefore, once the PC Once F decides on the BDT policy, PCF may send the policy to AMF, and the A The MF may be delivered to each individual UE in the group. If the UE is not connected or the AMF is not connected to the UE, the AMF communicates with the UDR / UDM. The UE may then contact the UE to retrieve the UE content including the UE ID based on the group ID. ,As a result, the BDT policy can be transmitted to the target UEs in the group.

[0080] It is found that multiple UEs in a group are served by one RAN node. If so, the AMF may send one N2 message to the RAN node. In the message, the AMF indicates the individual UE ID and / or the group ID. It may be up to the RAN node how to send the policy to individual UEs. However, the PCF sends a single message to the AMF with the BDT policy indicating only the group ID. A large number of UEs transmit data or control messages to the network at the same time. To avoid this situation, there is a back-off timer associated with the policy. This will be explained in.

[0081] Table 3 below shows the background data transfer policy sent by the network to the UE. This section provides a list of parameters that may be relevant to the policy.

[0082] [Table 3]

[0083] In one example, background data transfer policies are defined by the URSP framework. UE Route Selection Policy, which may be managed and distributed cy:URSP).

[0084] The AF shall provide the NEF with a BDT policy for a UE or group of UEs, as prepared by the AF. A BDT request may be sent indicating that the data size, area / location and Besides indicating the BDT details, such as the time window and the policy, the request also specifies the policy that the UE This indication may be used for initiation communication. In this specification, this may be referred to as MO-BDT policy indication. F may then forward this request to the PCF, which may then construct a policy. triggers the immediate transmission of the policy to the UE (via AMF and NAS signaling). As a guideline, MO-BDT policy indications may be used or PC F is the number of times that a UE (or group of UEs) can request a Subscribe to AMF for notifications when entering an indicated location or geographic area. When the notification is received from the AMF, the PCF notifies the UE (AMF and NAS system) The policy may be transmitted via a signaling.

[0085] When the UE receives the BDT forwarding policy, the content of the policy determines which of the following actions it should take: One or more of these may be implemented by the UE.

[0086] 1) Policy activation decision: The policy activation decision is made by the BDT policy. the UE detects that it has entered the location or geographic area indicated in the received policy When the UE detects that the DNN indicated in the policy is available, When the UE successfully establishes a PDU session with the DNN indicated in the policy, When the time window indicated in the policy is reached or when the filters listed in the policy are Event when the UE detects traffic matching the 5-tuple information. It may be triggered by any combination of the following: The UE activates the policy. When deciding to activate a policy, an offset may delay the policy activation. The offset may be indicated in the policy or may be determined by the random generator and / or was based on a part of the UE identifier, such as the SUPI or 5G-S-TMSI of the UE. The time window may also be shifted by an offset.

[0087] 2) Policy Activation Request: When the UE decides to activate a policy, , it may take one of the following steps:

[0088] Sending a registration update request to request connection to a new network slice. , which may include the S-NSSAI provided within the policy.

[0089] Sending a PDU session establishment request that may include the DNN provided in the policy. The DU session establishment request also includes a policy reference that identifies the policy received from the PCF. The policy reference ID may contain a policy ID (or policy ID) from the PCF. It is used by SMF to read the policy and apply it to the PDU session. This may be the case.

[0090] Sending a PDU session update request or service request. The UE S-NSSAI, DNN, ASP Identifier, 5-Tuple and / or PDU Session ID Based on the session ID, the PDU session associated with the PDU session update request or service request is identified. A PDU session update request or service request may also It may also contain a policy reference ID that identifies the policy received by the PCF. The policy reference ID retrieves the policy from the PCF and assigns it to the PDU session. May be used by SMFs that apply

[0091] 3) Policy Activation Notification: Once the policy is activated, the UE Sends a notification to the E application to let the UE application know that the policy is active The notification may include a time window, amount of data, and 5-Tu ple, application ID, ASP ID, and the BDT policy activated The UE may also include locations where the BDT may become inactive. When (outside the time window, data volume exceeded, out of the specified location, PDU session to DDN The UE may send a notification to the UE application to inform it that the Alternatively, the UE may decide to use the policy before activating it with the network. The UE may inform the application about the availability of the This may be done to ensure that the application requires the use of the policy. Alternatively, the UE may decide to allow the UE application to perform traffic pattern defined by the policy. The UE application will not be able to send traffic until it generates traffic that matches the specified pattern (e.g., filter). In some cases, the policy information is not provided to the UE via AT commands. It may be provided to the application.

[0092] 4) Deactivate Policy: The UE deactivates the area specified in the policy. Detects that the UE has transmitted more data than specified in the policy. Detect the expiration of a time window specified in the policy. Detects that policy-defined traffic has been sent after the specified timeout. (timeouts may be dictated by policy) or by a clear application When an application layer request is received, it may decide to deactivate the policy. Deactivating a policy will result in a PDU session modification, PDU session release message. This message involves sending a Registration Update message that deletes the S-NSSAI specified in the policy. The policy may be what triggers the release of the PDU session (timeout, trigger This may indicate a problem (such as being outside a time window, matching or exceeding data volume, etc.).

[0093] The UE may not be able to use the BD even after the policy has been determined by the PCF and sent to the UE. This may require realigning the policy with the network. Possible scenarios As an alternative, the UE may anticipate some changes to the pre-planned data transfer, e.g. For example, when the UE needs to change the start and / or end time of data transmission, the U E is the transfer of more data in the PDU session set by the BDT policy, or when a higher data rate is required or the UE has additional application data. When a data flow needs to be added to the BDT, the configured BDT To reconcile (i.e., update) its policy with the network, the UE performs a registration update procedure. procedure, service request procedure, or PDU session establishment / modification procedure In particular, the UE may determine the basis for the update and the BDT policy. A reference ID or BDT policy may be used to indicate the parameters that should be modified relative to the You may need to identify the BDT policy by providing an ID. The parameters to be calculated may include any of the parameters listed in Table 3.

[0094] Network features such as AF or PCF also allow future background data transfers. Changes in the service area of an LADN or DN that may affect an AS or A Future background data transfers where F requires a change to the BDT policy configuration Change in traffic characteristics, UE is not reachable in the area specified by the BDT policy or due to the network detecting that the device has moved out of range. This may require updating the BDT policy stored in the UE. This may be done with the support of the NWDAF within the network. Upon detecting this, it contacts the PCF to indicate the BDT policy and the associated UE. The network function may trigger the UE configuration update procedure. Use the database to provide the reference ID or BDT policy ID, the rationale for the update, and the BDT policy. Update the BDT policy by indicating the parameters that should be changed that are relevant to the policy. Good too.

[0095] FIG. 12 may be used in combination with any of the embodiments described herein. UE-initiated configuration of BDT policy for MO traffic in LTE EPC FIG. 12 is a diagram of an exemplary procedure 1200. Although each step is shown and described separately, it may be performed in a different order than shown. , multiple steps may be performed in parallel with each other or simultaneously with each other. In this example, the UE 1201 transmits MO background data to the MME 1202 via the NAS. The MME 1202 may send a forwarding request (step 1210) and the SCEF 1205 to the SCS / AS 1206 (step 121 1). The UE 1201 is described in any of the procedures described herein. The SCS / AS 1206 may include the same information in the BDT request as in the By indicating that it is for MO traffic with D, it includes resource management. The SCEF 12 may initiate a procedure for BDT configuration (step 1212). 05 is set in the MME 1202 by the PCRF 1204 and recorded in the SPR 1203. A BDT response may be sent along with the stored policy ID (step 1213). The MME 1202 transmits the BDT policy ID to the UE 1201 together with the policy ID for the MO BDT. A response may be sent (step 1214).

[0096] FIG. 13 illustrates an exemplary user interface for configuring background data transfer in a 5G network. 13 is a diagram of an interface 1300. The user interface is E), used by service providers (SCS / AS) and network operators As shown in the example in Figure 13, the 5G network interface The BDT configuration in 1301 is performed by the end device (UE), the service provider (SCS / A S) and / or network operator configuration 1302, and end devices (UE), Service Provider (SCS / AS) and / or Network Operator 13. A BDT setup 1303 corresponding to the above may be enabled.

[0097] FIG. 14 is a diagram illustrating an example of a UE connected to an inventory management system 1400. In the example of FIG. 4, the UE platform 1401 communicates with the 5GC 140 via the RAN 1402. 3 to access the enterprise inventory management system 1404. Some applications may include It only works when the hosting device (UE) is within the LADN service area. For example, it may only be activated when the UE is in a warehouse (as shown in the example in Figure 14). This may be desirable for warehouse inventory tracking and management applications (such as those used in In other words, for security reasons, warehouse owners may want their employees to observe and manage their inventory from home. Sometimes we don't want to be able to understand.

[0098] When the UE is outside the coverage area of the LADN, the UE has IP connectivity. However, it does not have connectivity to the enterprise inventory management system 1404. Therefore, these applications can be used regardless of whether the UE is inside or outside the LADN. The application may be aware of the UE's location, allowing it to know if the UE is not in the LADN. If the action is not successful, the action should not be attempted.

[0099] Provides finer granularity of access to the LADN from a service / application perspective. To provide this, 5GC1403 is based on the different services provided by LADN. The LADN may implement authorization procedures for some services / applications. It is anticipated that this will assist 5GC1403 by providing application information. One way is to define different service areas for different services provided by the LADN. 5GC1403 (e.g., PCF) is a service area and service In practice, the coverage area may be determined by the traffic load, and may vary depending on other factors such as mobility patterns.

[0100] In such a scenario, when the UE leaves the coverage area of the LADN, Your application session with the enterprise inventory management system 1404 may be interrupted. 5GC1403 specifies that the SMF is When the UE's user plane connection may be deactivated and when the SMF When the UE is notified that it has returned to the area, the SMF will establish a user plane connection for the UE. If you want to support this type of scenario, you can do so by indicating whether you want to reactivate the There are cases where the inventory management application is exposed by the UE platform 1401. The API used by the application is to determine whether the UE's user plane connection is left at the UE's location. The right may be considered.

[0101] When the inventory control application starts, it establishes a user plane connection for the UE. For example, the API call may use UDP or TCP or may be a request along with the IP address of the enterprise management system. The API call returns the LADN name and an indication that the LADN is the LADN name. In response to the API call, the UE platform may send the P A DU may send a session establishment message. The message is The message may indicate a "start request" and may be N may contain a new indication that the LADN name. The indication that it is a DN name may be used by the network, As a result, if the name is not recognized in the network, the DDN name is used by the more general The network knows that it will not replace the DDN. Instead, the network If you do not identify the provided DDN / LADN, the network will assume that the LADN / DDN name is with a cause value indicating not identified, not reachable, or not allowed. The GUI will notify you if the application is connected to the enterprise system. A message indicating whether

[0102] FIG. 15 may be used in combination with any of the embodiments described herein. 1 is a diagram of an example of establishing a connection to the UE platform 1500. 01 displays a message indicating whether the application is connected to a corporate system. It may include a graphical user interface (GUI) 1502 that displays the The inventory management application 1503 sends a request to the UE modem 1504 to establish a connection (LA DN indication) from the UE modem 1504 to receive a rejection or a message The PDU session establishment message is The DDN field may already contain a DN field. It may be used to provide a DN.

[0103] LADN information, including tracking areas that may reach the LADN, is stored in the registration process. When provided by the AMF to the UE during a procedure or UE configuration update procedure The UE detects that it is leaving an area where it can reach the LADN. When the UE platform receives the inventory control application, the user plane connection The UE may send a notification indicating that it has been suspended. Detects that the device has left a LDDN area when it determines that it has entered a non-LDDN tracking area. The user interface of the inventory management application may be displayed on the handset screen as follows: "goodbye" message indicating that the enterprise management system is not reachable from the current location If the UE is unable to reach the LADN, it may display the "If When the UE platform detects that the vehicle has re-entered a potentially dangerous area, it automatically triggers the inventory management app. The UE may send a notification to the application indicating that the user plane connection has been re-established. The inventory management application user interface displays the company's inventory at its current location on the handset screen. "Welcome back" to indicate that the business management system is reachable A message may be displayed.

[0104] When the UE re-enters the LADN area, it transfers the UE's PDU session to the network. Therefore, the UE may not know whether the The PDU session is displayed with a request type indicating "Existing PDU Session" and the PDU session ID. Additionally, the request may send a session establishment message if the request is for the same access ( i.e., to reactivate a session (3GPP or non-3GPP) The AMF may include an indication that the PDU session is still established. or a new PDU session is established in place of the previous one. The UE may reply with an indication of whether the The UE is provided with the same or a new PDU session ID for A UE may determine that it has entered a tracking area that is part of a LADN. When disconnecting from the UE, it may detect that it has entered an LADN area. When the user re-enters an area where the device may be in danger, the data is sent to the inventory management application. Instead, the notification set up in the UE will re-establish the PDU session with the LADN. may be transmitted after

[0105] FIG. 16 may be used in combination with any of the embodiments described herein. 16 is a diagram of an area notification via a GUI 1600. The UE platform 1601 , the inventory control application 1604 may send an out-of-area LADN message. and through a graphical user interface (GUI) 1602, the enterprise system is not reachable (for example, a "good bye" message) The UE modem 1605 may display a current Inventory management application 1604, within the LADN area or a connection re-establishment message is sent. may be transmitted via a graphical user interface (GUI) 1603 , a message indicating that the enterprise system is now reachable (e.g., "welcome back" message may be displayed.

[0106] There may also be a service layer that runs only on the LDAP. The application may be a service layer hosted on the UE. In oneM2M terminology, this This may be called an ASN-CSE or an ADN-AE. .

[0107] The above-mentioned enterprise inventory management system is a service layer hosted on a cloud server. In oneM2M terminology, this may be IN-CSE.

[0108] The ASN-CSE of the UE may perform the registration procedure together with the IN-CSE. IN-CSE can only be registered if the ASN-CSE is located in a certain geographic area. The ASN-CSE may provide an indication that the ASN-CSE has access to the Additionally, the IN-CSE may provide geographic region details to the ASN-CSE. Physical domain details include, but are not limited to, GPS coordinates, longitude, latitude, address, traffic Examples include tracking area and tracking area list.

[0109] ASN-CSE may hold location attributes or resources. E is an application that has registered its location attributes or resources with ASN-CSE. (e.g., an application hosted on the UE) to be able to see The ASN-CSE may provide geographic information to indicate when the IN-CSE is reachable. , may be made visible to registered applications. held by ASN-CSE and means IN-CSE <remotecse>Riso It may be part of a service.

[0110] Applications registered in the ASN-CSE are those that the UE can reach in the IN-CSE. Notification from ASN-CSE when leaving or entering a geographic area where You may subscribe to receive the

[0111] As mentioned above, the ASN-CSE is responsible for the UE's re-entry into the LADN area. may receive notification from the modem platform. Additionally, the ASN-CSE contains an attribute that indicates whether there is an active connection to the IN-CSE or not. The updated attributes or resources may be updated in the ASN-CSE. Related to (in oneM2M terms, <csebase>Resources), IN-CSE Related to (in oneM2M terms, <remotecse>resource) or or related to each application registered in ASN-CSE (oneM2M In terms of <ae>ASN-CSE registered application may be An application can subscribe to the state changes of the corresponding attribute or resource. ,Whether the UE is in the LADN or whether the IN-CSE is reachable. Applications may subscribe to receive notifications. Upon receiving the IN-CSE, the IN-CSE is not reachable and / or the UE is outside the LADN. If so, the application may either discontinue the activity or (if If the UE is reachable and / or is within the LADN, resume its activity. It may start.

[0112] In addition, an ASN-CSE may register multiple IN-CSEs together, but each IN- The CSE is responsible for a different service layer and has its own LADN. Therefore, the ASN-CSE may have multiple IN-CSEs associated with different LADNs. <rem The application on the UE may hold the LADN (i.e. It may be specific to a particular IN-CSE) and the UE may be and be notified when leaving or re-entering an area where IN-CSE is reachable. To believe, to respond <remotecse>You may subscribe to.

[0113] 3rd Generation Partnership Project: 3GPP) is a group of companies that develop and operate radio access, core transport networks, and service capabilities ( cellular technology, including those affecting coding / decoding, security, and quality of service - Developing technical standards for telecommunications network technology. The technology (RAT) standards are WCDMA (commonly referred to as 3G), LTE ( Commonly referred to as 4G), LTE-Advanced standard, and the new 3GPP NR standard development continues and is the next generation of radio access technology. It is expected that the new RAT will include provisions for new frequencies below 7 GHz. Flexible wireless access provisions and new ultra-mobile broadband above 7GHz It is envisaged that this will include provisions for broadband wireless access. The new non-backward compatible wireless access will be in new frequency bands below 7GHz. It is assumed that the access will consist of multiplexed signals in the same frequency band. Different behaviors may address a broad set of 3GPP NR use cases with different requirements. Ultra mobile broadband is expected to include indoor and outdoor modes of operation. Providing ultra-mobile broadband access opportunities for roads and hotspots It is envisaged that this will include the centimeter-wave and millimeter-wave frequency bands, which are used for radio wave applications. Ultra Mobile Broadband with mmWave and mmWave specific design optimizations below 7GHz It is envisioned to share a common design framework with flexible wireless access. .

[0114] 3GPP has established various user experience requirements for data rate, latency, and mobility. It identifies various use cases that NR is expected to support. The cases are divided into general categories: enhanced mobile broadband (eMBB); Ultra-reliable and low-latency communication (URLLC), large-scale machine-type communication (mMTC), network Network operations (e.g., network slicing, routing, migration) and interworking, energy conservation), and vehicle-to-vehicle Vehicle-to-Vehicle (V2V) and Vehicle-to-Infrastructure (Ve Vehicle-To-Infrastructure (V2I), Vehicle-to-Network Communication (Vehicle-To- Network (V2N), Vehicle-to-Pedestrian (V2N) 2P), and vehicle communications with other entities. Enhanced Vehicle-To-Everything (eV2X) Specific services and applications in these categories include, for example: For example, monitoring and sensor networks, remote device control, and interactive Remote control, personal cloud computing, video streaming, wireless cloud Road-based office, emergency responder connectivity, car e-call, disaster warning, real-time Time game, multi-person video call, autonomous driving, augmented reality, tactile internet, Birch This includes virtual reality, home automation, robotics and aerial drones. All of these use cases and others are contemplated herein.

[0115] FIG. 17A illustrates a method and apparatus for implementing the method and apparatus described and claimed herein. 1 illustrates an example of a communication system 100. The communication system 100 may generally or collectively be referred to as Wireless Transmit / Receive Unit (WTRU) 102 may refer to one or more WTRUs 102. Transmit / Receive Unit:WTRU)102a, 102b, 102c, 102d, 102 The communication system 100 may include wireless access points 102e, 102f, and / or 102g. Access Network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, Core Network 106 / 107 / 109, Public Switched Telephone Network One Network (PSTN) 108, Internet 110, Other Networks 112 and network services 113. The network services 113 may include: For example, V2X server, V2X function, ProSe server, ProSe function, IoT service may include services, video streaming and / or edge computing .

[0116] The concepts disclosed herein may be implemented in any number of WTRUs, base stations, networks, and / or It will be appreciated that the WTRU 102 may be used with any other network element. Each of the In the example of FIG. 17A, each of the WTRUs 102 may be a hardware 17A to 17E as a handheld wireless communication device. In various use cases, each WTRU may be, by way of example only, a user equipment (UE), Mobile stations, fixed or mobile subscriber units, pagers, cellular phones, mobile Personal Digital Assistants (PDAs), smartphones, and laptops , tablets, netbooks, notebook computers, personal computers, Linear sensors, consumer electronics, wearables such as smart watches or smart clothing devices, medical or e-health devices, robots, industrial equipment, drones, e.g., cars, any vehicle that transmits and / or receives radio signals, including vehicles such as buses, trucks, trains, or airplanes. any type of equipment or device that is configured to receive It will be understood that these may include:

[0117] The communications system 100 may also include a base station 114a and a base station 114b. In the example of FIG. 17A, each base station 114a and base station 114b is shown as a single element. In practice, base stations 114a and 114b may be any number of interconnected base stations and The base station 114a may include a WTRU 102 and / or a network element. a, 102b and 102c; Core Network 106 / 107 / 109, Internet 110, Network Services 113, and / or other networks 112. The device may be any type of device configured to facilitate access to a network. Similarly, base station 114b is connected to Remote Radio Head (RRH) 11 8a, 118b, Transmit / Receive Points (TRP) 119a, 119b and / or Load S At least one of the Roadside Units (RSUs) 120a and 120b and interfaces with the core network 106 / 10 7 / 109, the Internet 110, other networks 112, and / or Facilitating access to one or more communications networks, such as network services 113 The RRHs 118a, 118b may be any type of device configured to The WTRU 102 may wirelessly interface with at least one of the WTRUs 102, e.g., the WTRU 102c. -face, core network 106 / 107 / 109, Internet 110, network services 113, and / or other networks 112, Any type of device configured to facilitate access to one or more communication networks. It may also be a vise.

[0118] The TRPs 119a and 119b communicate wirelessly with at least one of the WTRUs 102d. The interface is the core network 106 / 107 / 109 and the Internet 110. , network services 113, and / or other networks 112, etc. or any type of device configured to facilitate access to multiple communications networks The RSUs 120a and 120b may be WTRUs 102e or 102b. 02f and wirelessly interfaces with at least one of the core networks 10 6 / 107 / 109, Internet 110, Other Networks 112, and / or access to one or more communications networks, such as a network service 113; The device may be any type of device configured to facilitate 114a and 114b are base transceiver stations (BTS), de-B, eNode B, Home NodeB, Home eNodeB, Next Generation Node- B (gNode B), satellite, site controller, access point :AP), a wireless router, etc.

[0119] The base station 114a may be part of the RAN 103 / 104 / 105. AN also includes a Base Station Controller (BSC), a wireless network Radio Network Controller (RNC), relay nodes, and other It may also include base stations and / or network elements (not shown). 4b may be part of RAN103b / 104b / 105b, and those RANs are , other base stations and / or network elements such as BSCs, RNCs, relay nodes, etc. (as shown A base station 114a may include a particular geographic area, sometimes called a cell. (not shown) may be configured to transmit and / or receive wireless signals within the Similarly, base station 114b may operate within a particular geographic area (not shown), sometimes referred to as a cell. may be configured to transmit and / or receive wired and / or wireless signals The cell may be further divided into cell sectors. For example, the cell sectors associated with base station 114a A cell attached to a base station may be divided into three sectors. Base station 114a may include three transceivers, one for each sector of the cell. For example, a uses Multiple-Input Multiple Output (MIMO) technology. Therefore, multiple transceivers may be used per sector of a cell. .

[0120] The base station 114a may be connected to any suitable wireless communication link (e.g., Radio Frequency :RF), microwave, infrared (IR), ultraviolet (UV), air interface 115 / 116 / , which may be optical, centimeter wave, millimeter wave, etc. One or more of WTRUs 102a, 102b, 102c, and 102g through 117 The air interface 115 / 116 / 117 may communicate with any It may be established using any suitable radio access technology (RAT).

[0121] The base station 114b may be connected via any suitable wired (e.g., cable, fiber optic, etc.) or Wireless communication links (e.g., RF, microwave, IR, UV, visible light, centimeter wave, millimeter wave, etc.) may be wired or air interface 115b / 116b / 117b Through RRH118a and 118b, TRP119a and 119b and / or It may communicate with one or more of the RSUs 120a, 120b. The interfaces 115b / 116b / 117b may be established using any suitable RAT. .

[0122] RRH118a, 118b, TRP119a, 119b, and / or RSU120a , 120b, may be any suitable wireless communication link (e.g., RF, microwave, IR, UV , visible light, centimeter wave, millimeter wave, etc.), air interface 115c / WTRU102c, 102d, 102e, 102f through 116c / 117c It may communicate with one or more air interfaces 115c / 116c / 11 7c may be established using any suitable RAT.

[0123] The WTRU 102 may communicate with any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, centimeter-wave, millimeter-wave, etc.) communicate with each other through a direct air interface 115d / 116d / 117d. The air interface 115d / 116d / 117d may be configured to support any suitable RAT. may be established using

[0124] The communication system 100 may be a multiple access system and may be any of a variety of access modes, including CDMA, TDMA, and the like. One or more channel accesses such as DMA, FDMA, OFDMA, SC-FDMA For example, base station 1 in RAN 103 / 104 / 105 may adopt a 14a and WTRUs 102a, 102b, and 102c, or RANs 103b / 104 RRH118a, 118b, TRP119a, 119b and / or RSUs 120a and 120b and WTRUs 102c, 102d, 102e, and 102f is a Universal Mobile Telecommunications System (UMTS) s System:UMTS), Universal Terrestrial Radio Access (UTRA) Wireless technologies such as UTRA may be implemented, thereby 115 / 116 / 117 and / or WCDMA (multi-hop multiple access point / air- interfaces 115 / 116 / 117 and / or WCDMA) WCDMA can be established in high speed or 115c / 116c / 117c. High-Speed Packet Access (HSPA) and / or evolved H It may also include communication protocols such as SPA (Evolved HSPA: HSPA+). High-Speed Downlink Packet Access (HSD PA) and / or High-Speed Uplink Packet Access It may also include HSUPA (Hardware Access).

[0125] For example, the base station 114a and the WTRU 102a, 104a, and 105 in the RAN 103 / 104 / 105 2b, 102c and 102g, or within RAN 103b / 104b / 105b RRH118a and 118b, TRP119a and 119b, and / or RSU1 20a and 120b and WTRUs 102c and 102d are Evolved UMTS Terrestrial Radio Access Evolved UMTS Terrestrial Radio Access (E-UTRA) and other wireless technologies may be implemented to support Long Term Evolution (LTE) and / or L Using LTE-Advanced (LTE-A), air interface 1 15 / 116 / 117 or 115c / 116c / 117c can be established respectively. Air interface 115 / 116 / 117 or 115c / 116c / 117 c may implement 3GPP NR technology. LTE and LTE-A technologies ( LTE D2D and / or V2X technologies and interfaces (e.g., sidelink communications) Similarly, 3GPP NR technology may include N-channel (e.g., sidelink) R May include V2X technology and interfaces.

[0126] A base station 114a and WTRUs 102a, 102b, and 102c and 102g, or RRH in RAN 103b / 104b / 105b 118a and 118b, TRP119a and 119b and / or RSU120a and 120b and WTRUs 102c, 102d, 102e, and 102f are IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Worldwide Interoperability For Microwave Access (WiMA) X)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-2000) -95), Interim Standard 856 (IS-856), Global System for Mobile Communications (Glob Global System For Mobile Communications (GSM), GSM evolution high data rate (Enhanced Data Rates For GSM Evolution:EDGE), GSM EDGE(GE The wireless technology may be implemented using a wireless LAN.

[0127] The base station 114c in FIG. 17A includes a wireless router, a home NodeB, a home eNodeB, Or it may be an access point, for example, a business, a house, a vehicle, a train, an antenna, Facilitate wireless connectivity within localized areas such as satellites, manufacturing plants, campuses, and other locations Any suitable RAT may be utilized for the purpose of communication between the base station 114c and the WTRU 102. For example, the WTRU 102e is a wireless device that implements wireless technology such as IEEE802.11. Establish a local area network (Wireless Local Area Network: WLAN) Similarly, the base station 114c and the WTRU 102, e.g., the WTRU 102d, may Implementing wireless technologies such as IEEE 802.15 to establish a wireless personal area network (Wi A wireless personal area network (WPAN) may be established between the base station 114c and the WPAN. The TRU 102, e.g., the WTRU 102e, is a cellular-based RAT (e.g., a WCDMA-based RAT). DMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) As shown in FIG. 17A, the base station 114c may establish a cell or a femtocell. may have a direct connection to the Internet 110. Thus, the base station 114c , accessing the Internet 110 via the core network 106 / 107 / 109. There may be cases where this is not necessary.

[0128] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b , may communicate with the core network 106 / 107 / 109, The network includes voice, data, messaging, authorization and authentication, applications, and / or or Voice Over Internet Protocol (VoIP) configured to provide IP (Internet Protocol) services to one or more of the WTRUs 102. It may be any type of network, for example, the core network 106 / 107 / 109 provides call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, packet data network connectivity, Provides Ethernet connectivity, video streaming, etc. and / or allows users High level security features such as authentication may be implemented.

[0129] Although not shown in FIG. 17A, RAN103 / 104 / 105 and / or RA N103b / 104b / 105b and / or Core Network 106 / 107 / 10 9 is RAN103 / 104 / 105 and / or RAN103b / 104b / 105 b) may communicate directly or indirectly with other RANs employing the same or different RATs. For example, it will be understood that RAN10, which may utilize E-UTRA radio technology, 3 / 104 / 105 and / or RAN103b / 104b / 105b In addition, the core network 106 / 107 / 109 may also use GSM or NR radio technology. The RAN may communicate with another RAN (not shown) employing the same.

[0130] The core network 106 / 107 / 109 also allows the WTRU 102 to connect to the PSTN 108, To access the Internet 110 and / or other networks 112 The PSTN 108 provides the Plain Telephone Service. including the circuit-switched telephone network providing Old Telephone Service (POTS) The Internet 110 may be implemented using the Transmission Control Protocol (TCP). TCP, User Datagram Protocol (UDP) , and the Internet Protocols in the TCP / IP Internet Protocol Suite ( Interconnected computers that use common communication protocols such as Internet Protocol (IP). This may include computer networks and global systems of devices. Network 112 may be owned and / or operated by other service providers, The network 112 may include a wired or wireless communication network. For example, the network 112 may include any Any type of packet data network (e.g., IEEE 802.3 Ethernet network) Network) or RAN103 / 104 / 105 and / or RAN103b One or more that may employ the same RAT as / 104b / 105b or a different RAT It may include another core network that is connected to multiple RANs.

[0131] Within the communication system 100, WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g, 102h, 102m ... 2b, 102c, 102d, 102e, and some or all of 102f, e.g., WTR U102a, 102b, 102c, 102d, 102e and 102f are different wireless It may contain multiple transceivers that communicate with different wireless networks over the same link. For example, the WTRU 102g shown in FIG. 17A may employ cellular-based wireless technology. and base station 114c, which may employ IEEE 802.11a wireless technology. may be configured to communicate with

[0132] Although not shown in FIG. 17A, the user terminal may make a wired connection to the gateway. It is understood that the gateway is a residential gateway. l Gateway (RG). RG is a network Many of the ideas contained herein may be used in conjunction with WT This applies equally to UEs that are RUs and UEs that use a wired connection to the network. For example, the wireless interfaces 115, 116, and 117 may be used. The idea applies to 17 and 115c / 116c / 117c, which are similarly connected to wired connections. It is okay to do so.

[0133] FIG. 17B is a system diagram of an example of the RAN 103 and core network 106. As mentioned above, the RAN 103 employs UTRA radio technology to provide the air interface 11 RAN1 may communicate with WTRUs 102a, 102b, and 102c through RAN1. 03 may also communicate with the core network 106. As shown in FIG. 17B, the RAN 103 communicates with WTRUs 102a, 102b and 102c over air interface 115. Nodes 2c, each of which may include one or more transceivers for communicating with Node-B 140a, 140b, and 140c. 0b and 140c are each associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a and 142b. 03 includes any number of Node-Bs and Radio Network Controllers (RNCs) It will be understood that there is.

[0134] As shown in FIG. 17B, Node-Bs 140a and 140b communicate with an RNC 142a. In addition, Node-B 140c may communicate with RNC 142b. Node-B 140a, 140b and 140c communicate via Iub interfaces. , may communicate with corresponding RNCs 142a and 142b. RNC 142a and 2b may communicate with each other via the Iur interface. Each of the Node-Bs 140a, 140b and 142b is connected to a respective Node-B 140a, 140b and 142b. In addition, the RNCs 142a, 142b may be configured to control the RNCs 142a, 142b. These are outer loop power control, load control, admission control, packet scheduling, Other features such as handover control, macro diversity, security functions, and data encryption are also available. The device may be configured to perform or support a function.

[0135] The core network 106 shown in FIG. 17B includes a media gateway. ay (MGW) 144, Mobile Switching Center (MSC) 146, Serving GPRS Support Node (SGSN) 148 , and / or Gateway GPRS Support Node Each of the above elements may include a core network 10 Although represented as part of 6, any one of these elements may be part of the core network. may be owned and / or operated by entities other than the Operator. Let it be understood.

[0136] RNC 142a in RAN 103 communicates with the core network via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may WTRU 102a, WTRU 102c, and WTRU 102d provide access to a circuit-switched network such as the PSTN 108. Communications between 102b and 102c and conventional terrestrial communications devices may be facilitated.

[0137] RNC 142a in RAN 103 also communicates with the core network via the IuPS interface. The SGSN 148 may be connected to the GGSN 1 50. The SGSN 148 and the GGSN 150 may be connected to the WTRU 102a, 02b and 102c provide access to packet-switched networks such as the Internet 110. provides access between the WTRUs 102a, 102b, and 102c and IP-enabled devices. It may facilitate communication between

[0138] The core network 106 may also be owned and / or operated by other service providers. Other networks 11 which may include other wired or wireless networks operated 2.

[0139] FIG. 17C is a system diagram of an example of the RAN 104 and core network 107. As mentioned above, the RAN 104 employs E-UTRA radio technology and provides an air interface 116 with the WTRUs 102a, 102b, and 102c. 4 may also be in communication with the core network 107.

[0140] The RAN 104 may include eNodeBs 160a, 160b, and 160c. , it will be appreciated that the RAN 104 may include any number of eNodeBs. The eNodeBs 160a, 160b and 160c each have an air interface 11 6 to communicate with the WTRUs 102a, 102b, and 102c. For example, eNode-Bs 160a, 160b and 160c may be provided. The eNode-B 160c may implement MIMO technology. For example, transmitting wireless signals to the WTRU 102a and receiving wireless signals from the WTRU 102a. To achieve this, multiple antennas may be used.

[0141] Each of the eNode-Bs 160a, 160b, and 160c is connected to a particular cell (not shown). and radio resource management decisions, handover decisions, uplink and / or configured to handle downlink user scheduling, etc. As shown in FIG. 17C, eNodeBs 160a, 160b, and 160c , may communicate with each other through the X2 interface.

[0142] The core network 107 shown in FIG. 17C includes a mobility management gateway (Mobili Management Gateway (MME) 162, Serving Gateway 164, and Packet Data Network (PDN) Gateway 166 Each of the above elements may be represented as part of the core network 107. However, any one of these elements may be owned by an entity other than the core network operator. It is understood that the information contained herein may be owned and / or operated by entities other than the Company.

[0143] The MME 162 communicates with the eNode-B 1 in the RAN 104 via the S1 interface. 60a, 160b and 160c, and function as control nodes. For example, the MME 162 may Authenticating the user, bearer activation / deactivation, WTRU 102a, 102 b and 102c, selecting a specific serving gateway during the initial connection. The MME 162 may also be responsible for communicating with the RAN 104 and other mobile networks, such as GSM or WCDMA. A control program is required to switch between other RANs (not shown) employing other radio technologies. A lane function may be provided.

[0144] The serving gateway 164 communicates with the RAN 104 via the S1 interface. The service may be connected to each of the eNode-Bs 160a, 160b, and 160c. The gateway 164 generally provides a Routing and routing user data packets from TRUs 102a, 102b, and 102c The serving gateway 164 may also forward the inter-eNodeB handover request. The user plane anchor between the WTRUs 102a, 102b and 102c, and downlink data is Triggering paging when available to the WTRUs 102a, 102b and 102c may perform other functions such as managing and storing the context.

[0145] The serving gateway 164 also notifies the WTRUs 102a, 102b, and 102c provides access to packet-switched networks such as the Internet 110, and 02a, 102b, 102c and IP-enabled devices. It may be connected to a DN gateway 166.

[0146] The core network 107 may facilitate communication with other networks. The PSTN 107 provides the WTRUs 102a, 102b, and 102c with 8, and the WTRUs 102a, 102b, and 102c For example, the core network 1 may facilitate communication between the 07 acts as an interface between the core network 107 and the PSTN 108 IP gateways (e.g., IP Multimedia Subsystems) It may contain or communicate with a core network (IMS) server. The network 107 provides the WTRUs 102a, 102b, and 102c with the services of other service providers. (b) any other wired or wireless network owned and / or operated by the Company; may provide access to a network 112.

[0147] FIG. 17D is a system diagram of an example of the RAN 105 and core network 109. The RAN 105 employs NR radio technology and communicates with the WTRU 1 over the air interface 117. RAN 105 may also communicate with Core Network 102a and 102b. 09. Non-3GPP Interworking Function Function: N3IWF)199 uses non-3GPP wireless technology to The N3IWF 199 may also communicate with the WTRU 102c through the core network 198. The network 109 may also be in communication with the network 109.

[0148] The RAN 105 may include gNode-Bs 180a and 180b. It will be appreciated that 5 may include any number of gNode-Bs. 180a and 180b each communicate with the WTRU 10 over the air interface 117. 2a and 102b. When integrated access and backhaul connectivity is used, the same air interface , a WTRU and a core network 109 via one or more gNBs. The gNode-Bs 180a and 180b may be used between the gNode-Bs. Implementing MIMO, MU-MIMO, and / or digital beamforming technologies Therefore, the gNode-B 180a may transmit a radio signal to the WTRU 102a, for example. and uses multiple antennas to transmit and receive wireless signals from the WTRU 102a. The RAN 105 may employ other types of base stations, such as eNode-B. It should be understood that the RAN 105 may include more than one type of base station. For example, the RAN may employ an eNode-B and a gNode-B. ode-B may be adopted.

[0149] The N3IWF 199 may include a non-3GPP access point 180c. It is understood that the WF199 may include any number of non-3GPP access points. The non-3GPP access point 180c communicates with the WLAN over the air interface 198. It may include one or more transceivers for communicating with the TRU 102c. The access point 180c communicates over the air interface using the 802.11 protocol. The WTRU 102c may communicate with the WTRU 102c through a WTRU 198.

[0150] Each of the gNode-Bs 180a and 180b is associated with a particular cell (not shown). and radio resource management decisions, handover decisions, uplink and / or or may be configured to handle scheduling of users in the downlink, etc. As shown in FIG. 17D, gNode-Bs 180a and 180b may be connected to, for example, the Xn interface. They may communicate with each other through an interface.

[0151] The core network 109 shown in FIG. 17D is a 5G Core Network (5G Core Network). The core network 109 may be a wireless access network. A network may offer numerous communications services to its customers that are interconnected by a network. The Core Network 109 comprises several entities that perform the functions of the Core Network. As used herein, the term "core network entity" or "network" refers to a A "Network Function" is any entity that performs one or more functions of the Core Network. Core Network Entity means a wireless and / or network communication entity. or configured for a computer system such as system 90 shown in FIG. 17G. computer-executable instructions stored in the memory of the device and executing on the processor of the device It is understood that the present invention may be a logical entity implemented in the form of a command (software). can be.

[0152] In the example of FIG. 17D, the 5G core network 109 includes an access and mobility management function ( Access and Mobility Management Function (AMF) 172, Session Management Function (Session Management Function: SMF) 174, User Plane Function Function (UPF) 176a and 176b, User Data Management Function (User Data Management Function) Management Function (UDM) 197, Authentication Server Function (Authentication Server Function tion:AUSF)190, Network Exposure Function ion (NEF) 196, Policy Control Function (PCF) 184 ,Non-3GPP Interworking Function (N3IWF) 199, User Data Repository ( Each of the above elements may include a User Data Repository (UDR) 178. Although depicted as part of the 5G Core Network 109, any of these elements One is that it is owned and / or operated by entities other than the core network operator. It will be understood that a 5G core network may be constructed from all of these elements. It may not consist of any particular element, may consist of additional elements, and each of these elements may consist of multiple elements. It will be appreciated that each network function may be configured with a corresponding Although the direct connections to each other are shown in Figure 17D, the Diameter routing agent When communication occurs through a routing agent such as a message agent or message bus It should be understood that there is.

[0153] In the example of Figure 17D, connectivity between network functions is achieved through interfaces or is realized through a set of reference points. Network functions are connected to other network functions. A module is a set of services that are started or called by a service. It will be understood that network function services may be modeled, described, or implemented in any manner. The service launch involves direct connections between network functions and messaging exchanges over a message bus. , can be realized through software function calls.

[0154] The AMF 172 may be connected to the RAN 105 via an N2 interface and may control For example, the AMF 172 may perform functions such as registration management, connection management, reachability management, and so on. AMF may be responsible for security management, access authentication, and access authorization. It is responsible for delivering user plane tunnel configuration information to the RAN 105 via the The AMF 172 receives the user plane data from the SMF via the N11 interface. The AMF 172 generally receives N1 interface configuration information. Routes NAS packets to / from WTRUs 102a, 102b, and 102c via The N1 interface is not shown in Figure 17D.

[0155] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly, the SMF connects to the PCF184 via the N7 interface and to the PCF184 via the N4 interface. The SMF 174 may be connected to the UPFs 176a and 176b via a control node. For example, the SMF 174 may perform session management, IP address assignment for a, 102b and 102c, UPF176a and UP Management and configuration of rules guiding traffic in F176b and AMF172 It may also be responsible for generating downlink data notifications.

[0156] UPF176a and UPF176b are WTRU102a, 102b, and 102c 110, providing access to packet data networks (PDNs) such as the Internet. and facilitates communication between the WTRUs 102a, 102b, and 102c and other devices. The UPF 176a and the UPF 176b may also and 102c, providing access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or a data It may be any type of network that exchanges packets. and UPF176b receive traffic from SMF174 via the N4 interface. UPF 176a and UPF 176b may receive rules that guide the N6 interface. By connecting a packet data network using a They connect with each other and with other UPFs using interfaces to form a packet data network. may provide access to a packet data network. In addition to providing the necessary security, the UPF176 also provides packet routing and forwarding, policy rule enforcement, and user Quality of service management for server-plane traffic, buffering of downlink packets It may also play a role in the

[0157] The AMF172 also connects to the N3IWF199 via the N2 interface, for example. The N3IWF may, for example, use a non-3GPP-defined air interface technology. facilitating connectivity between the WTRU 102c and the 5G core network 109 via AM F interacts with N3IWF199 in the same or similar manner as it interacts with RAN105. There may be interactions.

[0158] The PCF 184 may be connected to the SMF 174 via an N7 interface, and the N1 5 interface and can be connected to the AMF172 via the N5 interface Connected to Application Function (AF) 188 via The N15 and N5 interfaces are not shown in Figure 17D. 4 provides policy rules to control plane nodes such as AMF172 and SMF174 Each control plane node may then be able to enforce these rules. 84 instructs the AMF 172 to provide policies for the WTRUs 102a, 102b, and 102c. As a result, the AMF may transmit to the WTRU 102 via the N1 interface. a, 102b, and 102c. Then, the policy is May be enforced or applied in RUs 102a, 102b and 102c.

[0159] UDR178 serves as a repository for authentication credentials and subscription information. A UDR may connect to a network function, which may then ,It can add to, read from, and modify data in the repository. For example, UDR178 connects to PCF184 via N36 interface. Similarly, the UDR178 connects to the NEF196 via the N37 interface. and may be connected to the UDM197 via an N35 interface.

[0160] The UDM197 is the interface between the UDR178 and other network functions. The UDM 197 may function as a network For example, the UDM197 uses the N8 interface Connects to the AMF172 via the NI PXIe-4211 and to the SMF174 via the N10 interface. Similarly, the UDM197 can communicate with the AUSF190 via the N13 interface. The UDR178 and UDM197 may be tightly integrated. do.

[0161] AUSF190 performs authentication related operations and communicates with UD via the N13 interface. The M178 connects to the AMF172 via the N12 interface.

[0162] NEF196 is a framework for application-level capabilities and services within the 5G core network109. The application function (AF) 188 is exposed via the N33 API interface. The NEF is connected to the AF188 via the N33 interface. It may connect to other network functions and 9 capabilities and services.

[0163] The application function 188 is a network function within the 5G core network 109. The interaction between application functions188 and network functions Interaction is either through a direct interface or through the NEF196 The application function 188 may be implemented as a part of the 5G core network 109. may be considered part of the 5G core network or may be external to the 5G core network109 and deployed by companies that have business relationships with mobile network operators This may be the case.

[0164] Network slicing is the process of creating one or more networks behind the operator's air interface. by mobile network operators supporting multiple "virtual" core networks This is a mechanism that may be used to The core network is being restructured to support different service types operating across multiple Related to "slicing" into multiple virtual networks. Slicing allows operators to meet diverse requirements in functionality, performance, and separation, for example. We will build customized networks for different market scenarios and provide optimized solutions. This allows us to provide solutions.

[0165] 3GPP is adapting the 5G core network to support network slicing Network slicing is a technology that allows network operators to A diverse set of often demanding 5G use cases (e.g., large Supports large-scale IoT, critical communications, V2X, and advanced mobile broadband Each use case is a good tool that can be used to improve performance, scalability, and Network slicing has its own set of scalability and availability requirements. Without the use of QoS, network architectures cannot efficiently meet the needs of a wide range of use cases. may not be flexible and scalable enough to support new networks. The deployment of network services must be done more efficiently.

[0166] Referring again to FIG. 17D, in a network slicing scenario, the WTRU 102a , 102b or 102c connects to the AMF172 via the N1 interface. An AMF may be logically part of one or more slices. F is a WTRU 102a, 102b, or 102c and one or more UPFs 176a and 176b, SMF174, and other network functions. UPF176a and 176b, SMF174, and other Each of the network functions may be part of the same slice or a different slice. If they are part of different slices, they are different computing resources. They are separate from each other in that they may use a security certificate. There may be cases where this is the case.

[0167] The core network 109 may facilitate communication with other networks, for example The core network 109 is a network between the 5G core network 109 and the PSTN 108. IP Multimedia Subsystem (IMS) server that acts as an interface may contain or communicate with IP gateways, e.g., the Core Network Work 109 is a short message service that facilitates communication via short message service. including or related to Short Message Service (SMS) service centers. For example, the 5G core network 109 may communicate with the WTRU 102a, Non-IP devices between 102b and 102c and the server or application function 188 In addition, the core network 109 may facilitate the exchange of WTR data packets. U102a, 102b and 102c include services owned and / or operated by other service providers. or other wired or wireless networks operated by the network 112 may provide access to

[0168] The core described herein and illustrated in Figures 17A, 17C, 17D and 17E Network entities are those entities in certain existing 3GPP specifications. Although these entities and functions are identified by the names given to them, in the future, Capabilities may be identified by other names, and certain entities or functions may be It will be incorporated into future specifications published by 3GPP, including future 3GPP NR specifications. It should be understood that these may be combined. , 17D and 17E, the specific network entities and The features are provided by way of example only, and the subject matter disclosed and claimed herein does not necessarily represent the presently defined to any similar communications system, whether or not specified in the present or future. It should be understood that the present invention may be embodied or implemented in various ways.

[0169] FIG. 17E illustrates a communication system in which the systems, methods, and devices described herein may be used. 1 illustrates an example of a system 111. The communication system 111 includes a wireless transmit / receive unit (WTRU). )A, B, C, D, E, F, base station gNB121, V2X server 124, and load server In fact, the present specification The concepts presented in [1] can be applied to any number of WTRUs, base stations gNBs, V2X networks, and and / or other network elements. All WTRUs A, B, C, D, E and F are within the access network coverage 131 Among WTRUs A, B, and C in the V2X group, the WTR UA is the group leader, and WTRUs B and C are group members. be.

[0170] WTRUs A, B, C, D, E and F are the access network coverage 131, they communicate with each other through the Uu interface 129 via the gNB 121. In the example of FIG. 17E, WTRUs B and F may communicate with each other via the access network. WTRUs A, B, C, D, E, and F are shown in network coverage 131. A sidelink interface (such as interface 125a, 125b, or 128) For example, via PC5 or NR PC5, they are covered by the access network. whether it is under access network coverage 131 or outside access network coverage 131 For example, in the example of Figure 17E, WRTU D, which is outside work coverage 131, is WTRU D, which is within coverage 131. Communicate with F.

[0171] WTRUs A, B, C, D, E and F are Vehicle-to-Network (V2N) 133 or sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate with the vehicle trunk. V2X Server 1 via the V2I-Infrastructure (V2I) interface 127 WTRUs A, B, C, D, E and F may communicate with the vehicle May communicate with another UE via a person-to-person (V2P) interface 128 .

[0172] FIG. 17F illustrates a WTRU, such as the WTRU 102 of FIGS. configured for wireless communication and operation in accordance with the systems, methods and apparatus described herein 17 is a block diagram of an example of an apparatus or device WTRU 102 that may be implemented. As shown in FIG. 1, the exemplary WTRU 102 includes a processor 118, a transceiver 120, a transmit / receive unit 130, a Receiving element 122, speaker / microphone 124, keypad 126, display / tablet Touchpad / Indicator 128, Non-removable Memory 130, Removable Memory 1 32, power supply 134, Global Positioning System (GPS) chip The WTRU 102 may include a wireless router 136, a wireless device 138, and other peripherals 138. It should be understood that the base station 11 may include any sub-combination of the elements. 4a and 114b, and / or base stations 114a and 114b, the nodes Not included are, among others, Base Transceiver Stations (BTS), Node-B, Site Controllers , Access Point (AP), Home Node-B, Evolved Home Node-B d Home Node-B (eNodeB), Home Evolved Node-B :HeNB), Home Evolved Node-B Gateway, Next Generation Node-B (Generati on Node-B (gNode-B) and proxy node, and 17F, which may include some or all of the elements depicted in FIG. 17F.

[0173] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital Digital Signal Processor (DSP), multiple microprocessors one or more microprocessors associated with the DSP cores, a controller, Microcontrollers, Application Specific Integrated Circuits ASICs, Field Programmable Gate Arrays FPGA (Field Programmable Gate Array) circuits, any other type of integrated circuit (IC) C), a state machine, etc. The processor 118 may be a signal coding, a data processing processing, power control, input / output processing, and / or the WTRU 102 operating within the wireless environment. The processor 118 may also implement any other functionality that allows the transmission / reception 17F, the transceiver 120 may be coupled to the element 122. Although the processor 118 and the transceiver 120 are shown as separate components, The processor 118 and the transceiver 120 are integrated together in an electronic package or chip. It will be understood that this is also acceptable.

[0174] The UE transmit / receive element 122 transmits the signal over the air interface 115 / 116 / 117. via a base station (e.g., base station 114a in FIG. 17A) or air interface 115d. / 116d / 117d to transmit signals to or receive signals from other UEs. For example, the transmit / receive element 122 may be configured to transmit and receive RF signals. The transmit / receive element 122 may be an antenna configured to transmit and / or receive a signal. configured to transmit and / or receive, for example, IR, UV, or visible light signals The transmit / receive element 122 may be an emitter / detector that receives both RF and optical signals. The transmit / receive element 122 may be configured to transmit and receive wireless or wired signals. It is understood that the device may be configured to transmit and / or receive any combination of signals. Let's solve it.

[0175] Additionally, although the transmit / receive element 122 is depicted in FIG. 17F as a single element, The TRU 102 may include any number of transmit / receive elements 122. More specifically, The TRU 102 may employ MIMO technology. To transmit and receive radio signals through interfaces 115 / 116 / 117 , may include two or more transmit / receive elements 122 (eg, multiple antennas).

[0176] The transceiver 120 modulates the signal to be transmitted by the transmit / receive element 122. , and may be configured to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. The transceiver 120 may be configured to allow the WTRU 102 to support multiple RATs, e.g., NR and IEEE802. 2.11, or communicate via NR and E-UTRA, or different RRHs, T Allows communication with the same RAT via multiple beams to RPs, RSUs or nodes For this purpose, it may contain multiple transceivers.

[0177] The processor 118 of the WTRU 102 controls the speaker / microphone 124, the keypad 1 26, and / or a display / touchpad / indicator 128 (e.g., LCD Liquid Crystal Display (LCD) display device or organic light-emitting diode connected to an Organic Light-Emitting Diode (OLED) display device The processor 118 may also receive user input data from the The data is fed to a speaker / microphone 124, a keypad 126, and / or a display / The touchpad / indicator 128 may also output the touchpad / indicator 128. In addition, the processor 118 may Any type of removable memory 130 and / or removable memory 132 The device may access information from and store data in suitable memory. The available memory 130 may be a random-access memory (RAM). ), Read-Only Memory (ROM), hard disk, or any Other types of memory storage devices may also be included. , Subscriber Identity Module (SIM) card, memory stick Examples of such memory cards include a Secure Digital (SD) memory card and a Secure Digital (SD) memory card. The processor 118 may be hosted on a cloud or edge computing platform. on the WTRU 102, such as on a server where the may access information in and store data in memory that is not physically located in .

[0178] The processor 118 may derive power from a power supply 134 and other components within the WTRU 102. The power supply 13 may be configured to distribute and / or control power to the components. 4 may be any suitable device for powering the WTRU 102. For example, power supply 13 4 may include one or more dry batteries, solar cells, fuel cells, etc.

[0179] The processor 118 also generates location information (e.g., longitude, and latitude) to a GPS chipset 136. In addition to or instead of information from the GPS chipset 136, the WTR The U 102 communicates with a base station (e.g., a receive location information from a base station 114a, 114b) and / or from two or more nearby base stations; Its location may be determined based on the timing of signals received from the ground station. It is understood that the RU 102 may obtain location information by any suitable location determination method. It will be done.

[0180] The processor 118 may further include additional features, functionality, and / or wired or wireless connections. One or more software and / or hardware modules that provide the The peripherals 138 may also be connected to other peripherals 138, which may include other modules. 8 includes various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, e- AMPUS, satellite transceiver, digital camera (for photos or videos), universal serial a Universal Serial Bus (USB) port or other interconnection interface; Vibration devices, TV receivers, hands-free headsets, Bluetooth (registered trademark) module, Frequency Modulated (FM) radio unit, digital Music players, media players, video game player modules, internet browsers It may also include a browser.

[0181] The WTRU102 is ideal for sensors, consumer electronics products, smart watches, or smart clothing. Wearable devices, medical or e-health devices, robots, industrial equipment, contained in any other apparatus or device, such as a motor vehicle, car, truck, train, or airplane The WTRU 102 may include one of the peripherals 138. This is accomplished via one or more interconnection interfaces, such as a connection interface. Connect to other components, modules, or systems of such equipment or devices You may do so.

[0182] Figure 17G shows the RAN 103 / 104 / 105, core network 106 / 107 / 10 9, PSTN 108, Internet 110, other networks 112, or 1A and 1C, such as certain nodes or functional entities within the network service 113. , 1D and 1E are embodied in one or more devices of the communication network shown in FIG. 1 is a block diagram of an exemplary computing system 90 in which The operating system 90 may include a computer or a server, and may be implemented in the form of software ( Where or by what means such software is stored or accessed, The device may be primarily controlled by computer-readable instructions, which may be a program (even a program). Such computer readable instructions may be used to operate the computing system 90. The processor 91 may be a general-purpose processor, a special-purpose processor, or the like. processors, conventional processors, digital signal processors (DSPs), multiple microprocessors processor, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASICs), field programmers FPGA circuits, any other type of integrated circuit (IC), state machine The processor 91 may be a processor for signal coding, data processing, power control, input input / output processing and / or computing system 90 within a communications network The coprocessor 81 may also implement any other functionality that enables the main An optional processor distinct from the required processor 91, which performs additional functions. The processor 91 and / or the computer may Processor 81 receives, generates and processes data related to the methods and apparatus described herein. and processing may be carried out.

[0183] In operation, the processor 91 fetches, decodes, and executes instructions to perform computing The information is transmitted to other resources via the system bus 80, which is the main data transfer path of the operating system. Such a system bus transfers data to and from other resources. Connects components within the operating system 90 and defines a medium for data exchange. The system bus 80 typically includes a data line for transmitting data, an address line, and Address lines for sending data, and interrupts and operating the system bus An example of such a system bus 80 is a PCI (Peripheral Computer Interface) Component Interconnect) bus.

[0184] The memories coupled to the system bus 80 include random access memory (RAM) 82 and and read-only memory (ROM) 93. Such memory is used for storing and reading information. ROM 93 generally cannot be easily modified. The data stored in RAM 82 may be used by processor 91 or other may be read or changed by other hardware devices. Access to the ROM 93 may be controlled by a memory controller 92. The memory controller 92 converts the virtual address into a physical address when an instruction is executed. The memory controller 92 may also provide address translation functionality. Isolating processes within the system and isolating system processes from user processes Therefore, a program that runs in the first mode may Access only memory that is mapped by its own process virtual address space. Unless memory sharing between processes is configured, the virtual address of another process may be It is not possible to access memory in the address space.

[0185] In addition, the computing system 90 may transmit data from the processor 91 to a printer 94, a printer 95, a printer 96, a printer 97, a printer 98, a printer 99, a printer 100, a printer 101, a printer 102, a printer 103, a printer 104, a printer 105, a printer 106, a printer 107, a printer 108, a printer 109, a printer communicates commands to peripherals such as keyboard 84, mouse 95 and disk drive 85 It may also include a peripheral controller 83 that takes on the role of

[0186] The display 86 controlled by the display controller 96 is is used to display the visual output generated by the display system 90. Visual output includes text, graphics, animated graphics, and video. Visual output is a graphical user interface (GUI). The display 86 may be a CRT-based video display. Play, LCD-based flat panel displays, gas plasma-based flat panel displays It may be implemented as a panel display or touch panel. The controller 96 generates the voltages required to generate the video signal that is sent to the display 86. Contains child components.

[0187] Additionally, the computing system 90 may be implemented as a RAN103 / 104 / 105, Core Network 106 / 107 / 109, PSTN1 08, an external network such as the Internet 110, the WTRU 102 or another network 112 Used to connect a computing system 90 to a communications network or device The computing system 90 communicates with other nodes or functions in those networks. a wireless or wired network adapter, allowing communication with a functional entity 97. The communication circuitry may be used alone or in combination with the processor 91. In combination with the above, the transmission of certain devices, nodes, or functional entities described herein It may be used to perform the sending and receiving steps.

[0188] Any or all of the devices, systems, methods and processes described herein The program may be implemented as computer-executable instructions (e.g., programs) stored on a computer-readable storage medium. The instructions may be embodied in the form of a program code, which is transmitted to the processor 118 or 9. When executed by a processor, such as a processor 1, the processor is configured to implement the system described herein. It is understood that the systems, methods, and processes are performed and / or implemented. In any case, any step, operation, or function described herein may be implemented by any such computer. Implemented in the form of computer-executable instructions for wireless and / or wired network communications The method may be executed by a processor in a configured device or a computing system. A computer-readable storage medium is any non-transitory (e.g., tangible or physical) medium for storing information. Volatile and non-volatile media, removable and non-transitory, implemented in any method or technology Such computer-readable storage media, including removable media, do not include signals. The computer-readable storage medium may include RAM, ROM, EEPROM, flash memory, etc. Memory or other memory technology, CD-ROM, Digital Versatile Disk DVD or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic Disk storage device or other magnetic storage device or devices for storing desired information Any software that may be used in This includes, but is not limited to, other tangible or physical media.

[0189] In describing the preferred embodiments of the subject matter of the present disclosure as shown in the figures, for the sake of clarity, However, claimed subject matter does not necessarily rely on such selected specific terms. The term is not intended to be limiting and each specific element may serve a similar purpose. It is to be understood that the present invention includes all technical equivalents that operate in a similar manner to perform the functions of the present invention.

[0190] In describing the preferred embodiments of the subject matter of the present disclosure as shown in the figures, for the sake of clarity, However, claimed subject matter does not necessarily rely on such selected specific terms. The term is not intended to be limiting and each specific element may serve a similar purpose. It is to be understood that the present invention includes all technical equivalents that operate in a similar manner to perform the functions of the present invention.< / remotecse> < / ae> < / remotecse> < / csebase> < / remotecse>

Claims

1. A device including a processor, a memory, and a communication circuit, and connected to a network via the communication circuit. a device for executing a program, the device further comprising: a computer-executable instruction set stored in the memory of the device; and wherein the computer-executable instructions are executed by the processor of the device. When the device is The above for data transfer of data originating from a user equipment (UE) receiving a first message indicating a request from the UE; Existing Background Data Transfer (BDT) policies Subscription information associated with the UE, and and sending a request for a policy profile associated with the UE to a database. And, A response indicating whether there is an existing BDT policy that can be reused is sent to the Receiving from a database; Based on the received response, the BDT policy for the data transfer and the Local Area Data Network (LOD) provides data transfer determining the LADN; sending a second message to the UE indicating the determined BDT policy; sending a third message to the LAN indicating the determined BDT policy; and, An apparatus for performing an operation including:

2. The determining step may further include determining a Quality of Service (QOS) for the data transfer. The device of claim 1 , wherein the communication is based on a QoS parameter.

3. The device according to claim 1 , wherein the device comprises an application server or a network function. The device.

4. The network function is a Policy Control Function (PCF). The apparatus of claim 3 , comprising:

5. The request includes a Packet Data Unit (PDU) session identification The apparatus of claim 1 , further comprising a child.

6. The request indicates that the data transfer is for Mobile Originated (MO) data.

10. The apparatus of claim 1, further comprising an indication that the device is of the type specified by the claim 1.

7. 2. The method of claim 1, wherein the request includes an identifier of a LAN to which the data transfer is to be directed. Device.

8. The apparatus of claim 1 , wherein the request includes a quality of service (QoS) parameter.

9. The apparatus of claim 1 , wherein the request includes a data rate for the data transfer.

10. The apparatus of claim 1 , wherein the request includes an expected start time of the data transfer.

11. The apparatus of claim 1 , wherein the request includes a maximum delay for the data transfer.

12. The apparatus of claim 1 , wherein the request includes a periodic arrival time for the data transfer.

13. 10. The method of claim 1, wherein the request includes network slice information related to the data transfer. The apparatus described.

14. The apparatus of claim 1 , wherein the request includes an average data rate for the data transfer.

15. The request may include a BDT policy identifier or a BDT policy identifier associated with the determined BDT policy. The apparatus of claim 1 , further comprising: a reference identifier;

16. The apparatus of claim 1 , wherein the request includes a network type for the data transfer.

17. The device further comprises computer-executable instructions stored in the memory, The computer-executable instructions, when executed by the processor of the device, cause the device to 、 a fourth message notifying the UE of a time to start the data transfer; To believe, The apparatus of claim 1 further comprising:

18. The apparatus of claim 1 , wherein the UE is authorized to initiate BDT.

19. The device further comprises computer-executable instructions stored in the memory, The computer-executable instructions, when executed by the processor of the device, cause the device to 、 sending the updated BDT policy to the database for storage; The apparatus of claim 1 further comprising:

20. The determined BDT policy includes a Quality of Service (QoS) parameter.

1. The device described in 1.

21. The apparatus of claim 1 , wherein the determined BDT policy includes a data rate.

22. The method of claim 1 , wherein the determined BDT policy includes a reference to a charging policy. Equipment.

23. The determined BDT policy includes a traffic pattern of the data transfer.

10. The device of claim 1.

24. The method of claim 1 , wherein the determined BDT policy includes network slice information. Equipment.

25. The device of claim 1 , wherein the determined BDT policy includes a BDT policy identifier. Place.

26. The determined BDT policy includes an indication of whether it is reusable. The apparatus of claim 1 .

27. The determined BDT policy may include an indication of whether it can be shared with other UEs. The apparatus of claim 1 , further comprising:

28. The determined BDT policy includes an offset indicator and a back-off timer. The apparatus of claim 1 .

29. The determined BDT policy may be related to the UE or a group of UEs including the UE. The device of claim 1 .

30. The determined BDT policy may be applied to an application or a group of applications. The device of claim 1 , associated with a group.

31. The determined BDT policy is applied to Mobile Terminated (MT) traffic.

10. The device of claim 1, associated with the LAN for the metric.

32. The determined BDT policy is a mobile-originated (MO) BDT policy. Item 1. The device described in item 1.

33. The device further comprises computer-executable instructions stored in the memory, The computer-executable instructions, when executed by the processor of the device, cause the device to 、 a fourth message including an indication of the arrival time and data rate of said data transfer; transmitting a message to said LAN; The apparatus of claim 1 further comprising:

34. The transmitting of the second message includes transmitting an indicator associated with the request from the UE. The device of claim 1 , wherein the device is based on a network application.

35. The apparatus of claim 1 , wherein the request from the UE includes a location.

36. The device further comprises computer-executable instructions stored in the memory, The computer-executable instructions, when executed by the processor of the device, cause the device to 、 receiving a notification when the UE enters the location based on the request from the UE; To achieve this, Access and Mobility Management Function subscribe to the AMF (Agile Messaging Module), 36. The apparatus of claim 35, further comprising:

37. The sending of the second message is based on receiving the notification from the AMF.

37. The device of claim 36.

38. The sending of the second message may include transmitting the determined BDT policy to the UE. The device of claim 1 , further comprising:

39. The transmitting of the second message includes: A registration update request including the S-NSSAI to connect to a new network slice Sending and Packet data containing the Data Network Name (DNN) transmitting a session establishment request data unit (PDU); Sending a PDU session update request; The apparatus of claim 1 , wherein the apparatus performs at least one of the following:

40. The PDU session establishment request is sent to the Session Management Function ion: SMF) to read the determined BDT policy and 40. The method of claim 39, wherein the determined BDT policy is applied to a PDU session. Device.

41. The transmitting of the second message includes: an indication that the determined BDT policy is active, Time window, amount of data, 5-tuple, application identifier, ASP identifier and an indication including the location where the determined BDT policy is active. Sending the application An indication that the determined BDT policy is inactive is sent to the application. Sending the data to the application The apparatus of claim 1 , wherein the apparatus performs at least one of the following:

42. The sending of the second message may include transmitting the determined BDT policy to the UE. deactivating a BDT policy associated with the determined BDT policy; the UE leaving a location where the BDT policy is determined and a data threshold associated with the determined BDT policy. The UE detects that the BDT policy has been exceeded and determines whether the BDT policy has been exceeded. The UE detects that a time window for the The UE detects that an application layer request has been received, and the UE receives an application layer request. The apparatus of claim 1 , wherein the method is based on at least one of:

43. The device further comprises computer-executable instructions stored in the memory, The computer-executable instructions, when executed by the processor of the device, cause the device to 、 receiving a request from the UE to readjust the determined BDT policy; The apparatus of claim 1 further comprising:

44. The request to readjust the determined BDT policy may include a change related to the data transfer. and wherein the change comprises a new start time for the data transfer, a new end time for said data transfer, a different data rate associated with said data transfer, or at least one additional application data flow associated with the transmission.

43. The apparatus described in 43.

45. The device further comprises computer-executable instructions stored in the memory, The computer-executable instructions, when executed by the processor of the device, cause the device to 、 receiving a request from a network function to readjust the determined BDT policy; 、 The apparatus of claim 1 further comprising:

46. The request to readjust the determined BDT policy may include a change related to the data transfer. The change may be a change in the service area of the LAN, a change in traffic a characteristic change, or the UE becoming unreachable.

46. The apparatus of claim 45.

47. 10. The method of claim 1, wherein the LANs are associated with dynamically configured service areas. Equipment.

48. The dynamically configured service area is associated with a parameter, and the parameter The service area, application service identifier, time schedule, service event granularity of the real, quality of service (QoS) parameters.

47. The apparatus described in 47.

49. The device further comprises computer-executable instructions stored in the memory, The computer-executable instructions, when executed by the processor of the device, cause the device to 、 sending a fourth message to the UE including the parameters; 49. The apparatus of claim 48, further causing the apparatus to perform operations including:

50. Indicates a request from a user equipment (UE) for data transfer of data originating from the UE. receiving a first message; Determine if there is an existing Background Data Transfer (BDT) policy To do this, subscription information associated with the UE and a policy associated with the UE are sending a request for a profile to a database; A response indicating whether there is an existing BDT policy that can be reused is sent to the Receiving from a database; Based on the received response, the BDT policy for the data transfer and the determining a local area data network (LADN) that provides data transfer; sending a second message to the UE indicating the determined BDT policy; sending a third message to the LAN indicating the determined BDT policy; and a method comprising:

Images