How to manage connections to Local Area Data Networks (LADN) in 5G networks

Abstract

To provide methods and apparatuses to allow a service capability server / application server to configure information sharing and mobility support among a set of local area data networks / data networks.SOLUTION: A method includes: selecting, by an AMF, when UE sends, via RAN, a PDU establishment request to the AMF, an SMF, and sending a PDU session context creation request to the selected SMF; reading and / or updating, by the SMF, registration and subscriptions, and sending a PDU session context creation response to a UDM, the PDU session being authenticated and authorized between the UE and the DN; selecting, by the SMF, a PCF; establishing and / or modifying, by the SMF and the selected PCF, a session management policy, and selecting a UPF; modifying, by the SMF and the PCF 306, the session management policy; and transmitting, by the SMF 305, an N4 session establishment / modification request to the selected UPF.SELECTED DRAWING: Figure 3A

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. which is incorporated herein by reference in its entirety.

[0002] Background Data Transfer (BDT) is a service that transfers data at a constant Data transfer to User Equipments (UE) at a specific rate for a specific period of time. Allows the Application Server (AS) to be pre-configured Long Term Evolution is a resource management mechanism that ion (LTE) Evolved Packet Core (EPC) is a mobile-terminated (Mobile Terminated: MT) traffic BDT consists of the service capability service of the AS This document defines procedures for local area data networks. A LAN Data Network (LADN) is a data network that is accessible to UEs only at specific locations. Packets destined for the LAN / DN are sometimes defined as a 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 set of different tracking areas. 5G Core (5GC ) The network uses the UE's location to make the UE aware of the availability of the LAN. Support for the implementation of the proposed standard may be provided.

[0003] The LADN provides a specific area, which is defined as the service area. A user may need to repeatedly connect to a DN, for example, due to certain mobility patterns. It may contain lines.

[0004] Some Internet of Things (IoT) device applications Applications and IoT servers can only operate if they are within the service area of ​​the LANDN. In addition, the UE may also send Mobile Originated (MO) To transmit traffic and pre-configure BDT policies in 5G networks It may be necessary to

[0005] Therefore, data transfers in different LANs, such as for MO traffic, can be handled by the device. It is necessary to define mechanisms that allow for the implementation of schedules and implementation. Summary of the Invention

[0006] This Summary is provided in a simplified form to provide an overview of the detailed description of the invention, which is further described below. This Summary is intended to present a selection of 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, the claimed subject matter does not incorporate any of the features described anywhere in this disclosure. Nor is it intended to be construed as being constrained by limitations that would 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 it enables you 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 detect if there is an existing Background Data Transfer (BDT) policy. The subscription information associated with the UE and The device sends a request to the database for a policy profile associated with the reuse. 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 the data transfer. .

[0008] BRIEF DESCRIPTION OF THE DRAWINGS In order to facilitate a clearer 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 description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an exemplary non-roaming reference architecture with a service-based interface in the control plane. [Diagram 2] FIG. 2 shows an example 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 example procedure for background data transfer (BDT). [Diagram 5] Figure 5 is a conceptual architecture diagram of network slicing. [Figure 6] FIG. 6 is a diagram of an example 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 illustrates an example 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 example 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 illustrates an example of establishing a connection to the LAND. [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 PREFERRED EMBODIMENTS

[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 relates to a method and an apparatus for configuring a network and mobility support. Reusing session context information from a previous session This specification describes a simplified session establishment procedure for connecting to the LAN via Internet of Things (IoT) device applications will be 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 transmit actual data later in LAD N Also described herein.

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

[0012] [Table 1]

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

[0014] [Table 2]

[0015] FIG. 1 illustrates an exemplary non-roadmap using a service-based interface in a control plane 50. As shown in the example of Figure 1, the UE 70 is a wireless access point. Access via the N1 interface 67 via the RAN 71 Access to the Mobility Management Function (AMF) 65. The Namf interface 62 is also The RAN 71 communicates with the Access Mobility 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. The Session Management Facility (SMF) 66 is accessed 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 illustrates 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 is.

[0017] Figure 2 is a table of reference points showing how various network functions interact with each other. 2 illustrates an example 5G system architecture for a non-roaming case 200. End-to-end traffic between 201 applications and applications in external networks The end communication may use services provided by 3GPP systems, or The services provided by a Service Capability Server (SCS) that may reside on the DN204. As shown in the example of FIG. 2, the UE 201 may use the RAN 202. The AMF 212 is accessed through the N1 interface 220 via the Also shown is an N2 interface 232. The RAN 202 includes an N3 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 through the N9 interface 234. F203 accesses DN204 via N6 interface 225. Example of Figure 2 The figure also shows the 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. The SMF 21 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 UDM 211 communicates with the AUSF 210 via the N13 interface 231. This may be the case.

[0018] Applications in external networks are usually handled by application servers (AS). may use the SCS for additional value-added services. The P system includes transport, subscriber management, and, but is not limited to, the MTC. Includes various architectural extensions that are triggered by (e.g., control plane devices) The mobility management and session management functions are separate. The NAS connection of the N1 220 is managed by the registration management and connection management. For both On Management and Connection Management (RM / CM), and may be used for SM related messages and procedures for the UE 201. The N1 220 end point may be located within the AMF 212. The AMF 212 may transmit SM-related NAS information to the SMF 213. 01 and handles the registration management and connection management parts of the NAS signaling exchanged with The SMF 213 is responsible for managing the session of NAS signaling exchanged with the UE 201. May handle ports.

[0019] A Local Area Data Network (LADN) is a network that is accessible only to UEs at specific locations. A DN is defined as a DN that provides connectivity to a specific DN. The availability of the PDU session for the LAN DN may be provided to the UE. Access to the DN via the LAN may only be available in certain LAN DN service areas. A LADN service area may include a set of tracking areas. C supports the UE to be aware of the availability of LADN based on the UE's location. may be provided.

[0020] The AMF 212 transmits LADN information including information on the availability of the LADN to the UE 201. The AMF 212 provides the UE 201 with a LADN service area (i.e., a LAD N available area) depending on whether the SMF213 is located, 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 uses the DNS service area information, the UE 201 can use the DNS service area information. The LAN service area information provided to the UE 201 during the registration procedure The tracking area (i.e., the LADN subarea) belongs to the current registration area of ​​the UE 201. AMF21 may contain a set of AMF21 service areas (intersection of the service area and 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 ... Although the steps are shown and described separately, they may be used in different orders than shown and in relation to each other. Several 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 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: These include IPv4, IPv6, Ethernet and unstructured types. The PDU session may be, for example, an N1 interface between the UE and the SMF. using NAS SM signalling exchanged over the UE interface (at UE request) Established (by UE and 5GC requirements), modified (by UE and 5GC requirements), and In response to a request from the application server, the 5G C can trigger a specific application of the UE. The trigger message Upon receiving the request, the UE may pass it to an application that has been identified in 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. The AMF 303 may then send a U establishment request (step 311). Then (step 312), the PDU session context is stored in the selected SMF, SMF305. The SMF 305 may send a creation request (step 313). 3. Read and / or update the cryptography (step 314) and add it to the UDM 307 A DU session context creation response may be sent (step 315). A PDU session may be authenticated and authorized between the UE301 and the DN308. (Step 316). SMF 305 may select PCF 306 (Step Then, the SMF 305 and the selected PCF, PCF 306, Next, the SMF may establish and / or modify application management policies (step 318). The SMF 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 transmits to the RAN 302 an N2 PDU, which may be a 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 acknowledgment. The UE 301 may then transmit the first uplink data (step 326). Next, the AMF 303 may transmit 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 modification response to the SMF 305 (step 330). SMF305 sends Nsmf PDU session SM context update to AMF303. Response (step 331) and Nsmf PDU session SM to AMF 303 The SMF 305 may transmit 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 then be performed (step 335).

[0025] FIG. 4 is a diagram of an exemplary procedure for Background Data Transfer (BDT) 400. Although each step of the procedure 400 of 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 implemented to provide a specific period of time at a constant data rate. 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 a 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 to receive the request (step 411). Select to enable the Policy Control and Charging (PCC) program. The PCRF 403 and the SCS may trigger a procedure (step 412). Future requests by SCEF 404 delivering parameters provided by AS 405 This may include the negotiation of 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 , the reference ID and the forwarding policy may be delivered to the third-party SCS / AS 405 ( SCS / AS405 will use Reference I for future interaction with the PCRF. If more than one forwarding policy is received, the third-party SCS may store the forwarding policy. / AS405 selects one of them and sends the SCS / AS identifier, TTRI, and The SCEF40 then sends another BDT Request message, which may contain the forwarding policy specified in the 4 and the PCRF 403 may be informed of the selected forwarding policy (step 41 4) The SCEF 404 sends a background data transfer response message (TTRI). Confirm forwarding policy selection with the third-party SCS / AS405 by sending The SCEF 404 may then send the reference ID and the new forwarding address to the SPR (step 415). The PCRF403 that may remember the policy and the future background data transfer policy The SCS / AS 405 may then continue with negotiation of the loss (step 416). The AF (which acts as the AF) is the same or different for each UE (through the Rx interface). may contact different PCRFs 403 and the SCS / AS 405 may 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 is The selected forwarding policy 417 with 01 may be activated (step 417).

[0027] FIG. 5 is a diagram of a conceptual architecture 500 of network slicing. Network slicing may include both backhaul and core networks. Multiplexing behind the air interface across 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 and / or to support different service types operating across a single RAN , which involves "slicing" a network into multiple virtual networks. Slicing may entail 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 to include in the resource layer 503: Network functions, resources, and network functions that operate the network functions The network slice instance layer 502 may include a set 513. A plurality of network slice instances 511a, 511b, 511c, 511d, 11e, 511f, 511g and 511h, or subnetwork slice instances These may include 512a, 512b, 512c, 512d, 512e, and 512f. The subnetwork slice instance is responsible for 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 instance. As shown using network slice instance 512d, multiple network slice instances The service instance layer 501 is a layer that represents the service instances. The chests of drawers may include drawers 510a, 510b, 510c, 510d and 510e.

[0029] Network slicing technology will be incorporated into 3GPP 5G network and other technologies. Network slicing may be part of the 5G network use cases. (e.g., large-scale IoT, critical communications, and advanced mobile broadband) It enables relevant, diverse and highly demanding requirements. The 5G architecture will support smartphones, over-the-top (OTT) content, and Mobile traffic from smartphones, data cards, and embedded M2M devices Relatively monolithic networks and traffic that support a variety of services, including traffic Leverages the Transport Framework. Pre-5G architecture and related capabilities, extensions A specific set of performance and usage requirements efficiently supports a wide range of business needs. In addition, the new network services may not be flexible and scalable enough to support The introduction of services may be more efficient. Nevertheless, some users 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 the past, commuter trains may have video surveillance systems and electronic bulletin boards. Networks 603, Internet 608 and Multiple LADNs 605, 604, 6 They may be equipped with communications circuits allowing connections to 06 and 607. A station may contain an SCS / AS that hosts multiple AFs. When a train arrives at a station, Connect to a LADN such as LADN604 to upload video recordings from a surveillance system. It may also download some local ads for bulletin boards. The device used by the UE also connects to the LAN to download videos. Load and / or upload content from your device for backup For video uploads and local ad downloads, trains may be 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, trains may pass through stations on the same schedule 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 assigned different capabilities by the network operator. For example, a LADN 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 LAN, the router must know what services it is supporting and must know the services it is supporting. In some cases, a patient may be able to schedule or plan their visit to the service.

[0032] As mentioned above, based on the train schedule, it is possible to decide when the train will start connecting to the LADN. In other words, the time it takes to connect to the LADN can be predicted. Connections can be determined in advance according to train schedules. In some use cases, the use case may be repeated (periodically at fixed intervals). and the protocol defined in 5GC 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 that E is within the coverage area of ​​the LADN; and This involves many steps, such as the selection of an anchor point 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 above example the train, to complete the data transfer quickly and efficiently. Streamline the session establishment / activation mechanism for LADN so that It is desirable.

[0033] In addition, recognizing the LADN's ability to save time and be more efficient, Without this, it would be impossible to schedule data transfers in one LADN (for example, train station 1). and scheduled activity in a pre-configured LADN (e.g., Train Station 2). For example, trains may not be able to provide video recordings. However, if the LAN you are connecting to has a high uplink data rate, The LADN serving the next station may not support the high-speed uplink. The current LADN may know whether the device supports 1000Mbps data transfer. Therefore, the current LADN is the next LADN for that train. Schedule a data 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 on different LANs, such as for mail originated (MO) traffic. It is necessary to define the schedule and mechanisms that will allow implementation. By sharing additional information between the network functions (NFs) serving the LADN, Possible mechanism for session establishment / activation on LADN There is a need to streamline the process.

[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 more efficient to schedule and perform data transfers on different LANs for a group. It may be more efficient.

[0035] 5G LADN is accessible to UE only in specific locations and can only be connected to a specific DN. A DN 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 be connected to achieve efficient service delivery. Allows the UE to be hosted near the access point. During the set of LADN Configure information sharing and mobility support on the PDU session that connects the LADN. You can transfer a PDU session from one LADN to another without repeating the procedure of establishing a PDU session. moving applications, UE initiated procedures, DN / LADN initiated procedures 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 an apparatus are described herein.

[0036] 7 through 16 (described below) illustrate various aspects of managing connections to a LAN. In these figures, one or more nodes, apparatus, devices, servers, Various steps or operations performed by a network, function, or network are illustrated. For example, devices may operate alone or in conjunction with one another to perform the methods described herein. In this specification, 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 executed by the processor. That is, the methods described herein may be implemented, for example, by a node or a computer. A form of software stored in the memory of a network node such as a computer system (e.g. For example, the present invention may be implemented in computer-executable instructions, and the computer-executable instructions may be implemented in computer-executable instructions. 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 implemented as ,The node’s processor and the computer-executable instructions that the ,processor executes (e.g. For example, the communication may be performed by the communication circuitry of the node under control of software. It will be 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 in the LADN. The LADN server may be used to configure policies and exchange information. The AF may communicate with the core network to 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 700 that may be used in one embodiment to share information between the LADNs 700 and FIG. 7 is a diagram of an example procedure for configuring a reliability support. Although each step is shown and described separately, it may be performed in a different order than shown. Several steps may be performed in parallel or simultaneously with each other. Information may be shared among 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 LANs 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 LAN The UE specific context may be shared among a set of LADNs.

[0041] Such information sharing will result in connecting and / or disconnecting PDU sessions with the LADN. Registration and session management may be simplified for the UE when establishing or updating the Another benefit is that mobility is supported. and, in the context of LADN, this includes:

[0042] In one LADN, registration and session termination is performed when the UE moves out of the service area. The context information is stored and read when the UE comes back. 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] Registration and session context is preserved across multiple LADNs as the UE moves. This is because the UE may be connected to an edge device of one LADN. If you access content from the edge cache and the same content is not Move to another LADN that does not have the content cached, or move to a LADN or If you need to access the original version of the content, go to the DN This can be useful in caching use cases.

[0044] In the train use case above, each LADN along the track forms a LADN group. When trains are in close proximity to LADNs, they may use information sharing. In some cases, it may connect to the LADN, and the LADN server (i.e., the SCS / AS) may communicate with 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 sent to the network to configure a policy (step 710). This policy may apply to two or more LADNs to establish a UE connection. How connections and / or sessions can persist across the entire LADN A request message may be encapsulated in other types of request messages. Information may include, but is not limited to, the 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 LAN An indication that the AF wants to port, which may indicate the type of UE Type or application type (e.g., mobile non-IoT devices) and LADN Applications that may obtain 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 to support different LADNs. Policy or user policy shared across all AMFs, SMFs or UPFs serving In addition, each PCF may have a different LADN. When configuring policies, policies and user contexts are also managed across all PCFs. may be shared among multiple parties.

[0047] Instead of a LADN identifier or a list of DN identifiers, the AF uses the L An indication of the type of ADN may be provided. For example, this indication could be , 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: This includes background data transfer policy, charging policy, UE registration and session Context information, etc.

[0049] When a UE connects to a specific LAN, the AF provides mobility support to the core network. An indication that the AF wishes to support mobility is, for example, If you do not choose to do so, the UE connected to the LAND 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 an explicit 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 can be used to determine whether mobility is to or across a LADN. In the case of a single LADN, this may indicate whether the UE When a user moves out of 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 context is being maintained. In the case of multiple LADNs, this When the UE moves, the registration and session information and status are transferred from one LADN to another. may be forwarded from one LAN to another, for example Including from one SMF and / or UPF to another SMF and / or UPF There are cases.

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

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

[0053] PCF702 contacts UDM / UDR701 to confirm subscription and policy. The PCF 702 may obtain the license profile data (step 712). The ID and policy of 704 may include an identification of an LADN to which the policy may relate. UDM / UDR701 will notify you that any existing related policies configured for LADN / DN The UDM / UDR 701 may use that 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 responds to requests from AF704 and profiles from UDM / UDR701. Based on the registration data, a new policy may be determined (step 713). Registration 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 to which the information is shared, e.g. 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 transmit the NEF 703 and the AF 704 (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 preservation. Update your profile to reflect new policies on information sharing and mobility support. The policy to be stored may be requested to be mirrored (step 716). 4 and 715. For example, the PCF 702 may include: The existing BDT policy for MT traffic set by the set of LADNs ,is shared / reused by a set of LADNs belonging to the same network operator. The UE may request an indication that:

[0058] Steps 711, 712, 713, 714 and 716 are the components of step 710 of AF. Note that this may be performed once for each UE specified in the request. From an application layer perspective, the LADN or DN of a In addition, we may share information regarding the BDT structure and schedule. A 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. This is also 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). Lack of availability means that application providers are increasingly looking to build LAs that serve more UEs. Dynamically configure DN or provide application services to UE more efficiently This may prevent the

[0060] One solution is to offer different applications / services at different times. For this purpose, it is necessary to define flexible service areas for 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 A time schedule, e.g., a tracking area, a registration area, a cell, or a geographic area granularity of the service area, 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., maximum Parameters such as QoS parameters, which may indicate data rate and delay, are This may be related to allowing more flexibility in the DN's service area.

[0061] In addition, the NWDAF may take into account, but is not 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. As more data is transferred, 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 the traffic load. The mobility statistics of the UE are based on the fact that it remains in the service area of ​​the LADN and AF / AS to register 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 obtains access to the LADN. When requesting, the AMF shall send the UE the service area information and their related attributes of the LADN. In addition, the network may be slow to respond due to congestion, e.g., the LAN DSN. Any associated attributes of the service area or LADN may be dynamically updated so that 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 request that the AF / AS update any parameters related to its service area. Trigger network functions to initiate actions when changes need to be made Good too.

[0063] FIG. 8 may be used in combination with any of the embodiments described herein. 1 is an example procedure for moving a PDU session from a first LADN to a second LADN. FIG. 8 is a diagram of a procedure 800. Each step of the procedure 800 in FIG. 8 is shown and described separately. are shown, but may be run 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 termination message for a previously activated PDU session. session ID, the identifier of the LAN / DN for which 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 of this is to reactivate a previously existing session on the specified LADN / DN. Indication of,Q,e.g., aggregated maximum data rate, maximum delay, etc. The request may include information about 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 SMF, a different SMF than the one that originally established the PDU session is selected. This is also fine.

[0064] SMF803 receives subscription information and The session context may then be obtained (step 812). The test may include, but is not limited to, the QoS parameters, the session parameters that were set when the session was originally established, The periodic indication of the time between two active periods, the time The average length of the active period and the status of the PDU session (for example, active, Alternatively or additionally, SMF8 may include information such as 03 is the number of subscribed packets from the last UPF / NEF used to anchor the session. SMF803 may then obtain the session information and session context. Depending on the configuration, it may be decided whether the same anchor point should be used. In the above case, the SMF 803 may first consider the service area of ​​the LADN when making the decision. If 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 one providing the session, the SMF contacts the SMF providing the session. The session context information is read and the SMF is informed that the session is currently being provided. Session context information may indicate the current or previous session The identifier of the UPF being used may also be included.

[0065] SMF803 stores some session context information, e.g., data rate, The PDU session can be reconfigured if the active period length, connection to a different LAN, etc., changes. The application 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 LAN (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 the ID A more detailed policy profile may be obtained by invoking 5). SMF803 activates the PDU session and sends the request to the application that is providing the session. The anchor point is selected (step 816). 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] SMF803 may update the session context information of UDM / UDR804. The SMF 803 notifies the activation of the PDU session (step 817). In some cases, the linking 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 following may be provided: ,By including the session context information, AMF802 can 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 UPF / NEF 806 may F / NEF 806 address may be provided. Compared to the procedure of FIG. 3A to FIG. 3B The procedure 800 for re-establishing a PDU session by sharing information is Reduce 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 FIG. FIG. 9 is a diagram of a procedure 900. Each step of the procedure 900 in FIG. 9 is shown separately. and are described, but in a different order than shown, in parallel with each other, or with each other. In the train use case described above, the network A network 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 transmit MO data. The data rate may be supported, or the train may take longer to update before arriving at the next station. It may not have the complete data to load, or the train may be near its last stop. We may upload captured security footage from your device, or Trains may schedule data transfers on the centralized data network, which This allows the train to be instructed on which LADN the data transfer 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) starts configuring 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, the BDT is a centralized data network (e.g., the Internet) that is Alternatively, the UE may be scheduled by a core network entity. The configuration procedure may be initiated by communicating directly with the identity.

[0069] Referring to the example of FIG. 9, a UE 901 is connected to an AMF 903 via a RAN node 902. By sending a message indicating a request for BDT for UE 901 originating traffic. The procedure 900 may be started 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 sage, including, but not limited to, Information that may be included includes an indication that it is for MO traffic. , PDU sessions (R If there is an existing PDU session going from AN to UPF or AMF / NEF path The PDU session identifier (ID) that indicates whether the PDU session has a The UE is currently connected to a different DN / LADN than the destination LADN for the requested data transfer. The ID of the DNN of the LADN / DN to which MO traffic is destined. ,For example, periodic data with time intervals, average data size, data rate, maximum delay, and MO data traffic patterns, such as the 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 The BDT policy ID indicates the policy to be used by the core network entity to determine 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 in a non-3GPP network an indication of whether you wish to transfer data over the network; and UE mobility patterns or predicted UE location 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 authorization is granted, the AMF 90 3 is the location of the destination LADN / DN, the start of the session if a PDU session already exists The anchor point and the time of the session if the PDU session is not yet established. Manage the MO BDT configuration by considering the type (e.g. IP or non-IP) The AMF 903 selects an SMF (e.g., SMF 904) to be used (step 912). In conjunction with the information provided above with respect to 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) that manages the BDT, including managing the 06) may be selected (step 914).

[0071] Factors that may be taken into consideration to select an appropriate PCF include, but are not limited to: However, the PCF, UE, or network to which the UE registers that serves the destination LADN / DN PCF serving network slice instances, when used for MO BDT The PCF manages the policies regarding existing PDU sessions that may or may not exist, and The PCF that is serving the anchor point for the PDU session is different. Cases involving PCFs, e.g., a UE is in a network served by one PCF Connect to a workslice and the destination LADN / DN is served by another PCF Depending on the network operator configuration and the agreement between the 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 need to transmit non-IP data. and to promote the existing non-IMF through the AMF-NEF pathway for MO BDT. In this case, AMF 903 may provide an ID for the PDU session. In step 912, the PCF 906 is selected, and in step 913, a BDT request is sent to the PCF. Therefore, steps 914 and 915 may be omitted.

[0073] SMF904 may send a BDT request to a selected PCF (e.g., PCF906). 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. E901 may request related subscription information and policy profiles. (Step 916). If the UE 901 provides an 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 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 the The PCF 906 may check whether the received Based on the information collected, 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. The policy may include, but is not limited to, DT policy ID, UE ID and destination LADN / DN ID, e.g., along with time interval The periodic data, average data size, data rate and expected start time of data transfer Defined traffic patterns of MO traffic, such as between o BDT policies may be reused (shared) by another UE or LADN / DN An indication of whether the UE desires data transfer through a non-3GPP network. In this case, the PCF may select an N3IWF and include the ID of the N3IWF), then Also, the MO BDT may contain information including the PDU session ID and type associated with it. 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 fick may then be requested to be stored (step 919). The PCF 906 stores the BDT together with the policy ID and UDM / UDR ID in the SMF 904. A response may be sent (step 920) so that the SMF 904 is ready for data transfer. Therefore, in the future, when you need to establish / activate a PDU session, you will need to use the MO BD The PCF 906 can read the UE 901 T policy for MO traffic. If you select a destination LADN / DN different from the one identified by The SMF 904 may indicate the ID of the LADN / DN in the response message. 3 may deliver the BDT response 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 reply to the UE 901 with the BDT policy that is to be applied (step 922). The RAN node 902 receives M from the UE served by the RAN to the LADN / DN. O The core network may notify the presence of the BDT. The UE may then signal a UE-specific schedule of upcoming BDTs related to the selected LADN. Given the UE traffic and / or mobility patterns, 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 the locations. ADN1 downloads data at 5Mbps, and ADN2 uploads 15 minutes of video. The data rate of the 10 Mbps data stream was 15 minutes. AMF903 also supports periodic data with time intervals, average data size, Traffic-related information, such as data rates and expected start times for data transfers This is often done through the N2 interface. The SMF 904 forwards the MO traffic to the AF 908 that resides in the destination LADN / DN. The NEF 907 may also inform the MO of the BDT policy configured for the MO. The BDT policy ID and the PCF ID may be recorded (step 923). As an option, the PCF 906 may perform step 923. 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 FIG. 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. The BDT policy may be sent directly to the AMF. It may be delivered by the AMF as a payload of the 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 FIG. 10 is a diagram of an example procedure 1000 for BDT configuration. 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 the UE 1001 configuring the MO BDT is transmitted via the RAN 1002 to the AMF 1003 (step 1010), which then The BDT configuration procedure is started (step 1011). The DN is set by the UE 1001 as the destination LADN / DN for MO traffic. Instead, the LADN / DN that initiates 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 provided by the UE1001 or When MO traffic arrives, the UE 1001 detects the traffic based on the traffic pattern. There is a possibility that the mobile station is outside the service area, or some other condition prevents it from receiving MO traffic. It may indicate to a network entity that the received signal is not suitable for trust.

[0077] FIG. 11 may be used in combination with any of the embodiments described herein. BDT policy configuration for MO traffic initiated by DN / LADN 11 is a diagram of an exemplary procedure 1100 of FIG. Although shown and described separately, they may be used in parallel with each other in a different order than shown. Several steps may be performed in sequence or simultaneously with each other. For example, DN / LADN The SCS / AS may manage a group of sensors and schedule those sensors. In the example of FIG. 11, the AF 1106 may report these measurements periodically. 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 periodic data, average data size, data rate, maximum delay and data transfer The traffic characteristics, such as the start time of the AF 1003 transmission, the number of UEs, It defines certain conditions for stopping BDT, such as the threshold for the amount of data transferred 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 regarding the MO traffic (step 1114). The PCF 1104 may determine the BDT policy to be applied (step 1115). The UDR 1103 may transmit the determined BDT policy regarding the MO traffic. ,The UDM / UDR 1103 is the BDT policy determined for MO traffic. The RAN node 1101 may store the scheduled The BDT may be notified by the AMF 1102 (step 1117). In addition, PCF1104 sets up the paging policy for BDT and 02, so that AMF 1102 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. In some cases, the LADN / DN may transmit MT data to a group of UEs. In Rio, MT data is broadcast to all devices in the LADN service area. In another example 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 put pressure on each device and make it easier to Group-based BDT is particularly useful because it allows users to easily manage groups of applications. 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. A BDT request can be sent to the network by indicating an external group ID or an internal group ID. Therefore, once the PC Once F has determined 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. The AMF is aware of the location of any UE. 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 retrieve 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 the AMF receives an N2 message, the AMF may send one N2 message to the RAN node. In the message, the AMF indicates individual UE identities and / or group identities. 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 cases where this happens, there is a backoff timer associated with the policy. See below for details. This will be explained in.

[0081] Table 3 below shows the background data forwarding 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, the background data transfer policy is 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 The indication may indicate that the device is intended for use in initiating communications. 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 the policy. triggers the UE to immediately send the policy (via AMF and NAS signaling) As a policy indicator, MO-BDT policy indication 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 a specified 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 transmission policy, the content of the policy determines which of the following actions the UE should take: One or more of these may be implemented by the UE.

[0086] 1) Decision to activate a policy: The decision to activate a policy is made by the BDT policy. the UE detects that it has entered a location or geographic area indicated by 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 specified in the policy is reached or when the filters listed in the policy are Event when the UE detects traffic that matches the 5-tuple information The policy may be activated by any combination of the following: When deciding to activate a policy, the offset may delay the policy activation. The offset may be indicated in the policy or may be determined by the random generator and / or The UE identifier is based on a part of the UE identifier, such as the UE's SUPI or 5G-S-TMSI. 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 a connection to a new network slice. , which may include the S-NSSAI provided in 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. There may be cases where this occurs.

[0090] Sending a PDU session update request or a 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 displayed. 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 reads the policy from the PCF and assigns it to the PDU session. This may be used by SMFs that apply

[0091] 3) Policy Activation Notification: Once a policy is activated, the UE Sends a notification to the E application to inform the UE application that the policy is active. Notifications may include a time window, amount of data, and 5-Tu ple, application ID, ASP ID, and BDT policy activated The UE may also include locations where the BDT may become inactive. When (outside time window, data volume exceeded, out of specified location, PDU session to DDN It may send a notification to the UE application to inform it that the Alternatively, the UE may check the policy usage before activating the policy 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 allow UE applications to use traffic patterns defined by policies. The UE application is notified until it generates traffic that matches the specified group (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 sent 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 explicit application When it receives an application layer request, it may decide to deactivate the policy. Deactivating a policy will result in a PDU Session Modification, PDU Session Release message. This 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, timer 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 in the pre-planned data transmission, e.g. For example, when the UE needs to change the start and / or end time of data transmission, 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 when the UE has additional application data When a data flow needs to be added to the 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 reason for the update and the BDT policy. A reference ID or a BDT policy to indicate the parameters that should be changed 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 support 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 traffic characteristics change, the UE cannot reach the area specified by the BDT policy or due to the event of the network detecting that the In some cases, the BDT policy stored in the UE may need to be updated. This may be done with the assistance of the NWDAF in the network. When it detects a BDT policy, it contacts the PCF to indicate the BDT policy and the associated UE. The network function may trigger the UE configuration update process. The reference ID or BDT policy ID, the rationale for the update, and the BDT policy are used to Update the BDT policy by indicating the parameters that are relevant to the policy and should be changed. Good too.

[0095] FIG. 12 may be used in combination with any of the embodiments described herein. A UE-initiated configuration of BDT policy for MO traffic in the LTE EPC. FIG. 12 is a diagram of an example procedure 1200 of the procedure. 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) to 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 in the BDT request the same information as that in the By showing that the IEEE 802.11 standard is for MO traffic with D, The SCEF 12 may then start a procedure for BDT configuration, including the 05 is set in the MME 1202 by the PCRF 1204 and recorded in the SPR 1203. The BDT response may be sent along with the stored policy ID (step 1213). The MME 1202 transmits to the UE 1201 a policy ID for the MO BDT and a BDT policy ID. 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 of Figure 13, the 5G network interface The BDT configuration in 1301 consists of 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. In some cases, it may be possible to set up a BDT 1303 corresponding to the above.

[0097] FIG. 14 is a diagram illustrating an example of a UE connected to the 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 in the LANDN 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 currently being implemented). In other words, for security reasons, warehouse owners may want to allow employees to observe and manage their inventory from home. Sometimes we don't want to be understood.

[0098] When the UE is outside the coverage area of ​​the LAND, the UE has IP connectivity. However, it does not have connectivity to the enterprise inventory management system 1404. Therefore, these applications can be aware of whether the UE is inside or outside the LADN. The application may be aware of the presence of a UE in the LADN, allowing the application to know if the UE is not in the LADN. When this is not possible, the action should not be attempted.

[0099] Provides finer granularity of access to the LAN from a service / application perspective. To provide this service, the 5GC1403 supports a wide range of services based on the different services provided by the LADN. The LADN may implement an authorization procedure for some services / applications. It is anticipated that this initiative will assist 5GC1403 by providing application information. One method 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 service area is 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, Application sessions with the business inventory management system 1404 may be interrupted. 5GC1403 specifies that the SMF is not available when the UE moves out of the LADN service area. When the UE's user plane connection may be deactivated and when the SMF When the UE is notified of its return to the area, the SMF resets the user plane connection of the UE. To support this type of scenario, you can indicate whether the In some cases, the UE platform 1401 and the inventory management application The API used by the application is to determine whether the UE's user plane connection is left at the UE's location. In some cases, the right to

[0101] When the inventory management 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 an 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 A DU may send a session establishment message with the request type "Open". The message may indicate a "start request" and may be N may contain a new indication that LADN is a LADN name. The indication that it is a DN name may be used by the network, As a result, if the name is not known in the network, the DDN name is changed to the more common The network knows that it will not replace the DDN. Instead, the network If you do not identify the provided DDN / LADN, the network assumes 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. The device may display a message indicating whether

[0102] FIG. 15 may be used in combination with any of the embodiments described herein. FIG. 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 for displaying 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 is used to indicate whether the LA is connected to the network. It may be used to provide the DN.

[0103] LADN information, including tracking areas that may reach the LADN, is provided by 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 the LADN can be reached. When the UE platform detects that the user plane connection is The UE may send a notification indicating that the UE is not itself part of the LADN. Detects that the device has left a LDN area when it determines that it has entered a non-tracking area. The user interface of the inventory management application may be displayed on the handset screen as follows: "good bye" 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 not" message. When the UE platform detects that the vehicle has re-entered a potential area, the inventory management app The UE may then send a notification to the associated application indicating that the user plane connection has been re-established. The user interface of the inventory management application is displayed on the handset screen, displaying the company's "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 if the The PDU session is displayed with a request type indicating "Existing PDU Session" and the PDU session ID. In addition, the request may send a session establishment message if the request is 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 the UE disconnects the signal, it may detect that it has entered an LADN area. When the person re-enters an area where the person may be in danger, the information is sent to the inventory management application. Instead, the notification that was set up in the UE will cause the UE to re-establish a 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 inventory control application 1604 may send an out of range LADN message. 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 The warehouse management application 1604 is notified of the presence of a LADN area or connection re-establishment message. 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 LAN. An option may be a service layer hosted on the UE. In oneM2M terminology, this This may be called the ASN-CSE or it may be the 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 carry out the registration procedure together with the IN-CSE. IN-CSE is an ASN-CSE only if the ASN-CSE is located in a certain geographic area. RFC 3546 ... Additionally, the IN-CSE may provide geographic region details to the ASN-CSE. Physical domain details may include, but are not limited to, GPS coordinates, longitude, latitude, address, traffic Examples include tracking area and tracking area list.

[0109] An ASN-CSE may hold location attributes or resources. E is an application that registers 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. The information may be made available to registered applications. held in ASN-CSE and means IN-CSE <remotecse>Resources 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 the ASN-CSE when leaving or entering a geographic area where Users may subscribe to receive the

[0111] As mentioned above, the ASN-CSE is configured to automatically detect when the UE re-enters the LADN area. After receiving such notification, 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 terminology, <csebase>Resources), IN-CSE Related to (in oneM2M terminology, <remotecse>resource) or or related to each application registered in the ASN-CSE (oneM2M In terms of <ae>The application registered with ASN-CSE may be An application can subscribe to state changes of the corresponding attribute or resource. ,Whether the UE is in the LADN or whether the IN-CSE can be reached Applications may subscribe to receive notifications. Upon receiving the message, the IN-CSE is not reachable and / or the UE is outside the LADN. The application may either abort the activity or (if If the UE is reachable and / or is within the LAN, 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 different service layers and has its own LADN. Therefore, the ASN-CSE may request multiple IN-CSEs for each IN-CSE associated with a different LADN. <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 the IN-CSE is reachable. To believe, to respond <remotecse>You may subscribe to.

[0113] 3rd Generation Partnership Project: 3GPP) is a set of standards for radio access, core transport networks, and service capabilities ( Cellular technology, including those that affect encoding / decoding, security, and quality of service - Develops technical standards for telecommunications network technology. The technology (RAT) standards are WCDMA (commonly referred to as 3G), LTE ( Generally referred to as 4G), LTE-Advanced, and the new 5G standard. 3GPP NR standard development continues and is the next generation radio access technology. This is expected to include provisions for new frequency bands below 7 GHz. Provision of flexible wireless access and new ultra-mobile broadband above 7GHz It is envisaged that the system will include provisions for broadband wireless access. The new wireless access will be based on new non-backwards compatible wireless networks in new frequency bands below 7 GHz. It is expected that the system will consist of multiple accesses, which will be multiplexed together in the same frequency band. Different operating modes 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 mobile and hotspot use It is envisaged that this will include the centimeter wave and millimeter wave frequency bands, which are used for radio wave communication. Ultra Mobile Broadband with mmWave specific design optimizations below 7GHz It is expected to share a common design framework with Flexible Radio Access. .

[0114] 3GPP has set 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 the following 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 saving), 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, device remote control, bidirectional Remote control, personal cloud computing, video streaming, wireless cloud Data-based office, emergency responder connectivity, car e-call, disaster warning, real-time Time game, multi-party video call, autonomous driving, augmented reality, tactile internet, Birch This includes digital reality, home automation, robotics and aerial drones. All of these use cases and others are contemplated herein.

[0115] FIG. 17A illustrates a configuration in which the methods and apparatus described and claimed herein may be used. An example of a communication system 100 is shown. The communication system 100 may generally or collectively be Wireless Transmit / Receive Unit (WTRU) 102 may refer to 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 of a number of network elements. Each of the In the example of FIG. 17A, each of the WTRUs 102 may be a handheld device. The handheld wireless communication device is depicted in FIGS. 17A to 17E. 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 Assistant (PDA), smartphone, laptop , 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 equipped or 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, the base station 114b communicates with a remote radio head (RRH) 11 8a, 118b, Transmit / Receive Points (TRP) 119a, 119b and / or Load Sa At least one of the Roadside Units (RSUs) 120a and 120b 106 / 107 and 1080, which interface with the core network 106 / 107 via wired and / or wireless 7 / 109, the Internet 110, other networks 112, and / or facilitating access to one or more communications networks, such as the 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. 106 / 107 / 109, the core network 110, One or more of the following may be used: network services 113, and / or other networks 112. Any type of device configured to facilitate access to a communications network or multiple communications networks. It may be a vice.

[0118] The TRPs 119a and 119b communicate wirelessly with at least one of the WTRUs 102d. The interfaces are Core Network 106 / 107 / 109 and 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 1 02f and wirelessly interfaces with at least one of the core networks 10 6 / 107 / 109, Internet 110, Other Networks 112, and / or or network services 113. The device may be any type of device configured to facilitate 114a and 114b are base transceiver stations (BTSs), 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 Network Controller (Radio Network Controller: RNC), relay nodes, and other The base station 11 may also include base stations and / or network elements (not shown). 4b may be part of RAN 103b / 104b / 105b, which , other base stations and / or network elements such as BSC, RNC, relay nodes, etc. (as shown in the figure) A base station 114a may include a base station (not shown) for a particular geographic area, sometimes called a cell. (not shown) may be configured to transmit and / or receive wireless signals. 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. A cell attached to a base station may be divided into three sectors. The base station 114a may include three transceivers, one for each sector of the cell. For example, a adopts Multiple-Input Multiple Output (MIMO) technology. Therefore, multiple transceivers may be used per sector of a cell. .

[0120] The base station 114a may communicate with any suitable wireless communication link (e.g., Radio Frequency (RF) :RF), Microwave, Infrared (IR), Ultraviolet (UV), Possible Air Interface 115 / 116 / 117 through one of WTRUs 102a, 102b, 102c, and 102g 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 implemented using 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.) 115b / 116b / 117b, which may be a wired or air interface Through RRH118a and 118b, TRP119a and 119b and / or The RSU 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 The air interface 115c / 116c / 11 may communicate with one or more 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, The sidelink communication may be When communicating with each other through the direct air interface 115d / 116d / 117d The air interface 115d / 116d / 117d may be implemented using any suitable RAT. may be established using

[0124] The communication system 100 may be a multiple access system and may be implemented using CDMA, TDMA, One or more channel access such as DMA, FDMA, OFDMA, SC-FDMA For example, base station 1 in RAN 103 / 104 / 105 may adopt a packet transfer scheme. 14a and the WTRUs 102a, 102b, and 102c, or the RANs 103b / 104 RRH118a, 118b, TRP119a, 119b and / or RSUs 120a and 120b and WTRUs 102c, 102d, 102e, and 102f Universal Mobile Telecommunications System (UMTS) UMTS System, Universal Terrestrial Radio Access The wireless technology may implement a wideband CDMA (WDMA) or other wireless technologies such as UTRA (Unified Radio Access). MA:WCDMA) using air interfaces 115 / 116 / 117 and / or WCDMA can establish high-speed 115c / 116c / 117c. High-Speed ​​Packet Access (HSPA) and / or Advanced H It may 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 the High Security Unified Access (HSUPA).

[0125] For example, the base station 114a and the WTRU 102a, 10 2b, 102c and 102g, or in 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 are 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 technologies and interfaces.

[0126] A base station 114a in the RAN 103 / 104 / 105 and WTRUs 102a, 102b, 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 establishment, 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 purposes of the present invention. For example, the WTRU 102e is a wireless 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 IEEE802.15 to create wireless personal area networks (Wi The base station 114c may establish a wireless personal area network (WPAN). The TRU 102, e.g., the WTRU 102e, is a cellular-based RAT (e.g., DMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to 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 , and access the Internet 110 via the core network 106 / 107 / 109. There may be cases where it 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) oIP) 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 code , Internet connectivity, packet data network connectivity, Provides Ethernet connectivity, video distribution, etc. and / or allows users High level security features such as authentication may also be implemented.

[0129] Although not shown in FIG. 17A, RAN 103 / 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 a different RAT. For example, it will be appreciated that a RAN10 that may utilize E-UTRA radio technology 3 / 104 / 105 and / or RAN103b / 104b / 105b. In addition, the core network 106 / 107 / 109 also uses GSM or NR radio technology. The RAN may also communicate with another RAN (not shown) that employs

[0130] The core network 106 / 107 / 109 also includes a WTRU 102 that is connected to the PSTN 108, To access the Internet 110 and / or other networks 112 The PSTN 108 provides the Plain Telephone Service (PSTN). Includes circuit-switched telephone networks providing the Old Telephone Service (POTS). The Internet 110 may be implemented using the Transmission Control Protocol (TCP). col:TCP), User Datagram Protocol (UDP) , and the Internet Protocols in the TCP / IP Internet Protocol Suite ( A set of interconnected computers that use a common communication protocol such as the 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 types of packet data networks (e.g., IEEE 802.3 Ethernet networks) network) or RAN103 / 104 / 105 and / or RAN103b / 104b / 105b may employ the same RAT 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, 10c, 10d, 10e, 10f ... 2b, 102c, 102d, 102e and some or all of 102f, e.g., WTR U102a, 102b, 102c, 102d, 102e and 102f are different wireless A wireless network 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 a cellular-based wireless technology. and base station 114c, which may employ IEEE 802 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 will be understood that the gateway is a residential gateway. l Gateway (RG) may be the 106 / 107 / 10 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 is to apply 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 the core network 106. As mentioned above, the RAN 103 adopts UTRA radio technology to realize the air interface 11 5. RAN1 may communicate with WTRUs 102a, 102b, and 102c through 03 may also communicate with the core network 106. As shown in FIG. 103 communicates with the WTRUs 102a, 102b and 102c through the air interface 115. 2c, each of which may include one or more transceivers for communicating with Node-B 140a, 140b and 140c. Each of 140b and 140c is associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a and 142b. 03 may include any number of Node-Bs and Radio Network Controllers (RNCs) Please understand that there is.

[0134] As shown in FIG. 17B, Node-Bs 140a and 140b communicate with an RNC 142a. In addition, the Node-B 140c may communicate with the 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 corresponding Node-B 140a, 140b and In addition, the RNCs 142a, 142b and 140c may be configured to control the These are outer loop power control, load control, admission control, packet scheduling, Other features such as handover control, macro diversity, security functions, data encryption, etc. The device may be configured to perform or support certain functions.

[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 MGW 144 may be connected to the MSC 146 in the network 106. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may 102c, providing access to a circuit-switched network such as the PSTN 108; It may facilitate communications between 102b and 102c and conventional terrestrial communications devices.

[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 to and from the WTRUs 102a, 102b, and 102c to 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 that may include other wired or wireless networks operated 2.

[0139] FIG. 17C is a system diagram of an example of the RAN 104 and the 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. Each of the eNodeBs 160a, 160b and 160c is connected to an air interface 11. 6 to communicate with the WTRUs 102a, 102b, and 102c. For example, eNode-B 160a, 160b and 160c may be provided. The eNode-B 160c may implement MIMO technology. For example, a WTRU 102a may transmit a wireless signal to the WTRU 102a and receive a wireless signal from the WTRU 102a. In order 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 may be associated with radio resource management decisions, handover decisions, uplink and / or configured to handle user scheduling in the downlink, etc. As shown in FIG. 17C, eNodeBs 160a, 160b, and 160c may , may communicate with each other through the X2 interface.

[0142] The core network 107 shown in FIG. 17C includes a mobility management gateway (Mobility Management Gateway). ty 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 should be understood that the information contained herein may be owned and / or operated by third parties.

[0143] The MME 162 communicates with the eNode-B 1 in the RAN 104 via the S1 interface. 60a, 160b and 160c, respectively, and function as control nodes. For example, the MME 162 may authentication of the user, bearer activation / deactivation, WTRU 102a, 102b b and 102c, selecting a particular serving gateway during the initial connection. The MME 162 may also be responsible for communicating with the RAN 104 and other related systems, such as GSM or WCDMA. A control program is provided 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. Each of the eNode-Bs 160a, 160b, and 160c may be connected to a service node. The signaling gateway 164 generally provides signaling to / from the WTRUs 102a, 102b, and 102c. Routes and receives 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, 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 of the provides access to packet-switched networks such as the Internet 110 and the WTRU 1 02a, 102b, 102c and IP-enabled devices. It may be connected to the DN gateway 166.

[0146] The core network 107 may facilitate communication with other networks. The PSTN 107 connects the WTRUs 102a, 102b, and 102c to the 8, and the WTRUs 102a, 102b and 102c For example, the core network 1 may facilitate communication between the cellular network and conventional terrestrial communication devices. 07 acts as an interface between the core network 107 and the PSTN 108 IP gateways (e.g. IP Multimedia Subsystems) In addition, the IMS may include or communicate with a core network (IMS Server). The network 107 transmits the WTRUs 102a, 102b, and 102c to other service providers. (b) any other wired or wireless networks 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 the 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 adopts non-3GPP wireless technology to improve the air interface The N3IWF 199 may also communicate with the WTRU 102c through a 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 via the air interface 117. 2a and 102b. When integrated access and backhaul connections are 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 180a and 180b. Implementing MIMO, MU-MIMO, and / or digital beamforming technologies Thus, the gNode-B 180a may transmit a radio signal to the WTRU 102a, for example. WTRU 102a and WTRU 102b use multiple antennas to transmit and receive wireless signals from 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 include 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 WF199 may include any number of non-3GPP access points. The non-3GPP access point 180c communicates with the wireless LAN through 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 via a hub 198.

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

[0151] The core network 109 shown in FIG. 17D is a 5G core network. The core network 109 may be a wireless access network (WLAN). A network may provide numerous communications services to its customers that are interconnected by networks. The Access Network 109 consists of several entities that perform the functions of the core network. As used herein, the term "core network entity" or "network A "Network Function" is any entity that performs one or more functions of the Core Network. A Core Network Entity is a network entity that provides wireless and / or network communications. 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 nagement 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 may One is that they are owned and / or operated by entities other than the core network operator. It will be appreciated that the 5G core network may be constructed from all of these elements. It may not be composed of any particular elements, it 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 multiple instances of Although they are directly connected to each other as 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 provided by interfaces or is realized through a set of reference points. A network function can be connected to other network functions. A model is a set of services that are started or called by a service. It will be understood that network function servers may be modeled, described, or implemented in any manner. The service is launched by connecting network functions directly and exchanging messages on a message bus. , can be realized via 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 registration management, connection management, reachability management, and The AMF may also 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 signal from the SMF via the N11 interface. The AMF 172 generally receives N1 interface configuration information. Routes NAS packets to and from the 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 is connected 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 handle session management, IP address assignment for 102a, 102b and 102c, UPF176a and UP Management and configuration of rules directing traffic on F176b and AMF172 It may also be responsible for generating downlink data notifications.

[0156] UPF176a and UPF176b are WTRU102a, 102b and 102c 110 to provide 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 The network may be any type of network that exchanges packets. and UPF176b receive traffic from SMF174 via the N4 interface. The UPF 176a and the UPF 176b may receive rules that guide the N6 interface. By connecting packet data networks using the By connecting to each other and to other UPFs using interfaces, Providing access to packet data networks In addition to providing security, the UPF176 also performs packet routing and forwarding, policy rule enforcement, and user Service quality control for server-plane traffic, buffering of downlink packets The organization may also play a role in providing guidance.

[0157] The AMF172 also connects to the N3IWF199 via the N2 interface, for example. The N3IWF may, for example, support non-3GPP-defined air interface technologies. facilitating a connection between the WTRU 102c and the 5G core network 109 via the 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 may 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 FIG. 4 provides policy rules to control plane nodes such as AMF172 and SMF174 Each control plane node may then enforce these rules. 84 transmits policies for WTRUs 102a, 102b, and 102c to AMF 172. As a result, the AMF may be transmitted to the WTRU 102 via the N1 interface. a, 102b and 102c. The policy may then be distributed to the WT 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, so that the network function ,It is possible to add to, read from, and modify the data in the repository. For example, UDR178 connects to PCF184 via N36 interface. Similarly, the UDR178 is connected to the NEF196 via the N37 interface. and may be connected to a 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 100V interface and to the SMF174 via the N10 interface Similarly, the UDM197 may communicate with the AUSF190 via the N13 interface. The UDR178 and UDM197 may be tightly integrated. do.

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

[0162] NEF196 is a framework for application-specific capabilities and services within the 5G Core Network109. The exposure is via the N33 API interface. The NEF communicates with the AF188 via the N33 interface. It may also connect to other network functions, and 5G core network 10 9 capabilities and services.

[0163] The application function 188 is a network function in the 5G core network 109. There may be interactions between application functions188 and network functions. The 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 are deployed by companies that have business relationships with mobile network operators. There may be cases where this occurs.

[0164] Network slicing is the process of integrating one or more With mobile network operators supporting multiple "virtual" core networks This is a mechanism that may be used to The core network is being scaled to support different service types operating across multiple Network Slicing allows operators to determine the various requirements for functionality, performance, and separation, e.g. Build customized networks and optimize solutions for different market scenarios This enables us to provide solutions.

[0165] 3GPP is upgrading the 5G core network to support network slicing Network slicing is a technology that allows network operators to A diverse set of 5G use cases that are often demanding (e.g. 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 requirements, scalability, and availability. Without the use of QoS, network architectures cannot efficiently meet the needs of a wide range of use cases. In addition, new networks may not be flexible and scalable enough to support The introduction of network services must be made more efficient.

[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 nets may be adjusted. Each of the network functions may be part of the same slice or different slices. If they are part of different slices, they will be treated as different computing resources. They are separate from each other in that they may use a single authentication method, a single authentication service, or a security certificate. There may be cases where

[0167] The core network 109 may facilitate communication with other networks, such as The core network 109 is a 5G core network 109 and a PSTN 108. IP Multimedia Subsystem (IMS) server that acts as an interface For example, a core network may contain or communicate with an IP gateway. Work 109 is a short message service that facilitates communication via short message service. Short Message Service (SMS) service center or For example, the 5G core network 109 may communicate with the WTRU 102a, Non-IP digital 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 other service providers owned and / or 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. The network entities are those entities in certain existing 3GPP specifications. These entities and functions will be identified by the names given to them, but 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. Thus, Figs. 17A, 17B, and 17C , 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 is not limited to the presently defined to any similar communication system, whether or not specified in the present or future. It should be understood that the present invention may be embodied or implemented in any suitable manner.

[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 some cases, the reticle may include random sequence units (RSUs) 123a and 123b. The concepts presented in the paper 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 in the access network coverage 131 Among the V2X groups WTRU A, B, and C, the WTR UA is the group leader, and WTRUs B and C are group members. be.

[0170] WTRU A, B, C, D, E and F are the WTRUs that are in 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 FIG. 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 the access edge 131 or outside the access network coverage 131 For example, in the example of Figure 17E, the access network WRTU D, which is outside work coverage 131, is WTRU D, which is within coverage 131. Communicate with F.

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

[0172] FIG. 17F illustrates a WTRU 102, 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 in accordance with the present invention. As shown in FIG. 1F, the example WTRU 102 includes a processor 118, a transceiver 120, a transmit / receive control unit 122, and 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 data router 138, and other peripherals 138. It should be understood that the present invention may include any sub-combination of the above elements. 4a and 114b, and / or base stations 114a and 114b, the limitations are Not included are Base Transceiver Stations (BTS), Node-B, Site Controllers, among others. , 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, as described in this specification. The device 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 ircuits:ASIC, 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 operation of the WTRU 102 within a wireless environment. The processor 118 may also implement any other functionality that enables the transmission / reception In FIG. 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's transmit / receive element 122 communicates over the air interface 115 / 116 / 117. 17A) or the 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 , e.g., configured to transmit and / or receive 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 present invention may be configured to transmit and / or receive any combination of signals. Let it be understood.

[0175] In addition, the transmit / receive element 122, although depicted in FIG. 17F as a single element, may be 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 mentioned above, the WTRU 102 may have multi-mode capabilities. The transceiver 120 is 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 Allow 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 Display (Liquid Crystal Display: LCD) display device or organic light-emitting diode It is 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 touch pad / indicator 128 may also output the touch pad / 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 is a random access memory (RAM). ), Read-Only Memory (ROM), hard disk, or any The removable memory 132 may include other types of memory storage devices. , Subscriber Identity Module (SIM) cards, memory sticks and Secure Digital (SD) memory cards. The processor 118 may be hosted on a cloud or edge computing platform. on the WTRU 102, such as a server on which the WTRU 102 is hosted, or in a home computer (not shown). 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 source 134 and may be connected to other The power supply 13 may be configured to distribute and / or control power to the components. 4 may be any suitable device that provides power to 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, latitude, and latitude) to the GPS chipset 136. In addition to or instead of information from the GPS chipset 136, the WTR The user equipment 102 communicates with a base station (e.g., 114a, 114b) and / or two or more nearby stations. It may determine its location based on the timing of signals being received from the ground station. It will be appreciated that the RU 102 may obtain location information by any suitable location determination method. It will be.

[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 is a sensor that can be used with various sensors such as an accelerometer, a biometric (e.g., fingerprint) sensor, an e- , 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 can be used in 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 vehicle, car, truck, train, or airplane The WTRU 102 may include one of the peripheral devices 138. 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] FIG. 17G shows the RAN 103 / 104 / 105, the 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 include software in the form of 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 programmable logic device (e.g., a programmable logic controller, a programmable logic device, or a programmable logic device). 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 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 digital processor, etc. A power / output processing and / or computing system 90 in 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 and capable of performing 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.

[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 the computer's resources. Connects components within the operating system 90 and defines a medium for data exchange The system bus 80 typically includes data lines for transmitting data, address lines, and Address lines for sending data, and interrupts and manipulating the system bus. An example of such a system bus 80 is a PCI (Peripheral Computer Interface) The NI PXIe-4110 is a 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 the processor 91 or other The RAM 82 and 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 functions. A memo that isolates processes in the system and isolates 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. The virtual address of another process may be different from the virtual address of the other process unless memory sharing between processes is configured. It is not possible to access memory in the address space.

[0185] In addition, the computing system 90 includes a processor 91, a printer 94, 84, mouse 95 and disk drive 85. The peripheral controller 83 may also be responsible for:

[0186] The display 86 controlled by the display controller 96 is 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 converter 96 supplies the power needed to generate the video signal that is sent to the display 86. Contains child components.

[0187] Further, the computing system 90 may be implemented as a RAN103 / 104 / 105, Core Network106 / 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 of those networks. A network adapter, e.g., a wireless or wired network adapter, that allows a network 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 may be achieved. 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 present invention relates to a computer-executable instruction (e.g., a program) 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 caused to implement the system described herein. It is understood that the systems, methods, and processes described herein may be implemented and / or performed. 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 of 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-removable, implemented in any logical 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 (DVSD) 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 program that may be used to This includes, but is not limited to, other tangible or physical media.

[0189] In describing preferred embodiments of the subject matter of the present disclosure as illustrated in the figures, for the sake of clarity, In the present invention, specific terminology is employed. However, claimed subject matter does not incorporate such selected specific No limitation to the term is intended and each specific element may accomplish 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 preferred embodiments of the subject matter of the present disclosure as illustrated in the figures, for the sake of clarity, In the present invention, specific terminology is employed. However, claimed subject matter does not incorporate such selected specific No limitation to the term is intended and each specific element may accomplish 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 transmitter that transmits a request for first information to a database indicative of an existing background data transfer (BDT) policy for a wireless transmit / receive unit (WTRU); a receiver for receiving from the database a response including second information indicating the existing BDT policy and a location corresponding to the existing BDT policy; Equipped with The receiver further receives a notification when the WTRU enters the location; The transmitter further transmits a message to the WTRU indicating the existing BDT policy regarding data forwarding and a data network that provides the data forwarding based on the received response and the received notification. Device.

2. The apparatus of claim 1 , wherein the apparatus includes a policy control function (PCF).

3. The apparatus of claim 1 , wherein the request includes a BDT policy identifier or a reference identifier associated with the existing BDT policy.

4. The apparatus of claim 1 , wherein the message indicates a time to begin the data transfer.

5. The apparatus of claim 1 , further comprising: storing the existing BDT policy in the database.

6. The apparatus of claim 1 , wherein the existing BDT policy includes at least one of time window and network area information indicating when and where the existing BDT policy applies to the data transfer.

7. The apparatus of claim 1 , wherein the existing BDT policy is associated with the WTRU or a group of WTRUs that includes the WTRU.

8. The apparatus of claim 1 , wherein the existing BDT policy is associated with an application or a group of applications.

9. The apparatus of claim 1 , wherein the existing BDT policy is included as part of a UE route selection policy (URSP) rule.

10. The apparatus of claim 1 , further comprising: determining a location that corresponds to the existing BDT policy.

11. The apparatus of claim 1 , wherein the notification is received from an access and mobility management function (AMF).

12. The apparatus of claim 1 , wherein the database comprises a unified data repository.

13. The apparatus of claim 1 , wherein sending the request is in response to a request received at a second device, the second device including a policy control function (PCF).

14. sending a request for first information to a database indicating an existing background data transfer (BDT) policy for the wireless transmit / receive unit (WTRU); receiving a response from the database including second information indicating the existing BDT policy and a location corresponding to the existing BDT policy; receiving a notification when the WTRU enters the location; sending a message to the WTRU indicating the existing BDT policy regarding data forwarding and a data network providing the data forwarding based on the received response and the received notification; The method includes:

15. The method of claim 14 , wherein the database comprises a unified data repository.

Images