Server on communication path for internet of things

Abstract

To provide a device connected to a radio network such as a public land mobile network (PLMN) that facilitates migration of connection of wireless devices and supports non-coverage related PLMN migration.SOLUTION: In a device connected to a communication network via a communication circuit, computer-executable instructions stored in a memory that, when executed by a processor of the device, cause the device to receive, from a first PLMN, system information relating to network support for restricted access for network selection assistance, transmit a change registration request signaling a restricted registration to the first PLMN, transmit a manual network selection request, receive a manual network selection response including an indication to connect to a second PLMN, de-register from the first PLMN, and register with the second PLMN.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application is a joint venture of U.S. Provisional Patent Application No. 62 / 669,669, filed May 10, 2018. , entitled "Internet of Things Communication Path Server," the contents of which are hereby incorporated by reference in their entirety. is incorporated herein by reference. [Background technology]

[0002] This disclosure relates to Public Land Mobile Network (PLMN) selection and Machine-to-Machine (M2M), Internet of Things IoT (Internet of Things) and Web-of-Things (Web of Things) systems switching Regarding these, they are described in 3GPP TS 23.501, System Architecture for the 5G System. m; Stage 2, v15.0.0, TS 23.502, Procedures for the 5G System; Stage 2 , v15.0.0, TS 23.122, Non-Access-Stratum (NAS) functions related to Mobi le Station (MS) in idle mode, v15.2.0, RP-172021, Study on NR-based Ac cess to Unlicensed Spectrum, and 3GPP TS 21.905 Vocabulary for 3GPP S This is described in the specifications, V 14.1.1. Summary of the Invention

[0003] Radio networks, such as public land mobile networks (PLMNs), provide a means of connecting wireless devices. In addition, wireless networks may be adapted to facilitate the transition to non-coverage areas. This may be adapted to support service-associated PLMN transitions.

[0004] For example, the first wireless network may be a user equipment (UE) or a second Receives requests from wireless networks and forwards data from one wireless network to another The method may be adapted to initiate migration of one or more devices to the network. Further, the first wireless network may provide a wireless network to the user terminal or the second network. Initiate migration of one or more devices from one wireless network to another The Company may send a request to

[0005] Wireless networks may offer limited access to assist in network selection. For example, a device such as a user terminal may support , Systems related to network support for limited access for network selection assistance The device may receive system information from the first network. The device may then For example, if a second network is discovered and Allowing access to the first network for the limited purpose of migrating to To this end, the device and the first network may use signaling to establish a restricted registration. Establish.

[0006] User terminals and servers such as IoT servers will also be required to facilitate the transition to wireless networks. For example, the user terminal may be adapted to provide a service through the first network. A manual network selection request may be sent to the UE by the The server then sends the user terminal a list of networks that have been found through manual network selection. The response from the IoT server may be a connection to the second network. For example, the second network may include an indication of The UE then registers from the first network. The user may cancel the registration and register on the second network.

[0007] The manual network selection request may be, for example, a list of networks that the user terminal has discovered ( PLMN / RAT combination), received signal strength and other metrics for each network, The cell identity of the strongest cell per network, and the address of the IoT server to contact. It may contain one or more of the following:

[0008] A manual network selection request or response may be, for example, a modified non-access stratum (NAS) It is sent via a control message and is embedded in the registration request or response message, or The data may be sent to the IoT server via an IP connection.

[0009] For example, the UE may register with the first network and support non-coverage-related PLMN transition. The UE may then signal the port from the IoT server. The UE may receive a request to perform a search. The UE may perform the search and submit the request to the IoT server. Upon receiving the PLMN update request, the UE may send a list of discovered networks. 2 network, where the second network is the discovered network. The UE may then register from the first network. The PLMN update request may be sent, for example, to the first network, to cancel the first registration and register in the second network. Activation tag to cancel registration from one network and register with a second network and the UE deregisters from the first network and registers to the second network. The time window for determining whether the

[0010] Core network entities, such as devices implementing network functions, are part of the PLMN To facilitate the transition, core network entities may be adapted, for example ,one or more UEs served by an IoT server in another network; The entity may then determine that the IoT service needs to be migrated. The UE may send a UE transition request to the Io From the T server, a list of UEs to be migrated and the target network for these UEs The entity may then receive a UE transition response along with In some cases, the PLMN may send a PLMNUpdate request to the UE in question.

[0011] Such manipulation of core network entities may be implemented in a variety of ways. For example, the decision may be based on UL load, DL load, buffer load, or signaling load. or based on some combination of these. A UE transition request may be based on, for example, the list of The transition request may include the transition, the UE location, the UE network load, and the reason for the transition request.

[0012] The IoT server may be adapted to facilitate the PLMN transition in various ways. For example, an IoT server is a server that is connected to an IoT application server, a UE, and a network. The IoT server may request context information from the received Based on the text information, the service may assess whether a PLMN transition is warranted. The server determines that a UE in the first network needs to be migrated to an alternative network. The server then checks whether the alternative network is ready to accept the UE's registration. may send a UE transition proposal to an alternative network to determine if there is If so, the server sends a UE transition request to the UE through the first network. For example, evaluation by the IoT server may be performed by minimizing IoT server communication and Based on the migration of the UE to an alternative network utilizing the multicast capabilities of the network. It can be a spider.

[0013] 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.

[0014] BRIEF DESCRIPTION OF THE DRAWINGS A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which: It is possible. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram of an exemplary set of entities in a cellular and packet network. [Diagram 2] FIG. 2 is a block diagram of an example IoT cellular deployment. [Diagram 3] FIG. 3 is a block diagram of an example set of entities associated with home routing roaming. [Figure 4] FIG. 4 is a block diagram of an example set of entities associated with local breakout roaming. [Diagram 5] FIG. 5 is a block diagram of an example congestion use case. [Figure 6] FIG. 6 illustrates a call flow diagram of an exemplary method for PLMN selection triggered by an M2M / IoT device. [Figure 7] FIG. 7 illustrates a call flow diagram of an exemplary method for PLMN selection triggered by an M2M / IoT device. [Figure 8] FIG. 8 illustrates a call flow diagram of an exemplary method of core network triggered PLMN reselection. [Figure 9] FIG. 9 illustrates a call flow diagram of an exemplary method of core network triggered PLMN reselection. [Figure 10] FIG. 10 illustrates a call flow diagram of an exemplary method of core network triggered PLMN reselection. [Figure 11] FIG. 11 illustrates a call flow diagram of an exemplary method for PLMN reselection triggered by an M2M / IoT server. [Figure 12] FIG. 12 illustrates a call flow diagram of an exemplary method for PLMN reselection triggered by an M2M / IoT server. [Figure 13] FIG. 13 illustrates a call flow diagram of an exemplary method for PLMN reselection triggered by an M2M / IoT server. [Figure 14]FIG. 14 illustrates a call flow diagram of an exemplary method for PLMN reselection triggered by an M2M / IoT server. [Figure 15] FIG. 15 is a diagram illustrating an exemplary roaming variant. [Figure 16] FIG. 16 illustrates a call flow diagram of an exemplary method for PLMN reselection to a non-roaming-served routing PLMN. [Figure 17] FIG. 17 illustrates a call flow diagram of an exemplary method for PLMN reselection to a non-roaming-served routing PLMN. [Figure 18] FIG. 18 illustrates a call flow diagram of an exemplary method for PLMN reselection to a non-roaming-served routing PLMN. [Figure 19] FIG. 19 illustrates an exemplary graphical user interface. [Figure 20] FIG. 20 illustrates an exemplary communication system. [Figure 21] FIG. 21 is a system diagram of an example RAN and core network. [Figure 22] FIG. 22 is a system diagram of an example RAN and core network. [Figure 23] FIG. 23 is a system diagram of an example RAN and core network. [Figure 24] FIG. 24 illustrates another exemplary communication system. [Diagram 25] FIG. 25 is a block diagram of an example apparatus or device, such as a WTRU. [Figure 26] FIG. 26 is a block diagram of an exemplary computing system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] In this specification, the term "device registration" refers to the process by which a device registers with the core network of a PLMN. Device registration refers to the method of establishing a signaling connection with the 4G network. Through the ATTACH REQUEST and 5G network registration This may be accomplished through a TION REQUEST. Device registration allows the UE to Able to connect to a mobile network and receive services from that network Device registration is also called "device association" or "device connection." It may also be possible.

[0017] In this specification, the term "M2M / IoT application" refers to an M2M / IoT device. This refers to an application that remotely controls / monitors / configures a device. This is typically Through the help of services provided by M / IoT servers, and these devices In the cellular case, this is done through a wireless cellular network. Usually, in 3GPP, Such applications are managed by an Application Server (AS). It is considered that.

[0018] In this specification, the term "M2M / IoT server" refers to a server that provides It means infrastructure nodes that provide M2M services. These services It reduces the burden on M2M / IoT applications and streamlines discovery, access control, and connection. oneM2M IN-CSE includes, for example, M 3GPP defines such an entity as a Service Capability Server. Service Capability Server (SCS) or Application Capability Function:AF).

[0019] As used herein, the term "PLMN transition" refers to the transition from one PLMN to another. PLMN transition refers to a transition made by a cellular device switching to a PLMN. Switching of one or both of the line access network and / or core network This may be accompanied.

[0020] [Table 1]

[0021] (Cellular Network Entity (Network Function)) FIG. 1 illustrates some cellular networks related to the systems, methods and apparatus described herein. - Network entities and cellular network functions. 3GPP TS 21.905 Please refer to Vocabulary for 3GPP Specifications, V 14.1.1.

[0022] Referring to FIG. 1, the mobility management entity (MME) performs registration, mobility, and I The entity in the cellular network that manages the UE reachability in DLE mode. The MME is also involved in authentication and authorization.

[0023] Access and Mobility Management Function (AMF) manages registration, connectivity, mobility and reachability AMF is a network function within 5G cellular networks that handles security management. Also, security features such as access authentication, access authorization, and access network specific key derivation Therefore, the AMF is similar to the MME in terms of functionality. This is what we do.

[0024] The Home Subscriber Server (HSS) stores subscription information about connected devices. The subscription information is stored in the cellular network. User identity (in the form of IMSI), used for authentication, encryption and data integrity The HSS also contains the security keys that are used to access the services and transactions that can be accessed. Sub-services, including the quality of service they will receive, the access technologies they can use, and the billing model. In the examples herein, the script may generally include a script parameter associated with the script. The HSS is assumed to include the functionality of an authentication center (AuC). The AuC functionality may be located in a separate entity.

[0025] Unified Data Management (UDM) stores subscription information about connected devices. UDM is a network function within 5G cellular networks. In some cases, the operator subscription information is The UDM may be stored in a data repository (UDR), in which case the UDM may be This is a form of front-end that reads subscription data.

[0026] The Service Capability Exposure Function (SCEF) is a 3GPP network interface A cellular network that exposes the services and capabilities offered by the The SCEF is the entity responsible for ensuring that the UE is reachable by third party applications. Determine the possibility of, set up network event monitoring, and allow group messaging This makes it possible to:

[0027] The Network Exposure Function (NEF) is provided by the 3GPP network. NEF is a network function that exposes the services and capabilities that are available. Third-party applications may collect information, for example about mobility or communication patterns. It provides a means to provide a cellular network. Thus, the NEF is It is similar to SCEF.

[0028] The Policy and Charging Rules Function (PCRF) provides real-time network and operational support. to and from our online systems, and other sources (e.g., external third-party servers). It aggregates information from, supports the creation of rules, and makes policy decisions based on this input. The rules require subscribers to: and other entities within the 3GPP network that manage traffic from these subscribers. This is provided to the entity.

[0029] Policy Control Function (PCF) collects subscription information and third-party servers It receives input from and supports a unified policy framework to determine network behavior. Network management functions that control and provide control plane functions with the policy rules that they enforce. It is a function.

[0030] The Network Data Analysis Function (NWDAF) is, for example, a network slice instance. You can share different types of network analysis information, such as load level information for The network functions that allow the network functions to request and obtain

[0031] 5G RAN is, for example, a new radio (NR) radio access point that connects to the 5G core network. It is a network.

[0032] 4G-RAN is the RAN used in LTE (Long Term Evolution) .

[0033] (IoT Cellular Deployment) Figure 2 shows a typical IoT cellular deployment. M2M / IoT applications It is an application that remotely controls / monitors / configures 2M / IoT devices. ,usually through the help of services provided by M2M / IoT servers, If the device is cellular, this is done over a wireless cellular network. In 3GPP, such applications are usually called Application Servers (AS). Typically, oneM2M considers such devices to be part of infrastructure applications. The entity is considered an application entity (IN-AE).

[0034] The M2M / IoT server is responsible for managing M2M / IoT applications and M2M / IoT devices. This is a server that provides value-added M2M / IoT services to devices. The main purpose of the service is to reduce the burden on M2M / IoT applications and M2M / IoT devices. The M2M / IoT server is responsible for data storage, data advertisement, access control, and In most cases, M2M / IoT applications and It acts as an intermediary between the application and the M2M / IoT devices. ,Does not directly communicate with devices. Instead, devices,transmit these data to M2M / IoT The data is stored in the server, and the data is then sent to the M2M / IoT application from the M2M / IoT server. In 3GPP, M2M / I In general, oneM2M / IoT considers oT servers as service capability servers. The server is considered as an Infrastructure Capability Service Entity (IN-CSE).

[0035] The M2M / IoT server can serve many different M2M / IoT applications (e.g., It is understood that the patient may be served PP1, APP2, APP3 and APP4. M2M / IoT devices may be associated / connected / registered to different networks. Therefore, M2M / IoT servers serving these devices must The interfaces to each of these networks (Network 1, Network 2) M2M / IoT applications can associate and connect to different networks. The M2M / IoT device may communicate with the registered M2M / IoT device. , may communicate with many different M2M / IoT applications. The server is responsible for managing M2M / IoT applications, networks, and M2M / IoT devices. It is the funnel point between the

[0036] (PLMN selection) In 3GPP, a cellular-enabled device is also known as a UE and is a network A network operator is also known as a Public Land Mobile Network (PLMN). A PLMN is typically Generally, each country is contained within its own national borders. Typically, an operator has a single PLMN per country. However, in some cases, an operator may have multiple PLMNs within its borders.

[0037] Typically, the UE performs a procedure known as PLMN selection to select the cell You must find a network that provides this service and register with that network. PLMN selection is described in TS 23.122, Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode, v15.2.0, as defined in The procedure is based on a set of rules defined within the UE. The UE typically Operates in its Home PLMN (HPLMN) or Equivalent Home PLMN (EHPLMN) But if, for example, the UE loses coverage or roams in a foreign country, In some cases, the serving PLMN (VPLMN) may be selected. Two modes of PLMN selection are described: automatic and manual mode.

[0038] In automatic mode, a list of PLMN / access technology combinations is used in order of priority. The highest priority PLMN / access technology combination available and acceptable is selected. It is selected.

[0039] In manual mode, the UE indicates to the user which PLMNs are available. Only when manual selection is made will the UE attempt to acquire normal service of the PLMN.

[0040] The UE may maintain several lists in its USIM. The UE may The EHPLMN list stores a set of PLMNs equivalent to the HPLMN. For example, an operator with two or more assigned Mobile Network Codes (MNCs) The UE may use user controlled PLMN selection with access technology. The UE may store a list of PLMNs provided by the user in a list of PLMNs. , by the network to an operator-controlled PLMN selector list with access technologies It may store a list of served PLMNs.

[0041] The UE may also specify a list of forbidden PLMNs, e.g., a list of PLMNs forbidden by the network. For example, the UE may store a list of MNs that are not allowed after a registration attempt. If the network responds with a "Recipient MN" message, it is added to such a list. A UE in automatic mode will not attempt to register to any PLMNs in this list. If successful, or if the timer associated with the PLMN entry expires, the PLMN removes the will be removed from the list.

[0042] Once a UE is registered with a PLMN, this PLMN is called the Registered PLMN (RPLMN). It is called "Ping-Ponging" to avoid UE from one PLMN to another. In order to speed up the initial startup time, the UE always uses the last or previous RP. Attempt to re-enroll in LMN.

[0043] In a switchover or recovery due to lack of coverage, the RPLMN is no longer available. If not, and the UE is in automatic mode, the UE shall select the most preferred PLMN it has found during its PLMN search. In contrast, if the RPLMN is no longer available, the system automatically selects the PLMN with the highest priority. If the UE is in manual mode, the UE shall select the PLMNs discovered during the PLMN search. The user then selects one of the discovered PLMNs. It is expected that you will choose.

[0044] The operation is slightly different while roaming in a serving PLMN. In such a case, the UE , periodically, the HPLMN (or equivalent HPLMN, or "user-controlled PLMN The PLMNs / ADDRESSES listed in the "PLMN Selector" or "Operator Controlled PLMN Selector" The service attempts to acquire a service that is based on a combination of the following access technologies (a combination of the following access technologies with a higher priority):

[0045] (Steering or Roaming) A UE may be directed to a specific PLMN using "roaming steering". When the UE receives a command of type "Steering roaming", it First, the UE is expected to perform the operation of The highest priority entry in the "operator controlled PLMN selector" list and the receiving Second, the UE shall use the list provided in the received command to replace the list provided in the received command. Remove the PLMNs identified by the list from the forbidden PLMN list (each list includes Third, the UE considers the new information and selects the P Finally, the UE attempts to access the LMN with the higher priority service. We will immediately attempt to obtain the

[0046] (Inter-PLMN communication (for roaming)) The 5G network supports two modes of roaming: home and home, as shown in Figure 3. Routing, and local breakouts as shown in Figure 4. Home P The control plane communication between the LMN and the serving PLMN is handled by the security edge protection proxy ( The SEPP protocol is used to send and receive messages and messages from the N32 interface. Message filtering and policing at the inter-PLMN control plane interface It is a non-transparent proxy that mainly supports user plane communication over the N9 interface. This is a UDP / IP connection from the VPLMN to the HPLMN. It involves multiple PDU sessions.

[0047] (Shared and Unlicensed Spectrum) The use of unlicensed and shared spectrum is already available for LTE devices. New considerations include unlicensed spectrum, license assistance and spreadsheets. A joint 5G initiative is underway to consider 5G NR operation both standalone and on-premises.

[0048] RP-172021, Study on NR-based Access to Unlicensed Spectrum The target is, "For example, in response to coordination requirements for the 5 GHz, 37 GHz, and 60 GHz bands, Within the R base and between unlicensed NR-based operation and LTE-based LAA "The 5GHz RAT will be able to coexist with other incumbent RATs," the report said. As a baseline, the LTE-based LAA context already specifies the 5 GHz band. However, these methods above 5 GHz are not compatible with the existing coexistence methods. The high level of coverage includes NR-based operation of unlicensed spectrum. The number of Wi-Fi servers deployed is higher than that of additional Wi-Fi networks from the same carrier. There should be no impact to services (such as data, video, and voice services).

[0049] (NSSP and URSP) The UE Routing Policy (URSP) is a policy provided to the UE by the PCF in 5GC. These policies are used to determine how outgoing traffic is routed. Used by the UE to route traffic to established PDU sessions. either be transferred to a new PDU session, offloaded to a non-3GPP access outside the PDU session, or This may trigger the establishment of a new PDU session.

[0050] The URSP is the SSCMSP used to map traffic to the SSC mode. (SSC Mode Selection Policy), used to map traffic to S-NSSAI NSSP (Network Slice Selection Policy) that maps traffic to DNs The DNN selection policy used to select the access network type and the traffic The access network preference used to map the The UE may also be used to decide how to handle the traffic. Local preferences may be determined by the URS. takes precedence over P.

[0051] (Congestion use case example) FIG. 5 is a block diagram of an exemplary congestion use case. In FIG. 5, an M2M / IoT server Through their corresponding Exposure Functions (EFs), the three operator networks The vehicle interfaces with the following networks: Operator 1, Operator 2, and Operator 3. Both management companies (TrackUS) have several sensors installed on all of their trucks. The vast majority of these devices generate very little data and have limited Although less common, some of them need to be switched on periodically for safety or monitoring reasons. TrackUS is a video camera that can be used in a variety of situations. For this purpose, two domestic operators (i.e., Operator 1 and Operator 3) and a preferred We negotiated the rates. Both rates are very good, but Operator 1's rate is only For this reason, TrackUS recommends that Operator 1 connect its devices / sensors. I prefer to do that.

[0052] Due to a traffic jam, operator 1 may disable its signaling channel for a particular cell. In 4G networks, the EPC will select the This can solve the problem by preventing the device from accessing the network. However, instead of blocking low priority sensor devices, Operator 1 Decide to migrate some of these devices to another operator. The server has useful UE context information (e.g. preferred operator) and can also Operator 1 is in a better position to decide which sensor to transfer to the data. , and request migration assistance from the M2M / IoT server.

[0053] The M2M / IoT server provides the services required by Operator 2 and Operator 3. Operator 3 is the preferred operator and accepts the device. The M2M / IoT server will then be configured with a priority to connect to this operator. The sensor disconnects from operator 1 and connects to operator 3. Reconnect to retrieve the service.

[0054] (Example problems caused by conventional solutions) Existing standards that provide for inter-PLMN UE migration are possible under two conditions. First, An example would be during international roaming when the HPLMN does not provide service. In this case, the UE is registered to the VPLMN and the HPLMN is the one to which the UE is roaming. In IDLE mode, the UE will not provide service in countries where it has a higher priority. Attempts to register with MN periodically.

[0055] The second is for domestic local area networks when the coverage hole is within the operator's coverage. HPLMN and VPLMN are within the same border, but The UE may be in a location where reception of the LTE signal is very weak or non-existent. For example, this , known in Canada as extended coverage or extended national roaming. If operator 1 does not provide coverage for those UEs, UEs may be pushed out to a competing network (operator 2). There are no additional roaming charges and subscribers receive roughly the same service as competing networks. You are entitled to a set.

[0056] In most cases, each PLMN manages its own network and is responsible for coverage reasons. (in cases of poor signal quality when roaming domestically or in cases of lack of presence when roaming internationally) UEs share each other (due to either the presence or absence of coverage) Therefore, the conventional mechanisms for sharing UEs between PLMNs, such as congestion resolution mechanisms, There is no mechanism for optimization, or any other optimization. As a result, PLMNs are It is required to discontinue providing services to those UEs (e.g. to terminate the connection to those UEs) In addition, inter-PLMN Even if this transfer is possible, the PLMN must decide on the best option to select the UE to transfer. The unique position of SCS in the IoT communication pathway may not be fully utilized. Not used.

[0057] The SCS has knowledge of the network context and visibility across multiple PLMNs. (information about neighboring PLMNs that a PLMN does not need to know about) Or you can get slice information (number of slices, type of slice) , the burden of the network or network slice (user plane and control plane) load, network coverage area (or coverage hole), number of UEs, network Active (CONNECTED, IDLE or SUSPENDED) UEs and (Mobile originated or Mobile terminated traffic Includes the average UE delay of

[0058] The SCS includes information from UE subscriptions, the number of flows per UE, the location of the UE, UE mobility patterns, UE reachability, flow history to / from the UE, UE power A large amount of UE content, such as power saving state and transmission characteristics (communication patterns) to / from the UE The text information may be included or may be obtained.

[0059] For illustrative purposes, the solution provides a means of sharing UEs between PLMNs for non-coverage reasons, e.g. For example, the above-mentioned methods are described herein as a means of resolving congestion or for some other optimization. However, the same solution is also proposed for sharing UEs between PLMNs for coverage reasons. For example, the UE may use any of the techniques described herein. The LTE-2000 may be migrated to a Mobile Virtual Network Operator (MVNO) using the LTE-2000.

[0060] (PLMN transition) The call flows in Figures 6 through 14 show an exemplary method for accomplishing a PLMN transition. To achieve this, in Figures 6 to 14, the UE first connects to its home PLMN and then It is assumed that the UE is transferred to the VPLMN after the UE is connected to the serving PLMN. The solution may also apply to cases where a VPLMN is migrated to another VPLMN or HPLMN. For example, if a UE connects to VPLMN1 and VPLMN1 becomes congested, In this case, VPLMN1 may request the server to migrate some UEs. The server then transitions the UE to another VPLMN (VPLMN2), or It may decide to move the UE back to the HPLMN.

[0061] In each of the methods in Figures 6 to 14, a new PLMN selection policy is offered to the UE at any time. A new NSSP for the URSP rule may also be provided.

[0062] (PLMN reselection triggered by M2M / IoT device) Manual network selection is performed by the device owner through the M2M / IoT server. M2M / IoT devices may be registered with the M2M / IoT server via PLMN / R. The M2M / IoT server then selects which combinations to try. Select the desired setting.

[0063] Some PLMNs, for example, provide Limited Local Operator Services (RLOS) connectivity. M2M / IoT devices connect via a network with very limited and restricted access. This access is assumed to allow these devices to / It is possible to contact the IoT server to get server assistance for PLMN selection. These PLMNs are said to support "limited access for assisted network selection." RLOS support. By broadcasting, the UE uses the RLOS connection to tell the network Determine whether the device supports "Limited Access for Selective Assistance" and then RLOS connection may use the service to launch "limited access for network selection assistance." Learn more are shown in Figures 6 and 7 and described below.

[0064] In the examples shown in Figures 6 and 7, M2M / IoT device Dev1 is deployed and a specific M2M Verify that the M / IoT device (Dev1) has a preferred PLMN / RAT list We assume that the M2M / IoT application has already notified the M2M / IoT server. For example, the list may include three PLMNs and two RAT types: PLMN1, / RAT1, PLMN1 / RAT2, PLMN2 / RAT1, PLMN3 / RAT1, and and PLMN2 / RAT1 combination.

[0065] In step 0, the PLMN of core network 1 includes, as part of its system information, Broadcaster confirms that it supports "limited access for network selection assistance" to.

[0066] In step 1, DEV1 performs a PLMN search (power-on, resulting in loss of connectivity). , or periodic searches) and determine a list of candidate PLMNs / RATs. For each entry in this list, DEV1 also calculates the intensity of the strongest cell (e.g., relative DEV1 determines the signal strength (RSS) of the PLMNs that it has registered in the past. No. They do not have a policy on which PLMN to select, or they do not have such a policy. If a policy exists, it is disabled. For example, a 3GPP UE may The camera may be set to a work selection mode.

[0067] As part of the search, DEV1 determines whether the PLMN has “Limited Access for Network Selection Assistance” In some cases, the SEC may decide to allow "service" on the basis of the

[0068] In step 2, DEV1 registers with the core network. DEV1 then Supports "limited access for network selection assistance" from MN / RAT combinations For example, DEV1 may select the PLMN / RAT combination it finds. Randomly select one of the combinations or select the combination with the strongest signal. or select a PLMN / RAT combination that has been used before, or select the first It may select the discovered PLMN / RAT combination. For the examples of Figures 6 and 7 Assume that the M2M / IoT device selects core network 1. The registration request is , Registration type = Limited access for network selection support, e.g., registration request is M2M / For limited access that allows devices to contact IoT servers and an indication to the core network that the

[0069] In step 3, the core network 1 accepts the registration.

[0070] In step 4, DEV1 sends a new NAS control message, ManualNetwor Issue a kSelection request to Core Network 1. For example, this message , may be directed to the AMF of the core network 1. The request may include a list of discovered cells. Each entry in the list may contain a PLMN / RAT list, such as May include the received signal strength of the cells and the identity of the strongest cell (e.g., Cell ID). Alternatively, the list may be sorted from the strongest PLMN / RAT combination to the weakest PLMN The request may also be sent to the M2M / IoT device. It may also contain the server address.

[0071] In step 5, the AMF of the core network 1 transmits the request to the NEF, The core network sends the request to the M2M / IoT server in turn. location (e.g. cell identity or tracking area identity) or the network used Other UE context information such as work slice may be included in the request.

[0072] The call flow in Figure 6 is continued in Figure 7. In step 6 of Figure 7, the M2M / IoT server , the stored preferred PLMN / RAT list received in the request and other received UE The server uses the context information to select the PLMN / RAT combination. The server may have local policies that assist in the selection of N / RAT combinations. The received information is displayed graphically to allow the user to select a PLMN / RAT combination. The server may display the PLMN / RAT combination in the user interface. Sends notifications to configured third-party application servers to let them choose There are cases.

[0073] Once the PLMN / RAT selection is done, the M2M / IoT server The networkSelection response is sent to the NEF of core network 1. F sends it to the AMF and then to the M2M / IoT device.

[0074] In step 7, the M2M / IoT device deregisters from the core network 1, Register with Core Network 2.

[0075] As a variant of step 4 in Fig. 6, the UE establishes a PDU session with the core network. Establish a network and send a ManualNetworkSelection request to the M2M / For example, the RLOS connection may take It may be used for.

[0076] As another variation of step 4 in FIG. 6, the message is delivered from the AMF to the PCF. The PCF may generate a new preferred PLMN / RAT list and send it to the UE. The PCF may send a PLMN preference (through the NEF) to the In this process, the IoT server may be involved by querying the IoT server (as a proxy). be.

[0077] As another variation, the information in step 4 of FIG. 6 may be sent together with the initial registration request. (Step 2). For example, a ManualNetworkSelection request is Next, the core network 1 may include the ManualNetwo Extract the rkSelection request and send it to the M2M / IoT server for assistance. The ManualPLMNSelection response may then be sent to the core network. The UE may then include the Manual PL Extract the PLMN information from the MNSelection response and schedule the next registration to this PLMN. You may try.

[0078] (PLMN reselection triggered by the core network) Conditions that the core network can resolve by migrating some UEs to another PLMN When an incident is detected, the core network may request assistance from the M2M / IoT server. .

[0079] If the M2M / IoT server has a preference for a PLMN and wants to redirect to another PLMN Assume that we need to control the manner in which device transitions occur. The details are shown in Figures 8 to 10. are shown and described below.

[0080] In step 1 of Figure 8, the M2M / IoT device (DEV1) connects to the core network 1 As part of the registration, the UE includes its capabilities, and then DEV1 registers with the core Indicates the capability of network directed PLMN reselection. Alternatively, this information The registration acceptance message may be part of the device subscription information. The network indicates to the UE whether it supports this capability or not. Broadcast by the network.

[0081] In step 2, Core Network 1 decides to start monitoring for a problem condition. AMF1 sends the MonitorSubscribe request to the The NWDAF will provide the latest analytical data on the Core Network 1. For example, the AMF1 provides the user plane UL and / or DL ​​of the RAN. Load, user plane UL and / or DL ​​load of the core network, control plane U L and / or DL ​​load of RAN, control plane UL and / or core network DL load or buffering load in the core network (e.g., unreachable U E), one may subscribe to monitor

[0082] In addition, the granularity of the subscribe request can be specified for a specific cell, tracking area, or network. The request may be directed to a slice, a UE, or a group of UEs. or may be based on threshold violations of monitored criteria.

[0083] Regarding call flow, buffering, device counting, and restrictions within the core network The control plane connection or user plane connection load exceeds a threshold (e.g., beyond its maximum capacity). Assume that AMF1 requests to be notified when the

[0084] In step 3, at some point, the buffering load exceeds a threshold. Sends a MonitorNotify request to MF. This is related to buffer overflow. The UE ID may include a list of UEs that are serving the UE.

[0085] In step 4, AMF1 determines whether most of the problem UEs are receiving services from the M2M / IoT server. AMF1 determines that some UEs are offloading to another PLMN. Alternatively, the AMF and / or The NWDAF sends the necessary information to the PCF (the UE in question, the M2 serving these UEs, M / IoT server, network load, location of the UE in question, etc.), The CF must initiate offloading of some UEs to another PLMN. Some local policy may be used to determine if

[0086] The call flow in Figure 8 is continued in Figure 9. In step 5 of Figure 9, AMF1 The UETransferInd request is sent to the T server by the UE may contain UE context information, including a request to transition a percentage of UEs This request is sent to the M2M / IoT server via NEF1. Indication of location of the network, observed traffic load (user plane and control plane) lane), UE reachability cycle, UE network slice type, etc. This requirement may also be affected by migration reasons (e.g. S-GW DL buffer load, UL sim This request may include an indication of the M2M / IoT The PCF may then decide whether or not to offload the request. may determine which devices have

[0087] In step 6, the M2M / IoT server (or PCF1) decides which U Determine E. The call flow assumes that DEV1 is one of these UEs. The M2M / IoT server determines the offload PLMN for DEV1. For example, M2 The M / IoT Server confirms that Core Network 2 is the preferred PLMN by this UE. or makes a decision based on UE context information in the request. For example, the M2M / IoT server has a coverage map of all PLMNs. Also, which PLMN serves the current UE location and is offloaded If necessary, the PCF1 may determine whether the UE is a suitable candidate for the MPLMN. This information may be obtained from a 2M / IoT server.

[0088] In step 7, the M2M / IoT server (or PCF1) r request) to ask Core Network 2 if it is willing to accept DEV1. As part of this requirement, the M2M / IoT server (or PCF1) must be able to Given a given UE context (communication patterns, observed traffic load, reachability The message may contain the following information: the route, the UE location, etc. The message is sent via the NEF2 to the AMF2 (or to PCF2). If necessary, PCF1 may either directly, through the NEF, or through the M2M / IoT server to the core network 2. Communicate.

[0089] In step 8, AMF2 (or PCF2) is ready to accept the registration of DEV1. If so, send a UETransfer response to the M2M / IoT server. This is an indication of the time window in which this registration should take place. The time window may include a period from each UE to be migrated to the core network 2. This may be used to distribute registration requests among multiple users. If the time window expires, Core network 2 may assume that the UE will not be migrated to core network 2 .

[0090] Core Network 2 may decide that it is not ready to accept DEV1's registration. This may be due to its own loading concerns or lack of coverage at the UE's location. This may be due to little or no

[0091] In step 9 of FIG. 9, the M2M / IoT server (or PCF2) receives the UE to be migrated, and an indication of the new PLMN for these UEs to the core network 1 The response is returned in the UETransferInd response message.

[0092] The call flow in Figure 9 is continued in Figure 10. In step 10 of Figure 10, AMF1 creates a new Sends a PLMNUpdate request to DEV1 with the PLMN information. This is a periodic Through the registration procedure, the tracking area update procedure, or by signing up for a new This may be through a dedicated control plane procedure. Alternatively, the AMF1 may: With a USAT REFRESH command modifier of type "roaming steering" , send an SMS to DEV1 to transfer the SMS to the selected PLMN (Core Network 2) may be efficiently steered.

[0093] The request also includes an activation time, when to attempt to register with Core Network 2. The activation time is determined by the core network. This can be used to distribute registration requests to the core network 2 so that many UEs can When the 1GbE 10 ... It may be used to reduce

[0094] In step 11, DEV1 deregisters from Core Network 1 and Register with Core Network 2 in between.

[0095] As a variation of steps 10 and 11, the PLMNUpdate request may be This may include a time window during which DEV1 performs initial registration with Network 2. Then, you can randomly choose a time in this window to attempt that initial registration. do.

[0096] To assist the M2M / IoT server and provide additional UE context information, In step 4, the AMF1 may request the UE to report neighboring PLMN information. Next, the UE performs a PLMN search to obtain the received signal strength of the PLMN / RAT combination. The discovered PLMN / RAT combination is sent to the core network 1 along with the indication of Alternatively, the UE may periodically measure the signal strength of neighboring PLMNs and provide The neighboring PLMNs may be configured to report signaling information to the core network 1. The information is part of the UE context information provided to the M2M / IoT server in step 5. It may be included as.

[0097] (PLMN reselection triggered by M2M / IoT server) The M2M / IoT server collects information and transmits it from one PLMN to another. , to detect conditions that may be beneficially addressed by migrating some UEs. There may be cases where this occurs.

[0098] M2M / IoT in the communication path between the core network and the M2M / IoT application Due to the location of the IoT server, the M2M / IoT server can share context information from both It is uniquely positioned to collect and determine the best PLMN to serve the device. are shown in Figures 11 to 14 and described below.

[0099] Step 1 in FIG. 11 is the same as step 1 in FIG.

[0100] In step 2a / 2b, the M2M / IoT server receives the context from the core network. For example, this may include, for example, cell, tracking area, network The information may include load information per slice, UE and UE group. Network usage history, such as hourly, daily, weekly, and holiday network usage history Similarly, the information may include the multicast capability information of the users that are part of the multicast group. E, and UEs using unlicensed or shared frequency bands, and It may include several band types.

[0101] The M2M / IoT server periodically updates this information and / or updates it as it changes. You may subscribe to get NWD via NEF. It may be configured as AF, PCF, AMF or UDM / UDR.

[0102] In steps 3a and 3b, the M2M / IoT server For example, the server collects information from each M2M / IoT application. Overall requirements may be collected, for example, in the form of communication patterns over different time periods.

[0103] In step 4, the M2M / IoT server receives the context information and the network status. status information to allow certain devices to migrate from one PLMN to another. For example, the M2M / IoT server may decide whether or not the balancing, sharing of multicast groups, minimizing interference in shared frequency bands, or decide to migrate the UE for resource and service allocation optimization. There may be cases where this occurs.

[0104] For example, for load balancing, the M2M / IoT server must The application requirements can be aggregated to determine the overall requirements for each UE. The M2M / IoT server is also aware of the available capabilities of each of the core networks. M2M / IoT servers dynamically adapt requests to available capacity and The load of these UEs across the network may be distributed. For example, DEV1 is connected to Core Network 1 during this time, and to Core Network 2 otherwise. The Board may determine that it is necessary to

[0105] Regarding multicast group sharing, the M2M / IoT server can share multicast with a group of UEs. The UE may know that it has a multicast message to send. Part of the loop is registered in Core Network 1 (SubGroup1), and Meanwhile, the rest of the group is registered in Core Network 2 (SubGroup2). Instead of using separate multicast groups for each core network, M2M / I An oT server can create a single multicast group on only one network. As a result, all UEs from one subgroup are transferred to the other core network. For example, the M2M / IoT server is multi-connected to DEV1 and 20 other devices. You may decide that you need to send out periodic multicast messages. The devices are registered in the core network 2 and are also part of that network. A multicast group is a local or multicast group. To avoid sending multicast messages to the M2M / IoT network, The server may ask DEV1 to register with core network 2.

[0106] To minimize interference in the shared frequency band, M2M / IoT servers must be installed in the same shared frequency band. A mobile station may decide to communicate to two sets of UEs using several bands. Set 1 The UEs in set 1 are registered to core network 1, while the UEs in set 2 are registered to core network The M2M / IoT server also checks whether these devices are in close proximity to each other. Each of the two networks may be aware of their own Since they manage a shared frequency band, UEs registered in the two networks can communicate with each other. By migrating two sets of UEs to a single core network, The network can then better manage traffic to and from these UEs. This allows for coordination to minimize interference.

[0107] To optimize resource and service allocation, M2M / IoT servers If one or more UEs decide that they do not require any network services for a certain period of time, In this case, the M2M / IoT server may intentionally and for a specific period of time These UEs are then migrated to PLMNs that support “Limited Access for Assisted Network Selection.” After that, the UE can receive all network services. A PLMN reselection is performed to a PLMN that can support the UE.

[0108] The call flow in FIG. 11 is continued in FIG.

[0109] In step 5 of Fig. 12, the M2M / IoT server is transferred from the core network 1 to the core If you decide that you prefer to migrate DEV1 to network 2, the other UE controllers of DEV1 For example, if DEV1 is not able to transition to the PLMN You may need to check whether the

[0110] Steps 6 to 10 in Figures 12, 13, and 14 are the same as steps 7 to 10 in Figures 9 and 10. Similar to 11.

[0111] (Active PLMN Selection List) The M2M / IoT server also determines the set of PLMN lists and provides this set to the UE. The UE can then use the local policy to determine which PLMN to use. The policy may determine the list based on the UE's location, the UE load, the applications running on the UE, The criteria may be based on one or more of the following:

[0112] The M2M / IoT server receives information from the PLMN (coverage map, load, etc.) and and information from the application server (UEs being served, UE routes, etc.), Additionally, it may collect information resulting from this determination of one or more PLMN selection lists. These selection lists are then sent via NAS signalling or via the US internal to the UE. It may be transferred to the UE via some USAT command targeted to the IM. The UE then periodically uses its local policy to determine the number of PLMNs in its PLMN selection list. A PLMN selection / reselection may be performed by selecting from among them.

[0113] For example, based on information collected from core network and application servers The M2M / IoT server then determines the location of the UE based on its current location and the current running application. For example, the server may create the following five lists: You may also create a list. PLMN List 1: Location: City A, UE Application: Any PLMN List 2: Location: City B, UE Application: Any PLMN List 3: Location: Other Location, UE Application: Application 1 PLMN List 4: Location: Other Location, UE Application: Application 2 PLMN List 5: Default

[0114] The M2M / IoT server then notifies the UE, for example through a USAT command or These lists may be transmitted to the UE through the core network in which it is currently registered.

[0115] The UE updates its list and uses its local policy to decide which list to use. If no valid condition matching the list is found, the UE uses the default PLMN. Listing 5 may be used.

[0116] (Non-roaming - Visited routing) M2M / IoT devices with limited radio access capabilities cannot be migrated to another PLMN. In such cases, an alternative method called non-roaming-visited routing is used. The following roaming scheme may be used:

[0117] In the illustrations of Figures 6 to 14, an M2M / IoT device is registered in its home PLMN. It was assumed that the mobile station would be transferred to another PLMN, such as the serving PLMN. As far as the network is concerned, when the UE moves from the Home PLMN to the Visited PLMN, Roam efficiently. 3GPP supports two roaming variants: local and It defines breakout and home routing. Both variants allow the user to In the case of local breakout, the user plane route is the The data remains in the LMN and the VPLMN forwards the data to the data network. In the case of a WAN link, the user plane path returns to the home PLMN and the HPLMN forwards the data These three variations, non-roaming, local breakout, Home-routing roaming and home-routing roaming are shown in Fig. 15 for configurations a, b, and c, respectively. These are indicated by c and b.

[0118] Figure 15 shows a total of six functional entities in five configurations. The first entity is U E, which is a device that requires service from a wireless operator. The UE connects to a RAN entity based on its radio access capabilities. The RAN_h is the radio access network function element of the home PLMN. RAN_h corresponds to a particular technology and frequency band.

[0119] The third entity is RAN_v, which is the radio access network of the serving PLMN. RAN_v is a network functional entity that corresponds to a specific technology and frequency band. The fourth entity is CN_h, ​​which is the core network function of the home PLMN. It is a functional entity that is of a particular type (e.g. EPC, 5GS) and a particular Capabilities (e.g. slice support type, service support type) are supported.

[0120] The fifth entity is CN_v, which is the core network function of the serving PLMN. It is an entity that has a particular type (e.g. EPC, 5GS) and a particular function. The sixth entity corresponds to the slice support type and the service support type. , DN, which is the data network with which the UE wishes to communicate.

[0121] For simplicity, Figure 15 omits the internal network functions of the core network. do.

[0122] A fourth roaming variant is possible for M2M / IoT devices. ,M2M / IoT devices can only use a single RAT and its own ,preferred operator’s , These devices can only connect to the RAN of the HPLMN.

[0123] Similarly, in some cases, operators may choose to only use a small number of M2M / IoT devices. In some cases, you may not want to instantiate a dedicated network slice for , hoping to leverage relationships with other operators that offer dedicated network slices. There may be cases where you want to push these devices out to other operators.

[0124] However, due to these RAT limitations, these M2M / IoT devices are It is not possible to connect to other operators' RANs because it does not support the above mentioned functions and / or bands. For devices such as Another roaming variant is proposed, called RAN_h (the RAN of the home PLMN). Control plane and user plane traffic The UE then selects the serving PLMN (CN_v) that provides the latest service required by the UE. This saves on the home PLMN providing these services. .

[0125] Note that the functions in CN_h may be mutable. For example, In some cases, a PLMN may have minimal functionality to support inter-PLMN communications. It may provide some of the control plane functions or all of the user plane functions. Similarly, it can, through its NEF, for example, forward user plane traffic to the C Using the UPF of CN_v to send / receive data to / from the NEF of N_h, In some cases, the company may provide access to the work.

[0126] The latter two cases above rely on the HPLMN to forward traffic to the DN. Therefore, to distinguish these cases from other cases, we call them “non-roaming-partially-covered routers.” A modified example is shown in FIG. 15(e).

[0127] This roaming variant may be implemented in any of the PLMN transitions described with respect to Figures 6 to 14. To support such transitions, the entity that triggers the transition may be The type of migration requested (roaming-local breakout, roaming-local breakout, We propose to be able to specify (home routing, non-roaming-visited routing). Specific details of the core network triggered PLMN reselection are shown in Figures 16 to 18. For brevity, the call flows in Figures 6 through 18 are divided into several parts. Note that the call flow is split across pages. Entities may be omitted on the individual pages of each figure to avoid confusion.

[0128] Steps 1 to 6 in Figures 16 and 17 are similar to steps 1 to 6 in Figures 8 and 9. is.

[0129] In step 7 of FIG. 17, once the M2M / IoT server has determined which UEs will be migrated, , and requires additional UE information from the core network 1, e.g., UE radio access capabilities. There may be cases where this is necessary.

[0130] The call flow in Figures 16 and 17 continues in Figure 18. In step 8 of Figure 18, / The IoT server can, for example, use the UETransfer request to transfer the As part of this request, the M2M / IoT server The server uses the available UE context (communication patterns, observed traffic load, arrival Availability cycle, UE radio access capability, type of transition (roaming-local break (Out, Roaming-Home Routing, Non-Roaming-Visiting Routing) The message is sent to the AMF2 (or to the PCF2) through the NEF2. can be.

[0131] In step 9, AMF2 (or PCF2) is ready to accept the registration of DEV1. If so, send a UETransfer response to the M2M / IoT server. This sends a reply to the server containing an indication of the time window in which this registration should occur. In addition, the UE may only be able to receive the service request when non-roaming-visited routing is used. It may also indicate that the

[0132] In step 10, the M2M / IoT server notifies the UEs to be migrated, E's new PLMN and an indication of the roaming variant to be used for these UEs This information is returned to the core network 1 along with the UETransferInd Included in the response message.

[0133] In step 11, DEV1 is configured to use the non-roaming-visited routing variant. If selected, AMF1 will be used to update the roaming configuration as may be done, for example, for roaming modifications. Thus, inter-PLMN communication is set up between two PLMNs.

[0134] The UE is unaware of this PLMN change and continues to use the same RAN. Once the RAN node has transferred the user plane and control plane traffic to the core network, When the traffic is delivered to network 1, it is the core network that forwards the traffic to network 2. This is the responsibility of Network 1.

[0135] Alternatively, RAN_h may share the same WAN_h and CN_h in a shared network configuration, for example. The RANs of the HPLMN may have connections to both N_v. It may broadcast that it is a shared cell between CN_h and CN_v. From the broadcast information, the UE knows that the core network is available through the cell. and, for example, the network slice support perspective of these cells. In this variant, step 11 of FIG. 18 is F change procedure, in which the AMF serving the UE , it will be changed from AMF1 to AMF2.

[0136] (Graphical User Interface) Figure 19 shows three Graphical User Interfaces. : An exemplary deployment of GUI) is shown. (GUI) is, for example, in the core network, It may be implemented in an M2M / IoT server or in an M2M / IoT device. The interface triggers certain actions described herein, as well as PLMN transition operations. Might be used to display related status.

[0137] The GUI may, for example, indicate the type of UE access (e.g., limitations for network selection assistance). access, RLOS, rules) or server-assisted network selection This may be used by the UE to trigger

[0138] The GUI allows to configure the PLMN selection policy for e.g. non-coverage related PLMN transitions. For example, the GUI may be used in the core network to view The buffering load of the network exceeds a maximum of 70% and the number of registered UEs exceeds 1000. This may be used to configure the policy under which the UE is transitioned if the UE exceeds the

[0139] The GUI may, for example, be used to trigger a PLMN transition for a UE or a group of UEs. This may be used by the 2M / IoT server, if it contains the target PLMN for each UE. The GUI provides a M key to enter the preferred operator for a UE or a group of UEs. 2It may be used in M / IoT servers.

[0140] (Example architecture) 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. .

[0141] 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.

[0142] FIG. 20 illustrates a conventional system in which the methods and apparatus described and claimed herein may be used. 1 illustrates an example of a communication system 100. Communication systems 100 may generally or collectively be referred to as Wireless Transmit / Receive Unit (WTRU) 102 may refer to a WTRU or multiple WTRUs 102. ansmit / Receive Unit:WTRU)102a, 102b, 102c, 102d, 102e , 102f and / or 102g. The communication system 100 may include wireless access Network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, Network 106 / 107 / 109, Public Switched Telephone Network e Network (PSTN) 108, Internet 110, other networks 112 and and network services 113. Network services 113 may include, for example, For example, V2X server, V2X function, ProSe server, ProSe function, IoT service , video streaming and / or edge computing.

[0143] 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. 20, each of the WTRUs 102 may be a handset. 20 to 24 as handheld wireless communication devices. In various use cases, each WTRU may be referred to as, by way of example only, a user equipment (UE), a mobile station, , fixed or mobile subscriber units, pagers, cellular telephones, mobile information Terminals (Personal Digital Assistants: PDAs), smartphones, laptops, tablets Redbooks, netbooks, notebook computers, personal computers, wireless sensors Consumer electronics products, wearable devices such as smart watches or smart clothing medical or e-health devices, robots, industrial equipment, drones, e.g. cars, buses, Transmitting and / or receiving radio signals, including on racks, trains, or airplanes Any type of apparatus or device that is equipped with or configured to It will be understood that this may be included.

[0144] The communications system 100 may also include a base station 114a and a base station 114b. In the example of FIG. 20, 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 102a and / or a network element. , 102b and 102c, 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 workpiece. Similarly, base station 114b communicates with remote radio head (RRH) 118. a, 118b, Transmitting and Receiving Points (TRP) 119a, 119b and / or Roadside At least one of Roadside Units (RSUs) 120a and 120b and a core network 106 / 107 that interfaces with the / 109, the Internet 110, other networks 112, and / or the facilitating access to one or more communications networks, such as a work service 113 The RRHs 118a and 118b may be any type of device configured to , wirelessly interface with at least one of the WTRUs 102, e.g., the WTRU 102c. The core network 106 / 107 / 109, the Internet 110, network service 113, and / or other networks 112, Any type of device configured to facilitate access to multiple communication networks. It may also be a chair.

[0145] 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.

[0146] 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. .

[0147] 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).

[0148] 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. .

[0149] 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.

[0150] 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

[0151] 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).

[0152] 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 Air interface 1 using LTE-Advanced (LTE-A) 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.

[0153] 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.

[0154] The base station 114c in FIG. 20 may be a wireless router, a home NodeB, a home eNodeB, or It may be an access point, for example, a business premises, a house, a vehicle, a train, an antenna, a satellite Facilitate wireless connectivity within localized areas such as satellites, manufacturing plants, campuses, and other locations. Any suitable RAT may be utilized for communicating with the base station 114c and the WTRU 102, e.g. For example, the WTRU102e is a wireless router that implements wireless technology such as IEEE802.11. Even if a Wireless Local Area Network (WLAN) is established, Similarly, the base station 114c and the WTRU 102, e.g., the WTRU 102d, may Implementing wireless technologies such as EE802.15 to create wireless personal area networks (WPAs) The base station 114c and the WT The RU 102, e.g., the WTRU 102e, is a cellular-based RAT (e.g., WCD MA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) As shown in FIG. 20, the base station 114c may establish an internet cell or a femto cell. The base station 114c may have a direct connection to the internet 110. You need to access the Internet 110 through the Internet network 106 / 107 / 109. There may be no need.

[0155] 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.

[0156] Although not shown in FIG. 20, RAN103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or Core Network 106 / 107 / 109 RAN103 / 104 / 105 and / or RAN103b / 104b / 105b may communicate directly or indirectly with other RANs employing the same or different RATs. For example, it will be appreciated that the RAN 103 may utilize E-UTRA radio technology. / 104 / 105 and / or RAN 103b / 104b / 105b In addition, the core network 106 / 107 / 109 also uses GSM or NR radio technology. It may also communicate with another RAN (not shown) that it employs.

[0157] 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 (registered (Registered Trademark) Network) or RAN103 / 104 / 105 and / or R It may adopt the same RAT as AN103b / 104b / 105b or a different RAT. The RAN may include another core network connected to one or more RANs.

[0158] 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. 20 may employ a cellular-based wireless technology. Base station 114a, and base station 114c, which may employ IEEE 802 wireless technology. may be configured to communicate.

[0159] Although not shown in FIG. 20, the user terminal may make a wired connection to the gateway. It will be understood that the gateway is a residential gateway. RG is a gateway that is part of the core network 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.

[0160] FIG. 21 is a system diagram of an example of the RAN 103 and the core network 106. As mentioned above, RAN 103 adopts UTRA radio technology and provides air interface 115 The RAN 10 may communicate with the WTRUs 102a, 102b, and 102c through the RAN 10 may also communicate with a core network 106. As shown in FIG. 3 communicates with the WTRUs 102a, 102b and 102c over the air interface 115. Node-Bs, each of which may include one or more transceivers for communicating with Node-B 140a, 140b, and 140c. and 140c are each associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a and 142b. may contain any number of Node-Bs and Radio Network Controllers (RNCs). Please understand that.

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

[0162] The core network 106 shown in FIG. 21 includes a media gateway MGW) 144, Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148; and / or Gateway GPRS Support Node (GPRS Node: Each of the above elements may include a core network 106. Although depicted as part of the core network, any one of these elements may be You understand that the Services may be owned and / or operated by entities other than the Operator. Let it be understood.

[0163] 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.

[0164] 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

[0165] 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.

[0166] FIG. 22 is a system diagram of an example of the RAN 104 and the core network 107. As mentioned above, RAN104 adopts E-UTRA radio technology and has air interface 1 16 with the WTRUs 102a, 102b, and 102c. may also be in communication with the core network 107.

[0167] 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.

[0168] 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. 22, eNodeBs 160a, 160b, and 160c may They may communicate with each other through the X2 interface.

[0169] The core network 107 shown in FIG. Management Gateway (MME) 162, Serving Gateway 164, and Packet Packet Data Network (PDN) Gateway 166 Each of the above elements is depicted 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 will be understood that the information contained herein may be owned and / or operated by third parties.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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 .

[0174] FIG. 23 is a system diagram of an example of the RAN 105 and the core network 109. AN105 employs NR radio technology and supports WTRU10 over the air interface117. RAN 105 may also communicate with core network 102a and 102b. 9. Non-3GPP Interworking Function nction: N3IWF)199 adopts non-3GPP wireless technology to improve the air interface The N3IWF 199 may also communicate with the WTRU 102c through the core network. The wireless communication device may communicate with network 109.

[0175] 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.

[0176] 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.

[0177] 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. 23, gNode-B 180a and 180b are connected to the Xn interface. They may communicate with each other through an interface.

[0178] The core network 109 shown in FIG. 23 is a 5G core network. The core network 109 may be a wireless access network. A network may provide numerous communications services to its customers that are interconnected by a core network. The network 109 includes several entities that perform the functions of a 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. Core Network Entity means radio and / or network communication, Or an apparatus configured for a computer system such as the system 90 shown in FIG. The computer-executable instructions ( It is understood that the present invention may be implemented in the form of a logical entity such as software. .

[0179] In the example of FIG. 23, the 5G core network 109 includes an access and mobility management function (Ac Session and Mobility Management Function (AMF) 172, Session Management Function (S ESSION MANAGEMENT FUNCTION (SMF) 174, USER PLANE F function (UPF) 176a and 176b, User Data Management Function (User Data Management ement Function (UDM) 197, Authentication Server Function (Authentication Server Function n:AUSF) 190, Network Exposure Function :NEF) 196, Policy Control Function (PCF) 184, Non-3GPP Interworking Function (N3IWF) 199, User Data Repository (Us Each of the above elements may include the User Data Repository (UDR). Although represented as part of the G-Core Network 109, any one of these elements One is owned and / or operated by an entity other than the core network operator. It will be appreciated that the 5G core network may be comprised of all of these elements. may not be present, may consist of additional elements, and each of these elements may consist of multiple It will be appreciated that each network function may be configured with multiple instances. Although a direct connection to the Diameter routing agent is shown in Figure 23, These may be communicated through a routing agent such as a client or message bus. It should be understood that.

[0180] In the example of Figure 23, connectivity between network functions is expressed as interfaces or A network function can communicate with other network functions or It is modeled as a set of services that are invoked or called by a service. It will be understood that the Network Function Services may be modeled, described, or implemented in any manner. The service launch is based on direct connections between network functions, messaging exchanges on a message bus, This can be achieved via software function calls.

[0181] 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 FIG.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] 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. provides policy rules to control plane nodes such as AMF172 and SMF174. Each control plane node may then enforce these rules. 4 sends policies for the WTRUs 102a, 102b, and 102c to the AMF 172. As a result, the AMF may transmit the , 102b and 102c. The policy may then be distributed to the WTR May be enforced or applied under U102a, 102b and 102c.

[0186] 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.

[0187] 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.

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

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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.

[0193] Referring again to FIG. 23, in a network slicing scenario, the WTRU 102a, 102b or 102c when connecting to AMF172 via N1 interface An AMF may be logically part of one or more slices. The WTRU 102a, 102b, or 102c and one or more UPFs 176a and and 176b, SMF174, and other network functions. UPF176a and 176b, SMF174, and other networks 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 use different computing resources. They are separate from each other in that they may use the same services, security certificates, There may be cases where this occurs.

[0194] 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

[0195] The core network described herein and illustrated in Figures 20, 22, 23 and 24. The network entities are given the same rights as those entities in certain existing 3GPP specifications. Although these entities and functions will be identified by names used in the future, Certain entities or functions may be identified by their names in the future. Combination in future specifications published by 3GPP, including the GPP NR specifications It should be understood that in some cases, Figs. The specific network entities and functions described and illustrated in 4 are provided as examples. The subject matter disclosed and claimed herein is provided solely for illustrative purposes and is not intended to be limiting or to be limiting, either currently or in the future. embodied or in any similar communication system, whether or not conventionally defined. It is to be understood that there may be implementations.

[0196] FIG. 24 illustrates a communication system in which the systems, methods, and devices described herein may be used. 1 illustrates an example of a wireless communications system 111. The wireless communications system 111 includes a wireless transmit / receive unit (WTRU) A, B, C, D, E, F, base station gNB121, V2X server 124, and roadside In practice, the present invention may include RSUs 123a and 123b. The presented concept can be applied to any number of WTRUs, base stations gNBs, V2X networks, and / or or other network elements. WTRUs A, B, C, D, E and F are located in the access network coverage of 131 Among V2X group WTRUs A, B, and C, WTRU A is the group leader, and WTRUs B and C are group members. do.

[0197] 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. 24, WTRUs B and F may communicate with each other via the access network. WTRUs A, B, C, D, E and F are shown in coverage 131. Sidelink interfaces such as 125a, 125b or 128 (e.g. For example, via PC5 or NR PC5, they are covered by the access network. Whether it is under the access network coverage 131 or outside the access network coverage 131 For example, in the example of Figure 24, WTRU D, which is outside coverage 131, and WTRU F, which is within coverage 131, Communicate.

[0198] 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 .

[0199] FIG. 25 illustrates a WTRU 102 as described herein, such as the WTRU 102 of FIGS. When configured for wireless communication and operation in accordance with the systems, methods and apparatus described herein 25 is a block diagram of an example of an apparatus or device WTRU 102 having a The exemplary WTRU 102 includes a processor 118, a transceiver 120, a transmit / receive element 122, and a , speaker / microphone 124, keypad 126, display / touchpad / in indicator 128, non-removable memory 130, removable memory 132, power supply 13 4. Global Positioning System (GPS) chipset 136 , and other peripherals 138. The WTRU 102 may include any of the above elements. It should be understood that the combination may include subcombinations. 4b, and / or base stations 114a and 114b, including, but not limited to, In particular, base transceiver station (BTS), Node-B, site controller, access point AP, Home Node-B, Evolved Home Node-B B: eNodeB), Home Evolved Node-B (HeNB), Home evolved Node-B gateway, next generation Node-B (Generation Node-B:g Node-B), and proxy node, as described herein, and It may contain some or all of the elements depicted in 5.

[0200] 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 25, 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 well understood.

[0201] The UE's transmit / receive element 122 communicates over the air interface 115 / 116 / 117. 20), or the air interface 115d / Transmitting signals to or receiving signals from other UEs via 116d / 117d 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 receive and / or transmit a signal. For example, configured to transmit and / or receive IR, UV, or visible light signals The transmit / receive element 122 may be an emitter / detector. 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 Let it be.

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

[0203] 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 may be configured to support multiple RATs, such as NR and IEEE802. 2.11, or communicate via NR and E-UTRA, or different RRHs, T Allows communication with the same RAT via multiple beams to RPs, RSUs or nodes For this purpose, it may contain multiple transceivers.

[0204] 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 may be 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 on a server where 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 .

[0205] 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.

[0206] 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.

[0207] 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.

[0208] 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.

[0209] FIG. 26 shows the RAN 103 / 104 / 105 and the core network 106 / 107 / 109. , PSTN 108, the Internet 110, other networks 112, or 20, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52 One or more devices of the communication network shown in FIG. 23 and FIG. 24 may be embodied. FIG. 9 is a block diagram of an exemplary computing system 90 having a The operating system 90 may include a computer or a server, and may be implemented in the form of software (such as Where or by what means such software is stored or accessed, The device may be controlled primarily by computer readable instructions, which may be a programmable program (even if the programmable program is a programmable program). Such computer readable instructions may be used to operate the computing system 90. , may be executed within the processor 91. The processor 91 may be a general-purpose processor, a special-purpose processor, or processors, conventional processors, digital signal processors (DSPs), multiple microprocessors processor, one or more microprocessors associated with a DSP core, a controller , microcontrollers, application specific integrated circuits (ASICs), field programmers FPGA circuits, any other type of integrated circuit (IC), state machines The processor 91 may be a processor for signal coding, data processing, power control, input / output processing and / or computing system 90 operating within a communications network The coprocessor 81 may also implement any other functionality that enables the coprocessor 81 to operate in a manner that is consistent with the primary An optional processor distinct from processor 91 that performs additional functions The processor 91 and / or the coprocessor 92 may Processor 81 receives, generates and processes data related to the methods and apparatus described herein. The information may be processed in a timely manner.

[0210] 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 PXI Express Component Interconnect bus is a NI PXI Express Component Interconnect bus.

[0211] 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.

[0212] 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:

[0213] 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.

[0214] Further, the computing system 90 may be implemented as shown in FIGS. 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.

[0215] 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.

Claims

1. A processor, a memory, and a communication circuit, the communication circuit being connected to a communication network. a device coupled to said device, said device including computer executable instructions stored in said memory; the computer-executable instructions being executed by the processor of the device. When executed, the device: Related to network support for limited access to network selection assistance receiving system information from a first wireless network; sending a modified registration request to the first wireless network signaling a restricted registration; And, Transmitting a manual network selection request; a manual network selection response including an indication of connecting to the second wireless network; Receiving and deregistering from the first wireless network; registering with the second wireless network; A device that performs the above function.

2. The change registration request further signals support for a non-coverage related wireless network transition. The apparatus of claim 1 , further comprising:

3. The manual network selection request includes a list of discovered wireless networks. Item 2. The device described in item 1.

4. The second wireless network is selected from the list of discovered wireless networks. The apparatus of claim 3 .

5. The manual network selection request includes receiving a signal strength for each discovered wireless network. The apparatus of claim 3 further comprising:

6. The manual network selection request is The apparatus of claim 3 further comprising cell identification information.

7. The manual network selection request is transmitted to the Internet of Things via non-access stratum messaging.

2. The apparatus of claim 1, wherein the information is transmitted to an Internet-of-things (IoT) server. 。

8. The manual network selection request is transmitted via non-access stratum messaging to a policy-controlled 2. The apparatus of claim 1, wherein the policy control function (PCF) receives the policy control information from the policy control function.

9. The manual network selection request is sent via Internet Protocol (IP) Restricted Local Operator Services (ROS) are provided using IP-based communications.

2. The method according to claim 1, wherein the request is sent to an IoT server via a Remote Landing Service (RLOS) connection. The equipment.

10. The instructions further include causing the device to transmit the manual network selection request to the change registration request. The device of claim 1 .

11. The instructions further include causing the device to transmit the manual network address embedded in the registration response. The apparatus of claim 10 , further configured to receive a selection response.

12. A processor, a memory, and a communication circuit, the communication circuit being connected to a communication network. a device coupled to said device, said device including computer executable instructions stored in said memory; the computer-executable instructions being executed by the processor of the device. When executed, the device: registering on a first wireless network; The first wireless network is configured to support a non-coverage associated wireless network transition. Gunning and receiving a request to perform a wireless network search from an IoT server; Sending a list of discovered wireless networks to the IoT server; A transition request indicating a second wireless network selected from the list of discovered networks. receiving a request; deregistering from the first wireless network; registering with the second wireless network; A device that performs the above function.

13. The transition request may include a transition time for determining when to deregister from the first wireless network and to transition to the second wireless network. The device of claim 12, further comprising an activation condition indicating whether to register with the network. Place.

14. The apparatus of claim 13 , wherein the activation condition is time.

15. The transition request determines when to stop attempting to register with the second wireless network and to transition to the first wireless network. and an activation window indicating whether to return to the wireless network; The instructions further include causing the device to: canceling registration from the first wireless network and registering with the second wireless network 、 13. The apparatus of claim 12.

16. A processor, a memory, and a communication circuit, the communication circuit being connected to a communication network. a device coupled to said device, said device including computer executable instructions stored in said memory; the computer-executable instructions being executed by the processor of the device. When executed, the device: A first group of user equipment (UE) devices from a first wireless network determining that a group needs to be migrated, the UEs of the first group being Determining, served by an IoT server; Sending a first transition request to the IoT server; A transition response including a first indication of available capabilities and a second wireless network. from the IoT server; a second indication of the second wireless network based on the available capabilities. transmitting one or more second transition requests to a second group of UEs including: A device that performs the above function.

17. The instructions further include configuring the device to: or based at least in part on a signaling load, on the first wireless network. A first portion of the first group of user terminal devices (UE) needs to be migrated from the network The apparatus of claim 16, further comprising:

18. The first transition request is a list of the first group of UEs; positions of the first group of UEs; the network load of the first group of UEs; The reason for said first transition request; 17. The apparatus of claim 16, comprising at least one of:

19. A processor, a memory, and a communication circuit, the communication circuit being connected to a communication network. a device coupled to said device, said device including computer executable instructions stored in said memory; the computer-executable instructions being executed by the processor of the device. When executed, the device: an application server, a user equipment (UE), and a first wireless network, requesting context information from the one of the application server, the UE, and the first wireless network; collecting a set of contextual information from one or more of the Based at least in part on the set of context information, determining that the UE needs to be migrated to; sending a first transition request to the second wireless network; an indication that the second wireless network is willing to accept registration of the UE; receiving an acknowledgment from the second wireless network including the sending a second transition request to the UE via the first wireless network; A device that performs the above function.

20. The instructions further include causing the device to based at least in part on a multicast capability of the second wireless network.

20. The apparatus of claim 19, further comprising: a UE forwarding device configured to forward a UE to a mobile station;

Images